Usage@Bulk deletion

• Usecase: Bulk deletions of replaced AIPs versions

This agenda only allows deletions of AIPs which were already replaced with newer version (SIP versioning). The AIPs are identified by comma separated list of AIPs identifiers. Such identifiers might be found for example using filters in AIP search form

• Latest data version flag set to false
• XML version number = 1 (to reduce the result list, since we need AIP ID which is the same for all XML versions of the same AIP)

It could have happened, that the AIP version which we have identified as "not the latest one", could be in fact the latest one in PERSISTED state. This can happen for example if the newer / the newest version of the AIP has been deleted using deletion request. If this happens, then deletion of such AIP in bulk request is skipped by default. User can change this behavior checking the Delete even if newer versions have been deleted checkbox when creating the bulk deletion request.

Deletion of AIP is also skipped if the AIP is already deleted, it was ingested in debug mode or it is the latest AIP version (since those might be deleted only through a deletion request).

AIPs are deleted one by one, hence if a problem occurs during bulk deletion, the already deleted AIPs won't revert to previous state.

Deletion at the Archival Storage is asynchronous: once Archival Storage responds to the deletion call, the package might be considered as deleted. Archival Storage manages potential further errors in the async process on its own.