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

Efficiency & time savings: Automatically flags optimal images, eliminating the need for manual selection.

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

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

Error prevention: Reduces mistakes, such as using low-resolution images for print or oversized images for the web.

Example for web images

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

I created a Layer with a text field that has a display pattern for calculated values. The display pattern code checks whether the Content Item has a file extension and a width and height within the ranges we prefer. These values are extracted from your image upon ingestion into Fotoware Alto. This is a highly configurable .liquid template, so you can, of course, add in as many criteria as are 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 %}
{% assign minWidth = 1000 %}
{% assign maxWidth = 1200 %}
{% assign minHeight = 700 %}
{% assign maxHeight = 1000 %}
{% if imageMetadata.width >= minWidth and imageMetadata.width <= maxWidth and imageMetadata.height >= minHeight and imageMetadata.height <= maxHeight 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 evaluated 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 the web.

If 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 whether the newest or oldest Content Item in the system should receive the best-for-web flag. By default, the oldest is taken.