Find Visually Similar

December 31, 2019

With the release of 19.4.3, OCE introduced a new feature named "Find Visually Similar". This functionality can add a lot of value to all asset repositories with Digital Assets (images).

This feature only affects Digital Assets. When Finding Visually Similar Digital Assets, assets are filtered to exclude content items and limit the results to only images that are similar to the image originally selected.

Documentation: Search, Filter and Sort Assets

To use Find Visually Similar the Asset Repository must have Smart Content Enabled. Here is what an Asset Repository might look like if Smart Content is not yet enabled.

Learn more about Smart Content

To turn on Smart Content simply toggle the switch to the right. Once enabled, it will take some time for OCE to process the items already existing in the Asset Repository. How long? It would depend on how many Digital Assets already exist. Generally, even small repositories take fifteen minutes or more.

If Smart Content is NOT enabled end users may get the message Smart Content is not enabled for the repository when they attempt to invoke the Final Visually Similar menu option.

Finding Similar Images

Smart Content is turned on. The Assets are processed. End users can now find images similar to their selected image! For example, this is what searching for similar dog pictures may look like:

Selecting Source Image

  1. Select the source image
  2. Click Find Visually Similar

Review Results

Note how the selected image is now listed first. The visually similar images then follow directly after the source image.

API First Product Development

The Find Visually Similar feature is a great example of Oracle’s commitment to executing an API First development approach. As a developer, you can take advantage of this same technology through the REST API. It is even documented: Content Management REST API

When executing this functionality through the OCE Web Interface this same endpoint is called with parameters like this:


Breaking that down, the query string parameters look like this:

limit: 100
offset: 0
totalResults: true
includeAdditionalData: true
links: none
fields: all
returnMaster: true
q: repositoryId eq "FB454E95003618226370C2F6618C5706589383725339" AND (fileGroup eq "images")
© 2020 Jason Stortz (version 20200322-120514)