As a developer you need to identify the right assets and content to display within websites, applications, and other channels. To provide you with the required search capabilities, Acoustic Content is built on the powerful enterprise search platform Solr.

When your editors create, update, and publish assets or content, the hub stores related data in search collections. When your editors delete assets or content, the hub removes the corresponding data from the underlying search collections. Additionally, Acoustic Content tracks your categories, content types, image profiles, and taxonomies in its authoring search collections.

The data from the search collections includes fields that you can use to retrieve the items that you need. For example,

name – Contains the name of an item.

description – Contains the description of an item.

classification – Describes the type of item, for example, asset, category, content, content-type, image-profile, or taxonomy.

created – Contains the creation date of the item.

creator – Contains the name of the user that created the item.

lastModified – Contains the last modification date of the item.

lastModifier – Contains name of the user that last modified the item.

categories – Contains a list of all category selections for the asset or content.

tags – Contains the list of tags.

assetType – If the result is an asset, the value is document, file, image, or video.

mediaType – If the result is an asset, the value is the media type.

For a complete list, refer to the search REST API documentation that is available in the API Explorer.

As a developer, you can access the indexed items by using the REST APIs. To allow for a separation of the authoring system and the delivery system, two different Acoustic Content APIs are available for search.

2 comments on"Searching content"

  1. How is the search feature in WCH? Does it offer Enterprise search? How is the indexing limitation of Solr engine addressed in WCH?

    • Matthias Falkenberg July 27, 2017

      Hello vivek,
      Would you mind to please rephrase your questions and provide a tad more details on what you are looking for?
      For the time being, I can offer you the following answers:
      (1) WCH search is great. It caters to the needs of content authors as it gives them protected access to the authoring data. At the same time, it allows your developers to integrate published content easily into your applications without the need of authentication. Of course, we have rich set of REST APIs at your disposal. You can read about it at Follow the link and navigate to “Documentation > Authoring search” or “Documentation > Delivery search”. By the way, we are just about to rework the API documentation. Among others, we will add further examples to allow you to become familiar with WCH search quickly.

      (2) At present, the data that we index with WCH search is data from only WCH. That is, WCH does not offer a federated search across WCH and additional other services that you use. However, using the REST APIs, you could implement a federated search service that combines search results from WCH and other backends in one search result. While that is not the same as having a single search index for all of your enterprise data, it might be an option for you to consider.

      (3) To answer your question properly, would you mind to please be more specific about the limitation that you refer to?

      Thank you and kind regards,

Join The Discussion

Your email address will not be published. Required fields are marked *