Our interviewers will use an external telephony provider to conduct CAWI/CATI surveys. The provider will make audio recording available as download.
How do we upload the recording to Survey Solutions HQ and attach it to the interview?
We would like to do that with API, or manually either by the interviewer or by HQ operator admin/supervisor.
I saw a similar feature request, but there is no update to it.
Out of curiosity: What do you you use Survey Solutions for? Based on your request it seems you are doing the interview in a different software anyway?
In case you are doing a seperate (but related) interview with the observation within Survey Solutions: Why the need to upload it to the Headquarter Application? Do you need the audio file for reviewing a Survey Solutions interview? My gut feeling: The application itself is for collecting (&exporting) data, and not a data storage location. Consider building an external “tool”/system where you can link data sources.
We are going to do a nutrition examination survey (CAWI+CATI). We will use Survey Solutions for questionnaire entry, assignments and QA. The audio audit is required by QA. We need to attach the recording to the interview for direct access & referencing instead of using two apps.
I second @peter_brueck 's suggestion: build a separate tool.
Here’s the scope I see:
Download data. You would need both the microdata and audio data.
Move audio files into a file system. This could be the file system created by extracting the export archive downloaded from the server. This might also be a new file system where all audio files (for all versions of the questionnaire) are in sub-folders of the same folder.
Create a document of interviews to review that contains links to the interview on the server (i.e. URL of interview) and to the audio file in your file system. For the interview on the server, the link would be {your_server_url}/{your_workspace}/Interview/Review/{interview__id}. For the audio file, this would be some file system where the file could be located with interview__id.
Just some quick thoughts.
If you end up implementing this, I’d love to hear what you’ve done. This has been something in the back of my mind for awhile, but without an immediate uses case I’ve not done any development.