Task #11498 (new)
Opened 11 years ago
Last modified 8 years ago
Review: Multi-group view in Web
| Reported by: | wmoore | Owned by: | atarkowska |
|---|---|---|---|
| Priority: | major | Milestone: | GatherReqs |
| Component: | Web | Version: | 4.4.8 |
| Keywords: | n.a. | Cc: | ux@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description (last modified by atarkowska)
In order to assess the priority of adding multi-group support in web (in order to bring it into line with Insight) we need to have an idea about how much work this would be.
- UI changes (see latest proposal for Insight)
- request.session.get('active_group') in @login_required(setGroupContext = True) is currently used to assign current group context to a number of requests. Alternative methods for these?
- @login_required(setGroupContext = True) Changing this is a 'API change' for other web apps.
- Support for multiple users per group?
- Support for different scope per group? All users / specified users / just Me
https://drive.google.com/?authuser=0#folders/0B0o63qHVjgTQUy1KT3Z2NzVmdEk
Change History (12)
comment:1 Changed 11 years ago by jburel
- Cc ux@… added; atarkowska jburel removed
- Milestone changed from Unscheduled to 5.0.0-beta2
- Owner changed from wmoore to atarkowska
comment:2 Changed 11 years ago by atarkowska
In order to support multiple group display, client needs to maintain multiple omero sessions. From the code I see only one place where multiple connection could be stored
request.session['connector']
At the moment connector is nothing else then omero.gateway.BlitzGateway?. It could be changed to the dictionary of multiple connections identified by the group ID. That should give easy access to the right connector and replace active_group parameter.
comment:3 Changed 10 years ago by jburel
- Milestone changed from 5.0.0-beta2 to 5.0.0-beta3
discussion during Client meeting 14/11/13
*Ola to evaluate for testing addition of multiple users to tree
Pushing to next milestone, priority given to bugs
comment:4 Changed 10 years ago by atarkowska
- Description modified (diff)
comment:5 Changed 9 years ago by atarkowska
- Milestone changed from 5.1.2 to 5.1.4
comment:6 Changed 9 years ago by jburel
- Milestone changed from 5.1.4 to 5.2.0
Nothing will happen in 5.1.4, jstree work needs to be completed first.
Pushing to 5.2
comment:7 Changed 9 years ago by jamoore
- Milestone changed from 5.2.0 to OMERO-5.2.0
Splitting due to milestone decoupling.
comment:8 Changed 8 years ago by jburel
- Milestone changed from OMERO-5.2.1 to OMERO-5.2.2
Milestone OMERO-5.2.1 deleted
comment:9 Changed 8 years ago by jburel
- Milestone changed from OMERO-5.2.2 to OMERO-5.2.1
Milestone OMERO-5.2.2 deleted
comment:10 Changed 8 years ago by jamoore
Referencing ticket #9287 has changed sprint.
comment:11 Changed 8 years ago by jamoore
Referencing ticket #9287 has changed sprint.
comment:12 Changed 8 years ago by jburel
- Milestone changed from OMERO-5.2.2 to GatherReqs
Initial investigation by Ola