It occurs to me that one way to do this would be to change the process of creating from a file so that a person could upload a file containing existing requests which would then update those requests with new data. Feels like this would require a toggle somewhere in the process to flag for Aeon whether the file was for creating or updating.

The Omeka S module for uploading data from CSVs (https://omeka.org/s/docs/user-manual/modules/csvimport/) is much more complex than this would need to be but it might provide some models, inclusing for the kind of toggle that I'm talking about (https://omeka.org/s/docs/user-manual/modules/csvimport/#item-import-advanced-settings)

This feature would now need to take into account Custom Fields and allowing batch editing of them as well.

This would be a great, integral feature for us as well. We would like to enable bulk edits to request fields. Currently only bulk routing is possible, but we would like, for example, to change a patron's scheduled date or edit a call number for multiple boxes in bulk.

Could also make batch editing a more robust Clone Request tool so that the old requests were simply cancelled out and new requests were created. This could also make it possible to create multiple requests from one request more easy (for instance when someone makes a request for "Box 1-20" and we otherwise have to clone the request 20 times to fix for someone).

If part of a multiple request edit, perhaps the former settings could be bumped down to the notes field for future reference.

Need to decide the best way to display this. The edit would not be reversible if the wrong requests were chosen.