Bugs item #2171771, was opened at 2008-10-16 09:07 Message generated for change (Settings changed) made by tdonohue You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=119984&aid=2171771&group_id=19984
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Out of Date Priority: 5 Private: No Submitted By: Claudia Juergen (cjuergen) Assigned to: Nobody/Anonymous (nobody) Summary: Withdraw and reinstantiate items might change their policies Initial Comment: On withdrawal of an item the associated policies are removed and on reinstantiation new policies are assigned based on the default settings of the collection. These might differ from the orginial item policies. ---------------------------------------------------------------------- Comment By: Claudia Juergen (cjuergen) Date: 2009-03-04 06:51 Message: Hi Andrea, in case of withdrawn items, these should keep the policies associated with them. As for the other cases where policies change: a) last bitstream from bundle original removed will remove the bundle original, on adding new bitstream the bundle will be recreated Here the bundle should not be removed and it's policies kept, so that the newly added bitstream inherits these policies. This should be accompanied by a not if the policies from the bundle diverge from the default policies b) on item creation, no bundle created (skip file upload) In this case the bundle should derive it's policies from the default_item_read similar to a new submission. Claudia ---------------------------------------------------------------------- Comment By: Andrea Bollini (bollini) Date: 2009-03-04 04:06 Message: Hi Claudia, what do you think that should be the right behaviour? Keep the previous policies can be difficult because we need to handle it in a different way than the standard (also if the policy gives access to the resource we need to prevent it because the resource is withdrawn...) Do you think that a note/warning would be appropriate and solve this issue? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=119984&aid=2171771&group_id=19984 ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
