Open GenieTim opened 5 years ago
This is a test comment
dazu sagen wir nicht nein ;)
There are multiple ways to achieve this, of various difficulty and sensibility. The first distinction to make is:
The first idea might be annoying if all you want to do is check, open or look at the specimen. Additionally, technologically, it is much more difficult as it either needs a pessimistic lock on the database entry (with the additional disadvantage that this lock needs to be released; how to do that if the app crashes etc.) or some form of network communication between the DataShot instances, which in turn is not the safe choice in terms of security. Additional questions would arise, what to do e.g. when a user goes to eat lunch with a specimen still open.
The third approach is easier. But it also brings new questions:
a. should the changes of the first one to press save be successful and the others gets an error message and need to restart editing?
b. should the changes of the first one to press save be successful and the others be informed of the changes in order to overwrite, merge or cancel their changes?
I understand the concerns and we think we close this issue for now. We will coordinate on who is doing which species and we think this should solve the problem for now.
Prevent multiple people to work on the same file.