Adding the beginnings of a new import API. This API will be used to update the database e.g. adding PDB files etc. I need to rethink the current separation between this and the ddgadmin repository. The ddgadmin repository is mainly used to process and normalize experimental input to the database. Maybe that should be its function and the import API be the bridge that the main APIs (ppi_api, monomeric_stability_api) and the ddgadmin repo use.
Adding the beginnings of a new import API. This API will be used to update the database e.g. adding PDB files etc. I need to rethink the current separation between this and the ddgadmin repository.
The ddgadmin repository is mainly used to process and normalize experimental input to the database. Maybe that should be its function and the import API be the bridge that the main APIs (ppi_api, monomeric_stability_api) and the ddgadmin repo use.

The new import API will use SQLAlchemy and transactions directly rather than baking this logic in custom classes and error-prone logic.

Kortemme-Lab/kddg,Kortemme-Lab/kddg