grouper-dev - [grouper-dev] RE: additional columns on member table
Subject: Grouper Developers Forum
List archive
- From: Chris Hyzer <>
- To: Shilen Patel <>, "" <>
- Subject: [grouper-dev] RE: additional columns on member table
- Date: Sun, 13 Mar 2011 18:12:55 -0400
- Accept-language: en-US
- Acceptlanguage: en-US
Well, just remember it will a drop down per source, sounds like a kind of
confusing UI. If there is a hierarchy of privacy where the more private has
the more info, then I think it would be rare that you would want to bump down
to the less private = less information, right? :) (hopeful suggestion to
simplify things?)
Thanks,
Chris
-----Original Message-----
From: Shilen Patel
[mailto:]
Sent: Sunday, March 13, 2011 12:48 PM
To: Chris Hyzer;
Subject: RE: additional columns on member table
Restricting based on groups sounds good to me. Though I wonder if we should
allow users to sort / search using multiple attributes. For instance, the UI
can have two drop down lists where the user can select what to sort and
search on.
Then maybe have config options for the groups (default to wheel only).
jdbc.sortCol0.allowOnlyGroup = stem:all_employees
jdbc.sortCol1.allowOnlyGroup = stem:all_employees
jdbc.sortCol2.allowOnlyGroup = stem:all_employees
...
jdbc.searchCol0.allowOnlyGroup = stem:all_employees
jdbc.searchCol1.allowOnlyGroup = stem:all_employees
jdbc.searchCol2.allowOnlyGroup = stem:all_employees
...
Thanks!
-- Shilen
________________________________________
From:
[]
On Behalf Of Chris Hyzer
[]
Sent: Saturday, March 12, 2011 10:57 PM
To:
Subject: [grouper-dev] additional columns on member table
Just curious, Shilen / Jim, or anyone else, have we established how will
these be used.
Ie. there are multiple sort cols, and multiple search cols. 5 of each.
When a user is using the UI, how do we know which one to use for each source?
i.e. do we check to see if the user is in a certain group, and if so, then
use sortCol0/searchCol0. If not, then if they are in a certain other group,
then use sortCol1/searchCol1. And if not, then the default is
sortCol2/searchCol2 (the last one, most public one). So basically each
source will have N options, and N-1 ordered groups to check to see which one
to use.
Just curious, do we have a wiki page yet?
Thoughts?
Thanks,
Chris
- [grouper-dev] additional columns on member table, Chris Hyzer, 03/12/2011
- [grouper-dev] RE: additional columns on member table, Shilen Patel, 03/13/2011
- [grouper-dev] RE: additional columns on member table, Chris Hyzer, 03/13/2011
- [grouper-dev] RE: additional columns on member table, Chris Hyzer, 03/15/2011
- [grouper-dev] RE: additional columns on member table, Shilen Patel, 03/13/2011
Archive powered by MHonArc 2.6.16.