Embargo
-------
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
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
