Adjudication
Quality and rigourSettling disagreements between coders, by discussion or by a third person, so that each contested passage ends with one agreed code.
Also known as: consensusreconciliation
Clear explanations of qualitative research and Byleron QDA concepts.
Settling disagreements between coders, by discussion or by a third person, so that each contested passage ends with one agreed code.
Also known as: consensusreconciliation
A p-value corrected for making many comparisons at once. Without correction, some differences look significant purely by chance.
Also known as: corrected pmultiple comparisonsp-value
The optional AI features: suggested codes and passages, selected-text help, and Chat with Data. You decide what is sent and what to accept.
Also known as: AI codingAI provider
A set of suggested codes and passages produced by the AI Assistant. A draft is provisional: nothing becomes coding until you accept it and finalize.
Also known as: AI assistant draftprovisional coding
The area where you look at your coding as tables and figures. It is grouped into Overview, Variables, Evidence, Relations & Maps, Frequencies & Comparison and Rigour.
Also known as: analysis menu
A note on what a code is for: substantive (it carries meaning you analyse), descriptive (it records a feature such as who is speaking) or unspecified. Subcodes take the role of their parent unless you change it.
Also known as: code role
Removing or replacing details that could identify a participant. Anonymization removes them so they cannot be recovered; pseudonymization replaces them, for example with a code name, so that a separate key could restore them.
Also known as: anonymisationpseudonymde-identification
A record of what was done and decided during an analysis, so that others can follow how conclusions were reached. In Byleron QDA the project activity list records actions such as coding, merging codes and writing memos, with dates.
Also known as: activity logdecision trail
A copy of your project saved outside the workspace. A JSON export keeps everything Byleron QDA stores; a QDPX export is for other qualitative programs.
Also known as: JSON backupproject export
A search that combines words with AND, OR, NOT and NEAR so that you can find passages by a pattern of words. Results are shown with the words around them (keyword in context) and can be coded all at once.
Also known as: KWICkeyword in contextquick search
The unit you describe or compare, such as a participant, a family, a school or an organisation. In Byleron QDA a document usually stands for a case, so comparing documents compares cases.
Also known as: cases
A network that joins each case to the codes used in it. It shows which cases share ideas and which ideas stand alone.
Also known as: case-theme network
An AI assistant that answers questions about your documents and points to the passages it drew on. Its answers are leads to check against the text, not findings.
Also known as: data chat
A test of whether two categories, for example a group and the presence of a code, are related more than chance would explain. It is unreliable when expected counts are small, and Byleron QDA marks such cells.
Also known as: chi squareχ²test of association
A branching diagram that groups codes or documents by how similarly they are coded. Items on the same small branch are coded alike. The grouping depends on the settings you choose, so read it as a suggestion.
Also known as: dendrogramhierarchical clustering
Co-occurrence records two codes meeting the selected Same document, Overlap or Nearby rule. Qualifying sources counts sources once; coding-assignment pairs can count several matches within one source. Read the evidence to interpret the relationship.
Also known as: cooccurrenceco-occur
A short label for an idea, topic or concept found in the data, together with the passages coded with it. A code should have a definition so that it is applied the same way each time.
Also known as: codes
Which code tends to follow which in the order of a document or a conversation. It suits questions about sequence, such as what comes after a complaint.
Also known as: sequential adjacencytransition network
A written statement of what a code means, often with when to use it and when not to. Good definitions are what make coding repeatable, and they are what an AI assistant or a second coder relies on.
Also known as: include whenexclude wheninclusion criteria
A line showing how many new codes appear as you work through the documents in order. If it flattens, new documents are adding few new codes. That is a useful signal, not proof that nothing more can be found.
Also known as: saturation curve
The layered structure of codes: broad codes at the top, more specific subcodes beneath. A hierarchy helps you see how ideas group into larger themes. Byleron QDA allows up to ten levels.
Also known as: code treecoding frame
A written comparison for one code across files: what the files share, how they differ and any exceptions. You can write it at any time, once the code has coded text in at least two files.
Also known as: topic summary
The complete list of codes in a project with their definitions and structure. A clear codebook makes coding consistent over time and between coders, and it can be exported and imported.
Also known as: code systemcoding scheme
A passage, image region, frame or time range that you have coded. It is the material a code is based on. In Byleron QDA every coded item can be reopened in its document.
Also known as: evidencecoded segmentsegmentpassagequotation
The Analysis view that lists every coded passage for a code, with its document and location, so you can read what sits behind a count.
Also known as: evidence explorer
Attaching a label, called a code, to a passage of data so that everything about one idea can be found and compared later. Coding is an interpretive step: the label states what you think the passage is evidence of.
Also known as: to code
One code applied to one selected passage, region or range. The selection is the passage itself: a passage with three codes is one selection and three assignments, which is why counts of assignments and counts of selections can differ. Counts in Byleron are counts of assignments unless a screen says otherwise. A parent code's count adds the assignments of its subcodes, so it counts assignments, not different passages.
Also known as: assignmentselectionselections
A measure of agreement between two coders that corrects for the agreement expected by chance. A value near 1 means strong agreement; a value near 0 means agreement no better than chance. What counts as acceptable depends on the study.
Also known as: kappa
Working on one project with other people. The owner invites collaborators, and roles decide what each person can see and change.
Also known as: shared projectcollaboratorcoderco-coder
A comparison of how codes are used across groups defined by a variable, for example teachers and students. With small groups, differences may be due to chance, so treat them as leads to check in the text.
Also known as: group comparisoncross-tabulation
A method that sorts material into categories according to explicit rules and, in some forms, counts how often each category occurs. It suits questions about what is said and how often, and it depends on clear code definitions.
Also known as: qualitative content analysis
A parent code's total includes the evidence of all its subcodes. Its direct count is what was coded on the parent itself.
Also known as: rolled-up countdirect countrolled up
The share of a document's characters that carry at least one code. Passages that overlap are counted once, so coverage never exceeds 100 %. Only text selections are measured; files coded only by time ranges or regions are left out and reported. Coverage describes how much of the text has been coded. It does not measure analytical completeness, quality or the importance of a code.
Also known as: text coveragecoded share
A number from 0 to 1 that says how strong an association is, independent of sample size. A significant test with a tiny V is a real but weak pattern.
Also known as: Cramers Veffect size
Your project content stays yours. Byleron QDA stores it to run the workspace, and you can export it at any time.
Also known as: your datacontent ownership
Applying codes decided in advance, drawn from theory, earlier research or a research question, to the data. Codes can still be refined when the data do not fit.
Also known as: concept-driven codingtop-down coding
Coding assignments (text) per 1,000 characters of a document. A passage with several codes, and overlapping passages, are counted separately. Density describes how much coding activity a document has received, not how much of its text is coded; coverage does that.
Also known as: coding assignments per 1,000 characters
How coding is spread across documents and codes: whether an idea appears in many sources or is concentrated in a few.
Also known as: code distribution
One item of material in a project: an interview transcript, a report, a survey export, an image, a recording or a video. In Byleron QDA each document is added as a file and can be read, coded and given variables.
Also known as: filesourcedata source
A short display name for a document built from a prefix, its number and chosen variables, for example P3 · F · Tea. It changes how documents are named in figures and tables without renaming the files. Labels belong to the project, and only the owner can change them.
Also known as: labelsP1participant label
The percentage of documents in a group that contain a code at least once. It shows how widespread an idea is across cases, not how much of it there is.
Also known as: presence
Coding by selecting a passage and dragging it onto a code in the code list, instead of choosing the code from a menu.
Also known as: drag coding
A table with one row per file and one column per code. Each cell holds a short summary that you write of what that file says about the code, next to the coded passages it rests on. It lets you compare cases side by side.
Also known as: matrixcase by code table
The set of coded passages attached to a figure or table in Results Builder as its supporting quotations. You control which passages are in it, and only they are shared with the AI when you ask for a description.
A search across coded evidence that combines codes and variables, for example passages coded with A and with B, from documents where the group is teachers.
Also known as: advanced querycomplex query
A picture or a table taken from Analysis and placed in Results Builder. Each keeps the data behind it, and can be downloaded or exported to Word.
Also known as: results itemresult items
A method that organises data into a matrix of cases and themes so that each case can be summarised and compared across the whole data set. It is used often in applied and policy research.
How often a code was applied, and in how many documents. Frequency counts coding assignments, and a parent code's count adds the assignments of its subcodes, so a passage coded with two subcodes of the same parent counts twice at the parent. A code's share is its assignments, together with those of its subcodes, divided by all coding assignments in the scope. A parent's share already includes its subcodes, so a parent and its own subcodes must not be added together. Frequency shows where coding is concentrated. It is not a measure of importance: a rarely coded idea can matter a great deal.
Also known as: code frequency
Frequency & Spread compares assignment share with source coverage. Assignment share uses all coding assignments in the selected sources; source coverage uses all selected sources, including uncoded ones. Parent counts include subcodes. Neither measure alone establishes analytical importance.
Also known as: prominencedispersion
The shortest path from a new account to a first coded document and a first figure.
Also known as: first stepsquick tour
A round in which a second coder codes a copy of the material without seeing the first coder's coding, and then returns it to the owner for comparison and agreement checks.
Also known as: coding roundcoder return
Building codes from what you find in the data, without starting from a fixed list. The codebook grows and changes as you read.
Also known as: data-driven codingbottom-up coding
How closely two or more coders apply the same codes to the same material. It is used to check that a codebook is clear enough to be applied consistently. Not every qualitative approach uses it. In Byleron it is calculated from whether each document holds each code, so percent agreement and Cohen's kappa describe document-level code assignment, not agreement on the exact locations or boundaries of coded passages.
Also known as: inter-rater reliabilityintercoder reliabilitycoder agreement
A question put to participants. Giving equivalent questions the same question key across transcripts lets you compare how different participants answered the same question.
Also known as: question keyquestion label
Under Same document, Jaccard divides sources containing both codes by sources containing either code. Dice divides twice the shared-source count by the sum of the two source counts; the overlap coefficient divides it by the smaller source count. Under Overlap or Nearby, use relationship coverage and the separately named source ratios. These use sources meeting the selected rule, not raw assignment-pair counts.
Also known as: JaccardDice coefficientDice
An agreement measure that works with two or more coders and with missing data, and that also corrects for chance. It is widely used in content analysis.
Also known as: alpha
Drawing thicker lines for stronger links or for more heavily coded branches in a map or network, so strength is visible without reading numbers.
Also known as: edge widthtie strength
A code at the top level of the codebook, with or without subcodes. Some figures can show main codes only, and a main code’s counts include the counts of its subcodes.
Also known as: top-level codeparent code
A drawing of codes and cases as nodes joined by lines, for example the code hierarchy or the codes one case uses. A map is a way to look at structure and links; it is not a finding in itself.
Also known as: concept mapnetwork
A note you write to yourself during analysis: an emerging idea, a decision about a code, a link to theory, or a reflection on your own position. Memos are part of your reasoning, not participant evidence.
Also known as: memosanalytic memo
A label for the kind of thinking in a memo: analytic, theoretical, methodological, reflexive, codebook, or question. You can add your own categories.
Also known as: analytic memotheoretical memomethodological memo
A network with memos as nodes, joined to the codes they are about. It shows where your own thinking has gathered and which codes have none.
Also known as: memo-centered concept network
What a memo is attached to: the whole project, a code, a document, a passage or range, or an interview question. The type tells you what the memo is about; the category tells you what kind of thinking it holds.
Also known as: project memocode memodocument memopassage memoquestion memo
Combining two codes that mean the same thing into one. All evidence, the memo and any subcodes of the merged code move to the code you keep, and the merged code is deleted.
Also known as: merging
The guidance view in the AI Assistant where you review your study information, project readiness and areas that may need attention. Project Setup remains the place to review and complete the project frame.
Also known as: Project GuidanceYöntem Pusulası
Descriptive text about how the analysis was done, produced in Results Builder from your project details. It must be checked and edited by you before use.
Also known as: methods text
Sending ticked evidence from one code to another, or to a new code. It works for text passages, image and PDF regions, video frames and audio or video ranges.
Also known as: recodemove to code
A case that does not fit the pattern you are describing. Looking for and reporting negative cases tests an interpretation and often refines it.
Also known as: outlierdeviant casedisconfirming case
Two codes, or two passages with the same code, covering some of the same text. Overlap is normal when one passage means more than one thing; it becomes a problem when it duplicates the same evidence. Frequency counts both passages, while coverage counts the shared characters once.
Also known as: overlapmulti-coding
The first Analysis page. It shows what the project is about, where it stands, your recent activity, the data, coding progress and what needs attention.
Also known as: project overview
The hidden text behind the picture of a PDF page that lets you select and code words. A scanned PDF often has none, so its passages can only be coded as regions, or the text must be recognised first.
Also known as: selectable textscanned PDF
The share of coding decisions on which coders match. It is easy to read but does not allow for agreement that happens by chance.
Also known as: simple agreement
A compact profile of coding across documents or cases, so you can see at a glance what each case is mostly about.
Also known as: case portraitcoding profile
A container for one study: its documents, codes, coded evidence, memos, variables and results.
Also known as: workspace project
The information about your study (aim, research questions, context, method, how you coded, ethics and language) that the Methods draft is written from. Only a small framing part of it is sent to the AI Assistant.
Also known as: study details
The systematic study of non-numerical material, such as interviews, documents, images and recordings, to understand meaning and patterns. Software that supports this work is often called CAQDAS (computer-assisted qualitative data analysis software). The software organises and retrieves; the interpretation stays with the researcher.
Also known as: QDACAQDAS
A stretch of an audio or video recording, from one moment to another, that you code. The range can carry one or several codes and a memo.
Also known as: audio rangevideo rangetime range
An open exchange format for qualitative projects. A QDPX file carries codes, documents, coded passages and memos between programs, and a QDC file carries a codebook only. It lets you move work in and out of Byleron QDA.
Also known as: QDPXREFI-QDAQDC
The researcher's ongoing reflection on how their background, assumptions and choices shape what they see in the data and how they interpret it. Reflexive memos are a common way to record it.
Also known as: reflexive
A rectangle drawn on an image, a PDF page or a video frame to mark what you are coding, for example one person in a photograph.
Also known as: image regionPDF regionvideo frame region
The approval and oversight process that a university or institution applies to research involving people. Check what your review body requires before you upload participant data or use AI on it.
Also known as: ethics approvalinstitutional reviewIRBethics committee
The place where you collect tables and figures from Analysis, order them, add descriptive wording and export a results document. Interpretation and the final text stay yours.
The window that lists every piece of evidence coded with one code, with its document and location. From it you can open the evidence, move it to another code, and edit, merge, split or delete the code.
Also known as: retrieval
A small ready-made project you can open to try coding and analysis without using your own data.
Also known as: demo project
The point at which further data stop producing new codes or new insight. It is debated as a stopping rule, so justify any claim of saturation with your reasoning and not with a number alone.
Also known as: code saturationthematic saturation
A search you keep so that you can run it again with one click. It is stored with your project.
Also known as: saved searches
How long the coded passages are. Very short or very long passages can signal inconsistent coding, or a code that is applied to different kinds of things.
Also known as: length distribution
A Byleron QDA feature that prepares editable Methods and findings from your project details and analysis. Review the draft alongside your sources, figures and tables, then develop the interpretation in your own words.
Also known as: Smart FindingsAkıllı Taslakdraft Methodsdraft findings
One continuous contribution by one speaker in a transcript. Labelling turns by speaker and role lets you analyse what participants said separately from the interviewer.
Also known as: turnspeakerinterviewerparticipant
Dividing an overloaded code into more specific ones. You create the new codes, usually as subcodes of the original, and decide which evidence belongs to each. The original code is never deleted.
Also known as: splitting
A more specific code placed under a broader one. The broader code is the parent. In Byleron QDA a parent counts the evidence of its subcodes, so its total shows the whole idea and its own count shows what was coded directly.
Also known as: sub-codechild codeparent code
A method for identifying, organising and interpreting patterns of meaning, called themes, across a data set. Themes are built by the researcher from codes; they are not simply the most frequent codes.
Also known as: reflexive thematic analysis
How coding on a theme changes across an ordered variable, such as interview date or wave. It helps you see when an idea rises, fades or appears.
Also known as: trajectory
A pattern of meaning that organises several codes around one central idea. A theme is an interpretation you build and argue for, supported by evidence, not a label that is simply found.
Also known as: themescategory
A time marker, such as [00:12:40], that ties a line of a transcript to a moment in the audio or video. Timestamps let you code a range of the recording and play it back.
Also known as: time stamptime code
A written record of spoken material such as an interview or a focus group. In Byleron QDA a transcript can be imported, or created from an audio or video file, and it can carry timestamps that link each line to the recording.
Also known as: transcriptiontranscribing
Nested rectangles compare coding-assignment counts within the code hierarchy. Counts include subcodes; direct parent assignments are separate. Area does not measure conceptual importance. The searchable key lists every code, including those too small to label.
Checking a finding against more than one kind of source, method or researcher, so that it does not rest on a single view.
What each count or percentage is about: files, cases, participants, coding assignments or selections. Say which one you used, because the same data gives a different number for each.
Also known as: counting unit
A characteristic that describes a case or document, for example age group, school, gender or interview date. Variables let you compare groups and filter evidence, but they are not coded from the text.
Also known as: variablesmetadataattributeattributes
A single still picture from a video. You can code the whole frame or draw a region on it, which suits questions about what is visible at one moment.
Also known as: frame
A way to share a project so that someone can read its documents, codes, coded passages, memos and analyses without changing anything. The owner can end the access at any time.
Also known as: reviewerview only
The text, definitions and details of your project that are shared with the AI provider when you use an AI feature. It is limited to what the feature needs, and AI features are optional.
Also known as: data scopedata sent to AI
A picture in which words are sized by how often they occur. It describes vocabulary, not meaning, so use it to explore language and check it against the coded evidence.
Also known as: clouds
A Word file of your results, with numbered captions, figures and tables, created in Results Builder.
Also known as: DOCXWord document
Try a shorter word, or search the Questions & Answers page for how to do something.
Open Questions & Answers