Pagination for huge page series

[bsouster]

@rubinahaddad

We've got some pretty large pagination bars here at CIC:

We're wondering if we can go with pagers in this situation: http://wet-boew.github.io/wet-boew-styleguide/v4/design/pagination-en.html#pager

Although we think that if we go with pagers, we should have a Table of Content button in the middle of the pagers.

Thoughts?

Note: bringing this up because there is no design guide specific to Canada.ca. We're unsure of which pagination options should be standard across Canada.ca partners.

[rubinahaddad]

@bsouster yup that is definitely large! What were the reasons of not displaying only 10 options at a time?

[bsouster]

We can do that, but there's no functionality to 'see more' numbers without actively browsing later pages to uncover them. It doesn't sound very usable without that functionality or some indication that there are more than 10 pages.

And above all, we need to standardize which approaches to use in which situations for Canada.ca, else all the departments approach this situation in 5+ different ways.

[rubinahaddad]

Very true that we need a standardized approach. In terms of knowing there are more - this is a pretty basic pagination pattern so other cues that there are more pages include stating the number of results as well as the "next" is a clue there are more. The button will not show up if there are no more pages.

I'm going to tag this for the design guide for @burgvan to review

[thomasgohard]

@bsouster can you provide examples of pages where this use cases occurs.

[bsouster]

@thomasgohard http://www.cic.gc.ca/english/resources/statistics/facts2012/index.asp

[pcwsmith]

what about using an ellipsis to indicate many pages:

1 2 3 ... 61 62

thoughts?

[thomasgohard]

This seems like a case where the "previous - table of contents - next" pattern would be more appropriate. If someone wants to get to a particular set of data, the numbered page list is useless: They'd have to have memorised the contents and order from the table of contents.

The "previous - table of contents - next" pattern would allow them to move to and sequentially between sets of data, or get back to the table of contents to quickly access sets of data out of sequence.

[shawnthompson]

@bsouster We are presently working one just like that for Canada.ca and the Employment Insurance content. It's based on Jobseeker's Allowance (JSA).

[shawnthompson]

@bsouster did you look at what I sent you?

[bsouster]

@shawnthompson Now I have!