Analysis of relations between students and sectors of activity
Description
MyFuture has been helping young people to orient themselves since 2015 and has allowed thousands of college students/lyceans/students to carry out internships throughout France.
The following anonymous data sets help to understand the interest of young people in different sectors of activity.
# # general principle of the platform
The general principle of the platform [stagedecouverte.fr](https://www.stagedecouverte.fr/) proposed by Myfuture is to create links between:
— companies, on the one hand,
— people (mainly college students/lyceans/students) wishing to discover the professional world or a sector of activity, on the other hand
This connection shall be carried out as follows:
— an offer is published by a professional. An offer is located at a given address and has one or more related subdomains. The professional can indicate which public he is looking for, what his availability is (...)
— a student registers and indicates that he/she is looking for offers at a given address and is interested in specific sectors of activity
— the student will see the offer appear and may indicate his interest (statut liked) or not (statut disliked)
— the student, if he wishes, can also apply for the offer
— the professional will receive the application, will be able to exchange with the student to understand his project and his motivations, and can confirm the application if he wishes
## Presentation of the file “aggregationdepartementdomain.csv”
=> presentation of columns
— the columns **subarea** and **area** correspond to the nomenclature “IDEO-NOMENCLATURE ONISEP DOMAINES AND SOUS DOMAINES” available here [http://opendata.onisep.fr/data/5fa58d750a60c/2-ideo-nomenclature-onisep-domaines-et-sous-domaines.htm](http://opendata.onisep.fr/data/5fa58d750a60c/2-ideo-nomenclature-onisep-domaines-et-sous-domaines.htm). They are simply “slugified” to make them more robust “keys”
— column **departement** corresponds to the department where the traineeship offer is located
— column **nbOffers** corresponds to the number of tenders on the department and corresponding to the sub-area in question. Attention, it is not possible on this file to sum the column nbOffers to arrive at the total number of offers on the platform (more than 15,000). Indeed, as some offers have several subdomains, they appear in several “lines” and are therefore counted several times if one sums the column nbOffers
— column **nbElevesAyantInteragi** corresponds to the number of pupils who have had an interest in the offers in question (those of nbOffers) (by “liking” or “disliking”)
— column **nbElevesInteresses** corresponds to the number of pupils having “liked”
— column **nbApplications** corresponds to the number of applications
— column **nbConfirmes** corresponds to the number of applications validated by the corresponding professional
## Presentation of the file “rawexportuser domainstatut.csv”
This is a raw file of all the interactions that took place on the platform. This file can be used to analyse user behaviours (obviously preserving their anonymity).
It does not contain the dates of interaction, its focus is really on what students have interacted with, in a given department.
Note that some students may have interacted with other offers, in other sectors of activity, if they had been available in their region.
=> presentation of columns
— column **IDuser** corresponds to the id of a given student
— column **departement** corresponds to the student’s department
— column **genre** corresponds to the type indicated (this column may sometimes be empty or “unknown” depending on what the user wanted to inform (at his discretion)
— column **idOffer** corresponds to the id of an offer on the platform
— column **domains** corresponds to domains (separated by commas and slugified as indicated above for the domain aggregation file.csv)
— column **statut** corresponds to the status of interaction (the main statutes correspond to the scenario mentioned above: liked, disliked, feels, confirmed)
Resources
| Name |
Format |
Description |
Link |
|
8 |
|
https://www.data.gouv.fr/api/1/datasets/r/e043e0fb-5181-417e-b399-12be2524e403 |
|
8 |
|
https://www.data.gouv.fr/api/1/datasets/r/177faef9-ae19-4966-8cd6-fd1c0baedf6a |