You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the with respect to the banana problem, the neo4j graph standardizes to not duplicating embedded IDs. For instance, CHEBI:77746 appears as a node ID. However, from an INDRA perspective this is not valid, so every query endpoint should, at a very low level (i.e., as part of every higher level call) re-standardize these before they reach any outside code. Vice versa, incoming queries will use the standard that has these prefixes e.g., CHEBI:CHEBI:77746 so these would need to be mapped before running the query on the graph.
Alternatively, the graph could be changed to use a standard where embedded namespaces are preserved.
The text was updated successfully, but these errors were encountered:
Currently the with respect to the banana problem, the neo4j graph standardizes to not duplicating embedded IDs. For instance,
CHEBI:77746
appears as a node ID. However, from an INDRA perspective this is not valid, so every query endpoint should, at a very low level (i.e., as part of every higher level call) re-standardize these before they reach any outside code. Vice versa, incoming queries will use the standard that has these prefixes e.g.,CHEBI:CHEBI:77746
so these would need to be mapped before running the query on the graph.Alternatively, the graph could be changed to use a standard where embedded namespaces are preserved.
The text was updated successfully, but these errors were encountered: