[Debtags-devel] Using Python NLTK for tag generation [was: AI for tag generation].
Hervé Eychenne
rv@eychenne.org
Sun, 3 Oct 2004 18:06:46 +0200
On Fri, Oct 01, 2004 at 09:04:46PM +0200, Enrico Zini wrote:
> On Fri, Oct 01, 2004 at 05:49:01PM +0200, Erich Schubert wrote:
> > The suggestion by enrico of a "special:completely-tagged" tag is
> > sweet. I'd appreciate having this tag added to the vocabulary.
> Tag: special::completely-tagged
> Description: Package has been tagged with full care
> This package has been tagged by carefully checking and pondering tags
> from every facet, and it can be used as an example of good tagging and
> to train probabilistic tag inference altorithms.
> .
> This tag will also be automatically removed from all packages after
> vocabulary updates.
> Committed, updated on gluck and notified the central database of the
> update.
> Let's ROCK! ;)
Tagged carefully, ok... but at which time?
What if some new tags appear after the review, making the tag set of a
package not so up-to-date anymore?
In my opinion (I said that from the begining, if you look at my first
posts), we should take care of that. I was proposing that new tag
additions (addition of a new tag name, or addition of a tag in a package
taglist) should be timestamped.
This way, we would know exactly which tags would be introduced after
the "complete" review.
I agree that this would make the database a little heavier, but I keep
on thinking this is the right way to do things properly.
and
Hervé
--
_
(°= Hervé Eychenne
//) Homepage: http://www.eychenne.org/
v_/_ WallFire project: http://www.wallfire.org/