ENH: Adding a structured lineage <=> issue mapping file

[corneliusroemer]

Right now, we mention lineage-related issues in lineage_notes.txt which is a semi structured tsv file.

It would be less bug prone and easier for machines to parse if we added issue-lineage information in a separate lineage_issue.csv file.

[AngieHinrichs]

It should have either

• a column with repository name (cov-lineages/pango-designation or sars-cov-2-variants/lineage-proposals), if there is a numeric column with issue number

or

• a column with the URL to the issue

[AngieHinrichs]

@ciscorucinski are you already making a file like this?

[ciscorucinski]

Not at the moment. I used a regex within Google Sheets to pull that information from each row. I haven't expanded on it as the github issues aren't structured for data processing. But here is a simpler version of the regex that seems to work https://regex101.com/r/Qfjcil/1

Just want to say that there is a reference to https://github.com/jmcbroome/auto-pango-designation, too, (EG.1) which also has an issue attached to it. No other designations seem to have multiple IDs attached to it.

[ciscorucinski]

Here is a very quick Google Sheets that splits them by each repository (except auto pango)

https://docs.google.com/spreadsheets/d/1NqUjXOn_JMCdZBHSzPMmxtvu8xcbDZJBEMm3dEVr5TY/edit?usp=sharing

[AngieHinrichs]

Awesome, thanks @ciscorucinski!

[DailyCovidCases]

Please close this issue