A survey to collect data on source systems and integration of libraries considering FOLIO implementation is here (spreadsheet generated by SysOps members):

https://docs.google.com/spreadsheets/d/1O8orRx2dBedaeWIkbN30v2ZHyRG6BgecLXgy5xL35bQ/edit?usp=sharing

Any library considering FOLIO implementation is welcome to add their data to the spreadsheet.

Integration Matrix of the ARLEF group: https://docs.google.com/spreadsheets/d/1xkJGi-yO8pluHJ1zGJf-oTvlGZUsi5M1iTNChqRcRug/edit#gid=0

An Integration is a system or service, external to FOLIO, where we need to support automated data exchange between FOLIO and that external system. The data may flow in to FOLIO from the external system, from FOLIO to the external system, or bidirectionally. It may be transactional in nature, or it may be a bulk/batch process. Where possible, standard industry protocols should be used.

Integrations by functional/SIG area

Reporting

Most libraries need reporting tools to support daily operational needs and workflows, extend FOLIO functionality, and allow links to other systems
Libraries who run reports need the ability to define, code and run custom defined reports.
An LDP app is in development

External Systems

These are in use at at least one library.

Metadb - see https://github.com/metadb-project
LDP (Library Data Platform) - see https://docs.folio.org/docs/reporting/
Panorama (Integration reference - Panorama)
LDLite - https://github.com/library-data-platform/ldlite

Desired Integrations

insert tool name

JIRAs to track for more information

Follow jiras labeled "reporting" for the broadest picture of development.

The LDP project has its own github space: https://github.com/library-data-platform

User Management

Most academic libraries will want integration with a campus identity management system, as well as the ability to support users that are not in that system. The campus identity management system maintains identities, including inflow and outflow.
Most academic libraries also need to support Single Sign-On, including support for federated signon, e.g. InCommon (U.S. Higher Ed.)
User management may also play a part in access control - Users data can verify eligibility, provide physical access (cardswipe/turnstile) and provide network access (RADIUS, local AD domain)
External tools that are not in user management area rely on user management workflows to govern authorization (e.g., locker rental DB at UChicago.)

Note that FOLIO provides a bulk update user account module - mod-user-import (https://github.com/folio-org/mod-user-import)

External systems

These are in use at at least one library.

PeopleSoft Campus Solutions
OKTA

Desired integrations

EZProxy

JIRAs to track for more information

Resource Management - Acquisitions

As of the Lotus release, FOLIO supports exporting orders in EDIFACT format, and importing invoices in EDIFACT format, but does not yet support order import in EDIFACT format. See UXPROD-531 - Getting issue details... STATUS
Many libraries have home-grown tools used in Acquisitions (like Cornell's POOF tool). Those are not listed here, but are important considerations for implementers.

External systems

These are in use at at least one library.

GOBI API
FOLIO order import tool: https://github.com/folio-labs/folio-order-import-tool

Desired integrations

OASIS (Proquest/Coutts)
SAP
Baker & Taylor API

JIRAs to track for more information

Resource Management - Electronic Resource Management (ERM)

FOLIO provides built-in integration with EBSCO Holdings Management via the FOLIO eHoldings app
FOLIO provides support for a local knowledge base using the Local KB Admin app. The local knowledge base can be populated in multiple ways including:
- From GOKb (the Global Open Knowledege base) through an integration which automatically harvests data from the GOKb and populates the local KB
- From KBART files provided by suppliers
- From JSON files
- From the LAS:eR ERM (via an additional data sync module developed by Knowledge Integration and University of Leipzig)

External systems

These are in use at at least one library.

EBSCO Holdings Management
GOKb
LAS:eR ERM

Desired integrations

SFX
360 KB
Roam (https://roam.plus/)

JIRAs to track for more information

Metadata Management

FOLIO supports single record integration with OCLC - see UXPROD-211 - Getting issue details... STATUS

External systems

These are in use at at least one library.

OCLC
- WorldCat Metadata API
- WorldCat Search API
- CBS; connected with mod-inventory-update (used by the German library networks GBV, SWB, and Hebis)
Sinopia Linked Data Editor
- Uses Airflow to export BIBFRAME RDF to FOLIO Inventory records

Desired integrations

FOLIO adopting libraries are interested in integrations with the following tools/external systems:

Harrassowitz
Casalini
OCLC
- Direct export from OCLC to local system via TCP/IP
SHARE-VDE
BTCat
SkyRiver

JIRAs to track for more information

Special Collections

Most special collections workflows are focused on record description, maintaining item provenance information, and supporting reading room usage.
FOLIO does not provide built-in support for reading room functionality, though it can easily support library-use-only items.

External systems

These are in use at at least one library.

ArchivesSpace
AEON

Desired integrations

AtoM (https://www.accesstomemory.org/en/)

JIRAs to track for more information

Resource Access and Resource Sharing

Resource Access integrations primarily focus on user records (listed above), resource sharing, self-check tools, and course reserves
FOLIO provides a native course app and a module to support LTI connectivity, see
- https://github.com/folio-org/edge-lti-courses
- https://github.com/folio-org/ui-lti-courses
FOLIO supports both NCIP and SIP2, see
FOLIO supports Z39.50, see
- https://github.com/folio-org/Net-Z3950-FOLIO
FOLIO supports remote storage to facilitate use of off-site high-density library facilities. Currently CAIASoft and Dematic are supported. See
- https://github.com/folio-org/edge-caiasoft
- https://github.com/folio-org/edge-dematic

External systems

These are in use at at least one library.

ReShare (Integration reference - ReShare Returnables
Relais
MeeScan
Sakai (Integration reference - Learning Management System/LTI)
Ares
CAIASoft
Dematic

Desired integrations

ILL-Server (HBZ)
SLNP
Luxer One Contactless Lockers
DIBS (Controlled digital lending)
Cybersource
Springshare LibApps

JIRAs to track for more information

Financial Integrations

This will vary greatly library to library, depending on the systems that the institution is using.

External systems

These are in use at at least one library.

add tool name

Desired integrations

SAP
Cybersource
Moneris
Oracle ERP

JIRAs to track for more information

Discovery Layer

Institutions who have adopted or plan to adopt FOLIO are known to be using EDS, VuFind, or Blacklight
FOLIO supports OAI-PMH - see
Some libraries may have additional discovery tools outside of their main discovery layer to support things like building maps or reporting missing items
VuFind has developed a FOLIO driver - see https://github.com/vufind-org/vufind/blob/dev/module/VuFind/src/VuFind/ILS/Driver/Folio.php
FOLIO provides some modules to support patron and discovery connection - see

External systems

These are in use at at least one library.

Blacklight (Integration reference - Blacklight)
EDS (Integration reference - Ebsco Discovery Service (EDS))
VuFind (Integration reference - VuFind®)
Syndetic Solutions

Desired integrations

insert tool name

JIRAs to track for more information

Institutional Repositories / Digital Collections

Libraries may want to integrate FOLIO with their local institutional repository and/or digital collections system

External systems

These are in use at at least one library.

insert tool name

Desired integrations

insert tool name

JIRAs to track for more information

Workflow Engines and Tools

Some libraries may want to use external tools that are not subject-area specific, but rather leverage low-code tools or similar to automate library workflows
FOLIO has done a proof of concept with Camunda BPM, see https://github.com/folio-org/mod-camunda

External systems

These are in use at at least one library.

Airflow for Migration
Camunda (in use with the POC at Texas A&M)
Prefect

Desired integrations

insert tool name

JIRAs to track for more information

Browser not supported