Reject Redefined Date

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: carry the subject randomization date RANDDT from demographics into the subject-level analysis file.

Input: a subject-level demographics file holding the study and subject identifiers with RANDDT, produced from an Operational Data Model (ODM) extract.

Variables:

RANDDT would be the subject's randomization date, taken from RANDDT in the demographics file.

Note: the date's value kind is already fixed where the demographics file is produced. Stating it again beside the source would leave two authorities for the same field even when they agree, so the run is rejected before any data is read and no artifact is accepted.

How to fix

Keep the producing DM specification as the single type authority and remove the inline types entry:

input:
  DM:
    path: input/dm.csv
    schema: input/dm.schema.yaml

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: redundant_field_type
requirement: REQ-0523

expected/error.yaml

phase: validation
condition: redundant_field_type
spec_paths:
  - input.DM.types.RANDDT
requirement: REQ-0523
context:
  dataset: DM
  field: RANDDT
  type: date

YAML specification

1 spec file

spec.yaml

Edit29 lines

1schema_version: "1.0"2domain: ADSL3keys: [STUDYID, USUBJID]4input:5  DM:6    path: input/dm.csv7    # Intentionally invalid: the producing DM specification types RANDDT.8    types: {RANDDT: date}9    schema: input/dm.schema.yaml1011output:12  path: adsl.csv13  columns: [STUDYID, USUBJID, RANDDT]1415columns:16  - name: STUDYID17    type: str18    label: Study Identifier19    derivation: DM.STUDYID2021  - name: USUBJID22    type: str23    label: Unique Subject Identifier24    derivation: DM.USUBJID2526  - name: RANDDT27    type: date28    label: Date of Randomization29    derivation: DM.RANDDT

Inputs

Under review3 source files

input/dm.csv

Edit1 row

input/dm.csv
STUDYID	USUBJID	RANDDT
YAMAA-01		2025-01-12

input/dm.schema.yaml

Edit

schema_version: "1.0"
domain: DM
keys: [STUDYID, USUBJID]
input:
  ODM: odm.csv

output:
  path: dm.csv
  columns: [STUDYID, USUBJID, RANDDT]

columns:
  - name: STUDYID
    type: str
    label: Study Identifier
    derivation: ODM.StudyOID

  - name: USUBJID
    type: str
    label: Unique Subject Identifier
    derivation: ODM.SubjectKey

  - name: RANDDT
    type: date
    label: Date of Randomization
    derivation: ODM.Value

rows:
  - id: subject
    filter: "ODM.ItemOID = 'IT.DM.RANDDT'"
    derivations: {}

input/odm.csv

Edit1 row

input/odm.csv
StudyOID	MetaDataVersionOID	SubjectKey	StudyEventOID	StudyEventRepeatKey	ItemGroupOID	ItemGroupRepeatKey	ItemOID	Value
YAMAA-01	MDV.1	YAMAA-01-001	SCREENING	1	IG.DM	1	IT.DM.RANDDT	2025-01-12

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	Codelist/Controlled Terms	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	RANDDT	Date of Randomization	numeric	ISO 8601	Copy value from DM.RANDDT.	Predecessor

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

input/dm.schema.yaml

input/odm.csv

Comments

Mapping spec