Our intended model for loculus is that there can be arbitrary field names for unprocessed (originally submitted) metadata and for final processed data.
This would allow data to be submitted with say
city : London
but for the final processed data not to contain a city but to convert everything to
latitude : xxxx
longitude: yyyy
While we mostly support this pattern there is a problem that our errrors and warnings contain only info on the source i.e. the unprocessed data that triggered an error/warning. We would also like to be able to annotate the processed fields affected. At the moment we do that, but we do so by assuming the processed field has the same name as the source field.
I raised a PR to change this specification a while back:
Our intended model for loculus is that there can be arbitrary field names for
unprocessed(originally submitted) metadata and for finalprocesseddata.This would allow data to be submitted with say
city:Londonbut for the final processed data not to contain a
citybut to convert everything tolatitude: xxxxlongitude: yyyyWhile we mostly support this pattern there is a problem that our errrors and warnings contain only info on the
sourcei.e. the unprocessed data that triggered an error/warning. We would also like to be able to annotate the processed fields affected. At the moment we do that, but we do so by assuming the processed field has the same name as the source field.I raised a PR to change this specification a while back:
https://github.com/loculus-project/loculus/pull/932