Production of ADADAS

[bms63]

Background

Goal: Produce dataset using existing Pilot 3 code in the datasetjson format

Definition of Done

• Pilot 3 Code brought up to date with latest package versions
• Spec file is up to date
• datasetjson file is produced
• Comparison down back to Pilot 3 dataset
• Document Findings in [TBD]

[cpiraux]

@RConsortium/pilot5 , I have a question regarding the dataset JSON datatype. It is mentioned in the vignette that "this information must be provided directly by the user." As a user, I see two ways to assign the datatype for dataset JSON:

• The first approach is to map the dataframe datatype to the closest corresponding dataset JSON datatype. For example, if TRTPN = 1 and we don't specifically indicate that it is an integer, it will be saved as a double. In dataset JSON, the datatype is then assigned as "double."
• The second approach involves using metadata that follows the Define.xml specification. In this example, TRPN has an integer datatype in the specification, and TRTPN is a double in R; thus, the datatype in dataset JSON would be assigned as "integer." This means that the variables, which have a double datatype in the sending system, will have an integer datatype in the receiving system.

[robertdevine]

@RConsortium/pilot5 - the {xportr} 'Go meta' implementation provides Get/Set options for type coercion irrespective of {package} defaults. Deep dive here.