Grouper Users - Open Discussion List

[Michael Hodges <>]

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