Versions Compared

Old Version 2

changes.mady.by.user Charlotte Whitt

Saved on

compared with

New Version 3

changes.mady.by.user Jennifer Eustis

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Announcements



Inventory exports/harvests

Magda Zacharska 

  • Collect use cases for exporting/harvesting instance data direcly from Inventory with more than just abbreviated MARC (e.g. "indexing in discovery / opac"). Please add your use cases in advance to this wiki page: Export Use Cases (following item #16 in the list)
  • Review the existing mappings for data export/harvesting, and see what additional data should be included






No PC meeting, but a Tri-Council meeting

Charlotte Whitt 

FOLIO Tri-Council meeting on January 18th at 10:00am Eastern Time. The agenda:

  1. How many releases per year do we want for FOLIO?
  2. What do we want to get out of WOLFcon 2024?
  3. How do we make the FOLIO Project attractive to new member organizations?
Data Import Working Group

Jennifer Eustis 

At the 2024-1-17 Data Import Subgroup meeting, the working group discussed updates for Quesnelia, UXPROD-2742, and continued the discussion on MODATAIMP-879.

For Quesnelia, the focus continues to be reliability and stability improvements in addition to reducing the number of bugs. There are bug fixes for Poppy that will be part of a future CSP for Poppy. The group would like a better understanding of what is a bug, when any bug is changed to a feature or closed, and how bugs are evaluated.

For UXPROD-2742, this issue concerns how to handle an incoming marc to an existing marc srs field where the existing marc srs's field that is being match to is a repeatable field as in the case with the 035. We talked about use cases and common scenarios.

For MODDATAIMP-879, we continued the discussion on how to handle removing duplicate 856s in SRS.

For lab, we'll be brainstorming documenting bugs and other issues.

Chat