Built-in NodePaginator plugins

Name	Plugin name	Description
DefaultNodePaginator	Default	Standard file browser pagination, backed by the common JPA-based queries (NodeBaseSrv#getCommonChildrenPaginated / getCommonChildrenByCategoryPaginated). Column visibility in getConfig() comes straight from the current user’s profile (Profile > General > File Browser) - no metadata columns.
MariaDbExperimentalNodePaginator	Mariadb experimental	Alternative implementation for the same two queries, using hand-written native SQL against MariaDB instead of the common JPA-based queries, aimed at large repositories where the generic pagination becomes a bottleneck. MariaDB-specific and marked experimental - the native SQL is not portable to other database engines.
TestNodePaginator	Consulting metadata sample	Reference implementation demonstrating how to inject metadata columns into the file browser. Delegates pagination to the same common queries as DefaultNodePaginator, then adds up to 4 extra columns (Input 1, Input 2, Status, Icon) pulled from the demo “Consulting” metadata group’s own table (OKM_PGRP_CUR_CONSULTING) via a direct SQL query - the last two columns render arbitrary HTML (a badge and an icon) to show whether each node’s metadata row was found.

Note

A pagination plugin is not active by default - it must be enabled per profile from Profile > General > Pagination > Pagination plugins. Once enabled, an icon appears in the file browser to switch between the default paginator and the enabled one(s). See Creating your own NodePaginator plugin for the interface and the full metadata-column example.