When creating your codebook in Fora Insights, you will want to define each code that you enter. Both parent and child codes should have definitions. Definitions make it easier for all sensemakers to tag highlights with the same understanding of the meaning of each code. Definitions will also help you understand where similar themes or sentiments are found throughout your collection, and allow for you to consolidate your codebook later to reduce semantic redundancies and sharpen your analysis.
The definition for each code should be entered in the description box, as shown below.
Definitions for each code should be about one sentence long, succinctly describing what the code means in the context of your project.
Suggestions for Defining definitions as a team.
When deciding how to define codes as a team, you can consider these approaches. Every team is different, but in the past other partners have defined codes in various ways.
- List all codes in a Google document and assign codes to your team members for defining. Review all the definitions together to edit them and make sure you agree on each definition.
- Use an online whiteboard platform (like Mural, Miro or Jamboard) to brainstorm definitions for your codes
- Create a Google spreadsheet organizing each code into families and define them in the sheet.
- Write definitions for all the codes as you enter them into Fora Insights
Remember: If you are using another online platform to define your codes (ex: Google Docs/spreadsheet), make sure to copy and paste the definitions you created there into the description field on Fora Insights.
Note: Definitions are not visible on the Portal. However, you will have a chance to write descriptions of your code families in a different format for your Portal.