Scope of Services – Administration
Owners of a Fabasphere organization, as well as all users with the "App Administrator" role, can access the configuration settings in their DAM, Media Edition, or Publishing dashboard.
Digital Asset Management Configuration
The functionality described below is available to administrators regarding Digital Asset Management solution.
Use Case | Description |
|---|---|
Download formats | 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. |
Status | |
Tags/Tagging | |
Settings | 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. |
Publishing Configuration
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.
Use Case | Description |
|---|---|
Projects | 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. |
Project types | 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. |
Product types | 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. |
Components | 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 | 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. |
Deployment formats | 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. |
State | 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 | Rubrics allow to label sequences of pages that belong together logically or content-wise. |
Tags/Tagging | 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. |
Media-Edition Configuration
In the Media Edition configuration, general settings are defined that apply to workrooms and magazines and define issues. The functionality described below is available to administrators in the Media Edition section. In some cases, configuration options and settings can also be explicitly set at the level of individual workspaces or journals by users who have “Full Access” or “Change Access” permissions there.
Use Case | Description |
|---|---|
Workrooms | Magazines are assigned to a workroom and managed within it. Access rights can be defined at both the workroom level and the magazine level. Users granted permissions at the workroom level automatically receive the same permissions for the magazine within that workroom. |
Issue Types | When adding and managing issue types, default settings can be defined for newly created issues. This allows the administrator to preconfigure issues. When an end user creates an issue, various standard components are included by default. The list of optional, additional components can be specified for users. Administrators use issue types to define the delivery formats in which the issue can later be published. |
Components | An issue consists of one or more components. These components, in turn, contain layout templates. Components thus further structure issues into individual subsections. They allow you to define the minimum and maximum number of pages or pieces of content they can contain. Components can be used to subdivide traditional print products, but also to structure digital outputs. |
Layout Templates | Layout templates determine how product content is displayed. Templates can be generated for Adobe InDesign (.indd). To enable the app administrator to develop and test a new layout template step by step, these templates are subject to an approval process. Users can only view layout templates that have been approved, whereas administrators can also view the draft version of a layout template. They can both grant and revoke approval. |
Production Services |
|
Deployment formats | Deployment formats allow you to create specific publications from an issue. Essentially, they define how a usable PDF is generated from a specific issue using a defined production service. To enable the app administrator to develop and test a new deployment format step by step, these formats are subject to an approval process. Users can only work with deployment formats that have been approved, whereas administrators can also view and edit draft deployment formats. They can both grant and revoke approval. |
Status | Statuses are used to indicate the processing status in the layout plan. To do this, they must be linked to specific tasks via a BPMN process. A status cannot therefore be set manually, but only indirectly by completing these tasks. |
Rubrics | You can create rubrics that allow you to identify sequences of pages in the layout plan that are logically or thematically related. |
Tags/Tagging | Tags are used to categorize assets and content and are predefined by the app administrator in the list of tags in the configuration. Tags can be nested within one another. Additionally, you can specify "Applicable to" for tags, where you can select object classes on which these tags are allowed. |
Topic Types | Topic types simplify the creation of topics with recurring patterns in Media Edition by providing predefined article and task structures. |
Article Presets | Article presets are used to pre-select, for print articles scheduled within topics, which template and which editor should be associated with the article later on. Article presets can also be assigned to topic types. |
Publication Channels | Publication channels are used to pre-select, for online articles planned under specific topics, which template and which editor should be associated with the article later on. Publication channels can also be assigned to topic types. |