Uploaded image for project: 'DSpace'
  1. DSpace
  2. DS-4454

Private Bitstreams should still return name, content link

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Volunteer Needed (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: 7.0
    • Fix Version/s: 7.0
    • Component/s: REST API v7
    • Labels:
      None
    • Attachments:
      0
    • Comments:
      5
    • Documentation Status:
      Needed

      Description

      When a bitstream is private, the user should still be able to identify the bitstream name, and click on the button to either log in or request access.
      At this point in time, the bitstream AND the content is private.
      https://github.com/DSpace/DSpace/pull/2688 verifies the content is private, but there's no code nor test to prove the bitstream name, UUID and content link are visible (minimal requirements)

        Attachments

          Issue Links

          is duplicated by

          Code Task - A task for working on code, usually associated with a branch DS-4461 List reserved bitstreams in an item

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          is related to

          Task - A task that needs to be done. DS-4124 Create Integration Tests to prove access restricted Bitstreams cannot be accessed anonymously

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              benbosman Ben Bosman
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:

                  Zendesk Support