The Spring 2017 releases of the Adobe video tools run great with MatrixStore

Adobe Object Matrix

Sharing Content With Local and Global Teams using Adobe XMP Metadata

Metadata is key to sharing, exploiting and distributing content. Automatically extracting that content, indexing and making it searchable via an API is a key tenet of implementing a Digital Content Governance (DCG) strategy. Many formats of content get delivered with important and valuable metadata embedded in the content. Having a storage solution that understands those formats and that can automatically index the metadata means people or further processes are not required to perform the task. MatrixStore currently supports AS11, AS10, EXIF and also Adobe XMP metadata.

XMP Metadata Extraction, Adobe

Using XMP as an example: XMP files allow you to transfer your image metadata, ratings, tags, keywords, geolocation, and other attributes about the image outside of the actual JPG, CR2, or other file type. The XMP format was created by Adobe to standardize how metadata is stored and transferred and is a standard used by many news entities, photographers, photojournalists, image resellers, etc. The example below shows an organisation that is creating content in remote locations and archiving that content in a centralised DCG platform:

  • Using any of the latest Adobe Creative Cloud applications, media managers at remote locations add XMP metadata to the content they are creating.
  • That content is sent to a central MatrixStore repository into a vault that is configured for XMP metadata extraction.
  • MatrixStore PiP extracts the metadata automatically when the cluster is not performing digital preservation tasks. The metadata is stored as part of the object within MatrixStore and indexed to enable search operations.
  • The data is not delayed for pre-processing nor moved for post-processing. It is processed in place, where it lives.
Adobe Object Matrix PiP

MatrixStore PiP Benefits

  • Streamlines processes for sharing content across local or global teams.
  • Extracts metadata from ingested assets and makes it available for search via a fast and powerful distributed database.
  • Makes the metadata available via an API and shares metadata with technology partner’s applications.
  • Because the archive’s content is processed by local CPUs within direct attached servers there is no need to move petabytes of content in and out of the archive to perform post-processing.
  • Provides a flexible, scalable and extensible framework that allows advanced data analytics and advanced post processing algorithms to be carried out.

Find out more: Process in Place (PiP)