Example Surveys
From skylightwiki
Contents |
Simple Survey (One Author, one group of respondents)
The simplest survey involves one author sending a survey to one group of respondents by providing the respondents a single shared URL. ( These pages will walk you through the process )
Matrix Surveys
Matrix Survey Explained
A "matrix" survey is a survey structure that combines more than one respondent pools with one or more groups of questions. A simple survey is a degenerate case of a matrix because it uses one respondent pool and one group of questions.
Multiple Groups of Respondents
Groups of individual respondents are called "Respondent Pools." There are several reasons to administer the same survey to multiple respondent pools:
- To track the responses by group (e.g., the same survey adminstered to ENGL 101 and ENGL 425)
- To track the responses of one group over time (e.g., the same survey administered to the same respondents at several points during a semester)
- To administer the survey by different mechanisms to different groups (e.g., one group gets the survey by email, another group gets a single URL that all respondents use) ( see: Delivery Modes )
- To provide different reports to different individuals (e.g., each course's sub-reports could be access by the that course's instructor, and the overall data accessed by the Institutional Research department.) When a survey is administered to multiple respondent pools, the data can be viewed in a single report spanning all the groups, in a report per group, or in a custom report for some sub-set of all the pools.
Any or all of these administration mechanisms can be used at one time in a single survey. ( Learn More )
Additional Questions for Some Responent Pools
When there are multiple respondent pools, it may be desirable to administer additional questions to some pools. For example, all courses are asked a common set of questions, and all courses taught at a distance are asked some additional questions about the distance services.
The advantage of providing the additional questions within one survey is that the data for all respondents can be reported together, as well as broken out by Respondent Pool.
Multiple Groups of Authors
In the administration of a large survey, for example, all courses in a College, it may be desirable to distribute some of the responsibility for question authoring, especially in situations where some respondent pools will be asked different questions.
Author Groups can be created and assigned to create additional questions that will be administered to specific Respondent Pools ( Learn More )
Example Applications of Matrix Surveys
End of Term Course Evaluations
Presumptions that govern this analysis of an course evaluation survey application:
- Students are registered and known prior to the survey
- Each student should respond only once per course they are taking
- Survey should be anonymous
- Instructors may wish to add additional questions for their own class
- Reports are needed for the instructor, and summary reports are needed by the Department or College
- and in the advanced case
- Students might be ogranized into several groups for logistical reasons (e.g., by course)
- Students might see different surveys based on either group or individual metadata (e.g., different survey for courses with labs or taught online, and/or different survey for students who took the course as an elective or a requirement.
Simple Case
Advanced Case
Longitudinal Study
Alumni Survey
Presumptions that govern this analysis of an alumni survey application:
- Alumni are known prior to the survey
- Each alumni should respond only once
- Survey could be anonymous or not, depending on needs
- and in the advanced case
- Alumni might be ogranized into several groups for logistical reasons (e.g., by college or degree earned)
- Alumni might see different surveys based on either group or individual metadata (e.g., different survey for graduates of different colleges, and/or different survey for graduates with BA vs PhD.
Simple Case
Advanced Case
Election
Presumptions that govern this analysis of a voting application (see Example:
- Voters are registered and known prior to the election
- Each voter can vote once
- Votes cast are anonymous
- and in the advanced case
- Voters might be ogranized into several groups for logistical reasons (e.g., precincts)
- Voters might see different ballots based on either group or individual metadata (e.g., different candidates might be on the ballot for different precincts, and/or different candidates might be on the ballot based on voter party affiliation (ie, Democrat/ Rebublican).
Simple case A Registrar would create a list of voters. This list would enumerate each voter, and if email delivery were desired, would contain the voters' email addresses. (see Simple Survey)
The survey would be constructed, with start/stop dates, and the voter list uploaded. The system will create a unique URL per voter, which is then delivered by the system to the voter's email address (or downloaded by the Registrar and distributed by 3rd party means, depending on delivery mode chosen). The system will allow the voter to take the survey (vote) one time, and when the voter "finishes" the survey, the system would mark the voter's URL "used," preventing duplicate votes by the voter. The system would also break the linkage between the voter's idenitfying information and the vote cast.
Advanced case The Registrar would create multiple voter lists, with metadata associated with each list (see Multiple Groups). These multiple lists would be uploaded by the Registrar. Ballots (surveys) would be constructed with different ballot items (questions) to be administered to different groups of voters (see Multiple authors). When the voter uses their unique URL, the system would assemble the ballot (survey items) for the voter, based on the metadata.