Just wanted to add some more evidence on this. Doing some pre-semester tidying today, I contacted 8 of my lecturers who had Unpublished Changes on reading lists for modules coming up this semester. Without exception, they all replied to say sorry, they had forgotten/hadn't realised they hadn't published (no-one was still working on a list). So none of them had been alerted by the Unpublished Changes banner, probably because it was out of their view after adding items further down the list. Given there have been a lot of votes for this idea, any chance of an update?

Very much agree with Catherine's comment of 30th January about the wording of the Unpublished Changes banner for those who have Force Review on. I hadn't noticed that, as I have Acquisitions role myself so don't see the same wording! Should definitely be changed as Catherine suggests, to make it clearer that the list will NOT be reviewed until the academic hits Publish.

As a lot of our academics will access and edit directly from our learning management system it would be good to keep the Publish button very clear in their view.

Related to this (and probably not worth making a separate idea about?), I think the wording in the 'unpublished changes' banner is very misleading for list publishers without the Acquisitions role, ie academics, when you have Force Review switched on.

It currently says 'Unpublished changes! Your changes have been saved, but not published. The library acquisitions team will review the list for changes.'
(Screenshot below, from Talis' support article here https://support.talis.com/hc/en-us/articles/205644441-Publish-Review-workflow-options)

To me, this reads as though it's telling them we'll review the list anyway rather than emphasizing we will review the changes *when it has been published*.

It would be great if this wording was changed to something more like what it is for those who do not have Force Review on, eg: 'Unpublished changes! If you would like the library acquisitions team to review the list for changes, please select 'Publish.'

(I raised this with Talis when we switched on Force Review last autumn, and the feedback was logged with the Product team, but I haven't heard anything back as yet and the screenshot in the support article looks the same, so I assume it hasn't been changed.)

We've also seen the number of lists with 'published with unpublished changes' status go up, and I suspect a lot of the time it's us when we link an item to a list on receipt or similar, as well as academics forgetting to publish. I had to do a cleanup exercise recently which was time consuming (as I had to check which actually had noteworthy changes and might need a review requested).

I would love the warning banner to be pinned, and I also like Lucy's idea about highlighting the unpublished changes on the list. This would be a lot easier than clicking through to look at all the different 'recent changes' that may have been done in several batches.

Just want to add that we also feel this would be a great addition.

Since starting with New List Edit we have seen an uptick in the amount of lists showing as 'Published with unpublished changes', and this suggestion would likely help mitigate against this.

It might also be helpful to highlight all new items/sections on a list that have not been published with the yellow warning background. Then you could see exactly what will not be visible on the published version.

As we are rolling this out in the New Year, I have been training a lot of academics and this feature has been mentioned as something that would be useful.

Yes please!

This would be really useful.

I was thinking about this the other - good suggestion!

We’ve also found that since switching on new list edit our number of lists with unpublished changes have gone up considerably.

Good idea, it might need to keep its colour difference too, to stand out.

This is a sensible idea - I've been creating lists for years and have forgotten to publish several times especially when just doing a quick edit lower down.

Great idea

What an excellent idea! We also struggle with the same problem at Falmouth

This would be very useful for us at UEA as well, we've had feedback from a number of academic users that they sometimes miss the Unpublished Changes message if they're working on longer reading lists.