The original filepath metadata field is created when assets are ingested into Acquia DAM through the Acquia Asset Migration Service. It captures the folder structure from a hard drive or S3 transfer. Note that if you upload assets with the uploader, FTP, or API, this original filepath field will not be created. 

Here’s what a folder structure looks like on a hard drive.

Before asset migrations

Do not remove the original filepath from your metadata types. If you do, the field will not be filled in during asset migrations. 
 

Using the original filepath 

As a reference for metadata

The original filepath field can help you fill in metadata fields after asset migrations. For example, if the original filepath folder structure includes the year 2023, then you could refer to that information to edit a DAM metadata field for year. 
 

For batch editing

The original filepath field does not automatically map to metadata fields in the DAM. Using the text to columns feature in Microsoft Excel and DAM metadata import, you can map original filepath information, like folder names, to specific metadata fields and their values. 

For example, say your original filepath looks like this. 

What is the original filepath field?

The original filepath metadata field is created when assets are ingested into Acquia DAM through the Acquia Asset Migration Service. It captures the folder structure from a hard drive or S3 transfer. Note that if you upload assets with the uploader, FTP, or API, this original filepath field will not be created. 

Here’s what a folder structure looks like on a hard drive.

This is how the filepath will display in the DAM.

For new customers, this field is only available to DAM admins and Acquia teams. Admins can give other roles permission to view this field.
 

Before asset migrations

Do not remove the original filepath from your metadata types. If you do, the field will not be filled in during asset migrations. 
 

Using the original filepath 

As a reference for metadata

The original filepath field can help you fill in metadata fields after asset migrations. For example, if the original filepath folder structure includes the year 2023, then you could refer to that information to edit a DAM metadata field for year. 
 

For batch editing

The original filepath field does not automatically map to metadata fields in the DAM. Using the text to columns feature in Microsoft Excel and DAM metadata import, you can map original filepath information, like folder names, to specific metadata fields and their values. 

For example, say your original filepath looks like this. 

Then, this is what the metadata mapping would look like. 
 

Metadata field	Value
Asset type	Marketing Sales Tools
Tool type	Corporate Content
Content type	Branding Guidelines & Logos
Logo type	Company Trademark