Changes between Version 8 and Version 9 of ConceptLocks


Ignore:
Timestamp:
04/07/09 11:52:32 (16 years ago)
Author:
rostanin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ConceptLocks

    v8 v9  
    1616   1. One is allowed to add relations to a concept locked by another user 
    1717   1. One is allowed to edit an unlocked concept that is in a CM locked by another user 
    18    1. If a concept in a CM was changed by another source (e.g. in a infoItems cockpit or VV) 
    19       1. User has to get a signs that concepts were changed 
    20          1. e.g. some symbol displayed as a concept icon 
    21          1. If user opens such a concept it has to be refreshed from the server 
    22          1. Flex-application should send "refresh"-requests periodically to get informed about changed concepts 
    23    1. All read-only CMs should get a flag "dirty" if the editing user saved/closed it 
    24          1. e.g. some symbol displayed 
    25          1. User can refresh the CM contents from the server 
    26          1. User can request a CM lock if the editing user closed the CM 
    27          1. Flex-application should send "refresh"-requests periodically to get informed about changed CMs 
    2818   1. If a concept map is closed, CM locks must be removed 
    2919      1. If the application is closed, all user's CM and concept locks must be removed 
    … …  
    3727   1. If a new concept is created within a locked CM it is added to the server-side model and individual search index but not saved persistantly 
    3828   1. If a new concept is created withing other editing points it is added to the server-side model, common search index and saved persistantly 
     29   1. If a concept in a CM was changed by another source (e.g. in a infoItems cockpit or VV) 
     30      1. User has to get a signs that concepts were changed 
     31         1. e.g. some symbol displayed as a concept icon 
     32         1. If user opens such a concept it has to be refreshed from the server 
     33         1. Flex-application should send "refresh"-requests periodically to get informed about changed concepts 
    3934 
     35== Saving CMs == 
     36 
     37   1. All read-only CMs should get a flag "dirty" if the editing user saved/closed it 
     38         1. e.g. some symbol displayed 
     39         1. User can refresh the CM contents from the server 
     40         1. User can request a CM lock if the editing user closed the CM 
     41         1. Flex-application should send "refresh"-requests periodically to get informed about changed CMs 
     42   1. If the user closed a CM without saving, the server-side model has to be reverted