Define.xml

I'm using version 2.1.2 to validate define v2 xml (SDTM 3.2, CT 2015-12-18)

The config XML for 3.2 has numerous references to CodeListOID="CL.C66742.NY”  They look like:

         <CodeList OID="CL.C66742.NY" Name="No Yes Response" DataType="text"

                   nciodm:CodeListExtensible="No">

            <EnumeratedItem CodedValue="N">

               <Alias Name="C49487" Context="nci:ExtCodeID"/>

            </EnumeratedItem>

DD0074 is Variable/Value Level Origin Type mismatch.

Despite there not being a rule in define-xml 1.0 for variable/value origin matching, Pinnacle21 validator for define.xml is checking for this 2.0 rule.

In Define 1.0 file, my understanding is that the value-level metadata for findings files describes the --ORRES. 

If I eliminate the origin on LBORRES because I will define it at the value level, I get an error that I have a missing Origin.

Hi,

I am using the Pinnacle 21 v2.1 to validate the define 2.0 XML and met a ERROR DD0001 as below,

      Element 'MetaDataVersion' cannot have character [children], because the type's content type is element-only.

[SDTM Part]

  <MetaDataVersion OID="MDV.CDISC01.SDTMIG.3.1.3.SDTM.1.3"
      Name="Study XXX, Data Definitions"
      Description="Study XXX, Data Definitions"
      def:DefineVersion="2.0.0"
      def:StandardName="SDTM-IG"
      def:StandardVersion="3.1.3">

[ADaM Part] 

Hi, 

I have a variable which is coming from CRF as well as eDT, i am using Pinnacle 21 to generate my define.xml, however i am not able to show both origins together in the define.xml output. Below is the xml code, if i add eDT, CRF in the excel as Origin, it doesn't pick up the pdf page number. 

I have also attached a screenshot of my specs. 

Please advice. 

Hi all,

I have two WhereClauses in ADIE, one saying PARAMCD eq IEV2 and one saying PARAMCD ne IEV2. I have given these two different names (of course) in the Excel Specification, but I have discovered that the WhereClauseOID in define.xml created by Pinnacle 21 2.1.1 uses the text from the Value column, not the ID column. So in the define.xml, the two WhereClauses are given the same WhereClauseOID.

Why aren't Pinnacle21 using the ID column for creating the WhereClauseOID?

Regards,

Tommy

Hi,

Maybe a stupid question, but if I understand it correct the validator for define.xml (version 2) is using a schematron to validate the define document. Where can I find this schematron?

I am trying to assess the update from Pinnacle 21 community version 2.0.1 to version 2.1.1, and I was comparing the config files to see what was changes. For SDTM and ADaM this works quite well, but for define it looks like the logic is not in the config file but somewhere else (schematron). Therefore I am interested to see the schematron.

thanks,

Can we created Define.xml v1.0 by using OpenCDISC community or Pinnacle 21,

I knew that Define.xml v2.0 can be created using Pinnacle  21 

When I create a define.xml in Pinnacle 2.1.1, the Purpose column in the Datasets section is blank.  When I use the same Excel template to generate the define.xml file with an older version of Pinnacle, the Purpose column has the correct value as supplied in the spreadsheet (Tabulation).

It appears that version 2.1.1. of your software might be skipping the Purpose= element in the ItemDefGroup tag.

Hello,

In the new version 2.1.1 attribute "Description" became required for MetaDataVersion element. Based on the Define XML Specification 2.0 this attribute is optional.

This is not related to the topic, but I was always struggling to understand what to put in it, even in the Define XML specification on page 58 the example looks like:

Hi,

validating my define.xml I get two DD0059-Error: