...
Note taker: Laura Daniels, Lynne Fors, Alissa Hafele, Natascha Owens
...
| Announcements | |
|
| Inventory exports/harvests | | - 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
Magda hopes to get answers to the following questions: - Do we need to be able to export inventory records in MARC format that is not abbreviated MARC currently supported?
- Do custom mapping profiles meet such need? If not, what functionality is missing? What is the urgency (priority)?
- 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?
|
|
|
|
|
|
|
| No PC meeting, but a Tri-Council meeting | | FOLIO Tri-Council meeting on January 18th at 10:00am Eastern Time. The agenda: - How many releases per year do we want for FOLIO?
- significant consensus that 2 releases per year is best target for FOLIO
- 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)
- What do we want to get out of WOLFcon 2024?
- Have more hands on/work shop sessions (maybe as pre FOLIO conference day)
- Covernance meetings - in the councils (after the regular FOLIO conference). Worked well in Chicago
- Plan for sessions which will engage both SMEs and developers
- Opportunity for lunch time and evening sessions
- Improve the conversation across roles as PO, Conveners, SMEs, Devs, and SysOps
- Jennifer Eustis and Paul Moeller volunteered to be in the planning committee
- How do we make the FOLIO Project attractive to new member organizations?
- Reach out to potential FOLIO libraries, who then decided not to go with FOLIO
- Outline how the members contributions improve the FOLIO product
- EBSCO has many hosting customers, but not many of them are FOLIO members
|
| 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 |
|---|
| server | System Jira |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UXPROD-2742 |
|---|
|
For MODDATAIMP-879, we continued the discussion on how to handle removing duplicate 856s in SRS. | Jira Legacy |
|---|
| server | System Jira |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODDATAIMP-879 |
|---|
|
For lab, we'll be brainstorming documenting bugs and other issues. |
Chat