Reject Two Text Operations Written as One Value

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: standardize the collected race (RACE) to upper case, with each run of spaces reduced to one.

Input: collected demographics, one record per subject, with the race as entered.

Variables:

DOMAIN is DM on every record.
RACE would be the collected race in upper case, with single spaces.

Note: the race is given two operations at once, a change to upper case and a reduction of repeated spaces, each reading the collected text. Nothing says which applies first or whether the second reads the first one's result, so the run is rejected before any data is read and no artifact is accepted.

How to fix

Write one operation per value, and chain them through a column of their own:

- name: RACESP
  type: str
  label: Race, Single Spaces
  derivation: {str_replace: {source: RAW.RACE, pattern: ' +',
                             replacement: ' '}}
- name: RACE
  type: str
  label: Race
  derivation: {str_case: {source: RACESP, to: upper}}

Leave RACESP out of the published columns.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: invalid_operation_count
rule: SCHEMA-7

expected/error.yaml

phase: validation
condition: invalid_operation_count
spec_paths:
  - columns.RACE.derivation
rule: SCHEMA-7
context:
  registry: expressions
  count: 2

YAML specification

1 spec file

spec.yaml

Edit36 lines

1yamaa: "1.0"2type: spec3model: SDTM4domain: DM5keys: [STUDYID, USUBJID]6input:7  RAW: input/dm_raw.csv89output:10  path: dm.csv11  columns: [DOMAIN, STUDYID, USUBJID, RACE]1213columns:14  - name: DOMAIN15    type: str16    label: Domain Abbreviation17    derivation: "'DM'"1819  - name: STUDYID20    type: str21    label: Study Identifier22    derivation: RAW.STUDYID2324  - name: USUBJID25    type: str26    label: Unique Subject Identifier27    derivation: RAW.USUBJID2829  # Two operations in one value: upper case, and runs of spaces collapsed to30  # one. Nothing says which applies first, or to what.31  - name: RACE32    type: str33    label: Race34    derivation:35      str_case: {source: RAW.RACE, to: upper}36      str_replace: {source: RAW.RACE, pattern: ' +', replacement: ' '}

Inputs

Under review1 source file

input/dm_raw.csv

Edit2 rows

input/dm_raw.csv
STUDYID	USUBJID	RACE
YAMAA-01		white
YAMAA-01		BLACK OR AFRICAN AMERICAN

Unexpected Output

Under reviewNo artifact is produced

No fixture files in this directory.

Shaded columns are derived— = missing value

Human review and assessment

Variable Name	Variable Label	Type	Origin	Conversion Definition	Variable Type	Variable Order
DOMAIN	Domain Abbreviation	Char	Assigned	Set constant value "DM".	SDTM	1
STUDYID	Study Identifier	Char	Collected	Copy value from RAW.STUDYID.	SDTM	2
USUBJID	Unique Subject Identifier	Char	Collected	Copy value from RAW.USUBJID.	SDTM	3
RACE	Race	Char	Derived	Convert RAW.RACE to upper case.	SDTM	4

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_raw.csv

Your review

Mapping spec