Index grids, step-up grids, and reclassification grids for certified teachers of national education

Open data API in a single place

Provided by etalab

Get early access to Index grids, step-up grids, and reclassification grids for certified teachers of national education API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2022.08.08 23:47
Created
2022.07.02
Available languages
French
Keywords
professeurs, indiciaire, grille, points-dindice-bruts, indiciaires, indice, points-dindice, certifie, carriere, indices, progression, grilles, professeur, avancement, education-nationale, certifies
Quality scoring
235

Dataset description

Index grids give the number of gross index points for each step based on time and are named as **certifies_[grade]_indexes.csv**, where **[grade]** is equal to **cn** (normal class), **hc** (outclass) or **ce** (exceptional class). Columns of index grids: — effective date: date (format YYYY-MM-DD) of entry into force of the gross index value indicated; — date_text: date (format YYYY-MM-DD) of the signature of the Order or Order; — date_appearance_jo: date (format YYYY-MM-DD) of publication in the Official Journal; — echelon_n (with n a positive integer): step number in grade; — link_legifrance: link to the decree or decree. Step advancement grids give the durations of each step and the conditions for moving to the next grade. They are named as **certifies_[grade]_durees_[YYYY-MM-DD].csv**, where **[YYYY-MM-DD]** is the effective date of the new grid. Columns of step progress grids: — Echelon: step number in grade; — hard_old: duration of the step with advancement to seniority; — hard_choice: duration of the step with advancement at your choice (or career acceleration from 1 September 2017); — hard_grand_choice: duration of the step with advancement at large choice; — echelon_promo_[grade]: step number at the time of promotion to the higher grade (“ind” if ranking in step with an index equal to or immediately higher); —anciente_echelon_promo_[grade]: seniority to be achieved in the step before promotion to the higher grade; —anciente_promo_[grade]: become seniority in step after promotion in the higher grade (“acq” if acquired seniority is retained, without otherwise); — old limit_promo_[grade]: limit on seniority retained after promotion in the higher grade or “processing”: seniority lost if the salary increase following promotion is higher than that which would have been achieved by a step advancement in the former grade, “promo”: limitation of the time required to promote a step in the higher grade; — mark-up_anciente_promo_[grade]: number of years added to seniority in the step at the time of promotion (this number may be negative); The reclassification grids, giving the reclassification rules corresponding to the entry into force of a new advancement grid, are named as **certifies_[grade]_reclassification_[YYYY-MM-DD].csv**. Columns of the reclassification grids: — echelon_depart: step before reclassification; — old_departure: number of years of seniority to be held in the step before reclassification; — class_arrival: present only if the grade is different after reclassification (‘cn’, ‘hc’ or ‘ce’); — echelon_arrival: step after reclassification (step number or “anc_corps” if the step is calculated according to seniority in the body); — old_arrival: become seniority after reclassification (“acq” if acquired seniority is retained, “without” otherwise); — mark-up_old_arrival: number of years added to seniority in the step after reclassification (this number may be negative); — remuneration_securisee: is “yes” if the old treatment is maintained in the case of lower treatment after reclassification; — limit_old_arrival: maximum value of seniority after reclassification.
Build on reliable and scalable technology
Revolgy LogoAmazon Web Services LogoGoogle Cloud Logo
FAQ

Frequently Asked Questions

Some basic informations about API Store ®.

Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.

Didn't find the API you need?

Let us know and we will figure it out for you.

API Store provides access to European Open Data via scalable and reliable REST API interface.
Copyright © 2024. Made with ♥ by Apitalks