Skip to content

Commit bb6ba40

Browse files
authored
Update 2.4.-Working-in-a-Team.md
1 parent 1931b98 commit bb6ba40

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Follow these steps:
2626

2727
* Create a master project with the code system already defined (if applicable).
2828
* Ideally, import all empirical documents at this stage. Avoid linking to external files as this complicates the distribution of the project.
29-
* Zip your project folder, including all subfolders and files, and send it to your collaborators (or use an USB-stick).
29+
* 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.
3232
* 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)
@@ -36,7 +36,7 @@ Follow these steps:
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.
3737
* 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.)
3838

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.
39+
* 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 befoe the merge witha _pre_coder_merge suffix_.
4040
* 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.
4141
* This window is also accessible from the toolbar in the code text, code image, and code PDF workspaces, albeit with limited options.
4242

0 commit comments

Comments
 (0)