2024-01-18 Metadata Management Meeting notes

No announcements

R2 2023 Poppy Critical Service Patch #1 - https://folio-org.atlassian.net/secure/Dashboard.jspa?selectPageId=12920

• Collect use cases for exporting/harvesting instance data directly 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

Magda hopes to get answers to the following questions (from Slack):

• Do we need to be able to export inventory records in MARC format that is not abbreviated MARC currently supported? 
  • Lloyd (Marmot): The use case I can think of is migrating to another system. In that case, you might need all your data in MARC format, depending on how the other system imports data.
• Do custom mapping profiles meet such need? If not, what functionality is missing? What is the urgency (priority)?
  • Jennifer Eustis (5C): Holdings records and syncing with OCLC LHRs. Also, goes hand-in-hand when searching for holdings, results returned are Instance records.
    • Charlotte: Can search on holdings record data using the API and get only holdings records
• How the abbreviated MARC record affects discovery in your organization? Could you provide examples of when you would prefer more data included?
• Is there a need to export only a subset of the fields from SRS record instead of the entire record? If yes, what would be a use case for it?
  • Alyssa: Stanford has this need, want to exclude purchasing data.
  • Jenn Colt (Cornell): our use case for that last question is excluding local data in case someone didn’t say that yet
  • Reagan (Missouri State): export partial bib record to analyze genre/subject headings; see Export Use Case #17

• Question: Are there plans to extend the export formats beyond MARC? I don't have an urgent use case, but it might be worth looking at this topic.
  • Answer: Yes, there are plans. Bibframe is next. Other formats are not yet scheduled.
• Question: Can we deleted and edit export profiles/mapping profiles in Poppy?
  • Answer: Pain point for many libraries. Not yet. Feature in backlog for locking profiles to prevent deletion, no expected release for this functionality.

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?
   1. Significant consensus that 2 releases per year is best target for FOLIO
   2. Interested in how the work on App and Platform Formalization work in future will affect the releases if we can decouple FOLIO from the monolithic releases and provide more flexibility (maybe move more towards feature based releases)
2. What do we want to get out of WOLFcon 2024?
   1. Have more hands on/workshop sessions (maybe as pre FOLIO conference day)
   2. Governance meetings - in the councils (after the regular FOLIO conference). Worked well in Chicago
   3. Plan for sessions which will engage both SMEs and developers
   4. Opportunity for lunch time and evening sessions 
   5. Improve the conversation across roles as PO, Conveners, SMEs, Devs, and SysOps
   6. Jennifer Eustis and Paul Moeller volunteered to be in the planning committee
3. How do we make the FOLIO Project attractive to new member organizations?
   1. Reach out to potential FOLIO libraries, who then decided not to go with FOLIO
   2. Outline how the members contributions improve the FOLIO product
   3. EBSCO has many hosting customers, but not many of them are FOLIO members

No meeting this week.