Ideally, I would suggest that we add the following variables to the data dictionary (field type = 'text') and clearly state in the field label something like 'Assumes the ISARIC DAG naming convention. Please do not delete this variable unless you are following a different DAG naming convention'.
isaric_dag_site (field annotation = @HIDDEN @CALCTEXT(mid([record-dag-label], 11, 1000)))isaric_dag_country_iso3 (field annotation = @HIDDEN @CALCTEXT(mid([record-dag-label], 7, 3)))
If we choose not to do this, then it would be extremely useful for downstream pipelines to include the following variable to the data dictionary (field type = 'text')
isaric_dag_name (field annotation = @HIDDEN @CALCTEXT([record-dag-label]))
Also add field annotations to hide demog_calcage_days (which should be renamed in ARC from demog_calcage)
Ideally, I would suggest that we add the following variables to the data dictionary (field type = 'text') and clearly state in the field label something like 'Assumes the ISARIC DAG naming convention. Please do not delete this variable unless you are following a different DAG naming convention'.
isaric_dag_site(field annotation =@HIDDEN @CALCTEXT(mid([record-dag-label], 11, 1000)))isaric_dag_country_iso3(field annotation =@HIDDEN @CALCTEXT(mid([record-dag-label], 7, 3)))If we choose not to do this, then it would be extremely useful for downstream pipelines to include the following variable to the data dictionary (field type = 'text')
isaric_dag_name(field annotation =@HIDDEN @CALCTEXT([record-dag-label]))Also add field annotations to hide
demog_calcage_days(which should be renamed in ARC fromdemog_calcage)