MaximMoinat
commented
3 years ago This might be related to issue #272
And agreed, the whole mapping specification in RiaH should allow more complicated logic.
Some other things I was thinking about:
- use column for filtering (maybe in the same way you are suggesting, having a 'null/filter' box)
- many to one table/field mappings (with some intermediate box where you draw in multiple source fields, define how they are combined and map to the resulting column)
- one to many of the same table mapping. Sometimes multiple variables from one source table e.g. have to map to the observation table. Currently this becomes a mess.
- ...
The question is; do we want to keep putting effort in the current RiaH or develop something anew with modern frameworks?
It would be useful to be able to give logic to a CDM column even when there is no raw table column mapping to it.
For example, the TYPE Field usually will not have a raw column mapping to it, but depending on the table might depend on what type CONCEPT_ID I use. It would be good to add logic just for that RAW table --> CDM table mapping. Right now you can only add a comment and that applies to all mappings to that CDM table.
If I were to imaging a way to do it, I would add one more Raw column that is "empty", "no column", or "null" and then use that to draw a line from it to the CDM column of interest. That would allow me to add logic in a similar fashion to all the other mappings. But don't really care how it is implemented.