Address Book

Disclaimer

Please do not email me about this project without reading the disclaimer above.

Every few years, my address book gets too untidy with changed names and addresses and I start over, copying the most useful names, making errors in the process. I keep the old books around for reference. I would like to automate this process. I’m not rich enough to buy a Palm Pilot, so I ordered a program from Daytimer to do this.

Supposedly, it will let me maintain the lists electronically and periodically print out subsets of the master address book, so that for example I might just print out a mini address book of my Seattle contacts, or just people I might want to ask for sex, or my Christmas card list, the people I need to contact to organise a high school reunion, just the people I phone frequently…

Your job is to create a portable Java clone of this program.

Things to consider in doing a bang up job to make your code even better than DayTimer’s:

• Validate the heck out of the data. Cross check area code prefixes/state/province/zip/postalcode. Look for invalid x0x and x1x telephone prefixes in area codes that don’t support them. Look at the Business Classes for some ideas. Validate the format of email accounts and do a DNS (Domain Name Service) check on any domain names if you are online. Arrange for auto-update of validation classes.
• Allow printing in many formats, e.g. DayTimer expensive pre-printed sheets, blank paper with black circles showing where to punch, mini, midi and maxi formats, mail labels, plain paper lists. The trick here is to print on front and back of each sheet in such a way that when you cut the paper up into smaller pages, everything comes out in the right place.
• Automatically record the last change date and provide a way to print a list of entries given a start/end change date. That way you can get a list of likely obsolete entries or to review your recent entries. You might use it to print a master address book once every 6 months and, every month, a printed update of just the recent changes since that printing.
• vCard import.
• The simplest implementation is a ram-resident many-to-many TreeMap that you pickle between incarnations. You want to be able to look up each item by many different keys. Each key might link to many different items. George W. Cherry will be publishing a book that shows a simplified Personal Information Manager that demonstrates the technique. A fancier implementation would use an SQL (Standard Query Language) engine, possibly web-based to avoid the hassle of installing one on the client’s machine.
• Allow you to configure which fields you want to track on each person.
• Allow you to add new fields and give them names and types which controls data entry and validation.
• Allow plug-in additional data entry validation filters using Class. forName
• Allow you to define different reports listing which fields you want to keep. The fields tend to automatically align with minimal fiddling.

standard footer

	This page is posted on the web at:	http://mindprod.com/project/addressbook.html
	Optional Replicator mirror of mindprod.com on local hard disk J:	J:\mindprod\project\addressbook.html
	Please read the feedback from other visitors, or send your own feedback about the site. Contact Roedy. Please feel free to link to this page without explicit permission.
	Canadian Mind Products IP:[65.110.21.43] Your face IP:[3.149.29.209]
Feedback	You are visitor number