Report Output

RE: Report Output

Hi, We're glad to hear that you like the Excel report. We thought many people would prefer it over the other options. The current limitations on the Excel format stem from two factors. The first is that we simply didn't expect that many organizations in the industry would have upgraded their Microsoft Office installations to the 2007 version (I'm not sure if this is actually the case, but the corporate environment seems to be trending that way in general). Additionally, the current library that we use for generating the Excel files is quite memory-intensive, so we opted to take the more stable route and use the natural cutoff provided by the pre-2007 Excel file format. That being said, as we continue to develop the Validator, this is definitely something that we will work on improving so that we can extend the reporting functionality to meet everyone's needs (or, in your case, capabilities). Is it possible to put in a user specified cutoff such that once the number of errors exceed some value for each check the checking stops? Just for clarification, let me make sure I understood correctly. You'd like to be able to tag a given check, say IR4004, with a maximum number of error messages it should generate before stopping the check. Also, are you thinking along the lines of it stopping only the individual check, or the validation process as a whole? Thank you for your suggestions, we appreciate the time you took to provide feedback! Regards, Tim

Cutoff for report output

Generally when I get many errors I only need the first 1000 or so to identify the issue. I would make the tag a global one so that it applies to all checks across the board - no need to tag each individual check. One selection by the user would apply the tag to all checks. Once the error output reaches the user defined number then the validation would continue with the next check - the validation process as a whole would continue. Regards, David

RE: Cutoff for report output

Alright, great! That makes sense to me, thanks for the suggestion. We'll go ahead and make a note of this, and you should likely see some more flexible reporting functionality in the Beta 2 release. Regards, Tim

Report Save Option

Hi Tim, Minor detail: After running validation, can we have an option to save the output without having to view it in Excel first? Regards, David

RE: Report Save Option

Hi David, Currently, the report is saved in the "reports" folder with a unique name, which is the file you're viewing when the program opens Excel. We'll put customizing the name and location of this file on the list of things to consider for the next release. Thank you for the suggestion! Regards, Tim

IR4250

I am confused by the output for this check. For the disposition domain I am getting a warning message that DSTOXGR is defined in the configuration but is not present in the DS domain. We would never expect this variable to be defined in this domain. However, it is defined in the general observation class - EVENTS. Is it required to check the general observation classes? This is an example of where I would not or at least make it an INFO message.

RE: IR4250

Hi, After reviewing the SDTM specification, this is actually a bug in the configuration file. DSTOXGR is defined as a permissible variable in the configuration, but should have been omitted. I'll be sure to inform the configuration writers about this. Regards, Tim

RE: IR4250

Hi David, We have updated the configurations and removed DSTOXGR and all other --TOXGR variables that were not suppose to be there. Based on SDTM specification the only domains that could contain --TOXGR are AE, LB, generic Events, and generic Findings. The generic domains are only used to validate custom SDTM domains in the absence of a define.xml file. You can download the latest configurations here http://www.opencdisc.org/download#configurations. Just save them to your local PC and override the configurations that are in your “\opencdisc-validator\config” folder. Thanks, Max

IR4253

For PP and PC I get these warnings: PPBLFL IR4253 Expected variable defined in configuration not present PCBLFL IR4253 Expected variable defined in configuration not present I do not believe these variables are EXP for these domains. Also, I have a custom domain called MQ and I get the same message. I would not expect this check to fire for a custom findings domain; or am I missing something?

RE: IR4253

Hi David, You are correct, this check should not fire for custom findings domains. I have updated the configuration files to resolve this issue. Please download the latest configurations here http://www.opencdisc.org/download#configurations. Just save them to your local PC and override the configurations that are in your “\opencdisc-validator\config” folder. Thanks, Max

Updated Config

Thanks Max, works fine. Product Suggestion: On the Report Output Summary sheet at the top under the line for the configuration path can we have a single line with the path to the datasets that were used? Regards, David

Re: Updated Config

Alright, good suggestion. We should be able to add this in Beta 2 release. Thanks, Max

Excel report enhancement

Hi,

Is it possible to enhance the functionality of some of the Excel worksheets that are produced by automatically adding autofilters for each column? This is something we find ourselves doing every time when we start to drill down into the Details worksheet and the Rules worksheet. The Issue Summary worksheet would need to be reconfigured a little bit so that the 'Source' values appeared on each of their associated rows, rather than on their own row. But then that worksheet's columns could also be autofiltered. Thanks.