2.5 Requirements - OSP Community Library

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)