yamaa 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 meansREADME.mdPublic entries: Python and R. Passing coverage requires an installed inventory.
Goal: build a subject-level listing carrying SITEID and
SEX.
Input: collected demographics records for two subjects at one
site, carrying SITEID and two fields both named SEX. The two
fields agree for the first subject and disagree for the second, so
no single answer is defensible there.
Variables:
SITEIDwould contain the site the subject enrolled at, copied from the collected records.SEXwould contain the recorded sex, copied from the collected records, but a value asked for by that name could come from either of the two fields, which disagree for the second subject.
The run is rejected when the listing is read and no artifact is accepted.
How to fix
Give every field of the listing its own name. If the second field holds the sex as it was first collected, name it for that, and read whichever one the study governs:
STUDYID,USUBJID,SITEID,SEX,SEXORIG
If the two fields hold the same fact twice, remove one at the source. A listing that answers to one name twice cannot be read the same way twice.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- ingest
- condition
- source_field_name_duplicate
- rule
- CSV-16
expected/error.yaml
phase: ingest
condition: source_field_name_duplicate
spec_paths:
- input.DM.path
rule: CSV-16
context:
dataset: DM
path: input/dm.csv
record: 1
field: SEX
Inputs
Under review1 source fileinput/dm.csv
Editraw CSVShowing raw CSV because the source is not a valid rectangular table.
STUDYID,USUBJID,SITEID,SEX,SEX
YAMAA-01,YAMAA-01-101,101,F,F
YAMAA-01,YAMAA-01-102,101,M,F
Unexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
Human review and assessment
| Dataset Name | Variable Name | Variable Label | Type | Codelist/Controlled Terms | Core | 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 | SITEID | Study Site Identifier | character | Copy value from DM.SITEID. | Predecessor | ||
| ADSL | SEX | Sex | character | Copy value from DM.SEX. | Predecessor |
| Version | Date | Author | Description | Reviewer | Sign-off |
|---|---|---|---|---|---|
| 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 |