... | ... | @@ -216,4 +216,53 @@ Added steps for discussion (Not included in the proposal) |
|
|
|
|
|
4. User exports individual questions
|
|
|
* Proposal states: “Questions exportable to learning management systems (SCORM compliant), Word documents, or other formats including CSV, Google docs, and QTIs.”
|
|
|
(Error in Google doc, this relates to logged in users.) |
|
|
\ No newline at end of file |
|
|
(Error in Google doc, this relates to logged in users.)
|
|
|
|
|
|
## Week 6: Sign up, User management, and other info pages
|
|
|
|
|
|
|
|
|
Week 6 Agenda
|
|
|
|
|
|
1. Update: additional meet on Thursday 25 February to focus on production assignments and in-app chat
|
|
|
2. Walkthrough of wireframes for sign up process (and integration with HHMI)
|
|
|
3. Other pages
|
|
|
|
|
|
Walkthrough of wireframes for sign up process
|
|
|
|
|
|
Integrations with HHMI from proposal:
|
|
|
|
|
|
1. The question database (Qdb) will be: Available to the community through HHMI BioInteractive, linked from website
|
|
|
2. Log in using their BioInteractive website account, Google sign-in, or create a new account. New accounts created here should work on the BI website as well (better approach is to sign up on BI and then sign up with those credentials).
|
|
|
|
|
|
Other pages
|
|
|
|
|
|
1. Managing users and their roles:
|
|
|
* user management: a list of users in the system, showing basic info about the user; functionality to deactivate user
|
|
|
* Admins “View how many/which questions teachers submit”
|
|
|
* add users to 'teams': managing editors; handling editors; reviewers; production team
|
|
|
|
|
|
2. Profile page
|
|
|
* Change password or email?
|
|
|
* Reviewer role is opt-in, but there needs to be a place to remove role, and to opt-in at a later date.
|
|
|
|
|
|
3. Information pages:
|
|
|
* Questions & Learning Objectives (same purpose as 'Discover' page) search by both questions and LOs.
|
|
|
* Professional Learning (link to assessment courses and other pages on BioInteractive website)
|
|
|
* About
|
|
|
4. Home page is a landing page, that links to Discover page. Note: footer should be visible on all pages, not just landing page.
|
|
|
|
|
|
|
|
|
Not in proposal, added for discussion
|
|
|
Admins can add a “basic page” and link it from the navigation.
|
|
|
What are the options for styles on basic pages?
|
|
|
(agreed this feature won't be developed. Coko could create addition 'information pages' in future).
|
|
|
The Super/Sys admin will be able to edit all published questions (e.g. to fix a typo). Discussed possible feauture:Sys admin chat with ME.
|
|
|
|
|
|
Feedback on Wireframes from week 5
|
|
|
|
|
|
* Learning objectives need to be more prominent/ given equal weight as questions.
|
|
|
* Search should show the related LOs for a question result
|
|
|
* Coko to work on more detailed wireframe for the search functionality on 'Discover' page. E.g. what does user see when he fisrt arrives on page (latest published questions at top of list); what does search area show when users is searching; how are questions displayed when search is completed.
|
|
|
* Delete is preferred over archving a question or list of questions.
|
|
|
* future interations could have user-created tags for questions on lists page.
|
|
|
* Users can add the same questions to multiple lists |