Prerequisites

About this Feature

Historically, Strawberry extracted nearly all available metadata from media assets and stored it directly in the database. Over time, this led to significant database bloat, as the system processed vast amounts of information—primarily EXIF and XMP metadata—that was rarely required for daily operations like searching. To optimize performance and storage, Strawberry 7.0.4 introduced the Technical Metadata Index List. This feature allows administrators to define exactly which metadata fields are indexed and stored, ensuring the system remains lean and responsive.

Components of the Index List

The Technical Metadata Index List is categorized into three distinct areas to balance system stability with user customization:

1. Technical Metadata Index List (Factory)

This list contains the core metadata properties required for Strawberry’s essential operations.

  • Locked Settings: These entries cannot be removed or modified to ensure system stability.
  • XML Exception: Metadata originating from XML sidecar files is always written to the database. Because sidecar data is inherently unique to a specific workflow, the system treats it as essential information.
  • Defaults: Default Metadata Properties in the Technical Metadata Index List (Factory):
width, height, writing_application, codec, duration, album, title, artist, performer, genre, year, video.track_count, audio.track_count, shot_at, imported_at, standard, colorspace, display_aspect_ratio, bit_depth, format_commercial, language_code, scan_type, framerate, timecode_framerate, start_timecode, format, sample_rate, audio.channels, essence_type, resolution_id, sequence_names, video.aspect_ratio, clip_name, video.codec, audio.codec, material_package_uid, videotracks, audiotracks, essence_label, edit_rate, track_number, audio.sample_rate

2. Technical Metadata Index List (Custom)

The custom list includes all metadata properties manually added to the legacy Technical Metadata Allow List.

  • Legacy Integration: In versions prior to 7.0.4, the “Allow List” determined which metadata was searchable. The list included some properties that were pre-populated by Projective.
  • Automatic Migration: Any metadata existing in the “Allow List” before the 7.0.4 update is automatically carried over to the Custom section of the new Index List.
  • Metadata Mapper: Any non-XML files used in a metadata mapper before the 7.0.4 update are automatically carried over to the Custom section of the new Index List.
  • Defaults: Default Metadata Properties in the Technical Metadata Index List (Custom):
title, album, artist, genre, format, audio.codec, video.codec, video.commercial_codec, codec, width, height, make, model, sequence_names, dc:subject[1], dc:description[1], dc:creator[1], photoshop:Country, Iptc4xmpCore:CountryCode, xmp:CreatorTool, dc:title[1], dc:format, software

Technical Metadata Search List

While the Factory and Custom lists define what is indexed in the database, the Search List defines which of those indexed properties are added to the search index.

  • Granular Control: This allows for scenarios where certain metadata must be indexed for technical reasons but does not need to be searchable.
  • Performance Optimization: By keeping the search index focused only on necessary fields, search speed and overall system performance are significantly enhanced.
  • Migration Safety: When updating to Strawberry 7.0.4 or later, all metadata that have been present in the legacy Technical Metadata Allow List are applied to the search index. This allows for an uninterrupted workflow after the update.

The search index is automatically updated nightly.

Need more help with this?
Visit the Projective Support Websites

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.