Add Project Runeberg as trusted book provider #9983
Labels
Lead: @cdrini
Issues overseen by Drini (Staff: Team Lead & Solr, Library Explorer, i18n) [managed]
Needs: Breakdown
This big issue needs a checklist or subissues to describe a breakdown of work. [managed]
Needs: Triage
This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed]
Priority: 3
Issues that we can consider at our leisure. [managed]
Type: Feature Request
Issue describes a feature or enhancement we'd like to implement. [managed]
Proposal
Project Runeberg is a project similar to Project Gutenberg, but with a focus on Nordic/Scandinavian authors and literature.
It would be great to have Runeberg used as a trusted book provider, similar to how Gutenberg is currently used.
Justification
Problem:
We want more web books in Open Library, and we also want more diversified, non-English literature. Project Runeberg provides us both! Similar to Project Gutenberg, Runeberg takes literature that has fallen into the public domain, gets scans of them, OCRs them, and then has humans do proof‐reading of the books. When the books have been prepared, they are published to the public, in the public domain.
Impact:
Idk. More books and more non-English literature in OL? :)
Research:
We already support Project Gutenberg. This should be pretty similar feature-wise.
Breakdown
Requirements Checklist
Related files
openlibrary/book_providers.py
openlibrary/macros/RawQueryCarousel.html
openlibrary/plugins/worksearch/code.py
openlibrary/plugins/worksearch/schemes/works.py
openlibrary/plugins/worksearch/tests/test_worksearch.py
openlibrary/templates/book_providers/runeberg_download_options.html
(needs adding)openlibrary/templates/book_providers/runeberg_read_button.html
(needs adding)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: