Sakai 3 ePortfolio (UM)
High Level Portfolio Requirements
The following high level portfolio functions are described in more detail by the Portfolio-related vignettes page.
- Customize
- Present & Collaborate
- Guide
- Fine grained permissions
- Collect & Associate
- Portfolio artifacts must be available to both free-form (expressive) and guided/structured portfolios
- Workflow
- Reflect
- Evaluate & Feedback
- Inline comments/feedback, rubric-based feedback
- Email notification (opt-in)
- Multiple evaluator workflow
- Export
- Share
- All artifacts (images, etc) included in a portfolio must be easily viewed by any shared user
- Email notification
- Report
- Aggregate student responses (with student id) into comma or tab-delimited data that can be pulled into SPSS
- Tag (lesser priority pending user stories; supported by underlying Sling framework)
Legacy Portfolio Wish List
This section describes features that UM has wanted but been unable to implemented due to limitations with the underlying OSP framework. All have been mentioned above.
Multiple Evaluator Workflow
- Matrix cells (and other completed artifacts) must allow evaluation by multiple users
- Matrix cells (and other structures) must allow multiple types of evaluation (different forms specific to roles or users)
- Users must be able to request feedback or evaluation on arbitrary completed components to site members or anyone
- Guiding users (instructor/evaluator) must able to lock and "hand off" components to users who will take further action before returning an item to a student. (Per-item workflow phases).
Additional Permissions
- Users granted the ability must be able to edit instructions inside a Form or for a Cell without the full "Manage Matrices" permissions.
Bugs
- Artifacts linked or submitted through a portion (cell) of the portfolio must be available to the users that may view that portion (cell); also written up as "Embedded images in resources not passing through security advisor" in http://jira.sakaiproject.org/browse/SAK-7464
Email Notification
- Users must have the ability to opt into email notification for certain events (cells becoming available, being submitted, etc.)
- Notification opt-in must provide useful batch operations such as enabling notification for all Matrices, Matrices within a specific site, a group of cells, new requests for feedback, all new pending evaluations, etc. (i.e. scope of email notification must be configurable).
"Matrix" Batch Operation
- Batch operations must be better supported (e.g. changing a group of cells to available)
Reporting
- Aggregate student responses (with student id) into comma or tab-delimited data that can be pulled into SPSS
Inline Feedback
- Ability to associate inline feedback in a database with a completed form
- A mechanism for the user to request feedback from a portfolio page
- A mechanism for the mentor to enter feedback directly in the portfolio page
- A mechanism for the student to select which instance of feedback to view
- A mechanism to view the selected feedback
- Email notification upon request for feedback
- Email notification upon submission of feedback
- Several CSS styles to mark up feedback, such as a highlighted yellow background for inline feedback and a blockquote-like style for extended feedback.