Deleted Bitstream tombstone page

Open
  • Is something wrong?
#5,794 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
angular, typescript
Domain
frontend

Research direction

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.

Written by the indexing model from the issue text.

Description

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

Dominant language
TypeScript
Stars
180
Forks
577
Avg merge
2d 1h
Merged PRs (30d)
100

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DSpace/dspace-angular

All issues in DSpace/dspace-angular

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.