What is the difference between the algorithm value "ignore" and the option "nullMatch" set to false?
Using the algorithm value ignore
The search algorithms can be controlled by setting the type field to a specific value. If the type field is set to ignore, the algorithm will be configured to ignore the attribute in the search, and any matches will be returned regardless of the value of the attribute. If the type field is set to any other value, the algorithm will be configured to consider the attribute in the search and only return matches with the specified attribute value.
This applies to any attribute that can be used in a search query, such as dates of birth, nationalities, or addresses.
For example, setting the type field to same_year for the datesOfBirth attribute will only return matches with the same year of birth as the search query, while setting the type field to ignore for the datesOfBirth attribute will return matches regardless of their date of birth.
The following examples demonstrate how the type field of the dateOfBirthAlgo algorithm can be used to control the behavior of the search.
Example with a specified algorithm value
In the first example, the dateOfBirthAlgo is set to same_year. In this case, no match is found when searching for the individual named 'Abu Husayn' on the USA list because the API only considers matches where the year of birth is the same.
In the second example, the dateOfBirthAlgo is set to ignore, which means that the API will not use the date of birth as a criterion for searching the individual on the USA list. Instead, the API will only consider matches based on the full name.
When analyzing the results, we can notice that the first match comes with a date of birth equal to 1977 while the second one has a date of birth equal to 1974-03-25. Both years of birth are different from that of the individual sent in the search request. This explains why no match was returned in the first example.
Using the algorithm option nullMatch
The nullMatch option is used to specify how search algorithms should handle empty or missing attributes in the watchlists. This option allows the search to be more flexible and consider matches even if some attributes are not provided or are empty. This can be useful in situations where the information in the watchlists is incomplete or not fully known, and the search needs to be able to handle these cases.
When nullMatch is either not provided or set to true in a query, the search will consider attributes that are missing or empty as a match, whereas when it is set to false, these attributes will not be considered a match.
Example with the algorithm option nullMatch set to false
For example, if a search query is looking for an Iraqi (IQ) national named 'Abu Husayn' on the USA list and the nullMatch option associated with the nationalityAlgo is set to false, the search will only return a match if the individual's nationality is explicitly listed as IQ.
Example with the algorithm option nullMatch set to true
Now if nullMatch is set to true or not provided, the same search will also return a match if the individual's nationality is not specified in the list of attributes.
The first match is the same match which is found whennullMatch is set to false, where the individual's nationality is explicitly listed as IQ.
The second match is a new one with no specified nationality.
By default, the API performs searches with the nullMatch option set to true, which means that it will return matches where the attribute associated with a search algorithm is not specified in the watchlists. This is the default behavior of the search API in the absence of the nullMatch option. To change this behavior, specify the value false for the nullMatch option when making a search query.
