Provide local setup for Quiver to get results for data that should not be public #67
Description
The current Quiver setup is designed for running on the SUB's infrastructure in an automated manner. However, Quiver should also be usable for users on their local machine with their own workflows.
Glossary:
- CI quiver benchmarks: the quiver benchmarks setup for getting results for our GT. this is then displayed over at https://ocr-d.de/quiver-frontend.
- local quiver benchmarks: the setup for locally running workflows on either our or custom GT. the results are displayed on a local quiver front end.
- front end: the front end version used at https://ocr-d.de/quiver-frontend
- local front end: a local version of the front end, used to display results of local quiver runs
Steps to achieve this:
- outsource the core functionality of Quiver Benchmarks so it can be used by the "CI scenario" as well as the "local scenario"
- create separate repos for CI and local setup
- package front end to be used in local Docker compose setup
- create local quiver benchmarks that sends its data to local data base
- adjust CI quiver benchmarks to use core functionality
- create local MongoDB + API where the front end can request data
- adjust local front end to new local API
- write extensive documentation about local usage