2025-05-08 Metadata Management Meeting notes

Announcements

Results of the Data Import Prioritization Poll (see Slack message). Going forward, Data Import will rely on votes on Jira Issues. We encourage you all to vote for your issues. You can see the numbers of votes on issues per release in the Data Import Dashboard.

If you have questions about this, you can ask questions in the Data Import channel in Slack.

Open

MM SIG prioritization poll with the topics from our MM tracker page. Please rank your priorities until May 19th!

• https://PollEv.com/ranking_polls/UdTUvp6TrTPShthnUp4Ic/respond

• 5 responses as of 7 May 2025

Raegan reminded members that anyone can vote including multiple members from the same institution. You can also vote on these items in JIRA.

Starting next week, Felix will be the main convenor for the summer, so make sure to send agenda items to both Felix and Raegan.`

Metadata Management Implementers Topics

All

Felix led the discussion.

#12: Make 336 (instance resource type) repeatable on Instance records UXPROD-3973: DRAFT. Inventory. Instance. Resource type to be a repeatable data property.Draft

Felix created two tickets: Backend: MODINVSTOR-1412: DRAFT: Make instanceTypeId repeatable and change its data type from String to ArrayDraft and Frontend: UIIN-3370: DRAFT: Make instanceTypeId repeatableDraft

For the frontend ticket, Felix created some scenarios for discussion. He mentioned that it would be similar to how the UI handles format, so the change should be pretty straightforward. You can vote on this ticket, but Felix recommended voting on the feature instead UXPROD-3973: DRAFT. Inventory. Instance. Resource type to be a repeatable data property.Draft He also recommended reviewing and correcting the current use cases for UXPROD-3973 and adding new ones.

Felix reviewed the resource type filter in Inventory and discussed the possibility of an “AND” Boolean option. Jennifer asked if they will need to run a reindexing script to pick up a second or third 336 for records that are already there. Ryan set it should be covered with the MARC migration script with a reindex. Ryan proposed adding a new requirement for the Boolean “AND” option. Ryan agreed.

• Take a look at the 2 new stories and add use cases as a comment and a more detailed description.

#30: Support search within list

Felix added #30 after receiving a question from Vivian regarding a limit for the number of items linked to a holdings in Slack. Felix mentioned that there should be a way to search for certain items in the holdings record. Laura said that we want to make sure we can search through all pages not just the page currently displayed, and there should be a way to customize the sort for items. Christine said that last August they discussed inventory item search and have a frontend story that will require some backend work. They are also working on a spike to sort items, and this will be worked on first.

Product Council updates

Charlotte Whitt

2025-05-08 Product Council Agenda and Meeting Notes

Announcements: Data Import WG will become a SIG. Next PC meeting will be a Tri-Council meeting.

Summary

Early adopters and Eureka transition timeline: Main topic: has the criterias for the Eureka early updaters been fulfilled. The CC and PC acknowledged the Eureka timeline, and roll out with Sunflower with no delay, if all criterias were met by early adopters.

All criteria have not been met at this point. The early adopters Index Data and self-hosted institutions are worried they have not seen beyond the basics of Eureka. Postponing the Sunflower release will cause issues for Galileo who needs to go live on the Sunflower release. EBSCO cannot wait for early adopters to catch up.

There is also an issue in that they will only maintain two releases back. Trillium is planned to be released in November. When Trillium is released, only Trillium and Sunflower will be maintained. Both releases will only support the Eureka platform. Community driven development team is exploring maintaining Ramsons and okapi.

Details

GBV: It is difficult to say when to migrate to Sunflower / Eureka. GBV has spun up a platform complete system. But this is not production ready, while it can no interact with third party system. Also the SSL encryption issue.

Index Data: Expect to have the base platform up an running by next week. Next step is to make the system production ready. Swap platform is a major change, so all existing monitoring system, needs to be updated. Key worry is, getting all customers up and running on Sunflower by 11/10/2025.up and running on Sunflower by 11/10/2025.

TAMU: Experience same issues as GBV and Index Data. Had problems with name-spaces. Now everything had to be pulled into one name-space. The configuration is not as expected for a production system. TAMU can not confidently move on to Eureka until Spring-Summer 2026. Stephen Pampell underlined that moving ahead with this, put a tremendous pressure on the Self-hosting libraries.

Jeremy Huff mentioned that Community Driven Development could be an option: maintaining Ramson’s on Okapi for an extended period. Mark Veksler agreed. EBSCO has migrated LoC as an existing Okapi customer to Eureka.

Kristin Martin underlined that postponing Sunflower and Trillium is not an option, due to contractual obligations for customers with Go-live plans.

BELA (Bulk Edit and Lists App)

Jennifer Eustis

No meeting this week.

Jennifer encouraged MM members to visit the wiki and check out and vote on JIRA issues for Bulk Edit and Lists. Magda takes those into account when assigning priorities.

Data Import Working Group

Jennifer Eustis

https://folio-org.atlassian.net/wiki/spaces/DISIG/pages/955089068

They continued the discussion regarding how Data Import should be self-organized. Representatives from Data Import went to the Acquisitions and App Interaction SIGs. Discussions in MM and Data Import Working Group were taken into consideration.

The group decided to become a SIG. Christie Thomas and Jennifer Eustis will be co-convenors. Christie and Jennifer will work with Ryan on roles and responsibilities. Jennifer will schedule a presentation for the PC. Looking forward, this SIG wants to have more collaboration with other SIGs, provide both asynchronous and synchronous ways to participate, and ensure that all aspects of DI (acquisitions and bib) get the attention they need.

Data import updates will continue in MM, and there will still be a summary in the Data Import channel. Jennifer encouraged everyone to vote on JIRAs. Felix asked whether Data Import will have its own wiki and DI information will be transferred from MM to the new wiki. Jennifer said that administrative changes will be discussed in a future meeting and asked Felix and Raegan for feedback.

Raegan said it would make sense to move DI information to the new wiki so information will only be in one place. She suggested maybe leaving one page to let people know the Data Import now has its own wiki and provide links.