2025-05-22 Product Council Agenda and Meeting Notes

2025-05-22 Product Council Agenda and Meeting Notes

 Date

May 22, 2025

 Participants

  • @Alexis Manheim, @Martin Bauschmann , @Charlotte Whitt , @Lisa McColl , @Martina Tumulla , @Mark Veksler @Shelley Doljack @Lee Braginsky @Jana Freytag @Gang Zhou @Jenn Colt @Tod Olson , @Martin Scholz , @Hkaplanian , @Brooks Travis @Lucy Harrison @Owen Stephens @Stephanie S. Buck @Christopher Spalding

  • Note taker: @Kristin Martin

 Discussion topics

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes

5 min

Announcements and PC Calendar review

all

  • Documentation Working Group will have a new interim convener Ludwig Liebl from June 2025 on.

  • We will need to cancel PC on June 5 because it conflicts with the FOLIO members meeting. All are invited to that meeting. We will discuss in our planning meeting on how to reschedule the SIG Conveners Update meeting

  • As a follow up from the March 2025 in person summit, a CC working group revised the FOLIO vision statement. Details are in the CC meeting notes here: 2025-05-12 Community Council Meeting Minutes . This is not a vote, but please review and you can add any comments to the document.

  • Today is Sherlock Holmes Day.

5 min

Eureka early adopters updates

@Jeremy Huff @Charlotte Whitt
@Kirstin Kemner-Heek GBV, Texas A&M, Index Data

Few early adopters present at the meeting to provide an update. @Jana Freytag indicated no update from GBV

Continued cadence of these updates? Change updates to Ramsons support?

Maybe we should switch to every other week, given the slower cadence, but need to stay focused.

Decision: shift to every other week.

15 min

Better Sample Data working group update

@Charlotte Whitt @Shelley Doljack @Kristin Martin

Charlotte presented an overview of the Better Sample Data Working Group, which has been working for the past year as a working group of the PC. The goal is to update the data in Snapshot and also in BugFest, to make testing more effective and to be able to catch issues earlier in the development cycle.

Shelley then talked about Stanford’s work to supply their dataset to support a refresh of BugFest. The slides details how Stanford and other universities could share data into BugFest in a safe way that would protect user privacy. She shared the anonymization protocol to make data safe to share. Lee shared how EBSCO developed the anonymization proof-of-concept in fall 2024 to be able to replicate issues in production that were not able to be reproduced in test environment. Goal to reduce number of critical service patches. Stanford is the first implementation phase of this project. Noted that some anonymization is required by some institutions but not others, e.g., shuffling loan history on items, or types of material that can be shared in order data. We are working with Michigan State and Chicago to see if they can also donate their data. There is a forum on Mondays for data anonymization. Please reach out to @Lee Braginsky if you would like to join. https://folio-org.atlassian.net/wiki/x/BQA4K

Returning to Snapshot, Charlotte shared how data in Snapshot is getting updated to be more current and connected for testing.

30 min

Open Access SIG

@Martin Bauschmann

Martin shared the rationale for the Open Access App, the people involved, and current status. The app is not part of the FOLIO releases but comes up regularly to ensure compatibility. In use by multiple institutions in Germany. Exciting news for new development work to begin again after a period of hiatus. Will be looking for a sustainable way to support the app going forward.

Question: how are German libraries required to track the payment of APCs? Answer: paid mostly by the libraries, some additional funding sources, but wanting to centralize things in the library.

Question: what about orders for APCs? Answer: could be good to talk with Acquisitions SIG. Maybe there could be a way to create an encumbrance without an order.

5 min

Future topics

all

Juneteenth - should we meet? Alexis will survey PC members in slack