Hi Alastair,
Your question makes perfect sense to me, but I'm afraid we haven't written anything to directly address your needs: "incomplete coding" e.g. the codes assigned to items in a set that is in "multiple user" mode are "designed" to be visible to the current user in the "document details" window only. In principle, it would be possible for us to add what is needed to get frequencies on incomplete coding, but we never thought it may be necessary, so the facility is not available at this time. I will make sure we'll discuss this option at our next planning round, as it does make sense to me.
For now, there are two possible ways to proceed, one is slow and tedious, the other one fast and a little unconventional.
1) you can of course get the list of the items you have coded (in the collaborate tab, "coding assignments" area, click your own "started" number), open up the first item and manually flick through the full list, counting the number of the ones you've marked as included. Not ideal, I know!
2) the fastest alternative, which is viable because you don't have any already "completed" items, is to bulk complete all the items you've screened already, run a frequency report, save it as a separate file, bulk uncomplete the same items, and proceed with the double coding round as planned. This would be much faster, of course.
I'll give you the details on option 2): you can un/complete all items coded by a single reviewer via the "review statistics" tab (bottom right of the main screen), this is done by expanding the appropriate line in the "complete/incomplete" tables and clicking on the small coloured button (either a "no entry" or green "v" sign). Once you have completed your own items, re-select the "Codes" tab, right click your screening code set and select "Display included items frequencies (children)". This will bring you to the Frequencies table, you can export it via the buttons at the bottom of the screen. After saving the table as a file, please re-open the "review statistics" tab and bulk uncomplete your items (to make your own coding "private" again). At this point you'll have the information you needed and will still be able to proceed with a proper "double blind" phase, assuming that your collaborator didn't sneak in at the right time, precisely to look at your own decisions.
Does this seem viable to you? Please do let us know if you'll need further guidance.
Best wishes,
Sergio