Been taking a database design class; looks like I designed the databse for my lawyer referral site ( HTTP://freeduiconsultations.com ) somewhat wrong, it didn't account for the possibility of a lawyer being able to practice in more than one state, and many other things so I'm re-designing from scratch.
Probably making it over-complex now, as the current design allows for relationships between directory entries, such that an attorney can be a member of a law firm; and both can be members of bar associations; along with geographic area relationships (State/County/City), practice types (to expand beyond DUI), and a new way of handling Contact information, to allow multiple addresses and phone numbers of the same type.
it's almost a generic Object-Properties-Relationships implementation at the core, I don't know if thats a good or bad thing... I want it to be flexable, but I don't want to make it so flexable that it effectivly does nothing.
All that attorney data will mesh with a site redesign allowing multiple content templates and CSS Styles, allowing each domain name for the site to present appropriate data, user accounts, and such.