Most files will not need any preparation; however, creative project files, such as InDesign or QuarkXPress files, may need preparation. That preparation is significantly easier to do at this point, rather than waiting. Creative project files should be collected for output, zipped, and have a high-res PDF file generated. The ZIP file will remain as the saved archive, while the PDF file can be easily used and re-purposed by your users.
Files can be uploaded using the drag-and-drop capabilities of the DAM or by browsing for them.
If you have a large number of files (with “large” usually meaning more than 100 GB), we suggest transferring those files to a portable hard drive. After files have been transferred to the hard drive, return the drive to us and we’ll bulk upload the files to your site. We’ll give you an estimated completion date, which will be the date by which all of the files will be added to your site, ready for you to tag with metadata and edit.
If we bulk upload files, we’ll edit those files to a certain level, making adjustments to categorization, bringing in embedded metadata, and mapping that data to searchable fields. After that, you’ll need to finish editing. If you provide us with a category and asset group structure, we’ll organize your assets within the site. When it’s time for you to continue editing the assets, you can batch edit metadata, categories, and asset groups/security for a large number of assets at one time.
We suggest you organize and tag metadata in an “inverse triangle” method. For example, if you have 1,000 assets, you can either tag each asset with all of its metadata or make small changes to a large group of assets.
If you edit each asset individually, it might take you a couple minutes to fully tag each asset. At a couple of minutes per asset, times the total number of assets, it could take quite a long time to complete the entire asset library with enough metadata that aids in making searching effective.
Using the inverse triangle method, batch editing large groups of assets from in the DAM allows you to identify surface-level differences and apply the changes in large sweeps, making assets searchable almost instantly. It makes the process of editing assets go much more smoothly than editing assets individually.
Using the inverse triangle method, you can start by classifying assets by type, for example. Suppose you determine you have:
Logos
Product images
Lifestyle images
Sales brochures
Product literature
Video tutorials
Video demonstrations
With batch editing, you can classify your entire asset library into this high-level structure very quickly. Instantly, your DAM site is usable down to that level of granularity. From there, you can continue to break assets into smaller groups. Because you are making changes across the entire asset library, rather than to individual assets, the library is searchable almost instantly.
When gathering files from many different locations, you may find that a file exists in multiple places or that there are multiple compressed or low-res versions that were created for specific uses. After bulk upload, files will go through what’s known as the de-duping process, which will identify duplicate files. We’ll then let you decide what to do with those files, which may include deleting low-res or duplicated versions.
As you upload large numbers of assets, there is the potential for multiple assets to have the same filename. In the DAM, these are called conflicted assets and are listed in the Conflicted Uploaded Assets table on the Uploads page.
You can resolve conflicted assets in the Conflicted Uploaded Assets table either individually or in a batch. Conflicted assets can be resolved by adding the file of a newly uploaded asset as a version to an existing asset, adding the file and metadata as a version to an existing asset, renaming the existing or conflicting asset, or deleting the existing or conflicting asset.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.