Whenever a public, non-private, non-draft dataset is deleted, this should increment a counter somewhere, such that people know something has changed (hook in dataset_delete and/or purge). This is interesting for e.g. database dumps to json.
Not going to happen, because the effort does not justify the means (some versed user knows something changed). It's not even a canary that can tell what changed.
Whenever a public, non-private, non-draft dataset is deleted, this should increment a counter somewhere, such that people know something has changed (hook in dataset_delete and/or purge). This is interesting for e.g. database dumps to json.