Re: [Dspace-tech] Reading other files in Manakin (was: Re: Desired hierarchical display of communities and collection list)
On Nov 28, 2007 4:37 PM, Larry Stone [EMAIL PROTECTED] wrote: I agree that adding techMD to the METS is architecturally the right thing, but there is already a better (or at least, adequate..) technical metadata standard format in PREMIS. There is already a PREMIS crosswalk for the import/export METS packager which you can cannibalize, see org.dspace.content.crosswalk.PREMISCrosswalk This makes perfect sense to me, and in fact I'm kicking myself I didn't see it. Thanks! I have a couple-three chores on my plate before I can get to this (plus a trip this weekend that keeps me out Monday), but I'll get to it. Knowing there's a crosswalk already should make this considerably easier. Dorothea -- Dorothea Salo[EMAIL PROTECTED] Digital Repository Librarian AIM: mindsatuw University of Wisconsin Rm 218, Memorial Library (608) 262-5493 - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Reading other files in Manakin (was: Re: Desired hierarchical display of communities and collection list)
I agree that adding techMD to the METS is architecturally the right thing, but there is already a better (or at least, adequate..) technical metadata standard format in PREMIS. There is already a PREMIS crosswalk for the import/export METS packager which you can cannibalize, see org.dspace.content.crosswalk.PREMISCrosswalk You could put the format name in the element: objectCharacteristics/format/formatDesignation/formatName The crosswalk puts the MIME type there right now, but it would make more sense to use it for the name. (At the time I wrote the crosswalk, I didn't feel it was correct to dignify the chaos that is MIME types by calling it a registry of format identifiers, although we currently use it as such.) Then you can use PREMIS for other bits of technical metadata of use to Manakin, instead of perverting DIM. DIM was never supposed to escape beyond the internal use in XSLT-driven packager crosswalks! There's more about PREMIS here: http://www.loc.gov/standards/premis/ -- Larry 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=dsHappyFile 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/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Reading other files in Manakin (was: Re: Desired hierarchical display of communities and collection list)
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=dsHappyFile 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/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Reading other files in Manakin (was: Re: Desired hierarchical display of communities and collection list)
I haven't looked at the Manakin code, but the MIME media-type of a Bitstream must be coming from its associated BitstreamFormat -- so why not get the human-readable name from the BitstreamFormat as well? There is no need to establish a separate map of MIME-type to user-friendly name when it already exists in teh BitstreamFormat registry. String friendly = bitstream.getFormat().getShortDescription(); One complication, or perhaps advantage, of using BSFs directly is that some of them have the same MIME-type, so getting the friendly name from the BSF actually identifies the format more precisely -- e.g. XML-based formats might all have the MIME-type text/xml, but distinct friendly names. Thus, you should go to the Bitstream's BSF to get the friendly name rather than attempt to use the BSF registry as a map, because it might have multiple matches for one MIME-type. -- Larry On Nov 21, 2007 10:06 PM, Conal Tuohy [EMAIL PROTECTED] wrote: On Wed, 2007-11-21 at 16:43 -0600, Dorothea Salo wrote: The mapping between media-types and friendly names could be introduced into the pipeline using a Manakin Aspect, and then utilised in a View, via XSLT. Aha. I can try to tackle this. What would be the closest existing code? Alternatively, perhaps this is really just a case of i18n? I thought about that, but I can't quite make it work happily. Every time an administrator adds a new bitstream format (something I assume Manakin still has UI for?), DSpace itself would have to make an automatic change to messages.xml, which is under most circumstances a human-authored and source-controlled file. Automagically changing it will make a mess of any installation that keeps its source in source control, I would think. 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/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Reading other files in Manakin (was: Re: Desired hierarchical display of communities and collection list)
(Subject changed to keep from hijacking the earlier thread.) For instance, the hierarchical structure of the collections could be modelled in a simple XML or HTML document, and this hiearchy file could be read by Manakin and used to add contextual information and links to the web pages it generates. What would be the smart way to do this? I'm thinking it might be a solution to the bitstream-format naming problem: make DSpace spit out an XML file with MIME types and the human-friendly representations, then pull that into one's Manakin theme. 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/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Reading other files in Manakin (was: Re: Desired hierarchical display of communities and collection list)
On Wed, 2007-11-21 at 16:43 -0600, Dorothea Salo wrote: (Subject changed to keep from hijacking the earlier thread.) For instance, the hierarchical structure of the collections could be modelled in a simple XML or HTML document, and this hiearchy file could be read by Manakin and used to add contextual information and links to the web pages it generates. What would be the smart way to do this? I'm thinking it might be a solution to the bitstream-format naming problem: make DSpace spit out an XML file with MIME types and the human-friendly representations, then pull that into one's Manakin theme. The mapping between media-types and friendly names could be introduced into the pipeline using a Manakin Aspect, and then utilised in a View, via XSLT. Alternatively, perhaps this is really just a case of i18n? C -- Conal Tuohy New Zealand Electronic Text Centre www.nzetc.org - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
