2-step workflow display in DSpace 7

178 views
Skip to first unread message

Fitchett, Deborah

unread,
Jun 22, 2023, 5:29:30 PM6/22/23
to dspace-c...@googlegroups.com

Kia ora koutou,

 

We have a two-step approval process:

  • “Check submission” (workflow_step_2) lets curators reject, edit, or approve
  • “Final check” (workflow_step_3) lets curators edit or approve

Curators often want to choose tasks depending on which stage it’s at, so they can work through a set of Check-submission items all at once, or work on a set of Final-check items.

 

In DSpace 5, we configured the list of tasks in the pool to include a column displaying the stage each task was at. We’ve done some other custom configuration (as you can see) but I’d thought the option to list the workflow step was relatively out-of-the box – maybe I’m wrong though.

 

 

In DSpace 7.4, it seems that by default, no matter which workflow step the item is at, it shows with the status “Waiting for Controller”, so curators can’t identify what stage the item is at until after they’ve claimed it. Before we put this up as an issue, are there any ways we’ve missed that we can set a status based on the workflow step, or otherwise make the workflow step visible to the curators?

 

Ngā mihi,

 

Deborah

––––––––––––––––––––––––––––––––––

Deborah Fitchett (she/her) MLIS, RLIANZA

Associate University Librarian, Digital Scholarship

 

––––––––––––––––––––––––––––––––––

Learning, Teaching and Library – Te Whare Pūrākau

PO Box 85064, Lincoln University

Lincoln 7647, Christchurch, New Zealand

+64 3 423 0358

deborah....@lincoln.ac.nz

ltl.lincoln.ac.nz

 

––––––––––––––––––––––––––––––––––

Lincoln University

Te Whare Wānaka o Aoraki

––––––––––––––––––––––––––––––––––

 




"The contents of this e-mail (including any attachments) may be confidential and/or subject to copyright. Any unauthorised use, distribution, or copying of the contents is expressly prohibited. If you have received this e-mail in error, please advise the sender by return e-mail or telephone and then delete this e-mail together with all attachments from your system."
Message has been deleted

Fitchett, Deborah

unread,
Aug 28, 2023, 6:21:46 PM8/28/23
to Daryl M. Grenz, dspace-c...@googlegroups.com

Kia ora Daryl,

 

Thanks – I eventually did find that issue on the github project site but it looks like it is a matter of waiting for someone to volunteer to fix it. Unfortunately I’m getting the strong impression (from general silence on the mailing list, on that github issue, and from discussions with Atmire who’ll be hosting our upgraded site) that there aren’t any real workarounds.

 

My own team are going to be keeping their own spreadsheet to track what stage each item is in, which is less than ideal, and once our upgrade settles down I’ll be discussing with them whether we actually need to keep the two-step process.

 

Following the upgrade I’ll also be collating a list of the various bugs / desirable features we’d like to be addressed, and seeing if we’ve got budget to pay for development for any of these (aiming to contribute to the main codebase of course). No guarantees this issue will make the top of our list, but if it does I’ll keep you in the loop.

 

Deborah

 

 

 

From: Daryl M. Grenz <daryl...@kaust.edu.sa>
Sent: Tuesday, August 29, 2023 2:15 AM
To: Fitchett, Deborah <Deborah....@lincoln.ac.nz>
Cc: dspace-c...@googlegroups.com
Subject: RE: 2-step workflow display in DSpace 7

 

Caution: This email originated from outside our organisation. Do not click links or open attachments unless you recognize the sender and know the content is safe.

 

Hi Deborah,

 

We have similar step labels showing in DSpace 5 and are looking to see if we can do something similar in DSpace 7. It looks to me like it has been raised as an issue but no one has volunteered to fix it (https://github.com/DSpace/dspace-angular/issues/1609 ).

 

If you find a solution before it is fixed in the main code, please share it as it would be helpful to us and potentially others as well.

 

Regards,

Daryl

--
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-communi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/ME3PR01MB75244F0B835EF0150AC9B23BC522A%40ME3PR01MB7524.ausprd01.prod.outlook.com.

Aroldo Rique Júnior

unread,
Jul 28, 2025, 1:00:55 PMJul 28
to Fitchett, Deborah, dspace-c...@googlegroups.com, DSpace Technical Support, paulo...@mpf.mp.br
Hello everyone.

A friend here from my work (Paulo Matos - paulo...@mpf.mp.br) discovered a solution for this situation: using the step_authority metadata provided by Solr.

Just create a searchFilter in discovery.xml:

<!-- Used only to READ "submitter" facets (managed programmatically at SolrServiceImpl) -->
    <bean id="searchFilterSubmitter"
        class="org.dspace.discovery.configuration.DiscoverySearchFilterFacet">
        <property name="indexFieldName" value="submitter" />
        <property name="type" value="authority" />
        <property name="metadataFields">
            <list>
                <value>placeholder.placeholder.placeholder</value>
            </list>
        </property>
    </bean>


The result is this:

image.png

Aroldo




--

Aroldo Rique Júnior

unread,
Nov 17, 2025, 8:43:42 PM (11 days ago) Nov 17
to Fitchett, Deborah, dspace-c...@googlegroups.com, DSpace Technical Support, paulo...@mpf.mp.br
My apologies, everyone. The correct filter is this:

<bean id="searchFilterEtapa"
        class="org.dspace.discovery.configuration.DiscoverySearchFilterFacet">
        <property name="indexFieldName" value="step" />

<property name="type" value="authority" />
        <property name="metadataFields">
            <list>
                <value>placeholder.placeholder.placeholder</value>
            </list>
        </property>
    </bean>
Reply all
Reply to author
Forward
0 new messages