This is a very good idea. I asked about this sort of thing some time ago and even shared my spreadsheet to show why I needed one, but it wasn't understood. Happy to see this re-visited.

This would be extremely useful to us and is much needed. It will ensure that any additional information regarding the digitisation is available and accessible by the whole team, when needed. We deal with a large amount of digitisations and this means we will not have to store notes regarding digitisations elsewhere.

Would find this a very useful feature to improve staff communication and training

This would be so useful for us. Currently we have a basic database set up to record the progress on chapters/articles that are not straightforward (eg applying to BL for copyright fee-paid copy; contacted publisher re. second extract permission, etc) because there is no option to enter these on the main TADC page. This is really time consuming. The lack of notes makes it very complicated when sharing work amongst staff as everyone has to check to see if a request is currently being worked on or whether they need to pick it up. I would be really grateful if this was prioritised as a development as it would save a lot of time and duplication of effort/possible mistakes due to lack of info. As someone responsible for training new staff on Aspire it would be great to be able to explain things with a more straightforward, simplified process.

I really think a free text box to add comments would be really useful and i'm surprised its not already there. Its also important that any comments added to a request are retained when the item is rolled over so that whoever is reviewing the request can see the previous history.

We also would like to see this progressed.

We also keep a spreadsheet and in many cases we don't want to override the concierge as it is logging the process. However, it is too fixed when it reaches copyright permission and we could use an intermediate stage to show that copyright is in process as this takes weeks and could be forgotten about.
We would ideally like to see a Request log showing the automated processing with an Add tab for free text entry to track the workflow decsions for this part of the process which happens outside TADC.

Another scenario when a note would be useful would be to record messages from BLDSC, eg when told to REAPPLY and date to reapply.

This would be massive help to keep track of permissions too as we have now had to create a separate spreadsheet to log the permission requests we have made, to whom and when, what request number etc. This is a step backwards and time consuming to have to keep referring to another record for information.

1. With regards to the above scenario's, for the renewals we are having to check back against the catalogue, see how many pages are in the book, see how many pages we have scanned from a publication and calculation whether they are in the 5%. A note/comment which could be carried over at renewal would overcome this.

3. At renewals we are having to print out the catalogue record, go and get the book and check the book, only to find out that the chapter is not contained within it. A retention note would save this headache.

We would definitely appreciate a means of adding further information to the requests, particularly with so many of us in our team, knowing what was happening with an item would be a useful addition to help with the audit trail for a request.

Some more scenarios which we have to record on a separate spreadsheet and which could be recorded on the system in a "note" field:

- Item not available from BL - requested from another library
- Copies of title all on loan, hold placed for digitisation team
- Copy missing from library stock so ordered from BL
- Copy on order at BL. Expected supply date given

The "stages" feature doesn't seem appropriate for this. These are not stages which apply to all requests. A note feature would help to record actions/reports which apply to only a small number of requests.

It would be nice if we had the option to say (tick a box) if we wanted to let the academic receive the email or not on the updated note's field.