MediaCentral Production
When a MediaCental Production bulk deletion command finished successfully (either loc:delete-item-in-folder-by-id-bulk-command or loc:delete-item-by-id-bulk-command) the command property payload does contain the property details. It contains a summary of the number of successful and failed items and assets deletions (sub-property metadata) and successful and failed media file deletions (sub-property media).
These are the categories for metadata (items/assets) deletion:
| Property | Description |
|---|---|
file-assets |
currently not supported: Number of successfully deleted items referencing a file asset |
folders |
currently not supported: Number of successfully deleted folders |
assets |
Number of successfully deleted items referencing an asset |
reserved |
Number of (not deleted) reserved items |
online-media-references |
Number of (not deleted) items being the last reference to an asset with still has online media |
referenced |
Number of (not deleted) items being used by another item/asset |
not-found |
Number of items not found |
already-scheduled |
Number of assets already scheduled for deletion |
last-reference |
mode reference only: Number of (not deleted) items being the last last reference to an asset |
not-in-folder |
loc:delete-item-in-folder-by-id-bulk-command only: Number of (not deleted) items not in the folder |
These are the categories for media deletion:
| Property | Description |
|---|---|
in-use |
Number of (not deleted) media files still used by an asset |
reserved |
Number of (not deleted) reserved media files |
access-denied |
Number of (not deleted) media files to which the access was denied (for example because insufficient Nexis permissions of the Engine Execution user) |
deleted |
Number of successfully deleted media files |
failed-to-delete |
Number of (not deleted) media files because of a not otherwise categorized error |
ATTENTION: The sum of the metadata deletion can be greater than the size of requested array of items to delete (or the returned item deletion result array) because the deletion of a item/asset related to other items/assets might have triggered their deletion as well. If for example a sequence (item) is deleted, all related (relations:relations) and referenced (referenced status) items of the sequence in the same folder are deleted as well.
Example: details propery of finished MediaCental Production bulk deletion command.
{
…
"payload": {
…
"details": {
"metadata": {
"file-assets": 0,
"folders": 0,
"assets": 3,
"reserved": 2,
"online-media-references": 2,
"referenced": 3,
"not-found": 1,
"already-scheduled": 0,
"last-reference": 0,
"not-in-folder": 0
},
"media": {
"in-use": 0,
"reserved": 5,
"access-denied": 0,
"deleted": 11,
"failed-to-delete": 0
}
}
}
}