Open nataled opened 1 year ago
Done - fixes logged here - mismatch list.xlsx
This issue arose because, when we updated the Reactome local copies of UniProt records to conform to UniProt, we did not include a check for changed chain lengths in the UniProt records (with an alert to re-edit affected entityWithAccessionedSequence instances. We still need to implement that update check feature so I'm re-opening the ticket to track progess there.
The update check feature should now be implemented at Reactome but the ticket stays open until the feature is confirmed to work as expected.
I found something odd. The following error messages were generated from my processing of the 'Liam' data. Each of these point out when the stored information for sequence length in Reactome differs from UniProtKB. What's odd is that these errors are not visible when looking at the web presentation (at least for the ones I spot checked). An example:
https://www.reactome.org/content/detail/R-HSA-419522 (shows chain 1-1451) https://reactome.org/content/schema/instance/browser/419522 (shows endCoordinate 1471)