Versions Compared

Old Version 2

changes.mady.by.user Former user

Saved on

compared with

New Version 3

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Sakai 3 ePortfolio (UM)

Functional Requirements

...

Multiple Evaluator Workflow

  1. Matrix cells (and other completed artifacts) must allow evaluation by multiple users
  2. Matrix cells (and other structures) must allow multiple types of evaluation (different forms specific to roles or users)
  3. Users must be able to request feedback or evaluation on arbitrary completed components to site members or anyone
  4. 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

  1. 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

  1. 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

  1. Users must be able to filter a view to only those items that they may interact with
    1. Students must be able to filter to just those cells that are available
    2. Instructors must be able to filter to just completed cells that are pending evaluation
  2. 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"?
  3. Users must be able to filter a view to those items where another user has requested interaction (feedback/evaluation)

Email Notification

  1. Users must have the ability to opt into email notification for certain events (cells becoming available, being submitted, etc.)
  2. 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

  1. Batch operations must be better supported (e.g. changing a group of cells to available)