ANDV curations conflict with subsequent INSDC revisions

[maverbiest]

Describe the possible issue

There are six ANDV sequences for which we curated metadata on Pathoplexus for which the metadata were updated on INSDC. This causes an issue when we're ingesting INSDC data: the ingest pipeline see that there are changes in the newly ingested INSDC data, but because there are existing curations it does not know how to proceed. Currently, this causes many alerts to the Pathoplexus team.

Evidence of the problem

There are currently many automated alerts being sent to the Pathoplexus team (primarily on Slack). This has the potential to make the team miss other alerts and/or become desinsitised to these types of alerts.

Suggested change

The Pathoplexus team added to option to manually exclude specific changes to INSDC data from triggering a revision. Since this exclusion list is maintained manually in a targeted way at the accession level [link], there is no risk of this accidentally leading to us missing relevant changes in INSDC data.

Full list of affected sequences

PP_006VZ20, PP_006VZ3Y, PP_006VZ4W, PP_006VZ5U, PP_006VZ6S, PP_006VZ7Q

[anna-parker]

We believe the curations from the INSDC are invalid a summary of our findings can be found here: https://loculus.slack.com/archives/C05G172HL6L/p1781091311063189

Accession	Curated date	New date on the INSDC
MN258156	1996-12-11	1996-11-12
MN258157	1997-11-30	1997-12-01
MN258158	2018-11-09	2018-08-19
MN258159	2018-08-19	2018-09-11
MN258160	2018-04-09	2018-04-12