Reject Structured Literal

Review ask

As a clinical trial statistician or programmer, challenge anything in this benchmark: describe a problem in Comments, or propose a fix with the Edit button on any source file.

Task: Is this a specification error a study team could realistically make, and should the build stop on it rather than continue?
Inputs: Do they trigger the failure for the reason the summary gives?
Expected failure: Is this the right error, raised at the right point, and would it tell the programmer what to fix?

The other tabs beside Comments are background for assessment, not under review.

Summary

EditUnder reviewWhat this benchmark means

README.md

Goal: carry age into AGE and group subjects into AGEGRP, with the older group holding elderly and the younger group holding younger.

Input: collected demographics carrying age (AGE).

Variables:

AGEGRP would contain elderly for subjects aged 65 or older and younger for everyone else, including a subject with no recorded age. The older group's fixed value is written as a structure instead of a single value, and no reader may guess which part names the group, so the run is rejected before any data is read and no artifact is accepted.

How to fix

Decide the exact text the group carries, then write that single value. When the older group reads as one word, state the word:

- when: "AGE >= 65"
  then: {literal: elderly}

When the value genuinely has parts, each part needs its own result column rather than sharing one.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: invalid_field_type
requirement: REQ-0287

expected/error.yaml

phase: validation
condition: invalid_field_type
spec_paths:
  - columns.AGEGRP.derivation.case[0].then.literal
requirement: REQ-0287
context:
  expected: literal_value
  actual: mapping

YAML specification

1 spec file

spec.yaml

Edit37 lines

1schema_version: "1.0"2domain: ADSL3keys: [STUDYID, USUBJID]4input:5  DM: input/dm.csv67output:8  path: adsl.csv9  columns: [STUDYID, USUBJID, AGE, AGEGRP]1011columns:12  - name: STUDYID13    type: str14    label: Study Identifier15    derivation: DM.STUDYID1617  - name: USUBJID18    type: str19    label: Unique Subject Identifier20    derivation: DM.USUBJID2122  - name: AGE23    type: int24    label: Age25    derivation: DM.AGE2627  - name: AGEGRP28    type: str29    label: Age Group30    derivation:31      # The first branch's fixed value is a mapping, not a single value, so32      # the specification is rejected before any data is read. A missing AGE33      # would reach otherwise and get younger.34      case:35        - when: "AGE >= 65"36          then: {literal: {group: elderly}}37        - otherwise: {literal: younger}

Inputs

Under review1 source file

input/dm.csv

Edit4 rows

input/dm.csv
STUDYID	USUBJID	AGE
YAMAA-01		72
YAMAA-01		54
YAMAA-01		65
YAMAA-01		—

Unexpected Output

Under reviewNo artifact is produced

No fixture files in this directory.

Shaded columns are derived— = missing value

Comments and assessment materials

Dataset Name	Variable Name	Variable Label	Type	Computational Method	Origin
ADSL	STUDYID	Study Identifier	character	Copy value from DM.STUDYID.	Predecessor
ADSL	USUBJID	Unique Subject Identifier	character	Copy value from DM.USUBJID.	Predecessor
ADSL	AGE	Age	numeric	Copy value from DM.AGE.	Predecessor
ADSL	AGEGRP	Age Group	character	If AGE >= 65 then "{'group': 'elderly'}"; otherwise "younger".	Derived

Version	Date	Author	Description
1.3	2026-09-29	yamaa docs build	Show study codelist names, external dictionaries, and ISO 8601 formats in variable rows; list the document's codelist values and metadata
1.2	2026-09-29	yamaa docs build	Classify ADaM copies from a declared input as Predecessor and recodes as Derived, and SDTM recodes of locally derived columns as Derived
1.1	2026-09-29	yamaa docs build	Resolve lookups into the donor record they select, and give every derivation shape a plain-language rule instead of its raw YAML
1.0		yamaa docs build	Initial generation from spec.yaml

How to fix

input/dm.csv

Comments

Mapping spec