Changes between Version 118 and Version 119 of ReleaseNotes


Ignore:
Timestamp:
04.02.2015 00:50:29 (6 years ago)
Author:
jri
Comment:

4.5 release notes, revision 1

Legend:

Unmodified
Added
Removed
Modified
  • ReleaseNotes

    v118 v119  
    77== 2015-02-?: DeepaMehta 4.5 == 
    88 
    9 !DeepaMehta 4.5 is a major release that features a redesigned **Access Control** system that underlies DeepaMehta's sharing functionality. Sharing is governed by ''Workspaces'' which connect users to content. 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". For the first time a !DeepaMehta installation can hold private and shared data at the same time. 
    10  
    11 The new access control concepts are described in this posting: 
     94.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**. 
     10 
     11The **Access Control** system of !DeepaMehta 4.5 is completely redesigned. Its basic points are described in this posting:\\ 
    1212http://lists.deepamehta.de/pipermail/devel-lists.deepamehta.de/2014-December/000562.html\\ 
    13 Further details are described here: 
     13Further details are described here:\\ 
    1414http://lists.deepamehta.de/pipermail/devel-lists.deepamehta.de/2015-January/000570.html 
    1515 
    1616For plugin developers the highlight feature of !DeepaMehta 4.5 is **Service injection for migrations**. This supports the development of upgradable plugins. 
    1717 
    18 You 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]]. 3rd-party plugins compatible with !DeepaMehta 4.4 might be required to be adapted in order to work in DeepaMehta 4.5. 
     18You 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]]. 
     19 
     203rd-party plugins compatible with !DeepaMehta 4.4 might be required to be adapted in order to work with DeepaMehta 4.5. 
    1921 
    2022New features: 
    21 * **Redesigned Access Control** (#592). 
    22     * User configurable access realms by the means of ''Workspace Sharing Modes''. 
    23     * The Webclient GUI presents workspaces as well-defined spaces between the user can switch. 
    24     * True private sphere. 
    25 * 2 new context menu commands 
    26     * "Assign to Workspace": allows the user to assign a topic/association to another workspace and thus changing its accessibility (#592). 
    27     * "Get Info": shows creator/modifier/owner info and timestamps for a topic or association (#747, #749). 
     23* 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. 
     26* 2 new commands in the topic/association context menu: 
     27    * "Assign to Workspace": let the user assign a topic/association to another workspace and thus changing its accessibility (#592). 
     28    * "Get Info": shows creator/modifier/owner info and timestamps for a topic/association (#747, #749). 
    2829 
    2930Plugin Development Framework: 
    30 * **Service injection for migrations** (#324). 
    31 * Core API provides a generic `getObject(id)` method (#760). 
     31* **Service injection for migrations**: in your plugin's migrations you have access to the services provided by other plugins, including your own (#324). 
     32* Core module: 
     33    * The `postInstall()` hook is dropped. You can do the same with a migration now (#324). 
     34    * The Core API provides a generic `getObject(id)` method (#760). 
    3235* Workspaces module: 
    3336    * The automatic workspace assignment for things created can be switched off on a per-request basis (#752). 
    3437    * The Workspaces API is RESTful (#592). 
    35 * Webclient GUIToolkit: items rendered by `topic_menu()` can be disabled by the means of an indicator function (#755). 
    36 * Client-side Access Control events (#592): 
     38* Access Control module: changes in client-side events (#592): 
    3739    * The `logged_in` and `logged_out` events are replaced by `authority_increased` and `authority_decreased` with extended semantics. 
    3840    * 2 ''logout levels'' (in shape of the `authority_decreased` and `authority_decreased_2` events) allow plugin's to orchestrate their logout actions.  
    39 * The server-side `postInstall()` hook is dropped. You can do the same with a migration now (#324). 
     41* Webclient module: certain items rendered by GUIToolkit's `topic_menu()` can be disabled by the means of an indicator function (#755). 
    4042 
    4143Changes: 
     
    4446 
    4547Bug fixes: 
    46 * The ''Create Association'' operation is only available if the user has the corresponding permission (#592). 
     48* The "Create Association" operation is only available if the user has the corresponding permission (#592). 
    4749 
    4850----