comanage-dev - Re: [comanage-dev] some LIGO data
Subject: COmanage Developers List
List archive
- From: Benn Oshrin <>
- To:
- Subject: Re: [comanage-dev] some LIGO data
- Date: Sun, 03 Mar 2013 08:01:47 -0500
- Authentication-results: sfpop-ironport04.merit.edu; dkim=neutral (message not signed) header.i=none
There are already CO-209, CO-497, and CO-139 (which is linked to CO-312). We can add this to the dev and sprint planning agenda. Some thought needs to go into what the search box actually does, and the backend call(s) needed to support it.
-Benn-
On 3/2/13 10:53 PM, Marie Huynh wrote:
Yes! A search box would make finding things in the lists much easier.
Maybe I'll file that under the "scale to 1k people" ticket.
Marie
On Sat, Mar 2, 2013 at 7:28 PM, Scott Koranda
<
<mailto:>>
wrote:
Cool.
I will work on updating it more on Sunday and Monday, but you should
have enough now to see how
some menus do (and do not) work.
Search box!
Cheers,
Scott
On Sat, Mar 2, 2013 at 9:21 PM, Marie Huynh
<
<mailto:>>
wrote:
> Good news! I imported it, changed your identifier to mine, ran
Console/cake
> database, and it seems good to go. Thanks!
>
> Marie
>
> On Sat, Mar 2, 2013 at 3:41 PM, Scott Koranda
<
<mailto:>>
wrote:
>>
>> Hi,
>>
>> At
>>
>> https://www.lsc-group.phys.uwm.edu/~skoranda/mysqldump_cou29.sql.gz
>>
>> You will find some initial COmanage LIGO data.
>>
>> Please see if you can ingest it into a "raw" registry
>> database.
>>
>> I have a python script that works like this:
>>
>> $ python load_by_mou_group.py
>>
Communities:LVC:LSC:MOU:HobartWilliamSmith:HobartWilliamSmithGroupMembers
3
>> 28
>> Processing employeeNumber=420,ou=people,dc=ligo,dc=org...
>> Processing employeeNumber=1070,ou=people,dc=ligo,dc=org...
>> Processing employeeNumber=2747,ou=people,dc=ligo,dc=org...
>> Processing employeeNumber=3007,ou=people,dc=ligo,dc=org...
>> Processing employeeNumber=3008,ou=people,dc=ligo,dc=org...
>>
>> The first argument is the LDAP group to use as a filter on
>> isMemberOf to find people. The second argument is the CoId.
>> The third argument is the CouId.
>>
>> I have loaded roughly 29 COUs. It doesn't take long.
>>
>> What's left to do:
>>
>> - finish existing COUs
>> - add COUs that have other COUs as parents
>> - work on the other COs (LIGO Lab mainly)
>> - add extended attributes like FTE
>>
>> I will do more data entry tomorrow evening, but I think this
>> is a good start.
>>
>> Scott
>>
>>
>
- [comanage-dev] some LIGO data, Scott Koranda, 03/02/2013
- Re: [comanage-dev] some LIGO data, Marie Huynh, 03/02/2013
- Re: [comanage-dev] some LIGO data, Scott Koranda, 03/02/2013
- Re: [comanage-dev] some LIGO data, Marie Huynh, 03/02/2013
- Re: [comanage-dev] some LIGO data, Benn Oshrin, 03/03/2013
- Re: [comanage-dev] some LIGO data, Marie Huynh, 03/02/2013
- Re: [comanage-dev] some LIGO data, Scott Koranda, 03/02/2013
- [comanage-dev] Re: some LIGO data, Scott Koranda, 03/03/2013
- Re: [comanage-dev] some LIGO data, Marie Huynh, 03/02/2013
Archive powered by MHonArc 2.6.16.