Grouper Developers Forum

[Gagné Sébastien <>]

Couldn't you add an ORDER BY option in the query to the repository ? You 
would need to find which stem attribute(e.g. displayName, ID) is displayed 
though.


-----Message d'origine-----
De : Peter DiCamillo 
[mailto:]
 
Envoyé : 11 septembre 2012 14:03
À : Chris Hyzer
Cc : Gagné Sébastien; 

Objet : Re: [grouper-dev] Stem list not sorted with multiple pages

Just for the record, it's my patch. I think the issue is not so much the 
repository size as the repository structure, and how many items occur at one 
node in the tree. Although, of course, you need a somewhat large repository 
for a large list to be a possibility. The patch is not trivial, and I 
definitely would like to see the issue addressed in the new UI. One 
possibility might be to display items under alphabetical sub-lists, like, for 
example, A-H, I-Q, R-Z, with the division points calculated to generate 
appropriate list sizes (if there's not a patent on that :-))

Peter

Chris Hyzer wrote:
> The problem is that we have folders and groups (and potentially other types 
> of objects: e.g. attributes) being sorted and paged into one list.  Its 
> like when you are on Amazon, and you sort by something, and it wont let you 
> unless you pick which department you want to look in.  Maybe Sebastien's 
> patch would help for smaller repositories (the UI used to work that way, 
> and there were performance problems for large repositories so we broke it 
> :) ).  But we definitely need to have something in the new UI (maybe it 
> shows all the folders first, then groups, etc.  Not sure.
> 
> Thanks,
> Chris
> 
> -----Original Message-----
> From: 
> 
>  
> [mailto:]
>  On Behalf Of Peter 
> DiCamillo
> Sent: Tuesday, September 11, 2012 10:14 AM
> To: Gagné Sébastien
> Cc: 
> 
> Subject: Re: [grouper-dev] Stem list not sorted with multiple pages
> 
> Yes, I discovered that too. We have the same situation with stems 
> lists in a few cases not fitting on one page of the default size. I 
> have a patch for that for AbstractRepositoryBrowser.java, and I was 
> going to bring that up on the list after I finish our update to Grouper 
> 2.1.2.
> The patch just sorts the entire result set before displaying each page. 
> That's potentially a performance problem, but 350 stems is the worst 
> case for us, and not a problem.
> 
> Peter
> 
> Gagné Sébastien wrote:
>> Hi,
>>
>> Is it normal that the whole resulset isn't sorted when the stem list 
>> is on multiple pages ? They are properly sorted on each page, but not 
>> as a whole.
>>
>>  
>>
>> Thanks
>>
>>  
>>
>> Here is my example :
>>
>> Page 1
>>
>> Page 2
>>
>>  
>>
>> All on one page, using page size=100 (the yellow lines were found on 
>> Page 2 above)
>>
>>  
>>
>> * *
>>
>> *Sébastien Gagné,*     | Analyste en informatique
>>
>> 514-343-6111 x33844  | Université de Montréal,
>>
>>                      | Pavillon Roger-Gaudry, local X-100-11
>>
>>  
>>
>