Workflow: We should update the UX to make it clearer which steps are mandatory, which
compulsory and how far we are through the setup process.
Use implicit naming of outputs. It would be better to autogenerate the outputs into the outputs
folder using a standard naming convention like tab_name.tif e.g. care_responsibilities.tif. Same for
the aggregate outputs:
13 would become e.g. group_name_aggregate.tif e.g. individual_aggregate.tif
We propose to address all of these issues with a complete overhaul of the workflow. The new
version would use a stateful tree metaphor:
14 The user activity would be centered around populating the bottom level nodes of the tree. Where
layer metadata exists, these would be auto-populated for applicable layers.
The workflow would be split into three phases:
1) Assiging layers to tree nodes (with auto assignment where possible)
2) Preparing intermediate products. We will include logic here to only allow the prep phase to
commence if adequate layers are present for the analysis.
3) Analysis – this would be an interactive environment for exploring the aggregates and insights
outputs.
Estimated time required:
3 Weeks: UX overhaul with tree metaphor and ‘smart logic’ for when adequate data is available.
152 Weeks: Implement prepare phase logic with fault tolerance, background processing, statefulness
(e.g. ability to resume from last checkpoint after a QGIS restart)
2 Weeks: Implement the aggregates and insights explorer
1 Week: Overhaul the context help system
1 Week: Writing a comprehensive test suite
1 Week: Developer documentation and project house keeping
Review the workflow, the tabs in tabs metaphor breaks standard UX (see e.g. https://uxplanet.org/designing-perfect-tabs-2c0aaf835bfc)
Use better default for resolution
Workflow: We should update the UX to make it clearer which steps are mandatory, which compulsory and how far we are through the setup process. Use implicit naming of outputs. It would be better to autogenerate the outputs into the outputs folder using a standard naming convention like tab_name.tif e.g. care_responsibilities.tif. Same for the aggregate outputs: 13 would become e.g. group_name_aggregate.tif e.g. individual_aggregate.tif We propose to address all of these issues with a complete overhaul of the workflow. The new version would use a stateful tree metaphor: 14 The user activity would be centered around populating the bottom level nodes of the tree. Where layer metadata exists, these would be auto-populated for applicable layers.
The workflow would be split into three phases: 1) Assiging layers to tree nodes (with auto assignment where possible) 2) Preparing intermediate products. We will include logic here to only allow the prep phase to commence if adequate layers are present for the analysis. 3) Analysis – this would be an interactive environment for exploring the aggregates and insights outputs.
Estimated time required: 3 Weeks: UX overhaul with tree metaphor and ‘smart logic’ for when adequate data is available. 152 Weeks: Implement prepare phase logic with fault tolerance, background processing, statefulness (e.g. ability to resume from last checkpoint after a QGIS restart) 2 Weeks: Implement the aggregates and insights explorer 1 Week: Overhaul the context help system 1 Week: Writing a comprehensive test suite 1 Week: Developer documentation and project house keeping