please note that during the review of the endpoints I have noted and fixed another bug according to our general REST rules related to the use of the 400 response code instead of the 404 when the /process subpath of the script endpoint was used.
I want to mention that looking to the list of scripts it is clear that other scripts, such as export, import, harvest, should have a relaxed security as at least the community/collection admins should be able to run them but this is currently out-of-scope of this PR. The goal here was
to fix the curate script and open the script/process endpoint to other user than admins
The changes in this PR are needed to address the following bugs
please note that during the review of the endpoints I have noted and fixed another bug according to our general REST rules related to the use of the 400 response code instead of the 404 when the
/processsubpath of the script endpoint was used.I want to mention that looking to the list of scripts it is clear that other scripts, such as export, import, harvest, should have a relaxed security as at least the community/collection admins should be able to run them but this is currently out-of-scope of this PR. The goal here was
Finally, this PR is built on top of https://github.com/DSpace/RestContract/pull/221 you can check the changes belonging to only this PR looking to the latest commit https://github.com/DSpace/RestContract/pull/229/commits/8cedafabf4143fb9a041cb2aa1d47bbb65dad17e