OpenCDISC on Network Drive

Pinnacle 21 Support Troubleshooting and Problems
1

Hi Carol,

Could you confirm that your network folders have the same structure and files as you have on your local drive?

In particular, I see that SDTM CT path in your example is not exactly the same as expected. “… /2013-12-20/ …” instead of “…/2013-12-21/…”

Thank you,

Sergiy

2

Thanks, Sergiy,

In both instances the SDTM CT folder was named 2013-12-20. I changed the folder name to 2013-12-21 (in both) and now neither SKIP_SD0008 or SKIP_CT0018 are triggered on the network instance. I’m happy that you identified the problem and that I can run on the network drive. However, I am baffled as to why the name of this folder causes a problem only on the network drive and equally baffled as to why changing the SDTM CT file folder name effects the ability of OpenCDISC to find a file in the MedDRA folder. But this is all inconsequential to me. Everything works now.

Thanks again,

Carol

3

When running OpenCDISC on a network shared drive I get the SKIP_SD0008 error even though the pt.asc is available in the specified location and I get the SKIP_CT0018 error even though the SDTM Terminology.txt file is in the specified location. When I run OpenCDISC on my hard drive I do not get these errors. The messages accompanying these errors is as follows:

  • SKIP_SD0008 “N:\DEVELOPMENT\APPLICATIONS\OPENCDISC\1_4_1\opencdisc-validator\config/data/MedDRA/14.0/pt.asc is missing or lacks necessary variables and cannot be used for this cross-dataset validation.”
  • SKIP_CT0018 “N:\DEVELOPMENT\APPLICATIONS\OPENCDISC\1_4_1\opencdisc-validator\config/data/CDISC/SDTM/2013-12-20/SDTM Terminology.txt is missing or lacks necessary variables and cannot be used for this cross-dataset validation”

It appears that OpenCDISC adds the forward slashes (/) to the directory location which, on our network drive, is identified using backward slashes (). Is this a known issue? Is it possible for OpenCDISC to identify the location of MedDRA files and controlled terminology files when the directory is identified with backward slashes?