DSXchange

In my new role, I am advising on best practices and discovered that the organization has a policy of developing only rule sets. Even a single rule is put in a rule set and they run the rule set. So they have many rule sets that only have one rule in each. I think this is an odd practice but I have yet to inquire what the thinking is behind it.

I am about to advise against it but I thought I'd pick your brain on the matter.

Agreed that it's an odd practice. But I can't think of any real reason not to, other than interpolating an unnecessary layer of software.

I would guess that their reasoning is consistency of output format, whether they have one, two, or many rules in Rule Sets.

Argh...sorry I am not currently a paying member. But thanks, Ray.

We will be reviewing the rationale behind the practice and set an appropriate direction henceforth. I'll update this thread once we reach a decision.

You didn't miss much, so I've opened it.

Apparently, an ETL process moves DQ results from IADB to a dashboard. The ETL is a black box, barely documented, and we are told that it only looks at and expects rule sets. All developers just have to abide by the requirement to put all rules into rule sets.