Skip to content

Organisation Scheme Map

An Organisation Scheme Map (SDMX 3.0) maps the organisations of a source organisation scheme to the organisations of a target organisation scheme. The source and target may be different types of organisation scheme. Documents start ref: "OrganisationSchemeMap=AGENCY:ID(1.0)".

It uses the layout shared by all item scheme maps, which is described in full on the Category Scheme Map page.

Example

The document starts with the common header. Here a Data Consumer Scheme is mapped to an Organisation Unit Scheme:

format: "fusion-yaml(1.0.0)"
ref: "OrganisationSchemeMap=AGENCY:MAP(1.0)"
name: "TEST"
source: "DataConsumerScheme=AGENCY1:DATA_CONSUMERS(1.0)"
target: "OrganisationUnitScheme=AGENCY2:ORGU_S(1.0)"
mappedItems:
- source: "source2target-key1"
  target: "source2target-val1"
  startIdx: 100
  endIdx: 200
  validity: "1959-01-01T00:00:00Z/2029-12-31T23:59:59Z"
- source: "source2target-key3"
  target: "source2target-val3"
  startIdx: 100
  endIdx: 200
  validity: "1959-01-01T00:00:00Z/2029-12-31T23:59:59Z"
Source: organisationschememap/testSchemeDiffSourceTarget.yaml (trimmed)

  • source and target are canonical references, so the class name (DataConsumerScheme, OrganisationUnitScheme, DataProviderScheme, ...) identifies the type of each organisation scheme.
  • Each entry of mappedItems maps a source organisation id to a target organisation id. Entries are written in the order held by the map, not sorted. See Category Scheme Map for the optional startIdx, endIdx, pattern, validity and annotations fields.