Hello Iordan,
Further to James’ response the answer also depends on whether the codeset is set for single data entry or multiple data entry.
In both cases, coding is always tied to a user account.
If the codeset is set for single data entry, and reviewer A has coded sections 1-4, and reviewer B has coded sections 5-8, all of the items will get marked as complete automatically as they are coded. All of the coding, for all of the items coded, will then be accessible to the searching and reporting functions. There really isn’t a need to have all of the coding under one reviewer in this case.
If the codeset is set for multiple data entry, the expectation is that reviewer A and reviewer B would be coding the same items using the same section of the codeset. This is often called double coding or double screening. You would set up the work allocations in the Collaborate tab and after all of the items were double coded you would then run ‘Create comparisons’ (also in the Collaborate tab) to mark the agreements as complete and reconcile the disagreements. This is described in the user manual.
If you have set the codeset for multiple data entry but you are not double coding, you now probably have a number of items coded but not marked as complete. When a codeset is set for multiple data entry, an item does not automatically get marked as complete when a code is assigned to it. This is because of the expectation that there will be two (or more) people coding that item and the reviewers will want to compare what they have done, come to an agreement and then mark it as complete.
If you are in this situation you will need to manually mark the items as complete. The thing to watch out for is that marking an item as complete when the code set is marked for multiple data entry means you are only working with your own coding. It you are marking an item as complete that you did not code (but reviewer B did), the completed version will not show reviewer B’s coding.
To get around this you will want to first return the codeset to single data entry. Once you make that change, you will see both versions of coding (Reviewer A and Reviewer B) visible. Now, if you mark the item as complete, the completed item will have both versions of coding. In your situation this is what you want as Reviewer A coded some of the items and Reviewer B coded some of the items (but not the same items).
Marking an item as complete can be done in the Document details window (where you code the items). If the item is not marked as complete there is a little red disc next to the code set. If you click on that disc, a confirmation window pops up asking if you want to mark the item as complete. If you click yes, the item is marked as complete and the red disc next to the codeset changes to a green disk with a check in it. The green disc signifies the item is marked as complete.
At this point there is not a method to automatically mark a number of items as complete. We may add this function in future although it could be a very dangerous function if used improperly.
Please remember that what I am describing applies to your specific situation. If you actually have double coding (two versions of coding on the same item) then you should be using the ‘Create comparison’ functions to deal with agreements and disagreements in the coding.
Best regards
Jeff
EPPI-Reviewer support