[
http://jira.dspace.org/jira/browse/DS-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10915#action_10915
]
Richard Rodgers commented on DS-430:
------------------------------------
Hi Jim:
Thanks for exercising the Embargo stuff - it really helps to make it more
comprehensible. To your last points:
The reason the lift date is characterized as 'computed' is that you can express
terms other than a specific date which can be 'computed' or 'interpreted'. A
trivial example would be terms like '60 days', '3 months' etc. The Embargo
system has a place for a plugin to do this 'interpretation' (when the item is
installed in the archive). I think your confusion arises from the fact that we
offer 'out of the box' the simplest case: that in which an actual date is
entered by the submitter. You are absolutely right that in this case there is
no computation - the date is passed on as is. One can even imagine terms that
only indirectly reference dates at all, e.g. 'standard Elsevier terms'. (which
your plugin would know what to do with). Since the possible range of these
interpretations is quite large and various, we initially only offered the
straight date pass through. If other common cases are identified, we can easily
bundle in other plugins for you to use in the future.
As to point 2, yes, the invocation of the lifter is amenable (and in fact was
designed) to be cron scheduled.
Please post any other observations or questions to this issue, and thanks again.
> 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
