Skip to Content.
Sympa Menu

grouper-dev - RE: [grouper-dev] need to remove paging from admin ui subject search

Subject: Grouper Developers Forum

List archive

RE: [grouper-dev] need to remove paging from admin ui subject search


Chronological Thread 
  • From: Chris Hyzer <>
  • To: "GW Brown, Information Systems and Computing" <>, Grouper Dev <>
  • Subject: RE: [grouper-dev] need to remove paging from admin ui subject search
  • Date: Sun, 4 Dec 2011 04:03:00 +0000
  • Accept-language: en-US

Sorry, you need to put this in the soruces.xml for the source:

<!-- on a findPage() this is the most results returned -->
<init-param>
<param-name>maxPageSize</param-name>
<param-value>100</param-value>
</init-param>

Then you will see what I am seeing :)

Thanks,
Chris


-----Original Message-----
From: GW Brown, Information Systems and Computing
[mailto:]

Sent: Saturday, December 03, 2011 2:06 PM
To: Chris Hyzer; Grouper Dev
Subject: Re: [grouper-dev] need to remove paging from admin ui subject search

--On 03 December 2011 06:08 +0000 Chris Hyzer
<>
wrote:

>
>
> The problem is that the admin UI used to get all subjects for a search
> string, but that doesn't scale. The subject source interface doesn't
> have support for paging (e.g. record count, and getting specific pages
> /sizes… Im not sure this is possible in all subject source types)
>
>
>
> https://bugs.internet2.edu/jira/browse/GRP-716
>
>
>
> Gary, think you have time to look at this in the v2.0 branch?
>
>
>
> We need to remove paging buttons from subject search in admin ui, and if
> there are too many members (the SubjectFinder.findPage() method will tell
> you), then perhaps a message could be displayed that the user should
> narrow their search, and it should also show whatever members it found
> (e.g. the first 200 or whatever number is configured in the source).
I think you've already changed the code to deal with too many results - I
can provoke:
Error: Too many results, please narrow your search

It doesn't show any results - goes back to search screen - but I think that
is appropriate. Message might indicate the limit - but that appears to be
per source - SearchPageResult doesn't go to that level of detail - not that
you get on given the exception that is thrown.

Gary
>
>
>
> Thanks,
>
> Chris



----------------------
GW Brown, IT Services




Archive powered by MHonArc 2.6.16.

Top of Page