...
\uD83D\uDC65 Participants
Lucy (Galileo)
Gang Zhou (until ~ 30min)
Note taker: Martin Scholz
\uD83D\uDDE3 Discussion topics
Time | Item | Presenter | Notes |
---|---|---|---|
5 min | Announcements | all |
|
15 min | Calendar planning | SIG updates/convener meetings, etc. need to be added to our 2025 Topic Calendar
| |
25 min | Eureka timeline Can the PC affirm the community’s intentionto shift to Eureka in Sunflower and focus on planning for the transition? | Background: Recording of the Tri-Council meeting and/or review the meeting notes == DRAFT, still needs review from here == Alexis Manheim : Summary: EBSCO will roll out Eureka with Sunflower. What needs the Community to do to be able to follow. An early adopter program has startet to test Eureka on non-EBSCO hosted orgs. Main question: Can the community / PC vote for adopting the proposed timeline. Jeremy Huff : Having had no contact yet with Eureka, feels anxiety that it is unclear whether it requires greater implementation changes etc. Jennifer Eustis : Timeline seems bit rushed. Eureka test system was often down, doesn’t seem to work smoothly. Timeline may be too ambitious. Alexis Manheim : No need to immediately shift to Sunflower. Hosters may be able to remain on Ramsons for a while. (There will be CSPs for Ramsons after Sunflower is out.) Kristin Martin From Acq SIG: Not complete app formalisation with Sunflower. 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? => What does Community bugfest testing mean?
Jennifer Eustis PC is expected to help people understand what changes are gonna happen. Jeremy Huff good to know that CSP will be available for Okapi till T Tod Olson In timeline there are addressed “showstoppers” for Eureka adoption like hosting provider being able to run Eureka, documentation. 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) Kristin Martin Ensure that libraries that are already implemented on Folio, have a migration plan. Alexis Manheim Is it the responsibility of the hosters or the PC that hosters and implementers feel comortable? Kristin Martin PC has not done a great job on supporting libs that have implemented Folio already. Focus was on new functionality. Jeremy Huff Charge of councils does not require PC to support hosters. But it should be PC’s concern. Table in timeline doc should be seen as encourageing community to transition. Kirstin Kemner-Heek GBV is hosting provider for ~200 libs, currently runs ~50 tenants that have to be moved now. The early adopters will work out processes and documentation how to proceed. The transition and the early adopter programm costs time and money, but there is no alternative. Alexis Manheim Worries what to do when early adopters would express discomfort. What could be potential showstoppers?
Jeremy Huff Confirms. Without more information in hand, go conservative. Alexis Manheim Does this mean that the Sunflower release date needs to be postponed without that information / sufficient confidence in Eureka?
Alexis Manheim postponing Sunflower release until sufficient confidence should be expressed explicitly in document
| |
5 min | Future topics | all |