You configure your relevance ranking strategy by exporting the entire search configuration for the cloud application, editing the part of the exported configuration that applies to the relevance ranking strategy, and then re-importing the entire search configuration. To do this, follow these steps:

  1. Execute the following GET endpoint, which exports the entire search configuration for the cloud application in a ZIP file:

    GET /gsadmin/v1/cloud.zip

    For more information about the GET endpoint, see “Export all configuration in ZIP format“.

  2. Back up the ZIP file before opening it or extracting any of its contents.

    IMPORTANT: When you re-import the edited search configuration, you overwrite all existing search configuration. For this reason, it is important to keep a back-up of the original configuration.

  3. Unzip the zip file and extract the JSON file containing the search configuration.

  4. Open the JSON file containing the search configuration and find the relRankStrategy attribute of the resultsList object, in the contentItem object named “Guided Search Service”.

    Note: If the resultsList object or the relRankStrategy attribute is not defined, you must add them in the location shown in this example.

  5. Edit the value of the relRankStrategy attribute to specify the relevance ranking modules that you want the strategy to comprise. The order in which you specify the modules is significant. For more information, see “Understand how relevance ranking modules sort results“.

  6. Zip up the entire search configuration, including the edits that you made to the configuration of the relevance ranking strategy.

  7. Execute the following POST endpoint, which imports the search configuration in the ZIP file:

    POST /gsadmin/v1/cloud.zip

  8. If your relevance ranking strategy does not produce that results that you intended, make a copy of your backed up search configuration, edit the relevance ranking strategy in the copy to produce the intended results, and import the copy.


Copyright © 1997, 2017 Oracle and/or its affiliates. All rights reserved. Legal Notices