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 

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)

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

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-531

• 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.

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)

Metadata Management

• FOLIO supports single record integration with OCLC - see

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-211

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.

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
  • https://github.com/folio-org/mod-ncip
  • https://github.com/folio-org/edge-ncip
  • https://github.com/folio-org/edge-sip2
• 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

Financial Integrations

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

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 
  • https://github.com/folio-org/mod-oai-pmh
  • https://github.com/folio-org/edge-oai-pmh
  • https://github.com/folio-org/ui-oai-pmh
• 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
  • https://github.com/folio-org/mod-patron
  • https://github.com/folio-org/edge-patron
  • https://github.com/folio-org/mod-rtac
  • https://github.com/folio-org/edge-rtac

Institutional Repositories / Digital Collections

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

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