546
edits
Release: Difference between revisions
m
→Concept of releases
Epoximator (talk | contribs) |
Epoximator (talk | contribs) |
||
| Line 59: | Line 59: | ||
===Questions=== | ===Questions=== | ||
====Can it replace animegrouptb?==== | ====Can it replace animegrouptb?==== | ||
Don't think so. A release can not be 'dropped' because it would break the purpose of it self (at least partly). And since a system | Don't think so. A release can not be 'dropped' because it would break the purpose of it self (at least partly). And since a system like this can't be fully automated, the ag table is (most likely) needed as the basic way of file grouping. | ||
like this can't be fully automated, the ag table is (most likely) needed as the basic way of file grouping. | |||
====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 | 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"). | ||
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) | ||