1. Multi site Vidispine Bootcamp

2. Overview Used to synchronize entities between geographically separated Vidispine instances (sites) Synchronization is rule based File transfers can be executed using HTTP or using Signiant (Aspera to be supported)

3. Example use cases Syncing all assets between sites. Every site contains everything Syncing assets with a specific metadata field set – relevant to a specific site

4. Site rules Site rules can be applied to: –Items (individual or all) –Collections –Libraries –User groups –Users

5. Rules cont’d A site rule can specify –Which site to sync to –Which shapes to synchronize –Whether to sync metadata –Whether to sync ACLs –Whether to sync a user’s groups

6. Example site rule POST API/item/site-rule NY true original This rule will sync all items to the site NY Metadata, access and the original files will be synced

7. Syncing behaviour If a site rule has been defined from site A to B, those entities will be synced both ways Files are synced separately from everything else

8. The SiteCruncher This is the basic flow: –Every minute the cruncher checks which entities have been changed –A changeset is created for every changed entity –Changesets are transferred to remote sites –New external changesets are merged to the local entities

9. Files The changesets include references to files that should be synced The SiteFileCruncher checks every minute if there are file entities awaiting sync Files awaiting sync are requested from the remote sites