Topic

FOLIO ERM experiments

Lab notes on running FOLIO-adjacent ERM capabilities such as Licenses and Agreements in smaller, runtime-composed systems.

All topics

FOLIO: How Many Grapes Went into the Wine?

An opinion on operational enclosure, ecosystem enclosure, and the reciprocal obligations needed to sustain open-source library software.

  • opinion
  • folio
  • open-source
  • sustainability
  • operational-enclosure
  • ecosystem-enclosure
  • libraries
  • hosting
  • governance
  • foundry

Foundry Module SDK: profiles for a smaller FOLIO dev loop

A walkthrough of the new Foundry Module SDK profile model: start a production-shaped module runtime, then substitute only the backend or frontend you are actively changing.

  • foundry
  • folio
  • module-sdk
  • ill
  • erm
  • open-access
  • serials
  • lattice
  • developer-experience
  • microfrontends

Federated Identity in Libraries Is Already Happening

A response to Amanda Ferrante's Scholarly Kitchen article, and an argument that library federation is not only about login protocols but also about trust, attestation, and shared circulation across institutions.

  • libraries
  • federated identity
  • interoperability
  • resource sharing
  • DCB
  • MOBIUS
  • FOLIO
  • EBSCO
  • K-Int

Why not the whole of FOLIO?

Foundry could become a lighter self-hosting substrate for FOLIO, but the immediate goal is a sovereign home for K-Int apps and ILS-neutral library extensions.

  • foundry
  • folio
  • erm
  • open-access
  • ill
  • serials
  • koha
  • evergreen
  • platform-services

Foundry now runs a small FOLIO app suite on a laptop

Licenses, Agreements, Open Access, Serials Management, and ILL now run together in Foundry through descriptor-selected module-federation artifacts.

  • foundry
  • folio
  • lattice
  • module-federation
  • microfrontends
  • okapi
  • eureka
  • licenses
  • agreements
  • open-access
  • serials
  • ill

Foundry platform services and the docking layer

How Foundry is separating platform support APIs from FOLIO utility modules, and why acquisition units belong behind a provider-backed platform boundary.

  • foundry
  • folio
  • okapi
  • loom
  • envoy
  • platform-services
  • licenses