+1 to adding to a modified version of change_tag, or something like it.
While unfamiliar with the current tagging interface(s), the content of
ct_tag seems arbitrary ("possible movie studio tagger" appears 4 times in
enwiki.change_tag.ct_tag out of >2mil rows) and it probably makes sense to
keep machine tagging automatically added at the time of an edit distinct
from the apparent post-edit human/bot annotation use of ct_tag.
Re: information on which automatic tags to hide, I don't think that should
be stored with every row. Keeping that in configuration (where
configuration options may consist of patterns to match) seems more
appropriate.
The primary use cases for this feature appear to be around offline analysis
and I'd like to see design take into account the possibility of this table
existing in a separate database from the revision table at some point in
the future.
-A
On Wed, Feb 15, 2012 at 10:27 AM, Platonides <[email protected]> wrote:
> change_tag table?
>
> Seems straightforward.
> The only thing is that we may not want to show some of those automatic
> tags by default, so we would have to introduce a new concept of a
> 'hidden' tag.
> There are several ways to accomplish that, a list in the configuration,
> adding a new column, storing it in ct_params, or just using a convention
> in the tag name for hidden ones.
>
>
> _______________________________________________
> Wikitech-l mailing list
> [email protected]
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
_______________________________________________
Wikitech-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
