Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
yochannah opened this issue Sep 1, 2020 · 3 comments
Assignees
Labels
code-task This task will involve writing code of some sort - but it's okay to pick up and ask for help too! elife-sprint-2020 Issue opened as part of the 2020 eLife Sprint

Comments

@yochannah
Copy link
Collaborator

yochannah commented Sep 1, 2020

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 yochannah added code-task This task will involve writing code of some sort - but it's okay to pick up and ask for help too! elife-sprint-2020 Issue opened as part of the 2020 eLife Sprint labels Sep 1, 2020
@yochannah
Copy link
Collaborator Author

yochannah commented Sep 2, 2020

@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
Copy link
Member

JPTIZ commented Sep 2, 2020

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
Copy link
Member

JPTIZ commented Sep 3, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code-task This task will involve writing code of some sort - but it's okay to pick up and ask for help too! elife-sprint-2020 Issue opened as part of the 2020 eLife Sprint
Projects
None yet
Development

No branches or pull requests

2 participants