yamaa 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 meansREADME.mdGoal: 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.
The last comment opens quoting that it never closes, so the file says its text continues past the end of the file. Where that record ends, and therefore how many subjects the listing holds, depends on how far a reader chooses to read, so the run is rejected while reading the listing and no artifact is accepted.
How to fix
Close the quoting right after the text the investigator recorded; if the producer cut the comment short, take the full text from the source rather than guessing it:
STUDYID,USUBJID,COMMENT
CTX,CTX-01,Dose reduced
CTX,CTX-02,"Visit missed"
A quotation mark that belongs to the text is doubled inside the quoting,
as in "Subject said ""felt fine""". A comment holding a separator, a
quotation mark, or a line break stays quoted; one holding none of them
needs no quoting at all.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- ingest
- condition
- source_quote_unterminated
- requirement
- REQ-0851
expected/error.yaml
phase: ingest
condition: source_quote_unterminated
spec_paths:
- input.DM.path
requirement: REQ-0851
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
Unexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
Comments and assessment materials
| 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.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 |
Comments
Signed in with GitHub; saved in repository Discussions