Adobe Experience Manager Sites - Axiell Integration and Automation

Common Integration Use Cases Between Adobe Experience Manager Sites and Axiell

• Publish curated collection content from Axiell to Adobe Experience Manager Sites
  Use case: Museum, library, or archive teams manage object records, exhibit metadata, and descriptive content in Axiell, then publish approved summaries, images, and related stories to Adobe Experience Manager Sites for public web pages.
  Data flow: Axiell to Adobe Experience Manager Sites
  Business value: Reduces duplicate content entry, speeds up exhibit launches, and ensures the public website reflects authoritative collection data.
• Synchronize collection updates to keep public exhibit pages current
  Use case: When curators update an artifact description, provenance note, or exhibition status in Axiell, the changes are pushed to Adobe Experience Manager Sites for relevant collection pages, event pages, or digital exhibits.
  Data flow: Axiell to Adobe Experience Manager Sites
  Business value: Improves content accuracy, reduces manual website maintenance, and supports governance across curatorial and digital teams.
• Use Adobe Experience Manager Sites to create audience-facing narratives from Axiell records
  Use case: Content editors in Adobe Experience Manager Sites build thematic stories, educational pages, and campaign landing pages using structured collection data sourced from Axiell, such as artist, era, location, or object type.
  Data flow: Bi-directional, with Axiell providing source metadata and Adobe Experience Manager Sites publishing enriched content
  Business value: Enables faster content production, better reuse of collection metadata, and more engaging digital experiences for visitors and researchers.
• Push digital asset references from Axiell into Adobe Experience Manager Sites
  Use case: Axiell stores references to digitized objects, archival scans, or preservation files, and Adobe Experience Manager Sites consumes those references to display approved media on public pages without manual file handling.
  Data flow: Axiell to Adobe Experience Manager Sites
  Business value: Streamlines media publishing, supports controlled access to authoritative assets, and reduces the risk of using outdated or unapproved files.
• Return web engagement insights from Adobe Experience Manager Sites to Axiell teams
  Use case: Page views, click-throughs, and content engagement metrics from Adobe Experience Manager Sites are sent back to Axiell-related reporting workflows so curators can see which collections, exhibits, or topics attract the most interest.
  Data flow: Adobe Experience Manager Sites to Axiell
  Business value: Helps cultural institutions prioritize digitization, improve exhibit planning, and align collection work with audience demand.
• Automate approval workflows for public collection publishing
  Use case: A collection record is created or updated in Axiell, then routed through a publishing workflow where Adobe Experience Manager Sites only receives records marked approved for public release.
  Data flow: Axiell to Adobe Experience Manager Sites
  Business value: Strengthens governance, prevents premature publication, and gives curators and web teams a controlled handoff process.
• Support multilingual and localized exhibit pages from Axiell metadata
  Use case: Axiell provides standardized metadata fields and translations for object names, descriptions, and classification terms, which Adobe Experience Manager Sites uses to generate localized exhibit pages for different audiences or regions.
  Data flow: Axiell to Adobe Experience Manager Sites
  Business value: Improves accessibility for international audiences, reduces translation rework, and ensures consistent terminology across channels.