Some duplicate labels are due to field length restrictions from the old build process - how to resolve

[hoganwr]

Some duplicate labels (approx. 90 of them) result from label truncation in the old Scala-based build process. How can we fix these?

Investigation thus far:

1. The update_label process only updates active RxNorm "concepts" in the lastest monthly release
2. The labels involved are "historical" or "retired" RxCuis, and thus the latest monthly releases do not include them and update them
3. This RxAPI call can get the label from the RxCui: https://rxnav.nlm.nih.gov/REST/rxcui/805526/historystatus.json, and the RxCui 805526 is an example of one of the issues

So, we can try writing a script that takes the RxCuis as input, makes the API call, gets the "name" (aka 'label') out, and updates the template somehow.

Alternatively:
4. The RXNATOMARCHIVE.RRF folder has the name, we could either write a script to pull names out of that file or to load the RXNATOMARCHIVE.RRF file into sqlite and do a SQL-based update
5. The benefits of the latter in 4 is that it's easy to write out the templates from sqlite because that's the normal build process and we have a script for that already

To do that, we'd have to write a sql script that creates teh RXNATOMARCHIVE table and populates it, we could follow the examples for thte other tables.

[hoganwr]

Ok, build process now adds RXNATOMARCHIVE to the rxnorm.db that gets created. Next step is to use that to update the labels. Note that there can be multiple rows per RxCUI in that table, so we need to grab the most recent row, likely from the LAST_RELEASED field.

[hoganwr]

Now that we've updated labels from the "archive", there are ~1347 duplicate classes, defined as "same rdfs:label, same RxCUI annotation". See attached file.

We just need to keep one and obsolete the other, pointing the obsoleted one at the one we preserve (e.g., "replaced by".
duplicate-classes.tsv

[hoganwr]

Resolved w/recent PR merges