Review ask

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

Lifecycle: draftEditUnder review
What this benchmark means
README.md

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

Goal: build the demographics domain with each subject's study site (SITEID), and the metadata a data definition describes it by.

Input: collected demographics, one record per subject.

Variables:

  • DOMAIN is DM on every record.
  • SITEID would be the identifier of the subject's study site.

Note: the site identifier declares a length of 0, a placeholder that was never filled in. A length is the longest value the variable holds, so it is a positive number; no site identifier fits in zero characters, and the run is rejected before any data is read and no artifact is accepted.

How to fix

State the longest site identifier the study assigns:

submission:
  core: Req
  role: Record Qualifier
  length: 3
  origins:
    - type: Assigned
      source: Sponsor

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
validation
condition
submission_length_invalid
rule
SUB-7
expected/error.yaml
phase: validation
condition: submission_length_invalid
spec_paths:
  - columns.SITEID.submission.length
rule: SUB-7
context:
  column: SITEID
  length: 0

Inputs

Under review
1 source file

input/dm_raw.csv

Edit
2 rows
input/dm_raw.csv
STUDYIDUSUBJIDSITEID
YAMAA-01101
YAMAA-01102

Unexpected Output

Under review
No artifact is produced

No fixture files in this directory.

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

Variable NameVariable LabelTypeLengthControlled Terms or FormatOriginCoreConversion DefinitionVariable TypeVariable OrderComments for Define
DOMAINDomain AbbreviationChar2AssignedReqSet constant value "DM".SDTM1
STUDYIDStudy IdentifierChar8ProtocolReqCopy value from RAW.STUDYID.SDTM2
USUBJIDUnique Subject IdentifierChar12AssignedReqCopy value from RAW.USUBJID.SDTM3
SITEIDStudy Site IdentifierChar0AssignedReqCopy value from RAW.SITEID.SDTM4
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