Reject a Nonnumeric Padding Width

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: format a numeric laboratory sequence as an eight-character key.

Input: one laboratory record with a numeric sequence.

Variables:

IDVARVAL would be the sequence number padded to eight characters. The written width is text, so this output is rejected before data ingestion.

How to fix

Set the padding width to the number of characters required:

str_pad: {source: LB.LBSEQ, width: 8}

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.IDVARVAL.derivation.str_pad.width
requirement: REQ-0287
context:
  expected: int
  actual: str

YAML specification

1 spec file

spec.yaml

Edit26 lines

1schema_version: "1.0"2domain: ADLB3keys: [STUDYID, USUBJID, LBSEQ]4input:5  LB: {path: input/lb.csv, types: {LBSEQ: int}}6base: LB78output:9  path: adlb.csv10  columns: [STUDYID, USUBJID, LBSEQ, IDVARVAL]1112columns:13  - {name: STUDYID, type: str, label: Study Identifier, derivation: LB.STUDYID}1415  - name: USUBJID16    type: str17    label: Subject Identifier18    derivation: LB.USUBJID1920  - {name: LBSEQ, type: int, label: Sequence Number, derivation: LB.LBSEQ}2122  - name: IDVARVAL23    type: str24    label: Padded Sequence Number25    derivation:26      str_pad: {source: LB.LBSEQ, width: eight}

Inputs

Under review1 source file

input/lb.csv

Edit1 row

input/lb.csv
STUDYID	USUBJID	LBSEQ
PILOT3		259

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
ADLB	STUDYID	Study Identifier	character	Copy value from LB.STUDYID.	Predecessor
ADLB	USUBJID	Subject Identifier	character	Copy value from LB.USUBJID.	Predecessor
ADLB	LBSEQ	Sequence Number	numeric	Copy value from LB.LBSEQ.	Predecessor
ADLB	IDVARVAL	Padded Sequence Number	character	Pad LB.LBSEQ on the left with spaces to at least eight characters.	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/lb.csv

Comments

Mapping spec