60 likes | 146 Views
UES ‘ Autocoder ’. Vision for the autocoder …. We are aiming to create an autocoder that is Useful Accurate Flexible, and Cost effective (for build and updates)
E N D
Vision for the autocoder… • We are aiming to create an autocoder that is • Useful • Accurate • Flexible, and • Cost effective (for build and updates) • The framework and core programming for the autocoder should work across all related surveys with an annual update of the codebook
What does this mean in practical terms… The autocoder will be able to • Code large volumes of verbatim material (approximately 118,000 records for the UES) • Create an output that can be uploaded to the National or Institutional data files as coded numeric responses • Support codebook customisation at an institutional level • Display coded data in the form of frequency tables and customised charts, and • Allow full access to the complete, coded verbatims. Footer Text
‘Platform’ To address functionality issues associated with previous customised approached to the coding of qualitative data, a new tool has been designed in Microsoft Excel using Visual Basic Automation. The tool consists of two elements: • a macro-enabled Excel template; and • a codebook for each open ended question. Footer Text
Coding process In very general terms, we use a two stage process to code the UES data: • Bottom-up grounded theory approach where responses are explored and coded by the qualitative team • Top-down application of the UES constructs to the resulting thematic groups Footer Text
Approach to codebook build Footer Text