Reject a source ordinal name collision

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: preserve collected values when original record positions are requested for review.

Input: a listing with record labels and a collected position field.

Expected: the run is rejected when a generated position would replace a collected field. The stored values are never overwritten or renamed.

How to fix

Choose an ordinal name that is absent from the stored input fields, such as ordinal: OriginalPosition, and reference SOURCE.OriginalPosition in the consuming expressions. See REQ-1294.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: ordinal_field_collision
requirement: REQ-1294

expected/error.yaml

phase: validation
condition: ordinal_field_collision
spec_paths:
  - input.SOURCE.ordinal
requirement: REQ-1294
context:
  dataset: SOURCE
  field: SourceOrdinal

YAML specification

1 spec file

spec.yaml

Edit17 lines

1schema_version: "1.0"2domain: RECORDS3keys: [RECORD_LABEL]4input:5  SOURCE:6    path: input/source.csv7    ordinal: SourceOrdinal89output:10  path: records.csv11  columns: [RECORD_LABEL]1213columns:14  - name: RECORD_LABEL15    type: str16    label: Collected Record Label17    derivation: SOURCE.RecordLabel

Inputs

Under review1 source file

input/source.csv

Edit1 row

input/source.csv
RecordLabel	SourceOrdinal
ROW_B	collected-value

Unexpected Output

Under reviewNo artifact is produced

No fixture files in this directory.

Shaded columns are derived— = missing value

Comments and assessment materials

Variable Name	Variable Label	Type	Length	Controlled Terms or Format	Origin	Core	Conversion Definition	Variable Type	Variable Order	Comments for Define
RECORD_LABEL	Collected Record Label	Char			Collected		Copy value from SOURCE.RecordLabel.	SDTM	1

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/source.csv

Comments

Mapping spec