This initiative is about finding things on the openplans site.

<< Planning | project home | what tagger is up to >>

Taking tagging further

(next steps/possible directions)

xenozopic integration

1. arbitrary cataloging of metadata from non zope source(read task tracker, other wsgi apps)

2. creating proxy objects with unique ids so we can tag them

3. tagger/rhizome -> wsgi gateway for showing tag data on wsgi side

Managing proliferation

• tag merging and editing

• autocomplete within tagging/category interfaces
  
  

Pull/Push 

from other tagging services, particularily delicious or magnolia.

Auto-Tagging

embedding tags in mailing list email, wicked links, etc. think tagalag.

Tagging prepositions

similar to delicious's network tags.

a prefix triggers additional information to be stored that can be filtered on later.

• geographic info (coordinate, regions): at:West 12th and Hudson or in:Manhattan

• relationship to a project member or another finite node:  for:ian or of:press release or for:status blog

• conceptual parentage for creating navigate:  of:fall campaign

Then UIs utilize the data additional data.

ie: a map of all projects in:Manhattan for:traffic reform

tag groups

People like to organize their tags

I am sort of vague on what this actually means and how you would create a meaninful interface for it(been there).

Primary Goals

3. Tagging of Content
   
   • inclusion of tagging ui into content views
     
     1. inclusion of add and delete widget in UI
        (requires inclusion of all supporting js and possibly new views)
     2. clouds
        
        • for content
        • for users
        • for projects
     3. listing pages
        
        • user's tags
        • all content for a tag (or tag intersections)
        • related content
          
   • permission structure
     
     1. creation of/or reuse of view/modify perms
     2. proper display depending on project security
        (see related content)
        
   • project specific tagging
     
     1. tagger per project
        
     2. adding taggers to old project
        
     3. filtering tags for specific projects
        
   • listing pages
     
     1. user's tags
     2. related content for tags
   • inclusion in plone searching (livesearch, site search, smartfolders)
     
     1. Use of AT Computed fields (for indexing of SearchableText)
     2. "foaf:topics" index: special keyword index just for tags (mainly for smartfolders)
     3. IObjectTagsModified event subscribers to keep catalog synced
     4. (possible using some sort of deferment via ClockServer or threads to optimize)
     
     
4. Categorization of Projects (and content?)
   
   • project preferences ui (for managing category)
   • project page display "by category"
   • separation from tagging
     
     1. separate tagstore (at site level)
     2. use of AT field initially to integrate into project prefs
        
   • inclusion in plone searching (livesearch, sitesearch, smartfolders)
     
     1. cataloging as part of Keyword and SearchableText(?)
   • security for category management
     
     1. manage as an AT field(?)
   
   
3. Projects Page Revamp
   
   • Dynamically generate browsable listings by category and tags
   • view to browse content by tag or category

Latest developments: 1.0 tagging