Asking again here. Is there any way to delete "abandoned" submissions from
the database? Our editors sometimes accept submissions at the
"Accept/Reject/Edit" step that end up being duplicates or mistakenly
accepted for other reasons. Once they've accepted them there is no way to
reject them, only send them back to the task pool. We have thousands of
these as our repository is over ten years old!

Appreciate any help or stories from the SQL trenches...

On Mon, Oct 11, 2021 at 3:53 PM Alan Orth <[email protected]> wrote:

> Hi all,
>
> I've looked at both of these PRs and unfortunately they are for the
> configurable workflow (aka XML workflow). We are using the basic workflow
> so these won't work for us. That's a real shame because I have thousands of
> abandoned submissions from hundreds of editors over the past twelve years
> and I'd love to find a way to get rid of them. We are on DSpace 6.3.
>
> Regards,
>
> On Fri, Oct 1, 2021 at 7:06 PM 'Alexander Vielhauer' via DSpace Technical
> Support <[email protected]> wrote:
>
>> After testing and rereading the PRs, I can say that the workflow
>> administration (in DSpace7) is limited to workflow items which have been
>> submitted. Sorry for the confusion.
>> On 30/09/2021 18:06, 'Alexander Vielhauer' via DSpace Technical Support
>> wrote:
>>
>> Dear Hrafn,
>>
>> Thank you very much! From the PR I learned that DSpace7 has a handy admin
>> feature for browsing and deleting workflow items - another reason to push
>> for the upgrade! :)
>>
>> Best,
>> Alexander
>> On 24/09/2021 17:35, Hrafn Malmquist wrote:
>>
>> Hello Alexander
>>
>> To the best of my knowledge, there is currently no supported way of doing
>> this using DSpace UI.
>>
>> There are two PRs to DSpace 6 (assuming that's the version you're using)
>> intended to support such functionality:
>> https://github.com/DSpace/DSpace/pull/2200
>> and
>> https://github.com/DSpace/DSpace/pull/2076
>>
>> I've mostly looked at the latter one. It applies only to the XML
>> Configurable Workflow which I could not try out as our production servers
>> only use the basic workflow setup.
>>
>> Unfortunately I can't help you more.
>>
>> Good luck, Hrafn
>>
>>
>> On Fri, Sep 24, 2021 at 4:13 PM 'Alexander Vielhauer' via DSpace
>> Technical Support <[email protected]> wrote:
>>
>>> Dear list,
>>>
>>> what is your recommended workflow for deleting abandoned workspace items?
>>>
>>> We have a rather large dataset stuck in submission since the author
>>> started a new submission (which is now archived) instead of resuming his
>>> old submission.
>>>
>>> I cannot find a way though to delete workspace items via a command line
>>> operation or an admin feature in the UI. I'd rather not manipulate the
>>> database directly to allow the cleanup utility to take care of deleting
>>> the bitstreams.
>>>
>>> If anyone keeps track of this in their repo: How do you scan for "stuck"
>>> submissions and what are your thresholds and deadlines for notifying the
>>> authors and deleting the submission?
>>>
>>> Thank you and kind regards
>>> Alexander
>>>
>>> --
>>> Alexander Vielhauer
>>> Philipps-Universität Marburg | UB
>>> Digitale Dienste | Deutschhausstraße 9 | D226
>>> Tel. +49 06421 28-25290
>>>
>>> --
>>> All messages to this mailing list should adhere to the Code of Conduct:
>>> https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
>>> ---
>>> 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/2b00b729-5b64-8f95-91b5-b3a6c9cb4b10%40staff.uni-marburg.de
>>> .
>>>
>> --
>> Alexander Vielhauer
>> Philipps-Universität Marburg | UB
>> Digitale Dienste | Deutschhausstraße 9 | D226
>> Tel. +49 06421 28-25290
>>
>> --
>> All messages to this mailing list should adhere to the Code of Conduct:
>> https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
>> ---
>> 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/ae874de6-b24e-5a97-68e7-d4ff3ba96383%40staff.uni-marburg.de
>> <https://groups.google.com/d/msgid/dspace-tech/ae874de6-b24e-5a97-68e7-d4ff3ba96383%40staff.uni-marburg.de?utm_medium=email&utm_source=footer>
>> .
>>
>> --
>> Alexander Vielhauer
>> Philipps-Universität Marburg | UB
>> Digitale Dienste | Deutschhausstraße 9 | D226
>> Tel. +49 06421 28-25290
>>
>> --
>> All messages to this mailing list should adhere to the Code of Conduct:
>> https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
>> ---
>> 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/9ea7ca9d-501b-29fd-8927-ca1c68fab4f8%40staff.uni-marburg.de
>> <https://groups.google.com/d/msgid/dspace-tech/9ea7ca9d-501b-29fd-8927-ca1c68fab4f8%40staff.uni-marburg.de?utm_medium=email&utm_source=footer>
>> .
>>
>
>
> --
> Alan Orth
> [email protected]
> https://picturingjordan.com
> https://englishbulgaria.net
> https://mjanja.ch
>


-- 
Alan Orth
[email protected]
https://picturingjordan.com
https://englishbulgaria.net
https://mjanja.ch

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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/CAKKdN4Ven%3Dow%2BnncpZ%2B5%2B142k-jomEq-n58p%3DkNmLbFHRufEEg%40mail.gmail.com.

Reply via email to