Curations Guide

Each Engine contains a Curations UI.

This will allow any person - developer or otherwise - to curate a result set.

To begin, click into Curations.

Curations - A view without curations.

From there, click on Create new Curation.

You can provide one or more queries.

The idea of a Curation is to curate the result set of a given query.

And so, we must supply the query first to receive its result set.

You can enter one, or multiple queries. In this case, we want to curate the results for the "mountains" query.

Curations - Enter a query to curate its result set.

Once at least one query has been provided, results of that query will appear as a list of organic results.

Organic results have nothing promoted and nothing hidden, they reflect the current result set for that query.

Curations - The organic query appears. Organic queries do not have any hidden or promoted items.

Now, to promote a result.

We want Rocky Mountain National Park to be the first result when a user queries for "mountains".

We can either:

We can promote multiple documents and rearrange the order of our promoted documents.

If we promoted 3 documents, we can order them however we would like.

Click Demote All to return all promoted results back to the organic result set.

Curations - Promoting a result. You can drag and drop, or click the star.

What if we need to hide a document?

It seems appears "Mesa Verde National Park" is closed for maintenance.

We should hide the document so that it no longer appears within the result set.

To do so, click on the eye icon:

Curations - Hiding a result. Click the eye icon.

All hidden documents collapse underneath the organic results in their own section.

You can view your hidden results.

Click Restore All to unhide them:

Curations - Hidden documents collapse underneath the organic result set.

If you chose multiple queries, or want to curate another query, click Manage Queries.

From there, one can add or select a new query.

Selecting a query changes the result set to match that query.

This can be used to curate result sets for similar concepts that are not synonyms, like "big mountains", "small mountains", "mounds", and so on.

Curations - Curate different queries together if they share a logical thread.

The moment you promote or hide a document, the new result set will be active.

Anyone who uses the query that you have curated will receive your newly minted result set.

You can Restore Defaults to revert all of your changes, or delete the curation from the main curations view.

The App Search API provides full control over Curations.

When you craft a curation you must include one or more queries within an array.

That array of potential queries, along with the documents that fit the promoted and hidden parameters, form a curation.

In this way, users who query for banana, bonana and nanner will receive the same promoted items and not the same hidden items.

This set, this grouping, is considered a curation with its own unique identifier.

The id of a curation is serialized via BSON.

The id of a document is serialized via BSON as well, but you can supply your own id value.

A response might look something like this:

{
  "id": "cur-a5b6c7",
  "queries": [
    "banana", "bananana", "bonana", "nanner"
  ],
  "promoted": [
    "doc-123", "doc-a2b3c4", "doc-456"
  ],
  "hidden": [
    "doc-a9b87c", "doc-789", "doc-a7b6c5"
  ]
}

You may expect a curation to always be in its curated position, regardless of sort.

But that’s not always the case.

It’s helpful to understand cases where a curation will and will not have priority when using sorting.

Curations are applied when there is...

Curations are not applied when there is...

Your Curations can become mighty tools in improving the relevance, and thus the overall experience, of search queries. Business goals, too, as you can get your visitors where you would like them to be. If you want to take a deep look into how users are interacting with your engines, checkout: