Background:
This project will need to take into consideration the fact that end users are not likely to have the patience, training, or inclination to work directly with the database. The experience in the UI then needs to help bridge this gap.
Problem:
End users will be disinclined to use this tool if it is not accessible, does not make their life easier (i.e.: expedite research), and does not have a clean set of interaction workflows. The brunt of that experience will exist in the UI.
Success Criteria:
An initial pass at the possible usage operations and visual features (query, results display for searchable and non-searchable attributes, reset, export, etc.) has been performed and these use cases are documented in the wiki.
A mockup of the UI for each of the operations exists.
A mockup of the UX workflow which ties each of these operations together exists.
Notes:
Only simple UI diagrams (MS Paint sketches, MS Visio, LibreOffice Draw) are needed for this so that there is something to examine usage assumptions against. If this would be easier to visualize directly in the UI toolset defined in #7, then we should do so to avoid time sinks.
Followup Questions:
Should we create a set of tooltips to help guide users?
What sort of helpfile documentation should be created for this?
Background: This project will need to take into consideration the fact that end users are not likely to have the patience, training, or inclination to work directly with the database. The experience in the UI then needs to help bridge this gap.
Problem: End users will be disinclined to use this tool if it is not accessible, does not make their life easier (i.e.: expedite research), and does not have a clean set of interaction workflows. The brunt of that experience will exist in the UI.
Success Criteria:
Notes:
Followup Questions: