# Diagnostics and Querying Basics


There are two sections of the Diagnostics URL, the actual diagnostics page itself and the ability to use this URL to query and request the data you have inserted into the dataset. In order to access the diagnostics page, simply use the URL by itself with no URL parameters.

# What is This Page?

The page can be used to view your configurations set up in your Indexes and Navigations configs and will show what the output of a search result request and what your generated iNav will look like, it can also be used to quickly view your base iNav and search results for all your items, as well as a count of how many items are in your dataset as well.

For more information about the Diagnostics page, see Diagnostics

# Querying Your Data

After setting up your configuration and inputting some data you will now be able to query and request that data. Data can be viewed using URL parameters given after the diagnostics URL, this getting started guide will cover the most basic q= query.

# q= Query

A q= query is used in order to query the data with certain filters active. As this is a type of query and not a request, it must be combined with another request type in order to actually return any results, for more info on the other request types, see Usage. The easiest way to quickly return data is to combine the query with an empty search result request sr. The format would look like this

URL/v4/search?sr&q=

The /v4/search at the beginning is required for searching for data and the URL is the diagnostics URL mentioned above. The sr section refers to the blank search result request and will ensure that your query will provide results that you can view in JSON format.

A q= query can be seen as a kind of filter for your results, simply providing your URL with the sr keyword will produce every item you have inserted into your dataset, however, combining it with a q= query will allow it to refine your search and provide more precise results.

For Example: sr&q=Genre.Fantasy.

In this example, all items that have Fantasy listed in the Genre aspect will be returned. The section after the q= refers to a query string that is used to gather your data, it must be followed by a . at the end of the string in order to gather any data.

Another more complicated example: sr&q=(Or.Genre.Fantasy._.Genre.Horror.)

This example is using one of the many keywords used to multi-select items and have different filters combining together, there are four types of these, Not, And, Or, and C. In the example above Or is used in order to provide results that contain the Genre Fantasy and Horror. These can be viewed as combinational logic and work in a similar way with an exception being, C, which is used to query items that must contain attributes from the parent and child aspect e.g. C.Genre.Fantasy._.Series.LOTR.

To query the range you set up earlier, the q= query must be set up a little differently

For Example: sr&q=Price.range(min..max).

This is how you query a range item with a minimum and maximum. The name of your range comes first, followed by .range( then your min and max values separated by ...

For more information on the usage of 1search queries and requests, see 1search Usage