Dear Deividi,

we faced a similar problem recently in DSpace 7 and found a way to at least show the current reviewer's Name. This might help you.

We go to the HAL-Browser/REST-API of our repository and log in with an administrator account, then look up in the explorer field the following path:

/server/api/workflow/claimedtasks/search/findAllByItem?uuid=cfc2c83a-9c2f-47aa-bd03-cc3af6f311c4*

*The UUID here is just an example and needs to be replaced with the UUID of the item you are looking for.

Then it should show you the claimed task in the Response Body where you can find the Name of the task-owner/current reviewer:

                "owner": {
                    "id": "cfc2c83a-9c2f-47aa-bd03-cc3af6f311c4",
                    "uuid": "cfc2c83a-9c2f-47aa-bd03-cc3af6f311c4",
                    "name": "Simon Eiberger",


Kind regards from Germany

Simon


Am 19.08.2026 um 15:51 schrieb Deividi Moreira:
Hi everyone,

We are currently running *DSpace 8* and facing a challenge with workflow management. In certain situations, a reviewer claims an item for review but takes a prolonged time to complete it, causing publication delays.

To resolve this issue, we are looking into two specific features within the Administrator Tasks menu:

1.

    *Reverting to Backlog:* A button or action that allows an
    *administrator* to send an item currently under review back to the
    backlog (pool), making it available for redistribution to another
    reviewer.

2.

    *Reviewer Identification:* Displaying the *current reviewer's
    name* directly in the list of items under review.

We would appreciate any feedback from the community on the following:

 *

    *DSpace 8 Configuration:* Is there any native configuration in
    DSpace 8 that enables returning an item to the backlog or showing
    the reviewer's name in this list?

 *

    *Support in DSpace 9/10:* If this is not possible in DSpace 8, do
    *DSpace 9* or *DSpace 10* provide native support for these features?

 *

    *Custom Solutions:* If there is no native support across these
    versions, has anyone implemented a similar workaround, custom
    solution, or Pull Request that you would be willing to share?

Thanks in advance for your help!

Best regards,


--
*Deividi Fernando da Silva Moreira*
Universidade Federal de Ciências da Saúde de Porto Alegre - UFCSPA
--
All messages to this mailing list should adhere to the Code of Conduct: https://lyrasis.org/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 visit https://groups.google.com/d/msgid/dspace-tech/CAEbH%3DLAY_21%2B0%2B%2BXGrO72D0P9AN0bYtkxE2JtJAjtAFg%2BeGGDw%40mail.gmail.com <https://groups.google.com/d/msgid/dspace-tech/CAEbH%3DLAY_21%2B0%2B%2BXGrO72D0P9AN0bYtkxE2JtJAjtAFg%2BeGGDw%40mail.gmail.com?utm_medium=email&utm_source=footer>.

--
Simon Eiberger

Universität Ulm
Kommunikations und Informationszentrum
Abt. Informationssysteme
89069 Ulm
Tel: 0731 50-15582

--
All messages to this mailing list should adhere to the Code of Conduct: 
https://lyrasis.org/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 visit 
https://groups.google.com/d/msgid/dspace-tech/7e4419ef-ba45-4a3a-8b1b-7736a1415f1c%40uni-ulm.de.

Reply via email to