OSP 2.5 Requirements

Promoting OSP as a Sakai Core Tool

Leadership by The rSmart Group

Promoting OSP as a core tool will allow simulated load testing and scalability across all tools (see http://confluence.sakaiproject.org/confluence/x/ubM).

The following are required to be done as part of this promotion:

The following are desired to be done as part of this promotion:

Aggregated View

Leadership by the University of Michigan

User-centric, possibly in My Workspace, need to hide/integrate tools not being used, does not replace the course-centered view in CIGs, optional according to institutional configuration

Critical Priority Tasks (9 votes)

Moderate Priority Tasks

Goal Management Tool

Currently there are no Goal Management issues scheduled for the Sakai 2.5 release.

Improving the User Interface

Leadership by ?

Focus on making the user experience more integrated and cohesive by assessing current user workflows, reducing clicks, potentially reducing tools, increasing UI consistency between tools, and making language consistent. Following are the JIRA issues receiving top votes:

Bugs

Tasks & Feature Requests

User Interface Reviews

• Matrix UI Review
• Portfolio UI Review

Use Cases

See ui-usecases1-7.doc

Long-Term Requirements

A list of UX items that are likely to miss the 2.5 release is maintained in Future UX Requirements.

Portfolios

Leadership by LaGuardia Community College

(high priority portfolio issues by vote)

Bugs

Tasks & Feature Requests

Reports

(Note: all reports issues have been tabled until Sakai 2.6)

Meta-Tagging and Searching

Out of scope for OSP 2.5 but must be taken into consideration in relation to requirements for Goal Management and User Interface
Suggested group for additional thinking in this area: Noah Botimer, Sean Keesler, Melissa Peet, Darren Cambridge

• Functionally similar to putting an item in a matrix cell or linking to a goal with the goal management tool.
• Users tag items so that they can remember them and get back to them when they are ready to use them.
• For success, social meaning is required, where user has information about how others have tagged similar items. We don't know what to construct personally unless we have social knowledge.

Possible ways to begin (and initially limit) development:

1. Make all tools goal-aware? Goals are tags; ratings are tags.
2. Free-tagging with categories prescribed by site organizers rather than completely ad hoc reflective context. Teachers pre-populate tags for students to use.
3. In Resources, users tag items with themes, learning outcomes. Tags used for organizing and reflecting. Users create new tags, apply to existing content, and describe why items are tagged in this way.
4. Create tagging manager for goals and other types of tags.
5. Use Drupal http://drupal.org

OSP Community Library

Leadership by Nate Angell

• Community Library definition, development and participation
• Drupal-based community library is under development and targetted for release by June 30th.

(initial prototype available at http://ocl.codetools.org/ will be superseded by Drupal-based community library – currently at http://new.osportfolio.org/ for now)

A. First-Level (Absolute) Requirements (all trivial on recommended platform)

1. Uploads to the library (multiple versions)
2. Screenshot uploads
3. Categorization of widgets
4. Searching on widgets
5. Sorting of a view
6. Ability to place comments

B. Second-Level Requirements

1. Thorough integration with the osportfolio.org web site (trivial)
2. Integration with other community tools (eg, Confluence, Jira, etc) (requires integration with project LDAP)
3. Ability to rate experience with a widget (per user rating would require QA on existing rating modules)
4. Ability to mark institutions using a widget (trivial)
5. Bundling of individual widgets into a package (standalone and grouping) (medium hard)
   one method would be to establish bundle content type that could both stand alone (eg, with attached bundle of component files) or contain individual component records, each of which has an attached component

C. "Nice to have" items

1. Sharing lessons learned (trivial)
   this could be its own content type: a best practices or similar content type
2. Tagging (trivial)
   can be both freetagging and structured
3. "Live" Import/Export (might require some coding to make seamless to sakai instances)

XSD/XSL/CSS/XHTML Builders

• General bug fixes and improvements to XSD Weaver (contrib) tool