How to remove content

Business Case:

KPI to be measured

Bookmark this resource Follow

Ask a question

Was this article helpful? 1 out of 1 found this helpful

[tab:Actions]

THRON DAM PLATFORM puts at your disposal two different trashes: a User Trash (specific and personal for every single user) and a Platform Trash, accessible by Administrators only. They enable Users and Admins to retrieve deleted contents in case of accidental removals.

  • User Trash: from here every user can manage its own deleted contents and has the chance to definitely delete or retrieve them
  • Platform Trash: from here, Platform Administrators can manage all the contents that have been deleted in THRON, by any user. They can search for specific contents, definitely delete or reactivate them. Moreover, it is possible to define a period of time at the end of which the contents present in the Platform Trash will be automatically removed. This is particularly useful for content calculation for billing, as the contents present in the trash are included in the count as long as they are not definitely removed.

Schermata_2021-10-21_alle_16.16.45.png

 

 

Requirements

 

In order to delete content from THRON platform the following conditions must be complied:

  • A business user must be used, and it needs the appropriate access rights (r+w) on the content to be deleted; therefore its credentials must be used (username and password must be used to perform login and obtain a valid token); a THRON application may be used to delete content, but only through SU web service which allows it to impersonate a business user (usually the owner of the application).

 

Moving to trash or unpublishing

 

Content removal in THRON may occur in two different ways: content can be moved to trash through the service trash or they can be unpublished from platform through the service remove. Both methods can be found in content package of xadmin. Here you find the main difference between the two methods:

  • The first method (trash service) allows you to move a content into a "trash" area by removing all its links with public folders inside of which it had been published, all ACLs related to shares and all embed codes generated for that content. With this service the content maintains the references with its prettyID and its external ID: as a matter of fact, after this operation the content will still be present in the CDN and can be retrieved at any time (until trash is emptied) through the service untrash.
  • The second method (remove service) removes the content from the platform permanently, eliminating all its metadata from xcontent

Note: Remember that the persistence of the content within the trash has a limited duration which is defined by THRON administrator in “Settings”.

 

Restoring content from trash

 

In order to restore content from trash you will have to use the service untrash which is located into “content” package of xadmin. Whenever a content is restored it will be published into the private folder of the previous owner. If you wish to restore a content assigning it to a new owner you will have to fill the parameter newUserId with the username of the new owner.

[/tab]

 

[tab:Code Samples]

You can test the functionality of moving content to trash in the Developer Center here.

In the body of the request you can paste the following JSON, replacing the required values​​:


{
    "contentList": {
        "contentsToTrash": [{
            "xcontentId": "",
            "removeOptions": {
                "removeRatings": false,
                "removeLinkedContents": false,
                "removeComments": false,
                "removeCuePoints": false,
                "removeCustomMetadata": false
            }
        }]
    }
}    

You can test the functionality of removing content from platform in the Developer Center here.

In the body of the request you can paste the following JSON, replacing the required values​​:


{
    "xcontentId": ""
}    

 

You can test the functionality of retrieving content from trash in the Developer Center here.

In the body of the request you can paste the following JSON, replacing the required values​​:


{
    "contentList": {
        "newUserId": "",
        "xcontentIds": [
            ""
        ]
    }
}    

 

[/tab]

Was this article helpful?
1 out of 1 found this helpful

Have any question?

Open a ticket
Comments