Details
Assignee
UnassignedUnassignedReporter
Mike TaylorMike TaylorLabels
Priority
P4Development Team
Core: PlatformTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Unassigned
UnassignedReporter
Mike Taylor
Mike TaylorLabels
Priority
Development Team
Core: Platform
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created March 27, 2018 at 2:52 PM
Updated July 7, 2023 at 1:19 PM
As we start to build modules not based on RMB, such as mod-graphql – and as we start to see third-party modules arriving in potentially any language using any tools – we need to tersely and explicitly summarise what requirements a piece of software must meet to function as a FOLIO module.
The document that summarises this should probably be split into three sections:
1. What you need to do to run under Okapi.
2. What you need to do to run on Index Data/EBSCO CI.
3. Best practice (health-check WSAPIs, etc.)
(We are starting to think about a similar document for Stripes modules, too – see STCOR-180. This is good, healthy stuff: the kind of thing that fertilizes a diverse ecosystem.)