Coverage-Analyse

Diese Cypher-Query macht das semantische Matching sichtbar: Demand-Profil (Demo-Job) → Anforderung → ESCO-Skill → LearningOutcome → Säule-B-Modul. Die Pfad-Konstruktion operiert über das gemeinsame ESCO-Vokabular als semantischen Anker — Demo- und Echtdaten-Seite müssen sich gegenseitig nicht kennen.

    MATCH (j:Resource {uri: "http://hr-qde.org/demo/job/J04"})-[:hrqde__hasRequirement]->(req:Resource)
          -[:hrqde__refersToCompetence]->(skill:Resource)
    OPTIONAL MATCH (skill)-[:skosxl__prefLabel]->(skillLabel:Resource)
    OPTIONAL MATCH (skill)<-[:hrqde__targetsCompetence]-(o:hrqde__LearningOutcome)
                  <-[:hrqde__hasOutcome]-(m:hrqde__EducationalModule)
    WHERE m.uri STARTS WITH "http://hr-qde.org/data/koeppe/"
    OPTIONAL MATCH (m)-[:hrqde__offeredBy]->(hei:hrqde__HigherEducationInstitution)
    WITH req, skill,
         collect(DISTINCT skillLabel.skosxl__literalForm) AS skillLabels,
         collect(DISTINCT {
             moduleUri:   m.uri,
             moduleLabel: m.rdfs__label,
             moduleCode:  m.hrqde__moduleCode,
             ects:        m.hrqde__ects,
             heiLabel:    hei.rdfs__label,
             confidence:  o.hrqde__provenanceConfidence
         }) AS modules
    RETURN req.uri                    AS reqUri,
           req.hrqde__requirementKind AS kind,
           skill.uri                  AS skillUri,
           skillLabels,
           modules
    ORDER BY
      CASE WHEN req.hrqde__requirementKind = 'must' THEN 0 ELSE 1 END,
      req.uri