Concept locks

Types of locking situations

1. Concept map is locked
2. Concept map is read only
3. Concept map is locked, but concept to edit is a part of a CM locked by another user
4. Concept is viewed in the Vertex viewer
5. Concept is edited in InfoItems cockpit

Lock policies

1. One is not allowed to edit concepts in a read only CM (only view properties)
2. One is not allowed to save a CM/change CM properties for a read only CM
3. One is not allowed to edit concept properties if the concept is locked by another user (or the same user has open 2 edit dialogs for the same concept in different CMs)
4. One is allowed to add relations to a concept locked by another user
5. One is allowed to edit an unlocked concept that is in a CM locked by another user
6. If a concept in a CM was changed by another source (e.g. in a infoItems cockpit or VV)
   1. User has to get a signs that concepts were changed
      1. e.g. some symbol displayed as a concept icon
      2. If user opens such a concept it has to be refreshed from the server
      3. Flex-application should send "refresh"-requests periodically to get informed about changed concepts
7. All read-only CMs should get a flag "dirty" if the editing user saved/closed it
   1. e.g. some symbol displayed
   2. User can refresh the CM contents from the server
   3. User can request a CM lock if the editing user closed the CM
   4. Flex-application should send "refresh"-requests periodically to get informed about changed CMs
8. If a concept map is closed, CM locks must be removed
   1. If the application is closed, all user's CM and concept locks must be removed
      1. What to do if the the browser crashed?

Saving concepts/CMs

Saving concepts