Notes: Week 7 (5/10 - 5/16)
Usability Test #1, 5/14
Task #1: 9:35a - 9:40a (expected 9:50a)
- What does "required" mean? (It indicates that the element is required within the schema)
Task #2: 9:41a - 9:53a (expected 9:51a)
<university>element and begins writing out the input code
- reading over documentation to attempt to figure out first element to use
- begins with input element
- Design note: page number indexes on the main listing table to each element?
- Design note: Need notes on how to properly structure the schema on the first page of the schema usage documentation
- attempting to figure out how to fit the location in to the input element
- backtracking to figure out date inputs for day-by-day listings
Task #3: 9:54a - 10:05a (expected 10:05a)
- setting up input tag for material
- Design note: need to make allowed values for attributes clearer - consistently being missed
- closing and opening university tag for each fragment
- "need to start over" with each <university< element pair
- creates material tag, chemical formula = unit of measurement - do we need to move unit of measurement to be an attribute or sub-element of the material itself?
- (No in-test notes from task #4)
Task #5: 10:10 - end of test
- Documentation is clear, but hopes people will never be forced to write it.
- The schema is missing a time element - has no ability to track time. Attribute note on overview page was confusing - wasn't sure what it meant. Doesn't think page numbers are needed. Ordering of elements in list (with C-class items at the end) makes sense.
- Fairly confident in ability to represent sustainability data with the schema.
- Gets confusing when elements are referring to other elements, but is fairly clear otherwise.
- Fix the 1.1 notes on output and input
- university is 1, not 1.0