Open-End Coding quickly creates code frames to categorize text responses into categories (also known as codes), helping you gain valuable insights from your open-end data.
To access Open-End Coding, go to Analytics > Open-End Coding in the left navigation menu.
Overview
The Open-end Coding tool applies to non-numeric, open-end responses, for example text questions or "other specify" text fields.
- Open-End Coding is available to survey Makers and Researchers and users with the Open-End Coding add-on role.
- Code frames work with the latest published version of the survey, and are based on respondents with the status "C" (Completes).
- Code frames can be created manually or with AI. If code frames are manually created, AI is still used to automatically categorize the responses.
- Each code frame added creates a new field in the data. This is a multiselect variable by default, but this can be adjusted during the code frame creation process.
- The AI prompt can be edited as needed by clicking within the gray box.
- Users can edit, merge, delete, or add new codes at any time, even after responses have been collected.
- Users can view a high-level summary of coded results or a detailed view showing all responses and their assigned codes.
- "No qualifying codes" and "gibberish" codes are provided by default in all code frames. These two codes are mutually exclusive.
- Open-End Coding supports multiple languages, but each code frame generates categories in only one language. Read more about code frame and translations below.
- The code frame runs automatically once a day. Click Refresh to rerun it anytime.
Tip! To create a code frame within the source code, analyze responses for statuses other than "Completes", or reference the code frame as a variable in survey logic, see Automated open-end coding using SPL.
Creating a code frame
Select New Code Frame to get started. Create a code frame with AI or create your own.
Create with AI
Select the open-end field(s) to analyze. With AI, you can select multiple fields at once, each generating a unique code frame. You can also create multiple code frames for the same field if needed.
Create Your Own
Select the open-end field to analyze. When creating a code-frame manually, you must select one open-end field and build the code frame one at a time.
Enter code descriptions one at a time. Click + to add a new code.
Viewing and editing a code frame
Once a code frame is created, a high-level view appears on the landing page. Click a code frame to view results.
In the results view, use the toolbar to edit, download, or Refresh (recalculate) codes. Selecting the Edit option and at least one code allows you to merge, delete, add, or modify code descriptions.
Viewing all responses
Click View All Responses for a detailed view of code frame results at the response level. Click on any column heading to sort the results. Select Edit to modify the codes assigned to a response.
Code frames and translations
Code frames categorize open-end responses in the input language unless the autotranslate tag is applied. When the autotranslate tag is applied, codes are generated in the tag's specified language.
Scenario 1 - No 'autotranslate' tag
All text responses at Q1 are in Spanish. Reports store responses in a single field, with the native language captured at Q1. When creating the code frame, select Q1 to categorize responses, and the code labels will appear in Spanish.
Scenario 2 - 'autotranslate' is applied
Some Q1 responses are in Spanish, others in English, and the autotranslate tag is applied and set to English. Reports store responses in two fields: the native text at Q1 and the English translation at Q1_english. When creating the code frame, select Q1; it will pull translated text from Q1_english, and code labels will appear in English.
Even if all responses are in Spanish, still select Q1. With the autotranslate tag set to English, the system still uses Q1_english for translated text, and code labels appear in English.
Comments
0 comments
Please sign in to leave a comment.