MangaDB DEV: Difference between revisions
mNo edit summary |
mNo edit summary |
||
Line 4: | Line 4: | ||
this is the place to contribute ideas on a possible future addition of manga data to AniDB. | 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]] | For other areas of active development on AniDB, check: [[Development]]. | ||
Directly related: [[Generic PersonCompany DEV]] | Directly related: [[Generic PersonCompany DEV]] | ||
Line 25: | Line 25: | ||
==General== | ==General== | ||
===Mangaentries=== | ===Mangaentries=== | ||
*like | *like anime entries at AniDB | ||
*description | *description | ||
*genres/categories | *genres/categories |
Revision as of 16:19, 27 April 2009
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.
Directly related: Generic PersonCompany DEV
Vision
Data
What are the things we should be able to store/provide?
... list all entities and their attributes here ...
Situation and Problems
- packs aren't standardized
- repacks and re-edits are common
Hence because of that adding hashes or automating the add via those is somewhat impossible. The only way to do this would be if we break it down to the page level which is somewhat silly. Furthermore as viewer are capable of showing the content without extracting many people don't decompress the packs. Because of that going down to that level is pointless.
Implementation
General
Mangaentries
- like anime entries at AniDB
- description
- genres/categories
- producer
- picture
- colour/greyscale/B&W/mixed
Volume level
- is identical to the episode entries of AniDB
- data: volume name, volume number, release date
Chapter level
- is somewhat identical to the episode entries of AniDB
- a range of chapters builds a volume
- data: chapter name, chapter number (release date)
File level
- slightly identical to the file entries of AniDB
- only generic files
- generic files can have language and a group
- more than 1 generic file per chapter! basically every language + group combo creates a new file
- no size
- no hash
Database
Approach 1
Approach 2
mangatb
Fields go here, please specify types and default values
Automation
A bit of automation could get done with parsing the filename, but most adding would be manual labour, which is inevitable considering we store no hashes and there is no real way to do this with them.
It's essential to have mass-file-add tools for this. This includes mass-add to AniDB and mass-add to MyList.