Purpose
Axis is integrated with OneID OneSearch for searching OneID accounts. This document will outline the OneSearch functionality, and any differences that exist between our previous OneID search implementation with iQuery.
OneSearch Documenation
OneSearch Differences To iQuery
Strict Matching
From a "results returned" perspective, the biggest change that will be seen with OneSearch vs iQuery is in how values are searched. In iQuery, results are returned based on lucene searching, which returns results based on relevancy. This can end up returning "similiar" results, that are either visually or close matching to the value searched. Meanwhile, OneSearch results are returned based on SQL search matching, which follows exact pattern matching, with the addition of right side wildcards. Here's an example of username searching
| Platform | Searched Type | Search Value | Results Returned | Examples | Comments |
|---|---|---|---|---|---|
| iQuery | username | abcdefg | 88 | abcdefg150605, a5abcdefg01, abcdefg1108@disney.com | Matches can be found with additional chars at both the beginning and end |
| OneSearch | username | abcdefg | 1 | abcdefg | Only exact match found |
| OneSearch | username | abcdefg* | 100 | abcdefg, abcdefg-hey, abcdefghiga1979 | Returns any results that start out with abcdefg. Capped at 100 max results. |
Age Band
OneSearch does not contain the same value that we currently use for Age Band in the search results. OneSearch has a value called Assumed_Age_Band. This value is only filled for certain products, as it's optional unless configured by a product. OneID estimates that only 8% of production accounts have this value. With OneSearch, reps will probably need to rely more on birthdate for the use they are currently using Age Band
OneSearch Fields
Here are all of the fields that are currently supported by OneSearch. These fields can be used in any combination of 1) return value, 2) search constraint, 3) order by.
| Field Name | Currently Searchable | Displayed In Search Results | Comments |
|---|---|---|---|
| swid | Yes | Yes | |
| first_name | Yes | Yes | |
| last_name | Yes | Yes | |
| email_address | Yes | Yes | |
| parent_email_address | Yes | Yes | |
| birthdate | No | Yes | Not all accounts contains birthdate |
| assumed_age_band | No | Yes | Only filled in a small percentage of production accounts |
| pronunciation_name | No | No | |
| client_code | No | No | |
| status | No | Yes | OneSearch does not contain results for ANONYMIZED, DELETED, PURGED_PII statuses. Rare/strange statuses may cause errors when searching |
| is_primary | No | Yes | |
| phone_number | Yes | No | Including phone number search causes "duplicate" records to be returned, due to the one→many structure of the account/phone number relationship. We are not including this value in the results until a better solution to the duplicate records are determined |
Searches Currently Supported In Axis
| Search Type | OneSearch Values Searched | Results Ordered By | Comments |
|---|---|---|---|
| Smart Search | username OR swid OR email_address OR parent_email_address | username | |
| Account ID | swid | swid | |
| First Name | first_name | first_name, last_name | |
| Last Name | last_name | last_name, first_name | |
| Phone Number | phone_number | phone_number, email_address | |
| Last Name, First Name | last_name AND first_name | Last_name, first_name | |
| Display Name | displayname AND namespace | swid | |
| email_address OR parent_email_address | email_address, parent_email_address | ||
| Username | username | username | |
| Status | - | - | Removed, supported in iQuery, but only partially in OneSearch. As we have an alternate way to determine the anonymized rejected users this search is no longer needed or useful |
| Postal Code | - | - | Removed. Supported in iQuery, but not OneSearch as this was ultimately not a useful field to sort by |