Generic PersonCompany DEV

From AniDB
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?

Is mangaka sufficently different from producers? Or should mangaka simply be stored/handled like producers?

The concept of pseudonyms is still very unclear, what is the multiplicity? And are they also related to producers? Or persons? Also how are matching pseudonyms (they're not unique, are they?) handled?

The big picture

People1.png

  • To Fix:

...

Data Fields

Generic Fields

Generic Fields - Person

  • image
  • url (en)
  • url (jp)
  • url wiki (en)
  • url wiki (jp)
  • birth place
  • birth date
  • death date
  • gender
  • blood type
  • nationality
  • place of residence
  • description (extra data goes here)

Generic Fields - PersonTitle

  • title - some title, like: phd, bsc, etc
  • [name] - this is LASTNAME firstname for oriental names and firstname LASTNAME for western names
  • firstname - also know as Personal names
  • lastname - also know as Family name
  • lang - language of title
  • type - type of title
    • 1 - Main title
    • 2 - Alias
    • 3 - Maiden name
    • 4 - Nickname
  • verified

Generic Fields - Company

  • image
  • type - type of company
    • 1 - Company
    • 2 - Organization
  • url (en)
  • url (jp)
  • wiki (en)
  • wiki (jp)
  • date founded
  • date closed down
  • description - other stuff goes here

Generic Fields - CompanyTitle

  • name - name of the company
  • lang - language of title
  • type - type of title
    • 1 - Main title
    • 2 - Synonyms
    • 3 - Short
  • verified

Generic Fields - Collaboration

  • type - collaboration type
    • 1 - joint work
    • 2 - .. ?
  • url (en)
  • url (jp)
  • wiki (en)
  • wiki (jp)
  • start date
  • end date
  • description - other stuff goes here

Generic Fields - CollaborationEntities

  • type - type of entity
    • 1 - company
    • 2 - person
  • relid - entity id
  • titleid - titles used by the entity

Specializations

Producer

  • start date - if different from underlying entity
  • end date - if different from underlying entity
  • description - producer specific information
  • [ratings&co] - not implemented in the ui

Seiyuu

Artist

Mangaka

System

This details a bit of what is done and what we are aiming at

Producer

One can make a producer either from a Person, a Company entry or a Collaboration entry. One chooses from the related entry which names should the producer be known as.