Meeting Minutes for 02/22/2023

Marmot Union Cataloging Committee
Wednesday, Feb 22, 2023
Minutes

Announcements

• MLN2 catalogers are officially members of UCC
• IUG
  • May 10 - 13
  • Phoenix
  • In person only
• Rampart is leaving Marmot
• Marmot is hiring a new ILS administrator
• Finished loading all updated records from Marcive update in December.

Completed action items

Discussion Topics

• Unscoped logins for everyone.
  • After the last meeting's discussion of holds on orphaned order records, I realized everyone needs an unscoped login so they can fix these.
  • Lloyd will figure out who does not have an unscoped login and work with them to get them one and get them trained to use it.
  • Rampart
  • Grand
  • Lake?
  • Summit?
• Ingram sends weird characters in order records, causes one-click to fail
  • When these files fail to load correctly it is very hard to know what is missing. Some orders simply don't show up. You have to check the record count every time. There is no indication of failure. When some records don't show up, it is very difficult to find out which are missing because Ingram and Sierra sort them differently.
  • There is no solution from Sierra or Ingram
• Rescoping by III
  • III did a rescoping project on MLN1.
  • In the past, rescoping by III has created many out of scope errors.
  • We don't know if that has happened again, but it may.
  • Watch for out of scope items. If we find many of these, we can get III to redo the rescoping project.
• MLN2 link maintenance
  • Is MLN2 doing link maintenance?
  • Is there a reason for not doing it?
• Notes deleted by large Marcive update
  • An error in the field protection of the Marcive load profile caused some local notes to be deleted in Sierra. These would have been locally created notes in 500 to 589 that were entered into records after they were sent to Marcive.
  • Jamie asks for a list of the dates of records that would have been affected by this problem.
    • The problem would be limited to records entered before 2004.
• Cataloging training
  • What do people want to do with cataloging training?
  • In the past we did a monthly cataloging training, but few people signed up.
  • We have been trying on-demand training and nobody asked for it.
  • Then a couple months ago Western asked for cataloging training. I scheduled it and opened it up for everyone, and a whole lot of people signed up. So it seems there is demand for cataloging training, but I don't know how to schedule it so people can/will participate.
  • People suggest it might work to do quarterly training instead of monthly.
  • Chat suggests a monthly poll of which training more people are interested in.
  • Tammy says the announcements in UCC drive attendance at cataloging trainings.
  • Upcoming trainings could be in the newsletter.
  • Kristen says she finds smaller groups in training to be more useful.
    • We could offer on-demand trainings for single sites in addition to regular quarterly training.
• MLN2 Authority
  • Lloyd is still working out the authority update for MLN2
  • There was a full backfile on MLN2 in February 22 and an update file sent in July 22.
  • We will send them a file of new records created since July and records deleted since February.
  • MLN2 will use the same process as MLN1.
    • A "no a.c." note in a 958 field will keep the record out of authority.
    • Also, not having a CAT DATE will prevent a record from going to authority.
    • If you update a record and want it to go back to Marcive, then you can update the CAT DATE and it will go out again.
  • MLN2 will soon get a comprehensive update from Marcive. This is expected to replace most of the records on MLN2 with updated headings.
• Montrose is having a problem with item records for ILL not getting the correct item location. They are just getting the two character location code mr.
  • This is probably set in a template.
  • They are using on-the-fly records. Check what template is used by that user for on-the-fly. This is in settings in the "On-the-fly" tab.
  • We look at how Garfield is creating ILL records. They are putting all the ILL items on a single bib for each branch.
  • We notice there is an ICODE2 of ILLFLY, but it does not suppress the records. Only Fort Lewis is using it. Lloyd will contact Fort Lewis and see if they think it should be suppressed.
  • Montrose is interested in using the ILLFLY code so that it would be suppressed in Pika, but not Classic. Their staff could use Classic, but the public would use Pika.
• FOLIO Updates
  • Australian National Library is joining FOLIO and providing development teams
  • Creating multiple holdings and items with MARC record load scheduled for Poppy (R2 2023)

Ongoing Action Items

Next Special Projects Sub-committee meeting: March 8

Next UCC meeting: March 22