Describe the bug
When an admin user is trying to move an item from it's owning collection to a new collection the DSpace UI caching does not reflect the change without first refreshing the page. This leads endusers to assume that the item has not been moved to the new collection. It seems that when you move an item for the first time the change is not reflected. A refresh displays the move has been made and further moves are reflected instantly. But the initial move does not.
To Reproduce
The user wants to move an item from one owning collection to another.
They are logged in and have admin permissions.
They navigate to the item page click the edit button and navigate to the 'Status' tab.
They click the 'Move this Item to a different Collection' button and are navigated to the 'Move Item: xxx' page.
They search/select a collection from the dropdown.
They check the 'Inherent policies' (where applicable) checkbox and click the 'Save' button.
They are displayed a success pop-up.
Expected behavior
The owing collection display in the breadcrumbs should be updated to reflect the move
Note
It was also highlighted that when selecting a Collection from the dropdown it was not clear that a selection had been made. Clicking on the dropdown does not instantiate a visual change, i.e. it is not clear to the enduser the selection has been made. There is a bit of highlighting which is displayed as either a bit of greying of the background of the selected element or as a thick outline on the selected element but the enduser did not recognise this as confirmation that their selection had been made.
Describe the bug
When an admin user is trying to move an item from it's owning collection to a new collection the DSpace UI caching does not reflect the change without first refreshing the page. This leads endusers to assume that the item has not been moved to the new collection. It seems that when you move an item for the first time the change is not reflected. A refresh displays the move has been made and further moves are reflected instantly. But the initial move does not.
To Reproduce
The user wants to move an item from one owning collection to another.
They are logged in and have admin permissions.
They navigate to the item page click the edit button and navigate to the 'Status' tab.
They click the 'Move this Item to a different Collection' button and are navigated to the 'Move Item: xxx' page.
They search/select a collection from the dropdown.
They check the 'Inherent policies' (where applicable) checkbox and click the 'Save' button.
They are displayed a success pop-up.
Expected behavior
The owing collection display in the breadcrumbs should be updated to reflect the move
Note
It was also highlighted that when selecting a Collection from the dropdown it was not clear that a selection had been made. Clicking on the dropdown does not instantiate a visual change, i.e. it is not clear to the enduser the selection has been made. There is a bit of highlighting which is displayed as either a bit of greying of the background of the selected element or as a thick outline on the selected element but the enduser did not recognise this as confirmation that their selection had been made.