Bug #2565

Deleting master multi-page digital object from parent level deletes objects from child levels

Added by Evelyn McLellan almost 13 years ago. Updated about 9 years ago.

Status:NewStart date:
Priority:LowDue date:
Assignee:Peter Van Garderen% Done:


Target version:-
Google Code Legacy ID:atom-615 Tested version:
Sponsored: Requires documentation:


Currently this leaves behind child-level descriptions without digital
objects attached. If, for example, the wrong object is uploaded and then
removed and replaced with the right object, then a second body of child
objects is produced and the original empty child objects remain. Is this
the desired behaviour, or should all the child-level descriptions be
removed when the master digital object is removed from the parent?

[g] Legacy categories: Digital object


#1 Updated by Peter Van Garderen over 12 years ago

  • Target version set to Release 1.0.8

[g] Labels added: Milestone-Release-1.0.8

#2 Updated by David Juhasz about 12 years ago

  • Target version set to Release 1.1

Bumped to Release 1.1

[g] Labels added: Milestone-Release-1.1

#3 Updated by Anonymous over 11 years ago

  • Priority set to Low

[g] Labels added: Priority-Low

#4 Updated by Evelyn McLellan about 11 years ago

  • Target version set to Release 1.2

Moved to 1.2.

[g] Labels added: Milestone-Release-1.2

#5 Updated by David Juhasz about 10 years ago

  • Target version set to Release 1.3

Roll over to Release 1.3

[g] Labels added: Milestone-Release-1.3

Also available in: Atom PDF