Skip to main content
Skip table of contents

Compare Asset Deletion 1, 2 & 3

Asset deletion 3 is the successor of Asset Deletion 1 and 2 for deleting asset versions and asset files. It combines the advantages of the previous types. Find out about the differences between the three types.

Asset Deletion 2 is not available since 2019.1.

Overview table


Asset Deletion 1

Asset Deletion 2

Asset Deletion 3 

Policies for deletion

Deletes

Asset versions

Content versions

Asset versions

Always keep

-

First and last version (1)

First and last version (1)

Deletion rules

Asset version policies (configurable) + constraints (not configurable)

Asset version policies (configurable) + constraints (not configurable)

Asset version policies (configurable) + constraints (not configurable)

Policy automatically applies to its sub-type/sub-domain

No. A perfect match is necessary to apply a policy. Sub-domains and sub-types need extra policies.

Yes. If there is no perfect match, it applies the "parent" policy (from upper domain or asset type).

Yes. If there is no perfect match, it applies the "parent" policy (from upper domain or asset type).

Policy of current version applies to all asset versions

No (2)

Yes

Yes (7)

Warning on non-matching policies

No

No

Yes (in reports)

Report

No

Yes (censhare Client)

Yes (censhare Client & censhare Web) (3)

Deletion process

Number of queries to load assets (performance) (4)

High

High (queries with long execution time)

Low

Defined execution time of the deletion process

Yes. Runs until defined amount of assets is reached (configurable).

No. All assets are processed (not configurable). This does not scale.

Yes (configurable).

Resume deletion process

No. It starts from the beginning again.

No. It starts from the beginning again.

Yes. It starts from last asset ID on the next run.

Batch processing

Defined amount of assets (e.g. 10.000 assets)

Loads all available assets (not configurable). This does not scale.

Sequence of batches with 10.000 assets (not configurable)

Guarantees that all assets are processed

No

Yes

Yes

Server actions

Individual asset deletion

No

No

Yes (censhare Client)

One server action for the whole deletion process

No

Yes

Yes

Configure execution order necessary

Yes

No

No

Run each stage of the deletion process separately

Yes

No

Yes

Handling of exceptions in the database

Discard non-committed changes

No (5)

Yes

Yes

System

Database

Oracle

Oracle / PostgreSQL

Oracle / PostgreSQL

Scalable

Yes

No

Yes

(1) Applies also for Delete all version mode.

(2) Asset Deletion 1 decides for each asset version separately which asset version policy to use. If the domain changes, the policy also changes.

(3) Shows only asset versions with at least one constraint.

(4) There is a significant impact on the performance of the censhare system by the number of queries that are needed in the database to receive asset information.

(5) To limit the execution time, Asset Deletion 1 allows to set a limit of assets that are processed for the different server actions.

(6)  If there is an exception, censhare rolls back and stops the process. This means that all updates for the loaded assets are not done if they have not been committed until this point. The number of loaded assets is defined for the respective server action.

(7) In a general case, Asset Deletion 3 applies the same policy to all versions of the asset. If the asset has been moved between domains during its lifetime, and a special policy has been defined for the second (third, fourth, etc.) domain, for each asset version, the policy of the asset’s current domain will be applied. This information will also be shown by the AD3 report.


Checked constraints

Constraint

Description

Asset Deletion 1

Asset Deletion 2

Asset Deletion 3

Defined in the code

Last version

Excludes the current version (attribute currversion = "0").

-

X

X

Checked out

Asset is currently checked out (attribute currversion = "-2").

X

X

X

Variant

Ignores any asset with an associated variant.

X

X

X

Actual placement

Ignores versions with an actual placement relation.

X

X

X

Content version

Ignores versions holding a content version which is still used in later asset versions.

X

X

X

Feature reference

Ignores asset versions referenced by an asset feature.

X

X

 - (1)

Not matching policy

Ignores an asset if no asset version policy is defined.

X

-

-

Undeletable asset

Ignores asset versions with the state "not deletable" (attribute deletion = "2"), for example, module assets.

X

X

X

Snapshot

Ignores asset versions with a snapshot flag (online channel constraint).

X

X

X

Live tag

Ignores asset versions with a live tag (published on an online channel).

X

X

X

Expiration date

The asset version has expired (online channel).

-

X

-

Defined by policies (configurable)

Domain

Defined policy per domain 1, domain 2, and sub domains.

X

X

X

Asset type

Defined policy per asset type and sub-types.

X

X

X

Deletion mode

Delete all versions; Keep all versions; Delete selected versions

X

X

X

Deletion range

Keep the first x versions; keep the last x versions; keep the last x days; Keep for x hours before deletion

X

X

X

(1) Asset versions which contain asset references will be deleted as specified in the Asset version policies.  Referenced assets and all references are removed automatically and without further warning. The policies are applied as usual, i.e. the very first and very last asset versions are kept, unless manually marked for deletion.

Result

You know the main differences between Asset Deletion 1, 2 and 3. You understand the advantages of Asset Deletion 3 over Asset Deletion 1 and 2.  

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.