Recommended dates for printed conference handbook

From Admin Wiki
Revision as of 01:54, 13 February 2017 by ShiqiZhao (talk | contribs) (Created page with "What follows is the schedule recommended by Priscilla Rasmussen for printed conference handbook. ACL2017 (Vancouver , July 30 -- August 4, 2017) is taken as an example: =====...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

What follows is the schedule recommended by Priscilla Rasmussen for printed conference handbook. ACL2017 (Vancouver , July 30 -- August 4, 2017) is taken as an example:

==

Here's a suggestion, keeping in mind we are talking about the *printed conference handbook* which contains the entire main conference program and program-at-a-glance and bio sketches/descriptions of each invited speaker/talk, descriptions of each tutorial, descriptions and schedules for each workshop, local things of interest and things you should know, sponsors' ads and logos, etc. The deadlines I suggest below would be the drop-dead *final* deadlines.

Working backward:

  • Need handbooks delivered at venue 3-4 days minimum prior to July 30th (1st conference day) so they can be stuffed into conference bags = due date in Vancouver July 25-26.
  • Deadline to printer = July 3rd to be safe (includes possibly customs problems time and allows 2 weeks for Omni Press to do its thing and a week for shipping)
  • 2-3 weeks for getting/chasing/pestering workshop chairs for schedule and program = deadline of June 12th at latest to be comfortable.
  • Main conference program (including poster sessions) and program-at-a-glance = deadline of May 22nd which would coincide with being put online during the early registration period as people have requested and give the handbook chair(s) time for this most lengthy/difficult part of the booklet assembly.
  • Similar deadline as the main program for getting ads from sponsors, especially since these need to be placed where they will fit best given all the other materials
  • Tutorial and local descriptions and input should be available ahead of these times so could be fleshed out and put in as beginning steps almost at any time, I'd think.