[
https://jira.duraspace.org/browse/DS-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26596#comment-26596
]
Tim Donohue commented on DS-1335:
---------------------------------
[~mdiggory] -- that's a good point. I guess I didn't realize that normal
submitters can create a new version as well.
An alternative here would be to make it clearer what is going on in the process
& provide more information to the users. I think part of the confusion is that
when you are creating a new version, you just go through the normal submission
process again, and the final confirmation screen doesn't make it clear that
your new version may require additional review/approval. I obviously don't
mind that we are reusing the submission process in this way (it's a neat
trick). But I think that we may want a slightly customized submission process
(with slightly different language) -- otherwise I worry users will just get
lost and not understand what is going on.
Even as a DSpace expert I got completely lost when I completed a new version
and it didn't appear immediately. I couldn't figure out what was going on. If
there was some better explanation on either the final Submission Confirmation
page and/or on the Item page itself ("A new version is waiting on workflow
approval."), then that could go a long way towards usability. As it is, it's
just a bit confusing & seems like your version has essentially disappeared.
> 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
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
