CSV file format for importing asset relationships details
The CSV file for importing asset relationships details must conform to specific formatting rules.
Limitations
- File encoding is UTF-8.
- The maximum recommended size of a file is 10,000 lines.
- Relationship names are the default display relationship names.
- Relationships can only be from an asset or column to another asset or column or artifact.
- Relationships from an artifact to an asset or column are not supported.
- Cross container (workspace) relationships are supported.
Header row
The headers in the first row of the CSV file represent which properties are imported for the relationships.
- The header row must be the first row in the file and must not be repeated.
- The header must include the mandatory headers.
Mandatory headers
The header row of the CSV file must include the following mandatory headers:
- Relationship Name
- Default display relationship name in English. Do not use localized names.
Example:Contains
- Source Item Type
- Type of the source relationship: asset or column.
Example:column
- Source Workspace Type
- Source container: catalog, project or space.
Example:project
- Source Workspace Name
- Name of the source container.
Example:Test project
- Source Asset Name
- Name of the source asset.
Example:Test asset
- Source Column Name
- Name of the column if
Source Item Type
iscolumn
.
Example:Column1
- Target Item Type
- Type of the target relationship: asset, column or artifact.
Example:artifact
- Target Workspace Type
- Target container: catalog, project or space. Optional if
Target Item Type
isartifact
. - Target Workspace Name
- Name of the target container. Optional if
Target Item Type
isartifact
. - Target Asset Name
- Name of the target asset. Optional if
Target Item Type
isartifact
- Target Asset Resource Key
- Resource key of the target asset. Optional if
Target Item Type
isartifact
. - Target Column Name
- Name of the target column if
Target Item Type
iscolumn
. Optional ifTarget Item Type
isartifact
orasset
. - Target Category
- Artifact category path. Optional if
Target Item Type
isasset
orcolumn
.
Example:Root category>>Subcategory
- Target Artifact Name
- Artifact name. Optional if
Target Item Type
isasset
orcolumn
.
Example:Test category
- Target Artifact Type
- One of the following category of the artifact: category, glossary_term, classification, data_class, rule, policy, reference_data. Optional if
Target Item Type
isasset
orcolumn
.
Example:category
Optional headers
To specify more detailed asset relationships, add appropriate optional headers to your CSV file.
- Source Asset Resource Key
- Resource key of the source asset.
Example:testdata.csv
Example asset relationships CSV file
Relationship Name,Source Item Type,Source Workspace Type,Source Workspace Name,Source Asset Name,Source Asset Resource Key,Source Column Name,Target Item Type,Target Workspace Type,Target Workspace Name,Target Asset Name,Target Asset Resource Key,Target Column Name,Target Category,Target Artifact Name,Target Artifact Type
Has part,asset,catalog,import test,BANK_CLIENTS,0000:0000:0000:0000:0000:FFFF:A92C:974B|50000|BANK:/BANK1/BANK_CLIENTS,,column,catalog,csv-test-2,BANK_ACCOUNTS,0000:0000:0000:0000:0000:FFFF:091E:6D11|50000|Bank:/BANK2/BANK_ACCOUNTS,CUSTOMER_ID,,,
Implements,column,catalog,import test,BANK_CLIENTS,0000:0000:0000:0000:0000:FFFF:A92C:974B|50000|BANK:/BANK1/BANK_CLIENTS,CLIENT_ID,artifact,,,,,,Locations,Physical Locations,reference_data
Governs,asset,catalog,import test,BANK_CLIENTS,0000:0000:0000:0000:0000:FFFF:A92C:974B|50000|BANK:/BANK1/BANK_CLIENTS,,artifact,,,,,,[uncategorized],Account Number,data_class
Contains,asset,catalog,import test,BANK_CLIENTS,0000:0000:0000:0000:0000:FFFF:A92C:974B|50000|BANK:/BANK1/BANK_CLIENTS,,asset,catalog,csv-test-1,0 - EMD Mapping 1,/root###jjw_EMD_out###0 - EMD Mapping 1,,,,
In the example, there are four records that demonstrate the relationships:
Has part:
asset to column in a different catalog.Implements:
column to artifactreference_data
.Governs:
asset to artifactdata_class
.Contains:
asset to an asset in a different catalog.
Learn more
Parent topic: Adding and updating asset metadata