All digital assets, metadata and content of Microsoft Office and PDF documents are extracted and made searchable. Search allows sophisticated filtering on assets and fully respects the proper permissions. Metadata is covered in detail in metadata in Digital Asset Management.
Experience Manager Assets supports multiple ways of organizing content. You can organize them in a hierarchical manner using folders or you can organize them in an unordered, ad-hoc manner, using for example tags. Users can edit tags in the DAM Asset Editor where sub-assets, renditions, and metadata are displayed.
The most basic way to organize assets is to save these in folders. It is analogous to organizing files in folders in our local filesystem. For more information about how to create and manage folders, see Manage assets. How you name files and folders, how you arrange sub-folders, and how you handle the files within these folders can have a significant impact on how those assets are processed. By using consistent and appropriate file and folder naming strategies, along with good metadata practice, you can make the most of your digital assets repository.
In most cases, your digital assets repository is always growing. Therefore, it is important to formalize metadata use, folder structure, and file naming early in the content creation cycle.
Use folders only to impose a consistent storage structure for your digital assets. This consistency helps your process and manage your assets better. For example, assets placed in the following types of folders can help you use appropriate profiles to use for asset processing:
Create a directory of folders that are not likely to change so that any customization or automation continues to work. For example, the assigned processing profiles continue to work.
If an asset is already published, then you use Experience Manager to move the asset to another folder, and re-publish from its new location, the original published asset location is still available, along with the newly re-published asset. The original published asset, however, is lost to Experience Manager and cannot be unpublished. Therefore, as a best practice, first unpublish an asset and then move it to a different folder.
Using tags, as a metadata, you can easily search assets, create collections using the search results, boost search ranking for some assets, and leverage Adobe Sensei’s AI algorithms for asset discovery.
Adobe Experience Manager Assets uses a self-learning algorithm to create highly descriptive tags that allow you to find the right asset in just a few clicks. Smart tagging uses Adobe Sensei, our artificial intelligence and machine learning framework, which can be trained to recognize and apply both standard and business-specific tags to imagery. Smart Tags can also identify content, individual words, or phrases and automatically apply descriptive tags to assets
For more information, see the following articles:
With asset collections in Experience Manager Assets, you can streamline the ability to create, edit and share assets between users. Create several types of collections based on the way you use them, including collections that contain a static reference list of assets, folders and collections, as well as collections that pull in assets based on search criteria. You also can create collections with assets from different locations and share them with multiple users with different levels of access, viewing and editing privileges.
For more information, see manage collections
A processing profile contains Assets processing commands that apply to assets that get uploaded to pre-defined folders. Profiles are used to automate the processing of contents of a folder or freshly uploaded assets. You can leverage profiles to organize your assets better.
Standardizing metadata usage, file naming, and folder structure ensures that as your pool of digital assets grows, you can apply processing profiles to folders with greater precision and consistency.
For more information on various profiles that you can create and manage to process assets, see,