Grouper Developers Forum

[Tom Zeller <>]

I got a request to add a user to be a reader on a 60k member group.  So I
go to the UI, pull up the group, pull up the readers, and click the
button to assign to more users.  Then I wait, and wait, and wait, then I
get an error.

[snip]

 

Grouper could also optionally index this stuff in a search engine so
subject queries based on substring of description (although not real
time) would be superfast.   http://www.hibernate.org/410.html  This way
the source would really only need to be optimized for ID lookups, not
text searches…

I like the idea of indexing grouper attributes this way and adding to the current query filters. Not sure about Subjects. My take would be that Sources ought to be able to do the searching, sorting and paging you need. We can extend the Subject API to take advantage of such features, or sources can emulate them, but we shouldn't have Grouper specific stuff.

To follow along with Gary, I'm thinking of additional optional methods to Source which provide caching or batch operations.

When xml-importing, it might be nice to have Source.getAllSubjectsAndCache() and store Subjects in memory to avoid 'many' lookups. Retrieving Subjects using a configurable size, e.g. getSubjects(Set members, int batchsize), might also be helpful.

TomZ