... | ... | @@ -46,4 +46,37 @@ list of levels can be shared soon, complete list to come later |
|
|
* could be more than one image in a question
|
|
|
* images could be in the aswers too (e.g. 4 graphs to choose from)
|
|
|
* images possible (in question and answers)
|
|
|
* tables in questions |
|
|
\ No newline at end of file |
|
|
* tables in questions
|
|
|
|
|
|
## Week 2: Managing Editors check of the submitted questions and the review process
|
|
|
|
|
|
**User stories**
|
|
|
|
|
|
1. Managing editor assigns one or more questions to a handling editor
|
|
|
- optionally does quick check of questions before assigning to handling editor
|
|
|
- can skip handling editors (at least initially) and invite reviewers to review question(s).
|
|
|
2. Handling editor invites Reviewer to review one or more questions
|
|
|
- choose reviewer based on area of expertise (provided at time of sign up)
|
|
|
3. Reviewer gets invitation (question lands in dashboard) and makes decision (4 or 5)
|
|
|
4. Reviewer accepts the invitation. Status = In review
|
|
|
- Reviewer takes the question
|
|
|
- Reviewer completes survey (depends on correct/incorrect answer) which includes questions about metadata, i.e. does he agree/disagree with authors tags.
|
|
|
- Reviewer submits review of questions (goes to handing editors dashboard who assigns production team)
|
|
|
5. Reviewer rejects invitation. Status = Invite rejected.
|
|
|
- reasons for rejection include: out of my area of expertise; don't have time to do it within the next two weeks. Free text area to provide reason/or list of defined options and ‘other’.
|
|
|
- shows as ‘rejected invite’ row in reviewers dash
|
|
|
- question goes back to handing editors dashboard with info of reviewer name and reason for rejection.
|
|
|
|
|
|
|
|
|
**Teams**
|
|
|
|
|
|
1. Admin: Highest permissions.
|
|
|
2. Managing editors: small group of people on the HHMI team, or contractors, who delegate submitted questions to Handing editors.
|
|
|
3. Handing editors: small group of people on the HHMI team, or contractors, whose main responsibility is pushing content through the workflow and publishing questions.
|
|
|
4. Reviewers: large group of people mostly external to HHMI. Serve as content specialists (universities lectures, authors, teachers, etc.). May also be an Author in the system.
|
|
|
|
|
|
**Reviewer metadata**
|
|
|
|
|
|
* Reviewers have already agreed to be an HHMI before they are invited to review questions.
|
|
|
* All users fill out a questionnaire on the courses they teach and their content expertise (this currently happens externally, but should happen in the system at signs up)
|
|
|
- We might need an import script for current questionnaires (200-300). These users have an account created for them, they only need to accept terms to join. |