Add sourceConceptID to Code/Terminology as optional field in JSON schema
- Add
sourceConceptID
field in JSON schema where a Code or Terminology is defined. Applies to core concepts only. - When creating DB schema, skip the
sourceConceptID
columns in core concept tables. - Filter the keys on which the
JSONPreprocessing
pre-check should be applied by removing the keys where thesourceConceptID is defined
filtered_keys_2 = []
for filtered_key in filtered_keys_1:
if filtered_key.replace('/id', '/sourceConceptID').replace('/termid', '/sourceConceptID') not in keys:
filtered_keys_2.append(filtered_key)
The pre-check is then applied only to the Code/Terminology key paths where the source concept ID is not defined, therefore speeding up the process if many of those fields are already defined in the data. More details here: https://git.dcc.sib.swiss/sphn-semantic-framework/workingfair/-/issues/514#note_75498
Should we double-check with HUG,CHUV if adding this optional field will cause issues to them? Maybe it should be brought up tomorrow in the RDF meeting? @philip.krauss