332
edits
Changes
no edit summary
* The venue of C4L2014 could hold 350 people
* To ensure registration Presenters, Preconference Organizers, and Sponsors (Platinum, Gold, and Table), initial registration was capped at 325. This filled in approximately 48 hours.
* Demand for Code4Lib 2014 was 420 450 based on registrations and wait list.
* Local registrations by the hosting libraries (Duke, NCSU, UNC) was 41 registrations.
* CONCENTRA's registration system had some technical limitations as to data input and flow, but CONCENTRA handled all processing with little assistance by volunteers.
'''Sponsorships'''
* 46.8% of the estimated cost of C4L2014 was provided by sponsorships. The registration cost of $165 per person covered another 46.8%. The remaining balance of C4L2013 covered the remaining 6-7%.
* To keep registration costs low, it is critical the Sponsorship Committee raise a minimum of $50,000 per year.[This really depends on the overall venue costs. If the conference is hosted on a college campus, the costs tend to be much lower, and therefore the amount of sponsorship needed is much lower - jaf]
* The [http://code4lib.org/node/487|Code4Lib2014 Sponsorship Prospectus] was a '''significant''' tool in raising money this year.
* Using negotiation to buy "off menu" will save money.
* Make sure that you ask about dietary requirements during registration so that you can accommodate vegan / vegetarian / gluten-free, etc.
* Less than 65% of the attendees ate breakfast at the conference. Each day of the conference, the number of attendees at breakfast declined.
* 97% of the attendees ate lunch at the conference. The number of attendees at lunch was consistent for both days.
* Less than 100 cans of soda were taken during the afternoon break of the first day; 50 cans of soda were taken during the afternoon break of the second day.
'''Pre-Conferences'''
'''Ideas'''
* Quiet room? Traditionally we've used the lobby as a de facto quiet room for folks wanting to take a break from the conference, but if there's an actual room that we can dedicate for taking a quiet break from the full blast of the fire hose, that would be great! More information at [http://geekfeminism.wikia.com/wiki/Quiet_room].
* Lanyards for whether it is OK to take photographs
* Add chairs to the front of the room so that lightning talk presenters can sit before they talk
* Make the podium laptop desktop background a plain color with good contrast. After every group of presenters clean off the desktop to keep it quicker and easier for presenters to find their slides.
* Put someone at the front of the room who is responsible for helping presenters with the presenter computer.
* Podium Computer** Most people use Mac laptops, so if there is only one podium computer, it should be a Mac.(TMM disagrees)** Ideally, both a Mac and a Windows computer should be available. (TMM disagrees, see sub-bullet below)
*** Almost all of the presentations this year used standard formats (PPT, PDF, and HTML). The podium computer needs to be under the control of the A/V and Streaming Committees for their functions. Presenters should use a presentation standard.
** Several presenters had trouble with not being able to see what was being presented -- the podium computer(s) should be mirrored by default.
*** No, the podium computer should be setup as required for streaming and A/V setup.(TMM)
* Consider pre-combining lightning talks into a single slide deck to keep the flow going.
** This is difficult when lightning talk presenters want to do a live demo(TMM)
* Consider live closed captioning software for talks and streaming
** Another option is to have a stenographer or a live transcriber. @brainwane has had experience with a stenographer for one of her talks and it looked like that she was very pleased with the results...* Twitter feed of #c4lYY on screens when no presenter is up (was previously TMM edited IRC, but twitter to Twitter because Twitter feed is safer, more professional, and more compliant to code of conduct)** Twitter is no more CoC compliant than other online venues, including IRC. Each feed has its own risks in being viewed on the big screen (IRC in jokes vs Twitter hijacking of hashtags). (yo_bj)
* Consider switches at the tables
** what kind of switches?
* Add a Code4Lib logo to the podium
* Have someone whose job it is to collect questions during a presentation and that can then ask them. Allowing for anonymous questions may lead to more folks asking.