Page MenuHomePhorge

UX Design for Collaborative Document Editing
Open, NormalPublic


Provided the server-side implementation (T505, T506, T507) and the client-side implementation of a generic collaborative editing framework, questions arise about the functionality and behavior required/desired, that have more to do with the integration in to Kolab (or any other application suite) and the human experience of such integration.

For example, should a Kolab user log in to Manticore, then documents available for editing (those to which the user has write access) would be limited to documents residing in (IMAP) folders to which the Kolab user has access -- it may (or may not) be expected to provide a view on documents that cannot themselves be written to, but could be created a working copy of.

Similarly, provided restrictions to a "session" (the having opened a document for editing), the authorization to participate in the session could be assigned on the basis of an individual user or a group of users. The user that creates the session may alter the Access Control List, but would not necessarily expect that action to give out write access to the document as such -- the document is a single file in a folder, and access control is managed based on folders, not files.

The user would probably also not expect the entries available for Access Control to the session to be limited to those users or groups that already have access to write to the document being edited in the session.

A user might also be "invited" to participate in a session, meaning that the initial login (authentication) could need to lead the user to existing "sessions" in which the user is allowed to participate.

There's probably more questions and considerations to make, but I hope this spawns off a good thread on these subjects.


Ticket Type

Event Timeline

vanmeeuwen assigned this task to vincent.
vanmeeuwen raised the priority of this task from to 60.
vanmeeuwen updated the task description. (Show Details)
vanmeeuwen changed Ticket Type from Task to Epic.
vanmeeuwen added subscribers: vanmeeuwen, grote, Adityab.

@vincent At the moment, we don't have a great way to get WebDAV information about whether a user has read/write/delete permissions on a document.

So I'll need some UX ideas on how the main documents list should look like (with options to manipulate those documents).

But the absence of that info shouldn't be a huge deal for collaborative editing: as long as one can read a document, it can be opened in the collaborative editor and edited together. We could make it thus that only the original "author" can "save" it back to the WebDAV directory (my view, please let me know what you think!)

What I need from you are ideas on how a document can be shared with other users - either those with an account or guests, and whether adding users to a document will change WebDAV permissions.


vanmeeuwen lowered the priority of this task from 60 to Normal.Mar 28 2019, 8:13 AM