Usage of Quality Stage if data is already classified

divstands · Post by **divstands** » Fri Jun 05, 2009 4:56 pm

1. If we are not using Quality Stage for matching,
2. and the Address Data of the Customer is already well organized into different fields like Street, External Number, Interior Number, Colony, City, State , etc( where the data for one field say street will not be mis-placed in another field, say, external number/Colony)
3. and the client requirement is to see all the data together as one single address line

Do we really need intervention of Quality Stage in between DataStage and Customer Data Integration Hub?
If yes, what are the features of QualityStage which can be utilized yet?

ray.wurlod · Post by **ray.wurlod** » Sat Jun 06, 2009 5:20 pm

Consolidating all available information about the one customer into a single "best of breed" customer record is what QualityStage is about, but of course that implies that you do some form of matching between potentially duplicate customer records.

divstands · Post by **divstands** » Mon Jun 08, 2009 11:04 am

But we are not utilizing matching for the current assignment... and this is where my question comes

ray.wurlod wrote:Consolidating all available information about the one customer into a single "best of breed" customer record is what QualityStage is about, but of course that implies that you do some form of matching ...

chulett · Post by **chulett** » Mon Jun 08, 2009 11:09 am

If all you are talking about is assembling a 'full' address line from the various (clean/validated) parts then no, you certainly don't need QualityStage just for that.

ray.wurlod · Post by **ray.wurlod** » Mon Jun 08, 2009 4:05 pm

But if you are assembling name and address data from multiple records the only matching you can do without QualityStage is exact matching. This may miss some probable duplicates.

divstands · Post by **divstands** » Mon Jun 08, 2009 5:00 pm

yeah Ray

I agree with you. But certain unavoidable managerial stuff dont allow me to use matching!

ray.wurlod wrote:But if you are assembling name and address data from multiple records the only matching you can do without QualityStage is exact matching. This may miss some probable duplicates. ...

ray.wurlod · Post by **ray.wurlod** » Mon Jun 08, 2009 7:07 pm

Resist stupid requirements!

stuartjvnorton · Post by **stuartjvnorton** » Mon Jun 08, 2009 7:39 pm

divstands wrote:yeah Ray

I agree with you. But certain unavoidable managerial stuff dont allow me to use matching!

ray.wurlod wrote:But if you are assembling name and address data from multiple records the only matching you can do without QualityStage is exact matching. This may miss some probable duplicates. ...

Do a bit of QS matching and show them how it would do a better job.