How to restrict duplicate files from getting ingested into eMAM system and How to enable it during Ingest profile configuration?

How to restrict duplicate files from getting ingested into the eMAM system?

The default behavior of eMAM while checking duplicate files is to compare the file name, size, and checksum of the file in a Category. If all three of these values are the same, the files are considered duplicates. By default, we can save the same file in multiple categories or a file with the same name in multiple categories.

For example, let's say there is a category called "Movies" and we have a file with the name "Nightingale.mp4" in that category. By default, we can ingest the same file into another category or can ingest a different file with the same name "Nightingale.mp4" to any other category, the ingest will not be restricted because the category is different/file properties are different.

We can enable a system-wide checking as eMAM provides an option to prevent the ingesting of files that already exist in the eMAM system. This can be useful for preventing duplicate files from being ingested, which can save space and improve performance.

The restrict duplication option in the Advanced Settings of the ingest profile in eMAM works at system level, allowing only one file with a file name to exist, irrespective of the category.

For example, there is a category called "Movies" and we have a file called "Nightingale.mp4" in that category. If you enable the restrict duplication option and try to ingest another file called "Nightingale.mp4" into another category, the ingest will be rejected because there exists file with the same name in the system.

To enable the restrict duplication option,

1. Open the ingest profile and go to the Advanced settings.



2. Select the profile settings option and enable option Restrict duplicate files in the system.


3. Click on Save.

    • Related Articles

    • Bug Fixes eMAM 5.4

      Bug Fixes in eMAM 5.4 BUG ID DESCRIPTION 5.3.1_18NOV2021 11889 Storage DNA API change to handle "404 not found" in the response. 11899 Schedule metadata is not getting updated for PATCH api/v1/assets/{AssetId}/AssetMetadata 11708 PFR is not working ...

    • eMAM 5.4 Release, April 2023

      EMAM, Inc. is excited to announce the release of eMAM version 5.4! This new release includes several key features and enhancements to help you manage your media assets more efficiently than ever before. In addition to the key features, eMAM version ...

    • eMAM 5.3 Release, Oct 2021

      EMAM, Inc. is delighted to roll out its latest eMAM version 5.3 enriched with some exciting new additions like eFeeder, packaged asset delivery using ATEME TITAN, stitch & deliver using Elemental MediaConvert, instant asset, improved editing tools ...

    • eMAM Cloud Platform - Production (eCP-Production)

      eCP-Production Deployment About this Guide This guide is intended for IT infrastructure architects, administrators, and IT professionals who are planning to deploy eMAM system (PAAS) on AWS Cloud. Overview eMAM Cloud Platform - Production ...

    • Release Notes eMAM version 5.4

      Release Notes eMAM version 5.4 EMAM, Inc. is delighted to announce the release of eMAM version 5.4. This latest update includes several new features and enhancements that will help our users to be more productive and efficient in their video ...