What inspired this wish list request?
When (collaboratively) working on data analysis, models, reports, etc., keeping track of all the changes is often troublesome. We are all familiar with sending files via email, discussing via various chat channels which dataset is the latest, naming files or scripts with names like *_model1, *_model2, *_model2updated, etc. It often ends with a big mess, especially after you or your colleague continues working on the project after couple of years.
What is the improvement you would like to see?
Recently, I came across the Data Version Control (DVC) system, which is a sort of git-like system to organize data and models. I was wondering if something like that could also be implemented in JMP, perhaps in a similar fashion? Or perhaps more focused on "Script Version Control"? Since DVC supports remote storage types, such as Amazon S3, NFS, SSH, etc., it could probably be easily implemented in JMP, in a similar way as it is implemented in a VS Code environment (like git)
Why is this idea important?
To have more cleaned and systematic workflow of your data analysis. And to more easily share and communicate changes that you or your colleagues have made at various steps of data analysis.