Extending DAM
...
document libraries
| Info |
|---|
We are using the usual “libraries” term, that you may also know as “collection holdings”. |
The out of the box configuration only contains one DAM fund library which structure name is asset. This default structure is configured with recommended properties.
Most of these properties reflect technical properties of an asset (eg: width, height, assetnature...).
If you dont don't think you need some property, it is highly recommended to hide from users rather than to remove it from the structure.
Few of these properties are purely functional and are common to all DAMs (such as keywords, folder…)
Creating new
...
libraries
During the project implementation, you might need to create additional fundslibraries. This need can come from different use cases:
Qualify Differentiate assets with different functional metadata. Exemple: for product assets, you will probably need to store a product ID / SKU / product category for each asset
Ease governance of assets. Exemple: a legacy fund library can be created to store old assets not used, but kept for legacy. Such assets are generally not available to all users, and it can be easier to store them in a different repository.
It is recommended to duplicate the asset structure for creating a new fund library rather than creating the fund library from a fresh new structure. Doing so, you are sure not to forget required configuration.
Check list after creating a new
...
library from a BO perspective
Give a functional name to the fundlibrary
Create a new entry in the
rubriqueobjectAssign the created rubrique to roles in charge of managing this fundlibrary
Adapt permissions groups if the fund library is related to governance.
Create additional BO dashboard widgets to ease management for users
Check list after creating a new
...
library from a Portal perspective
Should a dedicated context in the DAM explore page be created?
Adapt dam-import configuration to make sure authorised users only have access to import assets in this new fundlibrary.
Extending a
...
library
You are free to add specific metadata to any fundlibrary. If you have created additional funds libraries and you want to add a property to multiple of the fundslibraries, remember you can copy a property from one structure to another.
...
Extending workflows
With starter-kit, DAM funds libraries and metadata use 2 workflows. If you want to enrich the default provided workflows, we recommend creating a new workflow and building statuses and actions on those instead of changing the default provided ones.
...