Open meowcat opened 5 years ago
But now I am doubting this again, since the database id names are different between different spectral formats, so they need to be translated...
I think this can be solved in a "hybrid" way if the deep mapping will work correctly. There might not be a need for hierarchy in the fields definitions themselves. But I would still consider an optional "parent" specification. (For my current way to specify the fields, see fields.yaml. This can change in the future)
Hi, are we aware of an "athoritative" comparison / mapping between flavours ? I was thinking about a google doc spreadsheet with corresponding field names. Did we start something like that at some stage ? Yours, Steffen
We started this back at the hackathon: https://docs.google.com/spreadsheets/d/1IGgtA6FL5lt9ajDSb0WR90qQfHtebDtcfyjX86tC_JQ/edit?usp=sharing
Hi @michaelwitting @treutler, What do you think of allowing "key-value pair" / "named-array" types in the schemas? Examples