[ http://jira.dspace.org/jira/browse/DS-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10913#action_10913 ]
Tim Donohue commented on DS-430:
You are definitely correct that, at this point, Embargo is not as well documented from a UI point of view.
However, it is available in the UI (though it is disabled by default). We've enabled it on one of our test instances for the Testathon.
It can be tested in JSPUI at:
Or XMLUI at:
However, to test it, you'd need to register with one of the above sites (with your email), and I can give you Admin or Submitter privileges. After you have those privileges, all you need to do is Submit a new item. At the bottom of the first "Describe" page, you'll see a new field called "Embargo lift date" which allows you to put an item under embargo until that date passes.
Send me an email and I'll give you access if you want to do some further testing (tdonohue [AT] duraspace.org).
Thanks for your comments about the Documentation! We'll try to get more details about using the embargo into the Documentation. In addition, you are correct that it's not limited to just theses and dissertations, and the text of the Documentation should be changed to make that clear.
> Key: DS-430
> URL: http://jira.dspace.org/jira/browse/DS-430
> Project: DSpace 1.x
> Issue Type: Bug
> Components: Documentation
> Reporter: Jim Ottaviani
> I realize the documentation in question is intended for programmers rather than less technical folks like myself, but I could not find information on how an embargo is set via the UI (either as an administrator or otherwise -- can it be set during the web-based submission process?). I gather that releasing embargoed items is a scriptable function, amenable to a cron job, but am not sure. Overall, implementation of this on the UI/collection administrator side is unclear to me, and it would be ideal to present some examples, somewhere. As it stands during the testathon, there was no way for me to evaluate its functionality and check for bugs.
> To comment more directly on the documentation as it is, it states that this is for theses and dissertations. We created an embargo feature locally, and use it for many things besides that. I would suggest making the language non-specific, unless this is explicitly tied to theses and dissertation metadata. (It doesn't appear to be, which is good.)
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira