[
https://jira.duraspace.org/browse/DS-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Diggory reopened DS-171:
-----------------------------
Assignee: Mark Diggory
I would like to resurrect this Issue because we have started working on an
Embargo solution that actually uses the start/end dates of resource policies to
enforce the embargo rather than a cron tab script. The new approach allows for
Embargo to be applied at either the Item level or individual Bitstream levels
and does not require executing a cronjob to adjust the state of the Item.
The AuthorizationManager already supports the enforcement of timeframes in
resourcePolicies. I would like to extend ResourcePolicy itself to be a better
DSpace Domain Model citizen and that would include having name and description
fields available to define the reason for a resource policy being set.
As we evolve the Metadata capabilities to support system/tech/admin/descirptive
metadata sections for all parts of the item, we can consider that the
ResourcePolices will inform the production of metadata about the embargo state
of the Item being exposed in OAI / SWORD /METS packagers and so-on. But for
now, we really need to make the Resource Policies be the mechanism that
enforces the policies within the system and not some metadata field set in the
item metadata description.
Mark
> Embargo_on_Bitstream_(JSP)
> --------------------------
>
> Key: DS-171
> URL: https://jira.duraspace.org/browse/DS-171
> Project: DSpace
> Issue Type: Improvement
> Components: JSPUI
> Reporter: Charles Kiplagat
> Assignee: Mark Diggory
> 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
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
