Enhancements and Feature Requests

Can the user be given the option of using the data/variables or the define file to assign class of a dataset

Hi.

We have some datasets that or not a true BDS structure, still borrowed some BDS elements. Open CDISC validates them as being BDS, however in the DEFINE.XML they have been flagged as OTHER. My question is if OPEN CDISC validator could use the type defined in the define.xml when it is available instead of trying to determine the structure based on the available variables?

Thanks.

Rob

 

Regarding check SD1029/FDAC214 (Non-ASCII or non-printable characters in -- variable) – this correctly identified an issue with a row in IE.IETEST. However, when we looked there were actually more issues present in the TI.IETEST content that were not being picked up. Does this check only check IE ? If yes then why when TI is the superset ? Is this behaviour intentional or can this be a fix request ?

One thought--it would be nice if there were a way to set things up so that multiple versions of OpenCDISC could access the same directory of standard dictionaries and terminology.  Right now our OpenCDISC 1.5 installation has almost 300mb of MedDRA files in Config/Data, and making these files available to our OpenCDISC Community 2.0 installation requires making an additional copy of everything.  (And this is in addition to the copies that live in our standard location for storing our MedDRA dictionaries, which is a completely separate location.)

In OpenCDISC validator version 1.3 the warning messages for Extensible user defined formats were not thrown after running the SAS transport files along with define.xml, in 1.4.1 the messages related to these are still appearing after running the SAS XPT's with define.xml. Please suggest a soultion.

When no issues are found (most often in validating define.xml), can you add a note to the Issue Summary tab stating this fact?  Sometimes I get worried that OpenCDISC did not run correctly when I see nothing on this tab.

Hello,

I'm testing OpenCDISC 1.5 with some dataset with Japanese characters.

OpenCDISC 1.5 can handle Japanese values correctly when it is passed by Dataset-XML format. (but currently .xpt format seems not to be supported yet).

But still there is a problem to validate datasets with non-ASCII characters. Checking controlled terminologies is done by parsing text files in config/data/CDISC/SDTM/yyyy-mm-dd/ folder, but there is no way to specify character encoding for these terminology files. It will be a barrier when users would like to check their data by localized terminologies.

Hello all,

I think it would be usefull to allow the Validator to process files separated also by the "tab" delimiter.

The UI now allows the user to specify the delimiter manually: by default it is comma. But he has no means of specifying "tab" as a delimiter. Maybe you can add an editable combobox with these two values predefined (tab and comma)?