UI Caching Issue When Admin User Is Attempting To Move Item Between Collections

Abierto
  • ¿Algo no está bien?
#5,734 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
42/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
angular, typescript
Área
frontend

Línea de trabajo

The bug is in the Angular UI of dspace-angular: after moving an item to another collection, the breadcrumb still shows the old owning collection until a page refresh. Start by finding the move-item page component and the NgRx store actions/reducers that refresh the cached item after a move. Done means the breadcrumb updates right after a successful move, confirmed by a spec covering that component.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

affects: 9.x bug component: Item help wanted low priority

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.

Lenguaje dominante
TypeScript
Estrellas
180
Forks
577
Merge medio
2 d 1 h
PR fusionados (30 d)
100

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de DSpace/dspace-angular

Todos los issues de DSpace/dspace-angular

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.