OSP-UI-16 OSP Dashboard Summary

Rationale/need:

• reduce clicks
• create me-centric experience in a site-centric system
• organize OSP activity on a task-centric basis

Assumptions:

• a dashboard is a plain summary view of selected domains
• a dashboard floats over a detailed view of a domain and/or the domain item itself
• domain lists are of 3 types - all with default selection, sorting and item count filters:
  1. time sensitive information (ie. My Deadlines, Recent activity)
  2. task based, but no due date is associated with the tasks
  3. all items of a domain (ie. My presentations, Portfolio Sites)
• all operations on list items take place in either the detailed view or the item itself - the dashboard is just a summary

Challenges

• the information is very varied
• the information can be very large
• roles and permissions complicate matters - since the dashboard is a cross-site aggregator, the aggregation needs to reflect the possible roles a given user may have
• cross-tool communication is needed at many levels - ie. tool needs to know that user arrived via the dashboard and take her back to the dashboard when the action has been completed or provide some navigation for the same purpose

Design proposal

Hierachy is unavoidable given the variability and size of information, as well as the varied relationships between a user and this information. Since the later is the "me" part of the equation the first level in the hierarchy could be:

The images that follow are meant only as a suggestion. The validity of the rationale, assumptions, design and details of the design need to be hashed out by the community - specially members much more familiar with the OSP-verse than me.

 User

Author 

 Administrator