...
Metadata Lineage from Eagle MDC to Ontology - field attributes and element definitions
Setup Set Up Temporary Table for fieldExpressions
...
rdcDataStrategy - list of applied data strtategies
Extract file:
...
Custom Mashup:
In case you want to use custom file (CSV, JSON, etc.) to mashup it with fieldattributes extract.
Create custom dataset definition for the file in the folder: estar\tpe\dynamic\metadata\core\datasets
For example:
View file | ||
---|---|---|
|
This file describe custom CSV file:
View file | ||
---|---|---|
|
NOTE: pay attention on file path and adjust it correspondently.
Place file for mashup to path specified in dataset definition:
For example in dataset definition, path is defined as:
"file_name": " /apps/eagle/estar/tpe/dynamic/metadata/core/ontology/templates/EADataMapping.csv",
To make this works create custom processing rule in cache:
KEY: eagle.ebs.resource:O17_FIELDATTRIBUTE_2.0.57
VALUE:
View file name Invalid file id - 3022b10c-aae4-47f3-aad0-ec9ebbc03976
Pay attention on the following:
Add definition with key in the register_for_mashups block
Add mashup in mashups block
Add mapping in taxonomy block
...
KEY: eagle.ebs.resource:O17_FIELDATTRIBUTE_VERSIONS
VALUE: 2.0.57
Info |
---|
NOTE: O17 this is tenant prefix. it can be different for your case. |
Run EQL extract:
Code Block |
---|
{
"ServiceName": "EBS",
"ServiceMethodName": "extract",
"resourcename": "fieldattribute",
"outputformat": "EagleJSON",
"disabledatasetcache": "Y",
"resourceversion": "2.0.57",
"filters": {
"fieldattributeid": "5300,4876,4877,2014,4263,4265,371,4266,5864,2110,108,109"
}
}
|
Info |
---|
|
Output example with custom mashup:
Code Block |
---|
{
"eagleJSONVersion": "2-0",
"eagleJSONType": "ReferenceTransactionMessage",
"eagleJSONRevision": "294",
"referenceTransactionMessage": {
"header": {},
"referenceTransaction": [
{
"header": {
"objectType": "FieldAttribute"
},
"fieldAttribute": [
{
"objectType": "FieldAttribute",
"statField": "Y",
"calcType": "di",
"databaseName": "security",
"fieldAttributeDescription": "i Cusip",
"fieldAttributeId": 108,
"fieldIndicator": "S",
"fieldName": "PRIMARY_ASSET_ID",
"tableName": "SECURITY_MASTER",
"refCodeId": 99,
"comments": "Cusip",
"fieldIdentifier": "I CUSIP",
"scope": 2,
"readOnly": "N",
"fieldAttributeOntologyDescription": "Stores the most appropriate (primary) market security identifier of the financial instrument.",
"rdcFieldGroup": "IIP_AF_5",
"ea_mapping.LOB": "NYL Investors",
"ea_mapping.SUBJECT_AREA_DOMAIN": "SECURITY",
"ea_mapping.SUB_DOMAIN": "SECURITY",
"ea_mapping.BUSINESS_NAME": "PRIMARY_ASSET_ID",
"ea_mapping.BUSINESS_DESCRIPTION": "Current Primary Identifier of a security",
"ea_mapping.PHASE_1_NYLIM": "-NA-",
"ea_mapping.REQUIRED_FOR_FUTURE_STATE": "Y",
"ea_mapping.SOURCE_PLATFORM": "CAMRA",
"ea_mapping.SOURCE_TABLE": "SECURITY",
"ea_mapping.SOURCE_COLUMN_SOURCE_COLUMN_STAT": "CUSIP",
"ea_mapping.FORMAT": "CHAR(100)",
"ea_mapping.COMMENTS_DERIVATIONS_TRANSFORMATIONS_FOR_SOURCE": "This is CUSIP",
"ea_mapping.EXTRACT_FIELD_EXTRACT_FIELD_STAT": "CUSIP",
"ea_mapping.FORMAT": "CHAR(100)",
"ea_mapping.ML_ELEMENT": "EagleML/referenceTransaction/genericSMF/primaryAssetId",
"ea_mapping.SUBJECT_AREA_FOR_INTERNAL": "cam_egl_smf",
"ea_mapping.TARGET_FIELD_NAME_FOR_INTERNAL": "primaryAssetId",
"ea_mapping.MANDATORY_FIELD": "Y"
}
]
}
]
}
} |
Add label