Uploaded image for project: 'Okapi'
  1. Okapi
  2. OKAPI-564

Tersely document requirements for an Okapi module

    XMLWordPrintable

Details

    • Task
    • Status: Open (View Workflow)
    • P4
    • Resolution: Unresolved
    • None
    • None
    • Core: Platform

    Description

      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.)

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                mike Mike Taylor
                Votes:
                1 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                  Created:
                  Updated:

                  Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 2 hours
                    2h

                    TestRail: Runs

                      TestRail: Cases