FTP - Axiell Integration and Automation

Common Integration Use Cases Between FTP and Axiell

• Bulk import of digitized collection assets into Axiell
  Flow: FTP to Axiell
  Digitization teams or external scanning vendors place large batches of image, PDF, audio, or video files on an FTP/SFTP server. Axiell ingests the files and associated metadata to create or update collection records. This is useful for museums, libraries, and archives managing high-volume digitization projects where files are too large or numerous for manual upload.
• Automated metadata delivery from Axiell to downstream file repositories
  Flow: Axiell to FTP
  Axiell exports structured metadata files such as CSV, XML, or JSON to FTP for consumption by digital asset management systems, preservation platforms, or external service providers. This supports scheduled publishing of catalog data, rights information, and descriptive records without manual intervention.
• Preservation package transfer to long-term storage
  Flow: Axiell to FTP
  When collections are approved for archival preservation, Axiell can generate preservation packages containing master files and metadata, then transfer them via FTP to a secure storage location or preservation vendor. This helps institutions maintain a controlled handoff from active collection management to long-term retention workflows.
• Receipt of external donor or partner submissions for accessioning
  Flow: FTP to Axiell
  Donors, partner institutions, or field teams upload large media files and descriptive spreadsheets to an FTP drop zone. Axiell imports the submissions for review, accessioning, and cataloging. This is especially valuable for archives receiving oral histories, photographic collections, or research datasets from multiple contributors.
• Scheduled synchronization of collection media with public access platforms
  Flow: Bi-directional
  Axiell can send approved media and metadata to FTP for publication workflows, while updated derivatives or corrected files can be returned from FTP into Axiell. This enables controlled synchronization between internal collection records and external discovery portals, reducing version drift and improving public access accuracy.
• Batch update of rights and access control data
  Flow: FTP to Axiell
  Legal, licensing, or curatorial teams prepare bulk rights updates in spreadsheet form and deliver them through FTP. Axiell imports the updates to apply embargo dates, usage restrictions, and access notes across large record sets. This is useful when rights changes affect many objects at once, such as exhibition loans or donor agreements.
• Disaster recovery and offline export of critical collection data
  Flow: Axiell to FTP
  Axiell periodically exports collection metadata, object relationships, and associated digital files to FTP as part of a backup or disaster recovery process. This provides an operational safeguard for cultural heritage institutions that need secure, repeatable offsite copies of essential records and assets.