For clustered OUs, datimvalidation::validateData output may be confusing

[jacksonsj]

When datimvalidation::validateData is fed a PSNU import file for a Clustered OU, it outputs a log showing validation rule violations at the PSNU level, made possible because of operations in distributeCluster which moves data from cluster to PSNU level in producing the PSNU import file.

This makes it difficult for reviewers (e.g., SI Advisors) to identify where in their Disagg Tools (at the Cluster level) to correct when looking at violations expressed at PSNU level in validateData's output.

For clustered OUs, could we perform validateData validations as part of datapackimporter::ImportSheets, prior to data being distributed from cluster to psnu, and also to incorporate these validation checks earlier?

This change would require validateData to be in sync with cluster mappings.

[jason-p-pickering]

I don't think this will work really, because validateData is all about what we are actually going to import. We might have a situation where there are NO validation rule violations with the clustered data, but after its distributed to the PNSU level, there are validation rule violations.

I think we could potentially add an additional column by manipulating what comes out of validateData, to make it clear that this PNSU is part of a cluster.