Libraries tagged by which
laurentmuller/fpdf2
2674 Downloads
FPDF 2 is a PHP class which allows to generate PDF files with pure PHP. F from FPDF stands for Free: you may use it for any kind of usage and modify it to suit your needs.
languagewire/html-dumper
4167 Downloads
A library which downloads pages as static HTML files and assets and dumps them on disk
lakedrops/docker-traefik
30254 Downloads
Library to prepare local Traefik Docker container which is used by e.g. Docker4Drupal.
kunjara/swetest
1526 Downloads
Command line program which computes planetary positions
justinbusschau/php-govtalk
13669 Downloads
A library for applications which interface with the UK Government Gateway
jpmschuler/powermail-limits
4900 Downloads
TYPO3 EXT:powermail_limits - Addition to EXT:powermail which allows limits for form submissions
joschi127/doctrine-entity-override-bundle
119564 Downloads
Symfony bundle which allows to override entities by using inheritance
jonsutherland/laravel-sns-sqs-sub-pub
6817 Downloads
A simple Laravel service provider which adds a new queue connector to handle SNS subscription queues.
jobinja/laravel-djangoable-auth
3199 Downloads
An authentication driver for Laravel5 which allows to authenticate users using their legacy Django PBKDF2
jobinja/blade-macro
4800 Downloads
Reusable scope-protected blade blocks, with empty I/O on runtime (replacement for @include which uses native I/O based PHP includes).
jcchavezs/cmb2-conditionals
6739 Downloads
CMB2 Conditionals is a plugin for CMB2 which allows developers to relate fields so one of them could only appear when one other have an specific value or when is not empty.
jandc/css-from-html-extractor
23777 Downloads
Php library which determines which css is used from html snippets.
jakewhiteley/hodl
4930 Downloads
A lightweight PSR-11 dependency injection container for PHP, which sites in between Pimple and the Laravel Container
intersvyaz/yii-tags-dependency
56452 Downloads
Verification of the cache relevance based on Dependency mechanism of Yii framework and tags, which are also stored in cache
inda-hr/php_sdk
500 Downloads
# Introduction **INDA (INtelligent Data Analysis)** is an [Intervieweb](https://www.intervieweb.it/hrm/) AI solution provided as a RESTful API. The INDA pricing model is *credits-based*, which means that a certain number of credits is associated to each API request. Hence, users have to purchase a certain amount of credits (established according to their needs) which will be reduced at each API call. INDA accepts and processes a user's request only if their credits quota is grater than - or, at least, equal to - the number of credits required by that request. To obtain further details on the pricing, please visit our [site](https://inda.ai) or contact us. INDA HR embraces a wide range of functionalities to manage the main elements of a recruitment process: + [**candidate**](https://api.inda.ai/hr/docs/v2/#tag/Resume-Management) (hereafter also referred to as **resume** or **applicant**), or rather a person looking for a job; + [**job advertisement**](https://api.inda.ai/hr/docs/v2/#tag/JobAd-Management) (hereafter also referred to as **job ad**), which is a document that collects all the main information and details about a job vacancy; + [**application**](https://api.inda.ai/hr/docs/v2/#tag/Application-Management), that binds candidates to job ads; it is generated whenever a candidate applies for a job. Each of them has a specific set of methods that grants users the ability to create, read, update and delete the relative documents, plus some special features based on AI approaches (such as *document parsing* or *semantic search*). They can be explored in their respective sections. Data about the listed document types can be enriched by connecting them to other INDA supported entities, such as [**companies**](https://api.inda.ai/hr/docs/v2/#tag/Company-Management) and [**universities**](https://api.inda.ai/hr/docs/v2/#tag/Universities), so that recruiters may get a better and more detailed idea on the candidates' experiences and acquired skills. All the functionalities mentioned above are meant to help recruiters during the talent acquisition process, by exploiting the power of AI systems. Among the advantages a recruiter has by using this kind of systems, tackling the bias problem is surely one of the most relevant. Bias in recruitment is a serious issue that affect both recruiters and candidates, since it may cause wrong hiring decisions. As we care a lot about this problem, we are constantly working on reduce the bias in original data so that INDA results may be as fair as possible. As of now, in order to tackle the bias issue, INDA automatically ignores specific fields (such as name, gender, age and nationality) during the initial processing of each candidate data. Furthermore, we decided to let users collect data of various types, including personal or sensitive details, but we do not allow their usage if it is different from statistical purposes; our aim is to discourage recruiters from focusing on candidates' personal information, and to put their attention on the candidate's skills and abilities. We want to help recruiters to prevent any kind of bias while searching for the most valuable candidates they really need. The following documentation is addressed both to developers, in order to provide all technical details for INDA integration, and to managers, to guide them in the exploration of the implementation possibilities. The host of the API is [https://api.inda.ai/hr/v2/](https://api.inda.ai/hr/v2/). We recommend to check the API version and build (displayed near the documentation title). You can contact us at [email protected] in case of problems, suggestions, or particular needs. The search panel on the left can be used to navigate through the documentation and provides an overview of the API structure. On the right, you can find (*i*) the url of the method, (*ii*) an example of request body (if present), and (*iii*) an example of response for each response code. Finally, in the central section of each API method, you can find (*i*) a general description of the purpose of the method, (*ii*) details on parameters and request body schema (if present), and (*iii*) details on response schema, error models, and error codes.