Watch out for his w00d jokes :P
UserPage on AniDB.
MangaDB concept
Hierarchy:
- Magazine would be the root in theory; on the interface, there wouldn't be much of a difference between Magazine and Manga entries. Since they would be on separate pages.
- Books and/or Volumes don't need to be present.
- Manga with only a chapter under it is what you'd call a one-shot manga (yomikiri) or a doujin.
- Manga with chapters under it is a commercial porn manga (not magazine) or a doujin.
- Chapters can be linked to and displayed under Issues and Volumes or Issues and Manga. Can't be linked under Manga and Volumes at the same time.
- Different editions of Books and/or Volumes would be added as separate entries under the manga entry.
Still needs to be thought of
- Group integration to chapters
- Interface
- http://saber.kawaii-shoujo.net/~pelican/requested.txt
Group integration
You assign chapters to a group, not groups to a chapter like it is with group-file relations. There will not be any files, not even generic. When assigning chapters to a group, you given them also the language, which should be the only property added to it I guess. Chapters are treated as generic files that can be added to your mylist with the possibility to add properties to them. Properties include adding a group if there are present (can also add chapters via group), language in case the manga was released in another country, chapter states (on hdd, on optical media, deleted, on paper).
Interface
Issue/vol (in ascii art):
name
<-prev- [drop] -next->
pic info
description
groups (displaying how many chapters of this volume a group has released)
chapter list
Magazine/manga (in ascii art):
name
pic info
description
categories
tags
discussions
groups|cast|recommendations|reviews|clubs
(books)
(volumes)/issues
chapter list