Using the Affinda Search UI
Affinda has developed a user interface for the Search & Match product that can be embedded within a customer’s platform. The interface is an easy-to-use tool that provides transparency to users on the reasons that candidates or jobs scored highly for the given search criteria. The interface is available for testing within the Affinda web app and can be embedded easily once a customer has moved to a paid plan. The embedded interface can be customised according to customer requirements, including changes to styling and functional elements.Uploading a document to Search & Match
Searches within the interface can be created in two ways:- Custom search criteria
- Uploading a document for matching
Adjusting a search
A custom search criteria, either from a blank start or using the outputs from an uploaded document, can be created by adjusting the fields and weightings within the Search Interface. Within the Search Interface, users can easily adjust the following elements to give the best results:- Search fields & criteria
- Search types (e.g. current job titles only)
- Category weights
Viewing results
Our results panel quickly ranks and summarises candidates in an easy-to-digest format. If users want to see additional detail about the candidate and where they performed well or poorly against the search criteria and a brief summary of the data held within their profile, expanding the candidate profile will unearth a range of additional detail. Users can also download the resume directly from the Search Interface if enabled, as well as other actions which can be customised within the users’ platform.Boolean Searches
To give users full flexibility, our Candidate and Job Match products allow users to specify Boolean searches. Our product uses ElasticSearch simple query string syntax to give you the power to make complex custom searches that fit your need. While this type of search is most typically used for the ‘Keyword’ category by users, the same syntax can be applied across all of our other search categories. Search syntax+
signifies AND operation|
signifies OR operation-
negates a single token"
wraps a number of tokens to signify a phrase for searching*
at the end of a term signifies a prefix query(
and)
signify precedence~N
after a word signifies edit distance (fuzziness)~N
after a phrase signifies slop amount