...

Introduction

HDC needs has the requirement to import and export data to/ from multiple different various data sources like such as design systems, management systems, electronic and paper documents. This data not only comes in different formats , but also, quite often, and often utilizes different means of identification are used.  Identifiers can be incompatible or Incompatibilities can arise with identifiers stored under different property fields.

In HDC, each of such these identifiable systems or data sources are called is referred to as EID. EID is actually represents a set of rules that describes defines how the objects should be identified and matched, as well as how to map (translate) their metadata should be translated to a common structure in within HDC. The mapping works both ways during This translation process operates bidirectionally during both import and export.

As the import of data shifted from manual procedures for data import have transitioned to high-volume automated importprocesses, it became clear that has become evident that managing multiple ID systems is necessary due to not only mistakes but simply different also differing object ID rules in across various data sources make it necessary to handle multiple ID systems while communicating HDC with external world. 

...

when communicating with the external world through HDC.

External  External Information Domains panel

...

...

Columns:

• Domain ID

...

• : This is the unique identifier for each domain.

• Name: The name of the domain.

• Is Live: Indicates whether the domain points to another online service configured in the Live Data Source tab

...

• .

• Public

...

• : Specifies if other HDC functions can use this domain

...

• , for example

...

• , copy object IDs

...

• .

...

After creation of external domain creating an external domain, you can click it's its name to see view detailed rules for this domain starting from the Object Classes tab.

...

Exporting and

...

Importing External Domain

...

Configuration

It is You can now possible to export chosen selected External Domain Configuration along with all it's mapping to its mappings to a file in JSON or XML format.

In In the TDXM panel, click on panel, navigate to the External Information Domains panel to get view a list of all external domains.
Select a domain, than then click on on the Export button button and choose the file format of for the export. This action will download a file with containing the configuration of the selected domain to your discdisk.



To import domain configuration create , follow these steps:

1. Create a new domain

...

1. and select it

...

1. .

2. Click on the Import button to choose the file with the exported configuration.

Here's what you need to know about the import process:

• All object classes and their fields from the exported domain will be added to the new domain

  on 

  on the Object

  Classes 

  Classes tab.

• Entries

  on 

  on the Object Mappings

   tab

  tab will only be added when target class/fields are present

  of course

  in the destination DB (in case

  import is done in

  of importing into a different DB/application)

  Same goes for 

  .

• The same applies to Global Layers

   mapping

  mapping - the target global layer must

  exists

  exist.

• All 

  All Private

  layers mapping

  Layers mapping will be added with a set of permissions if

  same

  users with matching usernames exist in

  destination DB are present as in exported one (matched by username

  both databases (exported and destination).

• Live Data Source

   configuration 

  configuration is not

   exported

  exported.