Reject Numeric Lowercase

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, in lower case.

Input: collected demographics with study and subject identifiers and the numeric site number (SITENUM).

Variables:

SITE would be the site name in lower case, but it is taken from the site number (SITENUM), and a number has no lower-case form.

The request is rejected before any data is read, and no artifact is accepted.

How to fix

Fold the collected site name rather than its number, once SITENM is present in the demographics extract:

str_case:
  source: DM.SITENM
  to: lower

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: incompatible_input_type
requirement: REQ-0308

expected/error.yaml

phase: validation
condition: incompatible_input_type
spec_paths:
  - columns.SITE.derivation.str_case.source
requirement: REQ-0308
context:
  source: SITENUM
  expected: str
  actual: int

YAML specification

1 spec file

spec.yaml

Edit36 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 site number read as an integer (DM holds it as text).23  - name: SITENUM24    type: int25    label: Site Number26    derivation: DM.SITENUM2728  # The defect: lower-casing needs text, and SITENUM is an integer, so the29  # spec is rejected before any data is read.30  - name: SITE31    type: str32    label: Site Name33    derivation:34      str_case:35        source: SITENUM36        to: lower

Inputs

Under review1 source file

input/dm.csv

Edit4 rows

input/dm.csv
STUDYID	USUBJID	SITENUM
YAMAA-01		101
YAMAA-01		102
YAMAA-01		999
YAMAA-01		1000

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 SITENUM to lower 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