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 a subject listing carrying SITEID and AGE from demographics received as a Dataset-JSON file.

Input: the received demographics input/dm.ndjson, a Clinical Data Interchange Standards Consortium (CDISC) Dataset-JSON 1.1 file in its newline-delimited form: the first line describes the columns, and each later line is one record. A record holds fewer values than the file declares.

Variables:

  • SITEID would identify the site where the subject enrolled. The rejected file produces no output value.
  • AGE would give the subject's age in whole years. The rejected file produces no output value.

A record lists its values in column order, so a record with a value too few does not say which column lost its value: reading the rest in order could put a value under the wrong column. The file is rejected while it is read, naming the record, and no artifact is accepted.

How to fix

Ask the sender to write every record with one value per column, writing an absent value as null rather than leaving it out:

["PILOT7", "P7-742", "102", null]

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
ingest
condition
source_dataset_json_invalid
rule
DSJSON-5
expected/error.yaml
phase: ingest
condition: source_dataset_json_invalid
spec_paths:
  - input.DM.path
rule: DSJSON-5
context:
  dataset: DM
  path: input/dm.ndjson
  cause: row_width
  record: 2

Inputs

Under review
1 source file

input/dm.ndjson

Edit
{"datasetJSONCreationDateTime": "2026-09-30T10:15:00", "datasetJSONVersion": "1.1.0", "fileOID": "www.example.org/PILOT7/DM", "sourceSystem": {"name": "Example EDC", "version": "5.1"}, "studyOID": "PILOT7", "metaDataVersionOID": "MDV.1", "itemGroupOID": "IG.DM", "records": 2, "name": "DM", "label": "Demographics", "columns": [{"itemOID": "IT.DM.STUDYID", "name": "STUDYID", "label": "Study Identifier", "dataType": "string", "length": 6, "keySequence": 1}, {"itemOID": "IT.DM.USUBJID", "name": "USUBJID", "label": "Unique Subject Identifier", "dataType": "string", "length": 6, "keySequence": 2}, {"itemOID": "IT.DM.SITEID", "name": "SITEID", "label": "Study Site Identifier", "dataType": "string", "length": 3}, {"itemOID": "IT.DM.AGE", "name": "AGE", "label": "Age", "dataType": "integer", "length": 3}]}
["PILOT7", "P7-741", "101", 24]
["PILOT7", "P7-742", "102"]

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

Dataset NameVariable NameVariable LabelTypeCodelist/Controlled TermsCoreComputational MethodOrigin
ADSLSTUDYIDStudy IdentifiercharacterCopy value from DM.STUDYID.Predecessor
ADSLUSUBJIDUnique Subject IdentifiercharacterCopy value from DM.USUBJID.Predecessor
ADSLSITEIDStudy Site IdentifiercharacterCopy value from DM.SITEID.Predecessor
ADSLAGEAgenumericCopy value from DM.AGE.Predecessor
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