[ 
http://jira.dspace.org/jira/browse/DS-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10601#action_10601
 ] 

Larry Stone commented on DS-267:
--------------------------------

I think it's confusing to use the policy actions DEFAULT_ITEM_READ and 
DEFAULT_BITSTREAM_READ to, effectively, store the policies for later deployment 
without making any changes that affect the actual access controls.  There is 
already enough confusion about those actions!

It would be more clear to simply add a new action, "PENDING_READ", and then 
just rename every READ to PENDING_READ while the Item is in workspace, 
workflow, withdrawn, ...or embargoed.  (as you might have guessed, I have an 
axe to grind, having implemented the "Harvard" embargo.)

The mechanism you use to implement "withdrawn" status will also work for 
embargoes, they are very similar.  It is a great improvement, since currently 
the reinstatement or lifting of an embargo can only apply the default, 
inherited, policies; now you can restore exactly the read policies it had 
before being withdrawn or put under embargo.  

With a change to a separate action like PENDING_READ, I'm in favor of this 
patch.  It's kludgy, but so is the whole access policy system.

> Item submission - possibility to overwrite the default item policies as 
> inherited from the owning collection during item submission
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DS-267
>                 URL: http://jira.dspace.org/jira/browse/DS-267
>             Project: DSpace 1.x
>          Issue Type: New Feature
>          Components: DSpace API
>            Reporter: Claudia Jürgen
>         Attachments: default-read-permission.patch
>
>
> At the moment the item policies are derived from the collection settings 
> DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ.
> It is not possible to influence the policies during submission only 
> afterwards by editing the policies.
> One should have the choice to either use the default inherited policies or 
> set policies during submission.
> Selectable policies should be configurable in order for submitters to use 
> them.

-- 
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

       

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to