Reject a Dataset-JSON File That Does Not Count Its Records

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

EditUnder reviewWhat 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.json, a Clinical Data Interchange Standards Consortium (CDISC) Dataset-JSON 1.1 file that leaves out the record count the standard requires every file to state.

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.

The count is how a reader knows that every record the sender wrote has arrived. Without it the file is not a Dataset-JSON 1.1 file, so it is rejected while it is read, before any record is used, and no artifact is accepted.

How to fix

Ask the sender for a file written to the Dataset-JSON 1.1 standard, which states the number of records beside the dataset's name and label:

"records": 2,
"name": "DM",
"label": "Demographics",

Do not add the count by hand unless you have confirmed, with the sender, how many records the dataset holds.

Expected failure

Editthe 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.json
  cause: member
  member: records

YAML specification

1 spec file

spec.yaml

Edit34 lines

1yamaa: "1.0"2type: spec3model: ADaM4domain: ADSL5keys: [STUDYID, USUBJID]6input:7  # Demographics received as a Dataset-JSON file that does not count its8  # records.9  DM: input/dm.json1011output:12  path: adsl.csv13  columns: [STUDYID, USUBJID, SITEID, AGE]1415columns:16  - name: STUDYID17    type: str18    label: Study Identifier19    derivation: DM.STUDYID2021  - name: USUBJID22    type: str23    label: Unique Subject Identifier24    derivation: DM.USUBJID2526  - name: SITEID27    type: str28    label: Study Site Identifier29    derivation: DM.SITEID3031  - name: AGE32    type: int33    label: Age34    derivation: DM.AGE

Inputs

Under review1 source file

input/dm.json

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",
  "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}
  ],
  "rows": [
    ["PILOT7", "P7-741", "101", 24],
    ["PILOT7", "P7-742", "102", 67]
  ]
}

Unexpected Output

Under reviewNo artifact is produced

No fixture files in this directory.

Shaded columns are derived— = missing value

Human review and assessment

Dataset Name	Variable Name	Variable Label	Type	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	SITEID	Study Site Identifier	character	Copy value from DM.SITEID.	Predecessor
ADSL	AGE	Age	numeric	Copy value from DM.AGE.	Predecessor

Version	Date	Author	Description
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

How to fix

input/dm.json

Your review

Mapping spec