3,699
edits
mNo edit summary |
|||
(2 intermediate revisions by the same user not shown) | |||
Line 5: | Line 5: | ||
For other areas of active development on AniDB, check: [[Development]]. | For other areas of active development on AniDB, check: [[Development]]. | ||
=Vision= | =Vision= | ||
Line 53: | Line 51: | ||
==Editions== | ==Editions== | ||
To make things worse the same content is released in multiple editions. Multiple editions usually share the same content (usually chapters) but might add different bonus content (illustrations, omake etc.). | To make things worse the same content is released in multiple editions. Multiple editions usually share the same content (usually chapters) but might add different bonus content (illustrations, omake etc.). | ||
We will have to ignore this idea in favor of simplicity. it's not feasible to completely mirror reality. | |||
If an edition is worth it it should be added as a new manga entry. While this might seem entirely stupid it's the only feasible way to do this. | |||
==Credits== | ==Credits== | ||
Line 90: | Line 90: | ||
==General== | ==General== | ||
===Manga entries=== | ===Manga entries=== | ||
* compareable to an anime entry | * compareable to an anime entry | ||
* made up of several elements (chapter, volumes, etc.) | * made up of several elements (chapter, volumes, etc.) | ||
* picture | * picture | ||
===Element | ===Element Relation=== | ||
* | * as certain blocks are content wise identical we need a mapping table between content and manga itself | ||
* | * contains meta data that is not content specific (dates, numbers, pics) | ||
* controls the order of elements (some internal number to shift content around) | * controls the order of elements (some internal number to shift content around) | ||
===Elements=== | ===Elements=== | ||
* | * comparable to an episode entry | ||
* content specific reusable elements | |||
* variable element which may be a volume, chapter, omake, illustration, etc. | * variable element which may be a volume, chapter, omake, illustration, etc. | ||
* needs nesting | * needs nesting capabilities to build a 2 level hirachy | ||
===Files=== | ===Files=== | ||
Line 116: | Line 110: | ||
===Mylist=== | ===Mylist=== | ||
* as files will exist on | * as files will exist on element (content) level, unbound of direct relation to manga, we want to store a mangaid in the data record to prevent every single appearance of the file/content in manga popping up in mylist; if the user really has multiple files of the same content in different manga he will have to add those files as well even if that means "duplicating" entries in listtb records. a unique key would hence need to be "uid, fid, mangaid" and not just "uid, fid" | ||
===Credits=== | |||
* while the content of a certain element might be identical the credits for said element might differ and hence we can't apply it on element level, but have to make it manga specific. this will mainly reflect on the publishing level. considering credits for manga are quite short duplicating the records shouldn't be too much work. | |||
=== | ===Character=== | ||
* | * as we enforce a unique content rule character can be set on element level and will hence apply for every related bit. | ||
==Database== | ==Database== | ||
[[Image:Mangadb- | [[Image:Mangadb-dbspecs3.png]] | ||
[[Category:Development]] | [[Category:Development]] |