[
http://jira.dspace.org/jira/browse/DS-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10914#action_10914
]
Jim Ottaviani commented on DS-430:
----------------------------------
Thanks Tim,
I tried it out and this looks like it works fine -- the UI is certainly
straightforward. I can't tell how the record looks yet (it's in the workflow)
but I'm sure that will be fine as well.
To get back to the notion of releasing the embargo, I found
"embargo.field.lift" coupled with its description as "DC metadata field to hold
computed "lift date" of embargo" confusing. Since the UI has the submitter
specify a release date, what has to be computed here? I suspect (hope!) that
this is something more clear to the programmer community than me...
Also, it appears that the embargo must be lifted by an invocation of the
appropriate plugin. As long as this invocation is amenable to being run as a
cron job (such that the plugin can be instructed to run on a nightly basis,
probably in tandem with indexing functions, etc.) this will be great. Again, I
assume it is, but was not sure when reading the manual.
> 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
