Search detailed applicants

[StaelTchinda]

Description

The main goal of this task is to search for detailed applicant profiles based on specific criteria. These criteria include:

• searched job title
• location ****
• min avg job position years
• min work experience years
• max sabbatical time years
• job titles ****
• job descriptions (****)
• education keyword
• skills ****
• languages ****

To achieve this, we need to understand their structure and build an endpoint.

Resources

I recommend using the tinydb library to read and search for information. You can refer to the official documentation.

Tasks

The tasks include:

• [x] Create a class ExtendedDetailedSearchParameters: This class will describe the attributes obtained from the search criteria and should be located at src/applicants/schemas/extended/request. The attributes will include all the criteria mentioned in the description.
• [x] Create a function build_detailed_search_query: This function will take as parameter the search criteria of type ExtendedDetailedSearchParameters and generate a query that will be used by the tinydb database DetailedApplicantsDb. The function should be located at src/applicants/service/extended/query.
• [x] Create an endpoint /applicants/search/Details: This endpoint in the router will take as parameters the search criteria, get the detailed profiles that match the criteria, save them in the tinydb local database, and return them.

[JRoss5]

@StaelTchinda Should the max_sabbatical_time_years check only the career path (i.e. Werdegang) or also consider the time between Ausbildungen?

[StaelTchinda]

@StaelTchinda Should the max_sabbatical_time_years check only the career path (i.e. Werdegang) or also consider the time between Ausbildungen?

@JRoss5 the career path is enough. Especially since the people we are targeting have more than 20 years experience. What happened in their school years is not anymore that decisive.

[JRoss5]

@StaelTchinda I've pushed a first version to a new branch search-detailed-applicants now. I had 2 questions for the implementation: by skills do we mean Kenntnisse or Softskills? I've set it to search through both for now. Also, what fields do we want to search for education_keyword? Right now I've set it to search a rather broad range of fields to be able to catch as many use cases as possible.

[StaelTchinda]

@JRoss5 By skills, we originally meant Kenntnisse, but you can keep both for the moment. It's fine.

For education_keyword, it is also fine like that for the moment. We can update later depending on how we use it.

I also created and reviewed a pull request. Please consider the comments I've made and let me know when you integrated them.