Description

Allow users to break up long lists of items into separate pages.  They should be able to decide if they want paging and how many per page.

Sakai has page navigation now -- "List Navigator UI Component" in the Sakai style guide.  The default for how many items to show on a page varies.  How many makes sense depends on context, how many total items, what type of items, etc.  The idea here is to make this navigator remember the users last setting (across sessions).  That way they set if for what makes sense given the current situation and it is persistent.  As things change for them they simply change the setting to meet current needs and again it's persistent until they need to change it again.  Currently this is a "one size fits all" default and many users have to change it every time they visit a particular page.

Problems with current Sakai widget 

Use Cases / Requirements for new component

Wireframes 


References / Competitive Analysis

NOTE:   Many of the below are for search navigation so should used strictly as a reference for more robust web application pages where users need to actually do something with the items in a list (other than just choose one).

Item Navigation (long list of items users may need to do something with) 

Search Navigation