Versions Compared

Key

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

Date

~~35

Note taker: Laura Daniels, Lynne Fors, Alissa Hafele, Natascha Owens

...

Discussion items

Announcements


No announcements

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

Inventory exports/harvests
  • Collect use cases for exporting/harvesting instance data direcly 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.


No PC meeting, but a Tri-Council meeting

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 Significant consensus that 2 releases per year is best target for FOLIO
    2. interested 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/work shop workshop sessions (maybe as pre FOLIO conference day)
    2. Covernance 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
BELA (Bulk Edit and Lists App)


No meeting this week.

Data Import Working Group

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.

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2742

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

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODDATAIMP-879

For lab, we'll be brainstorming documenting bugs and other issues. For Zoom meeting info, see #data-import-lab-sessions in Slack.

Chat