Naming conventions on filters (AuditStage)

This forum is in support of all issues about Data Quality regarding DataStage and other strategies.

Moderators: chulett, rschirm

Post Reply
Eulderma
Participant
Posts: 5
Joined: Wed Jan 17, 2007 4:24 am
Location: Netherlands

Naming conventions on filters (AuditStage)

Post by Eulderma »

Hi,

Has anyone experience with naming conventions and best practices regarding filter names in AuditStage?
If so, can you share this?

Thanks in advance.
jhmckeever
Premium Member
Premium Member
Posts: 301
Joined: Thu Jul 14, 2005 10:27 am
Location: Melbourne, Australia
Contact:

Post by jhmckeever »

Hi Eulderma,

We chose to use a format like 'DATASOURCE.Text Description'.

E.g.

Code: Select all

ACCOUNTS.Mismatch to Meter_Grps
ACCOUNTS.No live mandate for live DD
ACCOUNTS.Billing suspension date not null
AGREEMENTS.AGRMT_CUST_NAME is null
AGREEMENTS.Invalid price for SME
AGREEMENTS.No price line for CORPORATE
etc.
I'm not sure this is reflective of any 'Best Practice' but it worked well for us. In hindsight we may have also built in a Business Rule Reference Number such as ...

E.g.

Code: Select all

ACCOUNTS.B132.Mismatch to Meter_Grps
ACCOUNTS.B029.No live mandate for live DD
ACCOUNTS.X033.Billing suspension date not null
AGREEMENTS.B034.AGRMT_CUST_NAME is null
AGREEMENTS.B199.Invalid price for SME
AGREEMENTS.X043.No price line for CORPORATE
etc.
HTH,
John.
<b>John McKeever</b>
Data Migrators
<b><a href="https://www.mettleci.com">MettleCI</a> - DevOps for DataStage</b>
<a href="http://www.datamigrators.com/"><img src="https://www.datamigrators.com/assets/im ... l.png"></a>
Eulderma
Participant
Posts: 5
Joined: Wed Jan 17, 2007 4:24 am
Location: Netherlands

Post by Eulderma »

We named the filters via uniques numbering and a description that came closest to the business rule.
Example

00.1.1 Validate customer name similarity
Post Reply