...
The following high level portfolio functions are described in more detail by the Portfolio-related vignettes page. Sub-bullets describe specific UM application requirements.
- Guide
- Fine grained permissions
- Collect & Associate
- Portfolio artifacts must be available to both free-form (expressive) and guided/structured portfolios
- Reflect
- Evaluate & Feedback
- Inline comments/feedback, rubric-based feedback
- Email notification (opt-in)
- Multiple evaluator workflow
- 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
- Flow (Workflow)
- Email notification (opt-in)
- Collaborate
- Port (Download/Export)
- Customize
- templates and styles must be easy for non-technical users (Students/Faculty) to create and use
- PreserveTag ~(lesser priority pending user stories; supported by underlying Sling framework)~
- Migrate ~(lesser priority)~
- Dashboard/Aggregated view ~(additional details below)~
- This feature addresses usability issues, but doesn't seem to fall under any existing goals/functions on the Portfolio-related vignettes page (we should probably add a usability goal?)
- Tag (lesser priority pending user stories; supported by underlying Sling framework)
- Migrate (lesser priority)
...
Legacy Portfolio Wish List
...