Summary
Metadata is data that describes other data. For example if you think of a book, the title, author, publisher, year published, and edition would all be metadata regarding the book. For assets the metadata is an effective system that makes the specific data of digital files simpler to work with. Metadata helps clarify information and makes it easier to find and manage digital files.
Metadata is a critical component for search inside major marketing tech systems like CRM, DAM, and CMS, allowing for easier integration between marketing tools.
Who?
This feature/solution is enable-able by any Bynder portal user.
Why?
You can extract embedded metadata from your assets and map it to your existing metaproperties. This way, you can automate the enrichment of your assets with existing metadata. You can use any EXIF, XMP, or IPTC tag. However, the only fully custom metadata tags Bynder supports are those based on the XMP metadata standard.
How?
Consider:
Users can decide how they want to configure downloaded metadata, first there are some things to consider:
- Do you want XMP metadata embedded with each download?
- Should this be optional or required for each downloaded asset?
- Do you want to remove the original metadata before downloading and ensure that only metadata configured in the DAM is embedded?
- If Bynder-specific metadata is included, could you decide which fields to map?
- If including the default Bynder fields (e.g., title, description, tags), do you want them added to the standard tag or require them in another tag? Please note that Bynder default fields are not automatically mapped upon download. You must manually specify which fields you’d like the Bynder default fields to be mapped to.
Creating Custom Metadata Fields
- Create a new Metaproperty, and select the single-select metaproperty type to map the metaproperty.
- Navigate to Settings > Advanced Settings > Portal settings.
- Click Embedded metadata configuration in the left sidebar and ensure you’re in the On asset upload tab.
- Default metadata fields: Click View default fields to review the default metadata continuously extracted and embedded in your assets once uploaded to Bynder, regardless of settings.
- Paste the exact name of the metadata tag in the Custom metadata fields box. Separate the values by commas in case you want to map multiple metadata tags.
- Click the Metaproperties dropdown to select the Bynder metaproperty to which the metadata should be mapped.
- Click the Add Custom field to add additional mappings.
- Click Save Changes.
Note: In order to ensure that the correct value is extracted when mapping tags from EXIF, XMP and IPTC ensure that you use the correct namespace as well. For Example: WhiteBalance can be found under two namespaces XMP-exif and XMP-crs. If the namespace is not provided in the mapping and there is a value option for both tags then Bynder cannot know which will be extracted.
Note: If you would like your changes to apply to existing assets in your portal, please contact Bynder support.
Downloading Assets With Metadata
- Navigate to the asset(s) you want to download.
- Check the box next to Include XMP metadata in the Asset Details view. This box can be checked by default if you want to make this required.
- Click one or more of the available files to start the download. Alternatively, you can click Download all files to download all the files at once.
Note: Bynder default fields are not automatically mapped upon download. You will need to manually specify which fields you’d like the Bynder default fields to be mapped to.
Exporting Metadata
You can export metaproperties and their values to specific metadata tags. We support exporting to XMP, IPTC, and EXIF.
If you don't want this metadata to be written to the default metadata tags, we can set it up so it is written to a specific tag.
For example, instead of writing the Bynder Title to the default XMP:Title tag, it can be written to XMP-photoshop:Headline.
- Navigate to Settings > Advanced Settings > Portal settings.
- Click Embedded metadata configuration in the left sidebar and then the On asset download tab.
- CSV download: Enable this setting to allow users with the appropriate permission to download a CSV of the metadata for selected assets.
- XMP download: Enable this setting to embed the XMP metadata in the downloaded assets. If enabled, you can select which XMP metadata should be embedded.
- Required download: Enable the XMP metadata always to be embedded in the downloaded assets.
-
Update the existing XMP metadata: Enable the mapping of the Bynder metadata to metadata fields upon download.
- Default Bynder metadata: If you don’t want the default metadata to be written to the default metadata tags, add the metadata tag that you want the metadata written to, separated by a comma.
-
Metaproperties: You can map Bynder metaproperties and their values to specific metadata tags. We support exporting to XMP, IPTC, and EXIF.
- In the Metaproperties column, click the dropdown to select a Bynder metaproperty.
- In the Metadata tags column, paste the exact name of the metadata tag to which you’d like to write the metaproperty.
- Click Add metaproperty to add a mapping.
- Click Save Changes.
Extracting XMP Metadata When Uploading Assets
Embedded metadata from cameras, photo editing tools, or other systems can be leveraged to automatically populate your metaproperties in Bynder. Supported metadata formats include EXIF, XMP, and IPTC tags. While any tag within these formats can be used, fully custom metadata tags must adhere to the XMP metadata standard to ensure compatibility.
Note: Supported file types are the ones supported via the Exiftool except:
- .zip
- Office Documents
- Audio files(aside from default fields, which can be extracted).
Note: Metadata extraction for both default and custom metadata is supported for our uploaders aside from uploads via the API and templates.
Default Metadata
Once uploaded to Bynder, the following default metadata is continuously extracted and embedded in your assets, regardless of settings. This cannot be edited or disabled.
| Bynder Field | Metadata Tags |
| Author | Artist(XMP), By-Line(IPTC), Author(XMP), Creator(XMP) |
| Copyright | Copyright (IFD0, EXIF, XMP), CopyrightNotice (IPTC) |
| Description | Description(XMP), ImageDescription(EXIF), Caption-Abstract(IPTC) |
| DPI | XResolution(EXIF) |
| Make | Make (EXIF, XMP) |
| Model | Model (EXIF, XMP) |
| Publication date | CreateDate(EXIF, XMP), DateTime(XMP) |
| Tags | Keywords (IPTC), Subject (DC) |
| Title | Title(XMP), Headline(IPTC), ObjectName(IPTC) |
Using The ExifTool
- Navigate to ExifTool.
- Select the appropriate package for your OS(Windows or MacOS).
- Open the Terminal.
- Type ExifTool and press space.
- Drag the file you would like to read into the Terminal and press Enter.
- Scroll through the metadata and look for the name of the metadata embedded in the asset.
- This information can be used to write the metaproperty in your Bynder DAM.
Example of Exif data analysis using the ExifTool.
If the information you want to map to Bynder is not always available in the same Exif field and is saved to multiple Exif fields with (slightly) different names. In that case, you can map all Exif fields to the same metaproperty in Bynder.
FAQs
When I make changes in Embedded Metadata Configuration, can I apply these changes to existing assets?
No, if you change the Embedded Metadata settings, your changes will only apply to newly uploaded assets. If you want your changes to apply to all pre-existing assets, please contact Customer Support.
When I make changes in Embedded Metadata Configuration, can I apply these changes to existing assets?
No, if you change the Embedded Metadata settings, your changes will only apply to uploaded assets after you make them. If you want your changes to apply to all pre-existing assets, please contact Customer Support.
Related Articles
How To Download A CSV File With All Metadata
How To Upload Assets Via Mass Uploader
Level: Proficient
Proficient-level articles are for users who have some prior Bynder knowledge. These articles require you to know the basics and may also require higher-level portal rights to accomplish the task outlined within the article.