Grouper Developers Forum

[Jim Fox <>]

Seems like the two groups with different uuids are in fact two distinct 
groups that only happen to share a name.  Point-in-time should refer only 
to the group that esisted at that time.

Also, I think someone would need only read permission on the group to see 
the point-in-time membership, not admin privileges.

Jim

> Do you think it might make sense to only look at groups, stems, and 
> attributes that currently exist for these queries?  So for instance, say a
> group was created on 1/1/2010 that had some memberships and was deleted after 
> a few days.  Then a group (different uuid but same name) got added
> on 1/1/2011 possibly by somebody else.  If a point in time query is made for 
> all memberships of the group (based on a group name query) that
> existed on or before 1/2/2011, should that ignore the ones from the prior 
> group that was deleted?  Also, I'm assuming for security that you have
> to be a current admin of the group.
>
> Thanks!
>
> -- Shilen
>
>
> On 1/7/11 12:30 PM, Chris Hyzer wrote:
>
>       Shilen, lets talk point in time web services.
>
>       I picture it as augmenting the existing web services to include point 
> in time params…  I think we discussed that before.
>
>        
>
>       Which operations should take these as inputs? 
>
>        
>
>       These are the readonly WS queries: findGroups,  findStems, 
> getAttributeAssignments, getGrouperPrivileges, getGroups, getMembers,
>       getMemberships, getPermissionAssignments, hasMember  
>
>        
>
>       I think the findGroups and findStems ones would be hard, though maybe 
> you know better.
>
>        
>
>       Maybe we could start with these:  getGroups, getMembers, hasMember
>
>        
>
>       Maybe the first one is getMembers.
>
>        
>
>       Up to you.
>
>        
>
>       I made a wiki about how to augment a Grouper Web Services (e.g. for 
> point in time).
>
>        
>
>       
> https://spaces.internet2.edu/display/Grouper/Grouper+Web+Services+for+developers
>
>        
>
>       Anyways, let me know when you commit stuff so I can review, and update 
> that wiki if I missed something (there are a lot of steps, Im
>       sure I missed some J )
>
>        
>
>       Also, I bet we could pretty easily augment the lite UI to have an 
> option under the “advanced” button so two timestamp fields appear
>       and you could see the list (or I guess also export) based on point in 
> time.  If you are interested in that let me know and we can work
>       on it together or I could make a similar doc about it for you to work 
> on it… J
>
>        
>
>       Thanks,
>
>       Chris
>
>        
>
>        
>
>       From: 
>
>  
> [mailto:]
>  On Behalf Of Emily Eisbruch
>       Sent: Thursday, January 06, 2011 2:59 PM
>       To: Grouper Dev
>       Subject: [grouper-dev] Action Items: Grouper Call 5-Jan-2011
>
>  
>
> New Action Items
>
>  
>
> [AI] ( Rob) will continue to investigate the viability of a Grouper VM. 
>
>  
>
> [AI] (TomZ) will inform AnnKW which LDAPPC and which LDAPPC-ng wiki pages are 
> product versus development. 
>
>  
>
> [AI] (Ann KW) will move the appropriate development pages in the wiki to 
> project pages in the wiki.
>
>  
>
> [AI] (AnnKW) will look at queries of the Grouper wiki to be sure there are no 
> outdates pages.
>
>  
>
> [AI] (Shilen and Chris) will talk about point in time web services.
>
>  
>
> Carry Over Action Items
>
>  
>
> [AI] (TomZ) will report on timing for Grouper demo work. 
>
>  
>
> [AI] (TomZ) will create a wiki page enumerating activities related to 
> connectors. 
>
>  
>
> [AI] (TomZ) will work with Chad in the process of proposing a Working Group 
> to focus on provisioning.
>
>  
>
> [AI] (TomZ and Chris) will discuss/work on LDAP Grouper Loader for importing 
> groups. JIRA 442  
>
>  
>
> [AI] (Everyone) review Rob's chapters and give him feedback on the Grouper 
> Users
> List.https://spaces.internet2.edu/display/GrouperWG/GrouperBook   
>
>  
>
> [AI] (TomB) will explore new international participation for work on the 
> Grouper UI. 
>
>  
>
>  [AI] (Emily) will give suggestions to Ann KW on the community contributions 
> page of
> wikihttps://spaces.internet2.edu/display/Grouper/Contributions 
>
>  
>
>  
>
>  
>
>
> Emily Eisbruch, Technology Transfer Analyst
>
> Internet2
>
>
>
> office: +1-734-352-4996 | mobile +1-734-730-5749
>
>  
>
> Visit our website: www.internet2.edu
> Follow us on Twitter: www.twitter.com/internet2
> Become a Fan on Facebook: www.internet2.edu/facebook
>
>  
>
>  
>
>  
>
>  
>
>  
>
>  
>
>  
>
>  
>
>  
>
>  
>
>