yamaa / Benchmark

ADaM.ADLB

Sentence Case and Title Case

input files
1
subjects
5
expected rows
5
Review ask

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.

  1. Task: Would a real study need this derivation, specified this way? Does it follow CDISC ADaM: variable names, controlled terms, record structure? Flag any rule that is ambiguous or that a sponsor would handle differently.
  2. Inputs: Do they look like data collected in a real trial, and do they include the situations you would expect to meet in one?
  3. Expected output: Would independent QC programming reproduce every value from these inputs and rules?

The other tabs beside Comments are background for assessment, not under review.

Summary

Lifecycle: draftEditUnder reviewWhat this benchmark means
README.md

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 review1 source file

input/lb.csv

Edit5 rows
STUDYIDUSUBJIDVISIT
YAMAA-01WEEK 2
YAMAA-01WEEK 8
YAMAA-01SCREENING
YAMAA-01END OF TREATMENT
YAMAA-01FOLLOW-UP

Expected output

Under review5 expected rows

expected/adlb.csv

Edit5 rows
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

Comments and assessment materials

Comments

Signed in with GitHub; saved in repository 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.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

Runs the yamaa specification; its result must match the expected output

run.R

Edit4 lines
library(yamaa)adlb <- yamaa_domain("spec.yaml")$outputadlb

run.py

Edit4 lines
import yamaaadlb = yamaa.yamaa_domain("spec.yaml").outputadlb