Releases: Riminder/python-hrflow-api
v4.2.0
v3.3.0
Remove dependency on python-magic
Remove dependency on python-magic which requires having libmagic1
system dependency installed via sudo apt-get install libmagic1
or similar. The library is not used as of the v3 release serie.
v4.1.0
- Add interest and language fields to experience and education schemas
- Add a function to utils that checks profile eligibility for searching or scoring
from hrflow.utils.searching import is_valid_for_searching
from hrflow.utils.scoring import is_valid_for_scoring
generate_parsing_evaluation_report
- Handle the evaluation of indexed jobs in a board
- Update profile parsing evaluation by changing
person
(=first_name
&last_name
) score tofull_name
score (fillingfull_name
field in parsing) - Fix the way the
location
fill rate is calculated at the root of the profile, which used to result in a constant score of 1. Now it looks at the filling of the location text field for the profile. The location score for experiences & educations was not affected by this bug.
v4.0.1
- In file parsing :
- Use File object instead of bytes (replace file.read() by file)
- Handle BytesIO objet with no file name
- Infer filename base on File object
- Add some tests (multi format resumes)
- Improve docs
- Fix bug that hard code the person score in parsing evaluation
v4.0.0
- Add parsing evaluation & Function to generate the Excel report in
hrflow.utils
- Add limit rate for each endpoint
- Add Job/Profile schemas
v3.2.1
- Add backwards compatibility with the
text
parameter in Text Parsing.
v3.2.0
- Migrate on Poetry
- Add Ask endpoint
- Add Auth endpoint
- Add Unfold endpoint
- Handle batch in tagging
- Fix typo in README.md
- Create a testsuite
v3.1.1
- Added detailed Profile and Objects fields description in storing endpoints
- To be able to seamlessly index Profiles & Jobs from structured sources in HrFlow.ai
v3.1.0
HRFlow API Version 3.1.0 Release Notes
Minor Version Update - Improved Profile and Job Updates
In the 3.1.0 version of the HRFlow API, we have made a minor enhancement to the update process for both Profiles and Jobs. Now, when updating a Profile or a Job, it is no longer mandatory to provide the key as a keyword argument. This change offers more flexibility and ease of use when updating objects.
Key Features and Changes:
- Profiles and Jobs can now be updated using either the key or reference as a keyword argument.
- The update process is now more flexible and allows for simpler object updates.
- This version is backward compatible, and the key is still accepted as a keyword argument.
For detailed information on how to use the updated update functionality, please refer to the latest version of the API documentation and examples.
We recommend all users to update to this latest version to take advantage of the improved object update process. Thank you for your continued support and feedback.
For more information, detailed API documentation, and examples, please visit our GitHub repository.
If you have any questions or need assistance, please reach out to us at [email protected].
v3.0.0
🎉 New Features:
- Introduced new API Tracking: Allows you to track a Profile (or a Job) for Job (or a Profile) as a recruiter (or a candidate) with a specific action. For more details, refer to the Tracking API Documentation.
- Introduced new API Rating: Enables you to rate a Profile (or a Job) for Job (or a Profile) as a recruiter (or a candidate) with a score between 0 and 1. For more information, visit the Rating API Documentation.
⚠️ Breaking Changes:
- The resource indexing in both profile and job has been renamed to storing. It still offers the same functionality (with the same methods) and has introduced a new list method. This method allows you to apply additional filters when querying objects in the HrFlow.ai data warehouses (Sources and Boards).
🤝 Getting Started Notebooks:
- Added notebooks with examples to provide hands-on usage of the SDK and demonstrate how to use each module of our suite for both profiles and jobs. You can find the notebooks in the
examples
folder at the root of the project.
We encourage all users to upgrade to this latest version to take advantage of the new features and improvements. For more information, please refer to the updated documentation and examples.
Thank you for your continued support and feedback.
For more information and detailed API documentation, visit our GitHub repository.
If you have any questions or need assistance, please reach out to us at [email protected].