Suggestions on the database schema

[nileshtrivedi]

Because this problem space is so big, I'm hoping to see multiple apps and experiences built on top of the same shared dataset to innovate more efficiently. This is why it becomes critical to align on the dataset schema - even if it comes from different sources and formats (nested JSON, remote API).

Current schema is described here. Would like to hear suggestions on how this can be improved while keeping the complexity under control.

I heard some really good suggestions from @widged

• Use "novice" instead of "beginner" as difficulty level
• In some fields, useful knowledge changes very fast. Items should have data about recency and users should be able to filter by it.
• topic.image_url could be a short protocol reference like unsplash:photo-1530856021941-02c71be5926f.
• Consider allowing for multiple parent topics
• Support short blurb on top of topic image
• item.rating should cover diferent aspects: pinned, relevance, salience, quality

It'd be nice to have this discussion here in public.