Metadata & Discovery (Interoperability)

5.1 Schema.org/LRMI Profiles for Courses & Programs

Normative. Every course and program page MUST publish JSON-LD using Schema.org with LRMI terms.

• Courses: @type: "Course" + (optional) CourseInstance for cohorts.
  Required: name, identifier (stable code), version (rev), description, timeRequired, inLanguage, provider, teaches (LRMI AlignmentObject or DefinedTerm), isAccessibleForFree, learningResourceType.
• Programs: @type: "EducationalOccupationalProgram".
  Required: name, identifier (program code), timeToComplete, programPrerequisites (list of course codes), occupationalCategory (ESCO/O*NET), educationalCredentialAwarded.

Example (Course JSON-LD, minimal):

{
  "@context": ["https://schema.org", "https://lrmi.dublincore.org/jsonld/context.jsonld"],
  "@type": "Course",
  "name": "Stress Testing with Macro & Climate Scenarios",
  "identifier": "FIN-MC-318",
  "version": "25.09.1",
  "description": "Design macro/climate scenarios (Basel/ISSB), quantify EL/UL, publish board-ready DSS with provenance.",
  "timeRequired": "PT18H",
  "inLanguage": ["en","fr","es","ar"],
  "isAccessibleForFree": false,
  "provider": {"@type":"Organization","name":"GCRI"},
  "teaches": [{"@type":"DefinedTerm","name":"Stress testing","inDefinedTermSet":"https://esco.ec.europa.eu"}]
}

5.2 Dublin Core & IEEE LOM / ISO/IEC 19788 (MLR) Crosswalks

Purpose. Ensure repository and catalog portability.

• Crosswalk policy: For every course/program, maintain a mapping file (/metadata/<code>.xwalk.json) that links:
  • schema:name → dc:title, lom:general.title, mlr:statementOfTitle
  • schema:identifier → dc:identifier, lom:general.identifier, mlr:identifier
  • schema:description → dc:description, lom:general.description, mlr:description
  • schema:version → dc:hasVersion, lom:lifeCycle.version, mlr:version
  • schema:inLanguage → dc:language, lom:general.language, mlr:language
  • lrmi:teaches → dc:subject, lom:educational.description, mlr:learningObjective
  • schema:timeRequired → lom:educational.typicalLearningTime, mlr:learningTime
• Validation: Crosswalks MUST be tested in the catalog linter.

5.3 DCAT-AP for Catalogs & Dataset Listings

Catalogs. Publish a DCAT-AP catalog for courses, programs, articles, and datasets.

• Catalog root (dcat:Catalog) with dct:title, dct:publisher, dct:issued, dcat:dataset.
• Course as dcat:Dataset (discovery record) pointing to course page and JSON-LD.
• Datasets (labs/artifacts): use DCAT-AP with dcat:distribution (CSV/GeoTIFF/Parquet) and licenses (SPDX).

Snippet:

{
  "@context": "https://www.w3.org/ns/dcat#",
  "@type": "dcat:Catalog",
  "dct:title": "Nexus Academy Course Catalog",
  "dcat:dataset": [{"@type":"dcat:Dataset","dct:identifier":"FIN-MC-318","dct:title":"Stress Testing..."}]
}

5.4 JSON-LD Embeds & Validation

• Placement: One JSON-LD block per page (course/program), server-rendered.
• Validation: MUST pass Google Rich Results Test (where applicable) and JSON-LD schema validation in CI.
• Canonicalization: Use stable codes in identifier; use version for rev.
• Integrity: Include sameAs for DOI where present.

5.5 OAI-PMH Endpoints & Sets (courses, programs, articles, datasets)

Endpoint: /oai with sets:

• set=courses (Course records, LRMI/DC crosswalk)
• set=programs (EducationalOccupationalProgram)
• set=articles (JATS)
• set=datasets (DataCite/DCAT-AP)

Records: oai_dc and lrmi metadata formats; for articles, jats format.
Operations: Identify, ListSets, ListRecords, GetRecord. Updates triggered on rev changes.

5.6 Sitemaps, Canonical Tags & SEO

• Sitemaps: sitemap_index.xml → courses.xml, programs.xml, articles.xml, datasets.xml.
• Canonical: course pages MUST declare <link rel="canonical" href="/academy/courses/<code>">.
• Hreflang: publish language alternates (en, fr, es, ar), including RtL where used.
• Noindex: deprecated/superseded rev-specific views use noindex but keep canonical to the stable page.

5.7 ORCID/ROR Integration for People/Orgs

• Authors/Instructors: collect ORCID iDs; display and embed in JSON-LD (Person.identifier).
• Organizations: include ROR IDs for GCRI and partner institutions.
• Programs: occupationalCategory may include ESCO codes; use ROR for employer partners where applicable.

5.8 Persistent Identifiers (DOI via Crossref/DataCite)

• Articles: Crossref DOI with JATS deposit; reference course codes in article-meta/kwd-group.
• Datasets/Software: DataCite DOI; include relatedIdentifier linking to course codes and program codes; include SPDX license.
• Artifacts: capstone/public artifacts SHOULD receive DOIs if cited externally.

5.9 JATS & JATS4R for Journal Articles

• Format: NISO JATS 1.3 (Green) with JATS4R recommendations.
• Metadata: CRediT roles, ORCID for authors, ROR for affiliations, funding statements, data availability, ethics.
• Links: related-article to course code; related-object to DataCite DOIs.

Minimal JATS stub (excerpt):

<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article">
  <front><article-meta>
    <title-group><article-title>Parametric Triggers for Climate Risk</article-title></title-group>
    <contrib-group>
      <contrib contrib-type="author"><contrib-id contrib-id-type="orcid">0000-0002-...</contrib-id></contrib>
    </contrib-group>
    <kwd-group><kwd>FIN-MC-318</kwd></kwd-group>
  </article-meta></front>
</article>

5.10 STAC/OGC/ISO 19115 for EO/GIS Artifacts

• EO assets: publish STAC Items/Collections with assets (GeoTIFF/COG, Zarr, Parquet), projections, and licensing.
• OGC APIs: expose OGC API – Features/Coverages/Tiles for dynamic layers used in labs.
• ISO 19115/19157: include metadata and quality statements for geospatial datasets; produce ISO 19139 XML where required.
• Linkage: STAC/DataCite records MUST carry related links to course codes and DOIs.

STAC Item (excerpt):

{
  "type": "Feature",
  "stac_version": "1.0.0",
  "id": "ENV-311-drought-trigger-2025-09",
  "properties": {"datetime": "2025-09-01T00:00:00Z"},
  "assets": {"cog": {"href": ".../drought.tif", "type": "image/tiff; application=geotiff"}},
  "links": [{"rel": "related", "href": "/academy/courses/ENV-MC-311"}]
}

Acceptance Checks

• JSON-LD passes validation and includes stable identifier + version.
• OAI-PMH sets respond with 200 and return at least one record per set.
• Sitemaps list all live courses/programs; hreflang present for localized pages.
• ORCID/ROR identifiers included where applicable.
• Articles/datasets with DOIs resolve; JATS/DataCite deposits validated.
• STAC and ISO 19115 metadata present for EO/GIS artifacts used in labs.