Forums: Define.xml
Of course, it should. However ...
without following information, no way to find out what goes wrong ...
* which version of define.xml are you using? Version 1.0 or 2.0?
* what tool did you use to generate the define.xml?
* did you generate the define.xml BEFORE generating the datasets (strongly recommended) or did you generate it after dataset generation (discouraged)
* which stylesheet did you use (it might be a stylesheet issue) ?
* please post the code snippet (part "ItemDef" with "Origin" child element) - you can use NotePad++ to open it.
People still need to learn that a define.xml is in first instance a machine-readable file, with as "bonus" that one can visualize it using the stylesheet. So in case something doesn't work as expected, the first place to look is into the XML itself. If needed (also highly recommended), you can take a define.xml course from CDISC, where all this (including the XML) is explained. Don't let you scare off, my undergraduate students learn XML in less than 2 hours.
Jozef Aerts
Define-XML development team and Define-XML Instructor
Thank you very much for your response!
Please look at my comment below.
* which version of define.xml are you using? Version 1.0 or 2.0?→version2.0.
* what tool did you use to generate the define.xml?→I used define_xml_generator developed by a Japanese compay. I also tried P21 comunity, but all CRF page numbers are missing in spite of providing it in excel metadata spreadsheet.(I found the same issue put in this forum without any solution)
* did you generate the define.xml BEFORE generating the datasets (strongly recommended) or did you generate it after dataset generation (discouraged)→Before generating the datasets.
* which stylesheet did you use (it might be a stylesheet issue) ?→I downloaded the stylesheet from CDISC homepage.(define_xml_2_0_releasepackage20140424), is there any problem with that version of stylesheet?
* please post the code snippet (part "ItemDef" with "Origin" child element) - you can use NotePad++ to open it.→Please look at the code below. It seems correct.
<ItemDef OID="IT.DA.DAORRES" Name="DAORRES" DataType="text" Length="2" SASFieldName="DAORRES">
<Description>
<TranslatedText xml:lang="en">Assessment Result in Original Units</TranslatedText>
</Description>
<def:Origin Type="CRF">
<def:DocumentRef leafID="LF.blankcrf">
<def:PDFPageRef PageRefs="19" Type="PhysicalRef"/>
</def:DocumentRef>
</def:Origin>
<def:ValueListRef ValueListOID="VL.DA.DA.DAORRES"/>
</ItemDef>
Thanks! Your code looks perfectly ok! Does it only happen with DAORRES or also with other variables?
There is an improved stylesheet available at: https://wiki.cdisc.org/display/PUB/Stylesheet+Library (2015-01-16) which you might try.
If that doesn't help, you can create your HTML using define.xml + stylesheet, and then inspect the HTML.
You should see something like:
CRF Pages <a href="blankcrf.pdf#page=19">19</a>
Also not a bad idea to try once on a computer of a colleague. I have seen cases where the PDF reader indeed jumps to the first page (i.e. ignores the "#page=X"), which might be due to the settings of the viewer.
Best regards,
Jozef
Thanks a lot!
Unfortunately, the improved stylesheet doesn't work either.
I tried to open the PDF within the explorer, and it works this time.
So, it seems that jumping to a specific page doesn't work when you open the pdf file by Adobe PDF Reader, isn't it?
This should work though. When you can confirm that the link is correct (<a href="blankcrf.pdf#page=9">9</a>), it is not related to the stylesheet, but might have to do with the browser or PDF application.
Hi Zhengyan,
Try to use different browsers.
Regards,
Sergiy
Dear All
Thanks so much for all of your comments!
This problem is solved by changing the setting of the explorer to open the linked blankacrf.pdf within the browser.
Is it possible to jump to the specified CRF page which is set in the value level metadata?
I clicked the hyperlink with CRF page 9 in define XML for example, and always jumped to page 1 not page 9.