You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may be a bit too specific to our use case, but declaring the base model could help to infer some things. For example, the PEDSnet data model is based on OMOP so we could rely on that for implicit mappings and add a file type to declare the diff from the base model (rather than redefining all the fields).
The text was updated successfully, but these errors were encountered:
I generally agree with this. A more practical application would be to create a tool that copies an existing data model, increments the version across all the files and sets up the default mappings. For example, if you did data-models derive pedsnet/v1 omop/v4 it would copy all the files in omop/v4 and replace all the instances of model and version with pedsnet and v1 and add additional mappings between omop/v4 and pedsnet/v1.
This may be a bit too specific to our use case, but declaring the base model could help to infer some things. For example, the PEDSnet data model is based on OMOP so we could rely on that for implicit mappings and add a file type to declare the diff from the base model (rather than redefining all the fields).
The text was updated successfully, but these errors were encountered: