Design problems

i have to maintain a list of phone numbers. i also need to maintain the owners' details. but here's a problem: i already have access to the phone number data, but i'll fill up the owners' data as i go along. so here's the problem: how do i do this? quite a number of people have more than one phone number, so the phone number(s) cannot be the primary key. at the end of the day, each person whose data is recorded will have one or more phone numbers, but i currently have phone numbers but no associated personal data. how do i design my database so that i can fill in personal details when they come in, but i won't repeat any information and have a sufficiently extensible database design that can adapt to changing requirements?

Blogged with Flock