Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 3
Next »
Sakai 3 ePortfolio (UM)
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). Beth: What is a "component" in osp terminology (form, cell, matrix, ...)? Can you be more specific on types of further action?
Permissions
- Users granted the ability must be able to edit instructions inside a Form or for a Cell without the full "Manage Matrices" permissions. Beth: are there any other new permissions besides "allow-edit-instructions" that is being requested? Are you perhaps asking to allow reviewers and/or evaluator roles be allowed to update instructions?
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
Filtered Views
- Users must be able to filter a view to only those items that they may interact with
- Students must be able to filter to just those cells that are available
- Instructors must be able to filter to just completed cells that are pending evaluation
- Users must be able to filter or sort by recency of request or status change on a list of items Beth: What is an" item"?
- Users must be able to filter a view to those items where another user has requested interaction (feedback/evaluation)
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. Beth: Is this another way of saying you'd like to limit the scope of notifications?
Batch Operation
- Batch operations must be better supported (e.g. changing a group of cells to available)