Syncing Content and Metadata
Overview
CAM does not store an organization’s documents at any point. CAM only stores metadata about the documents, workspaces, sites, Teams, channels, and folders. Whenever content needs to be stored, either temporarily using Content Mover or for a longer-term period with Business Continuity, CAM uses a cloud storage bucket controlled by the organization. Litera provides a small piece of code to be configured on that cloud storage bucket to provide the integration needed for content sync or storage. Currently, CAM supports AWS S3 buckets as an option as well as Azure
Syncing metadata to CAM for Business Continuity on AWS
Syncing content using Content Mover on AWS
In both instances, all documents are stored in the organization’s AWS S3 bucket and the synching happens between AWS S3 and the DMS systems.
Best Practice- Don’t use invalid characters in the metadata creation or mapping.
|
|
---|---|
CAM can sync documents in the organization’s DMS to the AWS S3 bucket so if the organization’s cloud DMS goes down, users can access their documents securely through CAM using a one-time password. | |
Users can move documents stored in M365 Teams and Channels to the DMS, or from the DMS to Teams to facilitate easy access for the end-user to access documents when needed while providing governance around content and ensure content is moved to the desired DMS. | |
Setting up for Azure |
Let's Connect📌
☎ +1 630.598.1100
☎ +44 20 3880 1550
📧 support@litera.com
💻 https://www.litera.com/support/
📝 Support is available:
4 am - 8 pm US Eastern
(9 am - 1 am GMT/BST
7 pm - 11 am AET) on normal business days (excluding holidays)
© 2024 Litera