Thank you!!! From: Richard Rodgers [mailto:[email protected]] Sent: Friday, May 21, 2010 1:54 PM To: Blanco, Jose Cc: Jizba, Richard; [email protected] Subject: Re: [Dspace-tech] More re: Embargo error on Approval
Hi Jose: See inline Thanks, Richard On May 21, 2010, at 10:27 AM, Blanco, Jose wrote: Hi Richard: Re #1 I don't think we'll ever have a need for 'forever', so we may use the date type, and I guess if they just enter a year, it will just lift the embargo on the 1st of the year. If we decide to us onebox, is there validation done on the date? I think date should work as you describe - but you should test, since there may have been some work on the DCDate class. Onebox doesn't validate dates. Re #2 I guess I was expecting a message telling me the bitsteam is embargoed when I tried to access the embargoed bitstream rather than a prompt to authenticate, and I just wanted to make sure this was the expected behavior. OK, I see the question now. That is the expected behavior - embargo piggybacks on existing DSpace authorization, so there is no 'special' status at all for embargoed items. This has the upside that you can use regular administrative tools, but the 'downside' that it's indistinguishable in the UI from a protected resource (that you'd have to log in for). One more question and then, I promise to let you get back to work. I customized our system with my own version of embargo a few years ago. In my implementation I withdraw the item, and then I run a cron that goes through a db table with dates to lift the embargo, and if an item is ready, it re-instates the item. I would like to start using dspace's embargo, so this will not be a problem with the items that from now own will be embargoed using dspace, but what do I do with the other ones. I don't think I can just add the terms field and expect it to work. My best guess as to what I should do is to keep my version lifting embargo for the ones I have embargoed so far using the cron I have in place, and also run the lifter for dspace for any new items until all the old ones are gone, and then stop running that old cron, and just run dspaces lifter. I have quite a few embargoed items - I think about 400. I just wanted to check. No problem, good questions all. I'd say your plan (dual track until old batch gone) is probably the best I can think of. One could write custom code to migrate the old ones, but if you have the mechanism in place, and it's not a hardship, then continue... Thank you again for all your help. Jose From: Richard Rodgers [mailto:[email protected]] Sent: Thursday, May 20, 2010 6:18 PM To: Blanco, Jose Cc: Jizba, Richard; [email protected]<mailto:[email protected]> Subject: Re: [Dspace-tech] More re: Embargo error on Approval Hi Jose: Re #1. Date would be safe, but then you would not be able to enter the 'forever' (open ended) value, which is not a date. I would normally just use 'onebox' (smaller than a text-area). Re #2. I'm not positive I understand the question, but the embargo does not hide the metadata or item page - it merely removes 'read' permissions on the bitstreams. Re #3. As noted in another email, this is a 1.6 bug. You can get details about fixing at: http://jira.dspace.org/jira/browse/DS-506 Thanks, Richard R On May 20, 2010, at 3:55 PM, Blanco, Jose wrote: Richard, Thank you very much for this documentation. I've been experimenting with it today, and I just have few questions. 1. It seems like making the terms field a date type in the input-forms.xml file would be the safest thing to do, instead of a textarea. Any thoughts on this? 2. I deposited an item and set the terms field to some value in the future. I am able to see the item and when I try to access the bitstream, I am asked to authenticate, is this how it's suppose to work? 3. I tried running /dspace/bin/dspace embargo-lifter But it can't seem to find it. I looked around for the file "embargo-lifter" but I can't find it. This is the error I get: [dsp...@pocarisweat bin]$ ./dspace embargo-lifter Command not found: embargo-lifter Usage: dspace [command-name] {parameters} - checker: Run the checksum checker - checker-emailer: Send emails related to the checksum checker - cleanup: Remove deleted bitstreams from the assetstore - community-filiator: Tool to manage community and sub-community relationships - create-administrator: Create a DSpace administrator account - dsprop: View a DSpace property from dspace.cfg - export: Export items or collections - filter-media: Perform the media filtering to extract full text from docuemnts and to create thumbnails - generate-sitemaps: Generate search engine and html sitemaps - harvest: Manage the OAI-PMH harvesting of external collections - import: Import items into DSpace - index: General index command (requires extra paramters) - index-init: Initialise the search and browse indexes - index-update: Update the search and browse indexes - itemcounter: Update the item strength counts in the user interface - itemupdate: Item update tool for altering metadata and bitstream content in items - make-handle-config: Run the handle server simple setup command - metadata-export: Export metadata for batch editing - metadata-import: Import metadata after batch editing - packager: Execute a packager - registry-loader: Load entries into a registry - stat-general: Compile the general statistics - stat-initial: Compile the initial statistics - stat-monthly: Compile the monthly statistics - stat-report-general: Create the general statistics report - stat-report-initial: Create the general statistics report - stat-report-monthly: Create the monthly statistics report - stats-log-converter: Convert dspace.log files ready for import into solr statistics - stats-log-importer: Import previously converted log files into solr statistics - stats-util: Statistics Client for Maintenance of Solr Statistics Indexes - structure-builder: Build DSpace commnity and collection structure - test-database: Test the DSpace database connection is OK - test-email: Test the DSpace email server settings OK - sub-daily: Send daily subscription notices - update-handle-prefix: Update handle records and metadata when moving from one handle to another From: Richard Rodgers [mailto:[email protected]] Sent: Thursday, May 06, 2010 5:53 AM To: Jizba, Richard Cc: [email protected]<mailto:[email protected]> Subject: Re: [Dspace-tech] More re: Embargo error on Approval Hi Richard: Try this document for a fuller explanation. Let me know of any questions not addressed in it. We will try to include it in the next release. Thanks, Richard R On May 5, 2010, at 6:02 PM, Jizba, Richard wrote: I finally realized that the Embargo Setter is reading dc.embargo.terms for the date rather than dc.embargo.liftdate. I've check our dspace.cfg file and there does not seem to be a mix-up. Nor is there a mix-up on the submission form. Perhaps I don't understand what these fields are for? What is dc.embargo.terms supposed to do? Richard _____________________________________________ From: Jizba, Richard Sent: Wednesday, May 05, 2010 4:05 PM To: '[email protected]<mailto:'[email protected]>' Subject: Embargo error on Approval Hello, We we try to approve an item that has been submitted with an embargo date (in dc.embargo.liftdate) we receive the following error: java.lang.NullPointerException at org.dspace.embargo.EmbargoManager.getEmbargoDate(EmbargoManager.java:166) Can anyone suggest how to resolve this? We are running 1.6. Richard Jizba Creighton University Omaha, NE <ATT00001.c><ATT00002.c>
------------------------------------------------------------------------------
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
