Shoaib Sufi
The Software Sustainability Institute runs many activities (e.g. Fellowship, Open Call, Workshops) that require asking questions about participants and collecting data. A consistency of approach in asking and collecting data will allow us to do better analysis in and across our activities making data collection more useful and analysis (more) comparable.
The CFQ documents the common questions we ask, reasons we collect them and applicability.
There are many reasons to ask questions and collect data for activities, some of these are 'good' reasons and some less so.
Good reasons to collect data:
- For our funders and supporters (demographic data around diversity, domain, career stage, funders and geographic area come into this category)
- To help us run activities effectively (participation and logistical questions come into this category)
- To collect information to change our behavior (e.g. to find our where gaps might be in supporting research software or topics for a future workshop)
Bad ideas to collect data:
- 'Just in case' data collection; one should have a clear understanding as to why one is collecting the data
In UK and the EU General Data Protection Regulation (GDPR) regulates organisations who collect, process and store personal data. In any case it is important to abide by any regulations around privacy you are bound by. For more information please see https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/. An additional thing to remember is that you should not be storing the data indefinitely and local retention schedules apply - please contact your organisational data protection officers for further information.
If you are collecting data to report back to funders, helping you run an event, or write a blog post with summary data then you will normally not need ethics approval from your institution/organisation. However, if you intend to use the data for research purposes you will likely need to go through any local ethical approval routes such that you can report your findings in a way that is acceptable to publications and your organisation.
- Raise an issue at - https://github.com/softwaresaved/common-form-questions/issues
- Discuss this with the Project Lead
- Have your proposed changes ready in the same format (see the *-questions.md files as examples); you could do this in a clone or a branch or just in the issue
- Submit this as a pull request - don't just commit / push (this allows time for review by the Project Lead or designate)
- Personal Information Questions(PIQ) - personal-information-questions.md - personal information questions
- Demographic Questions (DQ) - demographic-questions.md - demographich questions
- Engagement Questions (EQ) - engagement-questions.md - engagement questions
- Software and Skills Questions (SSQ) - software-and-skills-questions.md - software and skills questions
- Application Questions(AQ) - application-questions.md - information for collecting applications for competitive activities e.g. Fellows, Open Call etc
- Participation Questions(EPQ) - participation-questions.md - information gathering that drive the content of events
- Logistics Questions(ELQ) - logistics-questions.md - information gathered to help organise logistics of e.g. place, food and access.
- Feedback Questions (FBQ) - feedback-questions.md - pertains to feedback/evaluation/impact etc questions after events and competitions
- Ask Why Question (AWQ) - ask-why-question.md - the standard asking 'why' someone answered a particular way in a followup question
- Format of Questions (FQ) - format.md - contains the format used in the markdown files to describe the common questions
- Format of Questions Cheatsheet (FQCC) - format-cheatsheet.md - contains essential headings from format.md
Follow this flowchart to help you use the CFQ when constructing a questionnaire:
Form design, i.e. how to present the questions and the flow of questions etc to users is out of scope for CFQ. However we are providing some links (which we will occasionally update) around form design which maybe of use to the users of the CFQ when they construct their survey/questionnairie/forms. If you have any further suggestions please contact the Project Lead or follow the Change process.
- Simple but Crucial User Interfaces in the World Wide Web: Introducing 20 Guidelines for Usable Web Form Design - https://www.intechopen.com/books/user-interfaces/simple-but-crucial-user-interfaces-in-the-world-wide-web-introducing-20-guidelines-for-usable-web-fo
- Designing usable web forms: empirical evaluation of web form improvement guidelines - https://dl.acm.org/citation.cfm?doid=2556288.2557265