What is filename mapping?

The filename mapping native integration provides an automated workflow that extracts metadata from filenames and populates the corresponding fields in Acquia DAM (Widen) to create a more efficient, accurate metadata tagging process. This integration detects new file uploads, parses filenames using specified delimiters, and maps the components to designated metadata fields.

How it works

When a new file is uploaded to DAM, the integration:

• Detects the new file upload.
• Parses the filename using predefined delimiters.
• Maps each filename component to specified metadata fields.
• Populates the metadata in assets automatically.

Key features

• Automated metadata extraction from filenames
• Real-time detection of new uploads
• Customizable filename parsing with delimiters
• Support for lookup table value mapping
• Filter options by upload profile, metadata type, asset group, global collection, or assets search query

Limitations

• Maximum of 20 metadata field mappings permitted
• Triggers only on new file uploads, not on renamed files
• Requires exact matches for controlled metadata values
• Integration does not modify metadata types, asset groups, or global collections
• No user interface components, operation is background only

Setting up the integration

Required documentation

• Filename mapping worksheet:
  • Define mappings between filename components and metadata fields.
  • Create separate tabs for different filename conventions.
  • Include an identifier for each convention type.
• Lookup table worksheet:
  • Specify filename component codes or keys.
  • Define corresponding DAM values.
  • Use exact matching criteria.
• Filter configuration:
  • Determine trigger criteria.
  • Specify applicable asset groups or profiles.

Important considerations

• Controlled vocabulary fields require exact matches.
• Lookup table values must be precise for the integration to function.
• Avoid using multiple automations on a single field.
• Field permissions affect integration functionality.

Best practices

• Use position-based mapping in lookup tables.
• Follow consistent filename conventions.
• Validate mapped values regularly.
• Monitor integration performance.

Support and maintenance

• The Support team monitors integration performance.
• The system provides error notifications.
• Submit changes or requests through support cases.
• Review configuration regularly.

For notifications about new uploads, use the DAM Paths feature separately from this integration.

Filename to metadata field mapping integration