A collection is a set of assets within Adobe Experience Manager Assets. Use collections to share assets between users. The set can be static collection or a dynamic collection that is based on search results.
Unlike folders, a collection can include assets from different locations. You can share collections with various users that are assigned different levels of privileges, including viewing, editing, and so on.
You can share multiple collections with a user. Each collection contains references to assets. The referential integrity of assets is maintained across collections.
Collections are of the following types, based on the way they collate assets:
A collection that contains a static reference list of assets, folders, and other collections.
A smart collection that dynamically includes assets based on a search criteria.
To open the Collections console:
To open the Collections, tap or click the Experience Manager logo. From the navigation page, go to Assets > Collections.
You can create a collection with static references, for example a collection with references to assets, folders, collections, spin sets, and image sets.
Navigate to the Collections console.
From the toolbar, tap/click Create.
In the Create Collection page, enter a title and an optional description for the collection.
Add members to the collection and assign appropriate permissions. Alternatively, select Public Collection to allow all users to access the collection.
To enable the members to share collections with other users, provide the
dam-users group read permissions at the path
home/users. Give permission to the users at
/content/dam/collections location to allow the users to view the Collections in pop up lists. Alternatively, make the user a part of
(Optional) Add a thumbnail image for the collection.
Tap/click Create, and then tap/click OK to close the dialog. A collection with the specified title and properties is opened in the Collections console.
Experience Manager Assets lets you create review tasks for a collection similar to the way you create review tasks for an assets folder.
To add assets to the collection, navigate to the Assets user interface. For details, see Add assets to a collection.
You can drag assets from the Assets UI to a collection. You can also create a copy of a collection and drag the assets there.
A Smart Collection uses a search criteria to dynamically populate assets. You can create a Smart Collection using only files and not folders or files and folders.
Navigate to the Assets UI, and tap/click the Search icon.
Enter search keyword in the Omni Search box and select
Enter. Tap/click the GlobalNav icon to display the Filters panel and apply a search filter from the Search panel.
From the Files & Folders list, select Files.
Tap/click Save Smart Collection.
Specify a name for the collection. Select Public to add the DAM Users group with the Viewer role to the smart collection.
If you select Public, the smart collection becomes available to everyone with the Owner role after you create it. If you cancel the Public option, the DAM user group is no longer associated with the smart collection.
Tap/click Save to create the smart collection, and then close the message box to complete the process. The new smart collection is also added to the Saved Searches list.
The label of the Create Smart Selection button changes to Edit Smart Selection. To edit the settings of the smart collection, select Files from the Files & Folders list. Then, tap/click the Edit Smart Selection button.
You can add assets to a collection that contains a list of referenced assets or folders.
Smart collections use a search query to populate assets. Therefore, static references to assets and folders are not applicable to them.
Smart collections are built by saving a search so you can alter their content by modifying the search parameters of the saved search.
Collection metadata comprises data about the collection, including any tags that are added.
You can edit the metadata of multiple collections simultaneously. This functionality helps you quickly replicate common metadata in multiple collections.
In the Collections console, select two or more collections for which you want to edit metadata.
From the toolbar, tap/click the Properties icon.
In the Collection Metadata page, edit the metadata under the Basic and Advanced tabs, as necessary.
Tap/click Save & Close from the toolbar, and then close the confirmation dialog to complete the process.
To append the new metadata with the existing metadata, select Apend mode. If you do not select this option, the new metadata replaces the existing metadata in the fields. Tap/click Submit.
The Append mode works only for fields that can contain multiple values. For fields that can contain only a single value, the new metadata is not appended to the existing value in the field even if you select Append mode.
You can search collections from the Collections console. When you search with keywords in the Omnisearch box, Experience Manager Assets searches for collection names, metadata, and the tags added to the collections.
If you search for collections from the top level, only individual collections are returned in search results. Assets or folders within the collections are excluded. In all other cases (for example, within an individual collection or in a folder hierarchy), all relevant assets, folders, and collections are returned.
In the Collections console, tap/click a collection to open it.
Within a collection, Experience Manager search is restricted to assets (and their tags and metadata) within the collection that you are viewing. When you search within a folder, all matching assets and child folders within the current folder are returned. When you search within a collection, only matching assets, folders, and other collections that are direct members of the collection are returned.
You can edit collection settings, such as title and description, or to add members to a collection.
From the Collections console, select one or more collections and tap/click the delete icon in the toolbar.
In the dialog, tap/click Delete to confirm the delete action.
You can also delete Smart collections by delete saved searches.
When you download a collection, the entire hierarchy of assets within the collection is downloaded, including folders and child collections.
From the Collections console, select one or more collections to download.
From the toolbar, tap/click the download icon.
In the Download dialog, tap/click Download. If you want to download the renditions of the assets within the collection, select Renditions.
When you select a collection to download, the complete folder hierarchy under the collection is downloaded. To include each collection you download (including assets in child collections nested under the parent collection) in an individual folder, select Create separate folder for each asset.
Adobe Enterprise Manager Assets lets you edit the metadata of many collections in bulk. Use the Properties page to perform metadata changes on multiple collections, for example, change metadata properties to a common value or add or modify tags.
To customize the metadata Properties page, including adding, modifying, deleting metadata properties, use the Schema editor.
The bulk editing methods work for assets available in a collection. For the assets that are available across folders or match a common criteria, it is possible to bulk update the metadata after searching.
From the collections console, select the collections you want to edit.
From the toolbar, tap/click Properties to open the Properties page for the selected collections.
Modify the metadata properties for selected collections under the various tabs.
The metadata you add for the selected collections overwrites the previous metadata for these collections, except for tags. Any tags you add in the Tags field, are appended to the existing list of tags in the metadata.
To view the metadata properties for a specific collection, cancel the selection of the remaining collections in the collections list. The metadata editor fields are populated with the metadata for the particular collection.
Save the changes.
You can add a collection to another collection, thereby creating a nested collection.
From the Collections console, select the desired collection or group of collections, and tap or click To Collection in the toolbar.
From the Add To Collection page, select the collection in which to add the collection.
The most recently updated collection is selected by default in the Add To Collection page.
Tap/click Add. A message confirms that the collection is added to the target collection in the Select Destination page. Close the message to complete the process.
Smart collections cannot be nested. In other words, Smart collections cannot contain any other collection.
In the Assets user interface, you can search or filter assets based on certain rules, search criteria, or custom search facets. If you save these as Saved Searches, you can access them later from the Saved Searches list in the Filter panel. Creating a saved search also creates a smart collection.
Saved searches are created when you create a smart collection. Smart collections are automatically added to the Saved Searches list. The Saved Searches query for the collection is saved in the
dam:query property in CRXDE at the relative location
/content/dam/collections/. There are no limits to the searches that you can save and on the saved searches displayed in the list.
You can share smart collections in the same way as you share static collections.
Editing saved searches is the same as editing smart collections. For details, see Edit a smart collection.
To delete saved searches, follow these steps:
In the Assets user interface, tap/click the search icon from the toolbar.
With the cursor in the Omnisearch field, select the
Click or tap the GlobalNav icon to display the Filters panel.
From the Saved Searches list, tap/click Delete next to the smart collection you want to delete.
In the dialog, tap/click Delete to delete the saved search.
You can run a workflow for the assets within a collection. If the collection contains nested collections, the workflow also runs on the assets within the nested collections. However, if the collection and the nested collection contain duplicate assets, the workflow only runs once for such assets.