Reject Reference Data Declared as Repeating

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: build the trial elements domain, one record per planned element of the trial, with the metadata a data definition describes it by.

Input: the protocol's planned elements, one record per element.

Variables:

DOMAIN is TE on every record.
ETCD would be the short code of the element.
ELEMENT would be the description of the element.

Note: the dataset is declared as reference data, which describes the trial rather than any subject, and also as repeating, which means more than one record per subject. Reference data has no subjects to repeat for, so the two declarations contradict each other, and the run is rejected before any data is read; no artifact is accepted.

How to fix

Keep the reference data declaration, and declare the dataset non-repeating:

submission:
  label: Trial Elements
  class: TRIAL DESIGN
  structure: One record per planned Element
  repeating: false
  reference_data: true

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: reference_data_repeating_conflict
rule: SUB-4

expected/error.yaml

phase: validation
condition: reference_data_repeating_conflict
spec_paths:
  - submission
rule: SUB-4

YAML specification

1 spec file

spec.yaml

Edit69 lines

1yamaa: "1.0"2type: spec3model: SDTM4domain: TE5keys: [STUDYID, ETCD]6input:7  RAW: input/te_raw.csv89output:10  path: te.csv11  columns: [DOMAIN, STUDYID, ETCD, ELEMENT]1213columns:14  - name: DOMAIN15    type: str16    label: Domain Abbreviation17    derivation: "'TE'"18    submission:19      core: Req20      role: Identifier21      length: 222      origins:23        - type: Assigned24          source: Sponsor2526  - name: STUDYID27    type: str28    label: Study Identifier29    derivation: RAW.STUDYID30    submission:31      core: Req32      role: Identifier33      length: 834      origins:35        - type: Protocol36          source: Sponsor3738  - name: ETCD39    type: str40    label: Element Code41    derivation: RAW.ETCD42    submission:43      core: Req44      role: Topic45      length: 446      origins:47        - type: Protocol48          source: Sponsor4950  - name: ELEMENT51    type: str52    label: Description of Element53    derivation: RAW.ELEMENT54    submission:55      core: Req56      role: Synonym Qualifier57      length: 958      origins:59        - type: Protocol60          source: Sponsor6162# The trial elements are reference data, one record per element, yet the63# dataset is declared to repeat.64submission:65  label: Trial Elements66  class: TRIAL DESIGN67  structure: One record per planned Element68  repeating: true69  reference_data: true

Inputs

Under review1 source file

input/te_raw.csv

Edit3 rows

input/te_raw.csv
STUDYID	ETCD	ELEMENT
YAMAA-01	SCRN	Screening
YAMAA-01	TRT	Treatment
YAMAA-01	FU	Follow-up

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	Length	Origin	Core	Conversion Definition	Variable Type	Variable Order
DOMAIN	Domain Abbreviation	Char	2	Assigned	Req	Set constant value "TE".	SDTM	1
STUDYID	Study Identifier	Char	8	Protocol	Req	Copy value from RAW.STUDYID.	SDTM	2
ETCD	Element Code	Char	4	Protocol	Req	Copy value from RAW.ETCD.	SDTM	3
ELEMENT	Description of Element	Char	9	Protocol	Req	Copy value from RAW.ELEMENT.	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/te_raw.csv

Your review

Mapping spec