Page 1 of 1
Data Integrity Question
Posted: Sun Oct 07, 2012 9:50 pm
by Pavilion
Hello Everyone:
I'm working on an application for one of my clients. Right now I'm setting up registration. Most of the registrations for their site application, will be business organizations. All data entered through the website has to be compared against data in my client's existing database. Now for my question.
- What advice do all of you have for preventing duplication of organizational data
- Users can enter ABC INC, or ABC Incorporated, or ABC, or Abbott, Bailey, Costello, Incorporated so I can't compare by Organization Name
- Some smaller organizations may not have websites, so I can't consistently depend on organization URLs for comparing against existing data
I've been building classical databases for over 20 years, and I've dealt with this issue before. I know there is no easy answer. But, I thought I'd check in with all of you before proceeding forward. It makes sense to get advice from those of you who have experience in online development.
All advice is appreciated - Thanks Much - Pavilion
Re: Data Integrity Question
Posted: Sun Oct 07, 2012 11:40 pm
by requinix
There must a name for these businesses in the existing database. Can you require that new signups use the same name as in the existing system (then allow the businesses to change the "display" name)? Or sign existing businesses up automatically and tell them the (temporary) credentials?
Re: Data Integrity Question
Posted: Mon Oct 08, 2012 8:44 am
by Pavilion
There must a name for these businesses in the existing database. Can you require that new signups use the same name as in the existing system (then allow the businesses to change the "display" name)?
This is what I would like to do. But... in concrete terms, how does one do this without allowing those who are registering to search (and see) companies already signed up? I think that is my biggest concern. Folks signing up for my client's application will be competitors - and my client is very protective of the data.
Or sign existing businesses up automatically and tell them the (temporary) credentials?
This option isn't really an option at all. The application is a way for my client to get new customers, and they are hoping the service will bring in new businesses (as well as their existing clients). Some businesses in their current database (close to 70%) are not current clients, they are prospects. So, although my client will market this service - they won't sign businesses up in advance and send them temporary credentials.
One of the things moving about in my head is using my client's existing email list to assign core URL's to the business. The problem I have with that is many of the businesses and organizations are small and their email accounts are simply with email providers, rather than through their own sites. So... it's not a perfect solution by any stretch. But... it is a major step towards building clean data. But... if I'm going to go this route, I need a good list of email service providers and their email extensions....
If you know of a way to allow users to search for their business, without viewing the names of other businesses in the database, I'm all ears, as that solution is probably my best bet for clean data.
Thanks Much - Pavilion
Re: Data Integrity Question
Posted: Mon Oct 08, 2012 6:36 pm
by requinix
Pavilion wrote:There must a name for these businesses in the existing database. Can you require that new signups use the same name as in the existing system (then allow the businesses to change the "display" name)?
This is what I would like to do. But... in concrete terms, how does one do this without allowing those who are registering to search (and see) companies already signed up? I think that is my biggest concern. Folks signing up for my client's application will be competitors - and my client is very protective of the data.
That's going to be a problem by itself: once the new system is up, if a brand-new company signs up then any subsequent companies could see them too.
There's another approach: allow anybody to sign up under any name they want (existing or not), but give them a secret username (or user ID or something) to authenticate with.
While you're doing this you should consider whether you'll need to verify these companies are who they say they are, but it sounds like your client can do that.