Re: Schema

> >
> >> create table contact_types (
> >> contact_type_id int4 primary key,
> >> contact_type_name varchar(32) -- e.g. home phone, work email, etc.
> >> )
> >>
> > I don't think this table is necessary and might complicate things, as
> > I'm sure we can establish an exhaustive list of contact types (and have
> > an 'Other' option) for each of the classes/destinations of contacts
> > outside of the database (as this should be fixed as part of the spec
> > anyway) making the above list extensible would potentially make it
> > harder to implement PIM apps/sync tools etc.
>
> It's certainly true that we as the developers of the app could enumerate all
> of the possible contact types that we foresee. I'm always in favor of
> providing advanced functionality, as long as it doesn't complicate the user
> experience. Providing this table allows the user to create their own contact
> types which we as developers may not think of. We could pre-populate this
> table with what we expect they might need (just like your enumeration) and
> then give them a pull-down list to select from the available choices when
> their entering a new person (or editing a person). The option to add contact
> types could be in an "advanced" tab so normally the user doesn't need to worry
> about it. I can foresee some reasonable subset of our users having a desire
> to create their own contact types, thus my arguing for this capability. It
> adds one more query for us as developers (and adds the "advanced" tab to the
> UI -- which can be put off to version 0.02) but shouldn't complicate the user
> experience at all.

i agree that it is perfectly valid feature, but the basic types _have_
to be there, and by making them extensible you open up the need for all
GPE applications to support then, I don't think you are going to be
severely dis-advantaging users by limiting them to a fixed list and one
or more "other" options.

sorry i could be wrong and i don't want to troll on as it is really just
a small thing.

what does everybody else think?

owen

-- 
Owen Cliffe, Ph.D. Student, Dept. Computer Science
University of Bath