2025-11-06 Product Council Agenda and Meeting Notes

5 min

Welcome & Announcements

@Tod Olson

• The Five Colleges’ test environment just went to Sunflower and Eureka. Would PC be interested in a presentation from our systems person? The User Mgt group and Implementers Group would be interested in that. There’s a permission subgroup.

• National Library of Sweden has spun up a running Eureka environment which will be there platform for going live.

Housekeeping

3 - 5 min

Liaison Updates

@Tod Olson , @Alexis Manheim , @Jennifer Eustis

TC:

• Eureka: Stanford making good progress

• Environment variables still the topic of dedicated discussion.

CC: No meeting this week or last. Meeting next Monday (11/10.)

RMS:

• Finalizing regression testing for Ramsons CSP #8.

• Working on Sunflower CSP #3. All tasks should be completed by Nov. 13 and GA is set for Nov 24th

• https://folio-org.atlassian.net/wiki/spaces/REL . This page now includes a calendar of FOLIO Releases.

3 - 5

Remind SIGs about December Update

@Tod Olson

• There is a common location for these updates: https://folio-org.atlassian.net/wiki/spaces/PC/pages/622657730

• An announcement was posted on the Slack #sig-coveners

3 - 5 min

Action Item Review

@Tod Olson

Thomas Trutt’s action item: The meeting is next Tuesday and will bring this action item up then.

Updates on Active Initiatives

3 - 5 min

Working Group Update: The Community Priorities Dashboard

@Alexis Manheim

Could everyone look this charter and provide feedback directly on the document?

3 - 5 min

Working Group Update: Community Directed Development Framework

@Jeremy Huff

The link to the charter was posted in Slack. There are some details in the Charter to work out.

3 - 5 min

Working Group Update: RMS/PC Roles, Relations and Communication

@Autumn Faulkner

Draft of our charter here. Feedback appreciated!

5 - 10 min

Working Group Update: Better Sample Data

@Autumn Faulkner @Yogesh Kumar

There are two scales: snapshot and bugfest. Snapshot will be smaller. Bugfest will be larger. The working group would like to get an anonymized set from an institution. For snapshot, the working group has started populated it with data and has run into issues. We need data sets from libraries to do proper testing. In the long term, there will be a need to work out how to sustain and maintain this.

New Topics

10- 15 min

SIG Priority Presentation: Implementors

@Thomas Trutt @Tara Barnett @Darsi Rueda

As a SIG, there are projects that are priorities: looking for a new convener; presentation on Archive Space and on RFID Integration. Looking for presentation topics. Heard that the SIG’s documentation is useful - guides to functionality. The SIG wants to clean up their wiki space. The other project is the survey. The SIG has 2 Jira issues for UXPROD-4776 and UXPROD-3822. The SIG doesn’t do prioritization sessions.

It makes sense to have UXPROD-3822 on this communities priorities spreadsheet. This is something where funding could be gathered.

One of things the working group on communities priorities is what should be in tickets and the priorities are actionable in some way.

10 - 15 min

SIG Priority Presentation: Cross App

@Tara Barnett

For Cross App, there are clear 5 priorities. There’s a date picker consistency problems. It is a struggle to move work forward. Search standards and documentation: by documenting the issues then the SIG can highlight was needs to be worked on.

10-20 min

TC Support Dates for Ramsons and Sunflower: VOTE

https://folio-org.atlassian.net/wiki/spaces/TC/pages/1187348628

What are the implications of these changes? The implication for libraries is that support for previous flower release would be limited.

One implication is that libraries who find it impossible to upgrade at this cycle are taking on a risk that issues won’t be fixed. Implementers may be taking on some risk.

Would it make sense to extend the time period would monitoring and mitigation advice would happen? The scope of document limits that to Ramsons which is an exception because of the delay to Trillium. The hosting vendor still has people on Ramsons and hence has an interest in supporting Ramsons. Functional fix is different from the security fix.

This is predicated on 2 releases per year. No as a project, we will set the end date of support for any 1 release regardless of any releases in between.

We’ve had the idea of rolling release. Does this framework take that into account? This hasn’t been taken into account and this decision would need to be re-evaluated.

Has this been presented to CC yet? If we feel we are ready to vote, we usually do it in Slack. CC hasn’t talked about this yet. From the TC, presenting this to CC wasn’t on their radar. Some confusion as to whether this needs to be endorsed by both councils. TC is not explicitly looking for CC input.

Would it make sense to separate security and functional releases? The resources that it might not are not inconsiderable. The hope is that Sunflower to Trillium is exceptional.

Planning

5 min

Newsletter topics

All

• Celebrate Closed Tickets on the Dashboard

• We need to be sure to promote the community dashboard

10 min

Define agendas for next 2 meetings

All

• Check Jira board

• Check Calendar

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