Reject Unknown Case

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: derive the site name (SITE) for analysis use with only its first letter capitalized.

Input: collected demographics carrying the site name (SITENM), recorded in capitals.

Variables:

SITE would be the site name with its first letter capitalized and every later letter in lower case.

The requested case, capitalize, is none of the four cases a site name can be put in: upper, lower, sentence, and title. The request is rejected before any data is read, and no artifact is accepted.

How to fix

Decide which case the analysis value takes, then name it. A capital first letter followed by lower case is sentence case:

str_case:
  source: DM.SITENM
  to: sentence

A value such as BOSTON GENERAL then becomes Boston general. Writing to: title instead capitalizes each word, giving Boston General.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: value_not_permitted
requirement: REQ-0287

expected/error.yaml

phase: validation
condition: value_not_permitted
spec_paths:
  - columns.SITE.derivation.str_case.to
requirement: REQ-0287
context:
  value: capitalize
  permitted: [upper, lower, sentence, title]

YAML specification

1 spec file

spec.yaml

Edit30 lines

1schema_version: "1.0"2domain: ADSL3keys: [STUDYID, USUBJID]4input:5  DM: input/dm.csv67output:8  path: adsl.csv9  columns: [STUDYID, USUBJID, SITE]1011columns:12  - name: STUDYID13    type: str14    label: Study Identifier15    derivation: DM.STUDYID1617  - name: USUBJID18    type: str19    label: Unique Subject Identifier20    derivation: DM.USUBJID2122  # The defect: capitalize is none of the four cases (upper, lower,23  # sentence, title), so the spec is rejected before any data is read.24  - name: SITE25    type: str26    label: Site Name27    derivation:28      str_case:29        source: DM.SITENM30        to: capitalize

Inputs

Under review1 source file

input/dm.csv

Edit2 rows

input/dm.csv
STUDYID	USUBJID	SITENM
PILOT7		BOSTON GENERAL
PILOT7		LAKESIDE CLINIC

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	SITE	Site Name	character	Convert DM.SITENM to capitalize case.	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