Occupation-name concepts

Definition

A definition is needed here.

Description

An occupation name concept is a detailed occupational designation, tied to groups on the fourth level of both the SSYK and the ISCO structures. The ISCO connection is primarily maintained in order to ensure interoperability with the Eures portal, while the SSYK connection is used more frequently in many implementations on the labour market.

The occupation name concepts aim at representing a language used and recognized by the industries and its employers on the labour market. In order to ensure this, the team that manages them attempts to collect as much information as possible from external sources, such as industry experts, , when curating the concepts,

On alternative labels, job titles and keywords

Occupational titles can have the attribute alternative-labels. They can also have connections to other types of concepts, such as job-title and keyword.

The attribute alternative-labels is only used in cases where an obvious synonym or abbreviation for the concept exists. For example, the occupation-name concept Museichef/Museidirektör. In many cases these concepts have the different terms connected to the alternative-labels attribute separated with a "/" in their preferred-label, but not always.

Unlike alternative-labels, a job-title is an own, separate, concept that has a different scope than a occupation-name concept. A job title that is linked to a occupation-name concept should therefore not be seen as a synonym. For example, consider the term Länsmuseichef, which is connected to Museichef/Museidirektör, but due to its narrower scope is represented as a job-title instead of an alternative-label.

Concepts classified as keyword often constitute a broad concept, or domain, that a multitude of occpupation-name concepts can be linked to. For instance, see Law.

Managed by

Team Redaktionen at Jobtech, Arbetsförmedlingen.

Purpose

The occupation-name concepts at Arbetsförmedlingen have a long history. As long as some form of digital matching has been conducted, occupation-name concepts, or their previous equivalents, have been necessary. They provide a terminology that aims to reflect the language of the labour market, with more frequent update intervals than the SSYK structure. The classification can be used for job matching, creating resumes, categorizing job ads, career guidance, etc.

Concepts that are deemed outdated are given the deprecated attribute to indicate that they should no longer be used. Concepts are however never removed from the database and can always be queried through the Taxonomy API, despite of deprecation.

Governance

Updates of the occupation-name concepts are performed continuously, and may occur in each new version of the Taxonomy. Generally the updates are performed as the need arises, and may be initiated in a number of ways:

• through user (such as employers, job seekers, or consumers of Taxonomy) feedback

• through research (carried out by the editorial team in charge of the Taxonomy)

• through changes in governing documents (such as for teachers and nursing assistants)

• through systematic reviews of the whole set of concepts (such as when mapping to ESCO)

Collaborations

Above all, it is through collaboration with industry representatives that good quality in the occupation-name concepts is achieved.

A representative is often tied to an employers organisation or a union within a particular industry. It could also be someone working at university or governmental agency or another type of organisation with knowledge on a specific domain on the labour market.

Such collaborations are however not always possible. In these cases the Editorial team makes an assessment on whether a concept should be updated or created. As a basis for the assessment, job ads and other descriptive texts related to the term at hand are often consulted.

Quality level

Quality is defined here in relation to how well a concept is anchored within an organization representing the industry in which the concept is relevant. The quality-level attribute of an occupation-name concept can be expressed using three different levels:

Level 1. Includes level 3 and/or 2, and: the update is done in consultation with a national actor, such as an employer and industry organization, professional board, education board, or government authority, see the document. New concepts and relocation of existing ones in the SSYK structure are done in consultation with Statistiska Centralbyrån (SCB).

Level 2. Includes level 3 and: the update is done in consultation with an employer or a recruiter. New concepts and relocation of existing ones in the SSYK structure are done in consultation with SCB.

Level 3. The update is done as a result of own research, i.e. through consulting job ads, websites related to the current concept, etc. New concepts and relocation of existing ones in the SSYK structure are done in consultation with SCB.

The quality-levelattribute is unique for occupation-name concepts. Do note however that currently only a subset of all occupation-name concepts makes use of the attribute.

Update frequency

The occupation-name concepts are continuously updated as new versions of the Taxonomy are published, approximately once every other month.

The updates that come with a new version do not cover the entire range of concepts, but instead focus on individual concepts and additions, name changes, deprecations, or changes regarding connections to other concepts.

For detailed information on each version's changes, please consult the taxonomy-version-history repo.

Standards

SKOS

SKOS (Simple Knowledge Organization System Reference) is used to describe how a concept relates to other concepts within and outside of its own terminology:

The SKOS mapping relations (relations containing "match" ) are used to represent relations to concepts within another taxonomy or terminology, e.g. ESCO-occupations.

SKOS is also used in the Taxonomy to define concepts:

Relations to other types of concepts in the Taxonomy

An occupation-name concept may be related to a number of other concept types within the Taxonomy, such as:

Constraints

• Most occupation-name concepts lack definitions (work in progress), the definition attribute is therefore generally populated with the same term as the preferred-label
• Not all concepts are up to date

Graph-QL examples

Below examples can be tested through our Graphi-QL GUI.

SSYK-level-4 groups with occupation-name concepts

query MyQuery {
  concepts(type: "ssyk-level-4") {
    id
    type
    preferred_label
    ssyk_code_2012
    narrower(type: "occupation-name") {
      id
      type
      preferred_label
      alternative_labels
    }
  }
}

Occupation-name concepts with related job titles and keywords

query MyQuery {
  concepts(type: "occupation-name") {
    id
    type
    preferred_label
    alternative_labels
    related(type: ["keyword", "job-title"]) {
      id
      type
      preferred_label
    }
  }
}

Occupation-name concepts with mapped ESCO occupations

query MyQuery {
  concepts(type: "occupation-name") {
    id
    type
    preferred_label
    alternative_labels
    exact_match(type: "esco-occupation") {
      id
      type
      preferred_label
    }
    broad_match(type: "esco-occupation") {
      id
      type
      preferred_label
    }
    narrow_match(type: "esco-occupation") {
      id
      type
      preferred_label
    }
    close_match(type: "esco-occupation") {
      id
      type
      preferred_label
    }
  }
}

Occupation structure (with Arbetsförmedlingen's occupation-fields)

query MyQuery {
  concepts(type: "occupation-field") {
    id
    type
    preferred_label
    narrower(type: "ssyk-level-4") {
      id
      type
      preferred_label
      ssyk_code_2012
      narrower(type: "occupation-name") {
        id
        type
        preferred_label
        alternative_labels
      }
    }
  }
}