[
https://jira.duraspace.org/browse/DS-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20382#action_20382
]
Tim Donohue edited comment on DS-171 at 5/18/11 5:46 PM:
---------------------------------------------------------
Re-Closing this issue. Please open up a new issue to describe any new changes
to the DSpace Embargo feature (DS-317) which was released in 1.6.0.
This current issue (DS-171) should be considered obsolete, as it describes an
unsupported implementation of "Embargo" that worked in pre-1.6.0 DSpace
(specifically 1.3.2, according to the wiki docs). The full description of this
unsupported implementation of Embargo is described on the wiki docs linked from
the description above:
https://wiki.duraspace.org/display/DSPACE/Embargo+on+Bitstream+%28JSP%29
was (Author: tdonohue):
Re-Closing this issue. Please open up a new issue to describe any new
changes to the DSpace Embargo feature (DS-371) which was released in 1.6.0.
This current issue (DS-171) should be considered obsolete, as it describes an
unsupported implementation of "Embargo" that worked in pre-1.6.0 DSpace
(specifically 1.3.2, according to the wiki docs). The full description of this
unsupported implementation of Embargo is described on the wiki docs linked from
the description above:
https://wiki.duraspace.org/display/DSPACE/Embargo+on+Bitstream+%28JSP%29
> Embargo_on_Bitstream_(JSP)
> --------------------------
>
> Key: DS-171
> URL: https://jira.duraspace.org/browse/DS-171
> Project: DSpace
> Issue Type: Improvement
> Components: Documentation, DSpace API, JSPUI, OAI-PMH, REST API
> (experimental), SWORD, Unit Testing Framework, XMLUI
> Reporter: Charles Kiplagat
> Priority: Major
>
> Bitstreams all have a resource policy. Most of the time this is a anonymous
> read policy. If a bitstream has no anonymous read policy then it cannot be
> read, so effectively it is under embargo.Now if you could set an end date for
> that embargo, it would be so much nicer. But this is already possible: DSpace
> allows resource policies to have a start date and an end date: so if you set
> an anonymous read policy with a start date of januari 1 2009, it is
> effectively under embargo until januari 1 2009. Now all this change does, is:
> * allow a submitter to set an embargo date when uploading a new file
> (optional) * allow an administrator to set the start and end dates of a
> resource policy for bitstreams * display the embargo date in a nice way when
> displaying an item with bitstream information, and disabling the link to that
> bitstream if it is under embargo (an administrator can always link to the
> bitstream)
> https://openaccess.leidenuniv.nl/handle/1887/12291
> http://wiki.dspace.org/index.php/Embargo_on_Bitstream_(JSP)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
