The Background Processing screen (specifically under MARC Import) does not currently support the newer LEAP pagination options available in other, more recent LEAP screens. This creates usability challenges when reviewing and managing historical imports.

Problem:
The current interface relies on a “More” button to load additional records page by page rather than having the option to load all and setting the record count to view. This creates several issues:
• Staff must repeatedly click “More” to access older records, which is inefficient and time-consuming
• There is no option to “load all” or quickly navigate to a specific point in the list
• The number of visible rows is effectively fixed unless manually expanded through repeated clicks

Additionally, filtering functionality is limited:
• Filters only apply to the currently loaded/visible records, not the full dataset
• This significantly reduces the usefulness of filtering when trying to locate specific imports
• Users may miss relevant records simply because they have not yet been loaded into view

These limitations are especially problematic given the increase in smaller, more frequent imports due to EDI workflows. As a result:
• The volume of import jobs is much higher
• It is more difficult to determine whether a file has already been imported
• There is increased risk of duplicate imports or missed updates

A key example is authority updates, where staff must confirm whether a specific authority file has already been processed. The current design makes this unnecessarily difficult and error-prone.

Requested Enhancement:
• Implement standard LEAP pagination controls (as seen in newer LEAP screens), including:
• Page-based navigation
• Ability to jump to specific pages
• Consistent row display options (e.g., 25 / 50 / 100 per page or “load all”)
• Update filtering behavior to:
• Apply across the full dataset (not just currently loaded records)
• Return complete, accurate results regardless of pagination

Benefit:
• Greatly improves efficiency when reviewing large volumes of imports
• Reduces risk of duplicate work or missed records
• Enables reliable searching and filtering
• Aligns the experience with modern LEAP interface standards