Collections are containers or virtual folders used for organizing, managing, and sharing content.
This article describes how to use Collections as a way of organizing content. For more information about Collections, see Working with Collections in Assets.
A Collection contains files in the same way that a folder contains files.
The difference is that a folder contains the actual file and that therefore a file can only be part of one folder.
In contrast, a Collection stores a reference to the file. This way, the same file can be made part of multiple Collections.
This makes Collections very suitable for gathering all files that are going to be used in the same project, story, publication, and so on.
Collections in Collections
A Collection can also be added to another Collection. This makes it possible to organize content more structurally, similar to a folder structure.
There is no limitation to the number of Collections that can be added to another Collection.
Using Collections in Collections is typically used in an environment in which the original files are archived as read-only files. Files are then added to a Collection structure similar to organizing folders, after which the files are copied over as editable files to the production environment.
Do you have corrections or additional information about this article? Leave a comment! Do you have a question about what is described in this article? Please contact Support.
Please sign in to leave a comment.