Lead management is one of our use cases for Jobtech data. To ensure we can use the Jobtech data for this end, we have these questions about data freshness.
a. How often is the data refreshed?
b. What is the lag of a job posting being included in the datafeed?
c. At what frequency are new job postings published / made available?
Jobstream includes all current job ads from Swedish Public Employment Service, updates every three minutes or so. This API is the preferred way to use if someone needs a full updated copy of all job ads from the Platsbanken (Job board from the Swedish Public Employment Service).
In addition to occupations, we use skills in various use cases. From our understanding Jobtech uses ESCO for skills and occupations.
We find that Jobtech includes 5950 skills. According to your schema these skills are based on ESCO, which includes 13890 skills. There seems to be some loss of granularity. We wonder if you have the mapping from ESCO skills to Jobtech skills.
The skills are not based on ESCO, only mapped to them. And you are right in that the ESCO-skills in general are more detailed than ours. I have included a query here through which you can get the mappings: Taxonomy version 19 - Please note though that some skills are unmapped (in which case we have not been able to find a proper mapping). Also if you want to see the mappings from the point of the taxonomy skills, just switch (“esco-skill” with “skill”, and vice versa) the type parameters in the query. You can input the query in our graphiql-gui: https://taxonomy.api.jobtechdev.se/v1/taxonomy/graphiql
Similarly, would it be possible to get access to the occupations mapping?
You can get the occupation mappings through the query found here: Taxonomy version 11 publicerad You can input the query in our graphiql-gui: https://taxonomy.api.jobtechdev.se/v1/taxonomy/graphiql
From the section of the flowchart of the Jobtech skill classification included on the next page we see that you are mainly using matching methods. We wonder if you are doing anything to account for semantics and syntax.
We have tried to use the SKOS relations as much as possible. When relating from our classification to ESCO we have used the mapping relations (ending with “match”). Looking at the chart it actually seems we have defined some relations between the two concept types with the wrong relation-type – we will have to look into that.
We use salary data for various use cases. Are thera any open data?
Try to use open data from SCB (Statistics Sweden, Central Bureau of Statistics). A service listing wage per occupation. SCB - Search on wages
This e-service (as an example) combines information about wages, occupation and forecats from those sources (taxonomy, SCB and forecasts): Hitta yrke
Modeling scarcity is one of our use cases. For this we are looking for data on labour force supply, specifically about job seekers.
a. what data do you have available on jobseekers?
b. If you have data, at what level of granularity in terms of location and occupation?
Personal data is by default not open data. There are some general statistics about the labour market and job seekers here: Statistik - Arbetsförmedlingen (but not per occupation). The Public Employment service forecasts (per occupation) is open data: Yrkesprognoser