CameronRushton / anime-anthology

0 stars 0 forks source link

Create initial database entities #2

Closed CameronRushton closed 4 years ago

CameronRushton commented 4 years ago

Currently, our database has an Anime entity with an ID. The only thing we're going to store is data that can't be stored or is not already provided by the anilist API. Since we need to remember not to accidentally build an anime list site, perhaps we can save relations to other anime. Saving the IDs from the anilist API should be OK. If we're in the business of recommending anime using a tier structure or a tree, we could have fields in our anime entity such as: level: Integer relatedWatchBefore: Array relatedWatchAfter: Array

maybe simply just 'related: Array'

We'll have to research if some of these fields be added to their graphQL API or if we need to maintain these ourselves in our own DB, which would mean we'll have to store every anime with an ID.

CameronRushton commented 4 years ago

PR #4 implements the initial pieces of this, but there's still a long way to go. I'll close this for now.