@EvanDietzMorris runs jobs that normalize lots of nodes in bulk, so he needs to make sure that NodeNorm doesn't change in the middle of his run. We discussed two things that would help with that:
If we could incorporate the Babel version number (e.g. 2022oct13) into the NodeNorm Swagger version number (currently 2.0.9 from the Babel image), then he could query the version number at the start and at the end of his run to confirm that all his normalization occurred consistently.
@EvanDietzMorris runs jobs that normalize lots of nodes in bulk, so he needs to make sure that NodeNorm doesn't change in the middle of his run. We discussed two things that would help with that:
2022oct13
) into the NodeNorm Swagger version number (currently 2.0.9 from the Babel image), then he could query the version number at the start and at the end of his run to confirm that all his normalization occurred consistently.