Meeting Minutes for 05/27/2020

Marmot Union Cataloging Committee
Wednesday, May 27, 2020
Minutes

Announcements

• RDA Beta course availability
  • We have the option of doing this course for $1600 no matter how many of us participate.
  • The class looks fairly intense.
  • If anyone else is interested, contact Lloyd or Brandon.
• Lloyd will convene the FOLIO consortia SIG to work on metadata issues
  • Western State has announced that they plan to implement FOLIO next year.
  • We are moving toward a structure that would allow individual members to choose to switch to FOLIO rather than Sierra.
  • The FOLIO Consortia SIG had an opening for a convener for the rest of the year, so Lloyd is volunteering to do this.  He will see if the SIG can start looking at metadata questions.
  • FOLIO meetings are open to anyone who wants to show up.
  • Oliver attended a meeting about Texas A&M.  He reports that they have a very long implementation process of about 2.5 years between the decision to final implementation.  He thinks they recorded the meeting and he would send out the link when he gets it.
  • There is also an implementers SIG that would be worth paying attention to for any library planning to implement.
• Duplicates Team Report
  • Rejected Lloyd’s idea to add a note into records that would identify the person who loaded the record.
  • Idea to check Marcive loads for records sent multiple times to evaluate cost.  We realized this would not be worth implementing because we don’t actually do it that often.  It looks like this only costs a few hundred dollars a year.  However, that could be an undercount due to deduping.
  • Lloyd will make a better effort to track this information before deduping, so we can find out how much this is costing us. << Action Item
• Pika Cataloging Collective Report
  • Problems with grouping by movie running time.  We learned at this meeting how the running time grace period would actually work.  There is no way to actually compare the times of two different records.  All it would do is round each of them to the nearest 10 minutes.  If those rounded numbers are equal, then it would count as the same.  The problem is that 4 minutes rounds to zero and 5 minutes rounds to ten.  So a pair could be one minute apart and this system would see them as not equal.
  • Lloyd checked the 100 pairs of videos with the same title and found that the failure rate was only 8% less effective that it would be if it was able to actually compare two times.  
    • Jamie asks if it would be possible to create a secondary grouping test for motion pictures that would allow for a more accurate running time grace period.  Lloyd will take that question to Pascal.  <<Action item  
    • Lloyd points out that since we know what scenario will lead to this grouping error, we could run lists to find those that will need to be fixed manually.
    • The group agrees that the current running time plan with rounding is enough of an improvement in the next Pika version.
• FAST subject headings
  • This topic has been discussed in the Pika Cataloging Collective.  Lloyd realized that Pika makes heavy use of subject faceting, but it currently pulls LCSH apart in a weird way in order to create the facets it now uses.
  • FAST headings are a version of LCSH that was created to make subject faceting easier.  We could make use of FAST headings for subject faceting in Pika.
  • Marcive could give us FAST headings in our records for no additional charge.
  • Mary says she would like to see how they work.
  • They are using them at Cornell.  We look at the Cornell catalog.
  • Jamie asks if Cornell is using VuFind.  No, they use Blacklight for their catalog.
  • Jamie suggests we ask on a VuFind email list to find if anyone is using FAST headings in VuFind to find examples. << Action Item

Completed action items

Discussion Topics

• Action note idea.  Voluntary note describing action taken on record in Sierra
  • Lisa had an idea for a note about when she changed a record in Sierra.  We could define a pattern that people could follow.
  • What would be the goal?  You can keep track of internal changes to records in Sierra.
  • This would be optional.
  • Tyler, Robin, Nicole are in favor.
  • We would want to record the library, action taken, name of person?
  • How would this work in the 949?
    • This would be in the bib record.  If you are loading from OCLC, you can just add the information into the master record in OCLC then load into Sierra.  Then there is no need to note the change in Sierra.
  • Lisa would not add this for a load, only for bibs already in Sierra?
  • Should it be protected?  No.
  • Could be used for local author note.
  • Lloyd will write a specific proposal to add to the Cataloging Standards. << Action Item
• Nicole asks if the Pika cataloging meeting could be combined with UCC so people don’t have to attend two cataloging meetings.
  • Lloyd will think about it and bring it up with Ashley.
  • [The Pika cataloging meeting has since stopped meeting in person, so this is moot]
• Working on language code problem records
  • Lloyd has developed a process to reload batches of records from OCLC.
  • This can be used to overlay any group of problem records from OCLC.
  • Lloyd will schedule training on using this process and make the recording available. << Action Item

New Action Items

Ongoing Action Items

Next Duplicates Sub-committee meeting: June 10

Next UCC meeting: June 24