This is the current cypher request that I use to download data. This example would be for all the GFEs for HLA-A in version 3.41.0
MATCH (n:IMGT_HLA)-[r:HAS_GFE]-(g:GFE) WHERE n.locus = "HLA-A" AND r.imgt_release = "3.41.0" RETURN n.name, g.name
What I currently use is JSON with GFE keys, and the HLA allele names as values, to make sure that I catch if two different GFE keys are assigned to the same HLA allele. (It was an issue because of the ambiguities in the KIR genes.) It sounds like the new database will do that check for me, so I don't care which is the key and value, just that I can get JSON formatted key-value pairs.
This is the current cypher request that I use to download data. This example would be for all the GFEs for HLA-A in version 3.41.0
MATCH (n:IMGT_HLA)-[r:HAS_GFE]-(g:GFE) WHERE n.locus = "HLA-A" AND r.imgt_release = "3.41.0" RETURN n.name, g.nameWhat I currently use is JSON with GFE keys, and the HLA allele names as values, to make sure that I catch if two different GFE keys are assigned to the same HLA allele. (It was an issue because of the ambiguities in the KIR genes.) It sounds like the new database will do that check for me, so I don't care which is the key and value, just that I can get JSON formatted key-value pairs.