I am preparing some papers for the IOD conferences (in Rome in May and in Las Vegas in October) on QualityStage Rule Sets.
I'd like to have a single slide with a list of the various kinds of classifiable data for which folks (that's YOU folks!) have built Rule Sets. All contributions are welcome.
So, for example, if you've created a Rule Set for medical supplies, tell me "medical supplies". If you've created a Rule Set for any kind of inventory, be a little more specific, for example "tools inventory". Geographic information (where are all our power poles?) - all good.
If you have done clever things with generating data (Jay?) into the Business Intelligence fields, I'd be please to hear about that too, but can't guarantee that that information will make it into my paper. For example if you're generating health warning information from the ingredients list of foodstuffs, let me know either through this topic or, if you need confidentiality, off line.
Thanks in advance,
Ray
QualityStage Rule Sets
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
QualityStage Rule Sets
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 527
- Joined: Thu Apr 19, 2007 1:25 am
- Location: Melbourne
ABN/ACN/RBN.
RBN was most of the work, cross-checking between format and state, etc.
Food inventory.
Basic parse, stan stuff.
Apart from that, biggest mods would be to AUPHON to do some tighter validation: length vs number ranges, state vs regional stuff (ie: you can have 07 3xxx xxxx, but not 07 9xxx xxxx), passing acceptable length phonewords. Variable splitting of the number into parts, based on length and type of number. No rocket science, but was useful at the time.
Good thread, Ray: it would be good to hear about some of the useful things people have done with rulesets.![Smile :)](./images/smilies/icon_smile.gif)
RBN was most of the work, cross-checking between format and state, etc.
Food inventory.
Basic parse, stan stuff.
Apart from that, biggest mods would be to AUPHON to do some tighter validation: length vs number ranges, state vs regional stuff (ie: you can have 07 3xxx xxxx, but not 07 9xxx xxxx), passing acceptable length phonewords. Variable splitting of the number into parts, based on length and type of number. No rocket science, but was useful at the time.
Good thread, Ray: it would be good to hear about some of the useful things people have done with rulesets.
![Smile :)](./images/smilies/icon_smile.gif)
-
- Premium Member
- Posts: 425
- Joined: Sat Nov 19, 2005 9:26 am
- Location: New York City
- Contact:
Anti Money Laundering ( AML )
For our Anti-Money Laundering (AML) system we developed a rule set to identify all parties and countries involved in a wire transfer, specifically those typed in free format fields
Basically this rule set parse all free format fields, coming from our legacy payment systems, looking for financial institution SWIFT BIC CODES, key terms for financial institutions, and countries names or ISO country codes with high risk
The Rule Set is part of a DataStage process that validates the data extracted/identified by the tool against a lookup table with real financial institution data
For our Anti-Money Laundering (AML) system we developed a rule set to identify all parties and countries involved in a wire transfer, specifically those typed in free format fields
Basically this rule set parse all free format fields, coming from our legacy payment systems, looking for financial institution SWIFT BIC CODES, key terms for financial institutions, and countries names or ISO country codes with high risk
The Rule Set is part of a DataStage process that validates the data extracted/identified by the tool against a lookup table with real financial institution data
Julio Rodriguez
ETL Developer by choice
"Sure we have lots of reasons for being rude - But no excuses
ETL Developer by choice
"Sure we have lots of reasons for being rude - But no excuses
-
- Participant
- Posts: 612
- Joined: Thu May 03, 2007 4:59 am
- Location: Melbourne
Australian Phone Number.
http://it.toolbox.com/blogs/dw-soa/qual ... tion-37351
AU Concession Card number.
For all the checksum (ABN,ACN, QLD SC Concession Card, NMI, MIRN) validations I found parallel routines best.
http://it.toolbox.com/blogs/dw-soa/qual ... tion-37351
AU Concession Card number.
For all the checksum (ABN,ACN, QLD SC Concession Card, NMI, MIRN) validations I found parallel routines best.
Joshy George
<a href="http://www.linkedin.com/in/joshygeorge1" ><img src="http://www.linkedin.com/img/webpromo/bt ... _80x15.gif" width="80" height="15" border="0"></a>
<a href="http://www.linkedin.com/in/joshygeorge1" ><img src="http://www.linkedin.com/img/webpromo/bt ... _80x15.gif" width="80" height="15" border="0"></a>