Metadata Maps

NetX manages two different types of Asset Metadata:

  • Attributes - name/value pairs of data that are stored in NetX and searchable from the integrated search engine.
  • Embedded Metadata - values of various types and formats, stored inside the asset file itself. There are a wide variety of embedded metadata formats including IPTC, EXIF (digital camera information), Camera Raw, Dublin Core, and various Adobe extensions among others. However, Adobe's XMP has become the industry standard, becoming a common container for all the other embedded metadata types.

This feature provides the ability to embed NetX attribute values into an asset file when a download or share action is executed.


The following properties are required in order to enable the embedded metadata feature:

Property Description

If the value of this property is true, you can set up embedded metadata maps and embed system and custom attributes into downloaded assets. If the value of this property is false, there will be no Metadata map tab in the Systems area to manage embedded metadata maps. 

Value options: true / false

Requires restart? No


The value of this property must correspond to a user level's numerical equivalent, e.g. a value of would be producer-level users. This is the minimum user level that will have access to the Embed metadata option while downloading assets.

Value options: Numerical user level

Requires restart? No


Creating metadata maps

Administrators can configure metadata maps that other users can apply to their downloaded assets via the Metadata maps tab in the Systems area.

  1. Navigate to the Metadata maps tab of the Systems area.
  2. Click on the upper-left plus icon to create a new map. If this is your first metadata map, you can also use the Create one now button. 
  3. Use the metadata map configuration window to create your map.

Configuring a metadata map

  1. Name: Give your map a name
  2. Add mapping: To add a new map, click the Add mapping button. Each new map allows you to assign an attribute to a specific metadata field. 
  3. Schema: Determines the metadata schema used to map your attribute. Metadata schemas are not all created equal or with standardized fields between them; your organization should have a standard schema used in order to ensure reliable results when used with embedded metadata.
  4. Schema field: Each metadata schema will have codified fields that in turn map to certain fields in any application you are using to view the asset's metadata. These fields are also not necessarily standardized across applications and should be tested before using a particular schema/schema field combination to ensure reliable results.
  5. Add attribute: Use the dropdown or begin typing an attribute name; these may be both system and custom attributes.
  6. Attribute: This displays any attributes associated with the map and can be altered using their dropdowns. Attributes may be reordered using the drag handle. To remove an attribute, use the X icon. 
  7. Selected: Counts the number of attributes included in the map, use the X icon to remove all attributes at once.
  8. Delete map: The X icon at the foot of the map will remove that map from the metadata mapping. The last map cannot be removed.
  9. Save: Once your map is configured, click Save to codify it as an available metadata map. 

Default maps

You can designate one map as the default map that will be embedded into downloaded assets using the toggle while viewing the Metadata maps tab in the Systems area. Note that the first map you create will automatically be made the default map.

Was this article helpful?
0 out of 0 found this helpful