[ 
https://jira.duraspace.org/browse/DS-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26974#comment-26974
 ] 

Bram Luyten (@mire) commented on DS-1335:
-----------------------------------------

Added more clarifications on the current situation to the documentation:
https://wiki.duraspace.org/display/DSDOC3x/Item+Level+Versioning#ItemLevelVersioning-Creatinganewversionofanitem

We could close this ticket and create two new ones for the next version:
- make it configurable to give submitters rights to create versions (WITH 
workflow enabled)
- Creating an option for admins to skip the workflow when they create new 
versions
                
> Versioned items will re-enter Collection workflow approval?
> -----------------------------------------------------------
>
>                 Key: DS-1335
>                 URL: https://jira.duraspace.org/browse/DS-1335
>             Project: DSpace
>          Issue Type: Bug
>          Components: XMLUI
>    Affects Versions: 3.0
>            Reporter: Tim Donohue
>            Assignee: Kevin Van de Velde
>            Priority: Major
>             Fix For: 3.0
>
>
> I'm not sure if this is a misunderstanding of the new Item Versioning 
> feature.  But, I noticed that if an Approval Workflow is required for a 
> Collection, when you version an item that new version goes back into the 
> Approval process. 
> This seems rather odd to me that the initial item and the new version both 
> require approval. Plus, it ends up making versioning an item extremely 
> confusing.  Here's what happens:
> 1. Visit Item in a Collection having an approval workflow (e.g. 
> http://demo.dspace.org/xmlui/handle/10673/21)
> 2. Click "Create version for this item" & enter a reason
> 3. You re-enter the submission process & make changes
> 4. At the completion of the submission process you just get the normal 
> 'submission complete' page (which in itself is slightly odd as you just 
> created a version not a new submission. Shouldn't this instead send you back 
> to the item page?)
> 5. You manually return to the item page. It says a new version is still "in 
> workflow"
> 6. You then have to have someone go in and approve the new version before it 
> will appear publicly.
> So, there may be two questions here:
> * Shouldn't a new version of an item automatically skip over any approval 
> workflows (or at least provide an option to skip it)?
> * At the end of creating a new version, is there any way to return back to 
> the item page itself (rather than giving users the generic "Thanks for your 
> submission" confirmation screen, which is misleading)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to