Page MenuHomePhorge

Listing active collaborative editing sessions
Closed, ResolvedPublic

Description

Roles

Eva: A system administrator at Acme Corp with extensive experience with Kolab Enterprise
Susy: A project manager at Acme Corp
Robert: Knowledge worker at Acme Corp, works part time from home, is a member of Susy's team

UserStory

Susy wants to see which of her team members are working on which documents.
She opens Roundcube Files and scrolls to the bottom of the folder listing and clicks on the "Editing Sessions" folder.
A list of all files she has rights to which are in an editing session is shown. She can see who is in each session and join a session by clicking on the file.

Details

Ticket Type
Story

Event Timeline

petersen raised the priority of this task from to 40.
petersen updated the task description. (Show Details)
petersen added a project: Manticore.
petersen changed the visibility from "Public (No Login Required)" to "All Users".
petersen changed Ticket Type from Task to Story.
petersen added subscribers: petersen, vanmeeuwen.

This could possibly be improved upon by suggestions raised in T725#10210 as well as T727#10213.

I believe the real estate needed does not need to be placed in such way, scrolling down to the bottom of a page (and/or requiring a click) is necessary at all, if "currently ongoing sessions you're authorized to participate in" can be a line-item virtual folder not unlike we have "Documents", "Videos" and others today, perhaps including the collapsible tree listing already committed to the kolab_files plugin in Roundcube Kolab Plugins as per T161#9317.

petersen changed the visibility from "All Users" to "Public (No Login Required)".Sep 8 2015, 7:38 AM

It is suggested two separate UI elements be used for indicating ongoing sessions:

  1. A list of ongoing sessions, including:
    • to which the user has access, either because the user created the session or the user has been invited to the session,
    • to which the user is considered eligible to request authorization to participate in the ongoing session by already having write access to the file being edited.
  2. An indicative icon or UI element to those files among a larger list of files, in the browsing interface, for which a collaborative editing session exists.

@vincent,

Users may also find it useful, to have an indication on files currently being edited, to which they have read-only access (such as your proverbial company-wide communique at shared/memo/communique.odt), so that they might postpone reading and/or downloading a copy of the document (since it is being edited). Any thoughts?

Just my two cents: Is providing a separate document list important? Why not simply use Manticore to view this list?

I think the idea is to keep the file navigation and status in the Kolab environment. So if no documents are open, you can view the editing status or last edited status etc... without opening the editor. Manticore was going to provide the editing part of the functionality/session only. This solution will provide an easier UX and keep the user in a familiar UI @vanmeeuwen is that correct? My visuals will support that approach... Arriving soon ;)

machniak subscribed.
  1. A list of ongoing sessions, including:
    • to which the user is considered eligible to request authorization to participate in the ongoing session by already having write access to the file being edited.

User can already see sessions in read-only folders (and request to join them). So, wouldn't be reasonable to list here ongoing sessions also on read-only files?

Implemented in git-master of chwala, roundcubemail-plugins-kolab and roundcubemail-skin-chameleon repos.