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
README.mdPublic entries: Python and R. Passing coverage requires an installed inventory.
Goal: keep each collected comment in COVAL, and stop the run for a
comment longer than the 200 characters one value holds.
Input: collected free-text comments, one record per comment, with the
subject and the comment number (COSEQ).
Variables:
COVALis the comment as collected. Its length is counted from the comment number instead of the comment text, and a number has no characters to count.
The request is rejected before any data is read, and no artifact is accepted.
How to fix
Count the characters of the comment text, not of its number:
str_length: {source: CO_RAW.COMMENT}
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- incompatible_input_type
- rule
- TEXT-1
expected/error.yaml
phase: validation
condition: incompatible_input_type
spec_paths:
- columns.COLEN.derivation.str_length.source
rule: TEXT-1
context:
source: CO_RAW.COSEQ
expected: str
actual: int
Inputs
Under review1 source fileinput/co_raw.csv
Edit2 rows| STUDYID | USUBJID | COSEQ | COMMENT |
|---|---|---|---|
| YAMAA-01 | 1 | Subject missed the week 4 visit because of a family emergency; the visit was completed 3 days later, outside the window. | |
| YAMAA-01 | 1 | Subject withdrew consent after the week 8 visit. |
Unexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
Human review and assessment
| Variable Name | Variable Label | Type | Length | Controlled Terms or Format | Origin | Core | Conversion Definition | Variable Type | Variable Order | Comments for Define |
|---|---|---|---|---|---|---|---|---|---|---|
| DOMAIN | Domain Abbreviation | Char | Assigned | Set constant value "CO". | SDTM | 1 | ||||
| STUDYID | Study Identifier | Char | Collected | Copy value from CO_RAW.STUDYID. | SDTM | 2 | ||||
| USUBJID | Unique Subject Identifier | Char | Collected | Copy value from CO_RAW.USUBJID. | SDTM | 3 | ||||
| COSEQ | Sequence Number | Num | Collected | Copy value from CO_RAW.COSEQ. | SDTM | 4 | ||||
| COVAL | Comment | Char | Collected | Copy value from CO_RAW.COMMENT. | SDTM | 5 |
| 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 |
yamaa