2026-03-12 Product Council Agenda and Minutes

5 min

Welcome & Announcements

• WOLFCon Presentations due on the 25th

•  

Liaison updates

TC:

• Ongoing concern about how PC & TC approval processes intersect.

• Continuing to work on the developer conference

• Refining Existing Module Review process, sorting out questions like remediating gaps that are found, pace of review. For details: https://folio-org.atlassian.net/wiki/spaces/TC/pages/1751580673

CC: AWS Costs Review Group met to review the FY 27 budget request. The proposed budget maintains the $30,000/month spending rate for Development, Testing, and Performance environments. Bugfest environments continue to be fully funded exclusively by EBSCO.

Request from the Better Sample data group: Anonymization scripts written for proof-of-concept, but more development is required before they are ready to implement. Developer volunteers needed to finish and deploy on a test dataset. Number of developers: 2, 180 hours; Languages and platforms: Java, Python & Airflow (as an alternative, used in post-POC preliminary efforts ), FOLIO Schematool.

Ratified Membership Committee charge. Next steps: Organize member meetings (virtual first, then WOLFCon face to face.)

RMS: No meeting this week.

Housekeeping

10 min

Discussion on Clarifying the Relationship Between Feature Endorsement (PC) and Implementation Approval (TC)

@Tod Olson @Jeremy Huff

Discussion on the PC’s discussion on endorsement process. They have identified gaps between what we are doing and what they are doing. How does the TC know if they need to approve any particular piece of development?

There is a desire to close that gap and ensure that our two processes are complimentary and easily understood by all. Charlotte suggested a shared document between the TC and the PC.

PC approves at the feature/function level, TC approves at the module level. Two main issues:

1. The connection between modules and endorsed functionality are not always clear, the connection from a submitted module back to approved functionality is not always clear.

2. TC does neither wants to spend time reviewing modules where functionality has not been endorsed nor provide an end-run around the PC process.

PC now has an review board (PCE) which helps, but also when the functionality is reviewed the modules may not yet have been defined.

Potential solution: PC endorsement process asks for modules implicated (may not be known or my change during implementation), TC approval process asks for links to endorsed functionality

Action: @Jeremy Huff to raise this coordinated approach on Slack with TC co-chairs.

Updates on Active Initiatives

15 - 20 min

Sub Group Updates

@Jeremy Huff @Alexis Manheim @Caitlin Stewart @Autumn Faulkner

Community Directed Development:

Harry: questions about what makes up a community development team, will make comments on documents

The Community Priorities Dashboard:
Returned to WOLFcon sessions, deciding on timelines for this year’s SIG priorities. Sequence: get SIG priorities, look for themes, plan workshop at WOLFcon

RMS/PC Roles, Relations and Communication:

Planning to present documents next week

New Topics

20 min

Advocating for a FOLIO AI SIG

https://folio-org.atlassian.net/browse/PCE-14

Jeremy Nelson

Last two WOLFcons were followed with discussion of establishing a SIG for investigating AI and ML in FOLIO. There are examples of sites working with AI/ML in FOLIO.

Not specifically for developers, more broadly available. Would like a central clearing house for AI issues in FOLIO.

• Offer annual AI in FOLIO WOLFcon workshops

• Use MCP to connect to AI assitants, using at Stanford in metadata creation, using an edge-ai module

• Context engineering for Gen AI

  • Can we expose FOLIO JSON to improve context?

  • Can we reduce the computing resources

• Promote ethical and responsible use of AI

Q: would the SIG be custodian of a particular module like edge-ai or more of consulting?

Maybe a bit of both, not seeing edge-ai as the main thing, more providing help with analysis.

Is there are role for providing guidance for developers about using AI in FOLIO coding? SIG could provide some transparency around the use of AI.

Also, establish some guardrails about how AI is used across FOLIO, not just in coding.

Next steps: see https://folio-org.atlassian.net/wiki/spaces/PC/pages/4882624

Planning

5 min

Newsletter topics

10 min

Define agendas for next 2 meetings

• Check Jira board

• Check Calendar

• Seehttps://folio-org.atlassian.net/wiki/x/koARJQ