Review ask

As a clinical trial statistician or programmer, answer two short questions in Your review: the task and the inputs and outputs. 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

Lifecycle: draftEditUnder review
What this benchmark means
README.md

Public entries: Python and R. Passing coverage requires an installed inventory.

Goal: derive AVISIT (sentence case) and AVISIT_TITLE (title case) from the collected visit name, replacing a hand-written visit-label mapping.

Input: lab records carrying VISIT (the collected visit name, e.g. WEEK 8), copied to the output unchanged.

Variables:

  • AVISIT is VISIT in sentence case: the first character becomes uppercase and every later letter lowercase, so END OF TREATMENT gives End of treatment.
  • AVISIT_TITLE is VISIT in title case: each unbroken run of letters starts uppercase and continues lowercase, and any other character, such as a space or hyphen, ends a word: END OF TREATMENT gives End Of Treatment and FOLLOW-UP gives Follow-Up.

Note: only the plain English letters A to Z change case; every other character is unchanged. The two forms agree whenever the visit name holds one run of letters (WEEK 8 gives Week 8 both ways). Rows are ordered by the collected visit name, then by subject.

Inputs

Under review
1 source file

input/lb.csv

Edit
5 rows
input/lb.csv
STUDYIDUSUBJIDVISIT
YAMAA-01WEEK 2
YAMAA-01WEEK 8
YAMAA-01SCREENING
YAMAA-01END OF TREATMENT
YAMAA-01FOLLOW-UP

Expected output

Under review
5 expected rows

expected/adlb.csv

Edit
5 rows
expected/adlb.csv
STUDYIDUSUBJIDVISITAVISITAVISIT_TITLE
YAMAA-01END OF TREATMENTEnd of treatmentEnd Of Treatment
YAMAA-01FOLLOW-UPFollow-upFollow-Up
YAMAA-01SCREENINGScreeningScreening
YAMAA-01WEEK 2Week 2Week 2
YAMAA-01WEEK 8Week 8Week 8
Shaded columns are derived— = missing value

Human review and assessment

Your review

2 questions and your comments · View benchmark discussions

Mapping spec

Generated from the benchmark YAML; do not edit by hand

Dataset NameVariable NameVariable LabelTypeCodelist/Controlled TermsCoreComputational MethodOrigin
ADLBSTUDYIDStudy IdentifiercharacterCopy value from LB.STUDYID.Predecessor
ADLBUSUBJIDUnique Subject IdentifiercharacterCopy value from LB.USUBJID.Predecessor
ADLBVISITVisit NamecharacterCopy value from LB.VISIT.Predecessor
ADLBAVISITAnalysis VisitcharacterConvert LB.VISIT to sentence case.Derived
ADLBAVISIT_TITLEAnalysis Visit Title CasecharacterConvert LB.VISIT to title case.Derived
VersionDateAuthorDescriptionReviewerSign-off
1.72026-10-20yamaa docs buildRead 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.62026-10-17yamaa docs buildDescribe collected date parts written as ISO 8601 date text and times of day counted in seconds since midnight
1.52026-10-17yamaa docs buildName 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.42026-10-15yamaa docs buildState datetime precision codes through the hour and minute, and complete only the time parts a collected datetime lacks
1.32026-09-29yamaa docs buildShow study codelist names, external dictionaries, and ISO 8601 formats in variable rows; list the document's codelist values and metadata
1.22026-09-29yamaa docs buildClassify ADaM copies from a declared input as Predecessor and recodes as Derived, and SDTM recodes of locally derived columns as Derived
1.12026-09-29yamaa docs buildResolve lookups into the donor record they select, and give every derivation shape a plain-language rule instead of its raw YAML
1.0yamaa docs buildInitial generation from spec.yaml

yamaa code

Public calls generated from benchmark.yaml; results must match the expected output

R

Edit
3 lines
library(yamaa)yamaa_spec("spec.yaml")$run()$output

Python

Edit
3 lines
import yamaayamaa.spec("spec.yaml").run().output