janagombitova
commented
7 years ago As a 1st implementation step we have decided to:
- make it easier to copy a survey from one instance to another by not having to manually create the survey and paste all forms in it, but by copying the survey as a package
- keep this action as a Akvo support service handled by the 2nd line support team in order to cross check that all attributes of the survey were copied in properly (survey settings, options, etc)
- create an easy way for Akvonauts and users to request a survey to be copied across instances
- not support copying of translations
- not deal with copying of cascade resources - those need to be created (or uploaded) separately, published and added to the survey
Learning points
What we aim to learn with this implementation is:
- how many requests do we receive?
- what is the nature of these request? Do they happen because the partner first used a different instance? Is it about sharing a survey across partners? Standard surveys?
- does the user want to be more independent in uploading surveys from other Flow instances? or does the support suffice?
- survey library?
After the implementation is released we will set a timeframe when to evaluate the learnings and see how to move forward.
Overview
Being able to copy a survey from one dashboard to another has strong value.
We already have cases when a partner creates a survey in one of Akvo's demo dashboards and then wants to reuse it in their own dashboard. Currently, either the dev team needs to copy and upload the survey in the backend, or the survey needs to be recreated manually in the new dashboard.
Furthermore, we have experienced situations where standardised surveys are used across organisations (e.x. certification standards, SDGs, or questionnaires used for disaster response) who have their own dashboards. At this moment there is no way for an organisation to share its survey structure with other partners and for the partner to in a simple way add it to their dashboard.
Thirdly, with Flow we help partners with their data collection exercises to collect good data in an easy way. We support them in analysing and understanding their data with our other tools. But we do not cover the 1st step before the data collection - building and designing a good survey. This is a very important part because without a good survey, you cannot collect good data. By making it possible to share surveys we can support knowledge exchange and improve the data collected.
Implementation ideas
We have heard partners asking for a 'library' of survey, or a portal where they can share and reuse surveys publicly. This is a larger feature. By simply making it possible for our users to download a survey from one dashboard and to upload it to another one, we can cover the basic requirements.
Known issues:
How to handle cases:
Links to documents
User stories, background and notes from discussion https://docs.google.com/document/d/1W28dh7kCPP46Mk31N6VUNGE_RutR2W1wU6lminGTX9Y/edit