As a systems librarian, I want the DELETE methods in the Inventory API endpoints to support and require CQL in order to make batch operations on Inventory records more safe and useful
This one came up after a Librarian by accident removed all items in Inventory, thinking the API endpoints implemented CQL for all methods.
There are permissions in place in order to prevent these things from happening, so the solution/workaround for
CHAL-38 is already in place.
But what this feature could enable, is a great tool for batch deleting things, but at the same time making it harder to make mistakes.
1. Make the Inventory/Items and Inventory/Instances endpoinds support CQL queries
2. Make CQL required for these endpoints.
3. Put in some kind of threshold so a user cannot delete more than 20% of the objects in one go.