Collections [DENIED]

old granted and denied feature requests

Moderator: AniDB

Locked
TARD

Collections [DENIED]

Post by TARD »

Collections, like over at fileheavens forums, or like over at audiogalaxy.com
most of the information is in the anidb already, like the images of the animes and the animes themselves.
just need to connect them to eachother with a link of some sort, like a person or a theme or anything. :)
I know nothing about anidb programming, but it doesnt sound all that hard to make..
exp
Site Admin
Posts: 2438
Joined: Tue Oct 01, 2002 9:42 pm
Location: Nowhere

Post by exp »

sorry but i don't really understand what you're requesting.

BYe!
EXP
Elberet
Posts: 778
Joined: Sat Jul 19, 2003 8:14 pm

Post by Elberet »

Probably a feauture to group different animes together into "packs", such as "The Bit Romance Pack (tm)", containing all kinds of love-story animes.

But...
a) we have genres for that.
b) if all users make their own packs, we'll have a huge mess.
c) if only certain people / moderators can create packs, it would defeat AniDB's purpose as a public anime database.
yidaki

Post by yidaki »

i was trying to be as general as possible, since a collection can consist of many things.
but i personally would like to do a "theme" on Go Nagai, the creator of mecha's and controversial animes.
like, i put up an image of go nagai, write some peronal facts on him, like his birthdate and where he grew up and what company he worked mainly with, then i would list all the animes that he has made, with links to their specific pages in anidb, and maybe a small thumbnail-image for every anime or just a resized image of the image presented with the anime.
since most of the things are already in the anidb, the work would only be to put it all into tables.

like over at audiogalaxy: http://www.audiogalaxy.com/pages/review ... _id=110586
or like in fileheaven's forums: http://www.fileheaven.org/forum/viewtopic.php?t=5824

it wouldnt be any more messy then animes being added to anidb.
a small image, a space for information, a title, and the list of animes in anidb which are related to the collection (which should be a requirement) anyone should be able to add an anime to a collection, just like episodes to an anime, could be useful if someone doesnt know this person did that anime aswell.

it would be awesome, you just browse a list of different collections, maybe categorized by topic(like Creator, or Designer, or just Theme) and you get to see all the animes created directly or indirectly by this person.
you cant do that with genres.
its just another way of looking at the same information, sorting by creator or character-designer or seiyuu or whatever the collection is based on...
Elberet
Posts: 778
Joined: Sat Jul 19, 2003 8:14 pm

Post by Elberet »

Ah, so to better describe what you want:
You're suggesting that AniDB should cross-reference animes by producer(s), director(s), designer(s) and voice actor(s) (to begin with). Cross-references are represented as collections: For each anime, a list of collections this anime is part of is shown, and available collections can be browsed in their own list.

Is that about it?
Guest

Post by Guest »

Elberet wrote:Ah, so to better describe what you want:
You're suggesting that AniDB should cross-reference animes by producer(s), director(s), designer(s) and voice actor(s) (to begin with). Cross-references are represented as collections: For each anime, a list of collections this anime is part of is shown, and available collections can be browsed in their own list.

Is that about it?
no, its the other way around. :)
not links from the anime to different collections.
you have a collection, of links to animes in anidb, as easy as that.
a list, with animes.
its nothing big im suggesting :P

ofcourse you should be able to browse the collections aswell, but thats just like browsing groups or animes, nothing big there either.

here's a rough image of what i want: http://w1.605.telia.com/~u60516417/go%2 ... ection.jpg
there's lots of errors in it, but i only made it in 5 miutes so please bare with me. :)
Elberet
Posts: 778
Joined: Sat Jul 19, 2003 8:14 pm

Post by Elberet »

Ok, let's get techy... :P

PostgresSQL is a relational database. That means that there's a table 'animes' that describes each anime. A second table would contain the list of collections. In order to link the two, you need a third link-table that contains bits of information, telling you that "anime 183 belongs into collection 17". You can get a list of all animes-in-a-collection by telling Postgres to find all entries in the link-table where the collection part is equal to a certain collection's id number. It works just as easily the other way around, tho. You can ask Postgres to find all rows where the anime part is equal to a certain id number, and the resulting list tells you all the collections that anime is in.

In other words:
My description and yours are essentially the same. :P
Iceman[grrrr]
Posts: 312
Joined: Sat Aug 02, 2003 3:22 am
Location: Québec, Canada

Post by Iceman[grrrr] »

He wants it like in animenfo: http://www.animenfo.com/person,51,vdfvq ... _yoko.html

a table persons with an other table to have the links between the 2
Elberet
Posts: 778
Joined: Sat Jul 19, 2003 8:14 pm

Post by Elberet »

Iceman[grrrr] wrote:a table persons with an other table to have the links between the 2
Yeah. Those are "crossreferences", no? :P
Iceman[grrrr]
Posts: 312
Joined: Sat Aug 02, 2003 3:22 am
Location: Québec, Canada

Post by Iceman[grrrr] »

yup, just restating it! ;)
exp
Site Admin
Posts: 2438
Joined: Tue Oct 01, 2002 9:42 pm
Location: Nowhere

Post by exp »

hm,

this might be interesting.
could be used for stuff like viewing-order-guides and other stuff too.

BYe!
EXP
Elberet
Posts: 778
Joined: Sat Jul 19, 2003 8:14 pm

Post by Elberet »

Hmmm, here's a *very* generic approach that is most likely too difficult to implement. I'll post it nevertheless. :P


Remove all the auxialary information from the anime table so that only title, type, number of episodes, year and whatever status flags you have/need are left.

Create a new table that lists allowed auxialary info-types (auxinfo), such as "Producer", "URL", "Animenfo URL", "Image" and whatnot, with three flags: singletons / multiple, primary / secondary, listed / unlisted.

Create a new table that contains generic information for all auxinfo bits, e.g. the auxinfo ID, associated anime ID (for singletons, -1 for multiples), title, text, URL and storage class.

Create a new table auxinfo-anime-rel that implements the relation between animes and multiple-auxinfo bits.

Primary singleton auxinfo bits are the Synonyms, Shortnames, URL, Animenfo URL, Prequels and Sequels and the Image(s). These are listed on the Anime page just where they are now. Note that an anime can have multiple singleton auxinfo bits. :P

Secondary singleton auxinfo bits are listed in a separate box on the anime page. For example, the MyList box can be moved to the right of the description and these auxinfo bits are listed below that in a "Other Information" box.

Now for the real beef...

Multiple auxinfo bits are what implements the collections that were mentioned earlier. They aren't associated with an anime directly but through the relations table. Primary multiples are shown in the same area where the primary singletons are listed. Typical entries for this would be "Producer" or "Distributor". Finally, secondary multiples are shown in a third box below the primary singletons (labeled "Crossreferences").

The "Collections" are created by creating a new secondary multiple auxinfo and assigning it to a number of animes. All animes in this collection will show a link to the collection in their "Crossreferences" section, and an additional Collections list can show all available multiple auxinfos that are of an auxinfo type that is flagged as "listed".

Finally, a note on the storage class thing mentioned above: If a text field, title and URL aren't enough (title and URL are used for things like the AniDB URL or images), the storage class can tell the script to use a specific Perl package to obtain more information on how to handle that auxinfo bit. This would include the name of another table that stores extra info for auxinfo bits of that type and a hash with info about the fields of that table.


Whew, I'm done. :P
As I said, it's a very long shot and I don't expect it to implemented, but hey, you might want to keep this in mind for the 2.0 version of AniDB. :P
PetriW
AniDB Staff
Posts: 1522
Joined: Sat May 24, 2003 2:34 pm

Post by PetriW »

That's how it's implemented in AniDB O'Matic except I do it with two tables instead of 4. 8O
AOM uses SQLite though which simplifies storing data as everything is strings.
Iceman[grrrr]
Posts: 312
Joined: Sat Aug 02, 2003 3:22 am
Location: Québec, Canada

Post by Iceman[grrrr] »

exp, what is on todo in this thread ??
in topic 661, the crew for anime is [?]
Locked