Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

In the Metadata Manager, you can create and edit CSV files with the CSV Editor. The format of the CSV files depends on the metadata that is being loaded via each file.

Items File Format

The items CSV file must contain the following columns, each row represents one item:

  • Item ID

  • Item Name

  • Eagle Version

The following table describes the sample_items.csv file layout for loading new items for the Table type. 

On this page:

Two new tables will be loaded: CLIENT_CUSTOM_SEC and CLIENT_CUSTOM_SEC_HIST.

Item ID

Item Name

Eagle Version

security.dbo.client_custom_sec

client_custom_sec

13.0.0.0

security.dbo.client_custom_sec_hist

client_custom_sec_hist

13.0.0.0

The following table describes the sample_items.csv file format for loading columns for the CLIENT_CUSTOM_SEC and CLIENT_CUSTOM_SEC_HIST tables. 

Item ID

Item Name

Eagle Version

security.dbo.client_custom_sec.security_alias

security_alias

13.0.0.0

security.dbo.client_custom_sec.client_data

client_data

13.0.0.0

security.dbo.client_custom_sec_hist.security_alias

security_alias

13.0.0.0

security.dbo.client_custom_sec_hist.src_intfc_inst

src_intfc_inst

13.0.0.0

security.dbo.client_custom_sec_hist.effective_date

effective_date

13.0.0.0

security.dbo.client_custom_sec_hist.client_data

client_data

13.0.0.0

Item Attributes File Format

The item attributes CSV file must contain the following columns:

  • Item ID

  • Attribute Name

  • Attribute Value

  • Eagle Version

The first two columns identify the item, and the last two columns provide the name of the attribute and its appropriate value.
The following table describes the sample_attributes.csv file for loading the Client Description attribute and the corresponding actual description for the CLIENT_CUSTOM_SEC and CLIENT_CUSTOM_SEC_HIST tables.

Item ID

Attribute Name

Attribute Value

Eagle Version

security.client_custom_sec

client description

Client custom security table

13.0.0.0

security_client_custom_sec_hist

client description

Client custom security history table

13.0.0.0

If you change the attribute value in the file, and then load the file again, it will overlay the previous value in the Metadata Manager's database.

Parents and Children File Format

The parents and children CSV file must contain the following columns:

  • Item ID

  • Child Type

  • Child ID

  • Eagle Version

The first two columns represent the parent item by item type and external ID and the last two columns provide the child item.
In the sample file below, the parent and children relationship between the tables and its columns will be loaded.
The following table describes the sample_containment.csv file format for loading the "containment" relationship between the CLIENT_CUSTOM_SEC and CLIENT_CUSTOM_SEC_HIST tables and the columns that were previously loaded.

Item ID

Child Type

Child ID

Eagle Version

security.dbo.client_custom_sec

column

security.client_custom_sec.security_alias

13.0.0.0

security.dbo.client_custom_sec

column

security.client_custom_sec.client_data

13.0.0.0

security.dbo.client_custom_sec_hist

column

security.client_custom_sec.hist.security_alias

13.0.0.0

security.dbo.client_custom_sec_hist

column

security.client_custom_sec.hist.src_intfc_inst

13.0.0.0

security.dbo.client_custom_sec_hist

column

security.client_custom_sec_hist.effective_date

13.0.0.0

security.dbo.client_custom_sec_hist

column

security.client_custom_sec._hist.client_data

13.0.0.0

Map File Format

The map CSV file must contain the following columns, each row represents one mapping relationship:

  • Map Name

  • From Type

  • To Type

  • Owner Item Type

  • Owner Item ID

  • Context Definition

  • Eagle Version

The following table describes the sample_map.csv file format for loading and defining four (4) maps: Positions, Cash Activity-CashFlow, CashActivity-Derived, and CloseTrades.

Map Name

From Type

To Type

Owner Item Type

Owner Item Type ID

Eagle Version

Positions

tag

column

Eagle Dictionary Datamaps

10

13.0.0.0

Cash Activity-
CashFlow

tag

column

Eagle Dictionary Datamaps

10

13.0.0.0

CashActivity-Derived

tag

column

Eagle Dictionary Datamaps

10

13.0.0.0

CloseTrades

tag

column

Eagle Dictionary Datamaps

10

13.0.0.0

Map Relation File Format

The map relation CSV file must contain the following columns, each row represents one mapping relationship:

  • Map Name

  • Target Item ID

  • Definition

  • Source Item ID

  • Eagle Version

The following table describes the sample_map_relations.csv file format for loading the mapping relationships (source and target items) into the map.

Map Name

Target Item ID

Definition

Source Item ID

Eagle Version

Cash Activity -
CashFlow

cash.dbo.cash_activity!entity_id

The entity id assigned to the entity.

5

13.0.0.0

Cash Activity-
CashFlow

cash.dbo.cash_activity!security_alias

The security_alias assigned to the security that is associated with the cash activity record..

10

13.0.0.0

CashActivity-CashFlow

cash.dbo.cash_activity!long_short_indicator

For reflexive flow always maps as "L" Else Map incoming value.

15

13.0.0.0

CashActivity-CashFlow

cash.dbo.cash_activity!bank_alias

The bank alias the cash record is stored in is STAR.

16

13.0.0.0

Map Attributes File Format

The map attributes CSV file must contain the following columns, each row represents one mapping relationship:

  • Map Name

  • Attribute Name

  • Attribute Value

  • Eagle Version

The following table describes the sample_map_attributes.csv file format for loading the attributes to further describe the map.

Map Name

Attribute Name

Attribute Value

Eagle Version

Positions

Department

Internal

13.0.0.0

Cash Activity-
CashFlow

Department

Product

13.0.0.0

CashActivity-Derived

Department

Product

13.0.0.0

CloseTrades

Department

Product

13.0.0.0


  • No labels