Conferences

CORE allows to host multiple conferences at the same time. You can manage them in the 'conferences' tab. Every conference can has its own specific settings and layout. CORE uses the hostname to differentiate between conferences.

• Google Calendar settings
  If you want to synchronize the CORE schedule with your google calendar, you have to set the fields: 'Google calendar event feed url', 'Google calendar username' and 'Google calendar password'. Make sure the google calendar is publicly available. Any changes made to the CORE schedule will also update the google calendar.

• Set timeslots for the various components (submit/review/schedule/streaming etc) - when the current time is outside of these timeslots the components should be disabled.
• Set languages
• Set layout

Send file over HTTP

See tracker

Sessions

During the Programme Committee meeting these 'preliminary' sessions are decided. They used to be called 'Topics' but that does not make any sense.

• Manage sessions
• Session chairs should be able to manage their own sessions

Login

• Upon successful login, reviewers should see the submissions they should review. Same as I did for TACAR. They can be directed to 'http://omega.terena.org/core/submit/list' and filtered by submission_id.

Submit

Anonymous users (not logged in) can enter their details and upload their papers. During this stage the personal details are saved to be used as speaker details in the future.

• submit paper (new)
• delete submission (admin)
• edit submission to give them status and attach a proposed session (http://omega.terena.org/core/review/list/24)
• list overview of submissions with submission stats + review stats
• filter submissions based on status
• filter submissions based on submission_id's - when a reviewer logs in they get directed to the submission grid which shows only the submissions they should review.
• order list
• Assign submissions to reviewers (many to many) - this should use autocomplete for the users since this will be query a big table

If you submit a paper it looks at the dynamic vhost part and uses that as the conference abbreviation. The abbreviation needs to be checked with existing abbreviations to prevent db weirdness. This should probably be done in the bootstrap process or in a dispatch plugin.
Another solution would be to use static vhosts, the upside of this is that I don't need an extra DB query, the downside is that if you add a abbreviation to CORE you also need to create the vhost.

Review

• List reviewers
• manage reviewers
• Email 'reminders' to reviewers; add a link to the submission grid to email all reviewers with the submissions they should review.
• Set reminder dates
• Generate proposed status of paper based on review scores
• Filtering of List based on status
• Sorting of columns, especially 'proposed session'
• Mass email all rejected paper submitters

Schedule

• List papers with filter for status set to 'yes'
• Manage days/timeslots/locations of event
• Assign papers to sessions
• Assign sessions to chairs
• Assign sessions to timeslots
• Order presentations
• Mass email accepted papers. Email template pulls data from timeslots/locations/papers and session data.

Speaker (so also Session chairs)

• Go to our login
• Edit personal details (photo as well)
• Upload presentation
• Chairs can edit their own session
  • Name
  • Abstract
  • Evaluation

Live

• Streams
• Feedback

After

• Mass email to different groups