Depending on the coding approach, researchers might also create a codebook or research notes for each code that defines the code and specifies instances in which the code should be applied. Researchers will often change, lump together, split, or re-organize codes as they analyze their data.
Some software packages allow the researcher to visualize codes and the relationships between them in new and innovative ways however, a cursory review of the literature suggests that qualitative researchers often use very basic features some even use software such as Endnote on Microsoft Word or even analog systems such as paper or sticky notes. Perhaps more importantly, software allows easy visualization and analysis of where codes co-occur (i.e., where multiple codes have been applied to the same snippets of text), and other linking activities that help researchers identify and specify themes in the data. Using software for QDA allows researchers to nest codes, then begin to see the number of instances in which a particular code has been applied. This approach is common toward the end of the process in fields such as organization studies, management, and other disciplines and is prominent as an approach from the beginning in fields with experimental or clinical roots (e.g., psychology). Sometimes the QDA process involves looking for instances that demonstrate some concept, mechanism, or theory from the academic literature on the subject. Later rounds involve conflating codes that might mean the same thing, relating codes to one another (often by documenting their meanings in a similar way to software documentation), and eliminating codes that no longer make sense. In another round, she might get even more specific with codes such as "conversation_package_nomoney" if a participant discussed not having money to create a package in R. For instance, if the researcher is coding observation notes and senses that conversations between two individuals will be relevant to the research questions, she might tag the instances in which the two individuals speak with the code "conversation." In the next round of coding, she might classify what the participants discuss with a finer tag, like "conversation_package" if they were talking about creating packages in R.
The researcher starts with open coding, meaning that she is free to tag snippets of text with whatever descriptions she deems appropriate. Qualitative data analysis (QDA) processes, particularly those developed by Corbin and Strauss (2014), Miles, Huberman, and Saldana (2013), and Glaser and Strauss (2017), can be thought of as layering interpretation onto the text. Textual qualitative data refers to text from interview transcripts, observation notes, memos, jottings and primary source/archival documents. The motivation stems from the need for a free, open source option for analyzing textual qualitative data.
update_links: Update document to unit links Saves or updates the links.txt2html: Format text as HTML Minimal conversion of a text to html.reexports: Objects exported from other packages.read_unit_document_map_data: Create a data frame of unit to document links from csv file.read_unit_data: Create a data frame of units from csv file Use this is you.read_documents_data: Create a data frame of documents.read_data: This launches the data-reader Shiny app.read_code_data: Create a file of codes from csv file Use this if you have a.qcoder-package: Code Qualitative Data A light weight approach to qualitative.
qcode_custom: This launches the coder custom Shiny app.qcode: This launches the coder Shiny app.parse_splititem: Parse a single item within a document.import_project_data: Read data into a project Convenience method to read raw data.get_codes: Extract codes from text Take coded text and extract the.do_update_document: Update document Updates the text field of the documents data.create_qcoder_project: Create a standard set of folders for a QCoder project.create_empty_units_file: Define an empty units data frame.create_empty_unit_doc_file: Define an empty many to many unit to document map.create_empty_docs_file: Create an empty documents data set.create_empty_code_file: Create an empty codes data set.
build_paths: Build the paths for file creation.add_unit: Add unit Append a new unit record to the existing data frame.add_new_documents: Add new documents Adds new document or documents to an.add_discovered_code: Update codes data frame Add discovered codes to the codes.add_codes_to_selection: Adds codes surrounding the selected text.add_code: Add code Append a new unit record to the existing data frame.