Generic PersonCompany DEV: Difference between revisions

Line 3: Line 3:
As the [[CharDB_DEV|CharDB]], [[OstDB_DEV|OstDB]], [[MangaDB_DEV|MangaDB]] and AniDB's producers all tend to include data about individuals 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.
As the [[CharDB_DEV|CharDB]], [[OstDB_DEV|OstDB]], [[MangaDB_DEV|MangaDB]] and AniDB's producers all tend to include data about individuals 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 data fields which are producer specific and would refer to a person or company table for the general data.
* I.e. instead of having all the data inside the producer table, it would only include those data fields 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/company table) and which fields are specific.
* The question is, which fields can be considered generic (and should thus be listed in the person/company table) and which fields are specific.


And also which relations should be possible between entries.
* And also which relations should be possible between entries.
* person<=>company relations? (works/ed for?)
** person<=>company relations? (works/ed for?)
* company<=>company relations?
** company<=>company relations?
* person<=>person relations? (married?)
** person<=>person relations? (married?)


<s>And multiplicities, i.e. has each producer only one person/company related to it, or multiple ones?</s> - ''Each producer as only one entity assigned to it. Although one of those entities is Collaboration which can hold multiple companies and/or persons.''
* <s>And multiplicities, i.e. has each producer only one person/company related to it, or multiple ones?</s> - ''Each producer as only one entity assigned to it. Although one of those entities is Collaboration which can hold multiple companies and/or persons.''


<s>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?</s> - ''Names have their own table for every Entity that has titles.''
* <s>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?</s> - ''Names have their own table for every Entity that has titles.''


Is mangaka sufficiently different from producers? Or should mangaka simply be stored/handled like producers?
* Is mangaka sufficiently 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?
* 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?
* Also how are matching pseudonyms (they're not unique, are they?) handled?
 
* Looking at [[Generic_PersonCompany_DEV#Producer|Producer]], [[Generic_PersonCompany_DEV#Artist|Artist]], [[Generic_PersonCompany_DEV#Mangaka|Mangaka]] and [[Generic_PersonCompany_DEV#Seiyuu|Seiyuu]] we see that they are very similar the only thing changing are the names of the generic fields (like start date), so a question is should we either:
*# have multiple modules for each specialization or should we keep it only under one module and differentiate with something like show=addentity&type=person[&edit=1]
*# keep using the current way that is xvcl everything and make several modules for each specialization?


=The big picture=
=The big picture=
347

edits

MediaWiki spam blocked by CleanTalk.
MediaWiki spam blocked by CleanTalk.