MangaDB DEV: Difference between revisions
Jump to navigation
Jump to search
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]] | ||
Latest revision as of 15:49, 2 January 2012
General
this is the place to contribute ideas on a possible future addition of manga data to AniDB.
For other areas of active development on AniDB, check: Development.
Vision
Data
First thing we need to be aware of what data we would like to actually store/how the real world looks like.
Content forms we care about
- (Light) Novels
- Manga
- Doujin
- Magazines
Releaseforms
Content comes in various forms made up of different elements.
chapter only releases
used where?
- official online distribution
content elements
- chapters
volume only releases
used where?
- some novels
- doujins
content elements
- volumes which consist of basically 1 "chapter"
- "chapter"; basically 1 per book
- omake (depending on wanted granularity)
- illustrations (depending on wanted granularity)
- other 1 page content (index etc.) (depending on wanted granularity)
mixed content
used where?
- everything else
content elements
- volumes which encapsule the content into datasets
- chapters
- omake (depending on wanted granularity)
- illustrations (depending on wanted granularity)
- other 1 page content (index etc.) (depending on wanted granularity)
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.).
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
- 作者, 著者 - Author
- 発行所, 発行 - Publishing Office
- 出版社, 発行者, 発行人 - Publisher
- 発売所 - Sales Office
- 編集, 編集人, 編集者 - Editing
- 編集協力 - Editing Assistance
- カパーイラスト, COVER ILLUSTRATION - Cover Illustration
- カパー&ロゴ - Cover and Logo
- 本文デザイン - Text Design
- 印刷, 印刷所 - Printing
- 装丁, 装幀 - Binding
- 製版, 本文製版 - Text Platemaking
- 製本 - book making (binding, publishing)
- ILLUSTRATION, SPECIAL ILLUSTRATION - porn mag illustrations
Additional ones may contain assistance, colouring, illustration.
Most credits apply on volume level and for regular manga are given in a short summary towards the end of the book. Though certain types of releases may contain content which doesn't fit that rule. Especially illustrations/guest work should receive credits on chapter level. Same goes for magazine releases
Character
- Chapter appearance
Nothing more to store here.
Situation and Problems
- packs aren't standardized
- repacks and re-edits are common
Implementation
General
Manga entries
- compareable to an anime entry
- made up of several elements (chapter, volumes, etc.)
- picture
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)
Elements
- comparable to an episode entry
- content specific reusable elements
- variable element which may be a volume, chapter, omake, illustration, etc.
- needs nesting capabilities to build a 2 level hirachy
Files
- generic files with language flag and group assignment
- possible would be to assign multiple hashes to each of these generic files to a) stop the clutter problem and b) still allow for automatisation without completely depending on filename parsing
Mylist
- 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
