Skip to content

Commit 2a9e07c

Browse files
authored
Update 2.4.-Working-in-a-Team.md
1 parent 08a44d5 commit 2a9e07c

1 file changed

Lines changed: 8 additions & 5 deletions

File tree

docs/doc/en/2.4.-Working-in-a-Team.md

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -29,20 +29,23 @@ Follow these steps:
2929
* Zip your project folder, including all subfolders and files, and send it to your collaborators (email, file transfer, or USB-stick).
3030
* Decide on a strategy for handling coder names in your team, as explained in the notes below.
3131
* Now, each team member can unzip their local copy of the project and work on it independently, adding codes, codings, memos, etc. However, do not edit the imported text of the empirical documents themselves, since this will potentially cause problems during the merging process later.
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)
32+
* Finally, gather all the local copies and sequentially merge them into your master project, using the [process described here](/doc/en/6.1.-Imports-and-Exports#merge-qualcoder-projects).
3333

3434
## Important Considerations Regarding Coder Names
3535

3636
* 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 /><img width="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.)
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.
38+
39+
<img width="500" alt="Coder dialog" src="https://github.com/user-attachments/assets/380291b1-6e34-4bd3-8344-182af8448140" />
40+
41+
(Note that "📌 Speaker coding" is used internally to automatically mark speaker utterances in transcripts. This name should not be used for other purposes.)
3842

3943
* Be careful, especially with the Merge function, as there is no Undo. If you make a mistake while you are in the coder names screen, press the cancel button, and the changes will be reverted. After clicking OK, the changes are permanent. However, the merge function will make a copy of your project before the merge with a _pre_coder_merge suffix_.
4044
* 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.
4145
* This window is also accessible from the toolbar in the code text, code image, and code PDF workspaces, albeit with limited options.
4246

43-
## Warning
44-
45-
Do not keep the project folder on a network drive or in a cloud location, and access that location whilst running Qualcoder. If the database connection is lost, it would corrupt the database while QualCoder is performing a series of database operations.
47+
!!! warning
48+
Do not keep the project folder on a network drive or in a cloud location, and access that location whilst running Qualcoder. If the database connection is lost, it would corrupt the database while QualCoder is performing a series of database operations.
4649

4750
## Backups
4851

0 commit comments

Comments
 (0)