Crops, Trims, and Renditions fall under an umbrella we call Additional Files. These are files that are included on a record, but aren’t used as the primary asset, or Master File. Additional files can be a lot of different things, included design docs, previous annotated creative feedback, related marketing materials, etc. This article will focus on Crops, Trims, and Renditions though
Crops are exclusive to image files in Aprimo. They can be generated automatically, manually in the UI, or through the REST API. All generated crops will be added to a DAM Record as Additional Files
Aprimo DAM contains create an automatic process that will create crops when certain conditions are met. For example, generate a series of crops when the master file has been updated with a new version. The different crops can be manually predefined in the system settings or let Aprimo AI determine the best crops to create.
Crops can be created in the UI as well.
Crops can be created using the Aprimo REST API’s Order endpoint. You can find documentation on how to use the CropImage action in the DAM training reference.
Trims are exclusive to videos. They are different segments of a video stored as Additional Files
Trims can be created on a video using the Aprimo UI.
Trims can be created using the Aprimo DAM REST API’s Order endpoint. You can learn how to use the TrimVideo action in the DAM Training Reference.
Renditions are additional files that have had some sort of transformation occur to the file. Such as changing the file format, resolution, or other actions. Renditions can be created automatically or through the REST API.
Similar to crops, admins can configure a system setting that predefines different renditions, and then use an automatic process to generate those renditions.
Renditions can be generated by using the Aprimo DAM Orders endpoint. You can learn about the different actions you can perform to create renditions in the DAM Training Reference.