Simplify Trusted Book Providers integration #10251
Labels
Lead: @scottbarnes
Issues overseen by Scott (Community Imports)
Needs: Breakdown
This big issue needs a checklist or subissues to describe a breakdown of work. [managed]
Priority: 2
Important, as time permits. [managed]
Theme: Trusted Book Providers
Type: Epic
A feature or refactor that is big enough to require subissues. [managed]
Type: Feature Request
Issue describes a feature or enhancement we'd like to implement. [managed]
Milestone
Proposal
A simplified Trusted Book Providers integration would mean that providers are added by adding the equivalent of json or yml entries to a registry, as opposed to manually adding new html files and classes for new providers.
There may be cases where a new mapper class is required between the ID / naming / url schemes of a provider and Open Library, however this should hopefully become the exception rather than the norm.
Justification
We have lots of trusted book providers pending evaluation and it would be great to arrive at a point where open librarians and contributing engineers can implement these solutions (and make it more trivial to review).
If done correctly, this could potentially result in dozens of new partner platforms that we can link out to, increasing access to tens of thousands of open access books.
Breakdown
Requirements Checklist
Related files
Stakeholders
Instructions for Contributors
Please run these commands to ensure your repository is up to date before creating a new branch to work on this issue and each time after pushing code to Github, because the pre-commit bot may add commits to your PRs upstream.
The text was updated successfully, but these errors were encountered: