2025-02-27 Metadata Management Meeting notes

Announcements

Call for new volunteers for note taking rotation. Need 2 more!

• Contribute to the community in an easy way! With the rotating schedule, you only take notes about once a month. Sometimes less if meetings are canceled! It's pretty easy to get coverage if you have a conflict on your designated meeting day with your cohort of notetakers.

Monthly implementers topics session

https://folio-org.atlassian.net/wiki/x/UQCxKg

• https://folio-org.atlassian.net/browse/UXPROD-5135

• Please reach out on Slack (in MM or Linked Data Channel or directly to Laura or Kalli) if you have questions, comments, or concerns about this

• Laura & Kalli will be updating the Jira to incorporate some of the suggestions and questions from today’s disucssion

• This feature was Initially discussed in Linked Open Data Sig; asking for an additional field that is part of the Instance Administrative Data where we could record Instance Source URI that would be linked to a source record outside of FOLIO, for example if you are working in Sinopia and you are mapping an Instance from Sinopia into FOLIO—but you could use this anytime you have a source of truth that is external to FOLIO.  This would be a single value hyperlink (not repeatable).  Essentially this is to help a current workflow at Stanford where they are testing and need a good place for a live link in place that makes sense. 

  Felix: At GBV we don't have a URI to reference the source instance record because our cataloging client is old-school, but if we would have the ability then we would probably use this field. We have URI's to reference the record via interfaces like SRU, but from there we are not able to edit them.

• Discussion about adding another source code is a separate topic

• Jennifer: Are you thinking that this field could also be in the queue of being updated by bulk edit/data import?  Maybe something to consider.

  Laura: I would prefer it not be editable initially because it is linking to the source data

  Jennifer: What about importing records with that field to populate it?

  Kalli: Most of the management will be happening outside of FOLIO so gut instinct would be no

• Christie: Instance source has been implemented in a way that can only be editable by business logic.  We always had intentions of being able to change the source of metadata but that has not happened yet.  I see so much need in the future as our workflows evolve to be more flexible.

  Nancy: Agrees with Christie in principle but does not want this project held up because we make it ten times larger, there are institutions need this implemented in order to continue with current/ongoing projects

  Christie: I completely agree, Nancy. I was speaking more about instance source and its use than the URI proposal.

  Jennifer: You may also want to think about the behavior if the instance is deleted when it has this link in it

• Next steps: Linked Open Data Sig will reach out to POs (Ryan/Khalilah/Christine) for their input

Product Council updates

Charlotte Whitt

2025-02-27 Product Council Agenda and Meeting Notes

Announcements: Call for proposals for WOLFcon will go out next week.

Eureka early adopters updates: VZG + K-Int have now got the basic components in place. Next step is establishing Security. Also setting up Permissions roles will be a challenges. The definition of what Sunflower is, needs to be defined - Collections, and version of applications. Oleksii explained there will still be a application descriptor. Each library will in future be able to select their use of application.

Changes of permissions to roles: Implementers SIG had a great session at Tuesday’s meeting. Here the link to the recording. Also the UM SIG has started up hands-on sessions, which were very useful. Maura Byrne plan to gather all relevant recordings at one place. Oleksii Petrenko has experimented with writing user documentation using ChatGPT: Demo website - FOLIO | Microsoft Copilot Studio.

Release cycles when we move to Eureka - Trillium will be 14 sprints. Feature freeze 9/19/2025. Bugfest begins 10/24.GA 11/11/2025.

How will the future cadence of releases be: Spring (April), and Autumn (October / November). Oleksii Petrenko explained that the planning will reflect what functionality is planned to have included.

With Eureka the platform will be more granular, and will in the future do more and smaller releases on demand. Kristin Martin asked how will the testing be organized. A constant low level testing - an ongoing Bugfest test?

Update on the PC’s work on the PC Ranked Goals. Has made progress on 1) Update the PC Review process; and 2) Engage with the App Formalization (the move to Eureka). 4) Solicit & analyse community priorities. This work is being lifted by the prioritization of features is now happening in the SIGs. 3) Revive Community Development - all agrees is highly relevant. Might be something to talk about at DC in two weeks or WOLFcon.

BELA (Bulk Edit and Lists App)

Jennifer Eustis

No meeting this week.

Data Import Working Group

Jennifer Eustis

https://folio-org.atlassian.net/wiki/spaces/MM/pages/744849409

A new UAT will be coming out soon to test the phase 2 implementation of set for deletion. We are beginning to look at how to overhaul the logs.