Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need to be able to define table joins explicitly #214

Open
ASL-rmarshall opened this issue Oct 16, 2023 · 1 comment
Open

Need to be able to define table joins explicitly #214

ASL-rmarshall opened this issue Oct 16, 2023 · 1 comment

Comments

@ASL-rmarshall
Copy link
Collaborator

Some analyses require reference to more than one input dataset (e.g., analysis of incidence of adverse events needs the full set of subjects from ADSL and, for example, the distinct list of SOC/PT combinations from ADAE). Although it is often possible to interpret the needs for a table join from the currently-defined metadata, it would be better to have metadata to explicitly identify required input datasets and to define the join conditions.

@AnalysisMate
Copy link

In regards to this scenario, Will there be impact to AnalysisSet as condition need to be applied to ADSL and ADAE both ? and Currently, AnalysisSet definition only allows to specify one dataset (i.e. condition_dataset)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants