Skip to end of banner
Go to start of banner

2024-08-08 Metadata Management Meeting notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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.

\uD83D\uDDD3 Date

✍️ 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

Announcements


UAT results

Christine Schultz-Richert

  • Results of UAT: Pub place index, related titles navigation, updates to 035 normalization, and bulk edit of FOLIO instance notes

  • 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.

PC updates

Charlotte Whitt

2024-08-08 Product Council Agenda & Meeting Notes

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.

MODDICORE-358 - Getting issue details... STATUS

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.

MODDATAIMP-879 - Getting issue details... STATUS

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

🧑‍💻 Chat

  • No labels