Rule blocked: CORERULES-9422

[aniemes]

• Attach test dataset files that can be used to test the new feature
• Replace the "###" in the issue title with the primary JIRA ticket number for the rule.
• Fill in the following information

Links to related JIRA Tickets

• https://jira.cdisc.org/projects/CORERULES/issues/CORERULES-9422
• https://jira.cdisc.org/projects/CORERULES/issues/CORERULES-9220

unit-test-coreid-FB1801-negative_01.xlsx

Rule Information

• Standard: FDA
• Rule ID: FB1801/FB1901
• Rule Description: The length of the variable is longer than the data within the variable

Describe the problem
We need a way to find the largest element of a single variable
We need a way to iterate through the variables in each dataset

Describe the solution
If the engine could search through all elements for a given variable, we could use this to compare this against the variable_size operator. If the engine could iterate through the list of variables we could use the previous check for all of the variables and compare them in this way.

Proposed rule logic

Check:
  all:
    - name: variable_size
      operator: less_than_or_equal_to
      value: $size
....
Operations:
  - id: $size
    operator: largest_variable_value

[gerrycampion]

@aniemes should it be greater_than instead of less_than_or_equal_to?

[gerrycampion]

I think a possible solution would be to add the metavariable variable_max_size to the Variable Metadata Check Rule Type. However, we would want this to lazy load this metavariable since it requires a record iteration.

[eljanssens]

@OGarcia11 : this ticket should go to the backlog as this is in scope for v1.0
@SFJohnson24 or @gerrycampion: this rule requires to check variable sizes across domains if they are matching (visitnum, visit). Is it actually possible to do this with the current engine set-up?

"The length of each variable cannot be different between datasets and should not be longer than the maximum length of the data contained by the variable"__

[SFJohnson24]

@eljanssens this is possible--it will just require some work to create the new piece of metadata. As @gerrycampion said-- we could iterate through records from all datasets and create a variable_max_size for Variable Metadata Check. It would be good to only do this in rules that require the variable as well as caching the variable name and the result so as to not do the same iteration twice