Grouper Users - Open Discussion List

[Julio Polo <>]

No answer yet to my last question, so let me try asking specific questions:

1) When using pagination with getMembers, how do you retrieve the number of pages in the group (or alternately, the number of members in the group without actually retrieving the entire membership)

2) I don't see anything in getMemberships that allows me to search for a string and return the group members matching that string.  If getMemberships is the right API for implementing filtering, which are the parameters where we specify the search string?  We want to search for members' subject attributes (id, identifier, description) containing string 'foo' 

3) If not getMemberships, how about using getSubjects for filtering?  I see that it takes a group and a search string.   I tried that but I don't think it's limiting the results to the provided group.  For example:

<WsRestGetSubjectsRequest>
  <WsGroupLookup>
   <groupName>etc:uiUsers</groupName>
  </WsGroupLookup>
 <searchString>foo</searchString>
 <subjectAttributeNames>
   <string>name</string>
 </subjectAttributeNames>
</WsRestGetSubjectsRequest>

and it seems to return the person with the 'foo' identifier, even if that person is not a member of the group specified in the request.  It also returns groups where 'foo' is a stem.

We are running Grouper 2.2.2 (looks like getMembership pagination is not available in 2.2.2 as we are getting errors like CannotResolveClassException: pageSize)

Any pointers would be appreciated.

-julio

On Wed, Oct 31, 2018 at 9:53 AM Julio Polo <> wrote:

The filtering that Michael wants to perform is along the lines of "show only the members of the group whose name, ID or identifier contain a particular string." I doubt that getMembers or getMemberships offer anything like that.  They both offer pagination and filtering by type of membership, subject source, etc. but I don't see anything that would filter based on membership's subject's attributes.  Am I wrong?  If not, how can the membership subject attribute search be performed without cycling through every member of the group returned by getMembers or getMemberships?

-julio

On Wed, Oct 31, 2018 at 9:23 AM Hyzer, Chris <> wrote:

I would look at “get members” first, and if you don’t have everything you need, then “get memberships”.  thanks

 

From: <> On Behalf Of Michael Hodges
Sent: Wednesday, October 31, 2018 2:47 PM
To:
Cc: Grouper Users <>
Subject: Re: [grouper-users] Grouper Web Services - Find Members

 

Hello Carey,

 

The use-case is a UI providing the presentation of a list of direct members, 20 per page.  Initially all of the members were retrieved and pagination with and without filtering was done only on the UI side.  That worked until the team encountered a group of 30k+ direct members, which triggered timeout issues and/or excessive UI delays.   Redesign work now involves investigating how to move pagination and filtering to the server.

 

I'll have the team take a look at memberships, thanks.

 

TMI: the context is our UH Groupings project: <https://github.com/uhawaii-system-its-ti-iam/uhgroupings>.

 

On Wed, Oct 31, 2018 at 2:27 AM Black, Carey M. <> wrote:

Michael,

 

Can you describe what they are trying to do? ( Not just the API calls they are trying to use, and what they want them to do.)

 

The reason I ask is that “Members” may not be what they are really after. ( They may actually be after “Memberships”. )

 

--

Carey Matthew

 

From: <> On Behalf Of Michael Hodges
Sent: Tuesday, October 30, 2018 9:41 PM
To: Grouper Users <>
Subject: [grouper-users] Grouper Web Services - Find Members

 

The service doesn't exist, but while working with a student team implementing an application that makes Grouper calls, this is the web service that they  anticipated:

  o Find Members - featuring filtering and pagination and sort

 

Get Subjects appears to be the best-fit available service, but then we would have to write custom pagination.

 

Are we reading the information correctly?

   o <https://spaces.at.internet2.edu/display/Grouper/Grouper+Web+Services>

 

Recommendations?

 

We note that Grouper handles pagination along with subject filtering, so reading Grouper's source code is an option that has been recommended to the team.  However, thought I'd check and see if there's any advice available.

 

Thanks for any advice,

 - Michael