Open cicdguy opened 3 years ago
Do we know what we need here? If not then we probably need some discussion label here.
Is this what you are looking for:
Provenance:
Creator: pawelru
@pawelru yes, but I'm thinking weather it should be a in:
Provenance:
Creator: gogonzo
For me (left) data extract panel is only about input specification. It's already too much there so I wouldn't put a new item in there. But let's discuss it.
Moreover, there are modules that has more than one analysis dataset (thus: how to name them? would it be clear for the end-user?). There are modules that has no analysis dataset per se (see missing data module). This should be also taken into account.
Provenance:
Creator: pawelru
I see both sides of the discussion here. On one hand, it's confusing, on the other hand, we already provide the code for the joins, so it should be clear what teal does.
Provenance:
Creator: kpagacz
We use to call
data_merge_module
in the server but it doesn't return any information to ui. We might need to present ANL details in the encoding panel.The reason for this is that
left_join
,full_join
causes some confusion. Reportedly it's not clear what is the output of used datasets - even if we havedatasets: ADSL, ADLB, ...
in the encoding panel and datasets sizes in the flter panel - it's still vague what is the result of these joins.merge_ui
(or other name) can be put (optionaly) in the ui and can receive some information from the module.Provenance: