Currently CDM v5.4's CDM_SOURCE table supports a source_release_date and is described as: The date the data was extracted from the source system. In some systems that is the same as the date the ETL was run. Typically the latest even date in the source is on the source_release_date. I'd propose adding a related column, source_release_version as a varchar(40) that enables sites to store a version number for the source.
Use Case: I have source data (as of the source_release_date) which uses a versioned ETL application (cdm_etl_reference) that produces a source_release_version. I discover a data quality issue which requires an update (patch) to my ETL application. I patch my ETL application (and therefore the cdm_etl_reference) and re-run the ETL to produces a new source_release_version that is incremented accordingly.
Currently CDM v5.4's CDM_SOURCE table supports a
source_release_dateand is described as: The date the data was extracted from the source system. In some systems that is the same as the date the ETL was run. Typically the latest even date in the source is on the source_release_date. I'd propose adding a related column,source_release_versionas a varchar(40) that enables sites to store a version number for the source.Use Case: I have source data (as of the
source_release_date) which uses a versioned ETL application (cdm_etl_reference) that produces asource_release_version. I discover a data quality issue which requires an update (patch) to my ETL application. I patch my ETL application (and therefore thecdm_etl_reference) and re-run the ETL to produces a newsource_release_versionthat is incremented accordingly.