Documenting ScholarSphere Integrations

[Seth Erickson (srerickson)]

There is a growing collection of tools/workflows that make use of ScholarSphere APIs. They include:

• Research Metadata Database, which uses ingest and doi APIs
• oats uses ingest and doi APIs
• Curation Tracking GH Action: uses Blacklight json endpoint and GraphQL endpoint.

On the external side:

• Unpaywall uses the OAI-PMH endpoint.

What's the best way to document/test these various integrations to reduce the chance of breaking changes?