Questions about creating and validating Define.xml
Pinnacle 21 test ID SD1021 (Publisher ID FDAC216) states "Character values should not have leading space ' ' characters, or '.' as an entire value. The only exceptions are COVALn and TSVALn variables."
However, when Pinnacle 21 is run using "SDTM 3.1.2 (FDA).xml", it is incorrectly identifying character strings containing newline characters as having failed the test. For example, the string:
"A string containing
a newline character"
causes Pinnacle 21 to issue the SD1021 warning.
Hi, when validating the define.xml I get the error message Invalid Standard Version value '1.1' for 'ADaM-IG', Version 1.1 has been available for a while. When will the program be updated to not flag version 1.1?
Thanks,
Rob
Dear Development Team,
I found that, when validating Define-XML for ADaM, DD0028 and DD0029 are not detected unless the ItemGroupDef Name (i.e. dataset name) is "BDS".
I was not able to identify the exact line of the source codes, but I produced this by using a test data with an incorrect DTYPE codelist.
Regards,
-Ebi
Dear development team,
It seems like the DD0028 (Term/NCI Code mismatch in Codelist) is not checked when a codelist is NOT extensible.
I happened to find this when I was looking at source codes on Bitbucket (go to the link below and search by "if (!isExtensible)").
https://bitbucket.org/opencdisc/define-generator/src/a8015905b5ebb8a6518dc3bb1c81259a032bc5d5/src/main/java/org/opencdisc/define/validator/ContentValidator.java?at=master&fileviewer=file-view-default
Regards,
-Ebi
Hi
I read somewhere in the forum that define.xml validation by community tool does not work for version 2.1.X using CLI
is it true for 2.2.0 as well, as i am not able to generate report, see call below, if so, any plans to update the community tool CLI?
-type=define
-source="V:\opencdisc\data\definefiles\define.xml"
-config="D:\apps\OpenCDISC\pinnacle21-community_2_2_0\components\config\Define.xml.xml"
- report="V:\opencdisc\data\pinnaclereports\OPENCDISC-report-define-2017.xls
Hi,
Scenario: There are more than one reference to dataguide for a method/comment. There is a warning message [DD0078] while validating generated define xml in Pinnacle21 V2.2.0. If we are giving more than one sections/links referred in a same comment / method then it seems Pinnacle21 considers the first data guide reference and list the remaining links are "Document <document> is not referenced" in the exception report. Please confirm whether Pinnacle21 takes the first hyperlink in a comment/method and ignore the further links in the same comment.
Hi,
We are getting a blank brace in the whereclause of value level metadata in define.xml ver 2.
Eg: QVAL EQ AESTRF()
Please advice, what value is actually expected inside the braces and how to get it populated.
Also, please explain, if we don't want any value in there, how to remove these braces?
Thanks in Advance.
When I create a ADaM Define 2.0 using OpenCDISC Community version 2.0.1 ADSL is located as the first dataset, but using the same excel sheet to create the define using Pinnacle 21 Community v2.2.0 ADSL is then sorted alphabetically.
Is this an know issue? Why does the dataset order change or is a different class name expected for ADSL for the later versions of the software to place ADSL first for the list of datasets.
I have validated my SDTM define.xml using the Community version 2.1.3 with the configuration DEFINE (PMDA) and the CDISC SDTM CT version 2015-09-25.
I get the warning: DD0029 (Required attribute def:ExtendedValue is missing or empty this is relating to 'Category of Questionnaire'), and the errors: DD031 (Missing NCI Code for Codelist 'Category of Questionnaire'), and DD032 (Missing NCI Code for Term in Codelist 'Category of Questionnaire'). These warnings and errors appear to be linked to the QSCAT domain.
I am using P21 community edition 2.1.3.
When I generate the spec sheet from my datasets in xpt format, the ValueLevel tab remains empty.
Do I have to enter all this information manually? Should I upload a separate document to populate this tab?
Thanks,
Adam