spwoodcock
commented
4 months ago To facilitate this I think we should update the project creation flow.
Current:
- Org admin creates entire project.
Proposal:
- Org admin create a project stub with minimal details, assign a project admin
- Requires a new endpoint
/project/stub/(or perhaps reuse/projectPOST endpoint.
- Requires a new endpoint
- Project admin fills out details and submits. This calls the project update endpoint, which is by default idempotent.
- The project update will fill out the remaining fields.
- For this to work, we probably need a flag in the db to determine when a project is full filled out, or only a stub.
Advantages of this approach:
- Idemponent: project creation can be repeated without issues.
- Reduce code duplication: the editing workflow can be the same as the project creation.
- Permissions: better to pass main project creation responsibility to project admin.
- Ordering: project is created prior to data extract, meaning we can include project id in the data extract file name.
- This allows for data extract tracking by HOT in production.
Is your feature request related to a problem? Please describe.
Task creation may fail due to various reasons not related to incorrect input (server overload, db connection limit, etc).
Describe the solution you'd like
The project files generation should be idempotent.
This means that there are checks to see which tasks have an odk token, form in odk central and uploaded geojson media.
It would increase the time of the endpoint due to additional calls, but worth it to allow multiple sequential executions, i.e. resume.
Describe alternatives you've considered
An additional endpoint to resume, but it would be nice to have the same one.
@manjitapandey