Step by step
Bring a paper's codes from another project
When a paper you coded in one project joins another, choose to bring all its codes, some of them, or none.
- Time
- 2 minutes
- Steps
- 4
Your coding is part of what you have learned about a paper. When a paper you have coded in one project joins another project, CurTask asks whether its coded passages should come along, with their codes and memos, so you don't code it twice.
Nothing is copied unless you choose to. The original project keeps its coding either way.
Step 1Add the paper to another project
Add the paper to a second project in any of the usual ways: from your Global Library, from the project's library, or with Add papers in the matrix. See Add papers to a project.
Step 2Choose what to bring
A dialog asks Bring this paper’s codes? It names the project the paper is coded in and how many codes it has. Choose one:
- Import all codes: every coded passage comes with its code.
- Choose codes: tick the codes you want; each shows how many passages it has.
- Don’t import: start this paper's coding fresh in this project.
When you add several coded papers at once, you can decide for all of them together, or choose Decide for each paper.
Choose Import.
Step 3Settle any matching names
If this project already has a code with the same name, CurTask asks what to do with each one: Merge into existing (the passages join the code you already have) or Keep as a new code under a new name. Choose Import again.
Step 4Check the codebook
The imported codes appear in this project's Codebook with their passages counted, and the paper's Coding strips show the imported passages. You can rename, merge or delete them here without touching the other project. See Build and tidy your codebook.
What's next
- Baggage: what else travels with a paper between projects.
- Memos and notes are never sent to AI.