Generic PersonCompany DEV

From AniDB
Revision as of 19:32, 23 February 2007 by Exp (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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?
  • person<=>person relations? (married?)

And multiplicities, i.e. has each producer only one person/company related to it, or multiple ones?

Also, should names be a separate table (like anime titles) or are there only a small number of names we'd want to store per person/company?

The big picture

People1.png

  • To Fix:

...

Data Fields

Generic Fields - Person

  • name
  • shortname
  • synonyms
  • image
  • url (en)
  • url (jp)
  • url wiki (en)
  • url wiki (jp)
  • birth place
  • birth date
  • age (for cases where exact birth date is unknown)
  • day of death
  • gender
  • blood type
  • nationality
  • occupation
  • description
  • ...

Generic Fields - Company

  • name
  • shortname
  • synonyms
  • image
  • url (en)
  • url (jp)
  • date founded
  • date closed down
  • description
  • ...