Define.xml

Hi, I think check OD0019 should be updated to allow SAS format name longer than 8 characters. I got an error in a CodeList Element saying that my SASFormatName attribute was not valid even though it was less than 32 characters and respected the SAS format naming convention. Moreover, nothing in the Define.xml 2.0 specifications states that a SAS format name should be <=8 characters (see page 82 of Define.xml 2.0 specifications). I think this check should be updated accordingly. Thanks Pierre

When the prefix-namespace declaration for the namespace "http://www.cdisc.org/ns/def/v2.0" is not on the top "ODM" element (where it is not necessary at all), but e.g. on the "MetadataVersion" (where it is needed because of def:DefineVersion), I still get an error DD0002 - Missing or invalid 'def' namespace reference. This error should not be thrown, as it is allowed to define namespaces everywhere in an XML document. It is not necessary at all to define them at the top element when not immediately necessary.

We get errors reported for our define.xml document when we include the C-Codes for QS terminology. It looks like the codes are included in the 'config\data\CDISC\SDTM\2014-06-27QS Terminology.txt' file, but they are not included in the 'config\data\SDTM Terminology.odm.xml'. Is there a way to get the validator to include the QS Terminology codes with the rest of the Controlled Terminology?

Hi!

Can one generate a Define.xml using the configuration files from Open CDISC?

 

Thanks

Joyce

Hi ,

 

I have the below error messages:

Hi

Using the Define v2.0 validation for the define.xml and we are getting the errors

Hi all,

I'm generating a define.xml with Validator 1.5 based on an XPT dataset, and I have a few questions:

1. In a previous topic it was said that Validator 1.5 will also support DefineXML2.0; I don't see this feature enabled in the UI. Will it be available in a future release?

2. Some attributes are generated with empty content: ODM FileOID, Study OID, StudyName, StudyDescription, ProtocolName. MetaDataVersion OID, MetaDataVersion Name, MetaDataVersion Description.

The intention is to have the user later fill in manually the content for these tags?

Hi, I get a few of these errors for different elements but everything seems to be lined up correctly in the define when viewed in IE.

DD0023 Element 'ItemDef' in wrong order within Define.xml
DD0023 Element 'ItemGroupDef' in wrong order within Define.xml
DD0023 Element 'def:CommentDef' in wrong order within Define.xml
DD0023 Element 'def:leaf' in wrong order within Define.xml

example:

OK, I'm starting this by stating that I have ZERO experience with Define.xml (in OpenCDISC or any other format), other than having a general idea as to what the output file should look like.

I just now downloaded OpenCDISC version 1.5, which has ADaM Define.xml capabilities.  I ran Define.xml as-is on my ADaM .xpt files that I had just validated.  It finished in a second, and the popup screen says "Note that you'll need to fill in some study and organization-specific values..."