Bugs item #1169975, was opened at 2005-03-24 10:05 Message generated for change (Settings changed) made by tdonohue You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=119984&aid=1169975&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: Authorisation Group: 1.2.1 >Status: Closed >Resolution: Out of Date Priority: 5 Private: No Submitted By: Jasper van den Bosch (japrowitz) Assigned to: Nobody/Anonymous (nobody) Summary: workspace item policy not updated after workflow change Initial Comment: The following course of action leads to a failing workflow: - An item is submitted to a collection which does not have a workflow. The submission is not finished, it is saved to the workspace - The administrator adds a workflow-step to the workflow of the collection of the submission in progress - The user picks up the item and finishes the submission - Another user having access to the subsequent workflowstep logs in and tries to accept the task. The acceptance of the task will fail in item.canedit() I backtracked it to the fact that the initial rights of an item are created (resourcepolicy) when the collection is submitted. When the administrator adds a workflow, the rights of the items in the submission progress are not updated with the new rights belonging to that change. This could be solved by updating the resourcepolicies according to the new situation when changes are made to either workflow or authorizations of a collection. Attached is the DSpace log containing some extra output added by me to track this bug. ---------------------------------------------------------------------- Comment By: Claudia Juergen (cjuergen) Date: 2008-09-04 11:03 Message: Logged In: YES user_id=1209523 Originator: NO Another use case which with changing staff/responsibilities quite often occurs is that the worflow group members change and the changes take no effect on existing workflows. At this point one can a) change it on db level b) ask the submitter to resubmit the item Especially the latter does not increase the confidence of self-submitters in the repository. ---------------------------------------------------------------------- Comment By: James Rutherford (jrutherford) Date: 2007-04-11 13:52 Message: Logged In: YES user_id=1472833 Originator: NO This is a tricky one. It's debatable that if the item submission started before there was a workflow in place, then it shouldn't go into any workflow when it is completed. This will require further thought / debate before being "fixed" either way... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=119984&aid=1169975&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
