Deleted Bitstream tombstone page

Abierto
  • ¿Algo no está bien?
#5,794 1 comentario 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
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
angular, typescript
Área
frontend

Línea de trabajo

The request concerns the bitstream edit route /bitstreams/.../edit and the item bitstreams page /items/.../edit/bitstreams in dspace-angular, which currently fall through to /404 for deleted bitstreams. Start by finding where the bitstream edit page is resolved and where a deleted bitstream is treated as not found, and check the item bitstream list's data source for the deleted filter. Done means an admin sees a disabled form with a clear deleted notice, and deleted bitstreams no longer appear in the item list. The issue names no specific test, so confirm the expected behaviour with maintainers first, since it is linked to #4368 and has had no reply in about four months.

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

Descripción

component: Item component: versioning needs discussion new feature

Is your feature request related to a problem? Please describe.

Bitstream records with deleted=true always lead to /404 the DSpace UI, even for administrators.
This means we cannot display original versions of Bitstreams that have been replaced.

Describe the solution you'd like

When a Bitstream is deleted, administrators should be able to view its /bitstreams/.../edit

  • The page should clearly specify that this Bitstream has been deleted and is no longer accessible, and the form should be disabled
  • We shouldn't include deleted Bitstreams on /items/.../edit/bitstreams, as they would be linked from other edit Bitstream pages

Additional information

Relevant to #4368

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.