Flagging service

The flagging service automatically identifies and flags the best Content Items for any purpose within your Content Platform. It can be tailored to customer specific needs and criteria with guidance from Content Platform experts. Key benefits include:

• Efficiency & Time Savings: Automatically flags optimal images, avoiding manual selection.

• Optimized Quality: Can flag Content Items for web (fast loading, correct formats) and print (high resolution, color profiles).

• Brand Consistency: Ensures flagged Content Items follow brand guidelines for color, lighting, and composition.

• Compliance: Meets technical requirements (color spaces, resolution, formats) for web and print.

• Error Prevention: Reduces mistakes like using low-res images for print or oversized images for web.

• User-Friendly & Scalable: Integrates with workflows, improves search/filtering, and scales with content libraries.

• Future-Proof: Easily adapt your configuration as formats and technologies evolve.

Example for web images

In this example I want to have the flagging service identify the best images I have of a museum exhibit for use in an article about a new exhibition.

I create a Layer with a text field that has a display pattern for calculated values. The display pattern code checks if the Content Item has a file extension that is a variation of .jpeg and horizontal and vertical resolution are 72DPI. Both of these values are read out of your image on ingestion into the Content Platform. This is a highly configurable .liquid template so you can of course add in as many criteria as is required for your business case.

Example .liquid display pattern for calculated values

{% assign imageMetadata = outerData.data.imageMetadata %}
{% assign validExtension = ".webp" %}
{% assign fileExtensionLowercase = imageMetadata.fileExtension | downcase %}

{% if imageMetadata.horizontalResolution == 72 and imageMetadata.verticalResolution == 72 and fileExtensionLowercase == validExtension %}
  true
{% else %}
  false
{% endif %}

We also configure the following in our configuration files for this use case:

{
  "identifierTagPath": "basicInformation.mObjects",
  "isMultiTagbox": false,
  "identifierListSchemaId": "basicInformation",
  "flagLayerId": "FlaggingLayer",
  "flagFieldId": "bestImageForWeb",
  "fields": [
    {
      "fieldPath": "flaggingLayer.highestWeighted"
    },
    {
      "fieldPath": "flaggingLayer.secondHighestWeighted"
    },
    {
      "fieldPath": "flaggingLayer.thirdHighestWeighted"
    },
    {
      "fieldPath": "audit.creationDate",
      "sortDirection": "Asc"
    }
  ]
}

The fields are then considered in order from top to bottom. All the Content Items with the same - in this example - Museum Plus object number are evaluated. If the first field is true on one of these images it will be flagged as best for web.

In case multiple Content Items have the same qualities or no Content Items match those qualities we also take the creationDate timestamp into account. You can configure if you would like the newest or oldest Content Item in the system to receive the best for web flag. Per default the oldest is taken.