The CoreMedia Content Hub allows integrating various external and asset management systems into the Studio library. It allows you to integrate just about any external system or platform into your CoreMedia system.

Note

Every integration of an external system for the Content Hub or any other CoreMedia hub is called adapter.

This section describes the functionality of the Content Hub and the required steps to implement a custom adapter for it. Adapters are usually implemented as extensions for Studio, using the extensions point studio-lib (and studio if UI customizations are required).

In order to create a custom Content Hub Preview, you must implement the ContentHubObject method getDetails, which returns a list of DetailsSections. A section can be configured to be non collapsible, also the header can be hidden. Within that Section a list of DetailsElement need to be defined. You can put a value of type Calendar, String or ContentHubBlob into this element. The interface ContentHubObject offers a special constant SHOW_TYPE_ICON that can be used to show the Content Hub Object's type icon instead of a picture.

In order to provide preview pictures in form of ContentHubBlob you need to provide an object of that type as value for your DetailsElement. This blob does not need to contain an InputStream yet, but only metadata and a so called classifier. In a second call the method getBlob will be called by the framework with the classifier in order to resolve the blob. This method must return a ContentHubBlob with an InputStream containing the picture's data.

Warning

Pictures sent as preview to the client should not exceed the limit of 10Mbyte. If that is the case, the framework will not display the picture in the client.

The Labels of Sections and Elements can be localized in your Content Hub Client extension. Therefore, you need to provide a localization key that consists of the label and postfix _sectionItemKey for Element labels or _sectionName for Section Headers.