Changes between Version 119 and Version 120 of ReleaseNotes


Ignore:
Timestamp:
04.02.2015 01:38:07 (6 years ago)
Author:
jri
Comment:

4.5 release notes, revision 2

Legend:

Unmodified
Added
Removed
Modified
  • ReleaseNotes

    v119 v120  
    55---- 
    66 
    7 == 2015-02-?: DeepaMehta 4.5 == 
     7== 2015-02-04: DeepaMehta 4.5 == 
    88 
    994.5 is a major release that brings !DeepaMehta's basis for **Collaboration** to the next level. For the first time the user can control the access to shared workspaces purposefully. For shared workspaces several access levels are supported, ranging from "completely closed" to "completely open". The access levels are enforced by the !DeepaMehta backend, so that confidential content is never exposed to unauthorized users. For the first time !DeepaMehta supports **Privacy**. 
    1010 
    11 The **Access Control** system of !DeepaMehta 4.5 is completely redesigned. Its basic points are described in this posting:\\ 
     11The **Access Control** system of !DeepaMehta 4.5 is completely redesigned. The basic points are described in this posting:\\ 
    1212http://lists.deepamehta.de/pipermail/devel-lists.deepamehta.de/2014-December/000562.html\\ 
    1313Further details are described here:\\ 
     
    1818You can upgrade any !DeepaMehta 4 standard installation which is not older than !DeepaMehta 4.1. For installation and update instructions see the [[https://github.com/jri/deepamehta#readme|README]]. 
    1919 
    20 3rd-party plugins compatible with !DeepaMehta 4.4 might be required to be adapted in order to work with DeepaMehta 4.5. 
     203rd-party plugins compatible with !DeepaMehta 4.4.x might be required to be adapted by the respective developers in order to work with DeepaMehta 4.5. 
    2121 
    2222New features: 
    2323* Completely redesigned **Access Control** system (#592): 
    24     * User configurable access levels by the means of ''Workspace Sharing Modes''. A **''Workspace Sharing Mode''** lets the user control how (if at all) the workspace content is accessible by others. To accommodate typical sharing scenarios 5 sharing modes are pre-defined: "Private", "Confidential", "Collaborative", "Public", and "Common". A matrix explaining the 5 sharing modes is available in ticket:592#comment:1 
    25     * The **Webclient GUI** presents workspaces as well-defined content spaces between the user can switch. The Workspaces menu lists only the workspaces the user has access to. The Topicmaps menu lists only the topicmaps that belong to the selected workspace. Topicmaps still can contain (interrelated) contents belonging to different workspaces. What parts of the topicmap are visible/accessible depends on the user's authority. 
     24    * User configurable access levels by the means of ''Workspace Sharing Modes''. A **''Workspace Sharing Mode''** lets the user control how (if at all) the workspace content is accessible by other users. To accommodate typical sharing scenarios 5 sharing modes are pre-defined: "Private", "Confidential", "Collaborative", "Public", and "Common". A matrix explaining the 5 sharing modes is available in ticket:592#comment:1 
     25    * The **Webclient GUI** presents workspaces as well-defined content spaces between the user can switch. The Workspaces menu lists only the workspaces the user has access to. The Topicmaps menu lists only the topicmaps that belong to the selected workspace. Topicmaps can still contain (interrelated) contents belonging to different workspaces. Which parts of the topicmap are visible/accessible to the user depends on the user's authority. 
    2626* 2 new commands in the topic/association context menu: 
    2727    * "Assign to Workspace": let the user assign a topic/association to another workspace and thus changing its accessibility (#592). 
     
    3434    * The Core API provides a generic `getObject(id)` method (#760). 
    3535* Workspaces module: 
    36     * The automatic workspace assignment for things created can be switched off on a per-request basis (#752). 
     36    * The automatic workspace assignment can be switched off on a per-request basis (#752). 
    3737    * The Workspaces API is RESTful (#592). 
    3838* Access Control module: changes in client-side events (#592):