2025-02-27 Product Council Agenda and Meeting Notes

5 min

Announcements

all

• Early next week the call for Wolfcon Proposal should come out (Jesse)

10 min

Eureka early adopters updates

Move to Eureka Permissions and documentation efforts

@Kirstin Kemner-Heek @Jeremy Huff
@Charlotte Whitt

GBV, Texas A&M, Index Data

Implementers and UM SIGs are working on becoming familiar with the new permissions setup in Eureka. What can the PC do to help/facilitate this process?

• Sasha: Eureka - define application which are collections of modules. What modules and what versions make up Sunflower release? FOLIO is becoming a rolling release, a fluent release?

• Oleksii agreed - this is a fluent release. Each library will select their own application.
  
  

Charlotte reported on the last Implementers' meeting. Thomas Trutt gave an introduction on what the changes will look like and demonstrated that in FOLIO snapshot when converted to the Eureka platform. He also demonstrated tools he is using to analyze permissions given to Cornell’s staff. He explained how he plans to migrate these changes.

Maura Byrne reported that the User Management Group had a lab session yesterday. Thomas was there. The group got a chance to look at permissions with Eureka. Maura set up a Eureka Lab page in the User Management SIG Wiki space. Maura suggested grouping meeting recordings that deal with the Eureka platform in one place.

Alexis brought up documentation. Documentation has not started yet. The Documentation Subgroup of the User Management Group will address this.

Alexis: Do we need a Permissions Subgroup?

Oleksii - suggested in addition to gathering recordings, having a summary of each meeting will be helpful too. FOLIO Knowledge Base chatbot <https://copilotstudio.microsoft.com/environments/Default-b41b72d0-4e9f-4c26-8a69-f949f367c91d/bots/cr4d9_folio/canvas?__version__=2&enableFileAttachment=true> Alexis suggested we turn on the transcription service for our PC meetings.

15 min

Future release planning under Eureka and app formalization

@Oleksii Petrenko

Trillium R2 2025 Release plan - FOLIO RMS.
Slides includes timeline of 20205 Trillium release.

Oleksii noted that in general the release cadence will be varying in the future. Often depends on customer demands.

In chat, “From us at the Nat Library of Sweden: re Trillium specifically the Klemming dev team will definitely need the full 14 sprints to be able to finish updated Reading Room Functionality. If we are to go live with FOLIO Q1 2026 that is “

Charlotte said for future planning maybe a more even release schedule may be possible, but we cannot change now in the middle of the planning year.

With various small releases Kristin mentioned a concern about constant testing. Oleksii noted the pros and cons of large releases and testing versus small release testing. He favors small releases so Bugfest is much smaller.

Alexis: How does that work with cross app interaction? If various apps are released at different times, how do we gauge their affect on each other?

Martin: Clarified the meaning of “smaller releases”. Oleksii answered that a small release means that less features will be released at a time but more frequently. A new module can be released to update a particular feature.

25 min

PC Goals

@Alexis Manheim

Follow up from last week on Google Calendar @Jesse Koennecke

PC Ranked Goals

1. Update PC Review Process – 37

2. Engage with App Formalization – 37

3. Revive Community Development – 40

4. Solicit & analyze community priorities – 41

5. Communicate Development priorities and activity to the community – 44

6. Develop leadership opportunities within the community - 52

7. Recommend cross-platform standardization – 57

(The lower the number, the more important the goal).

Alexis suggested documenting the progress that was made on 1 and 2. Do we want to move on to 3, 4, and 5?

• Jennifer said we have the Review Process in place, but now how do we find this new functionality that we want to review. This may fit into #4.

• Charlotte: Community Development is still relevant. The Resource Access SIG working group is working hard on their priorities. If there is anything we can do to further this goal it would be good.

  • Caitlyn wondered if Community Development would be a good topic for WolfCon.

  • Alexis - would getting a new developer advocate help?

• Kristin believes that 3 and 4 work well together. She referred to the “Setting Up a Filter Subscription” page set up by Kimberly Pamplin. This may be a way we as the PC can gather what the SIGs are asking for.

• Alexis: Subgroups seem to have worked well in the past. <Side note about calendar, which Jesse is working on - would like to set up best practices for the calendar. He will post to Slack>

• Kristin noted that we may have too many things on our list and that narrowing our focus may be beneficial to accomplishing more.

• Jennifer: The focus on new features can take away from features that were never fully developed. She noted the large backlog - how can everything get done?

• Alexis: Should we focus on community development to improve existing functionality?

  • Lisa thinks this is a good idea

  • Charlotte agrees with this approach as well. If PC can facilitate improvements on existing functionality that may help SIG members get engaged.

5 min

Future topics

all

Next week we will only talk about goals!