As a user, when browsing Katsu I expect it to be populated with data. Since DyCons is currently being developed as a prototype, the data in Katsu should be artificial, so that anybody interested in building DyCons and trying it out can browse the data without violating privacy.
Acceptance Criteria
[x] The process for running Katsu and populating it with data is mostly automatic, although it can involve a couple manual step. For example, it's OK for the data-populating step to be a script that is run from the command line (after spinning up Katsu with docker-compose up.)
[x] The process for running Katsu and populating it with data is documented in the compose repo README.
[x] The data used is artificial and approved for public viewing.
[x] Populating Katsu with data should not take a long time, to keep the process of testing relatively quick. If it takes longer than ~90 seconds, the size of the dataset should be reduced. Talk to @katpavlova about how to reduce the dataset before doing so.
sh-ura
commented
3 years ago
As a user, when browsing Katsu I expect it to be populated with data. Since DyCons is currently being developed as a prototype, the data in Katsu should be artificial, so that anybody interested in building DyCons and trying it out can browse the data without violating privacy.
Acceptance Criteria
docker-compose up.)composerepo README.Additional resources
It seems like CanDIG already has access to some publicly-viewable Katsu data here: https://candigv2.calculquebec.ca/
Dependencies
The testing and completion of #9 depends upon the completion of this ticket.