Attribute Manager

Status Brainstorm about what the issues are

Motivation

• Advanced Beginner level use cases (Level 2)
  • Choosing alternate attribute columns from a default list of options (ie. Right-click)
  • Choosing alternate attributes to add to detail view from a default list of options (ie. Right-click)
  • Adding ad-hoc attribute values in the summary / detail view (ie. New projects)
  • Not adding new attributes themselves (ie. New type of collection)
• Intermediate level use cases (Level 3) (Go to attribute manager)
  • Loading or Adding collections to the sidebar
  • Adding attribute columns from complete set of attributes
  • Adding attributes to the detail view from complete set of attributes
  • Attribute manager also contains the complete list of all user-defined collections and so a portion of it will function as the collections manager
• Advanced level use cases (Level 4)
  • Provide advanced users with an easy way to "edit" and manage the content model by adding and re-organizing user-defined attributes and attribute values. In that sense, the attribute manager is a user-facing representation of the Chandler content model.
• Super-advanced level use cases (Level 5)
  • Adding new kinds

• We want to consciously have a pretty steep learning curve to get to these mid and high level use cases. We want to provide this functionality for power users, see how they use them before selectively creating easier entry points for all users.

Issues

• How should the attributes be grouped?
• How do users control layout of attributes in Detail view?
• What attributes and attribute values do users need to be able to edit?
• What attributes and attribute values should users not be allowed to edit?
• How do users assigned "Kind-ness" to user-defined attributes and attribute values?

-- MimiYin - 11 Jun 2004

• Attribute_manager.xls: