Authority match sets are not working

Bug #867691 reported by Kathy Lussier
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Undecided
Unassigned
2.2
Fix Released
Undecided
Unassigned
2.3
Fix Released
Undecided
Unassigned

Bug Description

In master, the new authority match sets don't seem to be working. I set up match set to match on 010a, imported a fresh batch of authority records, and then re-imported the same batch using the new match set I had created. The system didn't find any matches. I tried with various other match sets without success.

tags: added: vandelay
Revision history for this message
Jason Stephenson (jstephenson) wrote :

I'm not sure this bug is still relevant. I think it may have been fixed elsewhere.

Changed in evergreen:
status: New → Incomplete
Revision history for this message
Kathy Lussier (klussier) wrote :

Just re-tested in master and can confirm that it is still a problem. I think the other fix was on an unrelated issue.

Revision history for this message
Lebbeous Fogle-Weekley (lebbeous) wrote :

You were trying authority records? Match sets don't work on those, only on bibs.

If I understand the situation correctly, we need to convert this into a wishlist bug expressing the need for authority record match sets and/or a better, more clear grouping of functions in the Import/Export user interface.

Revision history for this message
Kathy Lussier (klussier) wrote :

Hmmm. I'm confused. If authority matching is not supported, why are there match sets that you can create with an "authority" type?

Revision history for this message
Mary Llewellyn (mllewell) wrote :

I was going to point out the same thing, "authority" is presented as an match set type when creating a new match set.

Revision history for this message
Lebbeous Fogle-Weekley (lebbeous) wrote :

Thanks for pointing that out. Match sets have a field internally to signify whether they're for bibs or authorities to allow for future expansion, but that should not have been exposed in the user interface. That is definitely misleading. So the immediate thing we ought to do is fix the interface.

Revision history for this message
Mark Cooper (markchristophercooper) wrote :

I also tried making a match set and overlaying a few authorities before realizing the feature isn't there yet.

In the meantime: hide authority option from new match set --

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/mcooper/lp867691

tags: added: pullrequest
Bill Erickson (berick)
Changed in evergreen:
assignee: nobody → Bill Erickson (erickson-esilibrary)
status: Incomplete → In Progress
Revision history for this message
Bill Erickson (berick) wrote :

Tested and pushed Mark's patch to 2.2, 2.3, and master. Thanks, Mark. I'm going to mark this as fix-committed (so we can clear it from the pending pullrequests). I'd say a separate wishlist entry is in order if we want to address authority match set support in general.

Changed in evergreen:
status: In Progress → Fix Committed
milestone: none → 2.4.0-beta
assignee: Bill Erickson (erickson-esilibrary) → nobody
Ben Shum (bshum)
Changed in evergreen:
status: Fix Committed → Fix Released
Revision history for this message
Kyle Tomita (tomitakyle) wrote :

Just adding a link to the new bug, https://bugs.launchpad.net/evergreen/+bug/1171984, some might find this link useful so they do not have to search for it.

Yamil (ysuarez)
tags: added: authority
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.