Hello Andrew,
good, that it was so easy to solve.
What might have happened is that you changed the workflow
responsibilites after the item has been submitted.
Changing this only has effects on newly submitted items, not ones
already in workflow. So someone might have been in charge, who is no
longer working with the system.
You must have had someone in the group for the workflow step. If the
group for the workflow step is empty, the step will simply be skipped.
Hope this helps
Claudia Jürgen
Am 03.02.2020 um 14:53 schrieb Andrew Kierig:
> Hallo Claudia and everyone!
>
> Thank you all for your responses. What we ended up doing was logging
> into the JSPUI and kicking it back to the submitter. They subsequently
> resubmitted it and it showed up in the approve/reject/edit task pool as
> normal. We’re still not too sure what exactly happened (again—all of
> the submission and editing privileges were set correctly), but at least
> we know how to fix it.
>
> Thanks again for everyone’s help.
>
> Best,
> Andrew Kierig
>
> Digital Publishing Lead
> George Mason University Libraries
>> --
>> 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 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/ba92da02-0b4a-3574-f11b-37d0663d2dda%40tu-dortmund.de.