Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Insert excerpt
OSP :OSP Usage Scenario Style Sheet
OSP :OSP Usage Scenario Style Sheet
nopaneltrue

...

  1. Matrix/wizard administrator sets required number of evaluators per cell/page to 1.
  2. Matrix/wizard admin selects evaluators for cell/page X.
  3. Student submits matrix/wizard cell/page X for evaluation
  4. Evaluators who have opted in for individual or digest notifications, receive an email notification.
  5. Evaluator 1 logs in to evaluator dashboard and selects the cell/page X. 
  6. Cell/page X disappears from the dashboard of all approved evaluators because quota will be met when Evaluator 1's work is complete.
  7. At some point (the evaluation may be in-progress or resubmitted), Evaluator 1 determines that s/he is unable to complete the cell/page X evaluation or has a question for the matrix/wizard admin.
  8. The Evaluator forwards cell/page X to the matrix/wizard admin.
  9. A notification is sent to the matrix/wizard admin.
  10. The matrix/wizard admin logs in a locates the forwarded item in his Forwarded Evaluations queue.
  11. The matrix/wizard admin either answers question and returns cell/page X to Evaluator 1 for completion or (if Evalluator 1 cannot complete), releases cell/page X back into the Itmes Pending Evaluation queue. 

User Story 15:  Multiple Evaluators Use Evaluation Form with Clickable Descriptors to Rate Criteria and Goals and Calculate Average Ratings - rSmart (

...

March 24, 2008)

A) Functionality that already exists in 2.5 (with customization of forms).
  1. An evaluation form providing that uses .xslt to provide a scoring rubric in the form of matrix with clickable descriptors is associated with a matrix cell, wizard page, or portfolio. (The basic functionality for this requirement already exists in OSP 2.5.)
  2. The evaluation form identifies a specified set of evaluators (by role or username) to rate the cell, page, or portfolio.
  3. The set of evaluators may be organized to require any number of ratings per cell, page, or portfolio.
  4. The set of evaluators can include one or more peer advisers whose ratings are advisory only and do not enter into the calculation.
  5. If multiple goals or standards have been associated with the cell, page, or portfolio, evaluators rate each goal/standard.
  6. The evaluation forms for each evaluator feed into an evaluation results form associated with the cell, page, or portfolio.
  7. The evaluation results form includes a calculation field to provide the mean rating for each goal/standard across all evaluators. This field provides a cumulative total across evaluators as ratings are added.
  8. The evaluation form provides a comment area for evaluators to include public and private comments. The evaluation results form displays the public comments.
  9. The calculation field The evaluation form provides rows for each criterion (standard, outcome, etc.) and columns for each scoring level.
  10. The cells in the matrix provide descriptors for student performance for each criterion at each scoring level. Evaluators click on one matrix cell per row to indicate the score they award to each participant for each criterion. The cell that has been selected as the score for each row is highlighted for visual confirmation that it has been selected.
  11. Each time an evaluation form is submitted by an evaluator, the mean score across all criteria is calculated and displayed on the form for viewing by any user with permission.
  12. The evaluation form may provide a comment area for evaluators to include comments.
B) Functionality desired for OSP 2.6 or beyond (with customization of forms).
  1. Evaluation forms are also used to rate goals linked to a matrix cell or wizard page via the goal management tool.
  2. Evaluation forms, specified evaluators, and the goal management process may also be used with portfolios via the association of evaluation forms with portfolio templates.
  3. When evaluators add comments to an evaluation form instance, they may designate them as public or private comments.
  4. When each evaluator submits an instance of an evaluation form for a matrix cell, wizard page, or portfolio, the calculations for each criterion or goal in that form instance, as well as the mean score for the form instance, are combined with calculations from all other evaluation form instances for the owner of that cell, page, or portfolio to provide a mean score for each criterion or goal and a total mean score across all evaluators.
  5. The set of evaluators associated with a matrix cell, wizard page, or portfolio template can include one or more peer advisers whose ratings are advisory only and do not enter into the calculation of mean scores.
  6. The calculation of the mean score for each criterion or goal identifies an acceptable range of inter-rater reliability for each rating and flags ratings that require a third raterevaluator.
  7. A flagged evaluation form instance requires the submission of an additional rater evaluation form instance by a third evaluator before the cell, page, or portfolio can be complete. The additional rating may be preset to either substitute for the rating Ratings from the additional evaluator replace the scores from the evaluator farthest from the calculated mean or combined with existing ratings.The number and identity of the evaluators can be preset such that when score for the cell, page, or portfolio.
  8. When all evaluators have completed their ratings, the evaluation results form completes the cell, page, or portfolio and is displayed to the owner of the cell, page, or portfoliobecomes complete and its contents and score cannot be changed.
  9. The owner of the a completed matrix cell, wizard page, or portfolio can view combined ratings and public comments of all evaluators (with or without owners identified) according the process specified for the evaluation form.

Functional Details (may be added after community demo) (1)

See: Multiple Evaluator Workflow - Functional design

Describe any functionality not fully captured in the User Stories.

...

Include any ERDs, flowcharts, sketches, mockups, etc.Image Removed Image Removed

Community Acceptance (4)

...