K-Int Labs

Foundry glossary

Terms you’ll encounter when running FOLIO on Foundry, with examples from Labs.

For standard FOLIO terms, see the glossary in the FOLIO documentation.

Capability plan

A capability is a selectable unit of software in Foundry, such as a staff app and its backend services. A capability plan in KI Console shows what Foundry would add, remove or update before you apply the change. Adding a capability can bring in a dependency or require an upgrade to one you already run.

See a capability plan with an upgrade warning.

Foundry Hooks

Hooks let Foundry hand off configured work at points in a Workspace’s lifecycle. The first hook runs after an installation or rebuild. For example, Snapshot can run a Python recipe that sets up ILL institutions and pickup branches through the FOLIO APIs.

See the post-install event and ILL recipe.

Foundry Snapshot

Snapshot is both the name of a moving Foundry release channel and of K-Int’s test Workspace that follows it. The channel makes new revisions available. The test Workspace rebuilds nightly and recreates its configured test baseline. Staff can try recent changes there, knowing the next rebuild will replace their test data.

See how the nightly Snapshot rebuild works.

Foundry Workspace

A Workspace is a named environment where staff open their selected FOLIO apps. Foundry manages its app selections, software versions and staff admission, and routes requests to the associated FOLIO tenant. For example, a library can have a Workspace for ILL alone, with its own staff access and release settings.

See an ILL Workspace go from request to staff access.

Multi-institution ILL

Multi-institution interlibrary loan lets several libraries share one FOLIO tenant while each borrows and lends under its own institutional identity. Each library has its own Directory entry and identifier. Staff can switch between the institutions they’re authorised to act for.

A consortium of 150 libraries that only needs ILL can use this model to share one FOLIO tenant. In the demo, Riverside Library sends a request from its Borrow queue over ISO 18626. Parkside Library opens its own incoming record in the Supply queue.

Watch the multi-institution ILL demo on YouTube.

Release source

A Workspace’s release source tells Foundry where to look for versions when preparing an update. A channel follows a series of releases as new revisions become available. A pin selects one exact revision. Update policy controls when an update is applied, so a Workspace with manual updates can stay on its installed revision while its channel moves ahead.

Read how Foundry separates release availability from updates.