rs_millitome.xlsx
I’ve attached an Excel file where the relevant rows are highlighted—these are the cases that have multiple Millitome codes and need to be fuzed.
Bruce's Slack message for Reference.
Fusing is done on the millitome side. We have to publish a new version with fused versions added. So for instance, if you want A1+A2 fused, we have to add that to the millitome itself and it becomes a new identifier #A1_A2. But you can't do that from the other side. Then the rui IDs have a sameAs field, if you look at the json that points to the millitome it was based off of
rs_millitome.xlsx
I’ve attached an Excel file where the relevant rows are highlighted—these are the cases that have multiple Millitome codes and need to be fuzed.
Bruce's Slack message for Reference.
Fusing is done on the millitome side. We have to publish a new version with fused versions added. So for instance, if you want A1+A2 fused, we have to add that to the millitome itself and it becomes a new identifier #A1_A2. But you can't do that from the other side. Then the rui IDs have a sameAs field, if you look at the json that points to the millitome it was based off of