Groupentries:Status: Difference between revisions

From AniDB
Jump to navigation Jump to search
m (→‎Problems: some fixed)
Line 50: Line 50:
*<b>eternally stalled rels caused by groups which release eps way ahead of them</b><br>(example: Conan)<br>A group releases an ep way ahead of the eps they really sub which causes AniDB to wait for a "higher" ep<br> (maybe fixed once the new animepage is in place)
*<b>eternally stalled rels caused by groups which release eps way ahead of them</b><br>(example: Conan)<br>A group releases an ep way ahead of the eps they really sub which causes AniDB to wait for a "higher" ep<br> (maybe fixed once the new animepage is in place)


*<b>eternally stalled rels caused by a double ep at the end of the series</b><br><i>(example: PoT)</i><br>(fixed once the new animepage is in place)
*<b>eternally stalled rels caused by a merged rel</b><br><i>(example: eva movie)</i><br>(fixed once the new animepage is in place)<br>2 single eps released in 1 file listed under "Other" causes the staus to remain stalled.
*<b>finished set rels caused by doubleeps in the middle of the series</b><br>(fixed once the new animepage is in place)
__NOTOC__
__NOTOC__
[[Category:Definitions]][[Category:Features]]
[[Category:Definitions]][[Category:Features]]

Revision as of 15:31, 3 November 2006

The Groupstatus displays information about the current state of a release.
This information is displayed in the groupinfobox on every animeentry and in the groupentry for every listed group in AniDB.

Note: This feature doesn't have to be 100% correct as it's data is generated by AniDB automatically for most parts and is very dependent on the users. This means if users didn't add all files a group released it won't show the "true" status.
Take note the states aren't updated in realtime. See: Routine_Maintenance

Possible States

(asuming all files released by the group got added to AniDB)

  • complete
The group released for every episode for a specific anime in AniDB at least 1 file.
  • finished
The group released at least a file for the last episode of an anime.
  • ongoing
The group hasn't finished/completed this series yet. The release is still ongoing.
  • stalled
The group hasn't released a file for this series for at least 2 months.
  • dropped
The group has officially abandoned this project or the group isn't existing anymore.
THIS IS THE ONLY STATE SET MANUALLY BY MODS.
Note: Stalled, finished and complete are automically generated states! They CAN'T be set by AniDB mods!
Dropped is the only state which can be set by Mods!

How it works

ongoing to stalled

AniDB only check for the highest added file for an episode by a group to set states. A timestamp gets set for this episode and if a higher ep doesn't get released in a defined timeframe it gets set stalled. Adding lower eps won't change the timestamp.

Lets make an example to show what this means:

Meitantei Conan
Anime Conan is set 314 stalled 06.07.2003 by AniDB.
Though they are still releasing frequently enough to qualify for ongoing. Now why are they marked stalled?
Like shown they released ep 314 on the 06.07.2003. AniDB is waiting for them to release ep 315. Until this happens it will be stalled for eternity.

ongoing/stalled to finished/completed

A release will get considered complete/finished by AniDB if at least a file for the last ep gets added. AniDB compares the highest file with the total ep count set for the anime. If those match it's finished. If a group even released a file for every episode of this anime it's complete

Lets make an example to show what this means:

Tennis no Ouji-sama
SHS finished this series, but as the last ep (178) is a doubleepisode (with 177) it won't get set finished, but stalled

dropped/stalled to ongoing

This is identical to ongoing/stalled to finished/completed. Once an episode with a higher number than the one with the timestamp gets added it gets updated to another state.

ongoing/stalled to dropped

This process is manual! Please report any dropped release here

Problems

The AniDB status system obviously has various problems.

  • No relations between the groups that would influence the status.
    (example: HnG)
    While there are parent child connections between groups, they are nothing more than links. There is no dataexchange between those groups. Meaning If a series is done by a Team which splits up in the middle of the release and gets finished by 1 of the 2 groups it will only get set finished instead of completed
    See also: AniDB Bugtracker - stronger group relations/virtual groups
  • eternally stalled rels caused by groups which release eps way ahead of them
    (example: Conan)
    A group releases an ep way ahead of the eps they really sub which causes AniDB to wait for a "higher" ep
    (maybe fixed once the new animepage is in place)