Skip to content

MOCK_API_ENDPOINTS.md

Latest commit

 

History

History
733 lines (576 loc) · 27.4 KB

MOCK_API_ENDPOINTS.md

File metadata and controls

733 lines (576 loc) · 27.4 KB

Mock API - Endpoints Documentation

This guide explains how to use the mock API endpoints for testing the DDI REST API.

Overview

The mock server serves realistic data examples in both French and English, including:

  • Variables
  • Concepts
  • Concept Schemes
  • Variable Schemes
  • Code Lists
  • Code List Schemes
  • Category Schemes
  • Categories

Resource identifiers (URN vs plain ID)

The mock server applies the same rules as the OpenAPI specification:

Form Path or filter value Required query parameters
DDI URN urn:ddi:{agency}:{resource-id}:{version} None (URN is sufficient).
Plain ID e.g. var-001, concept-001 agencyID and version on the same request.
  • Single-resource URLs (GET .../variables/var-001): use either a full URN in the path, or a plain ID with ?agencyID=...&version=.... The resourceID query parameter is for list endpoints only, not for these paths.
  • List URLs with filters that contain plain IDs (variableID, conceptReference, resourceID, studyID, etc.): you must also pass agencyID and version.
  • If plain IDs are present but agencyID or version is missing: 400 Bad Request with an explanatory message.
  • Filters that use only URNs (e.g. urn=urn:ddi:...) or only non-ID filters (agencyID, offset, …) do not require the plain-ID context.
  • There is no endpoint that resolves a bare plain ID without agency/version context (no cross-agency disambiguation).

Mock data for examples below uses agencyID=example.agency and version=1.0.0.

Response Formats

The mock API supports DDI-specific formats only:

  • DDI JSON (default): application/vnd.ddi.structure+json;version=3.3
  • DDI XML: application/vnd.ddi.structure+xml;version=3.3

The format is determined by the Accept header in your request.

Default Behavior: If no Accept header is provided (or if Accept: */* is sent), the API returns DDI JSON format by default. You don't need to specify the Accept header to get JSON responses.

Note: Generic formats (application/json, application/xml, text/xml) are not supported and will return a 406 Not Acceptable error.

Aggregated items (GET /ddi/v1/items)

Use this first when you want the full mock corpus in one round-trip: all collections (variables, concepts, schemes, study units, datasets, …) are returned together as an ItemCatalog object in DDI JSON, or as one flattened ResourcePackage in DDI XML.

Filtering matches the per-type list endpoints: you can pass the same query parameters as for GET /variables, GET /concepts, etc. (union documented in ddi-rest.yaml on GET /items). Each parameter only affects the collections where it applies (e.g. variableID narrows variables; studyID narrows variables and datasets as on those routes). Plain IDs in those filters still require agencyID and version on the same request; URNs do not.

Single item (polymorphic): GET /ddi/v1/items/{itemIdentifier} — same resolution rules as type-specific item URLs: path may be a full URN, a {agencyID}:{id}:{version} triple (without urn:ddi:), or a plain id with agencyID and version in the query. The server walks collections in a fixed order and returns the first match (see OpenAPI).

  • offset / limit: applied per collection (as if you called each list endpoint with the same query).
  • references: resolve nested references like on collection endpoints; payloads can be large.

All Endpoints Supported

All endpoints from the OpenAPI specification are implemented:

Aggregated items:

  • GET /ddi/v1/items — all item collections in one response (same filter query params as the list endpoints; see OpenAPI)
  • GET /ddi/v1/items/{itemIdentifier} — one item, polymorphic (URN, agency:id:version in path, or plain id + agencyID / version query)

List endpoints (with filtering and pagination), by type:

  • GET /ddi/v1/variables
  • GET /ddi/v1/concepts
  • GET /ddi/v1/concept-schemes
  • GET /ddi/v1/variable-schemes
  • GET /ddi/v1/code-lists
  • GET /ddi/v1/code-list-schemes
  • GET /ddi/v1/category-schemes
  • GET /ddi/v1/study-units
  • GET /ddi/v1/physical-instances
  • GET /ddi/v1/datasets

Single Resource Endpoints:

  • GET /ddi/v1/variables/{variableID}
  • GET /ddi/v1/concepts/{conceptID}
  • GET /ddi/v1/concept-schemes/{conceptSchemeID}
  • GET /ddi/v1/variable-schemes/{variableSchemeID}
  • GET /ddi/v1/code-lists/{codeListID}
  • GET /ddi/v1/code-list-schemes/{codeListSchemeID}
  • GET /ddi/v1/category-schemes/{categorySchemeID}
  • GET /ddi/v1/study-units/{studyUnitID}
  • GET /ddi/v1/physical-instances/{physicalInstanceID}
  • GET /ddi/v1/datasets/{datasetID}

Search endpoints:

  • GET /ddi/v1/search/labels - Search resources by label

Utility endpoints:

  • GET /health - Health check
  • GET / - Service information

Local Development

Start the Mock Server

yarn mock

The mock server will run on http://localhost:4010

Test the Mock API

DDI JSON (default):

# Query suffix for plain IDs in path (required unless you use a full URN in the path)
# ?agencyID=example.agency&version=1.0.0

# Narrow to one concept via polymorphic item URL (scoped triple in path — no query needed)
curl "http://localhost:4010/ddi/v1/items/example.agency:concept-001:1.0.0"

# Same concept via full URN in path
curl "http://localhost:4010/ddi/v1/items/urn:ddi:example.agency:concept-001:1.0.0"

# All item collections at once (ItemCatalog — recommended to explore the mock)
curl http://localhost:4010/ddi/v1/items

# Same, with agency/version narrowing each collection
curl "http://localhost:4010/ddi/v1/items?agencyID=example.agency&version=1.0.0"

# Narrow variables via variableID (plain ID needs agency + version, same as GET /variables)
curl "http://localhost:4010/ddi/v1/items?variableID=var-001&agencyID=example.agency&version=1.0.0"

# Get all variables (DDI JSON - default)
curl http://localhost:4010/ddi/v1/variables

# Explicit DDI JSON request
curl -H "Accept: application/vnd.ddi.structure+json;version=3.3" http://localhost:4010/ddi/v1/variables

# Get a specific variable by plain ID (agency + version required)
curl "http://localhost:4010/ddi/v1/variables/var-001?agencyID=example.agency&version=1.0.0"

# Same resource via URN in the path (no agency/version query needed)
curl "http://localhost:4010/ddi/v1/variables/urn:ddi:example.agency:var-001:1.0.0"

# Get a specific variable with direct references resolved (children level)
curl "http://localhost:4010/ddi/v1/variables/var-001?agencyID=example.agency&version=1.0.0&references=children"

# Get a specific variable with all references resolved recursively
curl "http://localhost:4010/ddi/v1/variables/var-001?agencyID=example.agency&version=1.0.0&references=all"

# Get all concepts
curl http://localhost:4010/ddi/v1/concepts

# Get a specific concept (plain ID + agency context)
curl "http://localhost:4010/ddi/v1/concepts/concept-001?agencyID=example.agency&version=1.0.0"

# Get a specific concept with direct references resolved
curl "http://localhost:4010/ddi/v1/concepts/concept-001?agencyID=example.agency&version=1.0.0&references=children"

# Get a specific concept with all references resolved recursively
curl "http://localhost:4010/ddi/v1/concepts/concept-001?agencyID=example.agency&version=1.0.0&references=all"

# Get all code lists
curl http://localhost:4010/ddi/v1/code-lists

# Get a specific code list (plain ID + agency context)
curl "http://localhost:4010/ddi/v1/code-lists/codelist-001?agencyID=example.agency&version=1.0.0"

# Get a specific code list with direct references resolved
curl "http://localhost:4010/ddi/v1/code-lists/codelist-001?agencyID=example.agency&version=1.0.0&references=children"

# Get a specific code list with all references resolved recursively
curl "http://localhost:4010/ddi/v1/code-lists/codelist-001?agencyID=example.agency&version=1.0.0&references=all"

# Health check
curl http://localhost:4010/health

DDI XML:

# Get all variables (DDI XML)
curl -H "Accept: application/vnd.ddi.structure+xml;version=3.3" http://localhost:4010/ddi/v1/variables

# Get a specific variable (DDI XML) — plain ID needs agency + version
curl -H "Accept: application/vnd.ddi.structure+xml;version=3.3" "http://localhost:4010/ddi/v1/variables/var-001?agencyID=example.agency&version=1.0.0"

# Get variable with references resolved (DDI XML)
curl -H "Accept: application/vnd.ddi.structure+xml;version=3.3" "http://localhost:4010/ddi/v1/variables/var-001?agencyID=example.agency&version=1.0.0&references=all"

# Get all concepts (DDI XML)
curl -H "Accept: application/vnd.ddi.structure+xml;version=3.3" http://localhost:4010/ddi/v1/concepts

# Get a specific concept (DDI XML)
curl -H "Accept: application/vnd.ddi.structure+xml;version=3.3" "http://localhost:4010/ddi/v1/concepts/concept-001?agencyID=example.agency&version=1.0.0"

# Get code lists (DDI XML)
curl -H "Accept: application/vnd.ddi.structure+xml;version=3.3" http://localhost:4010/ddi/v1/code-lists

Search Endpoints

Search by Labels

The /ddi/v1/search/labels endpoint allows you to search for DDI resources by matching their labels.

Endpoint: GET /ddi/v1/search/labels

Parameters:

  • q (required): Search query string. Case-insensitive partial matching.
  • lang (optional): Language code for label search (en or fr). Default: en
  • type (optional): Filter results by resource type. Can be one or more of: Variable, Concept, ConceptScheme, VariableScheme, CodeList, CodeListScheme, CategoryScheme, Category
  • offset (optional): Pagination offset. Default: 0
  • limit (optional): Maximum number of results. Default: 100, Maximum: 1000

Examples:

# Search for "age" in English labels (default)
curl "http://localhost:4010/ddi/v1/search/labels?q=age"

# Search for "âge" in French labels
curl "http://localhost:4010/ddi/v1/search/labels?q=âge&lang=fr"

# Search only in Variables
curl "http://localhost:4010/ddi/v1/search/labels?q=baseline&type=Variable"

# Search in multiple resource types
curl "http://localhost:4010/ddi/v1/search/labels?q=gender&type=Variable&type=Concept"

# Search with pagination
curl "http://localhost:4010/ddi/v1/search/labels?q=age&offset=0&limit=10"

# Search in DDI XML format
curl -H "Accept: application/vnd.ddi.structure+xml;version=3.3" "http://localhost:4010/ddi/v1/search/labels?q=age"

Response Format:

Each result contains:

  • type: The resource type (Variable, Concept, ConceptScheme, etc.)
  • urn: The URN of the resource
  • id: The identifier of the resource
  • agencyID: The agency ID
  • version: The version
  • label: All labels for the resource (in all languages)
  • matchedLabel: The specific label that matched the search query (in the specified language)

Example Response:

[
  {
    "type": "Variable",
    "urn": "urn:ddi:example.agency:var-001:1.0.0",
    "id": "var-001",
    "agencyID": "example.agency",
    "version": "1.0.0",
    "label": [
      {
        "lang": "en",
        "value": "Age at baseline examination"
      },
      {
        "lang": "fr",
        "value": "Âge à l'examen de base"
      }
    ],
    "matchedLabel": {
      "lang": "en",
      "value": "Age at baseline examination"
    }
  }
]

Notes:

  • The search is case-insensitive
  • Partial matching is performed (e.g., searching for "age" will match "Age at baseline" and "average")
  • Only labels in the specified language (lang parameter) are searched
  • If no type parameter is provided, all resource types are searched
  • Results are paginated using offset and limit parameters

Understanding the references Parameter

The references query parameter controls how referenced objects are returned. It supports three levels:

Important: When references are resolved (references=children or references=all), the property name changes from xxxReference to xxx. Only one property is present, never both. For example:

  • conceptReference → concept (full Concept object)
  • codeListReference → codeList (full CodeList object)
  • categoryReference → category (full Category object)
  • subclassOfReference → subclassOf (full Concept object)
  • sourceVariableReference → sourceVariable (full Variable object)

Note: Objects that are children of schemes (like Concepts in ConceptScheme, CodeLists in CodeListScheme) do not have references back to their parent scheme. The relationship is one-way: schemes contain lists of their children. When references=children or references=all, these identifier lists are resolved to full objects.

  • references=none (default): Returns only references (URN, id, agencyID, version, typeOfObject)

    curl "http://localhost:4010/ddi/v1/variables/var-001?agencyID=example.agency&version=1.0.0"
# or explicitly
curl "http://localhost:4010/ddi/v1/variables/var-001?agencyID=example.agency&version=1.0.0&references=none"

    Response includes:

    {
  "conceptReference": {
    "urn": "urn:ddi:example.agency:concept-001:1.0.0",
    "id": "concept-001",
    "agencyID": "example.agency",
    "version": "1.0.0",
    "typeOfObject": "Concept"
  }
}

  • references=children: Returns full referenced objects at the root level, but references within those objects remain as references. The property name changes from xxxReference to xxx when resolved.

    curl "http://localhost:4010/ddi/v1/variables/var-001?agencyID=example.agency&version=1.0.0&references=children"

    Response includes:

    {
  "concept": {
    "urn": "urn:ddi:example.agency:concept-001:1.0.0",
    "id": "concept-001",
    "name": [{"lang": "en", "value": "age"}],
    "label": [{"lang": "en", "value": "Age"}],
    "description": [...],
    "definition": [...],
    "isUniversallyUnique": true
  }
}

    Note: The conceptReference property is replaced by concept containing the full Concept object. Concepts do not have references back to their parent ConceptScheme.

  • references=all: Returns full referenced objects recursively, including all nested references. The property name changes from xxxReference to xxx when resolved.

    curl "http://localhost:4010/ddi/v1/variables/var-001?agencyID=example.agency&version=1.0.0&references=all"

    Response includes:

    {
  "concept": {
    "urn": "urn:ddi:example.agency:concept-001:1.0.0",
    "id": "concept-001",
    "name": [{"lang": "en", "value": "age"}],
    "label": [{"lang": "en", "value": "Age"}],
    "description": [...],
    "definition": [...],
    "isUniversallyUnique": true
  }
}

    Note: All references are recursively resolved. Property names change from xxxReference to xxx (e.g., conceptReference → concept). Concepts do not have references back to their parent ConceptScheme, so there's no conceptScheme property in Concept objects.

Variable with Code List Representation

Variables can have a representation that references a code list. Here's how to retrieve them:

# Get variable with code list reference (without resolving - default)
curl "http://localhost:4010/ddi/v1/variables/var-002?agencyID=example.agency&version=1.0.0"

# Get variable with code list reference resolved (children level)
curl "http://localhost:4010/ddi/v1/variables/var-002?agencyID=example.agency&version=1.0.0&references=children"

# Get variable with code list and all nested references resolved (all level)
curl "http://localhost:4010/ddi/v1/variables/var-002?agencyID=example.agency&version=1.0.0&references=all"

With references=none (default):

{
  "id": "var-002",
  "representation": {
    "codeRepresentation": {
      "recommendedDataType": "String",
      "codeListReference": {
        "urn": "urn:ddi:example.agency:codelist-001:1.0.0",
        "id": "codelist-001",
        "agencyID": "example.agency",
        "version": "1.0.0",
        "typeOfObject": "CodeList"
      }
    }
  }
}

With references=children:

{
  "id": "var-002",
  "representation": {
    "codeRepresentation": {
      "recommendedDataType": "String",
      "codeList": {
        "urn": "urn:ddi:example.agency:codelist-001:1.0.0",
        "id": "codelist-001",
        "name": [{"lang": "en", "value": "gender_codes"}],
        "label": [{"lang": "en", "value": "Gender Codes"}],
        "codes": [
          {
            "id": "code-001",
            "value": "M",
            "category": {
              "urn": "urn:ddi:example.agency:category-001:1.0.0",
              "id": "category-001",
              "agencyID": "example.agency",
              "version": "1.0.0",
              "label": [{"lang": "en", "value": "Male"}, {"lang": "fr", "value": "Masculin"}]
            }
          },
          ...
        ]
      }
    }
  }
}

Note: The codeListReference property is replaced by codeList containing the full CodeList object with all codes. Codes have their categoryReference replaced by category (full Category object). CodeLists do not have references back to their parent CategoryScheme.

With references=all:

{
  "id": "var-002",
  "representation": {
    "codeRepresentation": {
      "recommendedDataType": "String",
      "codeList": {
        "urn": "urn:ddi:example.agency:codelist-001:1.0.0",
        "id": "codelist-001",
        "name": [{"lang": "en", "value": "gender_codes"}],
        "label": [{"lang": "en", "value": "Gender Codes"}],
        "codes": [
          {
            "id": "code-001",
            "value": "M",
            "category": {
              "urn": "urn:ddi:example.agency:category-001:1.0.0",
              "id": "category-001",
              "label": [{"lang": "en", "value": "Male"}, {"lang": "fr", "value": "Masculin"}]
            }
          },
          ...
        ]
      }
    }
  }
}

Note: All references are recursively resolved and property names change: codeListReference → codeList, categoryReference → category. CodeLists do not have references back to their parent CategoryScheme, so there's no categoryScheme property in CodeList objects.

Code Lists Examples

Code lists can have nested references that are resolved at different levels:

# Get code list without references (default)
curl "http://localhost:4010/ddi/v1/code-lists/codelist-001?agencyID=example.agency&version=1.0.0"

# Get code list with direct references resolved (children level)
curl "http://localhost:4010/ddi/v1/code-lists/codelist-001?agencyID=example.agency&version=1.0.0&references=children"

# Get code list with all references resolved recursively
curl "http://localhost:4010/ddi/v1/code-lists/codelist-001?agencyID=example.agency&version=1.0.0&references=all"

With references=children:

  • categoryReference is replaced by category (full Category object) in each code
  • References inside categories remain as references
  • CodeLists do not have references back to their parent CategoryScheme

With references=all:

  • categoryReference is replaced by category (full Category object) in each code
  • All nested references are resolved recursively
  • CodeLists do not have references back to their parent CategoryScheme

Scheme Examples

Schemes (ConceptScheme, VariableScheme, CodeListScheme, CategoryScheme) contain arrays of identifiers for their children. These identifiers are resolved to full objects when references is not none:

# Get concept scheme without resolving children (default)
curl "http://localhost:4010/ddi/v1/concept-schemes/conceptscheme-001?agencyID=example.agency&version=1.0.0"

# Get concept scheme with children resolved as full objects (children level)
curl "http://localhost:4010/ddi/v1/concept-schemes/conceptscheme-001?agencyID=example.agency&version=1.0.0&references=children"

# Get concept scheme with children and all nested references resolved (all level)
curl "http://localhost:4010/ddi/v1/concept-schemes/conceptscheme-001?agencyID=example.agency&version=1.0.0&references=all"

With references=none (default):

{
  "id": "conceptscheme-001",
  "concepts": [
    {
      "urn": "urn:ddi:example.agency:concept-001:1.0.0",
      "id": "concept-001",
      "agencyID": "example.agency",
      "version": "1.0.0"
    }
  ]
}

Note: Children are returned as identifiers only (URN, id, agencyID, version).

With references=children:

{
  "id": "conceptscheme-001",
  "concepts": [
    {
      "urn": "urn:ddi:example.agency:concept-001:1.0.0",
      "id": "concept-001",
      "name": [{"lang": "en", "value": "age"}],
      "label": [{"lang": "en", "value": "Age"}],
      "description": [...],
      "definition": [...],
      "isUniversallyUnique": true
    }
  ]
}

Note: Children identifiers are resolved to full objects. References within these objects (like subclassOfReference) remain as references.

With references=all:

{
  "id": "conceptscheme-001",
  "concepts": [
    {
      "urn": "urn:ddi:example.agency:concept-001:1.0.0",
      "id": "concept-001",
      "name": [{"lang": "en", "value": "age"}],
      "label": [{"lang": "en", "value": "Age"}],
      "description": [...],
      "definition": [...],
      "subclassOf": {
        "urn": "urn:ddi:example.agency:concept-004:1.0.0",
        "id": "concept-004",
        "name": [...],
        "label": [...]
      },
      "isUniversallyUnique": true
    }
  ]
}

Note: Children identifiers are resolved to full objects with all their references recursively resolved. Property names change from xxxReference to xxx (e.g., subclassOfReference → subclassOf).

This applies to all schemes:

  • ConceptScheme: concepts array is resolved to full Concept objects
  • VariableScheme: variables array is resolved to full Variable objects
  • CodeListScheme: codeLists array is resolved to full CodeList objects
  • CategoryScheme: categories array is resolved to full Category objects

Filtering Examples

All list endpoints support filtering with query parameters. Here are examples:

Filter by Agency ID

# Get all variables from a specific agency
curl "http://localhost:4010/ddi/v1/variables?agencyID=example.agency"

# Get multiple agencies (comma-separated or multiple parameters)
curl "http://localhost:4010/ddi/v1/variables?agencyID=example.agency&agencyID=other.agency"

Filter by Resource ID

# Get specific variables by ID (plain IDs need agency + version on the same request)
curl "http://localhost:4010/ddi/v1/variables?resourceID=var-001&agencyID=example.agency&version=1.0.0"

# Get multiple variables
curl "http://localhost:4010/ddi/v1/variables?resourceID=var-001&resourceID=var-002&agencyID=example.agency&version=1.0.0"

Filter by Version

# Get variables with specific version
curl "http://localhost:4010/ddi/v1/variables?version=1.0.0"

# Get multiple versions
curl "http://localhost:4010/ddi/v1/variables?version=1.0.0&version=2.0.0"

Filter by URN

# Get variable by URN
curl "http://localhost:4010/ddi/v1/variables?urn=urn:ddi:example.agency:var-001:1.0.0"

Filter Variables by Concept Reference

# Get variables that reference a specific concept (plain concept ID needs agency + version)
curl "http://localhost:4010/ddi/v1/variables?conceptReference=concept-001&agencyID=example.agency&version=1.0.0"

# Or by URN (no extra agency/version needed)
curl "http://localhost:4010/ddi/v1/variables?conceptReference=urn:ddi:example.agency:concept-001:1.0.0"

Pagination

# Get first 10 variables (offset 0, limit 10)
curl "http://localhost:4010/ddi/v1/variables?offset=0&limit=10"

# Get next 10 variables
curl "http://localhost:4010/ddi/v1/variables?offset=10&limit=10"

# Get all variables starting from offset 5
curl "http://localhost:4010/ddi/v1/variables?offset=5"

Combined Filters

# Combine multiple filters
curl "http://localhost:4010/ddi/v1/variables?agencyID=example.agency&version=1.0.0&limit=5"

# Filter by concept and resolve direct references
curl "http://localhost:4010/ddi/v1/variables?conceptReference=concept-001&agencyID=example.agency&version=1.0.0&references=children"

# Filter, paginate, and resolve all references recursively
curl "http://localhost:4010/ddi/v1/variables?agencyID=example.agency&offset=0&limit=10&references=all"

Filter Code Lists

# Get code lists by agency
curl "http://localhost:4010/ddi/v1/code-lists?agencyID=example.agency"

# Get specific code list by ID
curl "http://localhost:4010/ddi/v1/code-lists?resourceID=codelist-001&agencyID=example.agency&version=1.0.0"

# Get code lists with pagination
curl "http://localhost:4010/ddi/v1/code-lists?offset=0&limit=5"

Filter Concepts

# Get concepts by agency
curl "http://localhost:4010/ddi/v1/concepts?agencyID=example.agency"

# Get specific concepts by ID
curl "http://localhost:4010/ddi/v1/concepts?conceptID=concept-001&conceptID=concept-002&agencyID=example.agency&version=1.0.0"

# Get concepts with resolved references (children level)
curl "http://localhost:4010/ddi/v1/concepts?agencyID=example.agency&references=children"

# Get concepts with all references resolved recursively
curl "http://localhost:4010/ddi/v1/concepts?agencyID=example.agency&references=all"

Available Filter Parameters

All list endpoints support these query parameters:

  • urn: Filter by URN (exact match)
  • agencyID: Filter by agency ID (supports multiple values)
  • resourceID or id: Filter by resource ID (supports multiple values)
  • version: Filter by version (supports multiple values)
  • offset: Pagination offset (number)
  • limit: Pagination limit (number)
  • references: Resolve references (enum: none (default), children, or all)

Endpoint-specific filters:

  • Variables: variableID, conceptReference, studyID, datasetID
  • Concepts: conceptID, conceptSchemeID
  • Code Lists: codeListID, codeListSchemeID
  • Category Schemes: categorySchemeID

Mock Data Structure

Mock data is stored in mocks/data/ directory:

mocks/
├── data/
│   ├── variables.json              # List of variables
│   ├── variables-var-001.json     # Specific variable
│   ├── concepts.json               # List of concepts
│   ├── concepts-concept-001.json  # Specific concept
│   ├── concept-schemes.json        # List of concept schemes
│   ├── variable-schemes.json       # List of variable schemes
│   ├── code-lists.json            # List of code lists
│   ├── code-list-schemes.json     # List of code list schemes
│   ├── category-schemes.json      # List of category schemes
│   └── categories.json            # List of categories
└── server.js                       # Mock server

All mock data includes bilingual content (French and English) with:

  • Labels and descriptions in both languages
  • Complete DDI structure (URNs, references, representations)
  • Realistic examples following DDI standards

Available Mock Data

Variables:

  • var-001: Age at baseline (numeric)
  • var-002: Gender (coded)
  • var-003: Body Mass Index (numeric)

Concepts:

  • concept-001: Age
  • concept-002: Gender
  • concept-003: Body Mass Index

Schemes:

  • conceptscheme-001: Demographic Concepts Scheme
  • variablescheme-001: Baseline Variables Scheme
  • codelistscheme-001: Demographic Code Lists Scheme
  • categoryscheme-001: Gender Categories Scheme

Code Lists:

  • codelist-001: Gender codes (M, F, O)

Categories:

  • category-001: Male
  • category-002: Female
  • category-003: Other