How to handle upstream changes to chain-sequences?

[jamesaoverton]

We have a make update-seqs task that fetches sequences from IMGT and stores them in:

https://github.com/IEDB/MRO/blob/master/ontology/chain-sequence.tsv

Sometimes IMGT changes a sequence that we had previously stored, for example:

https://github.com/IEDB/MRO/pull/41/files#diff-10783046cde2b2261cb684331c670c2cR173

What should we do when we see upstream changes like this? @rvita @acrinklaw

[rvita]

we want MRO to stay up to date with IMGT, they are the SOT for the sequences, so we should have a schedule to check for updates & change MRO to match IMGT if any changes are found.

[jamesaoverton]

We're updating them regularly to match IMGT. But we're just silently updating MRO. Do you need to be warned when these change?

[rvita]

I do not, but if the tools are integrated, the tools team may need to know. This is a question for @jgbaum