Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

User Story #11753 (closed)

Opened 8 years ago

Closed 6 years ago

read-write in clients

Reported by: jburel Owned by:
Priority: critical Milestone: 5.1.2
Component: Client Keywords: n.a.
Cc: ux@…, jamoore, sbesson, java@…, python@… Story Points: n.a.
Sprint: n.a. Importance: n.a.
Total Remaining Time: n.a. Estimated Remaining Time: n.a.

Description (last modified by bpindelski)

Overarching ticket for tasks required to enable read-write group support in the client.

The read-write state (rwrw--) is available as a server option but has been kept out of the clients due to the complexity that it adds. In order to make the flag available across the board, we will need to:

  1. review the existing integration tests in Java & Python
    • include specific classes for: images, containers, rendering, annotations, ...
    • effort should be made to reduce variability in class/method naming, etc.
  2. likely write new integration tests to cover rwrw--
  3. ensure coverage of client-side API methods (canEdit(), canAnnotate(), ...) for the various user types (data-owner, group-member, group-owner, admin)
  4. evaluate needed changes to client-side API methods (client devs: Will/J-m/...)
    • Do we need canInsert()?
  5. update the spreadsheet(s) that are being maintained (client devs + Petr/Balaji?)
    • possibly simplifying them
    • possibly generating integration tests from them
    • possibly converting to a more maintainable format)
    • If this is out of scope, we may want to start by creating a new format just for rwrw-- and then extend this backwards to rwra-- etc.

A primary goal of the above would be to have the following representations/implementations of permissions all coincide minimally for rwrw--:

  • client (i.e. user) functions (GUI)
  • client gateway methods
  • client-side API methods (canEdit, etc)
  • low-level permissions object (e.g. rwrw--)
  • server-implementation
  • integration tests
  • and finally the "Spreadsheets" (i.e. permissions documentation)

If possible, no client/server breaking changes should be made so that the work could be backported to the 5.0 series if desired.

Change History (7)

comment:1 Changed 8 years ago by jburel

see also #9286

comment:2 Changed 8 years ago by jamoore

  • Cc jamoore sbesson java@… added
  • Description modified (diff)
  • Priority changed from major to critical

Starting to fill out this ticket, since it is linked from the "upcoming features" board. Individual tasks remain to be created.

comment:3 Changed 8 years ago by jamoore

  • Cc python@… added
  • Description modified (diff)

comment:4 Changed 8 years ago by bpindelski

  • Description modified (diff)

comment:5 Changed 7 years ago by jamoore

  • Milestone changed from 5.1.0 to 5.1.1

comment:6 Changed 7 years ago by jburel

  • Milestone changed from 5.1.1 to 5.1.2

comment:7 Changed 6 years ago by jamoore

  • Resolution set to fixed
  • Status changed from new to closed

I'm marking this as done. (If only to see the smile on Gus' face!)

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.180946 sec.)

We're Hiring!