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: carry the site name (SITENM) onto a subject listing.
Input: collected demographics carrying SITENM, saved by a spreadsheet
program as UTF-8 comma-separated text whose lines end in a carriage return
and a line feed.
Variables:
SITENMwould be the name of the site the subject enrolled at, taken from the collected value.
The file starts with a byte-order mark, the invisible character U+FEFF that some programs write before UTF-8 text, and nothing the study states says that it does. Kept, the mark would sit in front of the first field name; dropped, the reader would have decided on its own what the file holds. So the run is rejected while the file is read, and no artifact is accepted.
How to fix
Confirm that the program that exports the listing always starts its files with a byte-order mark, then state it on the input, so that exactly that one mark is skipped:
input:
DM:
path: input/dm.csv
byte_order_mark: true
Do not drop the mark by saving the listing again in a spreadsheet program's plain comma-separated format: that format writes the computer's own character encoding, so the accented letter in the second site name can change. Removing the mark with a tool that keeps the text UTF-8 is safe, and then the input states nothing.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- ingest
- condition
- source_byte_order_mark
- rule
- CSV-16
expected/error.yaml
phase: ingest
condition: source_byte_order_mark
spec_paths:
- input.DM.path
rule: CSV-16
context:
dataset: DM
path: input/dm.csv
record: 1
field: 1
declared: false
Inputs
Under review1 source fileinput/dm.csv
Edit2 rows| STUDYID | USUBJID | SITENM |
|---|---|---|
| CTX | Hospital Universitario La Paz | |
| CTX | Centre Hospitalier de Liège |
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 | SITENM | Study Site Name | character | Copy value from DM.SITENM. | 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 |