/
2025-09-11 Product Council Agenda and Minutes

2025-09-11 Product Council Agenda and Minutes

 Date

Sep 11, 2025

 Participants

  • PC Members: @Jennifer Eustis @Jana Freytag @Autumn Faulkner @Thomas Trutt @Charlotte Whitt @Jeremy Huff @Martin Scholz @Lisa McColl @Alexis Manheim @Caitlin Stewart

  • Other Attendees: @Gang Zhou @Cornelia Awenius @Lucy Harrison @Martina Schildt @Sharon Markus @Susan Kimball @Anja Kakau @Peter Murray (OLF Tech Coord) @Nicole Trujillo @Martina Tumulla @Hkaplanian

  • Regrets: @Tod Olson

  • Note taker: @Autumn Faulkner

20250911 PC Recording

Highlights for Monthly Newsletter

 Discussion topics

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes

3 min

Welcome, Announcements, & Note Taker

 

Jeremy

  • Sessions being offered for WolfCon presenters.

    • First information session for presenters has been held, recording will be shared.

    • Next session taking place Friday 9/12, which will be recorded as well.

      Slides, Zoom. 10-11 am ET

    • Sessions include maps and directions for reception and council meetings.

    • Updates will be posted in the WolfCon conference chat.

Updates from Liaisons:

  • Release Management (RMS)

  • TC

  • CC

 

 

 

5 min

RMS Update

Jennifer

  • RMS: Release Mgt Stakeholders Mgt

  • More info from Harry K. re: Kong

    • One of the components that makes up Eureka is Kong, an API gateway.

    • Kong code has been released as open source along with corresponding builds in the past; these builds will no longer be provided by the company behind Kong development. But the code is still being provided as Open Source.

    • We are investigating alternatives to Kong as a mitigation plan in case any changes to open source status happen in the future. This has happened to FOLIO in the past. Ex. Elastic search vs Open Search. See Kong-33

    • In addition, EBSCO has published instructions on the FOLIO wiki that show how to build Kong for Ubuntu. See Kong-34.

    • In an open-source environment, components like these are constantly changing, which is to be expected. The move to Eureka will help us adjust easily to these kinds of changes, given that it uses multiple single-purpose modules (like Kong!). This proves the concept Eureka was based on.

3 min

CC

Alexis

  • Tri-Council planning:

  • Pass-through funding proposal:

    • CC heard a presentation a few weeks ago about the proposal that asks hosting providers to include pass-through FOLIO community development funding as part of yearly hosting billing.

    • Fees would be passed from hosting providers directly to support community efforts and costs, like Bugfest and AWS, etc.

    • Fees would range from $500-$2000 depending on the size of the institution.

    • Opt-out option would possibly be available for institutions unable to participate.

3 min

TC

Tod

 

Housekeeping

5 min

Rolling SIG Updates

Jeremy

  • SIG Engagement Model:

    • Proposal to shift from seasonal updates to rolling updates for better continuity and focus.

  • Encouragement for SIGs to Refine Tickets:

    • More detailed documentation improves chances of development and funding

Updates on Active Initiatives

5 min

CDD Working Group Update

(Community Directed Development)

Jeremy

  • Proposal Synthesis:

    • Three major proposals (Tom Pramer, Mike Garel, Jeremy Huff) are being merged into a unified framework. See draft here:

  • Two WOLFcon sessions on CDD:

    • (1) Overview of CDD proposals and historical context.

    • (2) More specific proposal information and workshop for community feedback.

SIG Updates

10 min

Resource Access SIG

@Susan Kimball and @Cornelia Awenius , co-conveners.

  • Selecting priorities

    • FYI that this first attempt at prioritization was constrained by time and Jira considerations.

    • Four of the five Jiras selected are still in draft.

  • Top 5:

    • (1) Batch renewal across multiple users (manual first, then hopefully automated)

      • Larger universities have tools and resources for API workflows for issues like this; smaller libraries, however, really need a UI tool.

      • Suggestion from Harry: Flesh out UXPROD-3651 and others. It’s fairly simplistic at this point; adding context and concrete details enable developers to make a work plan. List out what you would like to see happen; doesn’t have to be technical, per se. Some libraries could even get together and pool funding to promote development.

    • (2) Search filtering on item loan type, both permanent and temporary

    • (3) Sorting printed pick slips; currently they come out in random order, and having to manually sort them is time consuming.

    • (4) Have multiple items on a request notice to a single patron, instead of notifying them by email 20 different times for each separate item.

    • (5) Title level hold requests, rather than just item-level.

  • Course Reserves subgroup

    • FYI that they have also identified five priorities of their own, separate from these

  • Question from Jeremy: What was the process for prioritization? Was there a lot of deliberation?

    • Not much time for deliberation. RA is one of the oldest SIGs, with Jira tickets dating back to the very first releases. Currently the focus is reviewing outstanding issues to consolidate and clarify current needs. The group wants to complete this process before they spend a ton of time on priority discussions.

    • If we had more time, we could have combined some of these issues into one ticket, since some of them are related.

10 min

Reporting SIG

@Sharon Markus

  • Reporting SIG deals with MetaDB (the main development focus), but also in-app reports, Lists, etc. Anything that takes data out of the system.

  • Data privacy

    • Chief concern of SIG at the moment is data privacy.

    • Considering how this data used by different institutions and working to reduce exposure to patron identifiers.

    • Complex topic, given competing needs for managing user tasks and data but protecting privacy wherever possible.

    • Anonymization feature being developed by IndexData for the 1.5 release of MetaDB.

    • Challenges include:

      • Historical data in MetaDB remains unanonymized.

      • Deleting data risks integrity; need upstream anonymization in Folio.

  • Subgroup Formed:

    • MetaDB Data Privacy Subgroup meets regularly to analyze and write tickets.

  • Other Priorities:

    • Data Array Extraction:

      • Convert JSON blobs to structured columns.

    • In-App Report UI Consistency:

      • Partnering with Cross-App SIG to standardize CSV download interfaces.

Planning

5 min

Newsletter topics

 

 

10 min

Define agendas for next 2 meetings

 

 

 Related materials

📄 Meeting Minutes: