Deleted Bitstream tombstone page

Aperta
  • Qualcosa non va?
#5,794 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
42/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
angular, typescript
Ambito
frontend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
TypeScript
Stelle
180
Fork
577
Merge medio
2g 1h
PR unite (30g)
100

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di DSpace/dspace-angular

Tutte le issue di DSpace/dspace-angular

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.