Okay, I did a little bit of scouting around today, and I discovered
that this gets really hairy really fast, but we probably can do
something about it, if we're willing to create a DSpace-specific
metadata schema just to hold bitstream information (which might not be
the world's worst idea, actually -- but then again it might).
The METS <file> element lets you have an "admid" attribute that points
to administrative metadata about the file elsewhere in the METS
document. For our purposes, we would probably end up creating
something like this (assume the new metadata is in a "ds" schema) for
each bitstream (or perhaps for each format in an item? one could point
more than one bitstream to the same amdSec):
<mets:amdSec id="bitstream_1">
<mets:techMD id="bitstream_1_techmd">
<mets:mdWrap OTHERMDTYPE="DIM" MDTYPE="other">
<mets:xmlData>
<dim:dim dspaceType="BITSTREAM">
<dim:field element="formatName" mdschema="ds">HappyFile
version 1.01</dim:field>
</dim:dim>
</mets:xmlData>
</mets:mdWrap>
</mets:techMD>
</mets:amdSec>
The place to pop this in, I *think*, is somewhere in
xmlui.objectmanager.ItemAdapter.java. If what I just suggested doesn't
seem outrageous, I'll take a whack at coding it up.
Dorothea
--
Dorothea Salo [EMAIL PROTECTED]
Digital Repository Librarian AIM: mindsatuw
University of Wisconsin
Rm 218, Memorial Library
(608) 262-5493
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
