No, it is not possible to search resumes without indexing first when using RChilli’s Search & Match APIs.
Here’s a detailed explanation:
Parsing vs. Indexing – Key Difference
-
Parsing: This step extracts structured data (like name, skills, education, etc.) from a resume using the Resume Parser API.
-
Indexing: This step stores the structured data into a searchable database, making it usable for search and match operations.
So, parsing prepares the data, but indexing makes it searchable.
- If you only parse a resume, it is not stored in RChilli’s system and therefore cannot be searched later.
- To make a resume searchable, it must be indexed using RChilli’s indexing functionality.
Combined Option: Parse and Index API
To streamline the process, RChilli offers a ParseAndIndex API that performs both operations in one call:
-
It parses the resume.
-
Immediately indexes the parsed data into the Search & Match database.
Reference: Parse and Index API documentation.
Data Storage Consideration
Although RChilli does not permanently store data from the Resume Parser API, the Search and Match module temporarily stores indexed data in a secure environment to facilitate fast and efficient search operations.
If needed, all indexed data can be removed using the DeleteAllDocuments API for a fresh start.
Conclusion
To summarize:
| Action | Resume Available for Search? |
|---|---|
| Parsed only | No |
| Parsed and Indexed | Yes |
If your goal is to use RChilli’s powerful search features, indexing is a required step.
For tailored setup or integration assistance, contact support@rchilli.com.
Comments
0 comments
Please sign in to leave a comment.