Define database schema (migrate from google form) - your choice of DB backend.

[yochannah]

Currently we have a google form to collect journal-policy related data. We need to make this more robust! See the current fields we collect here: https://docs.google.com/forms/d/e/1FAIpQLScckKkSwH1nW22G8u0_GMRKk1KAV7SQGxaRsH6ysLecS9EHFQ/viewform?usp=sf_link - we may want to add other fields based on user stories / user interviews.

Paid hosting can be provided, but whatever stack we choose should be reasonable open source, please :) :)

This issue is part of the 2020 eLife Innovation Sprint. For more info about this project and the sprint, or to get help, please see the Code Is Science eLife Sprint Plan

[yochannah]

@JPTIZ is working on defining a possible database schema for this. We're aware that some of the metrics aren't clearly defined and/or may change, but making a start with the journal table for the DB seems like it should be possible.

[JPTIZ]

I've made this sample DB scheme mockup adding some annotations.

I'm currently not thinking about "caching" analysis results (i.e. making the DB only consider policies and general characterstics, but not saving any analysis such as "this is well enforced" or not - leaving this part to front-end for now).

[JPTIZ]

Here is a small DB update with Keywords for journals as well.