Cloud organization owners, as well as all end users with “App-Administrator” role, can switch to configuration on their DAM resp. Publishing dashboard.
The functionality described below is available to administrators regarding Digital Asset Management solution.
Download formats for images, audios, videos and documents (general content) can be managed via the corresponding widget or tab. Download formats can be created, modified and – with the exception of original formats – deleted. Administrators can define which suitable formats are offered to the end users when downloading an asset or creating a public link to it, based on the type of the asset, the user’s role, and further parameters.
Via the Settings action, further configurations for assets and their metadata can be set. Optional and mandatory fields can be defined, the use of terms and tags can be preconfigured, settings for licensing and license types can be made, and the editability of image properties can be defined.
General settings that apply to projects and define the basic structure of projects and products are set within the Publishing configuration. The functionality described below is available to administrators. In some cases, configuration options and settings can also be made explicitly at the level of individual projects or products by end users who are granted with “Full Control” or “Change Access” there.
Products are assigned to a project and are managed within it. Access rights can be defined both at the project level and at the product level. The users who are authorized on the project level automatically receive the same rights on the underlying products.
When adding and managing project types, defaults can be predefined for newly created projects. This allows administrators to preconfigure projects. When a project of a certain project type is created by an end user, it automatically contains the standard products. Also a list of optional, additional products available for the end users can be predefined.
When adding and managing product types, defaults can be defined for newly created products. This allows administrators to preconfigure products. When a product of a certain product type is created by an end user, it automatically contains the standard components. Also, a list of optional, additional components for the end users can be predefined.
Administrators use the product types to define in which deployment format the product can be published.
A product contains of one or more components. These in turn contain layout templates. Components thus further structure products into individual subsections. They allow the definition of the minimum and maximum number of pages or content they can hold. Components can thus subdivide and structure classic print, as well as digital products. Components can either be of the type layout plan or structure plan.
Layout templates define the representation of the content of products. For example, Adobe InDesign (.indd) format templates can be created.
To allow the administrator to incrementally develop and test a new layout template, they are subject to a release process. Users can only see layout templates in the released status, whereas administrators can additionally see the draft of a layout template. They can both grant and revoke the release.
For a publication of a product, various output formats are supported. They are determined by deployment formats. With e.g. Adobe InDesign as deployment format output to PDF, HTML, and EPUB can be created.
To allow the administrator to incrementally develop and test a new deployment format, they are subject to an approval process. Users can only work with deployment formats in the released state, whereas administrators can additionally view and edit the draft of a deployment format. They can both grant and revoke the release.
The state functionality allows the labeling of processing statuses in the layout plan. This requires linking them with tasks via a BPMN process. A status can thus not be set manually, but indirectly by the completion of these tasks. By default, "In Progress" and "Approved" are provided.
Rubrics allow to label sequences of pages that belong together logically or content-wise.
Tagging is used to index objects like projects, products and assets. Tags are predefined by the administrators in the list of tags within the configuration. Tags can be nested within each other. Furthermore, it is possible to define for tags for which object classes they may be used for.