Technical preview function is in a state that it can be tried. The development is complete, there is documentation and there are samples, tutorials and hands-on labs as appropriate.
The community is looking for feedback on the function before declaring it stable. This feedback may result in changes to the external interfaces.
Display Integrator Open Metadata Integration Service (OMIS)¶
The Display Integrator OMIS supports the exchange of displayed data such as reports and forms along with their related schema and connection information between an external system supporting the data display and the open metadata ecosystem.
It supports a type of integration connector that are able to create assets representing forms, reports and queries along with their associated display schema .
Forms and Reports¶
Figure 1 shows the types of metadata for forms and reports that integrators connectors can create with this integration service.
Figure 1: Forms and Reports metadata supported by the Display Integrator OMIS
Either can be represented as a set of nested DataContainers with specific input and output DataFields use to represent the individual data items.
Integrators connectors can also create queries that support forms and reports with this integration service. Figure 2 shows the types of metadata for the queries.
Figure 2: Query metadata supported by the Display Integrator OMIS
Queries can also be represented as a set of nested data containers and data fields.
Open Metadata Types¶
Figure 3 shows the open metadata types used to represent the metadata for forms, reports and queries created through this service.
Figure 3: Form and Report open metadata types supported by the Display Integrator OMIS
The different subtypes enable metadata searches to narrow the results to this type of display metadata.
When a data container or a data field is attached to a form or report asset, the service automatically inserts the AssetSchemaType relationship, DisplaySchemaType entity and AttributeForSchema relationship in between the asset entity and the data container/field entity if not already in place.
When a data field/container is nested inside another, it is linked to the structure using the NestedSchemaAttribute relationship.
This integration service is paired with the Data Manager OMAS.