Hello Carla,

Sources are not directly tied to coding or duplicate checking. There isn’t a mechanism that would result in coding being removed from a particular source. If I look through some of the items in the ‘CINAHL Telehealth Chronic’ review I can see that they have coding.

What might be confusing things is that your codesets are all set up for multiple data entry. This means that none of your coding will show up in the search and reporting functions until you manually complete them. Multiple data entry (double coding) implies that two or more people will be coding the same items. If we look in the Review statistics tab we can see that most of the coding has been ‘completed’ but there are a number of items that still need to be completed. Even so, if the codeset is set up for multiple data entry and a code from that set is applied to an item it should be seen in the duplicate checking functions as coded (whether the item has been marked as 'complete' or not).

If you could let me know a particular item that I could look at I can try to give a more complete response.

Best regards

Jeff Brunton

Hello Ali,

I have had a closer look at your review.

I can see there are 14 sources. I went through each one and all of them have coding except for

CINAHL Telehealth Economic.bib
CINAHL Telehealth Chronic.ris

I must have been looking at a different source when I earlier said I thought there was coding in 'CINAHL Telehealth Chronic.ris'.

I looked at a database backup from about June 18 and at that time there weren't any codes applied to items from that source. I can see that there was quite a bit of coding carried out on other sources as of that day. Would you have expected coding on that source to be there on June 18? On June 18 the number of items and duplicates in that source was same as they are today.

To look into this further we would need a bit more information. If you think that on a particular day the coding should be there we could have a look at a backup from that day and verify if it was there or not.

As for the freezing issue, could I ask what browser you were using. There is a known problem where the FireFox browser has frozen the Silverlight plugin (that EPPI-Reviewer runs in).  It occurs when some non-native Silverlight dialog windows are not acknowledged quickly enough by the user. It is described and a workaround is given in this thread HERE (go to the third post in the thread where it says 'Side note').

Best regards,

Jeff