MangaDB DEV: Difference between revisions

← Older edit

MangaDB DEV (view source)

Revision as of 15:49, 2 January 2012

391 bytes removed , 2 January 2012

m

no edit summary

Der Idiot

Bureaucrats, Interface administrators, Administrators

3,699

edits

@@ Line 5: / Line 5: @@
 For other areas of active development on AniDB, check: [[Development]].
-Directly related: [[Generic PersonCompany DEV]]
 =Vision=
@@ Line 17: / Line 15: @@
 * Manga
 * Doujin
+* Magazines
 ==Releaseforms==
@@ Line 52: / Line 51: @@
 ==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.). Repackaging and rereleasing are further reasons.
+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.
-Hence an edition may or may not reuse existing content. It's potentially wanted to "transfer" as much data as possible with this. (where content = credits, release dates) While i say transfer what really is wanted is not duplication, but adressing the same content from multiple angles to lessen maintenance.
+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==
@@ Line 63: / Line 64: @@
 * 編集, 編集人, 編集者 - Editing
 * 編集協力 - Editing Assistance
-* カパーイラスト - Cover Illustration
+* カパーイラスト, COVER ILLUSTRATION - Cover Illustration
 * カパー&ロゴ - Cover and Logo
 * 本文デザイン - Text Design
@@ Line 71: / Line 72: @@
 * 製本 - book making (binding, publishing)
 * ILLUSTRATION, SPECIAL ILLUSTRATION - porn mag illustrations
-* COVER ILLUSTRATION - cover art (porn mags)
 Additional ones may contain assistance, colouring, illustration.
@@ Line 90: / Line 90: @@
 ==General==
 ===Manga entries===
-* basically just a name and a summary/description of the entry
-* further data can't be stored at this level
-* categories/tags would be assigned on this level
-===Editions===
 * compareable to an anime entry
 * made up of several elements (chapter, volumes, etc.)
 * picture
-===Element Edition===
+===Element Relation===
-* to make truly reuseable we need a layer between editions and elements
+* as certain blocks are content wise identical we need a mapping table between content and manga itself
-* release dates
+* contains meta data that is not content specific (dates, numbers, pics)
-* volume/chapter "number"
 * controls the order of elements (some internal number to shift content around)
 ===Elements===
-* compareable to an episode entry
+* comparable to an episode entry
+* content specific reusable elements
 * variable element which may be a volume, chapter, omake, illustration, etc.
-* needs nesting capeabilities to build a 2 level hirachy
+* needs nesting capabilities to build a 2 level hirachy
-* only volume/chapter(/omake?) ones should be addable to mylist; rest is mainly only in for credits and completeness sake
 ===Files===
@@ Line 116: / Line 110: @@
 ===Mylist===
-* as files will exist on chapter level, unbound of editions, we want to store an edition id in the data record to prevent every single edition popping up in mylist; if the user really has multiple editions he will have to add those chapter as well evne if that means "duplicating" entries the listtb records
+* 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.
-===Credits/Character===
+===Character===
-* credits will be set on element level; we can't add a manga or edition id in this for easy access as the data wouldn't be universally useable anymore
+* as we enforce a unique content rule character can be set on element level and will hence apply for every related bit.
-* to lessen the pain of data retrieval we will use a caching table which duplicates and condenses the data
 ==Database==
-[[Image:Mangadb-dbspecs2.png]]
+[[Image:Mangadb-dbspecs3.png]]
-===Example Data===
-[http://deridiot.kawaii-shoujo.net/tmp/stuff.xls example]
-===Workflows===
-====Adding new manga====
-* the add form should contain the data for mangatb, mangaeditiontb (to create the main edition as well), resourcetb, manganametb
-=====Result=====
-* 1 mangatb entry
-* 1 or 2 manganametb entries
-* 1 mangaeditiontb entry
-* 0,1 or multiple resourcetb entries
-=====Adding new
 [[Category:Development]]