This guide will show you how to configure Asset Update/Reject based on checksum readings to prevent duplicate content from coming in from multiple sources.

This article will demonstrate how to make the changes on a Watch folder ingest, however, similar changes are applied for a Curator Connect ingest and will also be covered in this guide.

First, It is advised that your ingest workflows are updated to their latest versions and should exceed or be of the same release version as Curator 3.2.

You will also need to ensure you have:

• Spawn - Get Additional Metadata On Source File 
• PEA - Get Checksum on Source File

You will be notified of any missing workflows installed within your Process Designer when testing.

Once the workflows are configured, Create a Custom Mediastore named ADDITIONAL-METADATA with the following: 

<ADDITIONAL-METADATA>
      <MediaStoreDescription></MediaStoreDescription>
      <MediaStoreTemplate>Custom</MediaStoreTemplate>
      <MetadataStores>CHECKSUM</MetadataStores>
      <Workflow>Spawn - Get Additional Metadata on Source File</Workflow>
</ADDITIONAL-METADATA>

 Next, on the relevant Ingest Mediastore you will need to include the below key:

<UniqueMatchMetadata>MD5Checksum</UniqueMatchMetadata>

In this example, the FILEINGEST-HI-RES-VIDEO Mediastore was modified.

UpdateMatchMetadata will look for existing assets with the same checksum. If there is an asset with the same checksum it will update that asset, or, if multiple matching assets are found, it will fail.

UniqueMatchMetadata will look for existing assets with the same checksum. If there are existing assets with the same checksum, it will either fail or create a failed placeholder for the file that is being ingested

Once you have added the above, add the additional metadata store key to your ingest Mediastore. 

This should be directed to the newly created Mediastore ADDITIONAL-METADATA:

 Finally, on your CHECKSUM Mediastore, add the key PEAExtractMetadataProcess = PEA - Get Checksum on Source File

To configure this process for Curator Connect ingest, checksum should be available on ingest (based on the settings) so you don't need the additional metadata. The rest of the configuration should be the same.

Once configured, you are ready to test. A good way to test this is by ingesting the same file twice, naming it differently on the second attempt and monitoring its behavior.