Update Vocabulary Latest UPDATE on every change in vocabulary

[acumarav]

Vocabulary's Latest Update should change on every change in vocabulary, source and target

[acumarav]

As per discussion with @Alexdavv - the field reflects changes in the source vocabulary and it's behavior should not be changed. The optimal change will be to add one more field which will be reflecting both source and output changes. After that Vocabularies update email notifications functionality can be switch to that new field

[mik-ohdsi]

During the release process, hand over the latest update date instead of the source release date to the vocabulary_conversion table and repurpose the latest_update field. This would also cover relationship updates including "to or from" changes for the respective vocabulary (which are very frequent). Create a new field “source_version_date” and a respective column that would receive the date currently present in the latest_update field. (is it possible to get little information flyouts / hover tooltips to explain the purpose of the respective column?)

[Alexdavv]

@mik-ohdsi @cgreich What about the changes in ancestry? Let’s discuss it also.

[cgreich]

Good point. Yes, they should trigger an OHDSI release as well to all vocabularies that are touched by a change. Which means, that ATC will get a time stamp if something changes in RxNorm, even though that change does not affect any ATC concept or any relationship of an ATC concept. Thoughts?