What inspired this wish list request?
We have seen many instances where a JMP data table on a shared location has been opened by a user A and then by another user B (while it is still opened by A). Then both users modify the data table and want to save their changes. However, given that only user A has full read and write rights, user B will not be able to save his/her changes in the same data table and will recognize this issue only when trying to save the data table. Consequently, either all changes of B are getting lost (undesirable) or B changes his/her modified version as a new data table and needs to merge the A-modified and B-modified data table afterwards. Also this latter option is error prone, time consuming and undesirable.
What is the improvement you would like to see?
We do currently see two options with different complexities:
(a) Simpler option: When opening the respective data table, each user gets informed if the table is already in use by another person and thus knows if/that they only have read but no write rights at this point in time. Ideally, in case the data table is already utilized by another user (say A), then user B gets informed which user is currently ‘blocking’ the data table.
(b) Advanced option: Similar to documents in the MS Office environment, a multi-user interaction on the same document without any interference/issues would be most desirable.
Why is this idea important?
This feature is helpful to all JMP users who work collaboratively on shared JMP data tables and thus run from time to time into the issues described above. Ultimately, it enables ‘true’ collaboration on JMP data tables and a vivid exchange of ideas, analyses, etc. that are all hosted within the same JMP data table as well as reduces frustration when trying to do so by e.g. removing the need to merge data table versions manually as well as data loss.
@martindemel