[CGI] Notifications if a group drops an anime [DONE]
Moderator: AniDB
[CGI] Notifications if a group drops an anime [DONE]
*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
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
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.
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. 

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


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.
-
- Posts: 312
- Joined: Sat Aug 02, 2003 3:22 am
- Location: Québec, Canada
-
- Posts: 312
- Joined: Sat Aug 02, 2003 3:22 am
- Location: Québec, Canada
-
- Posts: 312
- Joined: Sat Aug 02, 2003 3:22 am
- Location: Québec, Canada
Exactly but the query to the db should have already been done if the page is being printed, ne ?Elberet wrote: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.Iceman[grrrr] wrote:oh, on your next update... cosmetic change: make the "Group Info:" take the whole first column like "MyList:"
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.
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.

well,
perl is not object oriented
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
perl is not object oriented

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