Toggle navigation
Home
▼ Details
Products and pricing
Chart gallery
User stories
Text analytics
CDC NAMCS Library
Blog
Tutorials
Contact
Sign in
Post Editor
← All help posts
View post
Save
## Recoding raw open-ends in trackers ### Add new codes instead of renaming previous codes Make sure to add new codes to the existing code frame versus renaming previous codes. Renaming old codes might causes confusion when looking back at the results from previous waves. <img src="/uploads/upload/image/5200/direct/1688388897988-1688388897988.png" alt="Side-by-side comparison of two coding approaches in Protobi's Advanced Recode tool. The left panel labeled 'Codes' shows existing code categories (#EASY TO USE with 42 responses, #GOOD with 18, #NOT EASY with 15, etc.) with a '(New code)' button at the top for adding new codes. The right panel labeled 'Uncoded values' displays a search bar and raw open-end responses that haven't been assigned codes yet, including responses like 'good', 'interesting, should be easy to use', 'Good. Positive', and longer verbatims about elderly patients and product features." width="732px" class="fr-fic fr-dib"> ### Make sure you're coding values from the current wave In the past, users have reported changes to the results of previous coding after they code values in the most recent wave. This can happen if there are stray uncoded values from previous waves, and users do not code the values until a later wave. **Code current wave from simple recode tool** To check that all uncoded values are from this current wave, filter on the current wave and view uncoded responses from the [simple recode dialog](/edit-access/simple-open-end-recoding). You can filter using [press to query](/view-access/click-to-query) or [global filters](/view-access/global-filters). **Code current wave from advanced recode tool** The advanced recode tool does not adhere to filters within the project. If you prefer to use the [advanced recode tool](/text-open-end-questions/reformat-tool-advanced), set the current wave's data file as the [Primary](https://help.protobi.com/en_US/admin-access/project-data#What%20does%20%22Primary%22%20mean?-1) source for the project so that you only see the current wave's uncoded values. ## Additional open-end topics ### Create hierarchical code frames to show different levels of detail You can use the element attribute to create hierarchical code frames to organize codes based of different levels of detail. The element attribute takes the final post-calculation value from one element as the starting value for another element. In the example below, Q7\_recoded2 uses the coded results from Q7\_recoded as the input to a broader level code frame. <img src="/uploads/upload/image/5200/direct/1684262169794-1684262169794.png" alt="Protobi interface showing two-level recoding workflow. Left panel 'Q7_recoded' displays detailed codes with percentages: #EASY TO USE (42.0%), #GOOD (19.0%), #NOT EASY (15.0%), #ECO-FRIENDLY (14.0%), #DOSE INDICATOR (9.0%), #SIMILAR (8.0%), #COST EFFECTIVE (6.0%), #OTHER (3.0%). Right panel 'Q7_recoded2' shows broader sentiment categories: #POSITIVE SENTIMENT (78.0%), #NEGATIVE SENTIMENT (23.0%), #OTHER (3.0%). Properties panel shows Q7_recoded2 element field references Q7_recoded as source." class="fr-fic fr-dib"> The values in Q7\_recoded2 are the already recoded values from Q7\_recoded. I then recoded the existing codeframe into broader sentiment categories. <img src="/uploads/upload/image/5200/direct/1684261769313-1684261769313.png" alt="Protobi Advanced Recode interface showing sentiment code grouping. Left 'Codes' panel displays two expandable groups: #POSITIVE SENTIMENT (5 codes) containing #COST EFFECTIVE, #DOSE INDICATOR, #EASY TO USE, #ECO-FRIENDLY, #GOOD; and #NEGATIVE SENTIMENT (2 codes) containing #NOT EASY, #SIMILAR. Right 'Uncoded values' panel shows only #OTHER (1 response). Blue '(New code)' button at top for creating additional codes." width="530px" class="fr-fic fr-dib"> See [Set up open-end questions for easy recoding](/text-open-end-questions/set-up-open-end-questions-for-easy-recoding) to learn more. ### Display open-ends in a grid that shows both raw and coded values The view below is Protobi's [Verbatim chart](/text-open-end-questions/crosstab-raw-text-with-coded). The chart allows you to see the coded categories and the raw open-ends that belong under each code. <img src="/uploads/upload/image/5200/direct/1604409689256-1604409689256.png" alt="Protobi Verbatim chart displaying coded open-end responses in grid format. Header shows 'Q7 by Text coding' with search bar. Column headers show codes: #COST EFFECTIVE (N=5), #DOSE INDICATOR (N=9), #EASY TO USE (N=42), #ECO-FRIENDLY (N=14), #GOOD (N=19), #NOT EASY (N=15), #OTHER (N=3), #SIMILAR (N=8). Grid cells contain actual verbatim responses under each code category, allowing reviewers to see raw text grouped by assigned codes."> See [Display open-ends in a grid that shows both raw and coded values](/text-open-end-questions/crosstab-raw-text-with-coded) to learn more. ### Turn raw open-ends into word clouds Word clouds are a good way to quickly visualize the main themes in the raw responses without recoding the values. The more often a word was mentioned, the bigger the font will appear. You can choose a min and max font size for your chart and right click to select words that you want to exclude from view. <img src="/uploads/images/image-open-end-recoding-in-tracker-projects-2025-02-24-15-39-54.37.00 PM.png" alt="A word cloud visualization showing feedback about a medical device, with prominent terms like 'easy', 'patients', 'use', 'good', and 'device' in varying sizes." style="max-width: 400px"> See [Word clouds](/text-open-end-questions/create-word-clouds-in-protobi) to learn more on how to set up this chart type. ### Append separate open-end data to your project Often times raw open-end data might be in a separate file or you engaged another vendor to code the open-ends and you want to integrate the coded results into the Protobi project. Within Protobi you can add additional data as a new data table and use process code to join the open-end and main survey data files. <img src="/uploads/images/image-open-end-recoding-in-tracker-projects-2025-02-24-15-40-24.09.15 PM.png" alt="Protobi project settings interface showing three main sections: Data tables, Processes, and Documents, with a navigation menu on the left." style="max-width: 400px"> The example code below merges the auxiliary open-end data to main survey data in a Protobi data process. The left join function merges **two files** only - the "main" dataset (left table) and the new "OE" dataset with the coded open-ends (right table). The keys are used to match the new data with the rows of data in the left table. ``` var rows= data["main"] //primary data file var OE = data["OE"] //auxiliary data file // Keys are used to identify the respondent row to append the new data to var keys = ["respid"] rows = Protobi.left_join( rows, //left table (project's existing data) OE, //right table (data to be joined into project) keys, //join keys Object.keys(OE[0]) //All variables from the right table ); ``` See [Join additional data to your project](/process-data/tbd-csv-left-join) for more info.
Publishing
Date
Status
Published
Draft
Slug
edit
Content
Thumbnail
Categories
Manage
New to Protobi?
Charts
Making Changes
Intermediate topics for editors
Frequently Asked Questions
SERMO Topics
Tutorial Pages
Internal Docs
Data Processing
Videos
Obsolete
GSG Admin
SERMO Admin
GSG Topics
How to...
Basics for viewers
Basics for editors
For project admins
Advanced topics
Assessments
Articles (in-progress)
New and updated articles
Process data in Protobi
superseded
Text open-end questions
Troubleshooting
Tracking studies
Organizing the view
API References
Tools
AI Database
Checking AI...
Convert to MD
Danger zone
Delete