Work With Long Tables
Libcodesk uses one pagination pattern for long operational tables in the Libcodesk WebApp and the Standalone app. You will see it on applicable pages such as Members, Collections, Periodicals, Accession Register, circulation lists and history, Accounts, Visitors, Reading Room, reports, and notification history.
Understand The Controls
- Records shows the total number of records matching the current search and filters.
- Rows per page controls how many matching records are loaded at once.
- Go to page accepts a page number. Press Enter or select Go.
- Page X of Y shows the current page and total available pages.
- Previous page and Next page move one page at a time.
The controls wrap into additional rows on narrow windows instead of becoming compressed or leaving the screen. You can reach every control with the keyboard.
Search And Filter Safely
- Enter your search or select the required filters.
- Wait for the table to finish loading.
- Confirm the matching record count.
- Choose the number of rows per page if needed.
- Move with Previous or Next, or enter a known page number and select Go.
Changing search criteria, filters, the active library, or rows per page returns the result to its first valid page. Sorting and pagination apply to the full matched dataset, not only the rows currently visible.
If A Page Number Is Too Large
Libcodesk safely opens the last available page. It does not show a blank page merely because the requested number is higher than the current page count.
If filters reduce the number of results while you are on a later page, the table returns to a valid page automatically.
Do And Don't
- Do search or filter before paging through a very large result.
- Do check the record count before starting batch work.
- Do wait for the current page to finish loading before selecting another page.
- Don't assume a batch selection includes records on every page unless the page explicitly says all filtered results are selected.
- Don't repeatedly select Next while a loading indicator is visible.
Frequently Asked Questions
Why are some short lists not paginated?
Small configuration lists that are already fully visible do not need pagination. Pagination is used where loading or displaying the complete result could reduce speed or readability.
Does changing rows per page change my records?
No. It changes only how many matching records are displayed on one page.
Are WebApp and Standalone controls different?
Their visual controls follow the same order and behavior. The WebApp loads cloud data; a Local setup in the Standalone app loads its local database. The visible workflow remains the same.
Why did the table return to page one?
The search, filters, library scope, or rows-per-page value changed. Returning to the first page prevents an old page number from hiding the new result.