Strategic Intent

Dataset Versioning

Perhaps it's there and I don't see it, but it would seem that some kind of automated versioning system needs to be in place. My concern, from a transparency standpoint, would be if there is the capability to overwrite an existing dataset. Even if it is well intentioned, if the original dataset is not preserved, questions could arise as to what has been changed/added/removed.

This could also help with datasets that change over time. Rather than having numerous "Year 200x" versions, an automated version system could handle this much cleaner.


Submitted by

Stage: Active

Feedback Score

28 votes

Idea Details

Vote Activity (latest 20 votes)

  1. Upvoted
  2. Upvoted
  3. Upvoted
  4. Upvoted
  5. Upvoted
  6. Upvoted
  7. Upvoted
  8. Upvoted
  9. Upvoted
  10. Upvoted
  11. Upvoted
  12. Upvoted
  13. Upvoted
  14. Upvoted
  15. Upvoted
  16. Upvoted
  17. Upvoted
  18. Upvoted
  19. Upvoted
  20. Upvoted
(latest 20 votes)

Similar Ideas [ 4 ]


  1. Comment

    If I read correctly: Agreed. A history of some sort for each particular. This would be a protection from future abuse (or mistakes, as suggested), which should be an important thing to factor in, given term limits and the natural progression of time. Future generations might be aided greatly by a bit of this foresight.

  2. Comment

    Is data supposed to be preserved under federal law for archiving purposes? Does this serve to preserve versions per this suggestion?

Add your comment

Your comment will be published after it's approved by the moderators.