<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.code4lib.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Elizabeth</id>
		<title>Code4Lib - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.code4lib.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Elizabeth"/>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/Special:Contributions/Elizabeth"/>
		<updated>2026-04-10T07:04:04Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.26.2</generator>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=How_To_Plan_A_Code4LibCon&amp;diff=11536</id>
		<title>How To Plan A Code4LibCon</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=How_To_Plan_A_Code4LibCon&amp;diff=11536"/>
				<updated>2012-03-08T19:57:23Z</updated>
		
		<summary type="html">&lt;p&gt;Elizabeth: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* Apply to be a host&lt;br /&gt;
&lt;br /&gt;
* Consider your action plan&lt;br /&gt;
** Identify your venues for both the conference and the hotel (if different). This is critical, as you'll want to get some cost estimates from each. When we hosted in Corvallis, the campus provided the conference space at a low cost, and this made running the conference much more affordable. When we hosted the conference in Portland, and held everything in a single hotel, we had to acquire 2x the amount of sponsorship than what appears to be normal.&lt;br /&gt;
** Speaking of sponsorship, I believe we average around 20k per year in sponsorships to help run the conference and keep the registration low. Factor this into your budget.&lt;br /&gt;
** Also, when you get cost estimates, don't forget to include food costs.&lt;br /&gt;
** WIRELESS: Always an issue it seems. If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you are looking at a hotel or other venue, make sure you talk to them about bandwidth and costs. IMHO, the two things that really need to be addressed each year are connectivity and food - everything else generally manages itself in terms of facilities.&lt;br /&gt;
*** make sure VPN is allowed&lt;br /&gt;
** See if your institution has a conference planning services group or something similar - if it does, then I highly recommend using them. They'll handle registration, budgeting, contracts, etc, and really make life easy.&lt;br /&gt;
** Regarding conference hotel, you'll want to make sure that there are blocks of rooms available - not usually too bad an issue in larger towns, but in some college or smaller towns, hotel rooms may be limited.&lt;br /&gt;
*** prepare the hotel for deluge via web when announcement is made about hotel registration available.  We overwhelmed the Seattle hotel in 2012&lt;br /&gt;
** Remember, your institution is taking the risk of covering any costs not covered by registrations and sponsorships. To this point, I believe the conference has always ended up in the black, but there is always a chance it won't in a given year. Drafting a rough budget before submitting a proposal is critical.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Get approved by the community&lt;br /&gt;
* Find a hotel, negotiate and sign a contract with them. [[Sample RFI]]&lt;br /&gt;
* Invite the community to help with &lt;br /&gt;
* Have a timeline&lt;br /&gt;
*[[Useful information from 2012]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Important Public Resources ==&lt;br /&gt;
* Past calls for host sites: [http://code4lib.org/node/275 2010] - &lt;br /&gt;
* [http://dewey.library.nd.edu/mailing-lists/code4lib/ Code4Lib listserv]&lt;br /&gt;
* [http://groups.google.com/group/code4libcon Code4LibCon listserv]&lt;br /&gt;
* Sponsorship info (public)&lt;br /&gt;
* [http://code4lib.org/logo/ Logos]&lt;br /&gt;
&lt;br /&gt;
== Important Private Resources ==&lt;br /&gt;
* Code4LibCon-hostsite listserv&lt;br /&gt;
* Budgets from previous years&lt;br /&gt;
* Sponsorship info (private)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Gender Diversity &amp;amp; Minority Scholarship Committee==&lt;br /&gt;
The scholarship committee is a self-selected group that manages the gender diversity &amp;amp; minority scholarships. Separate groups handle AngelFund and Code4LibJapan scholarships.&lt;br /&gt;
&lt;br /&gt;
===Suggestions received===&lt;br /&gt;
* Send to a wider bunch of listservs, including for national orgs (ALA/SLA/MLA) &amp;amp; relevant sections? &amp;amp; student chapter&lt;br /&gt;
&lt;br /&gt;
===Process===&lt;br /&gt;
# Put out a call&lt;br /&gt;
# Receive and coordinate applications&lt;br /&gt;
# Distribute applications to the committee&lt;br /&gt;
# Select awardees&lt;br /&gt;
# Inform selected candidates&lt;br /&gt;
# Notify unsuccessful candidates&lt;br /&gt;
# Announce to Code4Lib main listserv and post on code4lib.org (e.g. http://code4lib.org/node/274 )&lt;br /&gt;
# Hosts work with awardees on reimbursement, registration, etc.&lt;br /&gt;
# Follow up with awardees after the conference -- receive report, ask for suggestions, etc.&lt;br /&gt;
&lt;br /&gt;
== Program Committtee==&lt;br /&gt;
The program committee is a self-selected group that manages talk proposals and other aspects of the program.&lt;br /&gt;
&lt;br /&gt;
(Add more info for the program committee here!)&lt;br /&gt;
&lt;br /&gt;
===Talk Acceptance Letter (samples)===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Dear &amp;lt;&amp;lt;first name last name&amp;gt;&amp;gt;,&lt;br /&gt;
 &lt;br /&gt;
On behalf of the Code4Lib Program Planning Committee, I am pleased to &lt;br /&gt;
notify you that your proposal, &amp;lt;&amp;lt;proposal title&amp;gt;&amp;gt; has been accepted for &lt;br /&gt;
the Code4Lib &amp;lt;&amp;lt;year&amp;gt;&amp;gt; in &amp;lt;&amp;lt;location&amp;gt;&amp;gt;.  Please reply to this message to &lt;br /&gt;
confirm your intention to present the approved session at the Conference.  &lt;br /&gt;
If at any time in the future you need to bow out or have any program &lt;br /&gt;
changes, please notify us immediately.  You will be sent a letter of &lt;br /&gt;
agreement soon.&lt;br /&gt;
 &lt;br /&gt;
The schedule for the conference is here:&lt;br /&gt;
&lt;br /&gt;
   http://code4lib.org/conference/2011/schedule&lt;br /&gt;
&lt;br /&gt;
You will have 20 minutes for your talk, including questions and answers.&lt;br /&gt;
A quick transition between speakers will be necessary.&lt;br /&gt;
 &lt;br /&gt;
It is very important that you focus your presentation on the more unique &lt;br /&gt;
and technical aspects of your topic whenever possible.  Although Code4Lib&lt;br /&gt;
attendees come from many different work environments, they attend Code4Lib &lt;br /&gt;
events for information technology education.&lt;br /&gt;
 &lt;br /&gt;
Experts like you are the heart of Code4Lib.  We really appreciate your contribution &lt;br /&gt;
and look forward to working with you.&lt;br /&gt;
  &lt;br /&gt;
Sincerely,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Talk Rejection Letter (sample)===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
I'm sorry, but your prepared talk proposal for the 2010 Code4Lib Conference in Asheville, NC did not receive enough votes to make it into the program. But here are a couple things you should know:&lt;br /&gt;
&lt;br /&gt;
- The field of presentations was very large (probably the largest we have had so far) and very strong, so you should not take it too hard.&lt;br /&gt;
- Please remember that there are many additional opportunities for participating, including lightning talks (open to anyone), breakout sessions (open to anyone to suggest and/or participate), and a special &amp;quot;Ask Anything&amp;quot; (or reply anything) open session. Also, the evening socializing opportunities are considered some of the most rewarding times of the event.&lt;br /&gt;
&lt;br /&gt;
Again, my condolences on not having your talk proposal accepted, but I hope we still see you in Asheville, NC in February.&lt;br /&gt;
Roy&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Sponsorship Committee ==&lt;br /&gt;
===Sample Sponsorship Request Letter===&lt;br /&gt;
As you know, Code4Lib is a group of library technologists, programmers, system administrators, web designers, and librarians.  Started in 2003, the group continues to grow--with a journal, a mailing list, and an active IRC channel. Since 2005, Code4Lib has sponsored an annual conference, which has attracted programmers and librarians from around the world.&lt;br /&gt;
&lt;br /&gt;
Topics at past conferences have included library information systems, new directions in library research, semantic web applications, and&lt;br /&gt;
information technology standards, among many others.  More details about the conference, including schedules of previous conferences, can be found from&lt;br /&gt;
http://www.code4lib.org/conference/&lt;br /&gt;
&lt;br /&gt;
Our &amp;lt;&amp;gt; conference will be held in &amp;lt;&amp;gt; from &amp;lt;&amp;gt;. Be a part of this library success story by underwriting the conference!&lt;br /&gt;
&lt;br /&gt;
We have several sponsorship levels:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;&amp;gt;&lt;br /&gt;
I look forward to hearing from you, and can be reached at &amp;lt;&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Best,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;&amp;gt;&lt;br /&gt;
http://code4lib.org/&lt;br /&gt;
&lt;br /&gt;
== Money==&lt;br /&gt;
* [[Conference_Financial_History_At_A_Glance]]&lt;br /&gt;
* private conlist has budget info &lt;br /&gt;
&lt;br /&gt;
== Shortly before the Conference ==&lt;br /&gt;
&lt;br /&gt;
=== Keynotes ===&lt;br /&gt;
# Contact speakers in advance to ask if they need anything, arrange airport pickup, etc&lt;br /&gt;
&lt;br /&gt;
=== Freenode IRC connection ===&lt;br /&gt;
Historically, conference attendees have had trouble maintaining persistent connections to the #code4lib IRC channel. We'd always assumed we were overwhelming the conference facility's Internet connection, but we were actually running into Freenode's IP-based connection limits. Freenode is supportive of the IRC-as-backchannel model, however, and they're happy to work with organizers to raise the connection limit.&lt;br /&gt;
&lt;br /&gt;
Contact the conference facility in advance and see if you can find out what your ''public IP address range'' will be during the conference. (If it starts with 10.*, 192.168.*, or 172.16.*, ask again -- those are &amp;quot;private&amp;quot; IP ranges used for connection sharing.)&lt;br /&gt;
&lt;br /&gt;
Once you have the IP address or range, send an email to [mailto:ilines@freenode.net ilines@freenode.net] containing a request to raise the connection limit. Include conference info, IP range(s), and the expected number of connections. For example:&lt;br /&gt;
&lt;br /&gt;
 To: ilines@freenode.net&lt;br /&gt;
 &lt;br /&gt;
 Hello,&lt;br /&gt;
 &lt;br /&gt;
 I'm helping plan the code4lib 2010 conference, taking place in Asheville, NC next week. &lt;br /&gt;
 Since our backchannel runs through #code4lib on Freenode, we're trying to plan ahead &lt;br /&gt;
 to avoid running up against the connection limit. Would it be possible to raise the cap &lt;br /&gt;
 for us during the conference? Details follow.&lt;br /&gt;
 &lt;br /&gt;
 Conference: code4lib 2010 &amp;lt; http://code4lib.org/conference/2010/ &amp;gt;&lt;br /&gt;
 Dates: February 22-26, 2010&lt;br /&gt;
 Attendees: 250&lt;br /&gt;
 Location: Renaissance Asheville Hotel, Asheville, NC&lt;br /&gt;
 IP Ranges: 12.21.216.106 and the entire 12.21.217.0/24 block&lt;br /&gt;
 &lt;br /&gt;
 We encourage in-channel participation, so we expect a high percentage of attendees to &lt;br /&gt;
 be connected at once. We'll also have two or three channel bots connected from the &lt;br /&gt;
 conference for the lobby monitors.&lt;br /&gt;
 &lt;br /&gt;
 Please let me know if you need any further information, and thanks very much for &lt;br /&gt;
 your help!&lt;br /&gt;
 &lt;br /&gt;
 Michael&lt;br /&gt;
&lt;br /&gt;
I received an automated reply with a ticket number almost instantly, but didn't hear back after that. I sent a quick followup early on the morning of the 22nd, and received a response (from a human) letting me know that it had been taken care of. (Follow-up, one year later: Same experience. Immediate automated reply, but with a need to follow up with Freenode staff in the #freenode channel to get the ticket resolved.)&lt;br /&gt;
&lt;br /&gt;
Additional support is available from the helpful volunteer Freenode staff in the #freenode channel.&lt;br /&gt;
&lt;br /&gt;
== At the Conference ==&lt;br /&gt;
&lt;br /&gt;
===Keynotes===&lt;br /&gt;
# Water at the podium&lt;br /&gt;
# Speaker gifts&lt;br /&gt;
# Dinner plans&lt;br /&gt;
&lt;br /&gt;
=== Timers ===&lt;br /&gt;
* Sit in the front of the room&lt;br /&gt;
* Have several people&lt;br /&gt;
* You may want to use an extra machine&lt;br /&gt;
* Here's what some of the software looks like: http://www.flickr.com/photos/schwartzray/4393891356/ (ask Ed Corrado for details)&lt;br /&gt;
* Dan Chudnov says the best free timer app for OSX is http://www.apimac.com/timer/&lt;br /&gt;
&lt;br /&gt;
=== Lightning Talks ===&lt;br /&gt;
* Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )&lt;br /&gt;
&lt;br /&gt;
===PreConf===&lt;br /&gt;
# make sure projector avail for each session&lt;br /&gt;
# whiteboards or reasonable facsimile thereof&lt;br /&gt;
# everyone wants a power outlet&lt;br /&gt;
&lt;br /&gt;
=== Conference ===&lt;br /&gt;
# power - everyone would like to plug in their laptop&lt;br /&gt;
&lt;br /&gt;
=== Video ===&lt;br /&gt;
# live stream is awesome&lt;br /&gt;
# join.me  ??&lt;br /&gt;
&lt;br /&gt;
=== Ask Anything===&lt;br /&gt;
* Need mics for people to line up at (image: http://www.flickr.com/photos/schwartzray/4393838640/ )&lt;br /&gt;
&lt;br /&gt;
===Book Raffle===&lt;br /&gt;
* (image: http://www.flickr.com/photos/schwartzray/4393619144/ with people for context: http://www.flickr.com/photos/schwartzray/4393623802/ and http://www.flickr.com/photos/schwartzray/4384550127/ ), better if there's a table&lt;br /&gt;
&lt;br /&gt;
=== Flipcharts ===&lt;br /&gt;
Flipcharts can be useful, but it's important to decide what to put on the wiki/website and what to put on a flipchart:&lt;br /&gt;
images: http://www.flickr.com/photos/schwartzray/4392998501/ http://www.flickr.com/photos/47860563@N05/4388430079/&lt;br /&gt;
&lt;br /&gt;
=== Hospitality Suite ===&lt;br /&gt;
# having a few people with room keys, any of whom might need to be available to open up or close down the room at the beginning or end of the evening&lt;br /&gt;
# making sure the mess left for cleaning staff is an appropriate mess&lt;br /&gt;
# making sure the noise made near other hotel guests is an appropriate noise&lt;br /&gt;
# having someone act as a point person to gather a gratuity for the housekeeping staff maintaining the suite&lt;br /&gt;
&lt;br /&gt;
== Suggested Timeline ==&lt;br /&gt;
* See [[C4L2010planning]] for an example &lt;br /&gt;
* Ideal to have program set before registration, including pre-conf&lt;br /&gt;
** also allows clarity for how many spots are avail for non-presenters&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2010]]&lt;br /&gt;
[[Category: Code4Lib2011]]&lt;br /&gt;
&lt;br /&gt;
===Calls for Hosting===&lt;br /&gt;
* 2008:&lt;br /&gt;
* 2009:&lt;br /&gt;
* 2010:&lt;br /&gt;
* 2011: March 5, 2010&lt;br /&gt;
* 2012:&lt;br /&gt;
* 2013:&lt;/div&gt;</summary>
		<author><name>Elizabeth</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Useful_information_from_2012&amp;diff=11535</id>
		<title>Useful information from 2012</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Useful_information_from_2012&amp;diff=11535"/>
				<updated>2012-03-08T19:55:37Z</updated>
		
		<summary type="html">&lt;p&gt;Elizabeth: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=='''Suggestions for streamlining registration:'''==&lt;br /&gt;
&lt;br /&gt;
*Have the pre-conference and conference presentations and presenters voted on before the registration opens. &lt;br /&gt;
**This will decrease the chaos that results in having presenters joining in the open registration and then having to account for their spots at a later date. &lt;br /&gt;
&lt;br /&gt;
*Do not open the hotel or the payment links to whomever registers. Open registration and then those who get into the allotted spots would be contacted with the links for payment and hotel reservation.&lt;br /&gt;
**This will decrease the need for refunds (which cost time and money).&lt;br /&gt;
**This will decrease the chaos of needing to account for people who have hotel rooms who did not get into the conference. &lt;br /&gt;
*Guest room counts and other information useful for venue negotiations are at the end of the document&lt;br /&gt;
&lt;br /&gt;
===How Code4Lib National was handled for 2012.===&lt;br /&gt;
'''''These are not recommendations. Registration was a nightmare.'''''&lt;br /&gt;
&lt;br /&gt;
*Presentations were not chosen before open registration. &lt;br /&gt;
**In 2010 there was a demand to have an earlier registration release date to accommodate for bureaucratic slowness at institutions.  &lt;br /&gt;
**The voting for the presenters went for another 2 weeks beyond the registration opening. This seriously delayed the finalization of the participant list and the release of the wait list. &lt;br /&gt;
**Each presenter (or person on the wait list who then could fill the space left vacant) had to be individually contacted to get their payment and connect with the hotel about their lodging.&lt;br /&gt;
&lt;br /&gt;
*We started with 213 spots open for general registration because pre-conference, conference presentations were not chosen yet and we didn’t know who the sponsors would be.&lt;br /&gt;
**This was an issue because some pre-conference and conference presentations had more than one presenter and some sponsors get more than one spot, so, again, having presentations chosen before registration would preclude those issues.&lt;br /&gt;
&lt;br /&gt;
*We opened registration at a certain time and date. The payment and hotel reservation links were open to whomever registered. &lt;br /&gt;
**Opening conference registration and hotel registrations at the same time proved difficult for several reasons:&lt;br /&gt;
***People who did not get into the conference made hotel reservations. These individuals needed to be individually contacted to cancel their reservations. &lt;br /&gt;
***The hotel had difficulty tracking the cancellations, and opening those spots for other participants.&lt;br /&gt;
***Based on the information from the 2011 host, the need for hotel rooms was seriously under estimated creating the need for several different blocks of rooms with several rooming contracts with different rates and different deadlines.&lt;br /&gt;
***The hotel reservation system was not prepared for the onslaught and we broke their registration system, creating more chaos. &lt;br /&gt;
&lt;br /&gt;
*Those 213 spots were filled in within the hour. The payment and hotel information was then moved so that no one else could access it. This created issues with registrations bouncing. &lt;br /&gt;
&lt;br /&gt;
*Around 15 people canceled their registrations 2 weeks before the conference which necessitated individually contacting those on the wait list and arranging for payment.&lt;br /&gt;
&lt;br /&gt;
*The participants list was not finalized until 7 working days before the conference.&lt;br /&gt;
**There continue to be messages on the lists offering spots even up to the Thursday and Friday before the start of the conference. Keeping track of dietary needs and cancellations have taken considerable Administrative time. &lt;br /&gt;
&lt;br /&gt;
*Original projection of Admin time was grossly under estimated. Based on other conventions of generally the same size and geographically diverse, the Admin time was estimated at 10 working days, not including actual time/overtime at the conference. Actual time was about 29 full working days, again, not including the actual time/overtime at the conference. &lt;br /&gt;
&lt;br /&gt;
===Statistics to help with 2013 Code4Lib Hosting===&lt;br /&gt;
&lt;br /&gt;
*Strict 250 participant cap – mandate from the community&lt;br /&gt;
*Adequate bandwidth for wireless usage at conference is vital&lt;br /&gt;
**Ended up needing wired internet access for streaming – was not part of the original negotiations&lt;br /&gt;
**Some questions that we asked the venues:&lt;br /&gt;
***Is your venue able to provide at least 8 mb/sec guaranteed service, either through a dedicated connection or a private VLAN?&lt;br /&gt;
***Can you provide multi-band access points that support both 24 &amp;amp; 5 Ghz service -- 802.11b, g, n and, ideally, 802.11a?&lt;br /&gt;
***Can your system accommodate at least 300 simultaneous connections?&lt;br /&gt;
*Make sure there are Vegetarian meals (30 Vegetarians; 4 Vegans; 3 Gluten-free; 12 Food Allergies)&lt;br /&gt;
*Anticipated Admin time usage (Not including actual time at conference): 10 working days&lt;br /&gt;
*Actual Admin time usage (Not including actual time at conference): 29 working days&lt;br /&gt;
&lt;br /&gt;
===Guest Room Pick up===&lt;br /&gt;
'''''We have use of the same room rate 2 days on both sides of the conference.'''''&lt;br /&gt;
&lt;br /&gt;
Total room Pick-up: 633&lt;br /&gt;
&lt;br /&gt;
:Feb 4  - 9 (2 days before conference)&lt;br /&gt;
:Feb 5 - 102 (day before pre-conference)&lt;br /&gt;
:Feb 6 - 155 (Pre-conference)&lt;br /&gt;
:Feb 7 – 156 (Conference)&lt;br /&gt;
:Feb 8 – 155 (Conference)&lt;br /&gt;
:Feb 9 – 47 (Last ½ day of conference)&lt;br /&gt;
:Feb 10 – 7&lt;br /&gt;
:Feb 11 – 2&lt;br /&gt;
&lt;br /&gt;
===T-shirt Amounts and Sizes===&lt;br /&gt;
'''''This is to give you an idea of what quantities you are looking for if you decide to do T-shirts again.'''''&lt;br /&gt;
&lt;br /&gt;
:Did not want a T-shirt - 9&lt;br /&gt;
:Small - 32 &lt;br /&gt;
:Medium - 82 &lt;br /&gt;
:Large - 66 &lt;br /&gt;
:X-large - 52 &lt;br /&gt;
:2x - 9 &lt;br /&gt;
:3X - 3 &lt;br /&gt;
:4X - 1&lt;br /&gt;
&lt;br /&gt;
===Budgetary Considerations===&lt;br /&gt;
'''''This is not a comprehensive list'''''&lt;br /&gt;
&lt;br /&gt;
When budgeting, things to account for are:&lt;br /&gt;
*Credit Card Charges (how much it will cost to take credit cards)&lt;br /&gt;
*Scholarships&lt;br /&gt;
*T-shirts (this are more expensive than originally thought)&lt;br /&gt;
*Loss from Cancellations (Credit Card refund costs, lost revenue, other things such as T-shirts and lowering minimum participant counts for hotel contracts)&lt;br /&gt;
*Internet usage and Networks&lt;br /&gt;
*Video and Streaming&lt;br /&gt;
*Key Note Speaker Costs, Complimentary registrations&lt;br /&gt;
*Logistics of payments and refunds for out of Country participants&lt;br /&gt;
&lt;br /&gt;
===Things to think about…===&lt;br /&gt;
&lt;br /&gt;
*Not having A/V available for the pre-conference did not work well. There were numerous requests for projectors and screens&lt;br /&gt;
*Don’t forget the need for extra extension cords and surge protectors. It was much less expensive to purchase the power cords than to pay for the use through the hotel &lt;br /&gt;
*The Hospitality suite needs to have room for around 50 people and the ability to bring alcohol&lt;br /&gt;
*Think about getting a list of programs and software needed for presenters before the beginning of the conference and setting up an equipment check when the A/V is set up or the night before the beginning of the conference&lt;br /&gt;
*The ‘Ask Anything’ sessions needs 3 microphones – 1 for the presenter and 2 for the audience&lt;br /&gt;
*There was a request for a Book/Magazine exchange&lt;/div&gt;</summary>
		<author><name>Elizabeth</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Useful_information_from_2012&amp;diff=11534</id>
		<title>Useful information from 2012</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Useful_information_from_2012&amp;diff=11534"/>
				<updated>2012-03-08T19:54:53Z</updated>
		
		<summary type="html">&lt;p&gt;Elizabeth: New page: =='''Suggestions for streamlining registration:'''==  *Have the pre-conference and conference presentations and presenters voted on before the registration opens.  **This will decrease the...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=='''Suggestions for streamlining registration:'''==&lt;br /&gt;
&lt;br /&gt;
*Have the pre-conference and conference presentations and presenters voted on before the registration opens. &lt;br /&gt;
**This will decrease the chaos that results in having presenters joining in the open registration and then having to account for their spots at a later date. &lt;br /&gt;
&lt;br /&gt;
*Do not open the hotel or the payment links to whomever registers. Open registration and then those who get into the allotted spots would be contacted with the links for payment and hotel reservation.&lt;br /&gt;
**This will decrease the need for refunds (which cost time and money).&lt;br /&gt;
**This will decrease the chaos of needing to account for people who have hotel rooms who did not get into the conference. &lt;br /&gt;
*Guest room counts and other information useful for venue negotiations are at the end of the document&lt;br /&gt;
&lt;br /&gt;
===How Code4Lib National was handled for 2012.===&lt;br /&gt;
'''''These are not recommendations. Registration was a nightmare.'''''&lt;br /&gt;
&lt;br /&gt;
*Presentations were not chosen before open registration. &lt;br /&gt;
**In 2010 there was a demand to have an earlier registration release date to accommodate for bureaucratic slowness at institutions.  &lt;br /&gt;
**The voting for the presenters went for another 2 weeks beyond the registration opening. This seriously delayed the finalization of the participant list and the release of the wait list. &lt;br /&gt;
**Each presenter (or person on the wait list who then could fill the space left vacant) had to be individually contacted to get their payment and connect with the hotel about their lodging.&lt;br /&gt;
&lt;br /&gt;
*We started with 213 spots open for general registration because pre-conference, conference presentations were not chosen yet and we didn’t know who the sponsors would be.&lt;br /&gt;
**This was an issue because some pre-conference and conference presentations had more than one presenter and some sponsors get more than one spot, so, again, having presentations chosen before registration would preclude those issues.&lt;br /&gt;
&lt;br /&gt;
*We opened registration at a certain time and date. The payment and hotel reservation links were open to whomever registered. &lt;br /&gt;
**Opening conference registration and hotel registrations at the same time proved difficult for several reasons:&lt;br /&gt;
***People who did not get into the conference made hotel reservations. These individuals needed to be individually contacted to cancel their reservations. &lt;br /&gt;
***The hotel had difficulty tracking the cancellations, and opening those spots for other participants.&lt;br /&gt;
***Based on the information from the 2011 host, the need for hotel rooms was seriously under estimated creating the need for several different blocks of rooms with several rooming contracts with different rates and different deadlines.&lt;br /&gt;
***The hotel reservation system was not prepared for the onslaught and we broke their registration system, creating more chaos. &lt;br /&gt;
&lt;br /&gt;
*Those 213 spots were filled in within the hour. The payment and hotel information was then moved so that no one else could access it. This created issues with registrations bouncing. &lt;br /&gt;
&lt;br /&gt;
*Around 15 people canceled their registrations 2 weeks before the conference which necessitated individually contacting those on the wait list and arranging for payment.&lt;br /&gt;
&lt;br /&gt;
*The participants list was not finalized until 7 working days before the conference.&lt;br /&gt;
**There continue to be messages on the lists offering spots even up to the Thursday and Friday before the start of the conference. Keeping track of dietary needs and cancellations have taken considerable Administrative time. &lt;br /&gt;
&lt;br /&gt;
*Original projection of Admin time was grossly under estimated. Based on other conventions of generally the same size and geographically diverse, the Admin time was estimated at 10 working days, not including actual time/overtime at the conference. Actual time was about 29 full working days, again, not including the actual time/overtime at the conference. &lt;br /&gt;
&lt;br /&gt;
===Statistics to help with 2013 Code4Lib Hosting===&lt;br /&gt;
&lt;br /&gt;
*Strict 250 participant cap – mandate from the community&lt;br /&gt;
*Adequate bandwidth for wireless usage at conference is vital&lt;br /&gt;
**Ended up needing wired internet access for streaming – was not part of the original negotiations&lt;br /&gt;
**Some questions that we asked the venues:&lt;br /&gt;
***Is your venue able to provide at least 8 mb/sec guaranteed service, either through a dedicated connection or a private VLAN?&lt;br /&gt;
***Can you provide multi-band access points that support both 24 &amp;amp; 5 Ghz service -- 802.11b, g, n and, ideally, 802.11a?&lt;br /&gt;
***Can your system accommodate at least 300 simultaneous connections?&lt;br /&gt;
*Make sure there are Vegetarian meals (30 Vegetarians; 4 Vegans; 3 Gluten-free; 12 Food Allergies)&lt;br /&gt;
*Anticipated Admin time usage (Not including actual time at conference): 10 working days&lt;br /&gt;
*Actual Admin time usage (Not including actual time at conference): 29 working days&lt;br /&gt;
&lt;br /&gt;
===Guest Room Pick up===&lt;br /&gt;
'''''We have use of the same room rate 2 days on both sides of the conference.'''''&lt;br /&gt;
&lt;br /&gt;
Total room Pick-up: 633&lt;br /&gt;
&lt;br /&gt;
:Feb 4  - 9 (2 days before conference)&lt;br /&gt;
:Feb 5 - 102 (day before pre-conference)&lt;br /&gt;
:Feb 6 - 155 (Pre-conference)&lt;br /&gt;
:Feb 7 – 156 (Conference)&lt;br /&gt;
:Feb 8 – 155 (Conference)&lt;br /&gt;
:Feb 9 – 47 (Last ½ day of conference)&lt;br /&gt;
:Feb 10 – 7&lt;br /&gt;
:Feb 11 – 2&lt;br /&gt;
&lt;br /&gt;
===T-shirt Amounts and Sizes===&lt;br /&gt;
'''''This is to give you an idea of what quantities you are looking for if you decide to do T-shirts again.'''''&lt;br /&gt;
&lt;br /&gt;
:Did not want a T-shirt - 9&lt;br /&gt;
:Small - 32 &lt;br /&gt;
:Medium - 82 &lt;br /&gt;
:Large - 66 &lt;br /&gt;
:X-large - 52 &lt;br /&gt;
:2x - 9 &lt;br /&gt;
:3X - 3 &lt;br /&gt;
:4X - 1&lt;br /&gt;
&lt;br /&gt;
===Budgetary Considerations===&lt;br /&gt;
'''''This is not a comprehensive list'''''&lt;br /&gt;
&lt;br /&gt;
When budgeting, things to account for are:&lt;br /&gt;
*Credit Card Charges (how much it will cost to take credit cards)&lt;br /&gt;
*Scholarships&lt;br /&gt;
*T-shirts (this are more expensive than originally thought)&lt;br /&gt;
*Loss from Cancellations (Credit Card refund costs, lost revenue, other things such as T-shirts and lowering minimum participant counts for hotel contracts)&lt;br /&gt;
*Internet usage and Networks&lt;br /&gt;
*Video and Streaming&lt;br /&gt;
*Key Note Speaker Costs, Complimentary registrations&lt;br /&gt;
*Logistics of payments and refunds for out of Country participants&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Things to think about…===&lt;br /&gt;
&lt;br /&gt;
*Not having A/V available for the pre-conference did not work well. There were numerous requests for projectors and screens&lt;br /&gt;
*Don’t forget the need for extra extension cords and surge protectors. It was much less expensive to purchase the power cords than to pay for the use through the hotel &lt;br /&gt;
*The Hospitality suite needs to have room for around 50 people and the ability to bring alcohol&lt;br /&gt;
*Think about getting a list of programs and software needed for presenters before the beginning of the conference and setting up an equipment check when the A/V is set up or the night before the beginning of the conference&lt;br /&gt;
*The ‘Ask Anything’ sessions needs 3 microphones – 1 for the presenter and 2 for the audience&lt;br /&gt;
*There was a request for a Book/Magazine exchange&lt;/div&gt;</summary>
		<author><name>Elizabeth</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=How_To_Plan_A_Code4LibCon&amp;diff=11533</id>
		<title>How To Plan A Code4LibCon</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=How_To_Plan_A_Code4LibCon&amp;diff=11533"/>
				<updated>2012-03-08T19:35:01Z</updated>
		
		<summary type="html">&lt;p&gt;Elizabeth: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* Apply to be a host&lt;br /&gt;
&lt;br /&gt;
* Consider your action plan&lt;br /&gt;
** Identify your venues for both the conference and the hotel (if different). This is critical, as you'll want to get some cost estimates from each. When we hosted in Corvallis, the campus provided the conference space at a low cost, and this made running the conference much more affordable. When we hosted the conference in Portland, and held everything in a single hotel, we had to acquire 2x the amount of sponsorship than what appears to be normal.&lt;br /&gt;
** Speaking of sponsorship, I believe we average around 20k per year in sponsorships to help run the conference and keep the registration low. Factor this into your budget.&lt;br /&gt;
** Also, when you get cost estimates, don't forget to include food costs.&lt;br /&gt;
** WIRELESS: Always an issue it seems. If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you are looking at a hotel or other venue, make sure you talk to them about bandwidth and costs. IMHO, the two things that really need to be addressed each year are connectivity and food - everything else generally manages itself in terms of facilities.&lt;br /&gt;
*** make sure VPN is allowed&lt;br /&gt;
** See if your institution has a conference planning services group or something similar - if it does, then I highly recommend using them. They'll handle registration, budgeting, contracts, etc, and really make life easy.&lt;br /&gt;
** Regarding conference hotel, you'll want to make sure that there are blocks of rooms available - not usually too bad an issue in larger towns, but in some college or smaller towns, hotel rooms may be limited.&lt;br /&gt;
*** prepare the hotel for deluge via web when announcement is made about hotel registration available.  We overwhelmed the Seattle hotel in 2012&lt;br /&gt;
** Remember, your institution is taking the risk of covering any costs not covered by registrations and sponsorships. To this point, I believe the conference has always ended up in the black, but there is always a chance it won't in a given year. Drafting a rough budget before submitting a proposal is critical.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Get approved by the community&lt;br /&gt;
* Find a hotel, negotiate and sign a contract with them. [[Sample RFI]]&lt;br /&gt;
* Invite the community to help with &lt;br /&gt;
* Have a timeline&lt;br /&gt;
*[[Useful information from 2012 Code4Lib]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Important Public Resources ==&lt;br /&gt;
* Past calls for host sites: [http://code4lib.org/node/275 2010] - &lt;br /&gt;
* [http://dewey.library.nd.edu/mailing-lists/code4lib/ Code4Lib listserv]&lt;br /&gt;
* [http://groups.google.com/group/code4libcon Code4LibCon listserv]&lt;br /&gt;
* Sponsorship info (public)&lt;br /&gt;
* [http://code4lib.org/logo/ Logos]&lt;br /&gt;
&lt;br /&gt;
== Important Private Resources ==&lt;br /&gt;
* Code4LibCon-hostsite listserv&lt;br /&gt;
* Budgets from previous years&lt;br /&gt;
* Sponsorship info (private)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Gender Diversity &amp;amp; Minority Scholarship Committee==&lt;br /&gt;
The scholarship committee is a self-selected group that manages the gender diversity &amp;amp; minority scholarships. Separate groups handle AngelFund and Code4LibJapan scholarships.&lt;br /&gt;
&lt;br /&gt;
===Suggestions received===&lt;br /&gt;
* Send to a wider bunch of listservs, including for national orgs (ALA/SLA/MLA) &amp;amp; relevant sections? &amp;amp; student chapter&lt;br /&gt;
&lt;br /&gt;
===Process===&lt;br /&gt;
# Put out a call&lt;br /&gt;
# Receive and coordinate applications&lt;br /&gt;
# Distribute applications to the committee&lt;br /&gt;
# Select awardees&lt;br /&gt;
# Inform selected candidates&lt;br /&gt;
# Notify unsuccessful candidates&lt;br /&gt;
# Announce to Code4Lib main listserv and post on code4lib.org (e.g. http://code4lib.org/node/274 )&lt;br /&gt;
# Hosts work with awardees on reimbursement, registration, etc.&lt;br /&gt;
# Follow up with awardees after the conference -- receive report, ask for suggestions, etc.&lt;br /&gt;
&lt;br /&gt;
== Program Committtee==&lt;br /&gt;
The program committee is a self-selected group that manages talk proposals and other aspects of the program.&lt;br /&gt;
&lt;br /&gt;
(Add more info for the program committee here!)&lt;br /&gt;
&lt;br /&gt;
===Talk Acceptance Letter (samples)===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Dear &amp;lt;&amp;lt;first name last name&amp;gt;&amp;gt;,&lt;br /&gt;
 &lt;br /&gt;
On behalf of the Code4Lib Program Planning Committee, I am pleased to &lt;br /&gt;
notify you that your proposal, &amp;lt;&amp;lt;proposal title&amp;gt;&amp;gt; has been accepted for &lt;br /&gt;
the Code4Lib &amp;lt;&amp;lt;year&amp;gt;&amp;gt; in &amp;lt;&amp;lt;location&amp;gt;&amp;gt;.  Please reply to this message to &lt;br /&gt;
confirm your intention to present the approved session at the Conference.  &lt;br /&gt;
If at any time in the future you need to bow out or have any program &lt;br /&gt;
changes, please notify us immediately.  You will be sent a letter of &lt;br /&gt;
agreement soon.&lt;br /&gt;
 &lt;br /&gt;
The schedule for the conference is here:&lt;br /&gt;
&lt;br /&gt;
   http://code4lib.org/conference/2011/schedule&lt;br /&gt;
&lt;br /&gt;
You will have 20 minutes for your talk, including questions and answers.&lt;br /&gt;
A quick transition between speakers will be necessary.&lt;br /&gt;
 &lt;br /&gt;
It is very important that you focus your presentation on the more unique &lt;br /&gt;
and technical aspects of your topic whenever possible.  Although Code4Lib&lt;br /&gt;
attendees come from many different work environments, they attend Code4Lib &lt;br /&gt;
events for information technology education.&lt;br /&gt;
 &lt;br /&gt;
Experts like you are the heart of Code4Lib.  We really appreciate your contribution &lt;br /&gt;
and look forward to working with you.&lt;br /&gt;
  &lt;br /&gt;
Sincerely,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Talk Rejection Letter (sample)===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
I'm sorry, but your prepared talk proposal for the 2010 Code4Lib Conference in Asheville, NC did not receive enough votes to make it into the program. But here are a couple things you should know:&lt;br /&gt;
&lt;br /&gt;
- The field of presentations was very large (probably the largest we have had so far) and very strong, so you should not take it too hard.&lt;br /&gt;
- Please remember that there are many additional opportunities for participating, including lightning talks (open to anyone), breakout sessions (open to anyone to suggest and/or participate), and a special &amp;quot;Ask Anything&amp;quot; (or reply anything) open session. Also, the evening socializing opportunities are considered some of the most rewarding times of the event.&lt;br /&gt;
&lt;br /&gt;
Again, my condolences on not having your talk proposal accepted, but I hope we still see you in Asheville, NC in February.&lt;br /&gt;
Roy&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Sponsorship Committee ==&lt;br /&gt;
===Sample Sponsorship Request Letter===&lt;br /&gt;
As you know, Code4Lib is a group of library technologists, programmers, system administrators, web designers, and librarians.  Started in 2003, the group continues to grow--with a journal, a mailing list, and an active IRC channel. Since 2005, Code4Lib has sponsored an annual conference, which has attracted programmers and librarians from around the world.&lt;br /&gt;
&lt;br /&gt;
Topics at past conferences have included library information systems, new directions in library research, semantic web applications, and&lt;br /&gt;
information technology standards, among many others.  More details about the conference, including schedules of previous conferences, can be found from&lt;br /&gt;
http://www.code4lib.org/conference/&lt;br /&gt;
&lt;br /&gt;
Our &amp;lt;&amp;gt; conference will be held in &amp;lt;&amp;gt; from &amp;lt;&amp;gt;. Be a part of this library success story by underwriting the conference!&lt;br /&gt;
&lt;br /&gt;
We have several sponsorship levels:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;&amp;gt;&lt;br /&gt;
I look forward to hearing from you, and can be reached at &amp;lt;&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Best,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;&amp;gt;&lt;br /&gt;
http://code4lib.org/&lt;br /&gt;
&lt;br /&gt;
== Money==&lt;br /&gt;
* [[Conference_Financial_History_At_A_Glance]]&lt;br /&gt;
* private conlist has budget info &lt;br /&gt;
&lt;br /&gt;
== Shortly before the Conference ==&lt;br /&gt;
&lt;br /&gt;
=== Keynotes ===&lt;br /&gt;
# Contact speakers in advance to ask if they need anything, arrange airport pickup, etc&lt;br /&gt;
&lt;br /&gt;
=== Freenode IRC connection ===&lt;br /&gt;
Historically, conference attendees have had trouble maintaining persistent connections to the #code4lib IRC channel. We'd always assumed we were overwhelming the conference facility's Internet connection, but we were actually running into Freenode's IP-based connection limits. Freenode is supportive of the IRC-as-backchannel model, however, and they're happy to work with organizers to raise the connection limit.&lt;br /&gt;
&lt;br /&gt;
Contact the conference facility in advance and see if you can find out what your ''public IP address range'' will be during the conference. (If it starts with 10.*, 192.168.*, or 172.16.*, ask again -- those are &amp;quot;private&amp;quot; IP ranges used for connection sharing.)&lt;br /&gt;
&lt;br /&gt;
Once you have the IP address or range, send an email to [mailto:ilines@freenode.net ilines@freenode.net] containing a request to raise the connection limit. Include conference info, IP range(s), and the expected number of connections. For example:&lt;br /&gt;
&lt;br /&gt;
 To: ilines@freenode.net&lt;br /&gt;
 &lt;br /&gt;
 Hello,&lt;br /&gt;
 &lt;br /&gt;
 I'm helping plan the code4lib 2010 conference, taking place in Asheville, NC next week. &lt;br /&gt;
 Since our backchannel runs through #code4lib on Freenode, we're trying to plan ahead &lt;br /&gt;
 to avoid running up against the connection limit. Would it be possible to raise the cap &lt;br /&gt;
 for us during the conference? Details follow.&lt;br /&gt;
 &lt;br /&gt;
 Conference: code4lib 2010 &amp;lt; http://code4lib.org/conference/2010/ &amp;gt;&lt;br /&gt;
 Dates: February 22-26, 2010&lt;br /&gt;
 Attendees: 250&lt;br /&gt;
 Location: Renaissance Asheville Hotel, Asheville, NC&lt;br /&gt;
 IP Ranges: 12.21.216.106 and the entire 12.21.217.0/24 block&lt;br /&gt;
 &lt;br /&gt;
 We encourage in-channel participation, so we expect a high percentage of attendees to &lt;br /&gt;
 be connected at once. We'll also have two or three channel bots connected from the &lt;br /&gt;
 conference for the lobby monitors.&lt;br /&gt;
 &lt;br /&gt;
 Please let me know if you need any further information, and thanks very much for &lt;br /&gt;
 your help!&lt;br /&gt;
 &lt;br /&gt;
 Michael&lt;br /&gt;
&lt;br /&gt;
I received an automated reply with a ticket number almost instantly, but didn't hear back after that. I sent a quick followup early on the morning of the 22nd, and received a response (from a human) letting me know that it had been taken care of. (Follow-up, one year later: Same experience. Immediate automated reply, but with a need to follow up with Freenode staff in the #freenode channel to get the ticket resolved.)&lt;br /&gt;
&lt;br /&gt;
Additional support is available from the helpful volunteer Freenode staff in the #freenode channel.&lt;br /&gt;
&lt;br /&gt;
== At the Conference ==&lt;br /&gt;
&lt;br /&gt;
===Keynotes===&lt;br /&gt;
# Water at the podium&lt;br /&gt;
# Speaker gifts&lt;br /&gt;
# Dinner plans&lt;br /&gt;
&lt;br /&gt;
=== Timers ===&lt;br /&gt;
* Sit in the front of the room&lt;br /&gt;
* Have several people&lt;br /&gt;
* You may want to use an extra machine&lt;br /&gt;
* Here's what some of the software looks like: http://www.flickr.com/photos/schwartzray/4393891356/ (ask Ed Corrado for details)&lt;br /&gt;
* Dan Chudnov says the best free timer app for OSX is http://www.apimac.com/timer/&lt;br /&gt;
&lt;br /&gt;
=== Lightning Talks ===&lt;br /&gt;
* Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )&lt;br /&gt;
&lt;br /&gt;
===PreConf===&lt;br /&gt;
# make sure projector avail for each session&lt;br /&gt;
# whiteboards or reasonable facsimile thereof&lt;br /&gt;
# everyone wants a power outlet&lt;br /&gt;
&lt;br /&gt;
=== Conference ===&lt;br /&gt;
# power - everyone would like to plug in their laptop&lt;br /&gt;
&lt;br /&gt;
=== Video ===&lt;br /&gt;
# live stream is awesome&lt;br /&gt;
# join.me  ??&lt;br /&gt;
&lt;br /&gt;
=== Ask Anything===&lt;br /&gt;
* Need mics for people to line up at (image: http://www.flickr.com/photos/schwartzray/4393838640/ )&lt;br /&gt;
&lt;br /&gt;
===Book Raffle===&lt;br /&gt;
* (image: http://www.flickr.com/photos/schwartzray/4393619144/ with people for context: http://www.flickr.com/photos/schwartzray/4393623802/ and http://www.flickr.com/photos/schwartzray/4384550127/ ), better if there's a table&lt;br /&gt;
&lt;br /&gt;
=== Flipcharts ===&lt;br /&gt;
Flipcharts can be useful, but it's important to decide what to put on the wiki/website and what to put on a flipchart:&lt;br /&gt;
images: http://www.flickr.com/photos/schwartzray/4392998501/ http://www.flickr.com/photos/47860563@N05/4388430079/&lt;br /&gt;
&lt;br /&gt;
=== Hospitality Suite ===&lt;br /&gt;
# having a few people with room keys, any of whom might need to be available to open up or close down the room at the beginning or end of the evening&lt;br /&gt;
# making sure the mess left for cleaning staff is an appropriate mess&lt;br /&gt;
# making sure the noise made near other hotel guests is an appropriate noise&lt;br /&gt;
# having someone act as a point person to gather a gratuity for the housekeeping staff maintaining the suite&lt;br /&gt;
&lt;br /&gt;
== Suggested Timeline ==&lt;br /&gt;
* See [[C4L2010planning]] for an example &lt;br /&gt;
* Ideal to have program set before registration, including pre-conf&lt;br /&gt;
** also allows clarity for how many spots are avail for non-presenters&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2010]]&lt;br /&gt;
[[Category: Code4Lib2011]]&lt;br /&gt;
&lt;br /&gt;
===Calls for Hosting===&lt;br /&gt;
* 2008:&lt;br /&gt;
* 2009:&lt;br /&gt;
* 2010:&lt;br /&gt;
* 2011: March 5, 2010&lt;br /&gt;
* 2012:&lt;br /&gt;
* 2013:&lt;/div&gt;</summary>
		<author><name>Elizabeth</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Main_Page&amp;diff=11418</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Main_Page&amp;diff=11418"/>
				<updated>2012-02-13T21:48:36Z</updated>
		
		<summary type="html">&lt;p&gt;Elizabeth: /* Earlier Conferences and events */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{|align=right&lt;br /&gt;
 |__TOC__&lt;br /&gt;
 |}&lt;br /&gt;
&lt;br /&gt;
== About Code4Lib ==&lt;br /&gt;
&lt;br /&gt;
* [[About Code4Lib]] - Background and history of the community&lt;br /&gt;
* [[A Guide for the Perplexed]] - Building skills for working with library technologies&lt;br /&gt;
* [[How to hack code4lib]] - For those newer to the community&lt;br /&gt;
&lt;br /&gt;
== Code4Lib 2012 Conference ==&lt;br /&gt;
&lt;br /&gt;
''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2012 Code4lib2012 category]''&lt;br /&gt;
&lt;br /&gt;
* [http://code4lib.org/conference/2012/ 2012 home]&lt;br /&gt;
* [[During_the_Conference_Volunteers|Volunteer to help at code4lib 2012]]&lt;br /&gt;
* [[2012_committees_sign-up_page|Volunteer to help plan 2012 conference]]&lt;br /&gt;
* [[2012_preconference_proposals|2012 Preconference Proposals]]--due Sunday, November 20&lt;br /&gt;
* [[2012_talks_proposals|2012 Talk Proposals]]--due Sunday, November 20&lt;br /&gt;
* [[2012_c4l2012_social_activities|Social Activities]] - ideas and sign-up&lt;br /&gt;
* [[c4l2012_rideshare|Rideshare-Roomshare]]&lt;br /&gt;
* [[c4l2012_t-shirtcontest|T-shirt contest]]&lt;br /&gt;
* [[ideas_for_2012|Put your ideas for 2012 here!]]&lt;br /&gt;
* [[C4L2012_Call_For_Host|2012 Call For Host]]&lt;br /&gt;
* [[How To Plan A Code4LibCon]]&lt;br /&gt;
* [http://linkd.in/unhJsR LinkedIn Event]&lt;br /&gt;
* [[2012_twitter_list|List your Twitter handle here]]&lt;br /&gt;
* [[2012_Lightning_Talks_Signup|Lightning Talks Signup]]&lt;br /&gt;
* [http://irc.code4lib.org/ IRC Channel Timeline &amp;amp; Log]&lt;br /&gt;
* [http://www.livestream.com/code4lib Conference Livestream] (non-attendees only, please!)&lt;br /&gt;
&lt;br /&gt;
== Local / Regional Groups ==&lt;br /&gt;
&lt;br /&gt;
* [[NYC|Code4LibNYC]] - NYC and surrounding areas&lt;br /&gt;
* [[NEC4L|New England Code4lib]] - New England&lt;br /&gt;
* [[NL|Code4Bib]] - Dutch Code4Bib&lt;br /&gt;
* [[MDC|Code4libMDC]] - Maryland, Washington D.C and surrounding areas&lt;br /&gt;
* [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest&lt;br /&gt;
* [[North|code4lib North]] - Ontario and surrounding areas ''(new for Jan 2010!)''&lt;br /&gt;
* [[Midwest|Code4Lib Midwest]] - Wherever that is...&lt;br /&gt;
* [http://groups.google.com/group/ikr-fejlesztok/ Code4lib.hu] - Group of Hungarian library developers&lt;br /&gt;
* [http://www.code4lib.jp/ Code4Lib Japan] -  ''(new in 2010!)'', see also [http://twitter.com/yesonline/statuses/28561046501 tweet from Jerry Lee]&lt;br /&gt;
* [http://groups.google.com/group/code4glam Code4GLAM Australia] - coders, hackers, developers and technologists in the Australian GLAM (Galleries, Libraries, Archives &amp;amp; Museums) sector.&lt;br /&gt;
&lt;br /&gt;
== Interest Groups ==&lt;br /&gt;
&lt;br /&gt;
* [[ILS_Interop|ILS Interoperability]] - A group working to develop an infrastructure for interoperating between discovery layers and integrated library systems.&lt;br /&gt;
* [[Open_Source_Book_Widgets|Open Source Book Widgets]] - A list of open source book widgets&lt;br /&gt;
* [[Discovery|Open Source Discovery]] - Open Source application to enhance and support &amp;quot;discovery&amp;quot; in libraries&lt;br /&gt;
* [[Mobile_Apps|Mobile Applications]] - A group interested in mobile web and native application development for libraries&lt;br /&gt;
* [[Sources_Of_Metadata|Sources Of Metadata]] - list of api's and sources of interest to libraries&lt;br /&gt;
&lt;br /&gt;
== Software Usage and Documentation ==&lt;br /&gt;
&lt;br /&gt;
* [[Umlaut]] - OpenURL link resolving middleware&lt;br /&gt;
* [[:Category:Patterns|Patterns for Collaborative Code]] - Patterns to make your open source 'more open', more amenable to distributed development and use at multiple institutions without forking. &lt;br /&gt;
* [[ILS Documentation]]&lt;br /&gt;
* [[OSS Directory]]&lt;br /&gt;
* [[Working with MaRC]]&lt;br /&gt;
* [[Rogue]] - principles for standards creation&lt;br /&gt;
&lt;br /&gt;
== Code4Lib Journal ==&lt;br /&gt;
&lt;br /&gt;
* [[:Category:Code4Lib Journal|Code4Lib Journal]] - information and working documents&lt;br /&gt;
&lt;br /&gt;
== Current topics ==&lt;br /&gt;
&lt;br /&gt;
* [[Code4Lib Website Update]]&lt;br /&gt;
* [[OCLC Policy Change]]&lt;br /&gt;
* [[SirsiDynix: Integrated Library System Platforms on Open Source]]&lt;br /&gt;
* [[Parsing Library Data]]&lt;br /&gt;
&lt;br /&gt;
== Other Code4Lib Sites ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.code4lib.org/ code4lib.org]&lt;br /&gt;
* [http://planet.code4lib.org planet.code4lib.org]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Earlier Conferences and events ==&lt;br /&gt;
[[Conference Financial History At A Glance]]&lt;br /&gt;
&lt;br /&gt;
===Code4Lib 2012 Conference===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Code4Lib 2011 Conference ===&lt;br /&gt;
''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2011 Code4lib2011 category]''&lt;br /&gt;
&lt;br /&gt;
* [http://code4lib.org/conference/2011 C4L2011 Home]&lt;br /&gt;
* [[C4L2011_registration | Registration Information!]]&lt;br /&gt;
* [[2011_committees_sign-up_page | 2011 Committees Sign-Up]] - '''Volunteer to help'''&lt;br /&gt;
* [[How To Plan A Code4LibCon]]&lt;br /&gt;
* [[C4L2011_social_activities|Social Activities]] - ideas &amp;amp; sign-up&lt;br /&gt;
* [[C4L2011_planning_wishlist|'''Put your ideas for 2011 here!''']]&lt;br /&gt;
* [http://www.facebook.com/event.php?eid=161853827200024 Facebook Event Page]&lt;br /&gt;
* [http://events.linkedin.com/Code4Lib-2011/pub/448897 LinkedIn Event Page]&lt;br /&gt;
&amp;lt;!-- commenting out until later * '''[[2011 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff''' --&amp;gt;&lt;br /&gt;
* [[C4L2011_rideshare|Airport Ride Share and Carpooling]]&lt;br /&gt;
* [[C4L2011_roomshare | Hotel room share]]&lt;br /&gt;
&lt;br /&gt;
=== Code4Lib 2010 Conference ===&lt;br /&gt;
&lt;br /&gt;
''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2010 Code4lib2010 category]''&lt;br /&gt;
* [http://code4lib.org/conference/2010/schedule Finalized schedule]&lt;br /&gt;
* [[2010 Lightning Talks Signup]] - sign up to give a lightning talk&lt;br /&gt;
* [[2010 Breakout Sessions]] - suggest a breakout here&lt;br /&gt;
* '''[[2010 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff'''&lt;br /&gt;
* [[C4L2010_social_activities|Social Activities]] - ideas &amp;amp; sign-up&lt;br /&gt;
* [[Committees sign-up page]] - '''Volunteer to help'''&lt;br /&gt;
* [[C4L2011_planning_wishlist|'''Put your ideas for 2011 here!''']]&lt;br /&gt;
* [[Asheville Airport to Hotel Van Manifest]] &lt;br /&gt;
* [[C4L2010rideshare|General shared travel/transportation planning]]&lt;br /&gt;
* [[C4L2010planning:RoommatesRidesEtc|Roommates, Rides, Etc]]&lt;br /&gt;
* [[C4L2010_manning_discount|Manning Publications Discount]] - discount code (40% off) for use by attendees through Feb. 28, 2010&lt;br /&gt;
* Thanks also to our other sponsors!&lt;br /&gt;
* [[C4L2010planning|2010 Planning]]&lt;br /&gt;
* [[C4L2010planning:_wishlist | 2010 Planning Wishlist]] - planning page for issues, expectations, etc. for the 2010 conference&lt;br /&gt;
&lt;br /&gt;
=== Code4Lib 2009 Conference ===&lt;br /&gt;
&lt;br /&gt;
* [[BookRaffle]] - coordinate begging publishers for books to raffle off at the conference&lt;br /&gt;
* [http://inkdroid.org/c4l2009/attendees Get FOAFed] - add your FOAF profile to the network of c4l2009 attendees&lt;br /&gt;
* PreConferences:&lt;br /&gt;
** [[GIS_preconf_code4libcon2009]] - Open source GIS just like mom used to make&lt;br /&gt;
** [[LinkedData]] - A proposal for a linked-data code4lib2009 pre-conference&lt;br /&gt;
** [[LibX_Preconference]] - Proposal for a half-day pre-conference targeted at developers who wish to use the LibX 2.0 platform&lt;br /&gt;
** [http://code4lib.org/2009/oclc-precon OCLC Grid Services Preconference]&lt;br /&gt;
* [[RoommatesRidesEtc]] - Find roommates for Code4Lib 2009, share rides, etc.&lt;br /&gt;
* [[2009 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff&lt;br /&gt;
&lt;br /&gt;
=== Other workshops ===&lt;br /&gt;
* [http://barcamp.org/SearchCampDC SearchCampDC] - barcamp style event in DC with usual suspects from code4lib&lt;br /&gt;
* [[code4lib/elag2010]] - 1-day code4lib preconference at elag2010&lt;br /&gt;
&lt;br /&gt;
== Archived topics ==&lt;br /&gt;
&lt;br /&gt;
* [[Logo Design Process]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[AdminToDo]] - ideas and tasks for maintaining the Code4Lib sites&lt;/div&gt;</summary>
		<author><name>Elizabeth</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=How_To_Plan_A_Code4LibCon&amp;diff=11417</id>
		<title>How To Plan A Code4LibCon</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=How_To_Plan_A_Code4LibCon&amp;diff=11417"/>
				<updated>2012-02-13T21:47:00Z</updated>
		
		<summary type="html">&lt;p&gt;Elizabeth: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* Apply to be a host&lt;br /&gt;
&lt;br /&gt;
* Consider your action plan&lt;br /&gt;
** Identify your venues for both the conference and the hotel (if different). This is critical, as you'll want to get some cost estimates from each. When we hosted in Corvallis, the campus provided the conference space at a low cost, and this made running the conference much more affordable. When we hosted the conference in Portland, and held everything in a single hotel, we had to acquire 2x the amount of sponsorship than what appears to be normal.&lt;br /&gt;
** Speaking of sponsorship, I believe we average around 20k per year in sponsorships to help run the conference and keep the registration low. Factor this into your budget.&lt;br /&gt;
** Also, when you get cost estimates, don't forget to include food costs.&lt;br /&gt;
** WIRELESS: Always an issue it seems. If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you are looking at a hotel or other venue, make sure you talk to them about bandwidth and costs. IMHO, the two things that really need to be addressed each year are connectivity and food - everything else generally manages itself in terms of facilities.&lt;br /&gt;
*** make sure VPN is allowed&lt;br /&gt;
** See if your institution has a conference planning services group or something similar - if it does, then I highly recommend using them. They'll handle registration, budgeting, contracts, etc, and really make life easy.&lt;br /&gt;
** Regarding conference hotel, you'll want to make sure that there are blocks of rooms available - not usually too bad an issue in larger towns, but in some college or smaller towns, hotel rooms may be limited.&lt;br /&gt;
*** prepare the hotel for deluge via web when announcement is made about hotel registration available.  We overwhelmed the Seattle hotel in 2012&lt;br /&gt;
** Remember, your institution is taking the risk of covering any costs not covered by registrations and sponsorships. To this point, I believe the conference has always ended up in the black, but there is always a chance it won't in a given year. Drafting a rough budget before submitting a proposal is critical.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Get approved by the community&lt;br /&gt;
* Find a hotel, negotiate and sign a contract with them. [[Sample RFI]]&lt;br /&gt;
* Invite the community to help with &lt;br /&gt;
* Have a timeline&lt;br /&gt;
*Useful information from 2012 Code4Lib&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Important Public Resources ==&lt;br /&gt;
* Past calls for host sites: [http://code4lib.org/node/275 2010] - &lt;br /&gt;
* [http://dewey.library.nd.edu/mailing-lists/code4lib/ Code4Lib listserv]&lt;br /&gt;
* [http://groups.google.com/group/code4libcon Code4LibCon listserv]&lt;br /&gt;
* Sponsorship info (public)&lt;br /&gt;
* [http://code4lib.org/logo/ Logos]&lt;br /&gt;
&lt;br /&gt;
== Important Private Resources ==&lt;br /&gt;
* Code4LibCon-hostsite listserv&lt;br /&gt;
* Budgets from previous years&lt;br /&gt;
* Sponsorship info (private)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Gender Diversity &amp;amp; Minority Scholarship Committee==&lt;br /&gt;
The scholarship committee is a self-selected group that manages the gender diversity &amp;amp; minority scholarships. Separate groups handle AngelFund and Code4LibJapan scholarships.&lt;br /&gt;
&lt;br /&gt;
===Suggestions received===&lt;br /&gt;
* Send to a wider bunch of listservs, including for national orgs (ALA/SLA/MLA) &amp;amp; relevant sections? &amp;amp; student chapter&lt;br /&gt;
&lt;br /&gt;
===Process===&lt;br /&gt;
# Put out a call&lt;br /&gt;
# Receive and coordinate applications&lt;br /&gt;
# Distribute applications to the committee&lt;br /&gt;
# Select awardees&lt;br /&gt;
# Inform selected candidates&lt;br /&gt;
# Notify unsuccessful candidates&lt;br /&gt;
# Announce to Code4Lib main listserv and post on code4lib.org (e.g. http://code4lib.org/node/274 )&lt;br /&gt;
# Hosts work with awardees on reimbursement, registration, etc.&lt;br /&gt;
# Follow up with awardees after the conference -- receive report, ask for suggestions, etc.&lt;br /&gt;
&lt;br /&gt;
== Program Committtee==&lt;br /&gt;
The program committee is a self-selected group that manages talk proposals and other aspects of the program.&lt;br /&gt;
&lt;br /&gt;
(Add more info for the program committee here!)&lt;br /&gt;
&lt;br /&gt;
===Talk Acceptance Letter (samples)===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Dear &amp;lt;&amp;lt;first name last name&amp;gt;&amp;gt;,&lt;br /&gt;
 &lt;br /&gt;
On behalf of the Code4Lib Program Planning Committee, I am pleased to &lt;br /&gt;
notify you that your proposal, &amp;lt;&amp;lt;proposal title&amp;gt;&amp;gt; has been accepted for &lt;br /&gt;
the Code4Lib &amp;lt;&amp;lt;year&amp;gt;&amp;gt; in &amp;lt;&amp;lt;location&amp;gt;&amp;gt;.  Please reply to this message to &lt;br /&gt;
confirm your intention to present the approved session at the Conference.  &lt;br /&gt;
If at any time in the future you need to bow out or have any program &lt;br /&gt;
changes, please notify us immediately.  You will be sent a letter of &lt;br /&gt;
agreement soon.&lt;br /&gt;
 &lt;br /&gt;
The schedule for the conference is here:&lt;br /&gt;
&lt;br /&gt;
   http://code4lib.org/conference/2011/schedule&lt;br /&gt;
&lt;br /&gt;
You will have 20 minutes for your talk, including questions and answers.&lt;br /&gt;
A quick transition between speakers will be necessary.&lt;br /&gt;
 &lt;br /&gt;
It is very important that you focus your presentation on the more unique &lt;br /&gt;
and technical aspects of your topic whenever possible.  Although Code4Lib&lt;br /&gt;
attendees come from many different work environments, they attend Code4Lib &lt;br /&gt;
events for information technology education.&lt;br /&gt;
 &lt;br /&gt;
Experts like you are the heart of Code4Lib.  We really appreciate your contribution &lt;br /&gt;
and look forward to working with you.&lt;br /&gt;
  &lt;br /&gt;
Sincerely,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Talk Rejection Letter (sample)===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
I'm sorry, but your prepared talk proposal for the 2010 Code4Lib Conference in Asheville, NC did not receive enough votes to make it into the program. But here are a couple things you should know:&lt;br /&gt;
&lt;br /&gt;
- The field of presentations was very large (probably the largest we have had so far) and very strong, so you should not take it too hard.&lt;br /&gt;
- Please remember that there are many additional opportunities for participating, including lightning talks (open to anyone), breakout sessions (open to anyone to suggest and/or participate), and a special &amp;quot;Ask Anything&amp;quot; (or reply anything) open session. Also, the evening socializing opportunities are considered some of the most rewarding times of the event.&lt;br /&gt;
&lt;br /&gt;
Again, my condolences on not having your talk proposal accepted, but I hope we still see you in Asheville, NC in February.&lt;br /&gt;
Roy&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Sponsorship Committee ==&lt;br /&gt;
===Sample Sponsorship Request Letter===&lt;br /&gt;
As you know, Code4Lib is a group of library technologists, programmers, system administrators, web designers, and librarians.  Started in 2003, the group continues to grow--with a journal, a mailing list, and an active IRC channel. Since 2005, Code4Lib has sponsored an annual conference, which has attracted programmers and librarians from around the world.&lt;br /&gt;
&lt;br /&gt;
Topics at past conferences have included library information systems, new directions in library research, semantic web applications, and&lt;br /&gt;
information technology standards, among many others.  More details about the conference, including schedules of previous conferences, can be found from&lt;br /&gt;
http://www.code4lib.org/conference/&lt;br /&gt;
&lt;br /&gt;
Our &amp;lt;&amp;gt; conference will be held in &amp;lt;&amp;gt; from &amp;lt;&amp;gt;. Be a part of this library success story by underwriting the conference!&lt;br /&gt;
&lt;br /&gt;
We have several sponsorship levels:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;&amp;gt;&lt;br /&gt;
I look forward to hearing from you, and can be reached at &amp;lt;&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Best,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;&amp;gt;&lt;br /&gt;
http://code4lib.org/&lt;br /&gt;
&lt;br /&gt;
== Money==&lt;br /&gt;
* [[Conference_Financial_History_At_A_Glance]]&lt;br /&gt;
* private conlist has budget info &lt;br /&gt;
&lt;br /&gt;
== Shortly before the Conference ==&lt;br /&gt;
&lt;br /&gt;
=== Keynotes ===&lt;br /&gt;
# Contact speakers in advance to ask if they need anything, arrange airport pickup, etc&lt;br /&gt;
&lt;br /&gt;
=== Freenode IRC connection ===&lt;br /&gt;
Historically, conference attendees have had trouble maintaining persistent connections to the #code4lib IRC channel. We'd always assumed we were overwhelming the conference facility's Internet connection, but we were actually running into Freenode's IP-based connection limits. Freenode is supportive of the IRC-as-backchannel model, however, and they're happy to work with organizers to raise the connection limit.&lt;br /&gt;
&lt;br /&gt;
Contact the conference facility in advance and see if you can find out what your ''public IP address range'' will be during the conference. (If it starts with 10.*, 192.168.*, or 172.16.*, ask again -- those are &amp;quot;private&amp;quot; IP ranges used for connection sharing.)&lt;br /&gt;
&lt;br /&gt;
Once you have the IP address or range, send an email to [mailto:ilines@freenode.net ilines@freenode.net] containing a request to raise the connection limit. Include conference info, IP range(s), and the expected number of connections. For example:&lt;br /&gt;
&lt;br /&gt;
 To: ilines@freenode.net&lt;br /&gt;
 &lt;br /&gt;
 Hello,&lt;br /&gt;
 &lt;br /&gt;
 I'm helping plan the code4lib 2010 conference, taking place in Asheville, NC next week. &lt;br /&gt;
 Since our backchannel runs through #code4lib on Freenode, we're trying to plan ahead &lt;br /&gt;
 to avoid running up against the connection limit. Would it be possible to raise the cap &lt;br /&gt;
 for us during the conference? Details follow.&lt;br /&gt;
 &lt;br /&gt;
 Conference: code4lib 2010 &amp;lt; http://code4lib.org/conference/2010/ &amp;gt;&lt;br /&gt;
 Dates: February 22-26, 2010&lt;br /&gt;
 Attendees: 250&lt;br /&gt;
 Location: Renaissance Asheville Hotel, Asheville, NC&lt;br /&gt;
 IP Ranges: 12.21.216.106 and the entire 12.21.217.0/24 block&lt;br /&gt;
 &lt;br /&gt;
 We encourage in-channel participation, so we expect a high percentage of attendees to &lt;br /&gt;
 be connected at once. We'll also have two or three channel bots connected from the &lt;br /&gt;
 conference for the lobby monitors.&lt;br /&gt;
 &lt;br /&gt;
 Please let me know if you need any further information, and thanks very much for &lt;br /&gt;
 your help!&lt;br /&gt;
 &lt;br /&gt;
 Michael&lt;br /&gt;
&lt;br /&gt;
I received an automated reply with a ticket number almost instantly, but didn't hear back after that. I sent a quick followup early on the morning of the 22nd, and received a response (from a human) letting me know that it had been taken care of. (Follow-up, one year later: Same experience. Immediate automated reply, but with a need to follow up with Freenode staff in the #freenode channel to get the ticket resolved.)&lt;br /&gt;
&lt;br /&gt;
Additional support is available from the helpful volunteer Freenode staff in the #freenode channel.&lt;br /&gt;
&lt;br /&gt;
== At the Conference ==&lt;br /&gt;
&lt;br /&gt;
===Keynotes===&lt;br /&gt;
# Water at the podium&lt;br /&gt;
# Speaker gifts&lt;br /&gt;
# Dinner plans&lt;br /&gt;
&lt;br /&gt;
=== Timers ===&lt;br /&gt;
* Sit in the front of the room&lt;br /&gt;
* Have several people&lt;br /&gt;
* You may want to use an extra machine&lt;br /&gt;
* Here's what some of the software looks like: http://www.flickr.com/photos/schwartzray/4393891356/ (ask Ed Corrado for details)&lt;br /&gt;
* Dan Chudnov says the best free timer app for OSX is http://www.apimac.com/timer/&lt;br /&gt;
&lt;br /&gt;
=== Lightning Talks ===&lt;br /&gt;
* Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )&lt;br /&gt;
&lt;br /&gt;
===PreConf===&lt;br /&gt;
# make sure projector avail for each session&lt;br /&gt;
# whiteboards or reasonable facsimile thereof&lt;br /&gt;
# everyone wants a power outlet&lt;br /&gt;
&lt;br /&gt;
=== Conference ===&lt;br /&gt;
# power - everyone would like to plug in their laptop&lt;br /&gt;
&lt;br /&gt;
=== Video ===&lt;br /&gt;
# live stream is awesome&lt;br /&gt;
# join.me  ??&lt;br /&gt;
&lt;br /&gt;
=== Ask Anything===&lt;br /&gt;
* Need mics for people to line up at (image: http://www.flickr.com/photos/schwartzray/4393838640/ )&lt;br /&gt;
&lt;br /&gt;
===Book Raffle===&lt;br /&gt;
* (image: http://www.flickr.com/photos/schwartzray/4393619144/ with people for context: http://www.flickr.com/photos/schwartzray/4393623802/ and http://www.flickr.com/photos/schwartzray/4384550127/ ), better if there's a table&lt;br /&gt;
&lt;br /&gt;
=== Flipcharts ===&lt;br /&gt;
Flipcharts can be useful, but it's important to decide what to put on the wiki/website and what to put on a flipchart:&lt;br /&gt;
images: http://www.flickr.com/photos/schwartzray/4392998501/ http://www.flickr.com/photos/47860563@N05/4388430079/&lt;br /&gt;
&lt;br /&gt;
=== Hospitality Suite ===&lt;br /&gt;
# having a few people with room keys, any of whom might need to be available to open up or close down the room at the beginning or end of the evening&lt;br /&gt;
# making sure the mess left for cleaning staff is an appropriate mess&lt;br /&gt;
# making sure the noise made near other hotel guests is an appropriate noise&lt;br /&gt;
# having someone act as a point person to gather a gratuity for the housekeeping staff maintaining the suite&lt;br /&gt;
&lt;br /&gt;
== Suggested Timeline ==&lt;br /&gt;
* See [[C4L2010planning]] for an example &lt;br /&gt;
* Ideal to have program set before registration, including pre-conf&lt;br /&gt;
** also allows clarity for how many spots are avail for non-presenters&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2010]]&lt;br /&gt;
[[Category: Code4Lib2011]]&lt;br /&gt;
&lt;br /&gt;
===Calls for Hosting===&lt;br /&gt;
* 2008:&lt;br /&gt;
* 2009:&lt;br /&gt;
* 2010:&lt;br /&gt;
* 2011: March 5, 2010&lt;br /&gt;
* 2012:&lt;br /&gt;
* 2013:&lt;/div&gt;</summary>
		<author><name>Elizabeth</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_talks_proposals&amp;diff=9677</id>
		<title>2012 talks proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_talks_proposals&amp;diff=9677"/>
				<updated>2011-11-14T21:19:09Z</updated>
		
		<summary type="html">&lt;p&gt;Elizabeth: /* So... you think you want to Host a Code4Lib National Conference, do you? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Deadline for talk submission is ''Sunday, November 20''.&lt;br /&gt;
&lt;br /&gt;
Prepared talks are 20 minutes (including setup and questions), and focus on one or more of the following areas:&lt;br /&gt;
 * tools (some cool new software, software library or integration platform)&lt;br /&gt;
 * specs (how to get the most out of some protocols, or proposals for new ones)&lt;br /&gt;
 * challenges (one or more big problems we should collectively address)&lt;br /&gt;
&lt;br /&gt;
The community will vote on proposals using the criteria of:&lt;br /&gt;
 * usefulness&lt;br /&gt;
 * newness&lt;br /&gt;
 * geekiness&lt;br /&gt;
 * diversity of topics&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Talk Title: ==&lt;br /&gt;
 &lt;br /&gt;
* Speaker's name, affiliation, and email address&lt;br /&gt;
* Second speaker's name, affiliation, email address, if second speaker&lt;br /&gt;
&lt;br /&gt;
Abstract of no more than 500 words.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== VuFind 2.0: Why and How? ==&lt;br /&gt;
&lt;br /&gt;
* Demian Katz, Villanova University, demian.katz@villanova.edu&lt;br /&gt;
&lt;br /&gt;
A major new version of the VuFind discovery software is currently in development.  While VuFind 1.x remains extremely popular, some of its components are beginning to show their age.  VuFind 2.0 aims to retain all the strengths of the previous version of the software while making the architecture cleaner, more modern and more standards-based.  This presentation will examine the motivation behind the update, preview some of the new features to look forward to, and discuss the challenges of creating a developer-friendly open source package in PHP.&lt;br /&gt;
&lt;br /&gt;
== Open Source Software Registry ==&lt;br /&gt;
&lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]], LYRASIS, Peter.Murray@lyrasis.org&lt;br /&gt;
&lt;br /&gt;
LYRASIS is creating and shepherding a [[Registry_E-R_Diagram|registry of library open source software]] as part of its [http://www.lyrasis.org/News/Press-Releases/2011/LYRASIS-Receives-Grant-to-Support-Open-Source.aspx grant from the Mellon Foundation to support the adoption of open source software by libraries].  &lt;br /&gt;
The goal of the grant is to help libraries of all types determine if open source software is right for them, and what combination of software, hosting, training, and consulting works for their situation.  &lt;br /&gt;
The registry is intended to become a community exchange point and stimulant for growth of the library open source ecosystem by connecting libraries with projects, service providers, and events.&lt;br /&gt;
&lt;br /&gt;
The first half of this session will demonstrate the registry functions and describe how projects and providers can get involved.  &lt;br /&gt;
The second half of the session will be a brainstorming suggestion of how to expand the functionality and usefulness of the registry.&lt;br /&gt;
&lt;br /&gt;
== Property Graphs And TinkerPop Applications in Digital Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Brian Tingle, California Digital Library, brian.tingle.cdlib.org@gmail.com&lt;br /&gt;
&lt;br /&gt;
[http://www.tinkerpop.com/ TinkerPop] is an open source software development group focusing on technologies in the [http://en.wikipedia.org/wiki/Graph_database graph database] space.   &lt;br /&gt;
This talk will provide a general introduction to the TinkerPop Graph Stack and the [https://github.com/tinkerpop/gremlin/wiki/Defining-a-Property-Graph property graph model] is uses.  The introduction will include code examples and explanations of the property graph models used by the [http://socialarchive.iath.virginia.edu/ Social Networks in Archival Context] project and show how the historical social graph is exposed as a JSON/REST API implemented by a TinkerPop [https://github.com/tinkerpop/rexster rexster] [https://github.com/tinkerpop/rexster-kibbles Kibble] that contains the application's graph theory logic.  Other graph database applications possible with TinkerPop such as RDF support, and citation analysis will also be discussed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Security in Mind ==&lt;br /&gt;
 &lt;br /&gt;
* Erin Germ, United States Naval Academy, Nimitz Library, germ@usna.edu&lt;br /&gt;
&lt;br /&gt;
I would like to talk about security of library software.&lt;br /&gt;
&lt;br /&gt;
Over the Summer, I discovered a critical vulnerability in a vendor’s software that (verified) allowed me to assume any user’s identity for that site, (verified) switch to any user, and to (unverified, meaning I didn’t not perform this as I didn’t want to “hack” another library’s site) assume the role of any user for any other library who used this particular vendor's software.&lt;br /&gt;
&lt;br /&gt;
Within a 3 hour period, I discovered a 2 vulnerabilities: 1) minor one allowing me to access any backups from any library site, and 2) a critical vulnerability.  From start to finish, the examination, discovery in the vulnerability, and execution of a working exploit was done in less than 2 hours. The vulnerability was a result of poor cookie implementation. The exploit itself revolved around modifying the cookie, and then altering the browser’s permissions by assuming the role of another user.&lt;br /&gt;
&lt;br /&gt;
I do not intend on stating which vendor it was, but I will show how I was able to perform this. If needed, I can do further research and “investigation” into other vendor's software to see what I can “find”.&lt;br /&gt;
&lt;br /&gt;
''If selected, I will contact the vendor to inform them that I will present about this at C4L2012. I do not intend on releasing the name of the vendor.''&lt;br /&gt;
&lt;br /&gt;
== Search Engines and Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Greg Lindahl, blekko CTO, greg@blekko.com&lt;br /&gt;
&lt;br /&gt;
[https://blekko.com blekko] is a new web-scale search engine which enables end-users to create vertical search engines, through a feature called [http://help.blekko.com/index.php/category/slashtags/ slashtags]. Slashtags can contain as few as 1 or as many as tens of thousands of websites relevant to a narrow or broad topic. We have an extensive set of slashtags curated by a combination of volunteers and an in-house librarian team, or end-users can create and share their own. This talk will cover examples of slashtag creation relevant to libraries, and show how to embed this search into a library website, either using javascript or via our API.&lt;br /&gt;
&lt;br /&gt;
''We have exhibited at a couple of library conferences, and have received a lot of interest. blekko is a free service.''&lt;br /&gt;
&lt;br /&gt;
== Beyond code. Versioning data with Git and Mercurial. ==&lt;br /&gt;
&lt;br /&gt;
* Stephanie Collett, California Digital Library, stephanie.collett@ucop.edu&lt;br /&gt;
* Martin Haye, California Digital Library, martin.haye@ucop.edu&lt;br /&gt;
&lt;br /&gt;
Within a relatively short time since their introduction, [http://en.wikipedia.org/wiki/Distributed_Version_Control_System distributed version control systems] (DVCS) like [http://git-scm.com/ Git] and [http://mercurial.selenic.com/ Mercurial] have enjoyed widespread adoption for versioning code. It didn’t take long for the library development community to start discussing the potential for using DVCS within our applications and repositories to version data. After all, many of the features that have made some of these systems popular in the open source community to version code (e.g. lightweight, file-based, compressed, reliable) also make them compelling options for versioning data.  And why write an entire versioning system from scratch if a DVCS solution can be a drop-in solution? At the [http://www.cdlib.org/ California Digital Library] (CDL) we’ve started using Git and Mercurial in some of our applications to version data. This has proven effective in some situations and unworkable in others. This presentation will be a practical case study of CDL’s experiences with using DVCS to version data. We will explain how we’re incorporating Git and Mercurial in our applications, describe our successes and failures and consider the issues involved in repurposing these systems for data versioning.&lt;br /&gt;
&lt;br /&gt;
==Design for Developers==&lt;br /&gt;
&lt;br /&gt;
*Lisa Kurt, University of Nevada, Reno, lkurt@unr.edu&lt;br /&gt;
&lt;br /&gt;
Users expect good design. This talk will delve into what makes really great design, what to look for, and how to do it. Learn the principles of great design to take your applications, user interfaces, and projects to a higher level. With years of experience in graphic design and illustration, Lisa will discuss design principles, trends, process, tools, and development. Design examples will be from her own projects as well as a variety from industry. You’ll walk away with design knowledge that you can apply immediately to a variety of applications and a number of top notch go-to resources to get you up and running.&lt;br /&gt;
&lt;br /&gt;
==Building research applications with Mendeley==&lt;br /&gt;
&lt;br /&gt;
William Gunn, Mendeley william.gunn@mendeley.com (@mrgunn)&lt;br /&gt;
&lt;br /&gt;
This is partly a tool talk and partly a big idea one.&lt;br /&gt;
&lt;br /&gt;
Mendeley has built the world's largest open database of research and we've now begun to collect some interesting social metadata around the document metadata. I would like to share with the Code4Lib attendees information about using this resource to do things within your application that have previously been impossible for the library community, or in some cases impossible without expensive database subscriptions. One thing that's now possible is to augment catalog search by surfacing information about content usage, allowing people to not only find things matching a query, but popular things or things read by their colleagues. In addition to augmenting search, you can also use this information to augment discovery. Imagine an online exhibit of artifacts from a newly discovered dig not just linking to papers which discuss the artifact, but linking to really good interesting papers about the place and the people who made the artifacts. So the big idea is, &amp;quot;How will looking at the literature from a broader perspective than simple citation analysis change how research is done and communicated? How can we build tools that make this process easier and faster?&amp;quot; I can show some examples of applications that have been built using the Mendeley and PLoS APIs to begin to address this question, and I can also present results from Mendeley's developer challenge which shows what kinds of applications researchers are looking for, what kind of applications peope are building, and illustrates some interesting places where the two don't overlap.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Your UI can make or break the application (to the user, anyway)==&lt;br /&gt;
&lt;br /&gt;
* Robin Schaaf, University of Notre Dame, schaaf.4@nd.edu&lt;br /&gt;
&lt;br /&gt;
UI development is hard and too often ends up as an after-thought to computer programmers - if you were a CS major in college I'll bet you didn't have many, if any, design courses.  I'll talk about how to involve the users upfront with design and some common pitfalls of this approach.  I'll also make a case for why you should do the screen design before a single line of code is written.  And I'll throw in some ideas for increasing usability and attractiveness of your web applications.  I'd like to make a case study of the UI development of our open source ERMS.&lt;br /&gt;
&lt;br /&gt;
==Why Nobody Knows How Big The Library Really Is - Perspective of a Library Outside Turned Insider==&lt;br /&gt;
&lt;br /&gt;
* Patrick Berry, California State University, Chico, pberry@csuchico.edu&lt;br /&gt;
&lt;br /&gt;
In this talk I would like to bring the perspective of an &amp;quot;outsider&amp;quot; (although an avowed IT insider) to let you know that people don't understand the full scope of the library.  As we &amp;quot;rethink education&amp;quot;, it is incumbent upon us to help educate our institutions as to the scope of the library.  I will present some of the tactics I'm employing to help people outside, and in some cases inside, the library to understand our size and the value we bring to the institution.&lt;br /&gt;
&lt;br /&gt;
==Building a URL Management Module using the Concrete5 Package Architecture==&lt;br /&gt;
&lt;br /&gt;
* David Uspal, Villanova University, david.uspal@villanova.edu&lt;br /&gt;
&lt;br /&gt;
Keeping track of URLs utilized across a large website such as a university library, and keeping that content up to date for subject and course guides, can be a pain, and as an open source shop, we’d like to have open source solution for this issue.  For this talk, I intend to detail our solution to this issue by walking step-by-step through the building process for our URL Management module -- including why a new solution was necessary; a quick rundown of our CMS ([http://www.concrete5.org Concrete5], a CMS that isn’t Drupal); utilizing the Concrete5 APIs to isolate our solution from core code (to avoid complications caused by core updates); how our solution was integrated into the CMS architecture for easy installation; and our future plans on the project.&lt;br /&gt;
&lt;br /&gt;
==Building an NCIP connector to OpenSRF to facilitate resource sharing==&lt;br /&gt;
&lt;br /&gt;
* Jon Scott, Lyrasis, jon_scott@wsu.edu and Kyle Banerjee, Orbis Cascade Alliance, banerjek@uoregon.edu &lt;br /&gt;
&lt;br /&gt;
How do you reverse engineer any protocol to provide a new service? Humans (and worse yet, committees) often design verbose protocols built around use cases that don't line up current reality. To compound difficulties, the contents of protocol containers are not sufficiently defined/predictable and the only assistance available is sketchy documentation and kind individuals on the internet willing to share what they learned via trial by fire.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCIP (Niso Circulation Interchange Protocol) is an open standard that defines a set of messages to support exchange of circulation data between disparate circulation, interlibrary loan, and related applications -- widespread adoption of NCIP would eliminate huge amounts of duplicate processing in separate systems. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This presentation discusses how we learned enough about NCIP and OpenSRF from scratch to build an NCIP responder for Evergreen to facilitate resource sharing in a large consortium that relies on over 20 different ILSes.&lt;br /&gt;
&lt;br /&gt;
==Practical Agile: What's Working for Stanford, Blacklight, and Hydra==&lt;br /&gt;
&lt;br /&gt;
* Naomi Dushay, Stanford University Libraries, ndushay@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Agile development techniques can be difficult to adopt in the context of library software development.  Maybe your shop has only one or two developers, or you always have too many simultaneous projects.   Maybe your new projects can’t be started until 27 librarians reach consensus on the specifications.&lt;br /&gt;
&lt;br /&gt;
This talk will present successful Agile- and Silicon-Valley-inspired practices we’ve adopted at Stanford and/or in the Blacklight and Hydra projects.  We’ve targeted developer happiness as well as improved productivity with our recent changes.  User stories, dead week, sight lines … it’ll be a grab bag of goodies to bring back to your institution, including some ideas on how to adopt these practices without overt management buy in.&lt;br /&gt;
&lt;br /&gt;
==Quick and &amp;lt;strike&amp;gt;Dirty&amp;lt;/strike&amp;gt; Clean Usability: Rapid Prototyping with Bootstrap==&lt;br /&gt;
&lt;br /&gt;
* Shaun Ellis, Princeton University Libraries, shaune@princeton.edu &lt;br /&gt;
&lt;br /&gt;
''&amp;quot;The code itself is unimportant; a project is only as useful as people actually find it.&amp;quot;  - Linus Torvalds'' [http://bit.ly/p4uuyy]&lt;br /&gt;
&lt;br /&gt;
Usability has been a buzzword for some time now, but what is the process for making the the transition toward a better user experience, and hence, better designed library sites?  I will discuss the one facet of the process my team is using to redesign the Finding Aids site for Princeton University Libraries (still in development).  The approach involves the use of rapid prototyping, with Bootstrap [http://twitter.github.com/bootstrap/], to make sure we are on track with what users and stakeholders expect up front, and throughout the development process.&lt;br /&gt;
&lt;br /&gt;
Because Bootstrap allows for early and iterative user feedback, it is more effective than the historic Photoshop mockups/wireframe technique.  The Photoshop approach allows stakeholders to test the look, but not the feel -- and often leaves developers scratching their heads.  Being a CSS/HTML/Javascript grid-based framework, Bootstrap makes it easy for anyone with a bit of HTML/CSS chops to quickly build slick, interactive prototypes right in the browser -- tangible solutions which can be shared, evaluated, revised, and followed by all stakeholders (see Minimum Viable Products [http://en.wikipedia.org/wiki/Minimum_viable_product]).  Efficiency is multiplied because the customized prototypes can flow directly into production use, as is the goal with iterative development approaches, such as the Agile methodology.&lt;br /&gt;
&lt;br /&gt;
While Bootstrap is not the only framework that offers grid-based layout, development is expedited and usability is enhanced by Bootstraps use of of &amp;quot;prefabbed&amp;quot; conventional UI patterns, clean typography, and lean Javascript for interactivity.   Furthermore, out-of-the box Bootstrap comes in a fairly neutral palette, so focus remains on usability, and does not devolve into premature discussions of color or branding choices.  Finally, using Less can be a powerful tool in conjunction with Bootstrap, but is not necessary.  I will discuss the pros and cons, and offer examples for how to getting up and running with or without Less.&lt;br /&gt;
&lt;br /&gt;
==Search Engine Relevancy Tuning - A Static Rank Framework for Solr/Lucene==&lt;br /&gt;
&lt;br /&gt;
* Mike Schultz, Amazon.com (formerly Summon Search Architect) mike.schultz@gmail.com&lt;br /&gt;
&lt;br /&gt;
Solr/Lucene provides a lot of flexibility for adjusting relevancy scoring and improving search results.  Roughly speaking there are two areas of concern: Firstly, a 'dynamic rank' calculation that is a function of the user query and document text fields.  And secondly, a 'static rank' which is independent of the query and generally is a function of non-text document metadata.  In this talk I will outline an easily understood, hand-tunable static rank system with a minimal number of parameters.&lt;br /&gt;
&lt;br /&gt;
The obvious major feature of a search engine is to return results relevant to a user query.  Perhaps less obvious is the huge role query independent document features play in achieving that. Google's PageRank is an example of a static ranking of web pages based on links and other secret sauce.  In the Summon service, our 800 million documents have features like publication date, document type, citation count and Boolean features like the-article-is-peer-reviewed.  These fields aren't textual and remain 'static' from query to query, but need to influence a document's relevancy score.  In our search results, with all query related features being equal, we'd rather have more recent documents above older ones, Journals above Newspapers, and articles that are peer reviewed above those that are not. The static rank system I will describe achieves this and has the following features:&lt;br /&gt;
&lt;br /&gt;
* Query-time only calculation - nothing is baked into the index - with parameters adjustable at query time.&lt;br /&gt;
* The system is based on a signal metaphor where components are 'wired' together.  System components allow multiplexing, amplifying, summing, tunable band-pass filtering, string-to-value-mapping all with a bare minimum of parameters.&lt;br /&gt;
* An intuitive approach for mixing dynamic and static rank that is more effective than simple adding or multiplying.&lt;br /&gt;
* A way of equating disparate static metadata types that leads to understandable results ordering.&lt;br /&gt;
&lt;br /&gt;
==Submitting Digitized Book-like things to the Internet Archive==&lt;br /&gt;
&lt;br /&gt;
* Joel Richard, Smithsonian Institution Libraries, richardjm@si.edu&lt;br /&gt;
&lt;br /&gt;
The Smithsonian Libraries has submitted thousands of out-of-copyright items to the Internet Archive over the years. Specifically in relation to the Biodiversity Heritage Library, we have developed an in-house boutique scanning and upload process that became a learning experience in automated uploading to the Archive. As part of the software development, we created a whitepaper that details the combined learning experiences of the Smithsonian Libraries and the Missouri Botanical Garden. We will discuss some of the the contents of this whitepaper in the context of our scanning process and the manner in which we upload items to the Archive. &lt;br /&gt;
&lt;br /&gt;
Our talk will include a discussion of the types of files and their formats used by the Archive, processes that the Archive performs on uploaded items, ways of interacting and affecting those processes, potential pitfalls and solutions that you may encounter when uploading, and tools that the Archive provides to help monitor and manage your uploaded documents. &lt;br /&gt;
&lt;br /&gt;
Finally, we'll wrap up with a brief summary of how to use things that are on the Internet Archive in your own websites.&lt;br /&gt;
&lt;br /&gt;
== So... you think you want to Host a Code4Lib National Conference, do you? ==&lt;br /&gt;
&lt;br /&gt;
* Elizabeth Duell, Orbis Cascade Alliance, eduell@uoregon.edu&lt;br /&gt;
&lt;br /&gt;
Are you interested in hosting your own Code4Lib Conference? Do you know what it would take? What does BEO stands for? What does F&amp;amp;B Minimum mean? Who would you talk to for support/mentoring? There are so many things to think about: internet support, venue size, rooming blocks, contracts, dietary restrictions and coffee (can't forget the coffee!) just to name a few. Putting together a conference of any size can look daunting, so let's take the scary out of it and replace it with a can do attitude!&lt;br /&gt;
&lt;br /&gt;
Be a step ahead of the game by learning from the people behind the curtain. Ask questions and be given templates/ cheat sheets! &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Elizabeth</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_talks_proposals&amp;diff=9669</id>
		<title>2012 talks proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_talks_proposals&amp;diff=9669"/>
				<updated>2011-11-14T20:48:07Z</updated>
		
		<summary type="html">&lt;p&gt;Elizabeth: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Deadline for talk submission is ''Sunday, November 20''.&lt;br /&gt;
&lt;br /&gt;
Prepared talks are 20 minutes (including setup and questions), and focus on one or more of the following areas:&lt;br /&gt;
 * tools (some cool new software, software library or integration platform)&lt;br /&gt;
 * specs (how to get the most out of some protocols, or proposals for new ones)&lt;br /&gt;
 * challenges (one or more big problems we should collectively address)&lt;br /&gt;
&lt;br /&gt;
The community will vote on proposals using the criteria of:&lt;br /&gt;
 * usefulness&lt;br /&gt;
 * newness&lt;br /&gt;
 * geekiness&lt;br /&gt;
 * diversity of topics&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Talk Title: ==&lt;br /&gt;
 &lt;br /&gt;
* Speaker's name, affiliation, and email address&lt;br /&gt;
* Second speaker's name, affiliation, email address, if second speaker&lt;br /&gt;
&lt;br /&gt;
Abstract of no more than 500 words.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== VuFind 2.0: Why and How? ==&lt;br /&gt;
&lt;br /&gt;
* Demian Katz, Villanova University, demian.katz@villanova.edu&lt;br /&gt;
&lt;br /&gt;
A major new version of the VuFind discovery software is currently in development.  While VuFind 1.x remains extremely popular, some of its components are beginning to show their age.  VuFind 2.0 aims to retain all the strengths of the previous version of the software while making the architecture cleaner, more modern and more standards-based.  This presentation will examine the motivation behind the update, preview some of the new features to look forward to, and discuss the challenges of creating a developer-friendly open source package in PHP.&lt;br /&gt;
&lt;br /&gt;
== Open Source Software Registry ==&lt;br /&gt;
&lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]], LYRASIS, Peter.Murray@lyrasis.org&lt;br /&gt;
&lt;br /&gt;
LYRASIS is creating and shepherding a [[Registry_E-R_Diagram|registry of library open source software]] as part of its [http://www.lyrasis.org/News/Press-Releases/2011/LYRASIS-Receives-Grant-to-Support-Open-Source.aspx grant from the Mellon Foundation to support the adoption of open source software by libraries].  &lt;br /&gt;
The goal of the grant is to help libraries of all types determine if open source software is right for them, and what combination of software, hosting, training, and consulting works for their situation.  &lt;br /&gt;
The registry is intended to become a community exchange point and stimulant for growth of the library open source ecosystem by connecting libraries with projects, service providers, and events.&lt;br /&gt;
&lt;br /&gt;
The first half of this session will demonstrate the registry functions and describe how projects and providers can get involved.  &lt;br /&gt;
The second half of the session will be a brainstorming suggestion of how to expand the functionality and usefulness of the registry.&lt;br /&gt;
&lt;br /&gt;
== Property Graphs And TinkerPop Applications in Digital Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Brian Tingle, California Digital Library, brian.tingle.cdlib.org@gmail.com&lt;br /&gt;
&lt;br /&gt;
[http://www.tinkerpop.com/ TinkerPop] is an open source software development group focusing on technologies in the [http://en.wikipedia.org/wiki/Graph_database graph database] space.   &lt;br /&gt;
This talk will provide a general introduction to the TinkerPop Graph Stack and the [https://github.com/tinkerpop/gremlin/wiki/Defining-a-Property-Graph property graph model] is uses.  The introduction will include code examples and explanations of the property graph models used by the [http://socialarchive.iath.virginia.edu/ Social Networks in Archival Context] project and show how the historical social graph is exposed as a JSON/REST API implemented by a TinkerPop [https://github.com/tinkerpop/rexster rexster] [https://github.com/tinkerpop/rexster-kibbles Kibble] that contains the application's graph theory logic.  Other graph database applications possible with TinkerPop such as RDF support, and citation analysis will also be discussed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Security in Mind ==&lt;br /&gt;
 &lt;br /&gt;
* Erin Germ, United States Naval Academy, Nimitz Library, germ@usna.edu&lt;br /&gt;
&lt;br /&gt;
I would like to talk about security of library software.&lt;br /&gt;
&lt;br /&gt;
Over the Summer, I discovered a critical vulnerability in a vendor’s software that (verified) allowed me to assume any user’s identity for that site, (verified) switch to any user, and to (unverified, meaning I didn’t not perform this as I didn’t want to “hack” another library’s site) assume the role of any user for any other library who used this particular vendor's software.&lt;br /&gt;
&lt;br /&gt;
Within a 3 hour period, I discovered a 2 vulnerabilities: 1) minor one allowing me to access any backups from any library site, and 2) a critical vulnerability.  From start to finish, the examination, discovery in the vulnerability, and execution of a working exploit was done in less than 2 hours. The vulnerability was a result of poor cookie implementation. The exploit itself revolved around modifying the cookie, and then altering the browser’s permissions by assuming the role of another user.&lt;br /&gt;
&lt;br /&gt;
I do not intend on stating which vendor it was, but I will show how I was able to perform this. If needed, I can do further research and “investigation” into other vendor's software to see what I can “find”.&lt;br /&gt;
&lt;br /&gt;
''If selected, I will contact the vendor to inform them that I will present about this at C4L2012. I do not intend on releasing the name of the vendor.''&lt;br /&gt;
&lt;br /&gt;
== Search Engines and Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Greg Lindahl, blekko CTO, greg@blekko.com&lt;br /&gt;
&lt;br /&gt;
[https://blekko.com blekko] is a new web-scale search engine which enables end-users to create vertical search engines, through a feature called [http://help.blekko.com/index.php/category/slashtags/ slashtags]. Slashtags can contain as few as 1 or as many as tens of thousands of websites relevant to a narrow or broad topic. We have an extensive set of slashtags curated by a combination of volunteers and an in-house librarian team, or end-users can create and share their own. This talk will cover examples of slashtag creation relevant to libraries, and show how to embed this search into a library website, either using javascript or via our API.&lt;br /&gt;
&lt;br /&gt;
''We have exhibited at a couple of library conferences, and have received a lot of interest. blekko is a free service.''&lt;br /&gt;
&lt;br /&gt;
== Beyond code. Versioning data with Git and Mercurial. ==&lt;br /&gt;
&lt;br /&gt;
* Stephanie Collett, California Digital Library, stephanie.collett@ucop.edu&lt;br /&gt;
* Martin Haye, California Digital Library, martin.haye@ucop.edu&lt;br /&gt;
&lt;br /&gt;
Within a relatively short time since their introduction, [http://en.wikipedia.org/wiki/Distributed_Version_Control_System distributed version control systems] (DVCS) like [http://git-scm.com/ Git] and [http://mercurial.selenic.com/ Mercurial] have enjoyed widespread adoption for versioning code. It didn’t take long for the library development community to start discussing the potential for using DVCS within our applications and repositories to version data. After all, many of the features that have made some of these systems popular in the open source community to version code (e.g. lightweight, file-based, compressed, reliable) also make them compelling options for versioning data.  And why write an entire versioning system from scratch if a DVCS solution can be a drop-in solution? At the [http://www.cdlib.org/ California Digital Library] (CDL) we’ve started using Git and Mercurial in some of our applications to version data. This has proven effective in some situations and unworkable in others. This presentation will be a practical case study of CDL’s experiences with using DVCS to version data. We will explain how we’re incorporating Git and Mercurial in our applications, describe our successes and failures and consider the issues involved in repurposing these systems for data versioning.&lt;br /&gt;
&lt;br /&gt;
==Design for Developers==&lt;br /&gt;
&lt;br /&gt;
*Lisa Kurt, University of Nevada, Reno, lkurt@unr.edu&lt;br /&gt;
&lt;br /&gt;
Users expect good design. This talk will delve into what makes really great design, what to look for, and how to do it. Learn the principles of great design to take your applications, user interfaces, and projects to a higher level. With years of experience in graphic design and illustration, Lisa will discuss design principles, trends, process, tools, and development. Design examples will be from her own projects as well as a variety from industry. You’ll walk away with design knowledge that you can apply immediately to a variety of applications and a number of top notch go-to resources to get you up and running.&lt;br /&gt;
&lt;br /&gt;
==Building research applications with Mendeley==&lt;br /&gt;
&lt;br /&gt;
William Gunn, Mendeley william.gunn@mendeley.com (@mrgunn)&lt;br /&gt;
&lt;br /&gt;
This is partly a tool talk and partly a big idea one.&lt;br /&gt;
&lt;br /&gt;
Mendeley has built the world's largest open database of research and we've now begun to collect some interesting social metadata around the document metadata. I would like to share with the Code4Lib attendees information about using this resource to do things within your application that have previously been impossible for the library community, or in some cases impossible without expensive database subscriptions. One thing that's now possible is to augment catalog search by surfacing information about content usage, allowing people to not only find things matching a query, but popular things or things read by their colleagues. In addition to augmenting search, you can also use this information to augment discovery. Imagine an online exhibit of artifacts from a newly discovered dig not just linking to papers which discuss the artifact, but linking to really good interesting papers about the place and the people who made the artifacts. So the big idea is, &amp;quot;How will looking at the literature from a broader perspective than simple citation analysis change how research is done and communicated? How can we build tools that make this process easier and faster?&amp;quot; I can show some examples of applications that have been built using the Mendeley and PLoS APIs to begin to address this question, and I can also present results from Mendeley's developer challenge which shows what kinds of applications researchers are looking for, what kind of applications peope are building, and illustrates some interesting places where the two don't overlap.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Your UI can make or break the application (to the user, anyway)==&lt;br /&gt;
&lt;br /&gt;
* Robin Schaaf, University of Notre Dame, schaaf.4@nd.edu&lt;br /&gt;
&lt;br /&gt;
UI development is hard and too often ends up as an after-thought to computer programmers - if you were a CS major in college I'll bet you didn't have many, if any, design courses.  I'll talk about how to involve the users upfront with design and some common pitfalls of this approach.  I'll also make a case for why you should do the screen design before a single line of code is written.  And I'll throw in some ideas for increasing usability and attractiveness of your web applications.  I'd like to make a case study of the UI development of our open source ERMS.&lt;br /&gt;
&lt;br /&gt;
==Why Nobody Knows How Big The Library Really Is - Perspective of a Library Outside Turned Insider==&lt;br /&gt;
&lt;br /&gt;
* Patrick Berry, California State University, Chico, pberry@csuchico.edu&lt;br /&gt;
&lt;br /&gt;
In this talk I would like to bring the perspective of an &amp;quot;outsider&amp;quot; (although an avowed IT insider) to let you know that people don't understand the full scope of the library.  As we &amp;quot;rethink education&amp;quot;, it is incumbent upon us to help educate our institutions as to the scope of the library.  I will present some of the tactics I'm employing to help people outside, and in some cases inside, the library to understand our size and the value we bring to the institution.&lt;br /&gt;
&lt;br /&gt;
==Building a URL Management Module using the Concrete5 Package Architecture==&lt;br /&gt;
&lt;br /&gt;
* David Uspal, Villanova University, david.uspal@villanova.edu&lt;br /&gt;
&lt;br /&gt;
Keeping track of URLs utilized across a large website such as a university library, and keeping that content up to date for subject and course guides, can be a pain, and as an open source shop, we’d like to have open source solution for this issue.  For this talk, I intend to detail our solution to this issue by walking step-by-step through the building process for our URL Management module -- including why a new solution was necessary; a quick rundown of our CMS ([http://www.concrete5.org Concrete5], a CMS that isn’t Drupal); utilizing the Concrete5 APIs to isolate our solution from core code (to avoid complications caused by core updates); how our solution was integrated into the CMS architecture for easy installation; and our future plans on the project.&lt;br /&gt;
&lt;br /&gt;
==Building an NCIP connector to OpenSRF to facilitate resource sharing==&lt;br /&gt;
&lt;br /&gt;
* Jon Scott, Lyrasis, jon_scott@wsu.edu and Kyle Banerjee, Orbis Cascade Alliance, banerjek@uoregon.edu &lt;br /&gt;
&lt;br /&gt;
How do you reverse engineer any protocol to provide a new service? Humans (and worse yet, committees) often design verbose protocols built around use cases that don't line up current reality. To compound difficulties, the contents of protocol containers are not sufficiently defined/predictable and the only assistance available is sketchy documentation and kind individuals on the internet willing to share what they learned via trial by fire.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCIP (Niso Circulation Interchange Protocol) is an open standard that defines a set of messages to support exchange of circulation data between disparate circulation, interlibrary loan, and related applications -- widespread adoption of NCIP would eliminate huge amounts of duplicate processing in separate systems. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This presentation discusses how we learned enough about NCIP and OpenSRF from scratch to build an NCIP responder for Evergreen to facilitate resource sharing in a large consortium that relies on over 20 different ILSes.&lt;br /&gt;
&lt;br /&gt;
==Practical Agile: What's Working for Stanford, Blacklight, and Hydra==&lt;br /&gt;
&lt;br /&gt;
* Naomi Dushay, Stanford University Libraries, ndushay@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Agile development techniques can be difficult to adopt in the context of library software development.  Maybe your shop has only one or two developers, or you always have too many simultaneous projects.   Maybe your new projects can’t be started until 27 librarians reach consensus on the specifications.&lt;br /&gt;
&lt;br /&gt;
This talk will present successful Agile- and Silicon-Valley-inspired practices we’ve adopted at Stanford and/or in the Blacklight and Hydra projects.  We’ve targeted developer happiness as well as improved productivity with our recent changes.  User stories, dead week, sight lines … it’ll be a grab bag of goodies to bring back to your institution, including some ideas on how to adopt these practices without overt management buy in.&lt;br /&gt;
&lt;br /&gt;
==Quick and &amp;lt;strike&amp;gt;Dirty&amp;lt;/strike&amp;gt; Clean Usability: Rapid Prototyping with Bootstrap==&lt;br /&gt;
&lt;br /&gt;
* Shaun Ellis, Princeton University Libraries, shaune@princeton.edu &lt;br /&gt;
&lt;br /&gt;
''&amp;quot;The code itself is unimportant; a project is only as useful as people actually find it.&amp;quot;  - Linus Torvalds'' [http://bit.ly/p4uuyy]&lt;br /&gt;
&lt;br /&gt;
Usability has been a buzzword for some time now, but what is the process for making the the transition toward a better user experience, and hence, better designed library sites?  I will discuss the one facet of the process my team is using to redesign the Finding Aids site for Princeton University Libraries (still in development).  The approach involves the use of rapid prototyping, with Bootstrap [http://twitter.github.com/bootstrap/], to make sure we are on track with what users and stakeholders expect up front, and throughout the development process.&lt;br /&gt;
&lt;br /&gt;
Because Bootstrap allows for early and iterative user feedback, it is more effective than the historic Photoshop mockups/wireframe technique.  The Photoshop approach allows stakeholders to test the look, but not the feel -- and often leaves developers scratching their heads.  Being a CSS/HTML/Javascript grid-based framework, Bootstrap makes it easy for anyone with a bit of HTML/CSS chops to quickly build slick, interactive prototypes right in the browser -- tangible solutions which can be shared, evaluated, revised, and followed by all stakeholders (see Minimum Viable Products [http://en.wikipedia.org/wiki/Minimum_viable_product]).  Efficiency is multiplied because the customized prototypes can flow directly into production use, as is the goal with iterative development approaches, such as the Agile methodology.&lt;br /&gt;
&lt;br /&gt;
While Bootstrap is not the only framework that offers grid-based layout, development is expedited and usability is enhanced by Bootstraps use of of &amp;quot;prefabbed&amp;quot; conventional UI patterns, clean typography, and lean Javascript for interactivity.   Furthermore, out-of-the box Bootstrap comes in a fairly neutral palette, so focus remains on usability, and does not devolve into premature discussions of color or branding choices.  Finally, using Less can be a powerful tool in conjunction with Bootstrap, but is not necessary.  I will discuss the pros and cons, and offer examples for how to getting up and running with or without Less.&lt;br /&gt;
&lt;br /&gt;
==Search Engine Relevancy Tuning - A Static Rank Framework for Solr/Lucene==&lt;br /&gt;
&lt;br /&gt;
* Mike Schultz, Amazon.com (formerly Summon Search Architect) mike.schultz@gmail.com&lt;br /&gt;
&lt;br /&gt;
Solr/Lucene provides a lot of flexibility for adjusting relevancy scoring and improving search results.  Roughly speaking there are two areas of concern: Firstly, a 'dynamic rank' calculation that is a function of the user query and document text fields.  And secondly, a 'static rank' which is independent of the query and generally is a function of non-text document metadata.  In this talk I will outline an easily understood, hand-tunable static rank system with a minimal number of parameters.&lt;br /&gt;
&lt;br /&gt;
The obvious major feature of a search engine is to return results relevant to a user query.  Perhaps less obvious is the huge role query independent document features play in achieving that. Google's PageRank is an example of a static ranking of web pages based on links and other secret sauce.  In the Summon service, our 800 million documents have features like publication date, document type, citation count and Boolean features like the-article-is-peer-reviewed.  These fields aren't textual and remain 'static' from query to query, but need to influence a document's relevancy score.  In our search results, with all query related features being equal, we'd rather have more recent documents above older ones, Journals above Newspapers, and articles that are peer reviewed above those that are not. The static rank system I will describe achieves this and has the following features:&lt;br /&gt;
&lt;br /&gt;
* Query-time only calculation - nothing is baked into the index - with parameters adjustable at query time.&lt;br /&gt;
* The system is based on a signal metaphor where components are 'wired' together.  System components allow multiplexing, amplifying, summing, tunable band-pass filtering, string-to-value-mapping all with a bare minimum of parameters.&lt;br /&gt;
* An intuitive approach for mixing dynamic and static rank that is more effective than simple adding or multiplying.&lt;br /&gt;
* A way of equating disparate static metadata types that leads to understandable results ordering.&lt;br /&gt;
&lt;br /&gt;
==Submitting Digitized Book-like things to the Internet Archive==&lt;br /&gt;
&lt;br /&gt;
* Joel Richard, Smithsonian Institution Libraries, richardjm@si.edu&lt;br /&gt;
&lt;br /&gt;
The Smithsonian Libraries has submitted thousands of out-of-copyright items to the Internet Archive over the years. Specifically in relation to the Biodiversity Heritage Library, we have developed an in-house boutique scanning and upload process that became a learning experience in automated uploading to the Archive. As part of the software development, we created a whitepaper that details the combined learning experiences of the Smithsonian Libraries and the Missouri Botanical Garden. We will discuss some of the the contents of this whitepaper in the context of our scanning process and the manner in which we upload items to the Archive. &lt;br /&gt;
&lt;br /&gt;
Our talk will include a discussion of the types of files and their formats used by the Archive, processes that the Archive performs on uploaded items, ways of interacting and affecting those processes, potential pitfalls and solutions that you may encounter when uploading, and tools that the Archive provides to help monitor and manage your uploaded documents. &lt;br /&gt;
&lt;br /&gt;
Finally, we'll wrap up with a brief summary of how to use things that are on the Internet Archive in your own websites.&lt;br /&gt;
&lt;br /&gt;
== So... you think you want to Host a Code4Lib National Conference, do you? ==&lt;br /&gt;
&lt;br /&gt;
* Elizabeth Duell, Orbis Cascade Alliance, eduell@uoregon.edu&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Elizabeth</name></author>	</entry>

	</feed>