Review of beta 1: Analyze interface
Bevan - August 3, 2008 - 02:43
| Project: | Usability Testing Suite |
| Version: | 6.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | duplicate |
Jump to:
Description
This should have been part of http://drupal.org/node/290271 but I forgot to review this section and ran out of time.
- Generally, throughout the analyze UIs:
- 'Name' is populated with the database prefix code. Use participant number instead, which is an incremented counting number based on the order of starting their sessions. e.g. 'Participant 1', 'Participant 2' etc.
- Timestamps should be relative, e.g. minutes and seconds after the start of the session.
- export links seem oddly placed. Would they make sense as a local task / tab? Secondary local task / tab?
- We still need a page that shows all event-based data feeds for one participant in one table. The data that will be used in the timeline. Without this it's almost impossible to 'follow' the user's progress in the tasks, which is the whole point of this.
- admin/uts/analyze/2/sessions
- Incomplete sessions should still be 'analyzable'
#1
To note on this issue, we are currently working on an actual design of the Analyse screen - which probably attacks most of these issues and creates a whole set of new ones. It will take some time though, before we can release any mock's that are good. Though this is not a part we want to rush.
#2
Other overlapping analysis issues have been completed.