SHARE best practices

This chapter provides two use case examples of SHARE best practice setups.

Use case 1

Setup

  • A CENTRAL CLOUDFLOW in the cloud.
  • Two production sites: SITE 1 and SITE 2. Both sites have two File stores:
    • RW (Read and Write): this is a File store with read and write permissions and where the operators work on the files.
    • RO (Read Only): this is a File store with read permissions only and where the operators save the files when they are finished. This File store is synchronized with the central CLOUDFLOW site through a synchronization mapping.

Example of a workflow

All production files are stored on the CENTRAL CLOUDFLOW. Because of the synchronization mapping, all the files are identical on the CENTRAL CLOUDFLOW, File store RO in SITE 1 and File store RO in SITE 2.
  1. An operator in SITE 1 is working on file A on File store RW in SITE 1.
  2. When finished, the operator checks in (copies) file A on File store RO in SITE 1.
  3. Through the synchronization mapping, file A is automatically updated on the CENTRAL CLOUDFLOW and File store RO in SITE 2 as well.
  4. An operator in SITE 2 wants to work on file A. To do that, the operator checks out (copies) file A to File store RW in SITE 2.
  5. When finished, the operator checks in (copies) file A on File store RO in SITE 2.
  6. Through the synchronization mapping, file A is automatically updated on the CENTRAL CLOUDFLOW and File store RO in SITE 1 as well.

Use case 2

In this example there are 2 sites: Site A and Site B. An operator in Site A enters a New Order in the Management Information System (MIS). Consequently, a job folder is automatically created on the File store in Site A, containing the files.

The operator wants to outsource certain jobs to Site B, for example the Artwork, Images, pdfQCFiles and Technical jobs. Therefore, the operator creates a Production Order for these jobs in the MIS and marks them to be outsourced. Through the sync spec, the outsourced jobs are synchronized to Site B. This means that the job folders and files of these outsourced jobs are copied to and synced with the File store in Site B. The jobs that are not outsourced are not accessible in Site B.

The sync spec keeps the outsourced jobs synchronized in Site A and Site B. This means that the files of the outsourced jobs are identical in Site A and Site B during the editing phase of the files.

When the operator in Site B is finished, the job is marked as done in the MIS in Site B. Consequently, the folders that were created on the File store in Site B are deleted as soon as the synchronization of the files is finished. The updated files are now only accessible in Site A.