Skip to main content
MediaBeacon University

Upload, Download, and Metadata in the MediaBeacon S3 Integration

MediaBeacon version 2018.1 and newer support S3 storage with metadata in MediaBeacon.

Version: 2018.1+

When users store assets using the S3 integration with MediaBeacon, the file is stored in the S3 bucket while the metadata sits on the MediaBeacon system. The metadata is held in a placeholder asset on MediaBeacon and is associated to an object on S3 through a MediaBeacon XMP field. Metadata is written to the placeholder and does not touch the object on S3. When an asset is downloaded, it can either be downloaded with or without the metadata.

  • Without Metadata: Using the Quick Download option, the asset will download directly from S3 without the metadata. This option is ideal when speed and scaling with a minimal of webheads is a desired factor since the web browser downloads directly from S3.
  • With Metadata: Using the Conversion Download option, the asset will download through MediaBeacon with the metadata attached. This option is typically slower because the download happens through Mediabeacon to S3, where the metadata the asset had originally when it was uploaded syncs to the asset. These actions happen before the web browser downloads the asset.
    Note: Quick Downloads with metadata can be forced using the system property <mb.s3.xmp.sync.quickdownload=true>, however the system's architecture will need to be built differently to support concurrency of download./li>

After the S3 and MediaBeacon integration is set up, the S3 Upload and Download functions perform in the following sequences, respectively.

S3 Upload

  1. User drags and drops file to MediaBeacon.
  2. The file is uploaded directly into an S3 bucket.
  3. Placeholder asset creation starts.
  4. Once the placeholder asset is created, it is imported and re-downloaded from S3 to the MediaBeacon Preview server (or core) for previewing by using the placeholder asset's ID.
  5. Metadata from the original asset is fetched and written into the placeholder at this step as well
  6. At this point:
    1. The placeholder is in MediaBeacon with the real (including hi-res) previews.
    2. The real asset is in S3.
    3. They are associated by an object key in the placeholder's metadata.
       

S3Upload.png

S3 Download with Metadata

  1. A conversion download is requested from the web interface.
  2. MediaBeacon core (or preview node) downloads the asset from S3.
  3. XMP from the placeholder assets is stamped onto the downloaded S3 Object.
  4. MediaBeacon sends the file to the user and the download is completed.

S3Download.png

S3 Download without Metadata

  1. A Quick Download is requested from the web interface.
  2. MediaBeacon downloads the asset from S3 with only the original metadata and download is completed.
    1. If <mb.s3.xmp.sync.quickdownload=true> is set, the asset will be downloaded and metadata synchronized prior to the download starting.
  • Was this article helpful?