Open topic with navigation

# Sort

By default results are displayed in order of relevance, and if several documents have the same relevance, their display order is determined by their `autn:docid` (document ID) number. You can modify the order in which result documents are displayed by typing one of the following sorting options:

`Off` | Results are displayed unsorted.
`AutnRank` | Results are displayed in order of the value in their `AutnRankType` field. The document with the highest `AutnRankType` field value is listed first.
`Cluster` | If you have added `Cluster``=true` to the action, the `Cluster` sort option allows you to display results in order of cluster (in decreasing cluster ID order).
`Database` | Results are displayed in order of database number (in increasing order). The database numbers are defined in the IDOL Server configuration file.
`Date` | Results are displayed in order of their date (the date contained in the results' `DateType` fields). The most recent document is listed first. If several documents have the same date, their display order is determined by their `autn:docid` (document ID) number (the highest `autn:docid` is listed first).
`Distcartesian` | Results are displayed according to their distance from a specified point using Cartesian coordinates (X/Y). The option has the following format:
    &sort=Distcartesian{coordX,coordY}:X:Y
where, `coordX` is the specified x coordinate. `coordY` is the specified y coordinate. `X` is the document field containing the X coordinate. `Y` is the document field containing the Y coordinate. Note: Two fields must be specified and must be given in the order X:Y. The fields must be of `NumericType`. For example:
    &sort=Distcartesian{10,11}:X:Y
In this example, documents are sorted according to their distance from the point (10,11). The “position” of a document in this example is contained in the fields X and Y, respectively.
`Distspherical` | Results are displayed according to their distance from a specified point using spherical coordinates (latitude/longitude). The option has the following format:
    &sort=Distspherical{lat,long}:Latfield:Longfield
where, `lat` is the specified latitude. Latitude positions south of the equator must be specified as negative. `long` is the specified longitude. Longitude positions west of the Greenwich Meridian must be specified as negative. `Latfield` is the document field containing the latitude. `Longfield` is the document field containing the longitude. Note: Two fields must be specified and must be given in the order `latitude:longitude`. The fields must be of `NumericType`. For example:
    &sort=Distspherical{37.75,-122.4}:Lat:Long
In this example, documents are sorted according to their distance from San Francisco (37.75N,122.4W). The latitude and longitude “position” of a document in this example is contained in the fields `Lat` and `Long`, respectively.
`DocIDDecreasing` | Results are displayed in order of their `autn:docid` (document ID) number. The document with the highest `autn:docid` is listed first.
`DocIDIncreasing` | Results are displayed in order of their `autn:docid` (document ID) number. The document with the lowest `autn:docid` is listed first.
`fieldName:sortMethod` | Results are sorted according to the value of a specified field. Note: Documents in which the specified field is empty are not returned. `fieldName`. Specify the name of the IDOL field whose value you want to determine the order in which the results are displayed. `sortMethod`. Type the sorting method that you want to apply to the field `fieldName`. The following sorting methods are available:
alphabetical | The display order of results is determined by the string contained in `fieldName`. Results are displayed in alphabetical order. Note: Distributed Action Handler can perform the sorting process more quickly if `fieldName` is a `SortType` field.
decreasing | The display order of results is determined by the number or string contained in `fieldName`. The result with the highest number or last in alphabetical order is listed first. Note: For `NumericType` fields, this method is equivalent to `numberdecreasing`; for `SortType` fields, this method is equivalent to `reversealphabetical`.
increasing | The display order of results is determined by the number or string contained in `fieldName`. The result with the lowest number or first in alphabetical order is listed first. Note: For `NumericType` fields, this method is equivalent to `numberincreasing`; for `SortType` fields, this method is equivalent to `alphabetical`.
numberdecreasing | The display order of results is determined by the number contained in `fieldName`. The result with the highest number is listed first. Note: Distributed Action Handler can perform the sorting process more quickly if `fieldName` is a `NumericType` field.
numberincreasing | The display order of results is determined by the number contained in `fieldName`. The result with the lowest number is listed first. Note: Distributed Action Handler can perform the sorting process more quickly if `fieldName` is a `NumericType` field.
reversealphabetical | The display order of results is determined by the string contained in `fieldName`. Results are displayed in reverse alphabetical order. Note: Distributed Action Handler can perform the sorting process more quickly if `fieldName` is a `SortType` field.
`Random` | Results are displayed in random order.
`Relevance` | Results are displayed in order of their relevance (the document with the highest is listed first). If documents have the same relevance, their display order is determined by their `autn:docid` (document ID) number (the highest `autn:docid` is listed first).
`ReverseDate` | Results are displayed in order of their date (the date contained in the results' `DateType` fields). The oldest document is listed first. If several documents have the same date, their display order is determined by their `autn:docid` (document ID) number (the highest `autn:docid` is listed first).
`ReverseRelevance` | Results are displayed in order of their relevance (the document with the lowest is listed first). If documents have the same relevance, their display order is determined by their `autn:docid` (document ID) number (the lowest `autn:docid` is listed first).

If you want to sort results using several criteria, you can specify these criteria in order of precedence, as follows:

    sortOption1+sortOption2+...

where `sortOptionN` specifies one of the available sorting options.

Note: if you specify `Cluster` as one of multiple sorting options, it automatically takes precedence over the other sorting options, regardless of its position in the list.

For example:

    &Sort=Relevance+DRETITLE:alphabetical+Date

In this example, results order first by `Relevance`, then alphabetically by `DRETITLE`, and finally by `Date`.

Actions: | Query
Type: | String
Default: | Relevance
Example: | `Sort=Date`
See Also: |

© 2016 Hewlett Packard Enterprise Development LP | Send documentation feedback to HPE Close We welcome your comments! To open the configured email client on this computer, open an email window. Otherwise, copy the information below to a web mail client, and send this email to AutonomyTPFeedback@hpe.com. Product: Topic Title: Help Topic: Feedback:

_HP_HTML5_bannerTitle.htm