[Create/edit survey] Allow organizers to create and apply survey templates

[rfontanarosa]

To improve survey creation efficiency and reduce redundancy, we propose implementing a survey templating system.

Allow users to designate any existing survey as a template during creation or via a dedicated action in the survey list view. This could be achieved by adding a checkbox or a dedicated "Save as Template" toggle.

Enable users to create new surveys from existing templates. When creating a new survey from a template, the system should copy:

• Survey metadata (name, description, integrations)
• Job structure (name, tasks)
• Exclude Location of Interests (LOIs) and Access Control Lists (ACLs)

[gino-m]

@lecrabe Mentioned that template can also be used by new users to test the app - new users can quickly use a public template to create a private survey for testing.

[kenstershiro]

Gregory Sampson, from WTO ITC also has a use case for this - create the same survey type for multiple different farmers. Same survey but different ACLs for each (each survey is shared with a single farmer). Current cloning doesn't allow different LOIs.

[gino-m]

Gregory Sampson, from WTO ITC also has a use case for this - create the same survey type for multiple different farmers. Same survey but different ACLs for each (each survey is shared with a single farmer). Current cloning doesn't allow different LOIs.

As far as I know, you can currently only clone jobs, not surveys. @rfontanarosa has a manual script for doing that, but nothing user facing.

@kenstershiro I assume templates should be public? Who can create templates, and how do we prevent random users from creating garbage or offensive templates?

[kenstershiro]

@kenstershiro I assume templates should be public? Who can create templates, and how do we prevent random users from creating garbage or offensive templates?

@gino-m one idea might be to allow users to create new templates themselves, and share with the same level of permissions that they have currently to share/invite surveys.

[gino-m]

@kenstershiro I assume templates should be public? Who can create templates, and how do we prevent random users from creating garbage or offensive templates?

[@gino-m](https://github.com/gino-m) one idea might be to allow users to create new templates themselves, and share with the same level of permissions that they have currently to share/invite surveys.

This would add a bit of complexity in the web UI and the web and Android implementations, so should be considered carefully. @lecrabe also wanted a template visible to everyone so that new users can quickly create a survey, so you'd also need to add a way to set a survey template to be available to "all users".

Would WTO ITC be ok with their templates being accessible to all Ground users? That make it easier to roll out an MVP.

[kenstershiro]

Question on workaround using cloning of surveys, and using public surveys for cold start issue.
Could be some relation to the FR to provide a test survey, and/or providing a starter sample survey to personalise and get started.
Could be task templates rather than entire survey templates? Do we need to clone LOIs? Task creation would need to include option to start from a template or start your own.
Suggestion to start with templating tasks only as first step, with limited number of public templates (could be achieved through public surveys which are cloneable and visible)
Possible follow up on providing options like land cover classes (separate issues on this)

[kenstershiro]

P0 for public surveys (for training) - #2121
P1 for copying any survey - #2122