Personal tools
You are here: Home Software Center do2gether PG Draft Features Tagging System
Document Actions

#21: Tagging System

Contents
  1. Definitions
  2. Motivation
  3. Assumptions
  4. Proposal
  5. Implementation
  6. Deliverables
  7. Risks
  8. Progress log
  9. Participants
Implement a system-wide tagging system (folksonomy)
Proposed by
TFF
Proposal type
Architecture, Other
Assigned to release
State
being-discussed

Definitions

!!! - a "must have" feature

!! - a requested feature

! - a less desired feature

? - desired feature, but can be discussed for smaller changes

?? - a feature open for discussion

??? - a feature fully open for discussion in behaviour, ui, architecture...

CF - Criticality Factor. It is the multiplier number for each feature, to be used when calculating penalties on deliverables, in case of bugs or delivery missing. The higher, the most critical the feature is.

Motivation

 

Assumptions


Proposal

  • Group owner can enable/disable members to submit one or more tags to any item (comments, topics, messages, posts) - !! CF 2
    • tags structure could be: include (or not) at least one tag from owner-defined tags, and any from most used tags, or a new tag by adding using an auto-fill/auto-suggest JS input box - ? CF 1
  • User can Add/edit/remove his own set of tags that he can apply to different items - ! CF 1
  • Group owner can define a set of tags to an object, and enforce users - when tagging - to choose at least one (and then add their custom tags) - ? CF 2
  • User can navigate a tag cloud page about his tagged content - !!! CF 3

Implementation


Deliverables

PG Manage Tags (low-res)






























Risks


Progress log


Participants



Powered by Plone CMS, the Open Source Content Management System

This site conforms to the following standards: