Project creation: use multiple workflows?

[spwoodcock]

Based on feedback we have a clear use case for multiple project creation workflows.

We should probably ask some questions and let the user select a project creation workflow that suits them best, or channel them down that direction with questions.

1: Basic Projects

• Using default forms, default data extracts, FMTM splitter (probably not so common, mostly for inexperienced users).
• This is pretty much the existing workflow.

2: Custom Projects

• A more customised workflow where users can upload custom XForm, custom data extract, upload their own task areas or use FMTM splitter.
• More advanced use case, which is probably quite common for organisations already quite familiar with ODK XForms etc.

Allowing for custom XForms and data extracts makes data conflation with OSM much harder.

3: No Map Features: i.e. the E2E workflow

This will eventually tie into the other tools TM and Drone TM.

• A workflow where the features have not been mapped first.
• Common in developing countries.
• The user wants to create their task area, check if data extracts exist.
• (Optional) fly some drone imagery for task generation.
• Using tm-admin create a TM project for mapping and link to that.
• Once the mapping has been complete on TM (e.g. using fAIr or other tools), then:
  • Upload the validated polygons to OSM.
  • Mark the FMTM project as ready for the next step.
• Unlock the next stage in the project creation flow: get data extract from OSM and continue with task splitting etc.

[spwoodcock]

The customised workflow needs configuration for generating the data extract (via flags etc):

• geoms_within: a param to determine if only the geometries entirely contained within the bbox will be extracted. Note this is an issue for linestring geometries that often extend outside the bbox. Maps to the useStWithin param for raw-data-api.
• ... others

[spwoodcock]

• Including the E2E flow in FMTM is likely out of scope.
• FMTM will be linked to from a higher level E2E tutorial page, such as https://kshitijrajsharma.github.io/e2etemplate/
• I would propose instead that we need two workflows, that would be toggled between from the user checking a box:
  • Do you wish to skip the project creation guide?
  • By default this is unchecked = normal user.
  • Checking the box = advanced user.

Standard workflow, with tutorials / help

• Add a new workflow that is a variation on the existing flow.
• Add tutorials and links at each step, with suggested defaults and explanations of configuration parameters.
• This is a guided workflow to make it as easy as possible to create a project.
• This would remove the need to have separate user docs for project creation - they are embedded directly in the workflow.

Advanced workflow without guardrails

• Keep the existing workflow we have.
• Perhaps gets a few extra config params in future.

What do you think @manjitapandey @susmina94 ?

[spwoodcock]

Perhaps we can consider this for release 2024.04 or 2024.05

[spwoodcock]

Moved to milestone for 2024.5.0 release. Closing.