Further to this, I've managed to access some MODS embedded in dmdSec
of a METS.xml (METADATA bundle bitstream, just uploaded manually.. no
ingest/crosswalk), but only by altering DIM-Handler.xsl so it knows
about the mods namespace, and doing the query there.
eg.
<tr><td><span class="bold">MODS Title</span></td>
<td><xsl:value-of
select="/mets:METS/mets:dmdSec/mets:mdwr...@mdtype='MODS']/mets:xmlData/mods:mods/mods:titleInfo/mods:title"/>
</td>
</tr>
I can't seem to get this working from a template in MODS-Handler.xsl at all.
I'll investigate org.dspace.app.xmlui.objectmanager.ItemAdaptor a bit
more, as well as MODS-Handler.xsl....
Cheers,
Kim
On 14 July 2010 09:53, Kim Shepherd <kim.sheph...@gmail.com> wrote:
> Hi Jonathan,
>
> I'm also interested in MODS: specifically, storing MODS or
> MODS-in-METS as bitstreams in the METADATA bundle of an Item. So far I
> haven't had a lot of success... I'll let you know if I figure out any
> tricks.
>
> It might help to read up about DSpaceMETSSIP packages (see
> https://wiki.duraspace.org/display/DSPACE/DSpaceMETSSIPProfile), but
> since ingested items are usually crosswalked to DC at the time of
> ingest, metadata typically isn't stored as MODS, just crosswalked for
> ingest, and also crosswalked for dissemination (eg. crosswalking DC to
> MODS for dissemination in OAI-PMH)
>
> As far as XMLUI's handling of METS/MODS bitstreams in the METADATA
> bundle of an item: it isn't really documented, except to claim it's
> possible (see http://www.dspace.org/1_6_2Documentation/ch07.html#N154ED)
>
> I've managed to stick some METS (named METS.xml) into the METADATA
> bundle of an item and get Manakin to access <mets:fileSec> properly
> for serving up external CONTENT bitstreams, but so far, I've had no
> luck getting any MODS inside <mets:dmdSec> accessible by
> MODS-Handler.xsl.
>
> If anyone is currently using METS and/or MODS-in-METS with XMLUI in
> this way, I'd love to see some examples!
>
> This is what I'm trying currently:
>
> <mets:dmdSec ID="dmd_1">
> <mets:mdWrap MDTYPE="MODS">
>
> <mets:xmlData>
>
> <mods:mods>
>
> <mods:titleInfo>
> <mods:title>Here is my MODS title</mods:title>
> </mods:titleInfo>
>
> </mods:mods>
>
> </mets:xmlData>
> </mets:mdWrap>
> </mets:dmdSec>
>
> ... followed by fileSec and structMap sections, which appear to work
> OK (though they are handled by General-Handler.xsl and not
> MODS-Handler templates)
>
> Cheers,
>
> Kim
>
> On 14 July 2010 03:06, <jd...@georgetown.edu> wrote:
>> I have a few questions about working with mods metadata with dspace. We
>> would like to be able to ingest Mods metadata then be able to index and
>> display the Mods metadata.
>>
>> I have attempted to create a metadata registry for Mods but have been
>> unsuccessful in being able to ingest the records using the crosswalk
>> plugins. Any suggestions on how to get Mods records ingested into Dspace
>> and maintaining the Mods metadata would be greatly appreciated.
>>
>> I have also unsuccessfully tried to use manakin to display the Mods metadata
>> as a bitstream. Also is it possible for manakin to index bitstream metadata
>> or is just just available for display?
>>
>> Thank you,
>>
>> Jonathan
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Sprint
>> What will you do first with EVO, the first 4G phone?
>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>> _______________________________________________
>> DSpace-tech mailing list
>> DSpace-tech@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>>
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
