Meeting Minutes for 03/28/2018

Marmot Union Cataloging Committee
Wednesday, March 28, 2018
Minutes

Announcements

• New Z39.50 targets in Sierra
  • Training for Aspen Schools next week

Reports

• Duplicate Committee Report
  • Discussed creating our own duplicate checking utility, probably with Tableau
  • Discussion later in the meeting

Reindexing Report

• If we do our own duplicate checker, does that change the reindexing project?
• Reindexing group determines that it does not make much difference.
• We decide to leave the 074s in the ISN index.  CMU does search on this and we are not sure what will be the effect of removing this from the index.  We won’t care about the effect on Headings Reports once we have our own utility.
• Patron birthdate plan for Garfield 
  • Garfield wants to be able to search patrons on birth date.  This requires that we copy the birth date information from the fixed field to a variable field.  Lloyd thinks we can do this with scheduler, which would export Garfield’s patrons every night, then reload them with a patron loader that would move the information.  Lloyd will experiment with this process.  Assuming it works, the variable field will get indexed in our upcoming reindexing project.  Anyone else interested in the ability to search birth dates could be added to the process.  
  • *Action Item: Lloyd will experiment with copying this data with a patron load profile
• Moving 590s with attached records
  • Tested this and it works.  Opened a ticket with III with question about the 690.
    • We will move the 590s into field group tag v, so they will move with attached records.  We want to know what will be the effect of putting 690 in v as well.  We would like them to move with the 590s, but we aren’t sure what that will mean for the subject indexing of the 690s.
    • *Action Item: Lloyd will experiment with what happens to indexing when you put 690s into the v field group tag.
• Grouping travel books meeting
  • YouTrack tickets D-1952 and D-1953 created.
    • The group investigated the issues with grouping travel books in Pika.  
    • We found that Pika treats an ampersand in a title differently from the word ‘and’ spelled out.  This will cause two records where the only difference is the ampersand, to not group.
    • Also Pika does not look at various subfields in the 245.  This means that it is grouping things that are in fact different, where the difference is only spelled out in those subfields.
    • Tickets were opened in YouTrack for these issues.
• Server upgrade
  • Thursday night
    • Sierra will move to the new server on Thursday night at 9:00.  This will be a live migration.  We do not expect any down time or interference with functioning.

Discussion Topics

• Revisit 938 and 902 fields in bib records
  • Last month we talked about deleting these fields.  We waited an extra month to see if anyone would raise any objections.  None were raised.  These fields will be deleted.
  • *Action Item: Lloyd will delete both of these fields, and prevent 938s from loading in the future.
• Look at new MARC 34x fields
  • We look at examples of 34x fields in our database and what Marcive would send us.  People are not enthusiastic about adding more URIs to our data when they don’t actually serve any function at this point.  Amy suggests that Lloyd ask Marcive if they can add 34x fields without |0.  If we do that can we get the |0 at some point in the future when they actually do something?  We could use a loader that leaves out the |0.
  • *Action Item: Lloyd ask Marcive about 34x fields without subfield zeros.
• Jamie mentions that he has a problem with exporting the subfield zeros we already have in subject headings.  They make a mess of his report and he has to go to a lot of trouble to remove them.  We could probably create an exporter that would exclude the subfield zero.
  • *Action Item: Lloyd will look into creating an exporter that excludes |0.
• Sample records with limited ISBD punctuation
  • Library of Congress is experimenting with creating MARC records with less ISBD punctuation.  These would allow systems to be more flexible with the way data is displayed.  The records would also be easier to create.
  • Information about the project is here: https://www.loc.gov/aba/pcc/documents/test-records-punctuation.html
  • Sample records from LC are in list 326 in Sierra.
  • We look at some of the sample records in Sierra, Classic, and Pika.
  • Pika is already adding some punctuation that is not in the records in some displays.
• Marmot duplicate checking utility
  • At the duplicates committee meeting we discussed the idea that we could build our own duplicate checking utility, perhaps with Tableau.  Brandon put together a demonstration of what Tableau could do for us.  It produces a list of all the duplicate 001 fields with the b numbers and titles.
  • It could add comparison of the 019 and 035 to the 001.  We could have versions that compare other fields such as 020, 022, 024, 028, and 010.
  • The demo can be viewed here: https://dev.marmot.org/content/marmot-001-duplicates
  • When you click the download icon at the bottom, and choose Crosstab, you can get a copy in Excel format that would be easier to work with.
  • The demo does not update.  The production version could update daily or hourly if we want.
    • Shelley would like it to update hourly.
    • Brandon says the refresh process would take about 10 minutes.
  • We want it to be able to limit by locations, so people can see those duplicate groups they have copies in.
  • We want it to be able to limit by record date.
  • We want to compare 001 and 019.
  • Jamie would like to be able to limit to local locations so he could focus on ebooks or some other collection.
    • Brandon says that getting data from item records would slow things down.  He would like to try to do this only with data from bib records.  However, bibs do have the locations field, which is created by link maintenance, and includes some granular location data.
    • Different users would like to see different levels of that granularity.
  • We would like to be able to filter the results by the number of duplicates in each group.  That can be done when the data is exported to Excel now.
  • We would like to see more of the title in the Tableau display.

Completed action items

Ongoing action items