1,633
edits
Release: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
|||
| Line 1: | Line 1: | ||
{{TOCright}} | |||
==Concept of releases== | ==Concept of releases== | ||
Instead of grouping files by group only (anime-group) we could introduce "Releases" in which files could be grouped completely arbitrary. That is both files from different groups and files without group. | |||
Instead of grouping files by group only (anime-group) we could introduce "Releases" in which files could be grouped completely | |||
===Why=== | ===Why=== | ||
*Fix ag-state, or rather an addition to ag state (240, 145) | *Fix ag-state, or rather an addition to ag state (240, 145) | ||
*Grouping and states for no-group files | *Grouping and states for no-group files | ||
*Multiple | *Multiple releases per group; DTV/DVD, low/high quality, avi/mkv, xvid/h264, etc. instead of version abuse | ||
===Why not?=== | ===Why not?=== | ||
| Line 13: | Line 14: | ||
===Possible tables=== | ===Possible tables=== | ||
releasetb( | releasetb( | ||
id int4, | id int4, | ||
| Line 47: | Line 47: | ||
: I am not sure about that assumption of one file per ep. I.e. what happens with releases which have external subtitles? (We could of course use the file-file relations for that info.) How would you handle a case where a release contains files from multiple groups and one or more eps were actually subbed by more than one group? I.e. group A released 1-10 and group B released 1-3 and A&B released 11-12. That cached ep map mentioned earlier is not the status int2, right? Would releases need a name? Or would there be different "types" of releases? | : I am not sure about that assumption of one file per ep. I.e. what happens with releases which have external subtitles? (We could of course use the file-file relations for that info.) How would you handle a case where a release contains files from multiple groups and one or more eps were actually subbed by more than one group? I.e. group A released 1-10 and group B released 1-3 and A&B released 11-12. That cached ep map mentioned earlier is not the status int2, right? Would releases need a name? Or would there be different "types" of releases? | ||
: [[User:Exp|Exp]] 18:56, 8 July 2007 (UTC) | : [[User:Exp|Exp]] 18:56, 8 July 2007 (UTC) | ||
:# a release is supposed to represent one possible "pack" of files that covers an anime (to assist you when you're wondering what to get) and in that regard only one file per ep is needed. you usually don't watch several files of the same ep unless you want to compare (or is | :# a release is supposed to represent one possible "pack" of files that covers an anime (to assist you when you're wondering what to get) and in that regard only one file per ep is needed. you usually don't watch several files of the same ep unless you want to compare (or is re-watching). so, using your example, we'd have to choose whether we want 1-3 from A or B in the "release". this could (and probably will) lead to some political issues, but in worst case two releases can be added; one with 1-3 from A and one with 1-3 from B (as one file can be part of several releases). allowing several files per ep (disregarding subtitles and split files for now) breaks the initial idea of releases, although it would still solve most of the issues it was supposed to address. (on a side note; new versions of files would "push out" the old versions in a release. complete re-encodes would be added as new releases). | ||
:#the cached ep map = eprange in animegrouptb, meaning eprange was based on that idea. | :#the cached ep map = eprange in animegrouptb, meaning eprange was based on that idea. | ||
:#releases would usually be addressed by group names, but could have both name and type too. the "other" bit is the alternative, meaning if a release needs some additional explaining it would go there. --[[User:Epoximator|Epoximator]] 13:11, 10 July 2007 (UTC) | :#releases would usually be addressed by group names, but could have both name and type too. the "other" bit is the alternative, meaning if a release needs some additional explaining it would go there. --[[User:Epoximator|Epoximator]] 13:11, 10 July 2007 (UTC) | ||
| Line 62: | Line 62: | ||
====Can it be semi-automated?==== | ====Can it be semi-automated?==== | ||
It should at least be possible to build the initial content based on some general rules. This might not be wanted though; it could only be an addition to animegroups. Meaning releases would only be used where it is needed (sort of like file/ep rels are used today). It should at least not be needed for movies/ | It should at least be possible to build the initial content based on some general rules. This might not be wanted though; it could only be an addition to animegroups. Meaning releases would only be used where it is needed (sort of like file/ep rels are used today). It should at least not be needed for movies/OVAs (only one "ep"). | ||
: As you've already pointed out such a release system would not fully replace the automatically generated animegrouptb data. Which would meant that there would probably be no reason to duplicate the data. For all those releases where the animegrouptb approach works fine, we wouldn't need to add any release info. Release info would only be manually added for the hard cases. And even there we might want to look for an approach which can handle the group<->subgroup releases mostly automatically. | : As you've already pointed out such a release system would not fully replace the automatically generated animegrouptb data. Which would meant that there would probably be no reason to duplicate the data. For all those releases where the animegrouptb approach works fine, we wouldn't need to add any release info. Release info would only be manually added for the hard cases. And even there we might want to look for an approach which can handle the group<->subgroup releases mostly automatically. | ||
: [[User:Exp|Exp]] 18:50, 8 July 2007 (UTC) | : [[User:Exp|Exp]] 18:50, 8 July 2007 (UTC) | ||