Hello Tim, Thanks for the reply, I would like to confirm that there is workflow set on collection, it is set by putting eperson on as editors but when receiving items from API they just get published, another test done was to add another eperson as submitter and do manual deposit using that eperson details, the item successfully remained in the workflow awaiting for editors to take task, also DSpace send emails to all editors on workflow to take task, only via API the items are published directly disregarding set workflow.
Please note email received when doing manual deposits : -----Original Message----- From: lewa...@email.com Sent: Wednesday, 15 May 2024 10:49 To: 1...@email.com>; sec...@email.com; th...@email.com; fou...@email.com; fi...@email.com Subject: A new item has been submitted: Title: Graphical data Collection: Research Outputs Submitted by: Lewatle Phaladi New task available. To claim this task, please visit your "MyGroup IR" page: https://repository.url.ac.za/mydspace Many thanks! The IR Team Regards, Lewatle On Tuesday 14 May 2024 at 18:54:03 UTC+2 DSpace Technical Support wrote: > Hi Lewatle, > > In DSpace 7, all items will be forced through the Workflow process as long > as the Collection has a Workflow enabled. If the Collection does *not* > have a Workflow enabled, then the Items will become immediately available > in the system. This works whether you submit the Item via the User > Interface or the REST API (after all, the REST API is how the User > Interface submits Items as well). > > To enable a Workflow at the Collection level, you need to set one or more > of the workflow "roles" (Editors, Final Editors or Reviewers) on the > Collection Edit pages: > https://wiki.lyrasis.org/display/DSDOC7x/Edit+Collection#EditCollection-AssignRoles > > To disable the Workfow, you'd delete these roles if they already exist. > > Tim > > On Monday, May 13, 2024 at 8:28:14 AM UTC-5 joem...@gmail.com wrote: > >> Dear DSpace Tech, >> >> I would like to ask how to make REST API comply with workflow on >> collection, I have collection where it have editors as explained "Editors >> are able to edit the metadata of incoming submissions, and then accept or >> reject them." All deposits are expected to remain in the workflow of users >> placed as editors but when receiving items from REST API they are jumping >> the workflow and get published immediately. Assist in how to set REST API >> or DSpace to force items coming from REST API to remain on the task pool >> for users to take task and edit items before publishing. On DSpace 6.X >> items were remaining on approvers task pool until users take task and >> publish or rejecting the submission. >> >> Regards, >> Lewatle >> > -- 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 dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/9dfe0026-9e4e-4886-aba4-0b570e08a989n%40googlegroups.com.
