2024-08-08 Metadata Management Meeting notes

a Meeting time: 11:30 AM EDT, 05:30 PM CEST, 04:30 PM BST

Meeting URL: https://zoom.us/j/527543204 . The meeting password can be found here.

 Date

Aug 8, 2024

Note taker

Laura Daniels, Lynne Fors, Alissa Hafele, Natascha Owens

Recordings

Recordings of meetings can be found in the Metadata_Management_SIG > Recordings folder on AWS from 2022 onwards: https://recordings.openlibraryfoundation.org/folio/metadata-management-sig/

Discussion items

Item

Presenter

Notes

Item

Presenter

Notes

Announcements



Should we spend some time in the next meeting to brainstorm topics for our working meeting at Wolfcon? https://wolfcon2024.sched.com/event/1eeqO/metadata-management-sig-working-meeting

Felix will add to the agenda

Christie: OCLC, various institutions having conversations re: Integrating FOLIO with OCLC – closer integrations for additional functionality - conversations are happening and we should think about what we would like for these types integrations. How much interest is there across the MM SIG for participation in these conversations?

Jennifer: It is an important topic for the SIG and we should talk about it as a group. Then bring what we want up to OCLC when they come to a meeting. We already have a lot of subgroups so discussing this at the SIG level would be best.

Christie: I don’t want to add more work! But want to be cognizant that not everyone here is a user of OCLC.

UAT results

@Christine Schultz-Richert & @Ryan Taylor

  • Results of UAT: Pub place index, related titles navigation, updates to 035 normalization, and bulk edit of FOLIO instance notes (see slide deck HERE)

    • Data Import - 035 OCLC Normalization: added removal of “on” prefix, spaces or periods between prefix and number--no major problems reported

    • Inventory - Related titles navigation for MARC source Instances (pre

  • Results of Q call number browse UAT:

Data import sorts protected fields out of order after update

@Ryan Taylor

https://folio-org.atlassian.net/browse/MODDICORE-358 will be discussed during the DI WG on Wednesday, August 7th and Ryan will provide updates to the MM SIG today.

Bulk Update UAT results

Jennifer Eustis

Question

Vivian Gould

 

PC updates

@Charlotte Whitt

2024-08-08 Product Council Agenda & Meeting Notes

Announcements: Lucy (Galileo) will be the new co-convener of the Consortia SIG. The Consortia SIG will send out today the Consortial Interest Survey 2024, with a questionary and a section to weigh in on goals for 2024/2025. The purpose with the survey is to get a better insight in what is the expectations.

Developer Advocate Update: Submitting requests to the Developer Advocate site is up and running (insert link). Developer meeting with Kevin Day. Working on Developer documentation - strategy and set frame work. Established a Developer Documentation Group. Subgroup under the TC. Documentation to be published in Confluence. The more general technical documentation is missing. Up to now the focus has been documentation on module level.

Ideas for tracking, and maintaining the FOLIO Roadmap: Transition from the Roadmap working group to track and follow the development of FOLIO. Lots of ideas; e.g. Calendar, and misc. Jira Dashboards. Yearly review could be a way to evaluate that the planned development, was achieved. Another idea is to have the goals qualitative annotade.

BELA (Bulk Edit and Lists App)

Jennifer Eustis

2024-08-06 BELA Meeting Notes

We reviewed upcoming features for Ramsons and followed up on the work on editing MARC instances.

We also covered the UAT feedback. The results can be found in this Google drive: .

Data Import Working Group

Jennifer Eustis

2024-8-7 Data Import Subgroup meeting

The working group worked on 2 Jira issues.

https://folio-org.atlassian.net/browse/MODDICORE-358

The proposal agreed on is that the protected field of the existing record should be placed either ahead or behind the same field number in the incoming record. Ryan is bringing this proposal to the development team.

https://folio-org.atlassian.net/browse/MODDATAIMP-879

The proposal agreed on is If an existing and incoming record has duplicate fields for any repeatable fields, the system should dedupe. If an existing and incoming record don't have duplicate fields for any repeatable fields, then the system should not dedupe. Ryan will bring this to the team.

quickMARC Subgroup update

Raegan Wiechert

No meeting this week

Chat