- The assets must already exist in eMAM.
- The module is launched directly from eMAM Director.
- The upload file must contain at least one column that can be used to uniquely match an asset.
High level Import Workflow
- Upload the file
- Select the asset matching field/column
- Map columns to asset fields or metadata fields
- Run the import
- Review the result summary
- Download the result workbook
Step-by-Step Instructions
- Open Metadata Import page: In the eMAM Director, open the Browse widget, click the Options menu in the Browse area and select Metadata Import.

Figure 1- Under Options menu select Metadata Import
- A new window or tab opens the Metadata Import Wizard.

Figure 2- Metadata Import Module page
Note:
- The launch URL contains a secure encrypted token generated by eMAM Director. Do not edit the URL manually.
- If you receive an Access Denied message, close the page and relaunch the module from eMAM Director. Opening the IIS URL directly without the Token parameter is not supported.
- Upload: Upload the Source File (excel/csv) with asset metadata details
- Drag and drop the file into the upload area or click Browse File and select the CSV or Excel file.

Figure 3- Upload the Source File (excel/csv) with asset metadata details
- Verify that the source file name, column count, and row count are displayed. Click on Next: Match & Map.

Figure 4- Verify source file details and click on Next: Match & Map
- Match & Map: In this page, you have option to match and map source sheet with eMAM metadata fields.
- Source file details: It displays the uploaded file, no. of columns & rows in that excel/csv file.

Figure 5- Match Map tab
- Asset Matching: Under Asset Matching section, choose the Excel column that should be used to find the corresponding asset in eMAM. Available target fields include Asset ID, Title, and File Name. The matching is exact. It is recommended to use Asset ID whenever possible.

Figure 6- Asset mapping Section
- Column Mapping: Under the Column Mapping section, map each excel column to the correct target field in eMAM. Available mapping targets include Ignore, Title, Description, and custom metadata fields from eMAM. Review the selected matching field and mappings & click on Start Import.

Figure 7- Column Mapping Section
Note: Asset ID and File Name are read-only matching fields. Use Column Mapping for Title, Description, and custom metadata updates. Only select the fields that need to be updated. Remaining can be marked as Ignore.
- Import: The import process begins, and the application processes the file in batches.

Figure 8- Import in progress
- Result: After the import process is completed, the result page shows the total rows attempted, success count, failed count, and the error details for the failed rows.

Figure 9- Import result page- All metadata Import completed successfully

Figure 10- Import result page- Import completed with errors
- Download Result File: For detailed report, click Download Result File and open the downloaded workbook.

Figure 11- Downloaded result file
Review the newly added columns such as ImportStatus and ImportReason.
- For Successful Imports: The ImportStatus will indicate success. To verify, open eMAM Director and confirm that the updated metadata values are correctly reflecting on the assets.
- For Failed Imports: The ImportStatus will indicate a failure. Check the ImportReason column to identify the specific error, rectify the underlying issue in your source file or mapping.
- Start Another Import: Correct the failed rows and re-upload by clicking on Start another import button (if necessary).

Figure 12- Start another Import
Best Practices
- Use Asset ID as the matching field wherever possible.
- Test a small file before using a large import file.
- Review the result file after every import.
- Correct and re-upload only the failed rows when needed.
Need Help