Agility - ArchivesSpace Integration and Automation

Common Integration Use Cases Between Agility and ArchivesSpace

Agility CMS and ArchivesSpace complement each other well in organizations that need to publish authoritative historical, archival, or institutional content to public-facing digital channels. ArchivesSpace serves as the system of record for archival descriptions, finding aids, and collection metadata, while Agility CMS manages the presentation, editorial workflow, and multi-channel delivery of that content.

1. Publish archival collection pages from ArchivesSpace into Agility CMS

Data flow: ArchivesSpace to Agility

Use ArchivesSpace as the authoritative source for collection records, series descriptions, container lists, and finding aids, then sync selected metadata into Agility CMS to generate public collection landing pages. Agility can present the content in a branded, user-friendly format for researchers, donors, students, and the general public.

• Reduces duplicate data entry across archival and web teams
• Ensures public pages stay aligned with the official archival record
• Allows marketing and communications teams to update page layouts without changing archival data

2. Create curated digital exhibits using archival metadata and media

Data flow: ArchivesSpace to Agility

ArchivesSpace can provide item-level descriptions, subject terms, dates, and related archival assets to Agility CMS for building online exhibits, anniversary microsites, or thematic story pages. Agility can combine this archival content with editorial copy, image galleries, timelines, and calls to action.

• Supports public engagement campaigns and educational programming
• Enables non-technical staff to build exhibit pages quickly
• Improves reuse of archival content across multiple campaigns

3. Synchronize controlled vocabulary and taxonomy for consistent discovery

Data flow: Bi-directional or ArchivesSpace to Agility

Organizations can integrate subject headings, collection categories, geographic terms, and creator names from ArchivesSpace into Agility CMS taxonomies. This helps ensure that archival content published on the website uses consistent terminology and supports better search, filtering, and navigation.

• Improves content consistency across departments
• Reduces manual taxonomy maintenance in the CMS
• Enhances site search and browse experiences for users

4. Automate updates when archival records change

Data flow: ArchivesSpace to Agility

When archivists update a finding aid, correct a description, or add new access conditions in ArchivesSpace, the integration can push those changes into Agility CMS for the corresponding public pages. This keeps the website current without requiring web editors to monitor archival changes manually.

• Minimizes stale or inconsistent public information
• Shortens the time between archival updates and web publication
• Supports governance for sensitive or restricted materials

5. Embed archival search and discovery into the public website

Data flow: ArchivesSpace to Agility

Agility CMS can host a public-facing research portal or archive landing page that embeds search, browse, or collection discovery components powered by ArchivesSpace APIs. This gives users a seamless experience from marketing or institutional pages into archival discovery tools.

• Improves access to collections from the main website
• Lets web teams control the surrounding page content and navigation
• Supports better conversion from awareness to research engagement

6. Publish donor, alumni, or institutional history content from archival sources

Data flow: ArchivesSpace to Agility

Universities, museums, libraries, and nonprofits can use ArchivesSpace records to populate historical pages about founders, milestones, major gifts, or institutional timelines in Agility CMS. Communications teams can then package this content for campaigns, annual reports, and commemorative pages.

• Creates a reliable source for historical storytelling
• Reduces research effort for communications teams
• Improves accuracy in externally published institutional history

7. Route editorial requests from web teams back to archivists for review

Data flow: Agility to ArchivesSpace

When web editors need new archival content, updated descriptions, or clarification on rights and restrictions, Agility can trigger a workflow or task back to the archival team. This creates a structured review process for content requests that require archival expertise.

• Improves collaboration between web, communications, and archives teams
• Provides traceability for content approvals and corrections
• Helps prioritize archival work based on public content demand

8. Build a unified content experience across public website and archival systems

Data flow: Bi-directional

Agility CMS can manage the front-end experience, while ArchivesSpace supplies authoritative archival data and record identifiers. Together, they can support a unified digital experience where users move from curated content pages to detailed archival records without losing context.

• Creates a more coherent user journey across institutional content
• Supports scalable headless architecture for public access
• Allows each team to work in its preferred system while sharing content efficiently