Import objects and links in uses from a CSV file

The purpose of this article is to explain how to import Uses in the catalog of Data Galaxy. 

To understand more in-depth the concept of property and objects, you can consult this article. 

As a reminder: Uses explains to users the source of the data used in restitution. 

The goal of this feature is to:

• Ease the import of Uses type object,
• Accelerate the objects update with the import of data previously exported.

The import option is available: 

• from the "Shortcuts" widget on the home page of the clientspace or workspace
• from the Uses module when it is empty
• from the contextual menu of the Uses module, to the right of the filtered views.

Importing objects

DataGalaxy users can import properties from a CSV file by following these steps:

1. Go to the Uses module

2. Click on the 3 dots icon

3. In the drop-down menu, click on Import
 4. Select or drag and drop your file to be imported into the CSV File area available at the top left.
 

If some options can be set later, the file to be imported must always contain the following columns:

• The object path
• The object type
• + a column for each attribute that is part of the object card that you want to import

Example of a file to import:

"Path";"Type";"Status";"DataOwners";"Summary";"CDPEtiquetteUsages"
"\Finance\Market Monitoring";"\Application\Dashboard";"Proposed";"dataowner@datagalaxy.com";"";"Finance"
"\Finance\SAP\Analysis of customer";"\Application\Application\Screen";"Valided";"dataowner@datagalaxy.com;""SAP screen accessible via the FAGL transaction ";""Finance","RGPD""

6. The next step allows you to map properties and perform functional checks before importing. When possible, an automatic mapping between source and target fields is performed and the verification of your file is launched.

• If the mandatory fields are not mapped, the verification is not launched and the import is not possible.
• if the check is sucess, the import is avaible (the Import button is immediately active).
• if the check is failure, the checking are in the Cheks tab. 

 By clicking on the check status, the tab opens with the list of failures checking has been detected: 

• When a blocking error can be solved, the solution is in the "Action" column.
• These controls are mandatory and must be re-launched when a modification in the Mapping tab is made.

7. Check the accuracy of the fields to be recovered in the Mapping tab

• You have to drag the fields of the left column on the corresponding fields on the right.
• Only the fields type and path, identified in red, are mandatory.
• For files with many attributes: it is possible to search for attributes and hide the fields used by checking the box. 

NB : In the case of updating your objects via this import, if you import empty values of the attributes in your file, which are already filled in your object cards, these empty values will be ignored by default and your existing values are saved. But, by checking this option (figure below), they will empty the existing values.

8. The Preview tab allows you to preview the values for each attribute to be imported, for which a match has been defined.

9. When these steps are completed and the check is successful, the Import button becomes active. Click on Import to launch the import. 

Import related objects (relations + uses)

It is possible to import:

• relations (logical links not visible in the lineage)
• use links (physical links with the glossary and the dictionary visible in the lineage)

To do this you need to:

1. Go to the Uses module

2. Click on the 3 dots icon

3. In the drop-down menu, click on Import

4. Select or drag and drop your file to be imported into the CSV File area available at the top left.

The file to be imported must always contain the following columns:

• The path of the source object
• The type of the source object
• The type of the relationship
• The path of the target object
• The type of the target object

Example of a file to import:

"SourceEntityPath";"SourceEntityType";"EntityLinkType";"LinkedEntityPath";"LinkedEntityType"
"\Extraction prospect;\Usage";"uses";"\AdventureWorks\ProspectiveBuyer";"\Database\Table"
"\Autres\Dynamics\Analyse comparative";"\Application\Application\Report";"is usage source for";"\Load asset";"\Data Processing"