We enable adding a notes field at review/list level to complement our acquisitions operations. Notes may be displayed with other list-level information in each review, so they're visible when reviewing each item.

At Nottingham, purchasing is managed by set rules/ratios and budget codes based on student numbers, faculty, etc. These must be recorded outside of Aspire and cross-checked before orders are produced. A notes field would let us enter the review's purchasing rule and budget. Acquisition employees could see this information when reviewing things without consulting external sources. https://thebackrooms.onl

Purchasing is a significant outcome of list reviews, therefore supporting that process will improve our workflows and efficiency.

I also support the idea of being able to add notes when requesting a review. This way you can advise why you are requesting a review if there is a specific section or title that needs looking at.

We fully support this idea of adding a notes field at review/list level, which could be used to record key information to support our acquisitions workflows. The notes field could be displayed along with other list level information within each review, so that it is visible when reviewing each item.

At the University of Nottingham our purchasing is governed by set rules/ratios and budget codes, which are applied to lists based on student numbers, faculty, etc. Currently these cannot be recorded within reviews and have to be recorded against each reading list review outside of Aspire and cross-checked before orders are created. A notes field would allow us to record the purchasing rule and budget that applies when a review is received. Acquisition staff could then easily see this information as they review items without having to consult external information.

Purchasing is a key outcome of list reviews and incorporating information to support that process would be helpful to our workflows and improve efficiency.

Other universities may have other uses for such a field. By creating a general note field this provides flexibility to record and communicate other key information between review stages.

Get the best essay writing help from expert writers at affordable prices. Our experts deliver quality content before the deadline
https://buycollegeessay.org/essay-writing-help

I'm not sure whether any more consideration has been given to this idea since 2016 but I'll leave my two cents as I think it remains highly relevant.

As already pointed out, this feature would be especially useful when we receive a second review of a list with a couple of new additions that need to be ordered, without reviewing the whole list. It would be advantageous over filtering the list by "Alerts", as it would immediately indicate that only a few items need to be ordered, rather than relying on the assistants to realise that the whole list doesn't need to be reviewed for the sake of a few new additions. In this way, it would account for different workflows (e.g. how people use the review filters).

I also agree with other comments re efficiency of communications - perhaps the feature could be assigned a permission under certain roles to limit who can use it (e.g. librarians but not academics)?

This would be hugely beneficial to us and certainly help communication between our teams!

An excellent suggestion which could greatly improve the efficiency of the communication between the academic and the library.

In Reviews 2 we no longer have dates showing in the overall view which allowed us to see when an item had been added so being able to receive some direct communication about the list from the academics would be very valuable.

This would be very valuable to us. Instructions applying to the whole list could be included here, which would cut down the need for a note for each entry. It would be far more efficient.

We most definitely need a general note for a list as there are frequently actions needed for a whole list or multiple items, as noted in other comments posted.

We would also find this very useful.

Good idea!

Frequently, we find ourselves needing to add a general note for the entire reading list . Our workflow relies on both the librarian and acquisition team being able to view such information on the both "Edit List" and the "Review List" views.

As mentioned in older posts, it's not practical to replicate such information in the Note for library, across several/all items on a list.

http://ideas.talisaspire.com/forums/189041-talis-aspire-ideas-2013/suggestions/3939670-notes-for-assign-reviewer-request-review