Open chunyuma opened 3 years ago
hmm.. interesting idea. I think I'm in favor of keeping them in KG2c - even though they're deprecated, there are still edges that use them. so we would lose those edges if we didn't include them.
looks like there are about 130,000 edges in KG2.6.1 that use a deprecated node:
match (n)-[e]-() where n.deprecated='True' return count(distinct e)
returns 131,303
@amykglen, although there are some edges that are connected to them in KG2.6.1, I found that almost half of them have no name and no description so I think I will doubt the reliability of these edges.
match (n) where n.deprecated='True' and n.name is NULL and n.description is NULL return count(distinct n.id)
count(distinct n.id)
--
21671
n.id | n.deprecated | n.name | n.description |
---|---|---|---|
"CHEBI:26169" | "True" | null | null |
"CHEBI:26165" | "True" | null | null |
"CHEBI:26166" | "True" | null | null |
"CHEBI:26168" | "True" | null | null |
"CHEBI:26161" | "True" | null | null |
"CHEBI:26162" | "True" | null | null |
"CHEBI:26163" | "True" | null | null |
"CHEBI:26164" | "True" | null | null |
@amykglen is this still relevant?
Based on the KG2.6.1c (http://kg2canonicalized.rtx.ai:7474/browser/) that @amykglen just built, I found that the nodes which are labelled as
deprecated
in KG2.6.1 are still used in KG2.6.1c. There are total 42,431 deprecated nodes in KG2.6.1. Should we ignore these nodes in KG2c build process?Here is one example: In KG2.6.1, we have
GO:0075020
which is labelled asdeprecated
But in KG2.6.1c, it still exists there.