Open Stack

1. yes, but probably only if its a short list. It may be feasible to show it only if there are 5 or less pages, and maybe just load all pages of data and paginate it on the client. If too big, ask the user to refine their search? Or always paginate to 5, and then the 6th page have a page requesting further refinement?

2. Not sure what the difference between searching and filtering is in this context? something like facets? If so, probably the 5 or less thing would work here too.

3. Yes, but again, probably within a smaller set of pages?

Thanks,
Kevin
________________________________________
From: Kruithof, Piet [pieter.c.kruithof-jr at hp.com]
Sent: Sunday, August 16, 2015 9:41 AM
To: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] [UX] [Keystone] [Horizon] Pagination support for Identity dashboard entities

I like Michael’s response because it moved the thread towards identifying actual user needs before digging into the technical feasibility.  IMHO, it would be helpful to have a few people on the list answer his questions:

1 - Do users want to page through search results?


2 - Do users want to page through filter results? (do they use filter results?)


3 - If they want to page, do they want to be able to go back a page and/or know their current page?


I understand that even if we answer “yes” to all three questions that there could be issues around implementation, but at least we’ll know a gap exists.


Piet Kruithof
Sr UX Architect, HP Helion Cloud
PTL, OpenStack UX project

"For every complex problem, there is a solution that is simple, neat and wrong.”

H L Menken


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev