3 ms·
Thank you. Can you please elaborate? I think your question will help me think this through again. I came to the file versioning conclusion after speaking to a
by babyent 2y ago
Thank you. Can you please elaborate? I think your question will help me think this through again.
I came to the file versioning conclusion after speaking to a few folks in this space who I want to help.
The common issues that kept coming up are around organization and accountability. In existing systems like Finder/File Explorer (and G Drive, One Drive, other cloud storage) we are prompted to Keep/Replace files. In some existing SaaS these folks use, it has neither versioning nor keep/replace prompts. It just uploads the same file name again and confuses users.
When users upload a new version of a file, with some new changes, people often rename arbitrarily, or accidentally replace, and it is hard to enforce process.
Using versioning will help them stay organized (tidier workspace), show them what changes and who made them, and finally help them trace back if need be.
These are files dealing with designs, permits, drafts, etc. Mostly PDFs, but sometimes doc or excel files as well.
- pestatije 2y agoright, i am talking about versioning systems like git...text files diffing comes included by default and pdfs, docs, etc might have a way to be dealt with as well