Having versions of a file is a great helper, especially in a collaborative environment. However, we lost some files because the file history was overwritten when the file was overwritten.
Consider this use case (as happened to us a couple of times):
- User A creates local FILE, which is synced to NC. He keeps working on FILE and the sync client keeps syncing so that eventually FILE is available in versions 1 through N on the server.
- User B, who also syncs FILE overwrites his local copy with a different file. The overwritten FILE gets synced to NC, thereby removing the current and all previous versions of FILE.
- A tries to go back to a previous version of his work but finds all versions deleted.
The same thing seems to happen when overwriting FILE through a web interface upload. Oh, and user A can cause the problem all by himself, too.
IMO it would be more logical to save a file that overwrites another as another version of the original file. Is there something I missed here?