[CGI] Notifications if a group drops an anime [DONE]

old granted and denied feature requests

Moderator: AniDB

Locked
exp
Site Admin
Posts: 2438
Joined: Tue Oct 01, 2002 9:42 pm
Location: Nowhere

[CGI] Notifications if a group drops an anime [DONE]

Post by exp »

*note to self and for open discussion*

Request:
A way to tell anidb that a certain group has dropped an anime and will therefore not release any more files for it.
This information could then be used for all kinds of things.
i.e.
- warn ppl if they try to download files for that anime from that group.
- notify all ppl who are currently collecting only files from that group.
- ...

BYe!
EXP
kamenoko
Posts: 26
Joined: Mon Jan 20, 2003 2:06 pm
Location: Neither here nor there
Contact:

Post by kamenoko »

It makes sense. You'd get to make a cute little icon for it as well. Maybe you'll want to implement a "Sort episodes by Group" feature before that though. :lol:

In all seriousness it should probably be a mod only option, that goes without saying. Just an extra option on the page to mark a group doing the series as "dropped". Where it will put a notation such as "<group> has stopped releasing this anime." in big, bold, neon green letters at the bottom of the page so the newbs will read it ;). You could probably make it a creq field as well, since we're all so lazy. :D
Elberet
Posts: 778
Joined: Sat Jul 19, 2003 8:14 pm

Post by Elberet »

I wonder where and how you intend to store that flag. It sounds as if there'd have to be a relation between animes and fansub groups for this to work. Well, maybe that's not the worst idea...
  • Make a new table that relates groups to animes.
  • Relations are created automatically when a file is added.
  • Each relation has a state value. By default, the state is "ongoing".
  • When a group has files for every episode in the anime, the state is automatically changed to "complete".
  • If a group does not release a new episode for 60 days, the state is auto-changed to "stalled". Once a new episode becomes available, it's reset to "ongoing", still automatically.
  • Setting the state to "dropped" requires a CREQ, however from what I read here about the CREQ system, it sounds as if you'd have to modify it, since the number of columns per anime CREQ would no longer be fixed.
  • Changing the group state should be allowed to moderators and via CREQs only. Neither the owner of the anime record nor the people who own the files or episodes do necessarily have first-hand information on the status of the groups subbing the anime.
Iceman[grrrr]
Posts: 312
Joined: Sat Aug 02, 2003 3:22 am
Location: Québec, Canada

Post by Iceman[grrrr] »

Or add "maintainers" for groups...

I add AnimeCo series and am well aware of what we are dropping and what we are not! ;)

It could be a simple field (uid) inside the fansub group<->series table
Elberet
Posts: 778
Joined: Sat Jul 19, 2003 8:14 pm

Post by Elberet »

Then you'd be limited to a single maintainer per group, tho. You'd need another table to build a uid <--> group relation.
wahaha
AniDB Staff
Posts: 1497
Joined: Sun Nov 17, 2002 3:33 pm

Post by wahaha »

Semi-OT:
Elberet wrote:Then you'd be limited to a single maintainer per group, tho. You'd need another table to build a uid <--> group relation.
Which would of course come in handy when (ever) wanting to grant editing-rights on a per-group-basis ;)
exp
Site Admin
Posts: 2438
Joined: Tue Oct 01, 2002 9:42 pm
Location: Nowhere

Post by exp »

first version is online.

for now only mods can mark an anime as dropped by a group and there are probably still some bugs in it.

for all those who don't like it there is a profile option to turn it off.

BYe!
EXP
Iceman[grrrr]
Posts: 312
Joined: Sat Aug 02, 2003 3:22 am
Location: Québec, Canada

Post by Iceman[grrrr] »

exp wrote:first version is online.

for now ...
so you're thinking about implementing group maintainers ? great then!

oh, on your next update... cosmetic change: make the "Group Info:" take the whole first column like "MyList:"
bbaab
Posts: 78
Joined: Thu Nov 20, 2003 2:13 pm

Post by bbaab »

exp wrote:first version is online.
Cooooool!

Two ideas for additional columns:

1. Languages of the sub/dub the group produces.

2. CRC-check status (how many of the episodes are in "checked" state)
Elberet
Posts: 778
Joined: Sat Jul 19, 2003 8:14 pm

Post by Elberet »

Iceman[grrrr] wrote:oh, on your next update... cosmetic change: make the "Group Info:" take the whole first column like "MyList:"
Ah, that's one of my favorites... Because you have to know the number of table rows before drawing the cell with the rowspan attribute. :mrgreen:
Gambit
AniDB Staff
Posts: 555
Joined: Sun Oct 06, 2002 11:21 am

Post by Gambit »

hmm .. interesting idea. I might want to take a look at it someday :)
Iceman[grrrr]
Posts: 312
Joined: Sat Aug 02, 2003 3:22 am
Location: Québec, Canada

Post by Iceman[grrrr] »

Elberet wrote:
Iceman[grrrr] wrote:oh, on your next update... cosmetic change: make the "Group Info:" take the whole first column like "MyList:"
Ah, that's one of my favorites... Because you have to know the number of table rows before drawing the cell with the rowspan attribute. :mrgreen:
Exactly but the query to the db should have already been done if the page is being printed, ne ?
Elberet
Posts: 778
Joined: Sat Jul 19, 2003 8:14 pm

Post by Elberet »

Yes, but to me it looks like the result from the database is being post-processed in Perl. A couple ifs here, a date calculation there... In the end, you have to read the result from the database into a list, count that and then do the drawing in one go, completely separeted from the logic part.

Of course, if you're a good (read "not evil", not "skilled") programmer, you'll separate querying, processing and output from the very beginning. It's cases like this where strict OOP pays off, and that's why I like them so much. ;)
exp
Site Admin
Posts: 2438
Joined: Tue Oct 01, 2002 9:42 pm
Location: Nowhere

Post by exp »

well,

perl is not object oriented :P
and the anidb source has become a quite ugly bunch of code lines, after all it has seen more than two years of constant changes.
so some queries are in deed handled before the acutaly printing of the output, however some are not.
i even rewrote most parts of anidb at some time and changed most queries to print the results directly on the file bc pageload times were to slow on the aruba host otherwise.
the first version of anidb even used a template system and had something which could be called a structure, all of that has been removed out of performance issues and lazyness.

so to sum it up, that rowspan request can't be done without extra chaching and I don't see a need for it. it would look pretty ugly.

BYe!
EXP
Locked