Harmonize SynGO's use of UniProt identifiers and MOD identifiers

[kltm]

Currently, bioentities coming from SynGO may use a different identifier (UniProt) than the same entity elsewhere in the GO data stream (i.e. MOD identifiers). This causes issues like confusion with endusers, items not getting their labels resolved in Noctua interfaces (NEO isssues), etc.

Closing this ticket would either be: 1) the SynGO upstream harmonizes with the current GO practice of using the MOD identifiers or 2) the GO, as part of a new (pipeline/ingest?) process, translates the incoming UniProt identifiers to the appropriate MOD-blessed ones.

As a first step, @thomaspd (?) will reach out and see if "1" is a possibility.

Tagging @thomaspd @pgaudet

[kltm]

Highlighting some forensic work from @dustine32 :

...UniProt has an intuitive workflow of mapping IDs and giving you the list of unmapped IDs, similar to PANTHER. Since you can only map to one MOD at a time, I tried MGI first. The results from UniProt:

701 out of 1,562 identifiers from UniProtKB AC/ID were successfully mapped to 698 MGI IDs.

Then I took the list of 861 remaining unmapped IDs and repeated for RGD, FlyBase, WormBase, HGNC to get a small list of 50. Checking these 50 IDs' taxons through the API, I see none of them are to mouse (NCBITaxon:10090).

[pgaudet]

@dustine32 Can you work with @thomaspd to give feedback to SynGO to update their annotations with the correct identifiers ?

@ftwkoopmans