Reject Nested Expression

Review ask

As a clinical trial statistician or programmer, answer two short questions in Your review: the task and the inputs. Agreeing with both approves this benchmark; disagreeing with either needs a comment. Propose a fix with the Edit button on any source file, or add it to your comments.

We suggest spending no more than 5 minutes on a review. The other tabs beside Your review are background for assessment, not under review.

Summary

EditUnder reviewWhat this benchmark means

README.md

Public entries: Python and R. Passing coverage requires an installed inventory.

Goal: carry COUNTRY on one record per subject, holding the subject's collected country in capitals, or the site country when the subject's own entry is blank.

Input: collected demographics records carrying the collected country (COUNTRY) and the site country (SITECNTY).

Variables:

COUNTRY would be the subject's own country in capitals, or the site country in capitals when the subject's own entry is blank.

Note: the uppercasing step is also asked to choose between the two entries, but it can only read one named value. Choosing the entry is a step of its own whose result must be named first, so the run is rejected before any data is read and no artifact is accepted.

How to fix

Derive the selected source in a helper column, then pass that value to the uppercasing step:

- name: COUNTRYSRC
  type: str
  derivation:
    first_available:
      sources: [DM.COUNTRY, DM.SITECNTY]

- name: COUNTRY
  type: str
  derivation:
    str_case:
      source: COUNTRYSRC
      to: upper

Keep the helper column out of the artifact by leaving it off the artifact column list. A subject with both entries blank then gets a blank country.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: invalid_field_type
rule: SCHEMA-12

expected/error.yaml

phase: validation
condition: invalid_field_type
spec_paths:
  - columns.COUNTRY.derivation.str_case.source
rule: SCHEMA-12
context:
  expected: variable
  actual: mapping

YAML specification

1 spec file

spec.yaml

Edit34 lines

1yamaa: "1.0"2type: spec3model: ADaM4domain: ADSL5keys: [STUDYID, USUBJID]6input:7  DM: input/dm.csv89output:10  path: adsl.csv11  columns: [STUDYID, USUBJID, COUNTRY]1213columns:14  - name: STUDYID15    type: str16    label: Study Identifier17    derivation: DM.STUDYID1819  - name: USUBJID20    type: str21    label: Unique Subject Identifier22    derivation: DM.USUBJID2324  - name: COUNTRY25    type: str26    label: Country27    # str_case reads one named variable; a nested first_available in its28    # place is rejected before any data is read.29    derivation:30      str_case:31        source:32          first_available:33            sources: [DM.COUNTRY, DM.SITECNTY]34        to: upper

Inputs

Under review1 source file

input/dm.csv

Edit2 rows

input/dm.csv
STUDYID	USUBJID	COUNTRY	SITECNTY
PILOT7		Deutschland	Germany
PILOT7		—	France

Unexpected Output

Under reviewNo artifact is produced

No fixture files in this directory.

Shaded columns are derived— = missing value

Human review and assessment

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	COUNTRY	Country	character	Convert {'first_available': {'sources': ['DM.COUNTRY', 'DM.SITECNTY']}} to upper case.	Derived

Version	Date	Author	Description
1.7	2026-10-20	yamaa docs build	Read a specification in the 1.0 surface as its 0.5 counterpart; state that missing values stay missing where a mapping declares no missing handler, and leave out a declared missing answer that restates a handler's default
1.6	2026-10-17	yamaa docs build	Describe collected date parts written as ISO 8601 date text and times of day counted in seconds since midnight
1.5	2026-10-17	yamaa docs build	Name collected precision in words instead of letter codes; state imputation fallbacks, minimum source precision, bounds ignored outside the collected period, and invalid text with no handler as an error; describe date and datetime shifts, imputation flag codes, and partial text giving no date part
1.4	2026-10-15	yamaa docs build	State datetime precision codes through the hour and minute, and complete only the time parts a collected datetime lacks
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

Your review

Mapping spec