Open gaurav opened 1 year ago
I think this might be from NodeNorm output; for example, we can get a result like:
"UniProtKB:Q80VY9-1": {
"categories": [
"biolink:GeneProductMixin",
"biolink:GeneOrGeneProduct",
"biolink:BiologicalEntity",
"biolink:Entity",
"biolink:ThingWithTaxon",
"biolink:NamedThing",
"biolink:ChemicalEntityOrGeneOrGeneProduct",
"biolink:Protein",
"biolink:ChemicalEntityOrProteinOrPolypeptide",
"biolink:MacromolecularMachineMixin",
"biolink:Polypeptide"
],
"name": "ATP-dependent RNA helicase DHX33 isoform m1 (mouse)",
"attributes": [
{
"attribute_type_id": "biolink:same_as",
"value": [
"UniProtKB:Q80VY9-1",
"PR:Q80VY9-1"
],
"value_type_id": "metatype:uriorcurie",
"original_attribute_name": "equivalent_identifiers",
"value_url": null,
"attribute_source": null,
"description": null,
"attributes": null
}
]
}
For example, in the query:
We get back the result:
This is not wrong, just unnecessary. This might be deliberate, so a client can figure out the identifier without looking at the key, and I'm not sure if the problem is in the cam-pipeline output or ORION. Just wanted to document this here so we can think about this later on.