 |
The application for attending a
conference can be independent from research, but the research committee
sometimes administers certain funds. All conference applications
and allocations are handled via the conference application
system. The conference may be linked to a research project
and it may be an outcome of research.
| Field | Type & Length |
Description |
|---|---|---|
| Conference Code | N4 | A unique code with which to identify the conference. |
| Name | A30 | A description of the conference. |
| Start / End Date | DD-MON-YYYY | The Start / End Date of the conference. |
| Local or Overseas | A1 | Is the conference being held Locally or Overseas? A <LIST> command is available. |
| Location (City) | A30 | The place where the conference will be held. |
| Organising Body | A30 | The Body that is organising the conference. |
| Feedback Expected Date | DD-MON-YYYY | The date on which it is expected that conference
attendees will provide feedback on the contents of the conference. If no “feedback expected date” is entered, it is interpreted that no feedback is expected. When a date is entered, an activity record will be created in the “Activities / Comments / Restrictions” option {SRAS-3}. This date can not be entered once the attendance of any person has been approved. A manual activity will then have to be created. |
|
| Processing Rules |
|
|---|---|
| No special processing rules. |
| Date | System Version | By Whom | Job | Description |
|---|---|---|---|---|
| 11-Dec-2006 | v01.0.0.0 | Amanda Nell | t134606 | New manual format. |
| 27-Jul-2007 | v01.0.0.0 | Magda van der Westhuizen | t134606 | Update manual. |
| 12-Aug-2008 | v01.0.0.0 | Magda van der Westhuizen | t152204 | Update manual - Language Editing. |