136 mixturedesign mapping #139
Conversation
|
The mixDesign-extraction produces a yaml-file that works with the new uploaded mixture-mapping-script. It is clear that everything related to Cem-II won't recieve values, since our raw data has only one typ of cement and it's information is saved in Cem-I. The checks need to be adjusted to this version of the mapping script. |
|
Update: No new mapping script for mixture is planned, instead we will use the same one as for emodule (#118 (comment)). |
|
I am closing this pull request and will delete the branch, because it is better to work on the MixDesign Extraction on the same branch as for emodule. A seperate mapping script is not needed. |
In order to make the mapping to placeholders work, the key-names in the extraction script need to fit the placeholders.
Since the raw data we have doesn't fit to the MixDesign Ontology (which is made for different types of cement, CemI, CemII), and we don't have any suitable raw data, I created a new extraction-script that will make our raw data work with the MixDesign Ontology: mixdesign_metadata_extraction.py
The old script (mixture_metadata_extraction.py) won't get touched so that it won't be lost and can be easily adjusted if one day we have a MixOntology that suits that raw data.
I explained the difference between those two scripts in a readme.