Hardy and everyone else interested, Thanks to Andrea Bollini, George Kozak, and Monika Mevenkamp for the ideas. I ended up choosing Andrea's to try first, and I think it may work best for our needs.
To implement Andrea's idea, you simply select a Dublin Core metadata field (I chose dc.relation.uri as we weren't using it for anything, and this is a "related" item), add the URL to the zoomable image to that DC metadata field for that object, edit dspace.cfg to customize webui.itemdisplay.default to display that DC field (complete with (link) at the end), and bounce your servlet container. If you choose a DC field that does not have a key value associated with it as a name, you will need to edit Messages.properties in [dspace-src] and rebuild DSpace. Or cheat like I did and just copy the Messages.properties file out of the jar, edit it to add the key value, and copy the file to [dspace]/webapps/jspui/WEB-INF/classes/ in my servlet container. Be sure to bounce the servlet container after editing. Details on Messages.properties here: https://wiki.duraspace.org/display/DSPACE/TechnicalFaq#TechnicalFaq-HowdoIupdateMessages.propertieswithoutrebuildingDSpace I chose Andrea's solution because it seemed to have the lightest touch on the source code, plus it provides the option for exposing this extra URL via OAI when the object data is harvested from DSpace. It does (possibly) abuse Dublin Core a bit, so metadata mavens out there may recoil in horror, I don't know. I had actually worked on a solution similar to George's when we were on DSpace 1.8.x, but I didn't like storing an HTML file as a bitstream of an object as a type of redirect. His solution works pretty well, though. Monika's solution is another good way to handle the link, if you already have the URL saved as DC metadata. Thanks again to everyone that offered solutions! -- Stacy Pennington Information Technology Services Rhodes College 901-843-3968 -----Original Message----- From: Pottinger, Hardy J. [mailto:[email protected]] Sent: Friday, March 21, 2014 9:16 PM To: Pennington_Stacy; [email protected] Subject: Re: [Dspace-tech] Linking from DSpace Object to External URL Hi, Stacy, I wonder if you wouldn't mind writing up your solution, once you've gotten it all settled? It sounds interesting. I've been kicking around the idea of setting something similar up, and there are obvious tie-ins with the streaming project underway. [1] Thanks! [1] http://tinyurl.com/dspace-streaming -- HARDY POTTINGER <[email protected]> University of Missouri Library Systems http://lso.umsystem.edu/~pottingerhj/ https://MOspace.umsystem.edu/ "Debug only code. Comments lie." On 3/21/14 4:25 PM, "Pennington_Stacy" <[email protected]> wrote: >Last week, I updated our DSpace from 1.8.2 to 4.1 without many (any?) >issues. Kudos to everyone on this list that worked on the DSpace 4.x >releases, whether as a developer, contributor, tester, or whatever. >Your efforts are appreciated! > >I'm wondering how to do something that seems pretty simple and can't >find any leads in the DSpace docs or wiki on how to do it. I would like >to provide a hyperlink from a DSpace object's page (we are using JSPUI) >to an external location to showcase that object's bitstream using >technology not associated with DSpace. > >For example, I've got high-resolution images saved as objects in >DSpace, so that the lossless TIFF (huge) and lossy JPEG (much smaller) >are available in DSpace, complete with lovely DC metadata. I've now got >a Djatoka server running with OpenSeaDragon as a viewer, and many of >these large images can be viewed on the external Djatoka server using a >custom URL for that image. I want to link to that external URL from >within the DSpace JSPUI object page in the simplest way possible, >without modifying DSpace code. Is this possible? > >I know that this may be bad form for a repository, but I'm not >interested in modifying the JSPUI template pages to load the Javascript >viewer on the page or anything like that. I'm willing to store the URL >to the zoomable viewer in the object's metadata, which of course I can >do now in DC but it doesn't create a hyperlink; the user needs to >copy/paste the URL to get to the zoomable viewer. I just need a simple >link from the object page, and if that link stops working in the >future, that's OK. I can remove it at that time. The bitstreams are the >most important thing, but the user would get the most use out of the >simple, zoomable, external URL. > >Does anyone have any advice for me? Again, I'm interested in the >simplest, easiest way to do this link, one with the least number of >changes to the DSpace source code. > >Thanks in advance for any ideas! > >-- >Stacy Pennington >Information Technology Services >Rhodes College >901-843-3968 ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
