Atlas view

Library Systems

This domain groups systems that solve Library Systems problems - shared vocabulary, common interfaces, and repeatable operational constraints. Use this page to see which systems already exist, what they ingest and emit, and which patterns we repeatedly rely on in this problem space.

Domains are how we avoid reinventing the same solution in slightly different shapes. When a domain repeats, it’s a signal to standardize schemas, mapping layers, auth patterns, and operator workflows.

Domain guide

How to read this domain

Definition

This domain groups systems focused on library systems workflows, shared data models, and repeatable operational constraints.

What belongs

  • Systems where library systems is the primary problem space.
  • Integrations that move, validate, or enforce data in this domain.
  • Operational tools that reduce risk and manual work for this domain.

What doesn't

  • Generic tools where library systems is incidental metadata.
  • One-off experiments without domain-specific constraints.

Typical integrations and constraints

  • Source-of-truth feeds, vendor APIs, and scheduled extracts.
  • Schema drift, credential scope, and compliance requirements.
  • Role-based access and operational review cycles.

Common interfaces

  • REST/JSON APIs and vendor export endpoints.
  • CSV, SQL views, or Sheets-based boundary objects.
  • Auth boundaries (service accounts, OAuth, SSO).

Common patterns and playbooks

No playbooks mapped yet.

Results 1 project
System ยท Active

Follett Destiny Patron Import

Generates and imports patron records into Follett Destiny so student library accounts stay aligned to current SIS data.

Reality Ingestion Delivery
Open project