dio:content - Interfaces

K4 Connector

Data located in dio:content is incorporated into the editorial workflow with K4 via Drag’n Drop or mass export where it is checked in automatically. After the page production has been completed, the complete pages are re-imported into dio:content. Complete pages and their elements are linked to one another and the various file types (complete pages, pictures, texts, displays) are made available in its own archive areas. In addition, publication and media-type-specific metadata is also handed over for archiving.

Quark QPS Integration

Data located in dio:content is incorporated into the editorial workflow with Quark via Drag'n Drop or targeted export.
After the page production has been completed, the complete pages are re-imported into dio:content; complete pages and their elements are linked to one another and the various file types (complete pages, pictures, texts, displays) are made available in own archive areas. In addition, publication and media-type-specific metadata is also handed over for archiving.

With the integrated solution from dio:content and QPS as of Version 7, dio:content serves as a common repository for the original data of both systems. This makes it possible to have a common view of the operations and content in the editorial workflow. Among other things, the functionality includes functions for the picture workflow such as a user interface that is optimized for quick viewing and selection (dio:content - work), online transmission of the selected pictures to the QPS workflow without a physical export, and an "Online long-term archiving" of the finished QPS publications in dio:content: The QPS7 integration is the basis for other modules such as Digital Marking, for example.

LDAP Connector

This connector makes it possible to have central system-independent management of users and user roles. Here, additional "Shadow" accounts are managed in the system that make it possible to store personal, system-related settings. These accounts can also be used for user authentication if need be, of the LDAP services are not available.

API Interface

With the help of this programming interface, it is possible for any software systems to connect to dio:content.