|
|
## User stories
|
|
|
|
|
|
The following stories were prioritised for the Baseline version.
|
|
|
|
|
|
#### Workflow step: Creating and submitting questions
|
|
|
|
|
|
1. All signed up users are Authors by default who create and submit questions that include metadata as part of the submission.
|
|
|
2. Authors accept legal terms for each question before submission.
|
|
|
3. Authors create and submit questions of these types:
|
|
|
* True/false
|
|
|
* Multiple TF
|
|
|
* Multiple choice (single correct)
|
|
|
* Multiple answers
|
|
|
* Fill in the blank
|
|
|
* Fill in multiple blanks
|
|
|
* Multiple dropdowns
|
|
|
* Matching
|
|
|
* Complex Item Sets (question with sub-questions)
|
|
|
* Essay.
|
|
|
|
|
|
#### Workflow step: Editors’ assessment of questions prior to review
|
|
|
|
|
|
1. Managing Editor assigns a submitted question (individually) to Handing Editors who check the question.
|
|
|
2. Managing Editor and Handling editors can chat with the question's Author to resolve any queries.
|
|
|
3. When a question is not accepted by an Editor, the Author gets boilerplate feedback via email notification.
|
|
|
4. Managing Editor and Handling Editors can invite multiple Reviewers to review questions.
|
|
|
5. Managing Editor and Handling Editors choose Reviewers to invite based on their expertise.
|
|
|
6. When an Editor invites a Reviewer, this notifies an HHMI finance person by email. The email includes the Author’s details and some question metadata (the Bloom’s level will determine the amount the author gets paid).
|
|
|
|
|
|
#### Workflow step: Reviewing questions
|
|
|
|
|
|
1. Reviewers can accept or reject an invitation to review a question.
|
|
|
2. Reviewers see a question without metadata and take the question as a student would.
|
|
|
3. Reviewers complete the reviewer's survey based on their answer, and submit their feedback.
|
|
|
4. Managing Editor and Handling Editors can chat with the question’s Reviewers to resolve any queries.
|
|
|
Workflow step: Editors’ assessment of questions after review
|
|
|
1. Managing Editor and Handling Editors can reject a submitted question based on the Reviewers’ feedback.
|
|
|
2. When a question is not accepted by the Editor, the Author gets boilerplate feedback via email notification.
|
|
|
3. Managing Editor and Handling Editors can accept a reviewed question which moves the question into production.
|
|
|
Workflow step: Producing and publishing questions
|
|
|
1. Managing Editor and Handling Editors can assign production tasks.
|
|
|
2. Production team can see all production assignments on one question.
|
|
|
3. Production team can edit questions and its metadata to complete their tasks.
|
|
|
4. Production team can mark a production assignment complete.
|
|
|
5. Managing Editor and Handling Editors can delete a production task.
|
|
|
6. Managing Editor, Handling Editors and Production team can chat to each other.
|
|
|
7. Managing Editor and Handling Editors can publish a question when all production assignments are complete.
|
|
|
8. The System Admin can edit all published questions (e.g. to fix a typo).
|
|
|
|
|
|
|
|
|
#### Workflow step: Curating and using questions
|
|
|
|
|
|
1. All users can discover questions by searching learning objectives, question text and other metadata fields.
|
|
|
2. Non-signed up users see a question in a 'student view' (take question, then see answer with feedback).
|
|
|
3. Signed up users see a question in a 'faculty view' (with metadata) and 'student view'.
|
|
|
4. All users can export individual questions to Word format.
|
|
|
5. Signed up users can export individual questions to SCORM format.
|
|
|
6. The exported questions meet HHMI's accessibility requirements.
|
|
|
|
|
|
|
|
|
#### Supporting functionality
|
|
|
|
|
|
1. Users sign up with local accounts.
|
|
|
2. On sign up, users:
|
|
|
* verify their email address
|
|
|
* accept HHMI legal terms
|
|
|
* complete a questionnaire on their academic knowledge and teaching experience
|
|
|
* can opt-in to be reviewers.
|
|
|
3. After sign up, users can:
|
|
|
* change email and password
|
|
|
* opt-in or out as a Reviewer.
|
|
|
4. Admins can
|
|
|
* disable a user's account
|
|
|
* add and remove users to teams: Managing Editors; Handling Editors; Reviewers; and Production team.
|
|
|
* see all users in the system (with basic information about them).
|
|
|
5. The site includes information pages created by HHMI, using the Drupal CMS, with text styles provided by Coko.
|
|
|
* a Home/landing page that links to the Discover page
|
|
|
* an About page. |
|
|
\ No newline at end of file |