Destruction

The destruction business logic is part of release 24.1

Introduction

A new collection of standard metadata fields has been introduced in https://mediahaven.atlassian.net/wiki/spaces/CS/pages/4040359937 to allow for the destruction of an object as part of its lifecycle by changing the https://mediahaven.atlassian.net/wiki/spaces/CS/pages/4082958355 to ultimately the value Destructed.

Destruction

Destruction has the following implications

  • The https://mediahaven.atlassian.net/wiki/spaces/CS/pages/4082958355 changes to the value Destructed

  • Because the record status changes to the valueDestructed, the changes to the value Archive and the object will no longer be visible to regular users, namely those users lacking the function ACCESS_PHASE_ARCHIVED as described in .

  • Generates an Event of type UPDATE.DESTRUCTION

  • If the is Data, and hence it is one of the , then all its child representations will be logically deleted but the data object itself is not deleted. The effect is only the metadata remains whereas the storage will be ultimately reclaimed when permanently deleting the representations after the recycling grace period.

  • If the is DataFlat then the object itself will be logically deleted and its metadata and storage will be ultimately reclaimed when permanently deleting the representations after the recycling grace period

Planning for Destruction

If the metadata field Governance.AutomaticDestruction.ExpectedDate is filled out with a particular date, then the system will automatically perform the destruction at the given date with the effect described in the previous section. See for the full reference of the new metadata fields.

The new metadata field Governance.RetentionPeriod can be used to store in the interval to retain the object. As of version 24.1 there is no automatic mechanism that fills out the Governance.AutomaticDestruction based on the Governance.RetentionPeriod. It is the responsibility of the customer to fill out the Governance.AutomaticDestruction manually or a custom plugin is written for the customer that calculates this field.