Tom Hoffman wrote: > I went over several standards documents for student demographic and > contact info and took a crack at assembling a reasonable common set of > attributes for the sake of starting further discussion. > > Name > ---- > > First name* > Last name* > Prefix > Middle name > Suffix > Preferred > Sort name? > > Demographics > ------------ > > ID # > Gender* > Birthday* > Ethnicity* > Native language > Place of birth > Citizenship > Photo > > Contact (per contact) > --------------------- > > We probably need to be able to attach arbitrary numbers of contact > persons to students. This data would be stored about the student > himself and/or each parent, etc. contact. > > Priority (in list of contacts) > Name (as above) > Address line 1 > Address line 2 > City > State > Country > Postal code > Email > Home phone > Work phone > Mobile phone > Language > > School > ------ > > Advisor > Counselor
These all look good to me, a small query/something to think about. Can siblings be linked ? So that duplicate contacts are not required. So a student can have multiple contacts and a contact can have multiple students. Also it might be usefull to think about addresses, an example use case would be if a student move address, then it is very likely that the parental contact(s) will move address as well. So maybe the contact could optionally inherit some properties from the student. Regards Martin Stevens _______________________________________________ Schooltool mailing list [email protected] http://lists.schooltool.org/mailman/listinfo/schooltool
