There is a class called PatchBadRequestException currently within DSpace 7 which seemed to be specifically made for the cases where a Patch would cause a BadRequestException. However there's no Patch specific logic within this class, so it would be a quick win to refactor this name to a more generic one so that it can be reused in several other places without the need for making a new Exception class to cover any other BadRequestException cases.
Currently any instance of 'Throw new BadRequestException' fails to give a proper status code. It currently provides a 500 status code whereas a 400 status code would be expected. I would like to re-use this above mentioned class to properly handle this type of BadRequestException when the code it's being discovered in isn't specific to a Patch.