2025-01-16 Product Council Agenda & Meeting Notes

5 min

Announcements

all

• Reminder to vote on Reading Room Circulation functionality

• @Jesse Koennecke asks for volunteers to help with Wolfcon 2025 planning

  • @Kristin Martin : What are there dates for Wolfcon25? Dates are not announced, yet. The dates will be roughly the same as for London: Sept 22-26

15 min

Calendar planning

@Alexis Manheim @Kristin Martin

SIG updates/convener meetings, etc. need to be added to our 2025 Topic Calendar

• SIG Convenors Meetings should not clash with end of FY, Wolfcon, holidays…

  • Some SIGs have new conveners. Be aware and inform/reach out.

• Tri-Council meetings may be on PC meeting time

• Presentation of new module mod-ill in FOLIO from K-Int next week. This functionality may be related to OpenRS. TC also was unaware of the module. It currently is unclear what scope and functionality this module shall provide and which SIG / subgroup is affiliated with that.

  • @Jeremy Huff Is this the first approach to ILL in Folio? Not sure, there may have been some rudimentary functionality.

    • @Jesse Koennecke There is an abandoned(?) Jira ticket from 2023 regarding TC review: https://folio-org.atlassian.net/issues/TCR-34?jql=ORDER%20BY%20created%20DESC

  • @Charlotte Whitt With which SIG is K-Int cooperating on that? => It’s unknown, definitely not with Consortia SIG.

25 min

Eureka timeline

Can the PC affirm the community’s intention to shift to Eureka in Sunflower and focus on planning for the transition?

@Alexis Manheim

Background:
Report on the timeline for adoption of the Eureka platform

Recording of the Tri-Council meeting and/or review the meeting notes

@Alexis Manheim : Summary: EBSCO will support only Eureka staring with Sunflower. An early adopter program has startet to test Eureka on non-EBSCO hosted orgs.

Main questions: Can the community / PC vote for adopting the proposed timeline? What does the Community need to do to be able to follow?

@Jeremy Huff : Having had little contact yet with Eureka, dropping support for Okapi already in Sunflower is worrying. If it comes out that greater implementation changes are required it may be too heavy

@Jennifer Eustis : Timeline seems bit rushed. Eureka test system was often down, doesn’t seem to work smoothly. Timeline may be too ambitious. It may be a lot of work in a couple of months for implementers.

@Alexis Manheim : No need to immediately shift to Sunflower. Implementers may choose / be able to remain on Ramsons for a while. (There will be CSPs for Ramsons after Sunflower is out.)

@Kristin Martin Regarding possible step “Long-term, but not required prior to Sunflower, support SIGs and POs in implementation of application formalization”: Impression that Dennis from ACQ SIG wants app formalisation finished with Sunflower. Seems too early to complete app formalisation with Sunflower. What is the timeline? Waht needs to be done for Sunflower by the PC?

@Brooks Travis LOC uses Eureka for some time now. Not much change in scripts interaction. Interacting with permissions will require bigger changes.

@Jeremy Huff What if community will not transition in sunflower? Specifically, what does Community bugfest testing mean?

• @Alexis Manheim Community will have to do bugfest on their own, providing own environments, resources, tooling, …

@Jennifer Eustis PC is expected to help people understand what changes are gonna happen.

@Jeremy Huff good that document mentions that CSP will be available for Okapi till Trillium

@Tod Olson In timeline there are addressed requirements for Eureka adoption like hosting providers having enough confidence in being able to run Eureka. Also, Sunflower modules not directly attached to Eureka are expected to work with Ramsons' Okapi. Okapi will still minimally be supported as long as Ramsons is supported. (CSPs until Trillium)
Therefore it may be more util to think about date when Ramsons going unsupported that Sunflower being released.

@Kristin Martin Ensure that libraries that are already implemented on Folio with Okapi have a clear migration path to Eureka. This could and should be a concern for the PC.

@Alexis Manheim Is it the responsibility of the hosting providers or the PC that hosting providers and implementers feel comfortable?

@Kristin Martin PC has not done a great job on supporting libs that have implemented Folio already. Focus was on new functionality and new implementations.

@Jeremy Huff Charge of councils does not require PC to support hosting providers. But it should be PC best interest.
Table in document “What if the community does not transition to Eureka in Sunflower?” feels confortable, but is presented as encouraging community to transition, assuming that commnuity is not able to go this way.
Community really should have more agency in order to run own bug festing, etc. if necessary, drilling down to community-run environments and community driven development.

@Kirstin Kemner-Heek Topic is complicated, has very many aspects to be considered. GBV is hosting provider for ~200 libs, currently runs ~50 tenants that have to be moved now. The early adopters step by step will work out processes and documentation how to proceed with the help of EBSCO. The transition and the early adopter programm will have impact on implementation plans, binds resources and costs money, but there is no alternative. Hope and optimistic impression that Eureka is a good choice for running FOLIO.
There should be regular reports to / communication with the community on status and input from the community.

@Alexis Manheim Worries what to do when early adopters would express discomfort. What could be potential showstoppers?

• @Kemner-Heek, Kirstin Too early to say. Atm, everything seems sensible. Early adopters meet weekly, before PC time. First really informed impression in a couple of weeks.

@Jeremy Huff Confirm. Without more information in hand, go conservative. Prefer voting on the timeline in March.

@Alexis Manheim Does this mean that the Sunflower release date needs to be postponed without that information / sufficient confidence in Eureka?

• @Jeremy Huff Yes

• @Tod Olson Confere to project mgmt triangle: resource, scope, time. Here: resources and scope are fixed, so time needs to be variable.

@Alexis Manheim postponing Sunflower release until sufficient confidence should be expressed explicitly in document

• majority votes thumbs up

5 min

Future topics

all