GFE not unique?

[mmaiers-nmdp]

There are two GFEs with the same name, this shouldn't happen in this database (e.g. need uniqueness constraint on g.name)

match (g:GFE)-[:HAS_SEQUENCE]-(s:Sequence) where g.name="HLA-Bw0-0-0-2410-0-5586-0-0-0-0-0-0-0-0-0"
    return g

also sequence should be 1-1 with GFE but these two GFEs that are the same string have 7 sequences associated

match (g:GFE)-[:HAS_SEQUENCE]-(s:Sequence) where g.name="HLA-Bw0-0-0-2410-0-5586-0-0-0-0-0-0-0-0-0"
    return g,s

Of these 7 sequences, 5 of them are unique and occur in GFEDB multiple times each:

match (g:GFE)-[:HAS_SEQUENCE]-(s:Sequence) where g.name="HLA-Bw0-0-0-2410-0-5586-0-0-0-0-0-0-0-0-0"
    return s.sequence, count(*)

Goal:

• GFE.name is unique within the database
• Sequence.sequence is unique within the database
• GFE and Sequence are 1-to-1 (which technically means they should be the same node)

[mmaiers-nmdp]

@pbashyal-nmdp found the uniqueness constraints and the one for GFE.name needs to be udpated (it currently says GFE.GFE_name).

Upon discussion, we agree to update the model to have a single GFE node with Sequence as a "property". And then make a uniqueness constraint on GFE.sequence

The queries will be simpler and faster. The HAS_SEQUENCE edge can be removed

[mmaiers-nmdp]

Are these actually not unique in IMGT?

[mmaiers-nmdp]

This is fixed in the current database on dockerhub "chrisammon3000/gfe-db:latest" accessed 2024-02-12