Skip to end of banner
Go to start of banner

2024-05-23 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 9 Current »

Meeting time: 11:30 AM ET, 05:30 PM CET, 04:30 PM GMT

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


PO Update Quesnelia: Data Export and Bulk Edit

Magda Zacharska

Bulk Edit

  • display entire record set

    • was 10 records in Poppy

  • holdings - electronic access

    • up to 10k records at 1 time

    • only folio, not marc holdings

    • all fields

    • clear, find/replace, find/remove, removal all

      • find is full field (restrictive as possible)

  • holdings - folio notes

    • only folio, not marc holdings

    • utf8 suport

    • up to 10k records at 1 time

    • multiple of same type | separated

  • instance - discovery and staff suppress

    • suppressed and unsupressed

    • change can be applied to underlying holdings and items

    • up to 100k records at 1 time

  • query tool can now be used

  • improve column display

*note files used in bulk edit are kept accessible via logs for 30 days

Data Export

  • Performance improvements through architecture changes (ahead of LOC implementation) - e.g. all bugfest ~8mill. instances in 4 hours)

    • endpoint changes (details in release notes)

    • new endpoint

      • params = record type, profile, deleted y/n, suppressed y/n

      • separate permission needed Data export: Export all

      • triggered via API but can be monitored/access files via UI

    • slicing of large exports (configurable). Multiple files stored in S3, compressed and available for download w/ 1 click

    • no significant UI changes

Questions

PC updates

Charlotte Whitt

2024-05-23 Product Council Agenda and Meeting Notes

PC discussed the Story of FOLIO. The origin of the document was: How do we introduce ourself to new members, interact with new members, engage them in FOLIO activities, and the councils work. The document is written by Mike Gorrell, Christina Spalding, Boaz, and Edwin Pretz. The goal to write up: This is how FOLIO works today. This is the things we are dealing with today. Funding is one of the critical aspects of the FOLIO work (development and maintenance). There is a paragraph about how FOLIO interact with the Open Library Foundation. A shift has happened in how new functionality are being prioritized. This is now customer driven, and dependent on funding. Status: the document has been updated based on the Community’s comments. The idea is that this document is to be updated maybe in 12 months , so we always have an updated version of the current state of FOLIO. This document will be presented at the OLF meeting in June 2024.

PC also started the discussion on the survey “Things that could be better with FOLIO”. PC will look into organizing the responses into sections and will continue this discussion next week.

BELA (Bulk Edit and Lists App)

Jennifer Eustis

No meeting this week. There are new wiki pages to add topics for the working group to discuss.

Bulk Edit: Bulk Edit Resource Management Implementation Topics

List App: List App Resource Management Implementation Topics

Data Import Working Group

Jennifer Eustis

2024-5-22 Data Import Subgroup meeting

The working group brought up an issue with Poppy - a marc srs bib record that has more than one version where the state is Actual. This is happening with large and small imports. To find these errors, Chicago used their LDP. This is now recorded in MODDATAIMP-1058 - Getting issue details... STATUS . If you are able, it is recommended to find any srs marc bib which has more than one version set to Actual.

The working group then moved on to the discussion on set to delete. Two issues were considered:

  • A delete flag is needed at the instance level in addition to a banner that says the instance is marked for deletion.

  • What are our expectations when doing an update when a match to a deleted record is made? Should the record be updated? Should DI not be aware of deleted records?

quickMARC Subgroup update

Raegan Wiechert

quickMARC meetings will be cancelled for the month of May.

🧑‍💻 Chat

  • No labels