2025-09-4 Product Council Agenda and Minutes

10 min

Welcome & Announcements

Need notetaker volunteer: Jennifer Eustis

Bringing back Tuesday agenda planning meeting: We went on a hiatus in August and now we are bringing this back. The co-chairs and liaison from TC and CC went to that meeting. Alexis will update that page to make sure that these core people make that meeting.

Trillium Delay

Jeremy: I have some mixed feelings. This was the ask originally to delay Trillium and extending Ramsons support. It would have been nice to have this decision last Spring. For Texas A&M, this puts them in a better place to go to Trillium. For those who needed the original deadline, this isn’t good.

Charlotte: For the National Library of Sweden, they are going live with Trillium. Last week there was a lot of conversations. The solution for NLS is that the new work will be included in Sunflower for the critical work. Now they will discuss how to divvy up the critical work in the CSPs for Sunflower. This wasn’t planned well.

All of Trillium is being pushed back.

Caitlin: How does communication and input happens?

Charlotte: The process for changes is done by the release management group which also comes to PC to explain things. Officially the decision hasn’t been made yet.

Jeremy: The relationship between PC and Release Management has been called into question. There are differing opinions on that relationship.

Caitlin: I’m not sure how this works and that’s a good point about discussing the relationship. Jeremy: Can you help with working on this relationship?

Jeremy: Perhaps we can have a document review.

Housekeeping - skip this week

Updates on Active Initiatives - skip this week

New Topics

10 min

Data Import SIG Priorities

We are working on how to contribute to Data Import and what this process looks like. There are many pathways to contribute and that can be confusing for many SMEs. For our priorities, these are mostly bugs. These were originally in scope for data import but were never developed. Some were never developed because of the architecture and the way DI has been implemented. Because of these decisions, it has made SMEs work in this area more difficult.

Kristin: You are creating a community MVP. This is a great way of framing these issues. How are you going to do this? How can we help market this?

Christie: We have this as a to-do for our community. We had a MVP when we started in 2018 with the UI designer. We’re so focused right now on putting out fires that what is in Jira should represent the MVP but don’t. We also didn’t subtract from the development we need. Our new process should include that. We have institution vision. We are a new SIG. Before this, our priorities were buried under MM SIG ones. We are taking this time to rethink how we accomplish this work.

Caitlin: PC is looking at a draft rubric for prioritization, https://folio-org.atlassian.net/wiki/spaces/PC/pages/1184956419 .

Lisa: As Christie and Jennifer were talking, both have stuck with Data Import to make it better. For Lucy Harrison has been a big sticky point. Data Import is a point to not moving to FOLIO.

Charlotte: We really need to focus on the UI. The majority of users don’t have the staff or the skills to use the APIs. It would be useful to have a session to learn how people are using the APIs. APIs shouldn’t be the primary or thin thread.

Caitlin: It could be a long time before these needs are addressed with our technical debt and timeline.

10 min

ERM SIG Priorities

Communitiy Priorities ERM

Requirements will be discussed are added to the implementers' topics. Jira ticket is created and then the community can vote. Then the issues are sorted by votes. From that list, there are the top 5 priorities that are teased out. Owen (PO Agreements/Licenses): This idea to do a copy or transfer of agreement lines opens up the possibility of delivering new functionality. For #4, this will allow to delete data they don’t need. Zorian (PO ERM): Within eHoldings app, you can add supplementary properties for agreement lines. This removes the middle step so that it can be done all at once. Stefan (PO Usage): Usage App is in use at several institutions and improvements are becoming clearer. They are working on a roadmap.

Caitlin: This SIG is more mature and has clear steps on how to improve usability.

Owen: Sounds good. It is an endless journey. There is a lot of existing functionality and they keep trying to push forward with enhancements.

10 min

Reflections on tri-council meeting

https://folio-org.atlassian.net/wiki/spaces/CC/pages/1144487953

PC will continue this discussion on Slack.

Planning

10 min

Define agendas for next 2 meetings to be done at next Tuesday’s Planning meeting

• Check Jira board

• Check Calendar

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