Meeting Minutes for 03/27/2019

Marmot Union Cataloging Committee
Wednesday, March 27, 2019
Minutes in blue text

Announcements

• Montrose is migrating to Marmot in the fall.  In preparation for that, they have joined the UCC.  We welcome them for their first meeting today.
• Lloyd discovered that in print templates the “.replace” command is not compatible with JAVA 1.8.  If your print templates stopped working, let Lloyd know.

Completed action items

Discussion Topics

• Double 001 fields from Bemis load.
  • How to deal with these problems.
  • We look at some examples.
  • The Tableau login we are using for deduping is ‘dedupe’.  The value of that is that we share the same view, so when one user excludes a pair that they cleaned up, then that is removed for all users of the same view.
  • Lloyd resaves the view after each save.  It is very fast to save, and very annoying if you do a bunch and forget to save.
  • When you see two numbers in the 001 duplicate checker that will be one of the duplicates created by the Bemis load.  The second number in quotation marks will be the duplicated number. Search on that to find the duplicate.
  • We look at some examples of 001 duplicates created by the Bemis load.
  • One situation we encounter is where one record described a single volume in the set the second record describes.  They have a matching 020 because the set record includes the ISBNs for all the individual volumes. In that case, Lloyd would move the ISBN for the single volume in the set record into subfield |z in the 020 so that it would still be searchable, but not act as a match point.  Also delete the duplicated 001.
  • We find an example where it appears there is a duplicate record in OCLC.  Lloyd emails OCLC at bibchange@oclc.org to suggest they combine these records.
  • Betsey points out that those who are not OCLC members can’t check Connexion so this process is more difficult to perform.
  • We look at worldcat.org, but we don’t see any way to view a MARC record, so it is not useful.
  • We find an example of a record that has been combined at OCLC, so we can combine them in our system.
  • Lloyd points out that he thinks he has thought of a way to improve the loading process for the Montrose load that will allow us to get any good OCLC numbers without creating the duplicate 001 issue.
• Report from Duplicates team meeting with SD
  • Ideas for DVD grouping.
    • Pika currently groups DVDs based on publisher not author
    • We don’t know if Pika is aware of 264
    • Publisher is not reliable regardless
    • Discussed ideas for how DVDs could be grouped
    • We need to use a field that all records will have, so 130 is not good.
    • Pika could look at 700 fields.
    • They would be normalized and alphabetized.
    • Maybe if three of them match, also title, then that would be grouped.
    • SD wants us to find examples of DVDs that we want grouped, and that we don’t want grouped.
    • They want examples that will be a problem for a system matching on three 700 fields.
    • The group explores various options for how we might group DVDs.
    • Someone suggests we consider using running time to determine if two films are the same.
    • Running time is in the 008 fixed field, so there is a clear place we can get a normalized figure for matching.
    • Maybe we could create a linking code in the MARC record that would tell Pika to group things.  It would function as a manual override for grouping that you could control from Sierra.
    • Action Item: Lloyd discuss with Pika team about using running time as the second check for grouping.
  • We asked about how Pika could deal with the set vs. volume problem
    • At the meeting, Pascal mentioned that we might be able to improve the set vs part holds problem if we had volume records.  Lloyd heard from JeffCo library where they have transitioned to volume records in a long project. They are very happy with them.  Lloyd wants to explore if this would be an improvement.
    • Lloyd wonders if it would be possible to export our records and reimport them with a volume record structure.
    • We discuss how volume records work.  They would be attached to bib records and items would be attached to them.  Each volume would get a volume record and each copy of that volume would have an item record attached to that volume.
    • JeffCo took years to move items over to volumes manually.  It does not have to happen all at once. The system will work with some bib that have volumes and others have items directly attached to bibs.  JeffCo only uses them for sets and serials.
    • It is not clear if we can use load profiles to create volume records.  Lloyd thinks it might be possible, but probably would require III. It might not be possible to reload our items without losing our circulation data.
    • Currently Pika is limited by what the classic catalog can do.  Holds really work through the classic catalog, so we don’t have much flexibility.
    • However, SD is planning to rebuild the backend of Pika to access SierraDNA instead of screen-scraping the classic catalog.  Then we could do something with the set vs volume problem.
    • SD is hoping to implement this by next summer.
    • SD would like us to write up a paragraph describing how we would like the set vs volume issue to work so they could include that in the development.
      • Jamie asks how we could deal with the case where three different libraries catalog the same item differently.  How should the system deal with the case were one library catalogs as a single set, another catalogs individual parts and another has subgroups of the set?  They may be on different bib records.
      • Lloyd suggests that Pika should have a system for when someone puts in a request for something with volumes, then it would pop up a dialog box asking which volume, or group of volumes the person wants, even if they are not on the same bib.  They should be able to request anything in the same format facet.
      • We also have to look into the question of whether volume records would be helpful or not.  We would have to find out how volume records are available to SQL.
  • Lloyd met with Rose from Prospector at the CLiC meeting.  We talked about how to get the display to work correctly. When we suppress on the item level, the bib still shows up in Prospector.  We will work with them to try figure out if there is a better way to handle our suppressed items. It appears that there are other codes we could use to make them display differently. [Later we learned we need to use ITYPE.  Our ITYPEs get translated into different things in Prospector.]
  • We have a discussion of the weird things we have in ICODE2. The TITLE and CHAPTER codes are for SD51 who need to keep track of when they purchase items with federal money.  They need to keep that information and be able to find those things easily.
  • Amy Currier announces that she is leaving CMC to take a job at Utah Valley University.  This will be her last UCC meeting.

New Action Items

Ongoing Action Items

• Duplicates Sub-committee meeting: April 10, 9-10 MT
• Next UCC meeting: April 24, 9-11 am MT