Compare bibs with an outside source - Leap
We would like the ability to compare bibliographic records in Leap with ones from an outside source, like z39.50. This is a key part of our cataloguing process and is a necessary piece to moving those staff members over to Leap.
-
MEEP candidate for the Polaris 8.3 release
Functional Requirements (what does it need to do?)
- Update Compare workform in Leap to include bibliographic records from remote databases
- Update the initial Find Tool that launches from the Compare action on a bibliographic record to include the ability to switch to Bibliographic Record (Remote Databases) and select one or more records to add to the Compare workform
* Not expected to exceed current maximum selection, may need to limit further due to performance issues with remote database connections
- Display the MARC from the record retrieved from the remote database
* Bib record launch icon would be disabled for remote records that have not been saved to the local Polaris database
- Allow the staff member to copy tags from the remote bibliographic record to a locally saved record
- Allow the staff member to save the remote bibliographic record to the Polaris database -
Catherine Eilers
commented
A cataloger just asked me if this is possible--certainly not having it is causing frustration at our library.
-
Christy Sayre
commented
This would be a huge timesaver. We already use Leap, but it would save time and be less confusing if we could see remote records side by side with our existing ones within Leap. Switching between tabs in the browser or scanning across different browser windows introduces a drag on continuity of the workflow and slows down decisionmaking.
-
AdminKatie LeBlanc
(Admin, Innovative)
commented
I feel like this can be accomplished easily if we can have Bibliographic Records (Remote Databases) be a search option when pulling in a comparison record? While cataloging is used to starting at the Remote Database bib, they could be trained to pull the existing record up first then compare to remote.
-
Vanessa Schwegman
commented
Z39.50 is essential to our library's cataloging processes. Leap absolutely needs this functionality in order for it to work for our cataloging team.
-
Christine Sneed
commented
This would be necessary before our cataloging team would even consider beginning to use Leap. We rely pretty heavily on z39.50 cataloging - and being able to compare a current record with one from OCLC is something we are doing constantly.
-
Ken Sawdon
commented
This is a vital part of our cataloguing processes. We want to create the best records we can, so we'll often pull the Subject Headings from one source, the Description from another, etc.
It's also helpful when we have concerns with something previously catalogued in our database and want to see how our record compares to other libraries. For example, how others have dealt with a sensitive topic.