You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/doc/en/2.4.-Working-in-a-Team.md
+6-9Lines changed: 6 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ There are several strategies for organising collaborative work on the same proje
8
8
## 1) Sequential Editing of the Same Project
9
9
This approach can be applied to both inductive and deductive coding. It is based on the principle that all team members work on the same project files, albeit not simultaneously.
10
10
11
-
### Coordinating the Sequence of Work Manually
11
+
**Coordinating the Sequence of Work:**
12
12
13
13
* You can do this via email so that each person, upon completing their tasks, mails the zipped project folder to the subsequent individual on the list.
14
14
* You can also work sequentially on the same computer, using the same project folder.
@@ -32,16 +32,13 @@ Follow these steps:
32
32
* Finally, gather all the local copies and sequentially merge them into your master project, using the [process described here](https://qualcoder-org.github.io/doc/en/6.1.-Imports-and-Exports#merge-qualcoder-projects)
33
33
34
34
## Important Considerations Regarding Coder Names
35
-
No matter which strategy you use to organize the collaborative coding process, you must decide if you want to use individual coder names or not.
36
35
37
-
* In most cases, you want to have a unique name for each coder on your team so that individual contributions can be identified even after merging the project together. To achieve this, please check the current coder's name in Files>Settings before doing any work.
38
-
* Click the "..." button next to the coder name in the Settings dialog to open a window where you can change your own identity or create, rename, or merge other coders within the current project.
* In most cases, you want to have a unique name for each coder on your team so that individual contributions can be identified even after merging the project together.
37
+
* In Project > Settings, click the "Change" button next to the coder name to open a window where you can alter your own identity or create, rename, or merge other coders within the current project.<br /><br /><imgwidth="500"alt="Coder dialog"src="https://github.com/user-attachments/assets/380291b1-6e34-4bd3-8344-182af8448140" /><br />(Note that "📌 Speaker coding" is used internally to automatically mark speaker utterances in transcripts. This name should not be used for other purposes.)
41
38
42
-
(Note that "📌 Speaker coding" is used internally to automatically mark speaker utterances in transcripts. This name should not be used for other purposes.)
43
-
* In the same window, you can also control the visibility of other collaborators. Since version 3.8 of QualCoder, contributions from other coders are always visible and editable by default, unless you choose otherwise. Hiding other contributors is especially useful for measuring inter-coder reliability, which requires the same document to be coded by multiple people without influencing each other.
44
-
* This window is also accessible from the toolbar in the code text, code image, and code PDF workspaces.
39
+
* Be careful, especially with the Merge function, as there is no Undo. If you make a mistake, cancel the dialog, and the changes will be reverted. After clicking OK, the changes are permanent.
40
+
* In the same window, you can control the visibility of other collaborators. Since version 3.8 of QualCoder, contributions from other coders are always visible and editable by default unless you choose otherwise. Hiding other contributors is especially useful for measuring inter-coder reliability, which requires multiple people to code the same document without influencing each other.
41
+
* This window is also accessible from the toolbar in the code text, code image, and code PDF workspaces, albeit with limited options.
0 commit comments