I just forgot that I skipped the hand-waving part.
You can find the URL to the Mets document inside of the reference set of a
page, Item page <https://kb.osu.edu/dspace/DRI/handle/1811/263> in my case.
<referenceSet id="
aspect.artifactbrowser.ItemViewer.referenceSet.collection-viewer" n="
collection-viewer" type="summaryView">
<reference repositoryID="1811" type="DSpace Item" url="
/metadata/handle/1811/263/mets.xml">
<referenceSet rend="hierarchy" type="detailList">
<head>This item appears in the following Collection(s)</head>
<reference repositoryID="1811" type="DSpace Collection" url="
/metadata/handle/1811/61/mets.xml"/>
</referenceSet>
</reference>
</referenceSet>
A browse
list<https://kb.osu.edu/dspace/DRI/handle/1811/61/browse?type=title>will
have a longer reference set.
<referenceSet id="
aspect.artifactbrowser.ConfigurableBrowse.referenceSet.browse-by-title"
orderBy="title" n="browse-by-title" type="summaryList">
<reference repositoryID="1811" type="DSpace Item" url="
/metadata/handle/1811/5913/mets.xml"/>
<reference repositoryID="1811" type="DSpace Item" url="
/metadata/handle/1811/29387/mets.xml"/>
<reference repositoryID="1811" type="DSpace Item" url="
/metadata/handle/1811/31934/mets.xml"/>
<reference repositoryID="1811" type="DSpace Item" url="
/metadata/handle/1811/36389/mets.xml"/>
<reference repositoryID="1811" type="DSpace Item" url="
/metadata/handle/1811/24113/mets.xml"/>
<reference repositoryID="1811" type="DSpace Item" url="
/metadata/handle/1811/116/mets.xml"/>
<reference repositoryID="1811" type="DSpace Item" url="
/metadata/handle/1811/24096/mets.xml"/>
<reference repositoryID="1811" type="DSpace Item" url="
/metadata/handle/1811/257/mets.xml"/>
<reference repositoryID="1811" type="DSpace Item" url="
/metadata/handle/1811/115/mets.xml"/>
<reference repositoryID="1811" type="DSpace Item" url="
/metadata/handle/1811/211/mets.xml"/>
<reference repositoryID="1811" type="DSpace Item" url="
/metadata/handle/1811/24091/mets.xml"/>
<reference repositoryID="1811" type="DSpace Item" url="
/metadata/handle/1811/24090/mets.xml"/>
<reference repositoryID="1811" type="DSpace Item" url="
/metadata/handle/1811/5905/mets.xml"/>
<reference repositoryID="1811" type="DSpace Item" url="
/metadata/handle/1811/511/mets.xml"/>
<reference repositoryID="1811" type="DSpace Item" url="
/metadata/handle/1811/401/mets.xml"/>
<reference repositoryID="1811" type="DSpace Item" url="
/metadata/handle/1811/99/mets.xml"/>
<reference repositoryID="1811" type="DSpace Item" url="
/metadata/handle/1811/244/mets.xml"/>
<reference repositoryID="1811" type="DSpace Item" url="
/metadata/handle/1811/264/mets.xml"/>
<reference repositoryID="1811" type="DSpace Item" url="
/metadata/handle/1811/114/mets.xml"/>
<reference repositoryID="1811" type="DSpace Item" url="
/metadata/handle/1811/396/mets.xml"/>
</referenceSet>
Peter Dietz
On Fri, May 27, 2011 at 6:35 PM, Peter Dietz <[email protected]> wrote:
> Hi Jose,
>
> in-line commenting.
>
> On Fri, May 27, 2011 at 2:28 PM, Blanco, Jose <[email protected]> wrote:
>
>> 1. I'm just experimenting with manakin and I thought if I made a change
>> in the webapp area to a file like DIM-Handler.xsl I could see the change
>> right away in the browser, but that does not seem to be the case. I tried
>> reloading the webapp via tomcat, but that does not work either. Is there a
>> way to see xmlui changes in the browser without having to rebuild
>> everything. In the JSP environment you can do this, and it's often very
>> helpful.
>>
> XMLUI might also be weighing you down with its "annoying" caching. The
> changes happened, but a cached copy is being served instead of regenerating
> it from a bunch of XSL changes.
>
> You can change:
> https://github.com/DSpace/DSpace/blob/master/dspace-xmlui/dspace-xmlui-webapp/src/main/webapp/sitemap.xmap#L196
> to
> default="noncaching" to disable caching all-together on your development
> machine.
> Or, you could try a few recommendations from:
> http://permalink.gmane.org/gmane.comp.db.dspace.user/13141
> The simplest trick is to append a junk parameter to the end of the url,
> like: ?some-random-text&more_random
>
>
>
>> 2. When I add ?XML to the url, I can see the DRI object which is great.
>> But when I look at some of the xsl commands I can't I can't make the
>> connection with the DRI object and the xsl. For example,
>>
>> <xsl:variable name="data"
>> select="./mets:dmdSec/mets:mdWrap/mets:xmlData/dim:dim"/>
>>
>> I don't see this in the output of ?XML
>>
> 1) Keep in mind that thats an XPath expression. So it involves traversing
> XML to find that piece of data.
> 2) You'll need to follow the ?XML or /DRI/ url to find the mets document
> behind it.
> An original URL: https://kb.osu.edu/dspace/DRI/handle/1811/263
> METS document: https://kb.osu.edu/dspace/metadata/handle/1811/263/mets.xml
>
> <*mets:dmdSec* GROUPID="group_dmd_0" ID="dmd_1">
> <*mets:mdWrap* MDTYPE="OTHER" OTHERMDTYPE="DIM">
> <*mets:xmlData*>
> <*dim:dim* dspaceType="ITEM">
> <dim:field element="creator" mdschema="dc">Brønnum, Rikke</dim:field>
> <dim:field element="creator" mdschema="dc">Jørgensen, S.E.</dim:field>
> <dim:field element="creator" mdschema="dc">Mitsch, William J.</dim:field>
> <dim:field element="date" qualifier="accessioned" mdschema="dc">
> 2004-12-16T13:17:10Z</dim:field>
> <dim:field element="date" qualifier="available" mdschema="dc">
> 2004-12-16T13:17:10Z</dim:field>
> <dim:field element="date" qualifier="issued" mdschema="dc">
> 2004-12-16T13:17:10Z</dim:field>
> <dim:field element="identifier" qualifier="uri" mdschema="dc">
> http://hdl.handle.net/1811/263</dim:field>
> <dim:field element="description" language="en" mdschema="dc">
> The University Archives has determined that this item is of continuing
> value to OSU's history.
> </dim:field>
> <dim:field element="format" qualifier="extent" mdschema="dc">73837 bytes
> </dim:field>
> <dim:field element="format" qualifier="extent" mdschema="dc">73837 bytes
> </dim:field>
> <dim:field element="format" qualifier="mimetype" mdschema="dc">
> application/pdf</dim:field>
> <dim:field element="format" qualifier="mimetype" mdschema="dc">
> application/pdf</dim:field>
> <dim:field element="language" mdschema="dc">English (United States)
> </dim:field>
> <dim:field element="language" qualifier="iso" mdschema="dc">en_US
> </dim:field>
> <dim:field element="relation" qualifier="ispartofseries" mdschema="dc">
> Annual report (Olentangy River Wetland Research Park);2000
> </dim:field>
> <dim:field element="title" language="en" mdschema="dc">
> Occurence and degradation of alachlor and nitrate in a created wetland in
> central Ohio
> </dim:field>
> <dim:field element="type" language="en" mdschema="dc">Technical Report
> </dim:field>
> </dim:dim>
> </mets:xmlData>
> </mets:mdWrap>
> </mets:dmdSec>
>
>
>> What am I not understanding?
>>
> That theres a long, steep learning curve associated with XMLUI.
>
>
> Peter Dietz
>
>
>>
>> Thank you!
>> Jose
>>
>>
>> ------------------------------------------------------------------------------
>> vRanger cuts backup time in half-while increasing security.
>> With the market-leading solution for virtual backup and recovery,
>> you get blazing-fast, flexible, and affordable data protection.
>> Download your free trial now.
>> http://p.sf.net/sfu/quest-d2dcopy1
>> _______________________________________________
>> DSpace-tech mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>>
>
>
------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
