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 investigator comment (CMNT) for each subject,
one record per subject.
Input: collected subject listing holding the investigator
comment (COMMENT).
Variables:
CMNTwould be the comment the investigator recorded about the subject, copied fromCOMMENT.
One comment closes its quoting and then carries on with more text before the next separator. Whether that text belongs to the comment, starts a new value or is dropped depends on the program that reads the file, so the comment has no single reading. The run is rejected while the listing is read, and no artifact is accepted.
How to fix
Have the program that writes the listing quote the whole comment, so the closing quotation mark comes right before the separator or the end of the record:
STUDYID,USUBJID,COMMENT
CTX,CTX-01,Dose reduced
CTX,CTX-02,"Visit missed by site"
CTX,CTX-03,
If the quotation marks belong to the comment itself, double each one inside
the quoting, as in """Visit missed"" by site".
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- ingest
- condition
- source_text_after_quote
- rule
- CSV-16
expected/error.yaml
phase: ingest
condition: source_text_after_quote
spec_paths:
- input.DM.path
rule: CSV-16
context:
dataset: DM
path: input/dm.csv
record: 3
field: 3
Inputs
Under review1 source fileinput/dm.csv
Editraw CSVShowing raw CSV because the source is not a valid rectangular table.
STUDYID,USUBJID,COMMENT
CTX,CTX-01,Dose reduced
CTX,CTX-02,"Visit missed" by site
CTX,CTX-03,
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 | CMNT | Investigator Comment | character | Copy value from DM.COMMENT. | 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 |