Include "Notes" field when cloning requests.
When a request is cloned either within the Aeon Client, or from the online platform, can the information present in the "Notes" field of the original request transfer into the new request? For example: our local/staff notes, which indicate unique item locations populate into this field. When cloning, these notes do not transfer, which impacts turn around time and requires staff to either look at and copy notes from the original request, or locate the material in our ILS to find the notes. The latter happening more often with researcher cloned requests, as staff are unaware that it has been cloned. Thank you!
Penny White
shared this idea
-
Anne Marie Lyons
commented
Boston Public Library would like this feature, as well. Because custom fields cannot currently accommodate more than 255 characters, the Notes is the only field that they can use to potentially record information about conservation needs and outcomes (they are currently working on a conservation workflow in Aeon). The requests sometimes need to be cloned because materials might be reshelved in between the identification of conservation needs and the actual conservation activities. The information would be lost, though, because the Notes field is not included in the cloning.
-
Kathleen Monahan
commented
This would be helpful for us with activities! We keep class-specific notes about books in the notes field, and it'd be great if they transferred when cloning the activity.