Profiles for processing metadata, images, and videos profiles-for-processing-metadata-images-and-videos

A profile is a recipe for what options to apply to assets that get uploaded to a folder. For example, you can specify what metadata profile and video encoding profile to apply to video assets that you upload. Or, what imaging profile to apply to image assets to have them properly cropped.

Those rules can include adding metadata, smart cropping of images, or establishing video encoding profiles. In Adobe Experience Manager, you can create three types of profiles, which are covered in detail at the following links:

You need Administrator rights to create, edit, and delete metadata, image, or video profiles.

After you create your metadata, image, or video profile, you assign it to one or more folders that you use as the destination for newly uploaded assets.

An important concept regarding the use of profiles in Experience Manager Assets is that they are assigned to folders. Within a profile are settings in the form of metadata profiles, along with video profiles or image profiles. These settings process the contents of a folder along with any of its subfolders. Therefore, how you name files and folders, how you arrange subfolders, and how you handle the files within these folders has a significant impact on how those assets are processed by a profile.
By using consistent and appropriate file and folder naming strategies, and good metadata practice, you make the most of your digital asset collection, and ensure that the right files are processed by the right profile.

Assets that you move from one folder to another do not get reprocessed. For example, suppose you have Folder 1 that has profile A assigned to it and Folder 2 that has profile B assigned to it. If you move assets from Folder 1 to Folder 2, the moved assets retain their original processing from Folder 1.
The same is true even when you move assets between two folders that have the same profile assigned to it.

Reprocess assets in a folder reprocessing-assets

Applies to Dynamic Media - Scene7 mode only in Experience Manager or later.

You can reprocess assets in a folder that already has an existing processing profile that you later changed.

For example, suppose you created an Image profile and assigned it to a folder. Any image assets you uploaded to the folder automatically had the Image profile applied to the assets. However, later you decide to add a new smart crop ratio to the profile. Now, instead of having select and reupload the assets to the folder all over again, you simply run the Dynamic Media Reprocess workflow.

You can run the reprocess workflow on an asset for which processing failed the first time. As such, even if you have not edited a processing profile or applied a processing profile, you can still run the reprocess workflow on a folder of assets anytime.

You can optionally adjust the batch size of the reprocess workflow from a default of 50 assets up to 1000 assets. When you run the Scene7: Reprocess Assets workflow on a folder, assets are grouped in batches, then sent to the Dynamic Media server for processing. Following processing, the metadata of each asset in the entire batch set is updated on Experience Manager. If the batch size is large, you may experience a delay in processing. Or, if the batch size is too small, it can cause too many round trips to the Dynamic Media server.

See Adjust the batch size of the reprocess workflow.

If you are performing a bulk migration of assets from Dynamic Media Classic to Experience Manager, you must enable the Migration replication agent on the Dynamic Media server. When the migration is complete, make sure you disable the agent.
The Migration publish agent must be disabled on the Dynamic Media server so the Reprocess workflow works as expected.

To reprocess assets in a folder:

  1. In Experience Manager, from the Assets page, navigate to a folder of assets that has a processing profile assigned to it and for which you want to apply the Dynamic Media Reprocess workflow,

    Folders that have a processing profile already assigned to it are indicated by the display of the profile’s name directly below the folder name in Card View.

  2. Select a folder.

    • The workflow considers all files in the selected folder, recursively.
    • If there are one or more subfolders with assets in the main selected folder, the workflow reprocesses every asset in the folder hierarchy.
    • As a best practice, you should avoid running this workflow on a folder hierarchy that has more than 1000 assets.
  3. Near the upper-left corner of the page, from the drop-down list, select Timeline.

  4. Near the lower-left corner of the page, to the right of the Comment field, select the carat icon ( ^ ) .

    Reprocess assets workflow 1

  5. Select Start Workflow.

  6. From the Start Workflow drop-down list, choose Dynamic Media Reprocess.

  7. (Optional) In the Enter title of workflow text field, enter a name for the workflow. You can use the name to reference the workflow instance, if necessary.

    Reprocess assets 2

  8. Select Start, then select Confirm.

    To monitor the workflow or check its progress, from the Experience Manager main console page, select Tools > Workflow. On the Workflow Instances page, select a workflow. On the menu bar, select Open History. You can also terminate, suspend, or rename a selected workflow from the same Workflow Instances page.

Adjust the batch size of the reprocess workflow adjusting-load

(Optional) The default batch size in the reprocessing workflow is 50 assets per job. This optimal batch size is governed by the average asset size and the MIME types of assets on which the reprocess is run. A higher value means you have many files in a single reprocessing job. So, the processing banner stays on Experience Manager assets for a longer time. However, if the average file size is small – 1 MB or less – Adobe recommends that you increase the value to several 100, but never more than 1000. If the average file size is large, such as hundreds of megabytes, Adobe recommends that you lower the batch size up to 10.

To optionally adjust the batch size of the reprocess workflow:

  1. In Experience Manager, select Adobe Experience Manager to access the global navigation console, then select the Tools (hammer) icon > Workflow > Models.

  2. On the Workflow Models page, in Card View or List View, select Dynamic Media Reprocess.

    Workflow Models page with Dynamic Media Reprocess workflow selected in Card View

  3. On the tool bar, select Edit. A new browser tab opens the Dynamic Media Reprocess workflow model page.

  4. On the Dynamic Media Reprocess workflow page, near the upper-right corner, select Edit to “unlock” the workflow.

  5. In the workflow, select the Scene7 Batch Upload component to open the toolbar, then select Configure on the toolbar.

    Scene7 Batch Upload component

  6. On the Batch Upload to Scene7 – Step Properties dialog box, set the following:

    • In the Title and Description text fields, enter a new title and description for the job, if desired.
    • Select Handler Advance if your handler will advance to the next step.
    • In the Timeout field, enter the external process timeout (seconds).
    • In the Period field, enter a polling interval (seconds) to test for the completion of the external process.
    • In the Batch field, enter the maximum number of assets (50-1000) to process in a Dynamic Media server batch processing upload job.
    • Select Advance on timeout if you want to advance when the timeout is reached. Cancel selection if you want to proceed to the inbox when the timeout is reached.

    Properties dialog box

  7. In the upper-right corner of the Batch Upload to Scene7 – Step Properties dialog box, select Done.

  8. In the upper-right corner of the Dynamic Media Reprocess workflow model page, select Sync. When you see Synced, the workflow runtime model is successfully synchronized and ready to reprocess assets in a folder.

    Synchronize the workflow model

  9. Close the browser tab that shows the Dynamic Media Reprocess workflow model.