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

Deleting a primary bitstream does not clear the primary_bitstream_id on the bundle table

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.5.0, 1.5.1, 1.5.2
    • Fix Version/s: 1.6.0
    • Component/s: None
    • Labels:
      None
    • Attachments:
      1
    • Comments:
      1

      Description

      If you delete a bitstream that is marked as a 'primary' bitstream, then the primary_bitstream_id field on the bundle table is not cleared.

      As this is a foreign key relationship, it causes an integrity constraint violation when the cleanup script attempts to remove the bitstream.

      Further, as the cleanup script doesn't isolate each bitstream cleanup, it has the effect of stopping the cleanup script from clearing any deleted bitstreams in that repository.

        Attachments

          Activity

            People

            • Assignee:
              cjuergen Claudia Jürgen
              Reporter:
              grahamtriggs Graham Triggs
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: