This page will describe how to configure Cognitive Services together with Digizuite. The following subjects are covered:
...
Note: This guide shows you how to configure the AI feature on the Azure Portal: How to add AI tagging (on Azure hosted environment), APP service/wiki/spaces/PSBOK/pages/702939141 (Lasse Brønnum Brønsholt (Unlicensed) )
...
- Add the Computer Vision service to your account through the Azure portal as illustrated below:
- Select a pricing tier that fits your consumption. After adding the service, it will appear in your dashboard.
Pricing Details
Pricing details can be found here: https://azure.microsoft.com/en-us/pricing/details/cognitive-services/computer-vision/
Please note the following, as stated on the Cognitive Services pricing page:
"For Recognize Text each POST call counts as a transaction. All GET calls to see the results of the async service are counted as transactions but are free of charge. For all other operations, each feature call counts as a transaction, whether called independently or grouped through the Analyze call. Analyze calls are used to make calling the API easier, but each feature used counts as a transaction. For instance, an Analyze call containing Tag, Face, and Adult would count as three transactions."
The features that are supported are shown below here. The number of transactions is dependent on the number of the desired visual features. This means that if the system is configured with all of them, then it will be 7 transactions per asset.
ImageType = 0,
Faces = 1,
Adult = 2,
Categories = 3,
Color = 4,
Tags = 5,
Description = 6
The default configuration for the service is set up to only analyze for Tags. This will mean that we out-of-the-box will have 1 transaction per asset.
Endpoint & subscription key
It's important for the Digizuite AI Service to have the endpoint and subscription key. These can be found when selecting the service in Azure as shown below:
...
| Info |
|---|
Make sure that the resource you take the information from is of the API type "Computer Vision". See image above for more info ↑ |
Facial recognition
| Info |
|---|
Using this feature involves storing biometric data on the user. As this is considered especially sensitive personal data, in case this feature is enabled in the EU, the GDPR needs to be taken into consideration in order to remain the part of the data processing agreement (DPA). |
...
| Info |
|---|
Make sure that the resource you take the info from, is of the API type "Face" (Can be found in the "Overview" of the resource under API type) |
Video Transcription
In order to use the Video Transcription feature of the Cognitive Services, a videoindexer subscription key must be acquired and configured.
...
| Panel |
|---|
"ComputerVisionDetails": { "subscriptionKey": "..................................", "AzureEndpointUrl": "https://northeurope.api.cognitive.microsoft.com/", "FacesKey": "..................................",, "FacesEndpointUrl": "https://digi-faces-dev.cognitiveservices.azure.com/", "FacesPersonGroup": "digipersons", "VisualFeatures": "Tags", "VideoIndexerKey": "..................................",, "VideoIndexerWatcherInterval": 180 } and "TranslationApi": { |
The subscription key is one of the 2 Manage keys in the Azure portal, it is not the Subscription ID.
If you want AI translation, then the `SubscriptionKey` has to be provided.
...
Automatic translation of metafields is available if Translation Services have been configured as mentioned above and if your field is either a "string" or "note" field. To make the field be translated automatically, you need to change the "Autotranslate_GOOGLE" column in the table dbo.item_metafield for the metafield to true in the database. There is currently no UI available to do this.
You can use one of the following scripts to change "Autotranslate_GOOGLE" to true.
| Code Block | ||||
|---|---|---|---|---|
| ||||
update item_metafield set autotranslate_GOOGLE = 1 where item_metafieldid = 50182 |
| Code Block | ||||
|---|---|---|---|---|
| ||||
update item_metafield set autotranslate_GOOGLE = 1 where item_metafieldid in (50182, 50495, 50181) |
Don't forget to replace the metafield ID(s).
After the field has been changed, recycle at least the LegacyService and main DAM app pools.
...