340
edits
OstDB DEV: Difference between revisions
Jump to navigation
Jump to search
→Approach 1
m (→Approach 1) |
|||
| Line 56: | Line 56: | ||
* multipilcities of released-by relation between audio file and audio group are wrong (switched) in diagram | * multipilcities of released-by relation between audio file and audio group are wrong (switched) in diagram | ||
* anime<->song relation with attributes (type: OP/ED, first-ep: eid) | * anime<->song relation with attributes (type: OP/ED, first-ep: eid) | ||
===Generic Person/Company Tables=== | |||
As the CharDB, OstDB, MangaDB and AniDB's producers all tend to include data about indivuduals or companies it would be a good idea to extract the generic data for individuals and companies into two separate tables which are then used by all other parts. | |||
I.e. instead of having all the data inside the producer table, it would only include those datafields which are producer specific and would refer to a person or company table for the general data. | |||
The question is, which fields can be considered generic (and should thus be listed in the person/comapny table) and which fields are specific. | |||
And also which relations should be possible between entries. | |||
* person<=>company relations? (works/ed for?) | |||
* company<=>company relations? | |||
An multiplicities, i.e. has each producer only one person/company related to it, or multiple ones? | |||
====Generic Fields - Person==== | |||
* name | |||
* shortname | |||
* synonyms | |||
* image | |||
* url | |||
* birth date | |||
* day of death | |||
* gender | |||
* description | |||
* ... | |||
====Generic Fields - Company==== | |||
* name | |||
* shortname | |||
* synonyms | |||
* image | |||
* url | |||
* founded | |||
* closed down | |||
* description | |||
* ... | |||