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: derive the site name (SITE) for analysis use with only its
first letter capitalized.
Input: collected demographics carrying the site name (SITENM),
recorded in capitals.
Variables:
SITEwould be the site name with its first letter capitalized and every later letter in lower case.
The requested case, capitalize, is none of the five cases a site name
can be put in: upper, lower, sentence, title, and proper. The request is
rejected before any data is read, and no artifact is accepted.
How to fix
Decide which case the analysis value takes, then name it. A capital first letter followed by lower case is sentence case:
str_case:
source: DM.SITENM
to: sentence
A value such as BOSTON GENERAL then becomes Boston general. Writing
to: title instead capitalizes each word, giving Boston General.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- value_not_permitted
- rule
- SCHEMA-12
expected/error.yaml
phase: validation
condition: value_not_permitted
spec_paths:
- columns.SITE.derivation.str_case.to
rule: SCHEMA-12
context:
value: capitalize
permitted: [upper, lower, sentence, title, proper]
Inputs
Under review1 source fileinput/dm.csv
Edit2 rows| STUDYID | USUBJID | SITENM |
|---|---|---|
| PILOT7 | BOSTON GENERAL | |
| PILOT7 | LAKESIDE CLINIC |
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 | SITE | Site Name | character | Convert DM.SITENM to capitalize case. | Derived |
| 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 |