High level requirements

Owned by Paul Seiler (Unlicensed)
Last updated: Jul 06, 2017
1 min read
  1. Promotion via a public website using an appropriate theme (often missed Victoria/other branding).
  2. Self-registration, and maybe subsequent edits. May overlap/also be called 'ticketing' and we will support multiple ticket options per event. Can be replaced with conveners preferred system.
  3. Payments (with the option of credit card and bank transfer) and invoicing. Often closely coupled to registration (above). Usually into a University account.  Can be replaced with conveners preferred system
  4. Call for proposals and the subsequent blind reviews and communications back to proposers. Manual matching between proposals and reviewers.  Can be replaced with conveners preferred system
  5. Speakers manage their own profiles and documents.
  6. Schedule development and publication.  Can be replaced with conveners preferred system
  7. Announcements/updates/communication with registered participants.
  8. Facilitate the production of a conference booklet. Not supported by our offering, except for an export of proposals.
  9. Facilitate the production of a conference proceedings. Not supported by our offering, except for an export of proposals.