Hi Tim, thanks a lot for your detailed answer! We are currently trying if that idea will work for us, and I will get back to you with our results shortly.
Johannes Tim Donohue schrieb am Dienstag, 25. August 2020 um 17:20:56 UTC+2: > Hi Johannes, > > This is not supported in DSpace out-of-the-box and may be complex to > implement. In DSpace terminology, deposit *always* begins with a > "WorkspaceItem" object (which is an active submission). That object by > default sits in a single user's "workspace" until submitted...at which > point it becomes a "WorkflowItem". That is where the approval process is > triggered...and once approved, it becomes an (archived) "Item". > > So, the flow is generally: > > WorkspaceItem <-> WorkflowItem -> (Archived) Item > > As implied by the double arrows between WorkspaceItem and WorkflowItem, a > submission may move *between* those states one or more times prior to > becoming "accepted" and archived. > > Because of this nature, you may want to consider whether small tweaks to > your internal process could allow you to use DSpace mostly "as-is". One > (perhaps simplified) idea might be: > > 1. Author creates a publication idea as a (partially filled out) > Submission (i.e. a new WorkspaceItem). They submit this new idea (making > it a WorkflowItem), perhaps even to a "Submission Ideas" Collection > tailored for this initial approval. > 2. Superior reviews the idea (now a WorkflowItem), and provide > feedback by "rejecting" the submission (you could rename the reject button > as needed to "provide feedback"). (This turns the WorkflowItem back into > a > WorkspaceItem & sends it back to the Author for changes or enhancements, > along with the superior's feedback.) > 3. Author then looks at feedback and either cancels/deletes the > Submission (if not a good idea) or enhances it (if it was approved). They > potentially resubmit for full approval (either to the same Collection, or > maybe different one, depending on needs) > > I realize that flow is slightly odd, but it'd allow you to do a > WorkspaceItem (draft idea) -> WorkflowItem (initial approval) -> > WorkspaceItem (enhanced) -> WorkflowItem (final approval). It may also be > easier to customize the DSpace UI to support this flow of data, as it's a > more "natural" flow for the DSpace object model & submission/workflow > process. You also can customize submission flows per Collection, so you > could have one flow for the "draft idea" (in a private, draft Collection, > perhaps with limited metadata fields required and an uploaded file > optional) and another for the "final idea/paper" (in a public/private final > Collection, perhaps with more metadata fields required & an uploaded file > required). > > Just something to consider here. You also could do a heavier > customization here to try to add Workflow Approval *first*. But, it seems > (to me) like there will need to be something to approve (which implies to > me that you may need a WorkspaceItem first anyhow, even if it's just a > partially filled out one). > > Tim > > *--* > > *Tim Donohue* > > Technical Lead, DSpace > > [email protected] > > Lyrasis.org <https://www.lyrasis.org/> | DSpace.org <http://dspace.org> > > > > ------------------------------ > *From:* [email protected] <[email protected]> on behalf > of J <[email protected]> > *Sent:* Thursday, August 20, 2020 3:38 AM > *To:* DSpace Technical Support <[email protected]> > *Subject:* [dspace-tech] Additional workflow before submission? > > Hi all, > > we need an additional workflow in which authors can present a publication > idea to their superiors and get it approved. This additional workflow > should happen before the submission process, so instead of [Submission -> > Workflow] we need [Additional Workflow -> Submission -> Workflow]. > > At first glance we would try to implement this functionality as a custom > submission step, but are unsure if the assignment of others users during > the submission process would work. Or is there an extension available that > already would support our use case? > > Regards > Johannes > > -- > All messages to this mailing list should adhere to the DuraSpace Code of > Conduct: https://duraspace.org/about/policies/code-of-conduct/ > --- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-tech/6f301637-f584-4c19-967b-dc8a186d6d50n%40googlegroups.com > > <https://groups.google.com/d/msgid/dspace-tech/6f301637-f584-4c19-967b-dc8a186d6d50n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/cc8c5ceb-407f-4253-a1f7-c4a1417ee2c0n%40googlegroups.com.
