Generating Define XML using community version

Pinnacle 21 Support Define.xml
1

Hi Jatin,

Are you using a stylesheet for define.xml v2.0?

Thanks,

Sergiy

2

Hi Sergiy,

I am using define2-0-0.xsl stylesheet which is came with define package.

Thanks

Jatin

3

Could you send me a sample of your excel files?

Thanks,

Sergiy

sergiy at opencdisc dot org

4

Hi Sergiy, I did send excel file and define to your attention. Thanks Jatin

5

Hi Jatin,

Links to CRF pages are generated by a define.xml stylesheet. The commonly used stylesheet provided in CDISC define.xml v2.0 package works only with one pre-defined Href attribute value for aCRF. It should be “blankcrf.pdf”.

Also ID should be “blankcrf”. It’s a hardcoded aCRF ID for Origin in OpenCDISC define.xml generator.

Otherwise CRF Page links will not be populated.

You need to correct Href value for aCRFs in Documents tab of your specifications.



ID

Title

Href


blankcrf

Annotated Case Report Form

blankcrf.pdf

Thank you,

Sergiy

6

Hi Sergiy,

You are right, that for Define-XML v1 the filename (blankcrf.pdf) was hard-coded in the stylesheet, since there was no metadata connecting the Origin to the annotated CRF document. In Define-XML v2 however, the filename is in the metadata (through def:Origin/def:DocumentRef) and the stylesheet does not make any assumptions for the annotated CRF filename.

Best,

Lex

7

We have an encountered an issue when creating define.xml using OpenCDISC community 2.0. Page numbers are not being displayed in the define.xml, albeit the specs do reflect the page numbers. We have modified the specs that is generated from the XPTs by adding Origin, Page Numbers etc., we have loaded the specs to generate the define, but the page numbers are not populating. Can you please let us know if there is any bug with the current version of the OpenCDISC community 2.0. Your input this is greatly appreciated.