LDP and Metadb

In order for the LDP software to connect to FOLIO, it needs read-only access to Okapi and the FOLIO database. The LDP can be hosted and administered locally by an institution’s own staff or by contracting hosting services out to a third party. You can find specific system requirements in the LDP documentation.

Installing and configuring the LDP software*

There are three main software components to install for your LDP implementation: LDP2, ldpmarc, and Folio Analytics. In general, install the latest production release for the LDP and ldpmarc software components, which do not have a dependency on FOLIO (flower) software release versions. For FOLIO Analytics, see https://github.com/folio-org/folio-analytics/blob/main/README.md.


For detailed information about how to set up and configure the LDP software, please review this link to access individual links to guides in the LDP repository. There you also will find the latest versions and fixes of the LDP software.

Setting up derived tables

To let report users take full advantage of the community-developed report queries as well as having a good starting point for ad hoc querying, it is strongly recommended to set up a nightly update on derived tables.

You can find instructions in Github on how to set up FOLIO Reporting Derived Tables.

Data privacy

The LDP software is designed to support GDPR and other data privacy requirements. Administrators can exclude a predefined set of tables.

See the Anonymization Guide for information on how to activate and configure these features.

The pages linked below list attributes that contain potential personal data:

  • Users module: tables that will not loaded in LDP software when anonymization is turned on
  • Organizations module: potential personal data in organizations module

Adding local data

As documented in the user guide, it is also possible to load and create local data into your LDP reporting database.

Using schemas

The concept of schemas allows you to organize tables and permissions within one database. In LDP we have initially four relevant schemas:

  • public: contains all extracted tables and its current data from the bound FOLIO tenant
  • history: stores data that have been updated in the past or may no longer exist
  • folio_reporting: contains all derived tables created and supported by the community
  • local: common area for report users to create or import own data

Besides using the local schema, you might consider setting up separate schemas for different report user groups or purposes. You are free to create more schemas for your local needs (e.g., to provide data for different departments or to separate and protect sensitive data).

Learn more about the schema concept and how to configure schemas using Postgres’s Schema Documentation.

For a granular setup of permissions, see also the built-in Roles and Privileges concepts of Postgres.

Moving and loading data

Loading and moving data into an LDP reporting database is as simple as it is for databases in general.

For Postgres there are two common approaches:

  • COPY: SQL command for moving table data via csv files
  • pg_dump / pg_restore: Postgres command line tools for importing and exporting data

Installing and configuring the Metadb software

The next generation software platform Metadb has been released and has been adopted by some institutions. Metadb is a new streaming data integration platform intended to eventually replace LDP. For installing and configuring Metadb follow the Metadb Documentation at the Library Data Platform - resources site.

Last modified November 14, 2023