Short answer
Collections are user-defined groups of assets that can be shared without moving or copying the files. Collections replace folders for temporary groupings such as a trade show, a campaign or an agency brief. One asset can sit in many collections at once, so a single update to the master reaches every collection that holds it.
How collections work in a DAM
Collections group references to assets, and the files themselves stay in one place in the library. Removing an asset from a collection leaves the asset untouched.
| Aspect | Folder | Collection |
|---|---|---|
| File location | The file lives in one folder | The file stays in the library and the collection points to it |
| Membership | One folder per file | Many collections per asset |
| Lifetime | Permanent structure | Often temporary, per project or event |
| Sharing | Folder permissions | Share link or invited users, often with expiry |
DAMs offer two kinds. Manual collections hold assets that a user picks one by one. Saved-search or smart collections update themselves from a faceted search query, such as all approved images for one product line.
Asset rights still apply inside a collection. A shared collection must hide or block any asset whose licence expires or whose embargo has not lifted.
Example of collections
Worked example: an events manager builds a collection of 60 approved images for a trade show. She shares it with the stand builder through a link that expires one week after the show and allows web-size downloads only.
Two weeks before the show, the studio replaces one image with a retouched version. The collection shows the new version automatically, because it points to the master.
Collections in a DAM selection
Collections belong at checkpoint 5, Test, where daily users try them in a scripted scenario. The demo script guide shows how to write the scenario.
Test these four behaviours in the demo:
- Build a collection from a faceted search result in a few clicks.
- Share it externally with an expiry date and a download size limit.
- Expire the licence on one asset and show it disappear from the shared collection.
- Create a saved-search collection and show it update when a new asset is approved.
Test rights enforcement inside shared collections. The demo script generator includes this scenario, and the functional requirements guide lists the collection requirements.
Common mistakes with collections
Collections cause problems through four common mistakes.
- Using collections as a permanent taxonomy, which recreates folder sprawl.
- Sharing links without expiry, so outdated assets stay accessible for years.
- Assuming a collection's permissions override asset rights and embargoes.
- Letting collections pile up without an owner or a clean-up rule.
Related terms: Brand portal, Faceted search.
Frequently asked
What is the difference between a folder and a collection in a DAM?
A folder holds the file itself, so each file sits in one folder. A collection points to assets in the library, so one asset can appear in many collections. Updating the master updates every collection that references it.
Can external users see collections in a DAM?
External users can see a collection when the owner shares it through a link or an invitation. Good practice sets an expiry date, limits downloads to suitable renditions and keeps asset rights and embargoes active inside the shared view.