Ataccama Naming Best Practice

Question

Hi everyone,

Just wondering if Ataccama provides any best practice guides on naming conventions when working with the platform. This includes best practice for rule names, error names, sql catalogue item names etc.

Kind Regards,

Vishy

Samuel Muvdi · Accepted Answer

Hi!When it comes to ONE desktop, we have a pretty standard best practice list for column prefixes:src_ : The source value of that field, it does not get alteredpur_ : This is a column that had transformations done to itstd_ : This is a column that has been standardized, usually with a dictionary or standardization transformationcio_ : The best possible value that can be achieved after processing is done, usually the std_mat_ : This is used for matching purposes only, for MDM for exampledic_ : A value that was returned or verified by using a dictionaryWhen it comes to scoring, we want to score between 0 (no changes or transformations done) to 10,000,000 (null value)for naming these scoring reasons, we can put things like “ID_IS_NULL” and set the score to 10,000,000 , or we can do “ADDRESS_INCORRECT” and set the score to 1,000,000.Usually when scoring, we will set a null value to be the score of 10,000,000 , while ones that have smaller rules broken to be under 10,000,000Some more tips:Try to be as descriptive as possible, but keep the names within a reasonable length“customers_NA” vs “customers_north_america” the customers_NA does the job and is more compact“FIRST_NAME_IS_NULL” vs “FN_NULL” we can use the first letter of words to get the same point accross and keep it more compactThere are times though where we can also just shorten the word a bit like “FST_NM_NULL” it's nice and compact but does the job! it helps describe better what it is while also not letting it get too longHope this helps! -Samuel :)

srija piratla · Answer

Hi @vdatla,Here are some best practices while creating any rules The rule must have a descriptive name. Since this is a collaborative platform, we want others tounderstand what the rule does and reuse it, instead of re-creating the same rule from scratch.The rule name should have the format is/has/contains/etc . Examples for rule names include:● Account ID is all zeros● Attribute (string) is duplicate● Attribute (string) is missing● Attribute (date) is missing● Email address is test● Email address format is invalid● ID contains a lowercase character● Market code is invalid● Account Balance is between 0 and 10,000Hope this helps !Regards,Srija Piratla

Sign up

Login to the Ataccama Community

Scanning file for viruses.

This file cannot be downloaded