Map out existing relational database to JSON-centric model
Trott opened this issue · comments
Only minimal fields for now. Add new fields only as their needed.
Take this opportunity to rename some stuff in the relational database:
- album => source
- artist
- individual
- track
Do we want relation tables preserved? Or do we want to embed objects inside source? Or repeat it for each track?
Include aliases for each of the above?
Maybe source needs a type? Some defined values, one for "compact disc" and one for "LP" and one for "internet" and so on?
Look at what discogs.com does.
And maybe look at some of these too: https://github.com/datasets
Used releases instead of sources to more closely map to discogs.org API. We can always change it. Uh, until 1.0 anyway.