Meeting Minutes for 05/25/2022

Marmot Union Cataloging Committee
Wednesday, May 25, 2022
Minutes
 

Announcements

  • ORC
  • New Sierra Idea Lab challenge
    • There is a new Idea Lab challenge focusing on global update functions.
    • Lloyd has submitted two ideas for improving global update. Everyone can participate to vote on ideas and submit ideas. Here is Marmot's guide on using Idea Lab:
    • https://marmot-support.atlassian.net/l/c/aydCnhkB
  • WolfCon 2022
  • Acquisitions documentation project update
    • Lloyd met with Nina to learn about the acquisitions process at Bud Werner. He will work up a page in the Marmot Knowledge Base so others might get ideas for how to make use of the acquisitions module.
    • Lloyd would like to have meetings with other libraries using acquisitions so he can develop more pages for the Knowledge Base.
  • Marmot cataloging services ideas
    • Previously we discussed some options for cataloging services from Marmot.
    • Lloyd discussed these with Brandon. He said that a proposal for Marmot to provide a new cataloging service would have to come from the director level. He suggested that people talk to their directors and ask them to bring it up.
  • Sierra rescoping project ongoing
    • Lloyd did a rescoping project for CMU. This required making a small change to every item record which forces Sierra to put the item in the correct scope.
    • This worked well for CMU, so he is starting to do this for the whole system.
    • He is using Global Update to change the OPACMSG fixed field and change it back on 50,000 item records a day.
  • Create List Saved Searches Project will actually start next month
  • Cataloging training is now all on-demand
    • Marmot cataloging training will now all be on-demand rather than scheduled. On-demand trainings can be scheduled more flexibly and can be tailored to cover the individual library situation.

Discussion Topics

  • OCLC reconciliation status
    • Lloyd only has files from Aims and Montrose so far.
    • Jamie says he will give his files to Lloyd at Council. 
  • Idea for new Marmot project management system
    • Marmot is implementing a new project management system.
    • The system is based on the system used in Software Development where people work on a 3-week schedule.
    • 3 week sprints
      • Week 1 innovation week: project planning, documentation, professional development
      • Week 2&3 sprint week: focus on projects
      • Weeks start on Wednesdays
    • Another option would be to operation on calendar months
      • Last week: innovation week
      • Remainder of month: focus on projects
    • Lloyd wants input on how the UCC would like to fit into this new system. If Lloyd is working on a 3-week schedule, it might make sense for the UCC to meet every 3 weeks during the planning week. That way UCC could participate in Lloyd's project planning.
    • People all prefer to keep operating as we have been rather than changing the schedule or function of the UCC meeting.

FOLIO Updates

  • General Dirt
    • Chicago is still very unhappy with Data Import, they might build their own data import app
    • PALCI has a new library joining and they will migrate directly onto FOLIO. Hosting by Index Data. OCLC for resource sharing.
    • ByWater is actually hosted by EBSCO, not self-hosting
    • Reference data is what they call all system customization: loan rules, patron types, material types, permissions, etc. All of these get overwritten when you upgrade and have to be recreated.
  • App Interaction
    • Discussion of controlled digital lending
    • Could FOLIO facilitate CDL?
    • If you have one physical object sequestered, you can lend one electronic copy, and vice versa. Can FOLIO manage that?
  • QuickMARC
    • Developing browse contributor function
    • Demo of mockups for linking MARC authorities to MARC bibs.
    • Can export MFHD in Lotus
  • Metadata Management
    • It may be possible to delete instances in Orchid
    • Record loading is getting faster
      • Can update 50,000 records in 1.5 hours. It used to be 11 hours. Sierra is 5 minutes.
    • In Lotus you can match on any MARC field, and use indicators and subfields
    • If it is a repeatable field, only the first incoming value is compared, all target fields are compared
    • Morning Glory will be able to match on POL or Vendor number
  • Bulk Edit
    • There will be two bulk edit methods, in-app, and export/import
      • Export/import will be more powerful and flexible
      • In-app will be in the app
      • Each record type will be available for export/import first, then in-app later
    • Can't now do a bulk edit based on characteristics of linked records
  • Acquisitions
    • Discussion of fiscal year rollover
  • INN-Reach
    • Anyone not hosted on EBSCO will be required to do extra sandbox verification
    • Grand Valley State will start implementation in early July. This testing must go for 6 months before anyone else can install.

Question in Chat: Does Marmot have a tentative timeline for FOLIO implementation.

  • At this point our next step is to implement a test server. We are hoping to have this done in the summer (but I would not be surprised if it stretches into Fall). That will be on Amazon Web Service not local hardware. We are working on setting that up.
  • A critical thing we are waiting for is INN-Reach implementation. Nobody wants to go if they would have to lose Prospector. Early next year is the soonest that could happen.
  • Nobody in Marmot has set a date for when they want to implement it.

Question: What has been presented so far makes me feel wary.

  • Many people in the FOLIO meetings seem to feel the same way.
  • Jamie: We are not in any rush. We can take our time.
  • Once we have a test server setup we can really test how this would actually work. It is hard to draw any firm conclusions without that.
  • We will need a member to decide they want to implement. Nobody is currently committed to implementing it.

Question: When will we upgrade Sierra to a more recent version. 

  • We are waiting for the next version again because the current version still has not fixed an important INN-Reach bug.
  • The bug is that users on Pika would be able to renew Prospector items an unlimited number of times. There would be no way to stop people from just renewing over and over. 
  • This was supposed to be fixed in 5.4, but it was not so we are waiting for 5.5.
  • 5.5 is supposed to be out in August, so hopefully we will be able to implement it then.
  • There are a bunch of new features in 5.4 that we would like to use.

Ongoing Action Items

Action

Responsible parties

Investigate a load profile that would protect local cover art 856 fields, both Pika and Midwest

Lloyd

Investigate a load profile to set the 856 field group tag to LOCAL INFO, both Pika and Midwest

Lloyd

Discuss subfield |5 for 690 genre headings in Cataloging Standards document

Lloyd

Update Cataloging Standards document to explain the problem with call number prefixes in subfield d for the old printing system and subfield f for print templates.

Lloyd

Investigate Tableau tool for finding bad dedupes

Lloyd/Brandon

Create a new itype for a dummy item that will only allow local holds for the library that creates the record, and change load profile (J) to use the new dummy item.

Brandon/Lloyd

Fix load profile (J) to use new dummy item.

Lloyd

Fix the documentation for load profile (J)

Lloyd/Tammy

Create a flowchart to describe when to use which order record loader.

Lloyd/Tammy

Investigate using |0 field to indicate record needs to go to Marcive

Lloyd

Document ways to find music with no language in list 21 language problem list.

Lloyd

Develop cataloging training materials

Tammy/Lloyd

Develop flow chart for how to use the volume field

Lloyd

Investigate a new Tableau utility for finding bad volume field use

Lloyd/Brandon

Develop documentation for Marquis macro

Lloyd/Tammy

 
 
Meeting Date: 
Wednesday, 2022, May 25
Documentation Type: 
Meeting Minutes
Committees: 
Union Catalog Committee