Thanks to all who responded. That was sufficient motivation for me to have another go at implementing embargoes in 1.5.1. Here's what I've discovered, and where I'm currently stuck. I hope someone will be able to nudge me in the right direction.
Embargo on Bitstream (JSP) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ http://wiki.dspace.org/index.php/Embargo_on_Bitstream This looks like a very nice implementation, requiring only changes to a few java and jsp files, and no modifications to the database as far as I can tell. Unfortunately it is only for 1.4.2 and before. Its author intends to re-implement it for 1.5, but has no immediate plans. Embargo on Bitstream v2 (JSP) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ http://wiki.dspace.org/index.php/Embargo_on_Bitstream_v2_(JSP) Officially for 1.4.2, this can be made to work in 1.5.1. The differences involve hunting down the correct java files and making the changes there instead of where described in the wiki page. This implementation treats the embargoed items as withdrawn items until the embargo period terminates. While this does work, it would be nicer to have some indication that the item exists though it is embargoed. User:Emetsger:Embargo ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ http://wiki.dspace.org/index.php/User:Emetsger:Embargo http://wiki.dspace.org/index.php/User:Emetsger:Embargo:Downloads_here http://wiki.dspace.org/index.php/JHU_Embargo_Patch_Documentation http://maven.mse.jhu.edu/embargo/faq.html This looks like the most full-featured implementation, and a patch for 1.5.1 exists. I just wish I could get it to work. What doesn't seem to be documented anywhere, except in the patch file, and the item-submission.xml file that it patches, is the crucial information that it necessary to edit this file and specify the collection handles that will have embargoes enabled. With the exception of '<message key="xmlui.administrative.collection.EditCollectionEmbargo.trail">Embargo settings</message>' in messages.xml , the patch file already seems to add everything mentioned in http://wiki.dspace.org/index.php/JHU_Embargo_Patch_Documentation. When I try to submit an item, I get an Infernal System Error, the relevant message from dspace.log seems to be: 2009-03-18 09:05:06,180 ERROR org.dspace.app.webui.servlet.SubmissionController @ Error loading step class'org.dspace.submit.step.EmbargoProcessor': java.lang.ClassNotFoundException: org.dspace.submit.step.EmbargoProcessor And sure enough, the EmbargoProcessor file is nowhere to be found in /dspace, though it does exist in my source: dsp...@esal-lr:~$ find dspace-1_5_1/ -name EmbargoProcessor* dspace-1_5_1/dspace-xmlui/dspace-xmlui-api/src/main/java/org/dspace/submit/step/EmbargoProcessor.java dspace-1_5_1/dspace-xmlui/dspace-xmlui-api/target/classes/org/dspace/submit/step/EmbargoProcessor.class Do I need to copy this class file file (and presumably others too) somewhere into the /dspace/webapps tree? Sean -- Sean Carte esAL Library Systems Manager +27 72 898 8775 +27 31 373 2490 fax: 0866741254 http://esal.dut.ac.za/ ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
