Keji
This is good news. Can I clarify what happens, firstly if a Review is already in progress and secondly if a publish event occurs and then the academic adds a further item the same day or within a few days but before the Review has started? I am concerned that we could get several Review Requests for the same list if a list is waiting to be reviewed.

Annette

I just wanted to update this as someone has asked a question. The element of this idea we have implemented is for publish events only. You can force a review to be requested every time a publish occurs. The review request will not be sent for editing/updates, only for publish events.

Definitely something we're also still eagerly waiting on.

As usual, I'd like to add that this should be flexible and configurable so it works well for any institution. I.e. there should be different alerts for the list being published for the first time and for updates to a list and each can be switched on/off by us. We should also be able to set the email address(es) to which each alert type should go.

If the update alerts highlighted the changes, that would be great - it would allow for easy forwarding to the relevant team (e.g. acquisitions, digitisation, etc).

(In the future, if we can get the necessary improvements to the hierarchy to allow us to assign a subject librarian to each school, having the alert go to the relevant subject librarian would be wonderful!)

This is similar to an archived request 'prevent academics from publishing list before sending for review', which has been commented on. Aspire say there are 'multiple publish/review scenarios that need to be covered and they should be configurable according to the tenancy'. They go on to say 'it is in our backlog for scheduling'.

Any timescales?