Skip to content

ANDV curations conflict with subsequent INSDC revisions #26

Description

@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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions