Hi Darren,
It is sometimes necessary to create custom lineage to (or from) Reference Data Sets/Elements. lineage_validator classifies all id's of Reference Data Sets as invalid. Adding "includeRefObjects": "true" to the first call of /access/2/catalog/data/objects inside validate_edc_id function should fix it.
So the lines 298-310 of the script would be:
tResp = edcHelper.session.get(
apiURL,
params={
"offset": 0,
"pageSize": 1,
"id": f"{id}",
"associations": link_type,
"includeDstLinks": "true",
"includeSrcLinks": "true",
"includeRefObjects": "true"
},
headers=header,
)
The is_resource_casesenitive function will not work for Reference Data Sets, as the /access/1/catalog/resources/{resourceName} does not work with Reference Resources well (they may have "too strange" names), but it is not an issue as the first call to /access/2/catalog/data/objects should validate correctly.
Thanks
Greg
Hi Darren,
It is sometimes necessary to create custom lineage to (or from) Reference Data Sets/Elements.
lineage_validatorclassifies all id's of Reference Data Sets as invalid. Adding"includeRefObjects": "true"to the first call of/access/2/catalog/data/objectsinsidevalidate_edc_idfunction should fix it.So the lines 298-310 of the script would be:
The
is_resource_casesenitivefunction will not work for Reference Data Sets, as the/access/1/catalog/resources/{resourceName}does not work with Reference Resources well (they may have "too strange" names), but it is not an issue as the first call to/access/2/catalog/data/objectsshould validate correctly.Thanks
Greg