Table of contents
Introduction
Benefits of Eureka adoption
Eureka adopter support
Timeline
Next steps for councils
Next steps for hosts and implementers
Next steps for EBSCO
Introduction
The community has two key questions to answer:
Does the community adopt Eureka?
On what timeline does the community make Eureka the official FOLIO release?
Implications of Eureka adoption
Changes
Move from module based platform to application-based platform
Features
Benefits
https://folio-org.atlassian.net/wiki/spaces/TC/pages/518946885/0010-eureka#Benefits
Reduced maintenance through deprecation of homegrown modules:https://folio-org.atlassian.net/wiki/spaces/TC/pages/518946885/0010-eureka#Deprecations
Eureka adopter support
Existing support
Planned support
Gaps in support
Timeline
Sunflower: EBSCO shifts support from Okapi to Eureka
How long does the community support Eureka? Does the community shift from Okapi to Eureka in Sunflower?
Quesnelia | Ramsons | Sunflower | Trillium | |
---|---|---|---|---|
EBSCO Primary development platform | Okapi | Okapi | Eureka | Eureka |
EBSCO Bugfixing for | Okapi and Eureka | Okapi and Eureka | Eureka | Eureka |
Community Bugfixing for | Okapi and Eureka | Okapi and Eureka | Eureka | Eureka |
Community Testing (bugfest) - EBSCO hosted | Okapi and Eureka | Okapi and Eureka | Eureka | Eureka |
Community Testing (bugfest) - Community | X | X | X | X |
Support for CSPs (critical issues only) | Quesnelia/Okapi Poppy/Okapi | Ramsons/Okapi Quesnelia/Okapi | Sunflower/Eureka Ramsons/Okapi | Trillium/Eureka Sunflower/Eureka |
Option | Running Sunflower modules Ramsons and Okapi support |
Next steps for councils
Technical council
Determine how to approve the large number of modules in time for Sunflower, or agree to approve as a package: https://folio-org.atlassian.net/wiki/spaces/TC/pages/518946885/0010-eureka#New-Components