The data handling in this application is currently hectic - it's a lot of dictionaries with a lot of post-processing, and the only fixed content it a couple of dataclasses which are still evolving.
Consider a formally spec'd model to underpin object concepts e.g. the representation of a variant, a MOI-confirmation event, a previously seen variant
This would benefit from an established way of navigating updates to models, such that if the model develops, older versions of the schema can be made compatible
The data handling in this application is currently hectic - it's a lot of dictionaries with a lot of post-processing, and the only fixed content it a couple of dataclasses which are still evolving.
Consider a formally spec'd model to underpin object concepts e.g. the representation of a variant, a MOI-confirmation event, a previously seen variant
https://avro.apache.org/docs/1.11.1/getting-started-python/ might be an example
This would benefit from an established way of navigating updates to models, such that if the model develops, older versions of the schema can be made compatible