HelpForum

Forum (Archive)

This forum is kept largely for historic reasons and for our latest changes announcements. (It was focused around our, older, EPPI Reviewer version 4.)

There are many informative posts and answers to common questions, but you may find our videos and other resources more informative if you are an EPPI Reviewer WEB user.

Click here to search the forum. If you do have questions or require support, please email eppisupport@ucl.ac.uk.

HomeHomeUsing EPPI-Revi...Using EPPI-Revi...New Feature Req...New Feature Req...Automatic ticking of higher order codesAutomatic ticking of higher order codes
Previous
 
Next
New Post
22/05/2013 11:11
 

Hi,

I think it would be helpful if there was an option, when creating a child code, that when this is ticked, the higher order code will automatically be ticked.

This would mean that if there is a code called 'study type', and the lower codes underneath are RCT, systematic review etc., the 'study type' code would automatically be ticked if you ticked RCT. This would be helpful for consistency. At the moment, it's easy to forget to tick 'study type' if you go straight to 'RCT'. This isn't always a problem, but can be at times.

I believe this would be particularly useful if you are scoping the literature rather than reviewing it. For example, at the moment we have a code called 'journal articles', undearneath there is 'empirical' OR 'non-empirical', and underneath each of them there are various options. So if there was such a function as I suggest, ticking on one of the lowest order options would automatically allocate the higher order ones. For our purpose this would be really good, because now there is a risk that someone forgets to tick the higher order ones leading to inconsistency in the later analysis.

Best wishes, Kristin

 
New Post
22/05/2013 11:52
 

Hello Kristin,

I can understand why you might want this functionality but before we would wish to implement this there are a few considerations.

Based on what you have described we would probably suggest arranging your coding tool a bit differently. If you have a code called 'study type' with a number of child codes below it, each representing a study type, then the top code is like a question. Perhaps your top code could be worded something like 'What is the study type'. The reviewer would then only need to select one (or more) of the child codes. There wouldn't be a need to select/check the parent code as it is just a question.

Your second example could be handled the same way. There could be a question called 'What is the publication type' and the child codes could be the different publication types (such as 'journal articles'). If you are then trying to collect data on whether the study or paper is 'empirical' or 'non-empirical', that could be handled in a second question. We would recommend not having too many multiple levels of hierarchy (nesting your codes) as generating reports and comparisons becomes more cumbersome. Having it set up as a series of questions with possible answers removes the need to be ticking the parent code.

A final consideration is that having the system automatically checking codes based on other codes that the user selected is quite different from how the system presently works. It would required a new type of 'code type' which may not be a problem. The bigger danger is that the user may not understand the implications of this code type and be confused as to why codes are being selected when they never selected them.

If is quite possible that I am not appreciating the requirements that you have described so please feel free to response to this thread.

Best regards,

Jeff
 

 
New Post
11/10/2013 13:00
 

Hi Jeff - rather a late reply I know (!), but thanks for this - I think you're right, we can order and rename our sets and this should make it better.

All the best, Kristin

 
Previous
 
Next
HomeHomeUsing EPPI-Revi...Using EPPI-Revi...New Feature Req...New Feature Req...Automatic ticking of higher order codesAutomatic ticking of higher order codes


Copyright 2021 by EPPI-Centre :: Privacy Statement :: Terms Of Use :: Site Map :: Login
Home::Help::EPPI-Mapper::RIS Export::About::Account Manager