One method of uploading assets to your Bynder DAM is via our Professional Services team. At an additional cost, you can provide your files and upload them via SFTP. Follow the steps outlined below to prepare your assets and CSV file.
Note
Our media import is a paid service. Contact your Onboarding Manager or Customer Success Manager for more information.
-
Migrating From an Existing System to Bynder
You must create a media import sheet based on your Bynder portal taxonomy. See the Import guidelines and file example section for more information.
-
Incorrect and Inconsistent Spelling
Make sure that you review the spelling, capitalization, and spacing of words and phrases within the import sheet. The media import will fail if a value is similar to a value that already exists in your DAM. Even slight inconsistencies may cause your asset import to fail and delay the media import process.
-
Multiple Import Sheets
We suggest you break your import into batches of 25,000 assets for import efficiency reasons. For example. If you have 100,000 assets, we suggest creating four import sheets containing 25,000 assets each.
- If you are still in the onboarding phase, you can contact your Onboarding Manager.
- If you already completed your onboarding phase, please get in touch with your Customer Success Manager.
Please look here for an example of the import file Bynder import instructions.
Follow the guidelines for successful import:
-
Provide us with your files by uploading them via SFTP. We'll also need a CSV file that includes the information, metaproperty options, and other data you want to tag your files with.
-
There should not be any demo data included.
-
The first nine columns of the spreadsheet are static and must exist in the following order. They cannot be removed or rearranged.
-
Asset Name (Required)
-
Asset Description
-
Brand (Required)
-
Date Created
-
Copyright
-
Tags (comma-separated, no trailing spaces)
-
Path to Assets (Required)
-
Archived (1 or 0, Required)
-
New Filename
-
-
The headers for custom metaproperties must match the metaproperty name.
-
The options for custom metaproperties must match the metaproperty label.
-
The file paths must include the full filename and extensions (for example, /Volumes/Drive/file_name.ext).
-
Metaproperty and metaproperty option dependencies are not respected. Data validation can be used for single-select metaproperties if desired.
-
New metaproperties must exist in the account with the relevant types and options.
-
Metaproperty options for new metaproperties can be automatically created.
-
Each line/row in the import sheet represents an asset to be imported. Therefore, a 1:1 relation of assets to lines should exist. The best practice is not to upload an asset more than once, for example, multiple lines with different metadata referencing a single asset.
-
Each line/row must include values for the required columns specified above.
-
Any options that do not match existing option labels will be created. Watch out for improper variations that would otherwise have to be cleaned up after the import. (for example, New York/NY/NYC, or United States/US/U.S.)
-
Multiple metaproperty options (multi-select) and the descriptive keyword tags (column F) should be comma-separated in the same cell with no "trailing spaces" (for example, Option1, Option2, Option3 and not Option 1, Option 2, Option 3)
-
Multiple options should be distinct from one column.
-
Dates must be in the YYYY-MM-DD format.
-
Avoid special characters. This includes filenames, titles, descriptions, and all metaproperty options and values. The import script does not support these characters and may cause errors with the import.
Common non-alphanumeric characters that can produce errors:
-
/ - Slashes in metaproperty option labels: slashes are used to define sub-options for pre-smart-filter taxonomies (for example, sub-categories nested inside of categories), so it may be best to leave slashes out of metaproperty labels until after the import.
-
"and" - Double quotes, single quotes, and apostrophes are often formatted in Microsoft Office as "smart quotes" or "curly quotes". It's best to find and replace all these with standard text "straight quotes."
-
® ™ © $ £ - Symbols are not supported and should be replaced.
-
é ñ î - Accented letters such as letters with grave, acute, circumflex, tilde, and umlaut should be replaced.
-
White space characters such as tabs, new lines, and embedded returns should be replaced.
-
Spaces in filenames are always advised against.
Comments
0 comments
Please sign in to leave a comment.