GrantNav Search Bar¶
GrantNav‘s search bar is a powerful and flexible tool that forms the starting point for almost every exploration of grants data with GrantNav
When you enter a term into the search bar and click ‘Search‘, GrantNav searches through all the grants in the database, and presents results in order of relevance - with the results that match the most words, most often, at the top.
By default, GrantNav searches all of the fields in the grant record - this includes the title and description, the names of places and geocodes, the names of funder and recipient, and any other information that the publisher of the data has provided.
To search for a particular phrase, put it in quotes in the search bar. Quotes can also help avoid unexpected results if your search term contains special characters such as dashes or brackets.
Text search isn‘t case-sensitive, so capital and lower-case letters will match each other; “GiRlS“ matches “girls“. Diacritics are ignored, so “Esmee“ matches “Esmée“.
GrantNav carries out stemming, so will return results for different forms of the same word; “disability“ matches “disability“, “disabled“, etc.
On the results page, you can refine your results to narrow down your search.
Try these examples
A single word: e.g.
Multiple words: e.g.
young people gardens . GrantNav will first show results that contain all the words, then those which contain two of the words, and then those which contain only one.
A phrase: e.g.
“frames and stonework“
A specific grant: e.g.
Grants that are by, or that mention, a particular organisation: e.g.
“The Dulverton Trust“
AND, OR and NOT operators¶
The search bar allows you to specify a more constrained search by specifying combinations of words which must or must not appear.
Searching Specific Fields¶
The search bar allows you to search within specific fields within the data, including all of the fields from the 360Giving Data Standard and fields provided by specific publishers. To see which fields each publisher provides, look at a sample of the grants that they‘ve published.
GrantNav uses the JSON field names rather than the “human-friendly“ form that you‘ll normally see used. The conversion uses the following rules:
- Fields with a single-word name are lower case - e.g. “Title“ becomes
- Fields with a multi-word name are camelCase - e.g. “Award Date“ becomes
- Colons become dots - e.g. “Beneficiary Location: Name“ becomes
- “Org“ becomes
Organization- e.g. “Funding Org: Name“ becomes
- “Geographic“ becomes
geo- e.g. “Beneficiary Location:0:Geographic Code“ becomes
Try these examples
title field for the word ‘gardens‘:
recipientOrganization.postalCode field for ‘NW1‘ (where the publisher has provided this field): e.g.
Funding Organisation:Name field for “London Councils“ (where the publisher has provided this field):
fundingOrganization.name:“London Councils“. Note that the quotes operate the same way as above - so the name has to match the phrase in order to be returned in these results.
The search bar allows you to search for a range of dates or values. Commonly, this is used to search by financial year rather than calendar year, or to look for specific ranges of funding values.
There are two ways of searching for a range - use whichever is easiest for you at the time!
The TO operator¶
This takes the form
fieldName:[value1 TO value2].
Either of the values can be a wildcard
*, which leaves that side of the range unbounded.
This uses the
< <= > >= operators to describe a range - e.g.
amountAwarded:>1000 . To describe a bounded range using the comparison operators, use the AND keyword.
As ever, searching for a field that‘s optional in the standard will exclude all grants that don‘t have that field provided.
Try these examples
Award date in FY17/18:
awardDate:[2017-04-01 TO 2018-03-31]
Planned start date in 2016:
plannedDates.startDate:>2016-01-01 AND plannedDates.startDate:<2016-12-31
Planned start date in 2015 and planned end date in 2017:
plannedDates.startDate:[2015-01-01 TO 2015-12-31] AND plannedDates.endDate:[2017-01-01 TO 2017-12-31]. Note that the quotes operate the same way as above - so the name has to match the phrase in order to be returned in these results.
Amount Awarded between £0 and £150:
amountAwarded:[0 TO 150]
Amount Applied for £1000 or more:
? wildcard can be used in place of an one character in text, and the
* wildcard can be in place of any number of characters.
* wildcard can also be used in place of any date or numerical value in a range, as above.
You can search for terms that are similar to, but not exactly like your search terms, using the “fuzzy” operator:
~ . To use it, put the
~ operator at the end of the term you’re looking for.
The fuzzy operator will take account of letter transposition (e.g. “youht“), letter replacement (e.g. “touth“), letters missing (e.g. “yoth“) and letters added (e.g. “yoouth“), in any combination. This can be useful for taking account of mis-spellings.
Note that GrantNav already carries out stemming (ie, searching for different forms of the same word), so fuzzy matching shouldn‘t be used for this as the stemming is far more accurate.
Results returned from a fuzzy match should be scrutinised closely, as it can very easily include irrelevant results - for example “boys~“ matches “boss“.
Try this example
Grants containing words that are similar to youth~“:
Combining search operators¶
All of the search operations described here can be combined to query for a very specific set of results.
All of the search operations also are compatible with the filters on the left-hand side, so you can search, and then refine.
However, be aware that the more specific the search, the more data is excluded due to data not being provided and data quality issues (such as typos or errors in the data). To learn more about this, see Understanding Results.
Try this example
Grants under £500 given in 2019 by funders whose name contains “Community Foundation“ and whose description relates to disability:
awardDate:[2019-01-01 TO 2019-12-31] AND amountAwarded:<500 AND fundingOrganization.name:“Community Foundation“ AND description:disability