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

Reply via email to