Re: [Fofredux-devel] tagging question

[Kevin <ke...@dr...>]

Andrew Turner (nilspace) wrote:
> Kevin (and group) I was curious what the "Auto Tag" feature did or is
> supposed to do? I haven't poured through the code - so I was hoping
> you could provide some talk on how/what the current tagging
> architecture is like and what you see being changed in the future.
>   
Auto tagging is:
     Any category/tag type data available in the source RSS will be 
carried over as an FoFR tag when update runs.  Different rss feeds 
encode the categories differently.  I look in <category>, <dc><subject>, 
and <media><category>.(this last one is for Flicr tags)   For each 
category/tag found in the RSS, that tag is added to the item being 
processed.  If the tag name does not exist in FoFR, it is created on the 
fly.  Tag aliases are used to help cut down on "tag explosion".  An FoFR 
tag can have multiple names associated with it.  Example:  "PHP", "PhP", 
"Php", "my php stuff" can all be rewritten to the FoFR tag: "PHP")   The 
aliases are only used for auto tagging.
There are two fields in the feed table to support this:
*auto_tag*:  a boolean flag to enable auto tagging for that feed.  It is 
disabled by default.
*auto_tag_separator*:  Some feeds overload the value of <category> and 
<dc><subject> by throwing a comma or space separated list of values 
instead of including multiple instances of the element.  I can't 
autodetect which overloading format is used, so the user will have to 
configure it on a per-feed basis.  Most feeds use comma so that will be 
the default value.  Flicr and del.icio.us use a space separator.

I'm considering moving these to the config table instead.  It would make 
it easier to change the default value if need be.

50% of this is still in my head.  have a look at the fof_update_feed() 
function to see the code written so far.

> Also - we should start talking/thinking about v0.3 release, what that
> will entail (we've already pulled in some 0.4 features, but other 0.3
> features are further out). We've gotten a lot of new features since
> 0.2 and it might be nice to do a finish up of some of the bugs, QA and
> release.
>
> I know looking at my list, I have a bunch of bugs/features to
> squash/implement - and will try to get them out of the way this
> weekend.
>