The Registration system written in 2004 is very unwieldy
and doesn't work on the ITEE server. Get this code to
work and produce a neat interface for registration form
design.
Add 'title' to fields for user, e.g. Mr, Dr, Prof, A/Prof. Title needs to be added to many areas like reports and session chair names. It would be stored in com_Registration. Currently it is very hard to dig down into where the data is edited in common functions area and it is not easy to just add an extra field like I could do in phpmyadmin as there may be many programs that rely on com_Registration that would be broken if I did. There needs to be an abstraction layer so any new fields added will not break the registration and reporting areas.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The registration referred to here is for payment of registration fee. On the issue of adding a title field, this is not so hard and would cause minimal breakage of components. The biggest risk comes from sql update commands. These can be rewritten to be insensitive to added fields fairly easily, if required. Academics tend to ignore personal titles in publications and elsewhere, so this was not considered in the original design, but can be added.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=606772
Originator: NO
Add 'title' to fields for user, e.g. Mr, Dr, Prof, A/Prof. Title needs to be added to many areas like reports and session chair names. It would be stored in com_Registration. Currently it is very hard to dig down into where the data is edited in common functions area and it is not easy to just add an extra field like I could do in phpmyadmin as there may be many programs that rely on com_Registration that would be broken if I did. There needs to be an abstraction layer so any new fields added will not break the registration and reporting areas.
Logged In: YES
user_id=774853
Originator: YES
The registration referred to here is for payment of registration fee. On the issue of adding a title field, this is not so hard and would cause minimal breakage of components. The biggest risk comes from sql update commands. These can be rewritten to be insensitive to added fields fairly easily, if required. Academics tend to ignore personal titles in publications and elsewhere, so this was not considered in the original design, but can be added.