Comment 1 for bug 1276874

At MVLC, we would do this with a table in a local schema (mvlc.temp_copy_changes, or similar). We'd record the copy id, what changed, the old and new values. Then, we could later run a script to set them back to the regular copy location. It was more generic than that and could be used for status and some other fields as well. This required central site intervention since library staff can't run SQL queries in the database.

I think having a feature like this would be very handy. How that would be implemented, I'm less sure of at the moment.

It could be done more or less with copy buckets. If you are mixing items from different locations, the safest thing would be to make a bucket for each origin copy location and maybe put that location's name in the bucket name as a reminder. Still not as convenient as what the bug description desires.