Hi Adam,
Sorry. We’ve found a bug in Define.xml import process around Value Level. Please wait for the first Auto-Update release soon.
Thank you,
Sergiy
Hi Adam,
Sorry. We’ve found a bug in Define.xml import process around Value Level. Please wait for the first Auto-Update release soon.
Thank you,
Sergiy
Was this issue ever resolved? I seem to be having the same problem - variable name is blank, and CL. appears in the controlled terms column, but there’s no codelist name in the spec.
Sample output from spec:
(http://www.opencdisc.org/#.IT.ADLB .PARAMCD) |
Order | Dataset | Variable | Where Clause | Data Type | Length | Significant Digits | Format | Mandatory | Codelist | Origin | Pages | Method | Predecessor | Value Level Comment | Join Comment |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ADLB | AVAL | ADLB.AVAL.HCG | integer | 8 | No | Assigned |
Results in this in the define.xml:
Variable |
Where |
Type |
Length / Display Format |
Controlled Terms or Format |
Origin |
Derivation/Comment |
---|---|---|---|---|---|---|
(http://www.opencdisc.org/#.IT.ADLB .PARAMCD)EQ HCG |
integer |
Assigned |
Hi,
I attended the training this past Thursday and it was very helpful once I downloaded 2.0 and began using it. The only item I seem to have issues with while developing an ADaM Define.xml v2.0 is with the ValueLevel/WhereClauses tabs within the generated specifications from OpenCDISC Community using the study XPT files. I’ve tried multiple variations of populating these tabs, but I always end up with a Define.xml where the Paremeter Value Lists are incomplete. It seems that Type, Format, Controlled Terms, Origin, and Derivation/Comment always populate correctly in the Define.xml, but Variable and Where do not, and the link from the Analysis Datasets section does not appear for the variable I wish to describe using the value level metadata (ex: Describe AVAL based on PARAMCD).
I’ve tried generating a complete specification off of the FDA example to use as a reference, but this causes an error (and I have a ticket open with the helpdesk for this issue). Any guidance on how I may be incorrectly using the specifications to populate the value level metadata would be appreciated. Thanks!