OpenText TeamSite - LiveSite Content Services - Axiell Integration and Automation

Common Integration Use Cases Between OpenText TeamSite - LiveSite Content Services and Axiell

1. Publish curated collection records to public-facing digital experiences

Data flow: Axiell → OpenText TeamSite - LiveSite Content Services

Axiell can send approved collection metadata, object descriptions, exhibition details, and related media references to OpenText TeamSite - LiveSite Content Services for rendering on museum, library, or archive websites. This allows content teams to publish searchable, context-aware public pages without manually rekeying records.

• Improves speed to publish new acquisitions and exhibition content
• Ensures public content stays aligned with authoritative collection data
• Reduces duplicate content entry across collections and web teams

2. Deliver personalized exhibit and collection recommendations

Data flow: Bi-directional

OpenText TeamSite - LiveSite Content Services can use visitor behavior, location, or campaign context to personalize content, while Axiell provides structured collection data, themes, and subject classifications to support relevant recommendations. For example, a visitor viewing ancient artifacts can be shown related objects, essays, or upcoming exhibitions.

• Increases engagement with digital collections
• Supports tailored experiences for educators, researchers, and general visitors
• Improves conversion to event registrations, donations, or membership actions

3. Automate media and asset publishing for digital collections

Data flow: Axiell → OpenText TeamSite - LiveSite Content Services

Axiell can provide approved metadata and links to digitized assets such as images, audio, video, or scans, which OpenText TeamSite - LiveSite Content Services can present in web pages, portals, and online exhibits. This is useful when institutions need to expose high-resolution or derivative assets while preserving governance over the master record.

• Speeds up publication of digitized archives and gallery assets
• Maintains consistent metadata and rights information
• Supports controlled public access to sensitive or restricted materials

4. Synchronize content updates for exhibitions and campaigns

Data flow: Bi-directional

When curators or collection managers update exhibition narratives, object status, or loan information in Axiell, those changes can flow into OpenText TeamSite - LiveSite Content Services to update web pages and campaign landing pages. In return, web editors can push promotional content, banners, and audience-specific messaging back into the digital experience layer without altering the core collection record.

• Reduces delays between curatorial updates and public web changes
• Improves coordination between collections, marketing, and digital teams
• Minimizes errors caused by manual content duplication

5. Expose searchable public discovery portals from collection data

Data flow: Axiell → OpenText TeamSite - LiveSite Content Services

Axiell can supply structured metadata, taxonomy, and authority terms to OpenText TeamSite - LiveSite Content Services to power public discovery portals with filters, faceted search, and topic pages. This is especially valuable for institutions offering online access to archives, special collections, or research catalogs.

• Improves discoverability of collection holdings
• Supports advanced search experiences for researchers and students
• Reduces dependence on custom one-off data exports

6. Manage rights, access restrictions, and publication approvals

Data flow: Axiell → OpenText TeamSite - LiveSite Content Services

Axiell can act as the system of record for rights status, embargo dates, and access restrictions. OpenText TeamSite - LiveSite Content Services can consume those rules to determine what content is shown publicly, what requires authentication, and what must remain hidden until approved.

• Helps enforce publishing governance and compliance requirements
• Prevents accidental exposure of restricted materials
• Supports controlled release of digitized content over time

7. Support multilingual and localized cultural heritage experiences

Data flow: Axiell → OpenText TeamSite - LiveSite Content Services

Axiell can provide multilingual object titles, descriptions, and subject terms to OpenText TeamSite - LiveSite Content Services, which can then render localized website content for different audiences. This is useful for institutions serving international visitors, bilingual communities, or regional education programs.

• Improves accessibility for diverse audiences
• Reduces manual translation effort for core collection content
• Enables consistent multilingual presentation across digital channels

8. Streamline editorial workflows for digital exhibitions and knowledge pages

Data flow: Bi-directional

Curators and collection staff can maintain authoritative object data in Axiell, while content editors use OpenText TeamSite - LiveSite Content Services to build interpretive pages, exhibition stories, and educational content around that data. Integration allows editors to reference live collection records, reducing the need to copy object details into separate editorial systems.

• Improves collaboration between curatorial and web publishing teams
• Speeds production of exhibition microsites and educational content
• Ensures interpretive content stays connected to current collection records