Skip to main content
Question

Best practice for utilizing/stacking multiple validations for RDM


Forum|alt.badge.img

Hi All - new to Ataccama’s products and I’ve got a question re: RDM and validations. 

What is the best practice for creating multiple validations for a field (column) level validation, with the aim being reusability and scalability? For example, I might have the following use cases:

  1. string must be all upper case
  2. string must not contain all spaces
  3. string must be camel case
  4. string must be alpha characters only
  5. string must be alphanumeric only
  6. string can contain digits but not special characters
  7. …...etc - the list could be lengthy!…….

And I want to apply the rules in various combinations like this:

  • Column A: 1,2,4
  • Column B: 1,2,6
  • Column C: 1,2,3,5

….etc.

Current thinking: 

  • It seems like domains would be a good place to start, but that given the different permutations it would mean creating a multitude of domains, and the regex could be cumbersome. 
  • Expression validations don’t promote reuse
  • Online services: this might be more in line with modularizing validations - setting up a “library” of validation rules that could be created (as components, maybe?) → haven’t worked with this yet, but will be digging into it shortly. 

If anyone has pros/cons to share regarding how you’ve done something similar, I’d love to hear it!

Thanks,

Cindy

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings