1777 Sentry Parkway West
Building 17, Suite 405
Blue Bell, PA 19422
+1 (888) 507-2270
Case sensentivity of DOMAIN= and NAME= ?
Forums: Define.xml
Case sensitivity
To clear up some confusion. The name of the submission SAS XPT transport file, or rather its relative location, is given by the value of the ItemGroupDef/def:leaf/@xlink:href attribute, not by the SASDataSetName attribute. In the context of a submission, this xlink:href attribute value should be lowercase according to the various regulatory guidances.
The SASDataSetName specifies the SAS dataset as it is transported by means of the SAS XPT transport file.
In SDTM, SEND and ADaM Name, Domain and SASDatasetName are all uppercase.
Lex Jansen
CDISC Define-XML Dev. team
Lex, The text from the IG…
Lex,
The text from the IG below is quite clear. Will this be amended in v2.1?
__
Root name of SAS dataset contained in the SAS Transport file containing the ItemGroup data.
This is the same as the file name but without the ".xpt" extension.
Business Rules:
Must conform to SAS Transport file naming rules.
Case sensitivity
Ryan, you are right. This sentence in the spec is confusing and even incorrect.
I have entered a JIRA defect to get it fixed: https://jira.cdisc.org/browse/DEFINEXML-246
Thanks for bringing this up!
I'm experiencing differing behavior when I validate define.xml using the define.xml configuration file and Community version 2.2. If I lowercase DOMAIN and NAME in order to match the SASDatasetName attribute, issues such as DD0028, DD0029, DD0031, DD0032, DD0034, DD0024, DD0039, and DD0059 do not surface. When I uppercase these attributes, the checks appear to fire and Pinnacle 21 Community will report these issues should any exist in the define.xml/metadata.
Are these checks contingent/conditional on the casing of both or either of these attributes? We have done some further testing and as suspected -- given it is a Mandatory piece of metadata -- the casing of the NAME attribute appears to be the deciding factor whether these checks are executed or not.
Where I struggle as it relates to this apparent bug in Pinnacle 21 community 2.2 is, in relation to the business rules for SASDatasetName (IG Section 5.3.10), the various regulatory guidance that indicate all submission files, including transport files (XPT), must be lower cased, and the DD0049 check that will surface if DOMAIN and NAME do not match SASDatasetName.