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

Design database/datastore approach #3

Open
kstapelfeldt opened this issue Sep 11, 2020 · 4 comments
Open

Design database/datastore approach #3

kstapelfeldt opened this issue Sep 11, 2020 · 4 comments
Assignees

Comments

@kstapelfeldt
Copy link
Member

Based on output here: https://docs.google.com/spreadsheets/d/11S4Hc4ky50lClzfn74f8B3MqqHB9_YRTEvEjBkOX634/edit#gid=649117397

Do we need a postgres database? Or keypair store? Something else?

Produce schema if necessary

We need a pretty picture, please :) - embed in an .md

@kstapelfeldt
Copy link
Member Author

kstapelfeldt commented Sep 15, 2020

Schema change: There is a one 2 many relationship between source and RSS feed as one domain name source can have multiple RSS feeds. Please update ticket with link to diagram if location changes. Unsure yet whether or not to use keypair or full database and will decide this later.

@kstapelfeldt kstapelfeldt transferred this issue from UTMediaCAT/Voyage Sep 21, 2020
@jacqueline-chan
Copy link
Contributor

@kstapelfeldt
Copy link
Member Author

We are missing authors. To be updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants