OD0070: Missing Length value

[sherry-chou]

The Length attribute is required when DataType is integer, float, or text.
This is currently missing in both define-360i.json/.xml.
Currently since we have no data...should some default value be kept to express it is empty...1?
But if we want to use some default value for Length, what about significantDigits (and subsequently displayFormat)?

[dostiep]

@sherry-chou Length is available for metadata coming from Biomedical Concepts. For Variables' metadata, we don't have Length attribute but we could put in place default values (i.e text = 200, variables that end with FL = 1, TESTCD = 8, etc...).

[sherry-chou]

@dostiep currently how are we selecting which VLM from those SDTM DSS used? Because e.g., VS.VSTESTCD = 'FRMSIZE' (Frame Size) is in both BC and DSS but is not in the define-360i.json?
I am assuming we're getting the length from SDTM DSS, columns X~Y, but I think currently not all were retrieved.
For example, when for OID = 'IT.VS.VSORRES.TEMP', we have:
"displayFormat": "8.3",
"significantDigits": 3

But when OID = 'IT.VS.VSORRES.DIABP', we don't have these attributes, but in SDTM DSS, these are current set as length = 3.

And actually...would there be no Length at all in the define-360i.json (but it's in the schema)?

I originally was thinking for variables where we have VLM, the variable-level Length should be set as the max length of all VLMs (since they come from SDTM DSS), and for variables where VLMs are not present, we can place default values as you suggested.