OpenText Core Signature - Axiell Integration and Automation

Common Integration Use Cases Between OpenText Core Signature and Axiell

OpenText Core Signature and Axiell complement each other well in cultural heritage organizations that need controlled approvals, legally binding consent, and reliable preservation workflows. OpenText Core Signature handles secure electronic signing, while Axiell manages collections, metadata, and long-term digital access. Together, they can reduce manual paperwork, speed up approvals, and improve governance across museums, libraries, and archives.

1. Acquisition and Donation Agreement Signing

Data flow: Axiell to OpenText Core Signature, then back to Axiell

When a museum or archive receives a proposed donation or acquisition, staff can generate the agreement from Axiell and send it to OpenText Core Signature for legally binding approval by donors, legal representatives, and internal approvers. Once signed, the executed document is returned to Axiell and linked to the collection record.

• Speeds up acquisition approvals
• Creates a complete audit trail for provenance and ownership
• Reduces risk of misplaced paper agreements

2. Rights and Reproduction Permission Management

Data flow: Axiell to OpenText Core Signature, then back to Axiell

For images, manuscripts, or artifacts requiring usage permissions, Axiell can trigger signature workflows for rights holders, artists, estates, or publishers. Signed licenses and reproduction permissions are stored against the relevant object or media record in Axiell, making it easier for staff to verify what can be published, loaned, or reused.

• Improves compliance with copyright and licensing terms
• Supports faster publication and exhibition planning
• Centralizes permission records with collection metadata

3. Loan Agreement and Condition Report Approval

Data flow: Bi-directional

For outgoing or incoming loans, Axiell can prepare loan documentation and condition reports, then route them through OpenText Core Signature for approval by curators, registrars, lenders, and borrowing institutions. Signed documents are returned to Axiell and attached to the loan record for future reference.

• Shortens loan processing cycles
• Ensures all parties approve the same controlled document version
• Improves accountability for object movement and condition tracking

4. Internal Approval of Deaccession or Conservation Actions

Data flow: Axiell to OpenText Core Signature, then back to Axiell

When an institution needs formal approval for deaccession, conservation treatment, or disposal decisions, Axiell can generate the supporting documentation and send it to OpenText Core Signature for review and sign-off by governance committees or senior leadership. The final signed approval is stored in Axiell as part of the object history.

• Supports policy-driven decision making
• Provides defensible records for audits and compliance reviews
• Reduces delays caused by email-based approvals

5. Donor Consent and Personal Data Authorization

Data flow: Axiell to OpenText Core Signature, then back to Axiell

Libraries and archives often collect personal data, oral histories, or donor restrictions that require explicit consent. Axiell can initiate consent forms through OpenText Core Signature, allowing donors, contributors, or interview subjects to sign usage and privacy authorizations electronically. Signed consent is then linked to the relevant record in Axiell.

• Strengthens privacy and consent management
• Improves readiness for data protection audits
• Makes consent status visible to collection and access teams

6. Exhibition and Publication Release Approvals

Data flow: Axiell to OpenText Core Signature, then back to Axiell

Before an object image, archival item, or catalog entry is published online or used in an exhibition catalog, Axiell can send release forms or internal approval documents to OpenText Core Signature. Curators, rights managers, and communications teams can sign off electronically, and the approved release is stored with the item record.

• Accelerates public access workflows
• Reduces the risk of publishing unapproved content
• Creates a clear approval history for each asset

7. Policy Acknowledgement for Staff and Volunteers

Data flow: OpenText Core Signature to Axiell, or bi-directional

Institutions can use OpenText Core Signature to collect signed acknowledgements for collection handling policies, confidentiality agreements, and volunteer onboarding documents. Axiell can store the signed records alongside staff-related or operational documentation where needed, supporting consistent governance across departments.

• Standardizes onboarding and policy compliance
• Provides evidence of acknowledgement for audits
• Reduces administrative effort for HR and collections teams

Overall, integrating OpenText Core Signature with Axiell helps cultural heritage organizations replace paper-heavy approval processes with secure digital workflows while keeping signed records connected to the collection, rights, and preservation context that staff need for daily operations.