https://wiki.code4lib.org/api.php?action=feedcontributions&user=No+reply&feedformat=atomCode4Lib - User contributions [en]2024-03-28T15:24:57ZUser contributionsMediaWiki 1.26.2https://wiki.code4lib.org/index.php?title=2015_Lightning_Talks&diff=427272015 Lightning Talks2015-02-10T20:35:35Z<p>No reply: /* Tuesday 14:30 PM to 15:30 PM */ Add official Tuesday lineup</p>
<hr />
<div><br />
==Lightning Talks==<br />
<big>'''Lightning talk signup will begin after the opening session, on a (physical) sign up board. As spots fill, we'll add them here for convenient reference.'''</big><br />
<br />
==Tuesday 14:30 PM to 15:30 PM==<br />
# Automated Entity Extractions to Relate Library Resources - Kyle Banerjee<br />
# ResCarta Recap<br />
# Information Design Thoughts - Dre<br />
# Vufind & Worldcat Discovery API - Karen Coombs<br />
# Video Accessibility - Jason Ronallo<br />
# ILS and Payment Systems - Josh Weisman<br />
# Fedora 4 Migration - Adam Wead<br />
# LDPath - Chris Beer<br />
# Self-Deposit of Scientific Data - Darren Hardy<br />
# Bread - Mx. Matienzo<br />
<br />
==Wednesday 11:00 AM to 12:00 PM==<br />
# <br />
#<br />
#<br />
#<br />
#<br />
#<br />
#<br />
#<br />
#<br />
#<br />
<br />
==Thursday 10:15 AM to 11:00 AM==<br />
<br />
#<br />
#<br />
#<br />
#<br />
#<br />
#<br />
#<br />
#<br />
#<br />
<br />
[[Category:Code4Lib2015]]</div>No replyhttps://wiki.code4lib.org/index.php?title=2015_Lightning_Talks&diff=426092015 Lightning Talks2015-02-03T21:20:34Z<p>No reply: With apologies to the people who signed up already.</p>
<hr />
<div>==Lightning Talks==<br />
<br />
Lightning talk signup will begin after the opening session, on a (physical) sign up board. As spots fill, we'll add them here for convenient reference.<br />
<br />
==Tuesday 14:30 PM to 15:30 PM==<br />
# <br />
# <br />
#<br />
#<br />
#<br />
#<br />
#<br />
#<br />
#<br />
#<br />
<br />
<br />
==Wednesday 11:00 AM to 12:00 PM==<br />
# <br />
#<br />
#<br />
#<br />
#<br />
#<br />
#<br />
#<br />
#<br />
#<br />
<br />
==Thursday 10:15 AM to 11:00 AM==<br />
<br />
#<br />
#<br />
#<br />
#<br />
#<br />
#<br />
#<br />
#<br />
#<br />
<br />
[[Category:Code4Lib2015]]</div>No replyhttps://wiki.code4lib.org/index.php?title=Template:Conference&diff=42568Template:Conference2015-01-31T20:37:30Z<p>No reply: </p>
<hr />
<div><noinclude><br />
This is the "Conference" template.<br />
It should be called in the following format:<br />
<pre><br />
{{Conference<br />
|Logo=File:xyz<br />
|URL=<br />
|Start Date=<br />
|End Date=<br />
|Location=<br />
|Coordinates=<br />
|Organizers=<br />
|Contact=<br />
}}<br />
</pre><br />
Edit the page to see the template text.<br />
</noinclude><includeonly>{| style="width: 30em; font-size: 90%; border: 1px solid #aaaaaa; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: right; text-align:left;"<br />
|-<br />
| {{#invoke:InfoboxImage|InfoboxImage|image={{{image|{{{Logo|}}}}}}|sizedefault=frameless|upright=.65|suppressplaceholder=yes}}<br />
|-<br />
! URL<br />
| [[sameAs::{{{URL|}}}]] <br />
|-<br />
! Dates<br />
| [[begins::{{{Start Date|}}}]] - [[ends::{{{End Date|}}}]]<br />
|-<br />
! Location<br />
| [[locationName::{{{Location|}}}]]<br />
|-<br />
! Contact<br />
| {{{Organizers|}}} <br />
{{{Contact|}}}<br />
|}<br />
<br />
[[Category:Conferences]]<br />
</includeonly></div>No replyhttps://wiki.code4lib.org/index.php?title=Template:Conference&diff=42567Template:Conference2015-01-31T20:36:59Z<p>No reply: </p>
<hr />
<div><noinclude><br />
This is the "Conference" template.<br />
It should be called in the following format:<br />
<pre><br />
{{Conference<br />
|Logo=File:xyz<br />
|URL=<br />
|Start Date=<br />
|End Date=<br />
|Location=<br />
|Coordinates=<br />
|Organizers=<br />
|Contact=<br />
}}<br />
</pre><br />
Edit the page to see the template text.<br />
</noinclude><includeonly>{| style="width: 30em; font-size: 90%; border: 1px solid #aaaaaa; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: right; text-align:left;"<br />
|-<br />
| {{#invoke:InfoboxImage|InfoboxImage|image={{{image|{{{Logo|}}}}}}|sizedefault=frameless|upright=.65|suppressplaceholder=yes}}<br />
|-<br />
! URL<br />
| [[sameAs::{{{URL|}}}]] <br />
|-<br />
! Dates<br />
| [[begins::{{{Start Date|}}}]] - [[ends::{{{End Date|}}}]]<br />
|-<br />
! Location<br />
| [[locationName::{{{Location|}}}]]<br />
|-<br />
! Contact<br />
| {{{Organizers|}}} <br />
| {{{Contact|}}}<br />
|}<br />
<br />
[[Category:Conferences]]<br />
</includeonly></div>No replyhttps://wiki.code4lib.org/index.php?title=Template:Conference&diff=42566Template:Conference2015-01-31T20:35:36Z<p>No reply: </p>
<hr />
<div><noinclude><br />
This is the "Conference" template.<br />
It should be called in the following format:<br />
<pre><br />
{{Conference<br />
|Logo=File:xyz<br />
|URL=<br />
|Start Date=<br />
|End Date=<br />
|Location=<br />
|Coordinates=<br />
|Organizers=<br />
|Contact=<br />
}}<br />
</pre><br />
Edit the page to see the template text.<br />
</noinclude><includeonly>{| style="width: 30em; font-size: 90%; border: 1px solid #aaaaaa; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: right; text-align:left;"<br />
|-<br />
| {{#invoke:InfoboxImage|InfoboxImage|image={{{image|{{{Logo|}}}}}}|sizedefault=frameless|upright=.65|suppressplaceholder=yes}}<br />
|-<br />
! URL<br />
| [[sameAs::{{{URL|}}}]] <br />
|-<br />
! Dates<br />
| [[begins::{{{Start Date|}}}]] - [[ends::{{{End Date|}}}]]<br />
|-<br />
! Location<br />
| [[locationName::{{{Location|}}}]]<br />
|-<br />
! Contact<br />
| {{{Organizers|}}} - {{{Contact|}}}<br />
|}<br />
<br />
[[Category:Conferences]]<br />
</includeonly></div>No replyhttps://wiki.code4lib.org/index.php?title=Template:Conference&diff=42565Template:Conference2015-01-31T20:35:07Z<p>No reply: </p>
<hr />
<div><noinclude><br />
This is the "Conference" template.<br />
It should be called in the following format:<br />
<pre><br />
{{Conference<br />
|Logo=File:xyz<br />
|URL=<br />
|Start Date=<br />
|End Date=<br />
|Location=<br />
|Coordinates=<br />
|Organizers=<br />
|Contact=<br />
}}<br />
</pre><br />
Edit the page to see the template text.<br />
</noinclude><includeonly>{| style="width: 30em; font-size: 90%; border: 1px solid #aaaaaa; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: right; text-align:left;"<br />
|-<br />
| {{#invoke:InfoboxImage|InfoboxImage|image={{{image|{{{Logo|}}}}}}|sizedefault=frameless|upright=.65|suppressplaceholder=yes}}<br />
|-<br />
! URL<br />
| [[sameAs::{{{URL|}}}]] <br />
|-<br />
! Dates<br />
| [[begins::{{{Start Date|}}}]] - [[ends::{{{End Date|}}}]]<br />
|-<br />
! Location<br />
| [[locationName::{{{Location|}}}]]<br />
|-<br />
! Contact<br />
| organizers::{{{Organizers|}}} contact::{{{Contact|}}}<br />
|}<br />
<br />
[[Category:Conferences]]<br />
</includeonly></div>No replyhttps://wiki.code4lib.org/index.php?title=Template:Conference&diff=42564Template:Conference2015-01-31T20:33:33Z<p>No reply: </p>
<hr />
<div><noinclude><br />
This is the "Conference" template.<br />
It should be called in the following format:<br />
<pre><br />
{{Conference<br />
|Logo=File:xyz<br />
|URL=<br />
|Start Date=<br />
|End Date=<br />
|Location=<br />
|Coordinates=<br />
|Organizers=<br />
|Contact=<br />
}}<br />
</pre><br />
Edit the page to see the template text.<br />
</noinclude><includeonly>{| style="width: 30em; font-size: 90%; border: 1px solid #aaaaaa; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: right; text-align:left;"<br />
|-<br />
| {{#invoke:InfoboxImage|InfoboxImage|image={{{image|{{{Logo|}}}}}}|sizedefault=frameless|upright=.65|suppressplaceholder=yes}}<br />
|-<br />
! URL<br />
| [[sameAs::{{{URL|}}}]] <br />
|-<br />
! Dates<br />
| [[begins::{{{Start Date|}}}]] - [[ends::{{{End Date|}}}]]<br />
|-<br />
! Location<br />
| [[locationName::{{{Location|}}}]]<br />
|-<br />
! Contact<br />
| [[organizers::{{{Organizers|}}}]] [[contact::{{{Contact|}}}]]<br />
|}<br />
<br />
[[Category:Conferences]]<br />
</includeonly></div>No replyhttps://wiki.code4lib.org/index.php?title=Template:Conference&diff=42563Template:Conference2015-01-31T20:32:41Z<p>No reply: Add Organizer info to infobox</p>
<hr />
<div><noinclude><br />
This is the "Conference" template.<br />
It should be called in the following format:<br />
<pre><br />
{{Conference<br />
|Logo=File:xyz<br />
|URL=<br />
|Start Date=<br />
|End Date=<br />
|Location=<br />
|Coordinates=<br />
|Organizers=<br />
|Contact=<br />
}}<br />
</pre><br />
Edit the page to see the template text.<br />
</noinclude><includeonly>{| style="width: 30em; font-size: 90%; border: 1px solid #aaaaaa; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: right; text-align:left;"<br />
|-<br />
| {{#invoke:InfoboxImage|InfoboxImage|image={{{image|{{{Logo|}}}}}}|sizedefault=frameless|upright=.65|suppressplaceholder=yes}}<br />
|-<br />
! URL<br />
| [[sameAs::{{{URL|}}}]] <br />
|-<br />
! Dates<br />
| [[begins::{{{Start Date|}}}]] - [[ends::{{{End Date|}}}]]<br />
|-<br />
! Location<br />
| [[locationName::{{{Location|}}}]]<br />
! Contact<br />
| [[organizers::{{{Organizers|}}}]] [[contact::{{{Contact|}}}]]<br />
|}<br />
<br />
[[Category:Conferences]]<br />
</includeonly></div>No replyhttps://wiki.code4lib.org/index.php?title=Category:Code4Lib2015&diff=42562Category:Code4Lib20152015-01-31T20:27:24Z<p>No reply: Add Organizer info to infobox</p>
<hr />
<div>{{Conference<br />
|URL=http://code4lib.org/conference/2015<br />
|Start Date=February 9, 2015<br />
|End Date=February 12, 2015<br />
|Location=Portland, OR<br />
|Coordinates=45° 31' 12"N 122° 40' 55"W<br />
|Organizers=Evviva Weinraub Lajoie, Tom Johnson<br />
|Contact=360-961-7721<br />
}}<br />
*[[2015 Conference Committees]]<br />
*[[2015 Hosting Proposals]]<br />
*[[2015 Prepared Talk Proposals]]<br />
*[[2015 Preconference Proposals]]<br />
*[[2015 Invited Speakers Nominations]]<br />
*[[2015 T-Shirt Design Proposals]]<br />
**[[2015 Sponsor Logos for T-Shirt]]<br />
*[[2015 Room and Ride Share]]<br />
*[[2015 Social Activities]]<br />
*[[2015 Video Recording & Streaming]]<br />
*[[2015 During the Conference Volunteers]]<br />
*[[2015 Lessons Learned]]<br />
<br />
[[Category:Conferences]]</div>No replyhttps://wiki.code4lib.org/index.php?title=2015_Lessons_Learned&diff=425612015 Lessons Learned2015-01-31T19:15:50Z<p>No reply: /* Program & Keynotes */</p>
<hr />
<div>== Conference Planning ==<br />
<br />
=== Program & Keynotes ===<br />
<br />
* Set consistent proposal opening/closing, voting opening/closing dates and times. At the very least, we should be able to agree across keynote/presentation/tshirt committees on a common time to close submissions (this year, we had closing times at 5pm, 8pm, and 11:59pm PT).<br />
<br />
=== Child Care ===</div>No replyhttps://wiki.code4lib.org/index.php?title=2015_Lessons_Learned&diff=425602015 Lessons Learned2015-01-31T19:15:17Z<p>No reply: /* Conference Planning */</p>
<hr />
<div>== Conference Planning ==<br />
<br />
=== Program & Keynotes ===<br />
<br />
* Set consistent proposal opening/closing, voting opening/closing dates and times. At the very least, we should be able to agree across keynote/presentation/tshirt committees on a common time to close submissions (this year, we had closing times at 5pm, 8pm, and 11:59pm PT).<br />
<br />
<br />
=== Child Care ===</div>No replyhttps://wiki.code4lib.org/index.php?title=2015_Craft_Drinkup&diff=424722015 Craft Drinkup2015-01-22T04:25:33Z<p>No reply: /* Signup */</p>
<hr />
<div>When: Tuesday, February 10th - 7pm - 10pm (ish)<br />
<br />
Where: eBay Offices - 1400 SW 5th Ave, Portland, OR 97201<br />
<br />
The Craft Brew Drinkup at Code4lib 2015 is all about sharing and enjoying good beer, soda, and other drinks with fellow conference attendees. The idea is to bring bottles of your favorite beers or non-alcoholic drinks.<br />
<br />
While you're not obligated to bring local brews from wherever you're from, participants are definitely encouraged to bring brews that you think is special and might be somewhat hard for others outside your area to find. Homebrew is especially welcome as are non-alcoholic beverages.<br />
<br />
This year, eBay has agreed to host the Code4Lib Drinkup at their offices in downtown Portland, a 6 block walk from the conference hotel. Attendees should expect to bring something to share.<br />
<br />
Please Note: The space must be cleaned up and all folks gone no later than 11pm.<br />
<br />
Space is limited to the first 200 people who register.<br />
<br />
== Signup ==<br />
Please sign up below to share the brews and bottles you're thinking of bringing along and make any special requests (but don't expect that your wishes will be granted).<br />
<br />
{| class="wikitable"<br />
|-<br />
! Name !! Bringing !! Wanting<br />
|-<br />
| Esmé Cowles || Cigar City 110K+OT Batch #7 or Marshal Zhukov, Homebrew Imperial Saison || Any saison or sour!<br />
|-<br />
| Francis Kayiwa || (at least the following) Boulevard Quad Bourbon Barrel, Weyebacher Althea || <strike> Scotty Karate </strike> barleywines and any porters<br />
|-<br />
| Becky Yoose || Non-alcoholic options: I have access to craft sodas from Millstream, Sprechers, Stevens Point - '''ping me at b.yoose at gmail if you have a wish list!''' Otherwise, I'll buy whatever's available in PDX|| N/A drinks :c) Melon soda (not Ramune) greatly appreciated<br />
|-<br />
| Tania Fersenheim || Something from Pretty Things || ...<br />
|-<br />
| Ben Armintor || BCS Pappy Van Winkle, Dark Lord 2009, Black Tuesday || ...<br />
|-<br />
| Justin Coyne || Surly Darkness? || ...<br />
|-<br />
| Whitni Watkins|| Non-alcoholic Ginger beer options: at least Reed's & Saranac Lake. Potentially one other local brewed Ginger beer. If you have a request from Upstate NY HMU whitni.watkins at gmail (alcoholic and N/A) || Ginger Beers & Ales specifically: Fentimans, River City, Bundaberg and Blenheim Red Hot<br />
|-<br />
| Sarah Simpkin || Accepting requests for tasty Quebecois beers -- [https://brouehaha.com/en/nos-bieres/ see this list for breweries]. Otherwise will grab a small selection. Contact me at sarahsimpkin at gmail.com :-) || Hefeweizen-y beers appreciated<br />
|-<br />
| mx matienzo || Transmitter Brewing B2, De Molen SSS Triple Stout 2011, perhaps a couple southern Upstate NY ciders, ...? || Saisons, sours and gueuzes, weird ciders, other horseblankety stuff<br />
|-<br />
| David Bass || TBT || ...<br />
|-<br />
| Christina Harlow || Probably something from Grimm...? Who knows, stuff from Brooklyn & stuff from Eastern Tenn/Western NC (Highland brewery?) || English bitter type stuff or stouts<br />
|-<br />
| Tom Johnson || Portland/Willamette Valley things you might not find downtown. Heater Allen, Pfriem, The Commons, Block 15, and/or Crux Fermentation. Homebrew (Old Ale brewed in October and racked over the winter).|| ...<br />
|}</div>No replyhttps://wiki.code4lib.org/index.php?title=2015_During_the_Conference_Volunteers&diff=424712015 During the Conference Volunteers2015-01-22T04:17:42Z<p>No reply: </p>
<hr />
<div>code4lib 2015 During the Conference Volunteers<br />
<br />
<!--== Hospitality Suite Committee ==<br />
<br />
This committee makes arrangements for any hospitality suite amenities (technology, snacks, games, icebreakers...) we may want.<br />
--><br />
<br />
== Welcome Wagon Committee ==<br />
<br />
Offers conference newcomers an opportunity to self-identify; offers oldtimers an opportunity to meet newcomers. May also want to constitute a year-round variation for #code4lib.<br />
<br />
* Becky Yoose (b.yoose at google)<br />
<br />
== Social Networking ==<br />
Responsible for non-IRC social networking presence.<br />
<br />
1-2 person(s) to take questions for sessions (assuming there's time during the session) via Twitter/IRC, and adding resources to lanyrd schedule (slides, notes, resources mentioned, etc.) Make a note if you can only do one or both.<br />
<br />
Consider directing people with questions to presenter on twitter/IRC (if applicable) if there is no time for questions.<br />
<br />
== Beverage Share Setup/Teardown ==<br />
<br />
Help set up and clean up after the Tuesday event at the Ebay offices.<br />
<br />
== IRC Helpers ==<br />
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.<br />
<br />
One of the easiest ways to participate is to [http://webchat.freenode.net/ Go here] with your web browser. Choose a nickname (anything works so long as it is unique; if you want to be anonymous pick appropriately). Enter "code4lib" as the "Channel".<br />
<br />
If you've managed to get into the channel without help, type "@helpers" (without the quotes) to see a list of #code4lib helpers.<br />
<br />
== IRC Access ==<br />
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people<br />
<br />
* Mx Matienzo (anarchivist)<br />
<br />
==Registration Desk Volunteers==<br />
<br />
'''Monday'''<br />
<br />
'''Tuesday'''<br />
<br />
'''Wednesday'''<br />
<br />
==MCs==<br />
<br />
'''Tuesday AM'''<br />
<br />
'''Tuesday PM'''<br />
<br />
'''Wednesday AM'''<br />
*Becky, destroyer of last names, singer of badly adapted show tunes <br />
<br />
'''Wednesday PM'''<br />
<br />
'''Thursday AM'''<br />
<br />
<br />
== Session Timer Volunteers ==<br />
<br />
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop with a stopwatch program). It's good to have two people in each slot to back each other up in case of machinery failure.<br />
<br />
'''Schedule for Session Timers'''<br />
<br />
'''Tuesday AM'''<br />
<br />
'''Tuesday PM'''<br />
<br />
'''Wednesday AM'''<br />
<br />
'''Wednesday PM'''<br />
<br />
'''Thursday AM'''<br />
<br />
<br />
== Raffles ==<br />
<br />
<br />
== Whatever Else Needs to be Done ==<br />
<br />
[[Category: Code4Lib2015]]</div>No replyhttps://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&diff=420332015 Preconference Proposals2014-11-08T01:01:06Z<p>No reply: /* DPLA API Workshop: */</p>
<hr />
<div>== Instructions ==<br />
Thank you for considering proposing a pre-conference! Here are a few details:<br />
<br />
* We will be taking pre-conference proposals until '''November 7, 2014'''<br />
* If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu<br />
* Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]<br />
* If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)<br />
* If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu<br />
* '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions<br />
* Please use the template for proposals provided in the pre-formatted block below<br />
<br />
=== Proposal formatting guidelines: ===<br />
<pre><br />
<br />
=== Preconference Title: ===<br />
<br />
One of:<br />
'''"Full Day"''' <br />
'''"Half Day [Morning]"''' <br />
'''"Half Day [Afternoon]"''' <br />
<br />
* Facilitator's name, affiliation, and email address<br />
* Second facilitator's name, affiliation, email address, if second speaker<br />
<br />
Abstract<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
</pre><br />
<br />
<br />
== Pre-conference Proposals ==<br />
<br />
Post your ideas here!<br />
<br />
=== Delivering and Preserving GIS Data ===<br />
<br />
'''Half Day [Morning]'''<br />
<br />
* Darren Hardy, Stanford University, drh@stanford.edu<br />
* Jack Reed, Stanford University, pjreed@stanford.edu<br />
<br />
We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# [[User:Ssimpkin|Sarah Simpkin]]<br />
# Vicky Steeves<br />
# Andrew Battista<br />
# Peggy Griesinger<br />
#<br />
<br />
=== A hands-on introduction to GeoBlacklight ===<br />
<br />
'''Half Day [Afternoon]'''<br />
<br />
* Darren Hardy, Stanford University, drh@stanford.edu<br />
* Jack Reed, Stanford University, pjreed@stanford.edu<br />
<br />
GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop "Delivering and Preserving GIS Data".<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# [[User:Ssimpkin|Sarah Simpkin]]<br />
# Vicky Steeves<br />
# Andrew Battista<br />
# Peggy Griesinger<br />
#<br />
<br />
===RailsBridge: Intro to programming in Ruby on Rails===<br />
'''"Half-Day" [morning]'''<br />
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu<br />
* Additional instructors welcome<br />
<br />
Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.<br />
<br />
RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Maura Carbone<br />
#Vicky Steeves<br />
# Peggy Griesinger<br />
#<br />
<br />
=== Replace yourself with a painfully complex bash script...or try Ansible ===<br />
'''Half Day [Morning]'''<br />
<br />
* Chad Nelson, chad dot nelson @ lyrasis dot org<br />
* Blake Carver, Blake dot carver @lyrasis dot org<br />
<br />
Abstract: <br />
<br />
[http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
#<br />
#<br />
#<br />
<br />
=== Intro to Docker ===<br />
'''Half Day [Whenever]'''<br />
<br />
* John Fink, McMaster University, john dot fink at gmail dot com<br />
* Francis Kayiwa, Kayiwa Consulting , francis dot kayiwa at gmail dot com<br />
<br />
Abstract:<br />
<br />
[http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.<br />
<br />
''Interested in Attending''<br />
<br />
1. Jim Hahn<br />
2. Joshua Gomez<br />
<br />
=== Code Retreat ===<br />
'''Full Day'''<br />
<br />
* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu<br />
* Additional facilitators welcome; Especially if you have CodeRetreat experience.<br />
<br />
Abstract:<br />
<br />
"Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.<br />
By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.<br />
Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time." [http://coderetreat.org/about About Code Retreat]<br />
<br />
''Interested in Attending''<br />
<br />
=== Presentations workshop ===<br />
<br />
'''"Half Day [Afternoon]"''' (but could be expanded based on interest)<br />
<br />
* Chris Beer, Stanford University, cabeer@stanford.edu<br />
* Additional facilitators welcome.<br />
<br />
This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#Vicky Steeves<br />
#<br />
#<br />
<br />
=== Dive into Hydra ===<br />
<br />
One of:<br />
'''"Half Day [Afternoon]"''' <br />
<br />
* Justin Coyne, Data Curation Experts, justin@curationexperts.com<br />
* Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend "RailsBridge" prior to this workshop.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Maura Carbone<br />
# Peggy Griesinger<br />
#<br />
<br />
<br />
=== code4lib/Write The Docs barcamp ===<br />
<br />
One of:<br />
'''"Full Day"''', with options for jumping in for half a day<br />
<br />
* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu<br />
* Write the Docs contacts: TBA<br />
<br />
Abstract<br />
<br />
Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization. <br />
<br />
Remember, like metadata, documentation is a love note to the future.<br />
<br />
More information about Write the Docs at http://conf.writethedocs.org/<br />
<br />
There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). <br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
'''Full day'''<br />
#<br />
#<br />
#<br />
<br />
'''Morning'''<br />
#<br />
#<br />
#<br />
<br />
'''Afternoon'''<br />
#<br />
#<br />
#<br />
<br />
=== Linked Data Workshop ===<br />
<br />
One of:<br />
'''"Half Day [morning]"''' <br />
<br />
* Karen Estlund, University of Oregon, kestlund@uoregon.edu<br />
* Tom Johnson, DPLA, tom@dp.la<br />
<br />
Abstract:<br />
<br />
Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Logan Cox<br />
#<br />
#<br />
<br />
=== Code4Arc ===<br />
<br />
One of:<br />
'''"Full Day"''' (with options for half day participation)<br />
<br />
* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com<br />
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com<br />
* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org<br />
* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com<br />
<br />
Abstract:<br />
<br />
What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? <br />
<br />
Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.<br />
<br />
The schedule may include the following:<br />
<br />
* Panel type conversations about the State of Art in Archives <br />
* Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed <br />
* Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)<br />
<br />
Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with. <br />
<br />
When signing up, please indicate if you are an end-user or a developer.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Laney McGlohon - developer<br />
#<br />
#<br />
<br />
=== Fail4Lib 2015 ===<br />
'''Half Day [TBD, probably afternoon]'''<br />
<br />
* Andreas Orphanides, akorphan (at) ncsu.edu<br />
* Jason Casden, jmcasden (at) ncsu.edu<br />
<br />
Abstract:<br />
<br />
Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.<br />
<br />
This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)<br />
<br />
The schedule may include the following:<br />
<br />
* Case studies. Avoid our own mistakes by bearing witness to the failures of others.<br />
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.<br />
* Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.<br />
<br />
''Interested in attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
=== Coding Custom Solutions for Every Department in the Library with File Analyzer ===<br />
<br />
One of:<br />
'''"Half Day [Morning]"''' <br />
<br />
* Terry Brady, Georgetown University Library, twb27@georgetown.edu<br />
<br />
Abstract<br />
<br />
The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.<br />
<br />
* Analyzing Marc Records for the Cataloging department<br />
* Transferring ILS invoices for the University Account System for the Acquisitions department <br />
* Delivering patron fines to the Bursar’s office for the Access Service department<br />
* Summarizing student worker timesheet data for the Finance department<br />
* Validating counter compliant reports for the Electronic Resources department<br />
* Preparing ingest packages for the Digital Services department<br />
* Validating checksums for the Preservation department<br />
<br />
This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.<br />
<br />
The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
=== Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===<br />
<br />
'''Half Day [Whenever]'''<br />
<br />
* Karen A. Coombs, OCLC, coombsk@oclc.org<br />
<br />
Abstract<br />
Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.<br />
<br />
We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Peggy Griesinger<br />
#<br />
#<br />
<br />
<br />
=== UXtravaganza ===<br />
'''"Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]"'''<br />
<br />
* William Hicks, University of North Texas, William.hicks@unt.edu<br />
* Volunteers?<br />
<br />
Abstract<br />
<br />
I’m envisioning a 1/2 of full day for front-end developers, content strategy people, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state of current research, and play with each other’s sites. A half day seems doable, but if there’s significant enough interest we could push for a full? Here are a few of the things I think might be interesting to see happen:<br />
<br />
* '''Analytics Share-fest:''' A few volunteers demonstrate data about their websites, catalogs, archival/digital collections. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etc. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeing.<br />
<br />
* '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation. Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc.<br />
<br />
* '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an [http://labup.org Open Device Lab]. We have about a dozen devices now of varying sizes, OS, OS Versions, + Google Glass. I’ll bring the devices, you can bring yours, and assuming we can get the wifi up and running we can test our sites/services with our big sausage fingers rather than pretending to do so through emulators and the one or two devices we each usually have on hand. If anyone is game they can do a tutorial on Browser-based Inspector Tools, Browser-Cams, or other testing services.<br />
<br />
* '''The Eye’s Have It.''' The UNT Libraries is also in the process of acquiring an eye tracker and software for usability and other gaze-based research studies. We’ll take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before the conference. Assuming we can get our act together learning the device and can get past the technical hurdles of setting it up at the pre-conference, we could try to do some live demos on each other’s sites; i.e. You nominate a site/service, someone in the audience volunteers to wear the device, and we all watch them struggle do the tasks you request on a projector. Rinse. Lather. Repeat. It would hardly be scientific, but it sure would be fun. As a backup, if we have some sites nominated beforehand, I can run a few students at my library through some tasks here and we can show off the results to the crowd.<br />
<br />
For those of you wanting to attend and help out, I’d really like to see some discussion on typography, writing for the web, “dealing with business/administrative requirements from on-high", maybe do some prototyping exercises, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running a usability test, that would be rad. But we need you to step up and steer part of the time for most of this to work, so if you are interested in some aspect, and especially if you want to volunteer to lead a bit of the time, contact me.<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your<br />
name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
=== Intro to Git & possibly beyond ===<br />
<br />
'''Half Day [Whenever]'''<br />
<br />
* Erin Fahy, Stanford University, efahy@stanford.edu<br />
* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu<br />
<br />
We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:<br />
<br />
* What is a Distributed Version Control System?<br />
* What's the difference between Git and Github.com?<br />
* How to initialize new Git projects locally and on a remote server/Github<br />
* Cloning/Forking existing projects and keeping up to date<br />
* The wonderful world of Git branches<br />
* Interactive rebasing<br />
* Contributing code to existing projects & what pull requests are<br />
* How to handle merge conflicts<br />
* Overview of workflows and branch best practices<br />
* (time allowing) Advanced git: pre/post hooks, submodules, anything else?<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
=== Visualizing Library Data ===<br />
<br />
'''"Half Day [Morning||Afternoon]"''' <br />
<br />
* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs<br />
<br />
Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Ashley Blewer!<br />
#<br />
#<br />
<br />
<br />
=== CollectionSpace: Getting it up and running at your museum ===<br />
<br />
'''Half Day [Afternoon]'''<br />
<br />
* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org<br />
* TBD<br />
<br />
This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org<br />
<br />
Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.<br />
<br />
''Interested in Attending''<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
=== DPLA API Workshop: ===<br />
<br />
'''Half Day [Afternoon]''' <br />
<br />
* Audrey Altman, DPLA<br />
* Mark Breedlove, DPLA<br />
* Mark Matienzo, DPLA<br />
* Tom Johnson, DPLA<br />
<br />
The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
<br />
[[Category:Code4Lib2015]]</div>No replyhttps://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&diff=420322015 Preconference Proposals2014-11-08T01:00:23Z<p>No reply: /* DPLA API Workshop: */</p>
<hr />
<div>== Instructions ==<br />
Thank you for considering proposing a pre-conference! Here are a few details:<br />
<br />
* We will be taking pre-conference proposals until '''November 7, 2014'''<br />
* If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu<br />
* Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]<br />
* If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)<br />
* If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu<br />
* '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions<br />
* Please use the template for proposals provided in the pre-formatted block below<br />
<br />
=== Proposal formatting guidelines: ===<br />
<pre><br />
<br />
=== Preconference Title: ===<br />
<br />
One of:<br />
'''"Full Day"''' <br />
'''"Half Day [Morning]"''' <br />
'''"Half Day [Afternoon]"''' <br />
<br />
* Facilitator's name, affiliation, and email address<br />
* Second facilitator's name, affiliation, email address, if second speaker<br />
<br />
Abstract<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
</pre><br />
<br />
<br />
== Pre-conference Proposals ==<br />
<br />
Post your ideas here!<br />
<br />
=== Delivering and Preserving GIS Data ===<br />
<br />
'''Half Day [Morning]'''<br />
<br />
* Darren Hardy, Stanford University, drh@stanford.edu<br />
* Jack Reed, Stanford University, pjreed@stanford.edu<br />
<br />
We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# [[User:Ssimpkin|Sarah Simpkin]]<br />
# Vicky Steeves<br />
# Andrew Battista<br />
# Peggy Griesinger<br />
#<br />
<br />
=== A hands-on introduction to GeoBlacklight ===<br />
<br />
'''Half Day [Afternoon]'''<br />
<br />
* Darren Hardy, Stanford University, drh@stanford.edu<br />
* Jack Reed, Stanford University, pjreed@stanford.edu<br />
<br />
GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop "Delivering and Preserving GIS Data".<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# [[User:Ssimpkin|Sarah Simpkin]]<br />
# Vicky Steeves<br />
# Andrew Battista<br />
# Peggy Griesinger<br />
#<br />
<br />
===RailsBridge: Intro to programming in Ruby on Rails===<br />
'''"Half-Day" [morning]'''<br />
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu<br />
* Additional instructors welcome<br />
<br />
Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.<br />
<br />
RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Maura Carbone<br />
#Vicky Steeves<br />
# Peggy Griesinger<br />
#<br />
<br />
=== Replace yourself with a painfully complex bash script...or try Ansible ===<br />
'''Half Day [Morning]'''<br />
<br />
* Chad Nelson, chad dot nelson @ lyrasis dot org<br />
* Blake Carver, Blake dot carver @lyrasis dot org<br />
<br />
Abstract: <br />
<br />
[http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
#<br />
#<br />
#<br />
<br />
=== Intro to Docker ===<br />
'''Half Day [Whenever]'''<br />
<br />
* John Fink, McMaster University, john dot fink at gmail dot com<br />
* Francis Kayiwa, Kayiwa Consulting , francis dot kayiwa at gmail dot com<br />
<br />
Abstract:<br />
<br />
[http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.<br />
<br />
''Interested in Attending''<br />
<br />
1. Jim Hahn<br />
2. Joshua Gomez<br />
<br />
=== Code Retreat ===<br />
'''Full Day'''<br />
<br />
* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu<br />
* Additional facilitators welcome; Especially if you have CodeRetreat experience.<br />
<br />
Abstract:<br />
<br />
"Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.<br />
By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.<br />
Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time." [http://coderetreat.org/about About Code Retreat]<br />
<br />
''Interested in Attending''<br />
<br />
=== Presentations workshop ===<br />
<br />
'''"Half Day [Afternoon]"''' (but could be expanded based on interest)<br />
<br />
* Chris Beer, Stanford University, cabeer@stanford.edu<br />
* Additional facilitators welcome.<br />
<br />
This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#Vicky Steeves<br />
#<br />
#<br />
<br />
=== Dive into Hydra ===<br />
<br />
One of:<br />
'''"Half Day [Afternoon]"''' <br />
<br />
* Justin Coyne, Data Curation Experts, justin@curationexperts.com<br />
* Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend "RailsBridge" prior to this workshop.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Maura Carbone<br />
# Peggy Griesinger<br />
#<br />
<br />
<br />
=== code4lib/Write The Docs barcamp ===<br />
<br />
One of:<br />
'''"Full Day"''', with options for jumping in for half a day<br />
<br />
* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu<br />
* Write the Docs contacts: TBA<br />
<br />
Abstract<br />
<br />
Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization. <br />
<br />
Remember, like metadata, documentation is a love note to the future.<br />
<br />
More information about Write the Docs at http://conf.writethedocs.org/<br />
<br />
There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). <br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
'''Full day'''<br />
#<br />
#<br />
#<br />
<br />
'''Morning'''<br />
#<br />
#<br />
#<br />
<br />
'''Afternoon'''<br />
#<br />
#<br />
#<br />
<br />
=== Linked Data Workshop ===<br />
<br />
One of:<br />
'''"Half Day [morning]"''' <br />
<br />
* Karen Estlund, University of Oregon, kestlund@uoregon.edu<br />
* Tom Johnson, DPLA, tom@dp.la<br />
<br />
Abstract:<br />
<br />
Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Logan Cox<br />
#<br />
#<br />
<br />
=== Code4Arc ===<br />
<br />
One of:<br />
'''"Full Day"''' (with options for half day participation)<br />
<br />
* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com<br />
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com<br />
* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org<br />
* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com<br />
<br />
Abstract:<br />
<br />
What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? <br />
<br />
Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.<br />
<br />
The schedule may include the following:<br />
<br />
* Panel type conversations about the State of Art in Archives <br />
* Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed <br />
* Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)<br />
<br />
Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with. <br />
<br />
When signing up, please indicate if you are an end-user or a developer.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Laney McGlohon - developer<br />
#<br />
#<br />
<br />
=== Fail4Lib 2015 ===<br />
'''Half Day [TBD, probably afternoon]'''<br />
<br />
* Andreas Orphanides, akorphan (at) ncsu.edu<br />
* Jason Casden, jmcasden (at) ncsu.edu<br />
<br />
Abstract:<br />
<br />
Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.<br />
<br />
This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)<br />
<br />
The schedule may include the following:<br />
<br />
* Case studies. Avoid our own mistakes by bearing witness to the failures of others.<br />
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.<br />
* Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.<br />
<br />
''Interested in attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
=== Coding Custom Solutions for Every Department in the Library with File Analyzer ===<br />
<br />
One of:<br />
'''"Half Day [Morning]"''' <br />
<br />
* Terry Brady, Georgetown University Library, twb27@georgetown.edu<br />
<br />
Abstract<br />
<br />
The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.<br />
<br />
* Analyzing Marc Records for the Cataloging department<br />
* Transferring ILS invoices for the University Account System for the Acquisitions department <br />
* Delivering patron fines to the Bursar’s office for the Access Service department<br />
* Summarizing student worker timesheet data for the Finance department<br />
* Validating counter compliant reports for the Electronic Resources department<br />
* Preparing ingest packages for the Digital Services department<br />
* Validating checksums for the Preservation department<br />
<br />
This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.<br />
<br />
The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
=== Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===<br />
<br />
'''Half Day [Whenever]'''<br />
<br />
* Karen A. Coombs, OCLC, coombsk@oclc.org<br />
<br />
Abstract<br />
Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.<br />
<br />
We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Peggy Griesinger<br />
#<br />
#<br />
<br />
<br />
=== UXtravaganza ===<br />
'''"Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]"'''<br />
<br />
* William Hicks, University of North Texas, William.hicks@unt.edu<br />
* Volunteers?<br />
<br />
Abstract<br />
<br />
I’m envisioning a 1/2 of full day for front-end developers, content strategy people, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state of current research, and play with each other’s sites. A half day seems doable, but if there’s significant enough interest we could push for a full? Here are a few of the things I think might be interesting to see happen:<br />
<br />
* '''Analytics Share-fest:''' A few volunteers demonstrate data about their websites, catalogs, archival/digital collections. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etc. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeing.<br />
<br />
* '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation. Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc.<br />
<br />
* '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an [http://labup.org Open Device Lab]. We have about a dozen devices now of varying sizes, OS, OS Versions, + Google Glass. I’ll bring the devices, you can bring yours, and assuming we can get the wifi up and running we can test our sites/services with our big sausage fingers rather than pretending to do so through emulators and the one or two devices we each usually have on hand. If anyone is game they can do a tutorial on Browser-based Inspector Tools, Browser-Cams, or other testing services.<br />
<br />
* '''The Eye’s Have It.''' The UNT Libraries is also in the process of acquiring an eye tracker and software for usability and other gaze-based research studies. We’ll take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before the conference. Assuming we can get our act together learning the device and can get past the technical hurdles of setting it up at the pre-conference, we could try to do some live demos on each other’s sites; i.e. You nominate a site/service, someone in the audience volunteers to wear the device, and we all watch them struggle do the tasks you request on a projector. Rinse. Lather. Repeat. It would hardly be scientific, but it sure would be fun. As a backup, if we have some sites nominated beforehand, I can run a few students at my library through some tasks here and we can show off the results to the crowd.<br />
<br />
For those of you wanting to attend and help out, I’d really like to see some discussion on typography, writing for the web, “dealing with business/administrative requirements from on-high", maybe do some prototyping exercises, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running a usability test, that would be rad. But we need you to step up and steer part of the time for most of this to work, so if you are interested in some aspect, and especially if you want to volunteer to lead a bit of the time, contact me.<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your<br />
name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
=== Intro to Git & possibly beyond ===<br />
<br />
'''Half Day [Whenever]'''<br />
<br />
* Erin Fahy, Stanford University, efahy@stanford.edu<br />
* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu<br />
<br />
We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:<br />
<br />
* What is a Distributed Version Control System?<br />
* What's the difference between Git and Github.com?<br />
* How to initialize new Git projects locally and on a remote server/Github<br />
* Cloning/Forking existing projects and keeping up to date<br />
* The wonderful world of Git branches<br />
* Interactive rebasing<br />
* Contributing code to existing projects & what pull requests are<br />
* How to handle merge conflicts<br />
* Overview of workflows and branch best practices<br />
* (time allowing) Advanced git: pre/post hooks, submodules, anything else?<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
=== Visualizing Library Data ===<br />
<br />
'''"Half Day [Morning||Afternoon]"''' <br />
<br />
* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs<br />
<br />
Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Ashley Blewer!<br />
#<br />
#<br />
<br />
<br />
=== CollectionSpace: Getting it up and running at your museum ===<br />
<br />
'''Half Day [Afternoon]'''<br />
<br />
* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org<br />
* TBD<br />
<br />
This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org<br />
<br />
Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.<br />
<br />
''Interested in Attending''<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
=== DPLA API Workshop: ===<br />
<br />
'''Half Day [Afternoon]''' <br />
<br />
* Audrey Altman, DPLA<br />
* Mark Breedlove, DPLA<br />
* Mark Matienzo, DPLA<br />
* Tom Johnson, DPLA<br />
<br />
Abstract<br />
<br />
The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
<br />
[[Category:Code4Lib2015]]</div>No replyhttps://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&diff=420312015 Preconference Proposals2014-11-08T00:58:49Z<p>No reply: /* DPLA API Workshop: */</p>
<hr />
<div>== Instructions ==<br />
Thank you for considering proposing a pre-conference! Here are a few details:<br />
<br />
* We will be taking pre-conference proposals until '''November 7, 2014'''<br />
* If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu<br />
* Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]<br />
* If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)<br />
* If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu<br />
* '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions<br />
* Please use the template for proposals provided in the pre-formatted block below<br />
<br />
=== Proposal formatting guidelines: ===<br />
<pre><br />
<br />
=== Preconference Title: ===<br />
<br />
One of:<br />
'''"Full Day"''' <br />
'''"Half Day [Morning]"''' <br />
'''"Half Day [Afternoon]"''' <br />
<br />
* Facilitator's name, affiliation, and email address<br />
* Second facilitator's name, affiliation, email address, if second speaker<br />
<br />
Abstract<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
</pre><br />
<br />
<br />
== Pre-conference Proposals ==<br />
<br />
Post your ideas here!<br />
<br />
=== Delivering and Preserving GIS Data ===<br />
<br />
'''Half Day [Morning]'''<br />
<br />
* Darren Hardy, Stanford University, drh@stanford.edu<br />
* Jack Reed, Stanford University, pjreed@stanford.edu<br />
<br />
We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# [[User:Ssimpkin|Sarah Simpkin]]<br />
# Vicky Steeves<br />
# Andrew Battista<br />
# Peggy Griesinger<br />
#<br />
<br />
=== A hands-on introduction to GeoBlacklight ===<br />
<br />
'''Half Day [Afternoon]'''<br />
<br />
* Darren Hardy, Stanford University, drh@stanford.edu<br />
* Jack Reed, Stanford University, pjreed@stanford.edu<br />
<br />
GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop "Delivering and Preserving GIS Data".<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# [[User:Ssimpkin|Sarah Simpkin]]<br />
# Vicky Steeves<br />
# Andrew Battista<br />
# Peggy Griesinger<br />
#<br />
<br />
===RailsBridge: Intro to programming in Ruby on Rails===<br />
'''"Half-Day" [morning]'''<br />
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu<br />
* Additional instructors welcome<br />
<br />
Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.<br />
<br />
RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Maura Carbone<br />
#Vicky Steeves<br />
# Peggy Griesinger<br />
#<br />
<br />
=== Replace yourself with a painfully complex bash script...or try Ansible ===<br />
'''Half Day [Morning]'''<br />
<br />
* Chad Nelson, chad dot nelson @ lyrasis dot org<br />
* Blake Carver, Blake dot carver @lyrasis dot org<br />
<br />
Abstract: <br />
<br />
[http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
#<br />
#<br />
#<br />
<br />
=== Intro to Docker ===<br />
'''Half Day [Whenever]'''<br />
<br />
* John Fink, McMaster University, john dot fink at gmail dot com<br />
* Francis Kayiwa, Kayiwa Consulting , francis dot kayiwa at gmail dot com<br />
<br />
Abstract:<br />
<br />
[http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.<br />
<br />
''Interested in Attending''<br />
<br />
1. Jim Hahn<br />
2. Joshua Gomez<br />
<br />
=== Code Retreat ===<br />
'''Full Day'''<br />
<br />
* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu<br />
* Additional facilitators welcome; Especially if you have CodeRetreat experience.<br />
<br />
Abstract:<br />
<br />
"Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.<br />
By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.<br />
Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time." [http://coderetreat.org/about About Code Retreat]<br />
<br />
''Interested in Attending''<br />
<br />
=== Presentations workshop ===<br />
<br />
'''"Half Day [Afternoon]"''' (but could be expanded based on interest)<br />
<br />
* Chris Beer, Stanford University, cabeer@stanford.edu<br />
* Additional facilitators welcome.<br />
<br />
This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#Vicky Steeves<br />
#<br />
#<br />
<br />
=== Dive into Hydra ===<br />
<br />
One of:<br />
'''"Half Day [Afternoon]"''' <br />
<br />
* Justin Coyne, Data Curation Experts, justin@curationexperts.com<br />
* Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend "RailsBridge" prior to this workshop.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Maura Carbone<br />
# Peggy Griesinger<br />
#<br />
<br />
<br />
=== code4lib/Write The Docs barcamp ===<br />
<br />
One of:<br />
'''"Full Day"''', with options for jumping in for half a day<br />
<br />
* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu<br />
* Write the Docs contacts: TBA<br />
<br />
Abstract<br />
<br />
Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization. <br />
<br />
Remember, like metadata, documentation is a love note to the future.<br />
<br />
More information about Write the Docs at http://conf.writethedocs.org/<br />
<br />
There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). <br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
'''Full day'''<br />
#<br />
#<br />
#<br />
<br />
'''Morning'''<br />
#<br />
#<br />
#<br />
<br />
'''Afternoon'''<br />
#<br />
#<br />
#<br />
<br />
=== Linked Data Workshop ===<br />
<br />
One of:<br />
'''"Half Day [morning]"''' <br />
<br />
* Karen Estlund, University of Oregon, kestlund@uoregon.edu<br />
* Tom Johnson, DPLA, tom@dp.la<br />
<br />
Abstract:<br />
<br />
Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Logan Cox<br />
#<br />
#<br />
<br />
=== Code4Arc ===<br />
<br />
One of:<br />
'''"Full Day"''' (with options for half day participation)<br />
<br />
* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com<br />
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com<br />
* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org<br />
* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com<br />
<br />
Abstract:<br />
<br />
What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? <br />
<br />
Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.<br />
<br />
The schedule may include the following:<br />
<br />
* Panel type conversations about the State of Art in Archives <br />
* Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed <br />
* Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)<br />
<br />
Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with. <br />
<br />
When signing up, please indicate if you are an end-user or a developer.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Laney McGlohon - developer<br />
#<br />
#<br />
<br />
=== Fail4Lib 2015 ===<br />
'''Half Day [TBD, probably afternoon]'''<br />
<br />
* Andreas Orphanides, akorphan (at) ncsu.edu<br />
* Jason Casden, jmcasden (at) ncsu.edu<br />
<br />
Abstract:<br />
<br />
Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.<br />
<br />
This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)<br />
<br />
The schedule may include the following:<br />
<br />
* Case studies. Avoid our own mistakes by bearing witness to the failures of others.<br />
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.<br />
* Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.<br />
<br />
''Interested in attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
=== Coding Custom Solutions for Every Department in the Library with File Analyzer ===<br />
<br />
One of:<br />
'''"Half Day [Morning]"''' <br />
<br />
* Terry Brady, Georgetown University Library, twb27@georgetown.edu<br />
<br />
Abstract<br />
<br />
The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.<br />
<br />
* Analyzing Marc Records for the Cataloging department<br />
* Transferring ILS invoices for the University Account System for the Acquisitions department <br />
* Delivering patron fines to the Bursar’s office for the Access Service department<br />
* Summarizing student worker timesheet data for the Finance department<br />
* Validating counter compliant reports for the Electronic Resources department<br />
* Preparing ingest packages for the Digital Services department<br />
* Validating checksums for the Preservation department<br />
<br />
This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.<br />
<br />
The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
=== Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===<br />
<br />
'''Half Day [Whenever]'''<br />
<br />
* Karen A. Coombs, OCLC, coombsk@oclc.org<br />
<br />
Abstract<br />
Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.<br />
<br />
We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Peggy Griesinger<br />
#<br />
#<br />
<br />
<br />
=== UXtravaganza ===<br />
'''"Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]"'''<br />
<br />
* William Hicks, University of North Texas, William.hicks@unt.edu<br />
* Volunteers?<br />
<br />
Abstract<br />
<br />
I’m envisioning a 1/2 of full day for front-end developers, content strategy people, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state of current research, and play with each other’s sites. A half day seems doable, but if there’s significant enough interest we could push for a full? Here are a few of the things I think might be interesting to see happen:<br />
<br />
* '''Analytics Share-fest:''' A few volunteers demonstrate data about their websites, catalogs, archival/digital collections. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etc. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeing.<br />
<br />
* '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation. Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc.<br />
<br />
* '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an [http://labup.org Open Device Lab]. We have about a dozen devices now of varying sizes, OS, OS Versions, + Google Glass. I’ll bring the devices, you can bring yours, and assuming we can get the wifi up and running we can test our sites/services with our big sausage fingers rather than pretending to do so through emulators and the one or two devices we each usually have on hand. If anyone is game they can do a tutorial on Browser-based Inspector Tools, Browser-Cams, or other testing services.<br />
<br />
* '''The Eye’s Have It.''' The UNT Libraries is also in the process of acquiring an eye tracker and software for usability and other gaze-based research studies. We’ll take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before the conference. Assuming we can get our act together learning the device and can get past the technical hurdles of setting it up at the pre-conference, we could try to do some live demos on each other’s sites; i.e. You nominate a site/service, someone in the audience volunteers to wear the device, and we all watch them struggle do the tasks you request on a projector. Rinse. Lather. Repeat. It would hardly be scientific, but it sure would be fun. As a backup, if we have some sites nominated beforehand, I can run a few students at my library through some tasks here and we can show off the results to the crowd.<br />
<br />
For those of you wanting to attend and help out, I’d really like to see some discussion on typography, writing for the web, “dealing with business/administrative requirements from on-high", maybe do some prototyping exercises, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running a usability test, that would be rad. But we need you to step up and steer part of the time for most of this to work, so if you are interested in some aspect, and especially if you want to volunteer to lead a bit of the time, contact me.<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your<br />
name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
=== Intro to Git & possibly beyond ===<br />
<br />
'''Half Day [Whenever]'''<br />
<br />
* Erin Fahy, Stanford University, efahy@stanford.edu<br />
* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu<br />
<br />
We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:<br />
<br />
* What is a Distributed Version Control System?<br />
* What's the difference between Git and Github.com?<br />
* How to initialize new Git projects locally and on a remote server/Github<br />
* Cloning/Forking existing projects and keeping up to date<br />
* The wonderful world of Git branches<br />
* Interactive rebasing<br />
* Contributing code to existing projects & what pull requests are<br />
* How to handle merge conflicts<br />
* Overview of workflows and branch best practices<br />
* (time allowing) Advanced git: pre/post hooks, submodules, anything else?<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
=== Visualizing Library Data ===<br />
<br />
'''"Half Day [Morning||Afternoon]"''' <br />
<br />
* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs<br />
<br />
Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Ashley Blewer!<br />
#<br />
#<br />
<br />
<br />
=== CollectionSpace: Getting it up and running at your museum ===<br />
<br />
'''Half Day [Afternoon]'''<br />
<br />
* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org<br />
* TBD<br />
<br />
This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org<br />
<br />
Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.<br />
<br />
''Interested in Attending''<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
=== DPLA API Workshop: ===<br />
<br />
'''Half Day [Afternoon]''' <br />
<br />
* Audrey Altman, DPLA<br />
* Mark Breedlove, DPLA<br />
* Mark Matienzo, DPLA<br />
* Tom Johnson, DPLA<br />
<br />
Abstract<br />
<br />
The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a Linked Data format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
<br />
[[Category:Code4Lib2015]]</div>No replyhttps://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&diff=420302015 Preconference Proposals2014-11-08T00:58:05Z<p>No reply: DPLA API Workshop</p>
<hr />
<div>== Instructions ==<br />
Thank you for considering proposing a pre-conference! Here are a few details:<br />
<br />
* We will be taking pre-conference proposals until '''November 7, 2014'''<br />
* If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu<br />
* Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]<br />
* If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)<br />
* If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu<br />
* '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions<br />
* Please use the template for proposals provided in the pre-formatted block below<br />
<br />
=== Proposal formatting guidelines: ===<br />
<pre><br />
<br />
=== Preconference Title: ===<br />
<br />
One of:<br />
'''"Full Day"''' <br />
'''"Half Day [Morning]"''' <br />
'''"Half Day [Afternoon]"''' <br />
<br />
* Facilitator's name, affiliation, and email address<br />
* Second facilitator's name, affiliation, email address, if second speaker<br />
<br />
Abstract<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
</pre><br />
<br />
<br />
== Pre-conference Proposals ==<br />
<br />
Post your ideas here!<br />
<br />
=== Delivering and Preserving GIS Data ===<br />
<br />
'''Half Day [Morning]'''<br />
<br />
* Darren Hardy, Stanford University, drh@stanford.edu<br />
* Jack Reed, Stanford University, pjreed@stanford.edu<br />
<br />
We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# [[User:Ssimpkin|Sarah Simpkin]]<br />
# Vicky Steeves<br />
# Andrew Battista<br />
# Peggy Griesinger<br />
#<br />
<br />
=== A hands-on introduction to GeoBlacklight ===<br />
<br />
'''Half Day [Afternoon]'''<br />
<br />
* Darren Hardy, Stanford University, drh@stanford.edu<br />
* Jack Reed, Stanford University, pjreed@stanford.edu<br />
<br />
GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop "Delivering and Preserving GIS Data".<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# [[User:Ssimpkin|Sarah Simpkin]]<br />
# Vicky Steeves<br />
# Andrew Battista<br />
# Peggy Griesinger<br />
#<br />
<br />
===RailsBridge: Intro to programming in Ruby on Rails===<br />
'''"Half-Day" [morning]'''<br />
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu<br />
* Additional instructors welcome<br />
<br />
Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.<br />
<br />
RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Maura Carbone<br />
#Vicky Steeves<br />
# Peggy Griesinger<br />
#<br />
<br />
=== Replace yourself with a painfully complex bash script...or try Ansible ===<br />
'''Half Day [Morning]'''<br />
<br />
* Chad Nelson, chad dot nelson @ lyrasis dot org<br />
* Blake Carver, Blake dot carver @lyrasis dot org<br />
<br />
Abstract: <br />
<br />
[http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
#<br />
#<br />
#<br />
<br />
=== Intro to Docker ===<br />
'''Half Day [Whenever]'''<br />
<br />
* John Fink, McMaster University, john dot fink at gmail dot com<br />
* Francis Kayiwa, Kayiwa Consulting , francis dot kayiwa at gmail dot com<br />
<br />
Abstract:<br />
<br />
[http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.<br />
<br />
''Interested in Attending''<br />
<br />
1. Jim Hahn<br />
2. Joshua Gomez<br />
<br />
=== Code Retreat ===<br />
'''Full Day'''<br />
<br />
* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu<br />
* Additional facilitators welcome; Especially if you have CodeRetreat experience.<br />
<br />
Abstract:<br />
<br />
"Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.<br />
By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.<br />
Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time." [http://coderetreat.org/about About Code Retreat]<br />
<br />
''Interested in Attending''<br />
<br />
=== Presentations workshop ===<br />
<br />
'''"Half Day [Afternoon]"''' (but could be expanded based on interest)<br />
<br />
* Chris Beer, Stanford University, cabeer@stanford.edu<br />
* Additional facilitators welcome.<br />
<br />
This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#Vicky Steeves<br />
#<br />
#<br />
<br />
=== Dive into Hydra ===<br />
<br />
One of:<br />
'''"Half Day [Afternoon]"''' <br />
<br />
* Justin Coyne, Data Curation Experts, justin@curationexperts.com<br />
* Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend "RailsBridge" prior to this workshop.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Maura Carbone<br />
# Peggy Griesinger<br />
#<br />
<br />
<br />
=== code4lib/Write The Docs barcamp ===<br />
<br />
One of:<br />
'''"Full Day"''', with options for jumping in for half a day<br />
<br />
* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu<br />
* Write the Docs contacts: TBA<br />
<br />
Abstract<br />
<br />
Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization. <br />
<br />
Remember, like metadata, documentation is a love note to the future.<br />
<br />
More information about Write the Docs at http://conf.writethedocs.org/<br />
<br />
There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). <br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
'''Full day'''<br />
#<br />
#<br />
#<br />
<br />
'''Morning'''<br />
#<br />
#<br />
#<br />
<br />
'''Afternoon'''<br />
#<br />
#<br />
#<br />
<br />
=== Linked Data Workshop ===<br />
<br />
One of:<br />
'''"Half Day [morning]"''' <br />
<br />
* Karen Estlund, University of Oregon, kestlund@uoregon.edu<br />
* Tom Johnson, DPLA, tom@dp.la<br />
<br />
Abstract:<br />
<br />
Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Logan Cox<br />
#<br />
#<br />
<br />
=== Code4Arc ===<br />
<br />
One of:<br />
'''"Full Day"''' (with options for half day participation)<br />
<br />
* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com<br />
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com<br />
* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org<br />
* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com<br />
<br />
Abstract:<br />
<br />
What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? <br />
<br />
Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.<br />
<br />
The schedule may include the following:<br />
<br />
* Panel type conversations about the State of Art in Archives <br />
* Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed <br />
* Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)<br />
<br />
Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with. <br />
<br />
When signing up, please indicate if you are an end-user or a developer.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Laney McGlohon - developer<br />
#<br />
#<br />
<br />
=== Fail4Lib 2015 ===<br />
'''Half Day [TBD, probably afternoon]'''<br />
<br />
* Andreas Orphanides, akorphan (at) ncsu.edu<br />
* Jason Casden, jmcasden (at) ncsu.edu<br />
<br />
Abstract:<br />
<br />
Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.<br />
<br />
This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)<br />
<br />
The schedule may include the following:<br />
<br />
* Case studies. Avoid our own mistakes by bearing witness to the failures of others.<br />
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.<br />
* Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.<br />
<br />
''Interested in attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
=== Coding Custom Solutions for Every Department in the Library with File Analyzer ===<br />
<br />
One of:<br />
'''"Half Day [Morning]"''' <br />
<br />
* Terry Brady, Georgetown University Library, twb27@georgetown.edu<br />
<br />
Abstract<br />
<br />
The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.<br />
<br />
* Analyzing Marc Records for the Cataloging department<br />
* Transferring ILS invoices for the University Account System for the Acquisitions department <br />
* Delivering patron fines to the Bursar’s office for the Access Service department<br />
* Summarizing student worker timesheet data for the Finance department<br />
* Validating counter compliant reports for the Electronic Resources department<br />
* Preparing ingest packages for the Digital Services department<br />
* Validating checksums for the Preservation department<br />
<br />
This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.<br />
<br />
The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
=== Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===<br />
<br />
'''Half Day [Whenever]'''<br />
<br />
* Karen A. Coombs, OCLC, coombsk@oclc.org<br />
<br />
Abstract<br />
Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.<br />
<br />
We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Peggy Griesinger<br />
#<br />
#<br />
<br />
<br />
=== UXtravaganza ===<br />
'''"Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]"'''<br />
<br />
* William Hicks, University of North Texas, William.hicks@unt.edu<br />
* Volunteers?<br />
<br />
Abstract<br />
<br />
I’m envisioning a 1/2 of full day for front-end developers, content strategy people, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state of current research, and play with each other’s sites. A half day seems doable, but if there’s significant enough interest we could push for a full? Here are a few of the things I think might be interesting to see happen:<br />
<br />
* '''Analytics Share-fest:''' A few volunteers demonstrate data about their websites, catalogs, archival/digital collections. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etc. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeing.<br />
<br />
* '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation. Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc.<br />
<br />
* '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an [http://labup.org Open Device Lab]. We have about a dozen devices now of varying sizes, OS, OS Versions, + Google Glass. I’ll bring the devices, you can bring yours, and assuming we can get the wifi up and running we can test our sites/services with our big sausage fingers rather than pretending to do so through emulators and the one or two devices we each usually have on hand. If anyone is game they can do a tutorial on Browser-based Inspector Tools, Browser-Cams, or other testing services.<br />
<br />
* '''The Eye’s Have It.''' The UNT Libraries is also in the process of acquiring an eye tracker and software for usability and other gaze-based research studies. We’ll take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before the conference. Assuming we can get our act together learning the device and can get past the technical hurdles of setting it up at the pre-conference, we could try to do some live demos on each other’s sites; i.e. You nominate a site/service, someone in the audience volunteers to wear the device, and we all watch them struggle do the tasks you request on a projector. Rinse. Lather. Repeat. It would hardly be scientific, but it sure would be fun. As a backup, if we have some sites nominated beforehand, I can run a few students at my library through some tasks here and we can show off the results to the crowd.<br />
<br />
For those of you wanting to attend and help out, I’d really like to see some discussion on typography, writing for the web, “dealing with business/administrative requirements from on-high", maybe do some prototyping exercises, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running a usability test, that would be rad. But we need you to step up and steer part of the time for most of this to work, so if you are interested in some aspect, and especially if you want to volunteer to lead a bit of the time, contact me.<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your<br />
name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
=== Intro to Git & possibly beyond ===<br />
<br />
'''Half Day [Whenever]'''<br />
<br />
* Erin Fahy, Stanford University, efahy@stanford.edu<br />
* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu<br />
<br />
We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:<br />
<br />
* What is a Distributed Version Control System?<br />
* What's the difference between Git and Github.com?<br />
* How to initialize new Git projects locally and on a remote server/Github<br />
* Cloning/Forking existing projects and keeping up to date<br />
* The wonderful world of Git branches<br />
* Interactive rebasing<br />
* Contributing code to existing projects & what pull requests are<br />
* How to handle merge conflicts<br />
* Overview of workflows and branch best practices<br />
* (time allowing) Advanced git: pre/post hooks, submodules, anything else?<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
=== Visualizing Library Data ===<br />
<br />
'''"Half Day [Morning||Afternoon]"''' <br />
<br />
* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs<br />
<br />
Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Ashley Blewer!<br />
#<br />
#<br />
<br />
<br />
=== CollectionSpace: Getting it up and running at your museum ===<br />
<br />
'''Half Day [Afternoon]'''<br />
<br />
* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org<br />
* TBD<br />
<br />
This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org<br />
<br />
Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.<br />
<br />
''Interested in Attending''<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
=== DPLA API Workshop: ===<br />
<br />
'''"Half Day [Afternoon]"''' <br />
<br />
* Audrey Altman, DPLA<br />
* Mark Breedlove, DPLA<br />
* Mark Matienzo, DPLA<br />
* Tom Johnson, DPLA<br />
<br />
Abstract<br />
<br />
The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a Linked Data format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#<br />
#<br />
#<br />
<br />
<br />
[[Category:Code4Lib2015]]</div>No replyhttps://wiki.code4lib.org/index.php?title=2015_Conference_Committees&diff=414732015 Conference Committees2014-08-15T16:08:58Z<p>No reply: /* Code4Lib 2015 Committees */ Adding childcare committee</p>
<hr />
<div>= Code4Lib 2015 Committees =<br />
<br />
If you are interested in helping out with a particular part of the Code4Lib 2015 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.<br />
<br />
We will assign a local contact to each committee.<br />
<br />
== Location and Dates ==<br />
<br />
(more details at [http://code4lib.org/conference/2015 http://code4lib.org/conference/2015])<br />
* Location: Hilton Portland and Executive Tower, Portland, Oregon<br />
* Dates: <br />
** Pre-conferences - February 9th, 2015<br />
** Main meeting - February 10th - 12th, 2015<br />
** Post conference activities?<br />
<br />
== Book Give-Away Committee ==<br />
<br />
This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br />
<br />
Need about 2 months to get books shipped to the conference location.<br />
<br />
* [[User:JasonMichel|Jason Paul Michel]]<br />
<br />
== Keynote Speakers Committee ==<br />
<br />
This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br />
<br />
* [[User:Phette23|Eric Phetteplace]]<br />
* Heidi Dowding<br />
<br />
== Onsite Volunteer Committee ==<br />
<br />
This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br />
* Whitni Watkins<br />
* Dre<br />
<br />
== Pre-conference Committee ==<br />
<br />
This committee plans the pre-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.<br />
* [[User:ChristinaHarlow|Christina]]<br />
* [[User:LauraKrier|Laura Krier]]<br />
* [[User:aaroncollie|Aaron Collie]]<br />
<br />
== Program Committee ==<br />
<br />
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.<br />
<br />
* mx matienzo<br />
* cbeer<br />
* Tod Olson<br />
* [[User:Cynthia|Arty]]<br />
* [[User:Ssimpkin|Sarah Simpkin]]<br />
* Ranti Junus<br />
* [[User:DataGazetteer|Peter Murray]] - v<br />
<br />
== Scholarships Committee ==<br />
<br />
This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.<br />
<br />
* Sarah Shealy - v<br />
* Ruth Kitchin Tillman<br />
* Francis Kayiwa<br />
* Bohyun Kim<br />
* Mairelys Lemus-Rojas<br />
<br />
== Social Activities Committee ==<br />
<br />
The committee plans, proposes, and organizes the evening activities.<br />
<br />
* Becky Yoose - v(committee member 4 life)<br />
* Sarah Shealy<br />
* Bohyun Kim<br />
* Whitni Watkins<br />
<br />
== Childcare Committee ==<br />
<br />
Committee to evaluate needs and explore possibilities for on-site child care at the conference. Will implement whatever is determined to be possible this year and develop guidelines for future conferences.<br />
<br />
* Sara Amato (lead)<br />
* Christina Salazar <br />
<br />
== Sponsorships Committee ==<br />
<br />
This committee organizes the sponsorship activities. Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br />
<br />
* Evviva Weinraub, Oregon State University Libraries, evviva.weinraub@oregonstate.edu - local contact<br />
* Roy Tennant, OCLC, firstnamelastname@gmail.com<br />
<br />
== Streaming Video Committee ==<br />
<br />
*[[User:highermath|Cary Gordon]] has equipment, experience and domain knowledge to share.<br />
*[[User:RileyChilds|Riley Childs]] has Knowledge and the YouTube Account credentials (he will consult but conf attendance is iffy)<br />
<br />
== T-Shirt Committee ==<br />
<br />
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.<br />
*[[User:ChristinaHarlow|Christina]]<br />
<br />
== Voting Activities Committee ==<br />
<br />
This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br />
<br />
<br />
== Whatever Committee ==<br />
<br />
This committee does whatever the organizers can't talk anyone else into doing.<br />
<br />
* Francis Kayiwa<br />
* Becky Yoose (will do things for mortgage payment assistance)<br />
* [[User:ChristinaHarlow|Christina]]<br />
* [[User:Ssimpkin|Sarah Simpkin]]<br />
* Ranti Junus<br />
* Whitni Watkins<br />
* Sarah Park<br />
<br />
== Wifi / Electrical / IRC ==<br />
<br />
This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community.<br />
<br />
* [[User:highermath|Cary Gordon]], cgordon@chillco.com<br />
* [[User:RileyChilds|Riley Childs]] is able to assist with Wireless planning and IRC stuffs, rchilds@cucawarriors.com (he will consult but conf attendance is iffy)<br />
<br />
= Documentation =<br />
To help with documention, no need to sign up, just start editing.<br />
* [[How To Plan A Code4LibCon]]<br />
<br />
== Documentation Interest Group ==<br />
Promote ongoing documentation efforts.<br />
<br />
[[Category: Code4Lib2015]]</div>No replyhttps://wiki.code4lib.org/index.php?title=2015_Conference_Committees&diff=409972015 Conference Committees2014-03-27T22:57:46Z<p>No reply: </p>
<hr />
<div>= Code4Lib 2015 Committees =<br />
<br />
If you are interested in helping out with a particular part of the Code4Lib 2015 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.<br />
<br />
We will assign a local contact to each committee.<br />
<br />
== Book Give-Away Committee ==<br />
<br />
This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br />
<br />
Need about 2 months to get books shipped to the conference location.<br />
<br />
*<br />
<br />
== Keynote Speakers Committee ==<br />
<br />
This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br />
<br />
<br />
== Onsite Volunteer Committee ==<br />
<br />
This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br />
<br />
<br />
== Pre-conference Committee ==<br />
<br />
This committee plans the pre-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.<br />
<br />
<br />
== Program Committee ==<br />
<br />
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.<br />
<br />
* mx matienzo<br />
<br />
== Scholarships Committee ==<br />
<br />
This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.<br />
<br />
<br />
== Social Activities Committee ==<br />
<br />
The committee plans, proposes, and organizes the evening activities.<br />
<br />
<br />
== Sponsorships Committee ==<br />
<br />
This committee organizes the sponsorship activities. Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br />
<br />
<br />
<br />
== Streaming Video Committee ==<br />
<br />
[[User:highermath|Cary Gordon]] has equipment and domain knowledge to share.<br />
<br />
== T-Shirt Committee ==<br />
<br />
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.<br />
<br />
<br />
== Voting Activities Committee ==<br />
<br />
This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br />
<br />
<br />
== Whatever Committee ==<br />
<br />
This committee does whatever the organizers can't talk anyone else into doing.<br />
<br />
*<br />
<br />
== Wifi / Electrical / IRC ==<br />
<br />
This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community.<br />
<br />
* [[User:highermath|Cary Gordon]], cgordon@chillco.com<br />
*<br />
<br />
= Documentation =<br />
To help with documention, no need to sign up, just start editing.<br />
* [[How To Plan A Code4LibCon]]<br />
<br />
== Documentation Interest Group ==<br />
Promote ongoing documentation efforts.<br />
<br />
[[Category: Code4Lib2015]]</div>No replyhttps://wiki.code4lib.org/index.php?title=2015_Conference_Committees&diff=409962015 Conference Committees2014-03-27T22:15:20Z<p>No reply: /* Book Give-Away Committee */</p>
<hr />
<div>= Code4Lib 2015 Committees =<br />
<br />
If you are interested in helping out with a particular part of the Code4Lib 2015 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.<br />
<br />
We will assign a local contact to each committee.<br />
<br />
== Book Give-Away Committee ==<br />
<br />
This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br />
<br />
Need about 2 months to get books shipped to the conference location.<br />
<br />
*<br />
<br />
== Keynote Speakers Committee ==<br />
<br />
This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br />
<br />
<br />
== Onsite Volunteer Committee ==<br />
<br />
This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br />
<br />
<br />
== Pre-conference Committee ==<br />
<br />
This committee plans the pre-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.<br />
<br />
<br />
== Program Committee ==<br />
<br />
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.<br />
<br />
* mx matienzo<br />
<br />
== Scholarships Committee ==<br />
<br />
This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.<br />
<br />
<br />
== Social Activities Committee ==<br />
<br />
The committee plans, proposes, and organizes the evening activities.<br />
<br />
<br />
== Sponsorships Committee ==<br />
<br />
This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br />
<br />
<br />
<br />
== Streaming Video Committee ==<br />
<br />
[[User:highermath|Cary Gordon]] has equipment and domain knowledge to share.<br />
<br />
== T-Shirt Committee ==<br />
<br />
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.<br />
<br />
<br />
== Voting Activities Committee ==<br />
<br />
This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br />
<br />
<br />
== Whatever Committee ==<br />
<br />
This committee does whatever the organizers can't talk anyone else into doing.<br />
<br />
*<br />
<br />
== Wifi / Electrical / IRC ==<br />
<br />
This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community.<br />
<br />
* [[User:highermath|Cary Gordon]], cgordon@chillco.com<br />
*<br />
<br />
= Documentation =<br />
To help with documention, no need to sign up, just start editing.<br />
* [[How To Plan A Code4LibCon]]<br />
<br />
== Documentation Interest Group ==<br />
Promote ongoing documentation efforts.<br />
<br />
[[Category: Code4Lib2015]]</div>No replyhttps://wiki.code4lib.org/index.php?title=2015_Conference_Committees&diff=409392015 Conference Committees2014-03-26T19:45:14Z<p>No reply: Created Page.</p>
<hr />
<div>= Code4Lib 2015 Committees =<br />
<br />
If you are interested in helping out with a particular part of the Code4Lib 2015 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.<br />
<br />
We will assign a local contact to each committee.<br />
<br />
== Book Give-Away Committee ==<br />
<br />
This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br />
<br />
Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br />
<br />
*<br />
<br />
== Keynote Speakers Committee ==<br />
<br />
This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br />
<br />
<br />
== Onsite Volunteer Committee ==<br />
<br />
This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br />
<br />
<br />
== Pre-conference Committee ==<br />
<br />
This committee plans the pre-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.<br />
<br />
<br />
== Program Committee ==<br />
<br />
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.<br />
<br />
<br />
== Scholarships Committee ==<br />
<br />
This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.<br />
<br />
<br />
== Social Activities Committee ==<br />
<br />
The committee plans, proposes, and organizes the evening activities.<br />
<br />
<br />
== Sponsorships Committee ==<br />
<br />
This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br />
<br />
<br />
<br />
== Streaming Video Committee ==<br />
<br />
<br />
== T-Shirt Committee ==<br />
<br />
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.<br />
<br />
<br />
== Voting Activities Committee ==<br />
<br />
This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br />
<br />
<br />
== Whatever Committee ==<br />
<br />
This committee does whatever the organizers can't talk anyone else into doing.<br />
<br />
*<br />
<br />
== Wifi / Electrical / IRC ==<br />
<br />
This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community.<br />
<br />
*<br />
<br />
= Documentation =<br />
To help with documention, no need to sign up, just start editing.<br />
* [[How To Plan A Code4LibCon]]<br />
<br />
== Documentation Interest Group ==<br />
Promote ongoing documentation efforts.<br />
<br />
[[Category: Code4Lib2015]]</div>No replyhttps://wiki.code4lib.org/index.php?title=Main_Page&diff=40938Main Page2014-03-26T19:41:56Z<p>No reply: /* Code4Lib 2015 Conference */</p>
<hr />
<div>{|align=right<br />
|__TOC__<br />
|}<br />
<br />
== About Code4Lib ==<br />
<br />
* [[About Code4Lib]] - Background and history of the community<br />
* [[A Guide for the Perplexed]] - Building skills for working with library technologies<br />
* [[How to hack code4lib]] - For those newer to the community<br />
* [https://docs.google.com/document/d/1m-9VtL7L_fUxl2hTF_YZSdFRfucaLtmHvLSzom6XPVM/edit?pli=1 Code4Lib Indoctrination] (This is a Google doc open to all including anonymous feedback.)<br />
**"How do we make code4lib a more inclusive place for newcomers? <br/> Or, how do we quickly indoctrinate newbies to our values and ways of doing things?" <br />
**Suggestions, ideas, and follow-up actions solicited.<br />
* [[One recommended tool/resource for n00bs]] - For new coding librarians/library Coders<br />
* [[Mentorship Program]]<br />
* [[Zoia or the Code4Lib IRC bot]]<br />
<br />
==Code4Lib 2015 Conference==<br />
*[[2015 Conference Committees]]<br />
*[[2015 Hosting Proposals]]<br />
<br />
==Code4Lib 2014 Conference==<br />
See also the ''[[:Category:Code4Lib2014]] category''<br />
*[http://code4lib.org/conference/2014 Summary Information]<br />
*[[2014 Notes for Speakers]] (UNOFFICIAL)<br />
*[[Code4Lib 2014 Conference Planning Volunteers]]<br />
*[[2014 Proposals]]<br />
*[[2014 Prepared Talk Proposals]]<br />
*[[2014 preconference proposals]]<br />
*[[2014 Breakout I (Tuesday)]]<br />
*[[2014 Breakout II (Wednesday)]]<br />
*[[2014 Lightning Talks]]<br />
*[[2014 Links from Talks]]<br />
*[[2014 Invited Speakers Nominations]]<br />
*[[Sponsor Logos for T-Shirt]]<br />
*[[2014 t-shirt design proposals]]<br />
**[[media:cmarkman-shirt.gif|winning design]]<br />
*[[2014 Room and Ride Share]]<br />
*[[2014 Social Activities]]<br />
*[[2014 Video Recording & Streaming]]<br />
*[[2014 Lessons Learned]]<br />
*[[2014 During the Conference Volunteers]]<br />
<br />
== Local / Regional Groups ==<br />
<br />
* [[NYC|Code4LibNYC]] - NYC and surrounding areas<br />
* [[NEC4L|New England Code4lib]] - New England<br />
* [[NL|Code4Bib]] - Dutch Code4Bib<br />
* [[MDC|Code4libMDC]] - Maryland, Washington D.C, Virginia, and surrounding areas<br />
* [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest<br />
* [[North|code4lib North]] - Ontario and surrounding areas ''(new for Jan 2010!)''<br />
* [[Midwest|Code4Lib Midwest]] - Wherever that is...<br />
* [http://groups.google.com/group/ikr-fejlesztok/ Code4lib.hu] - Group of Hungarian library developers<br />
* [http://www.code4lib.jp/ Code4Lib Japan] - ''(new in 2010!)'', see also [http://twitter.com/yesonline/statuses/28561046501 tweet from Jerry Lee]<br />
* [http://groups.google.com/group/code4glam Code4GLAM Australia] - coders, hackers, developers and technologists in the Australian GLAM (Galleries, Libraries, Archives & Museums) sector.<br />
* [[GreatEastern|Code4Lib Great Eastern]] - Atlantic Provinces<br />
* [[Code4lib_Mid-Atlantic|Code4Lib Mid-Atlantic]] - Philadelphia and the Greater Tri-State Area<br />
* [[BC|Code4Lib BC]] - British Columbia ''(new in 2013)''<br />
* [[Edmonton|Code4LibYEG]] - Edmonton, Alberta ''(also new in 2013)''<br />
<br />
== Interest Groups ==<br />
<br />
* [[ILS_Interop|ILS Interoperability]] - A group working to develop an infrastructure for interoperating between discovery layers and integrated library systems.<br />
* [[Open_Source_Book_Widgets|Open Source Book Widgets]] - A list of open source book widgets<br />
* [[Discovery|Open Source Discovery]] - Open Source application to enhance and support "discovery" in libraries<br />
* [[Mobile_Apps|Mobile Applications]] - A group interested in mobile web and native application development for libraries<br />
* [[Sources_Of_Metadata|Sources Of Metadata]] - list of api's and sources of interest to libraries<br />
<br />
== Software Usage and Documentation ==<br />
<br />
* [[Umlaut]] - OpenURL link resolving middleware<br />
* [[: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. <br />
* [[ILS Documentation]]<br />
* [[OSS Directory]]<br />
* [[Working with MARC]]<br />
* [[Rogue]] - principles for standards creation<br />
* [[ProjectManagement]] - list of project management and issue tracking software that are frequently mentioned on the Code4Lib mailinglist<br />
<br />
== Code4Lib Journal ==<br />
<br />
* [[:Category:Code4Lib Journal|Code4Lib Journal]] - information and working documents<br />
<br />
== Current topics ==<br />
<br />
* [[Code4Lib Website Update]]<br />
* [[OCLC Policy Change]]<br />
* [[SirsiDynix: Integrated Library System Platforms on Open Source]]<br />
* [[Parsing Library Data]]<br />
* [[Robots Are Our Friends]]<br />
* [[List of Library Github Accounts]]<br />
<br />
== Other Code4Lib Sites ==<br />
<br />
* [http://www.code4lib.org/ code4lib.org]<br />
* [http://planet.code4lib.org planet.code4lib.org]<br />
* [http://journal.code4lib.org journal.code4lib.org]<br />
<br />
== Earlier Conferences and events ==<br />
[[Conference Financial History At A Glance]]<br />
<br />
===Code4Lib 2013 Conference===<br />
See also the ''[[:Category:Code4Lib2013]] category''<br />
*[http://code4lib.org/conference/2013/schedule 2013 Schedule]<br />
*[[2013 Lightning Talks Signup]]<br />
*[https://docs.google.com/document/d/1TahfqabnchZLD1opq6ILs8XCYdXkgJDsj8-WyVLNzI4/edit Breakout Session Signups] | [[2013_breakout_sessions_reports|2013 Breakout Sessions Reports]]<br />
*[[2013_committees_sign-up_page|Volunteer to help plan 2013 conference]]<br />
*[[2013_During_the_Conference_Volunteers|During the conference volunteer signup]]<br />
*[[2013 Invited Speakers Nominations]] -- nominations close Aug. 31, 2012.<br />
*[[2013 preconference proposals|2013 preconference sessions]] - try to sign up by Jan 15th<br />
*[[2013 talks proposals]] - due Friday, Nov 9<br />
*[[2013 t-shirt design proposals]] - due Monday, Dec. 31<br />
**[[media:Metadata.jpg|winning design]]<br />
<br />
*[[2013_social_activities|Social Activities for 2013 Conference]]<br />
*[[2013_travel|Travel Advice and Getting To and From the 2013 Conference]]<br />
*[[2013_room_ride_share|2013 Conference Room and Ride Share]]<br />
*[[2013_Guide_To_Wireless| Connecting to the UIC's Wifi]]<br />
*[[2013 Twitter List| 2013 Twitter Attendee List]]<br />
<br />
* Conference hashtag: #c4l13 -- [https://docs.google.com/spreadsheet/ccc?key=0AsyivMoYhk87dFljMUZURWZMYzNzT2lwcEduUUJ6d1E#gid=113 Archive of tweets] | [http://www.flickr.com/search/?q=c4l13 Flickr photos]<br />
<br />
===Code4Lib 2012 Conference===<br />
''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2012 Code4lib2012 category]''<br />
<br />
* [http://code4lib.org/conference/2012/ 2012 home]<br />
* [[During_the_Conference_Volunteers|Volunteer to help at code4lib 2012]]<br />
* [[2012_committees_sign-up_page|Volunteer to help plan 2012 conference]]<br />
* [[2012_preconference_proposals|2012 Preconference Proposals]]--due Sunday, November 20<br />
* [[2012_talks_proposals|2012 Talk Proposals]]--due Sunday, November 20<br />
* [[2012_c4l2012_social_activities|Social Activities]] - ideas and sign-up<br />
* [[c4l2012_rideshare|Rideshare-Roomshare]]<br />
* [[c4l2012_t-shirtcontest|T-shirt contest]]<br />
**[[media:C4l12-t-shirt.jpg|winning design]]<br />
* [[ideas_for_2012|Put your ideas for 2012 here!]]<br />
* [[C4L2012_Call_For_Host|2012 Call For Host]]<br />
* [[How To Plan A Code4LibCon]]<br />
* [http://linkd.in/unhJsR LinkedIn Event]<br />
* [[2012_twitter_list|List your Twitter handle here]]<br />
* [[2012_Lightning_Talks_Signup|Lightning Talks Signup]]<br />
* [http://irc.code4lib.org/ IRC Channel Timeline & Log]<br />
* [http://www.livestream.com/code4lib Conference Livestream] (non-attendees only, please!)<br />
<br />
=== Code4Lib 2011 Conference ===<br />
''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2011 Code4lib2011 category]''<br />
<br />
* [http://code4lib.org/conference/2011 C4L2011 Home]<br />
* [[C4L2011_registration | Registration Information!]]<br />
* [[2011_committees_sign-up_page | 2011 Committees Sign-Up]] - '''Volunteer to help'''<br />
* [[How To Plan A Code4LibCon]]<br />
* [[C4L2011_social_activities|Social Activities]] - ideas & sign-up<br />
* [[C4L2011_planning_wishlist|'''Put your ideas for 2011 here!''']]<br />
* [http://www.facebook.com/event.php?eid=161853827200024 Facebook Event Page]<br />
* [http://events.linkedin.com/Code4Lib-2011/pub/448897 LinkedIn Event Page]<br />
<!-- commenting out until later * '''[[2011 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff''' --><br />
* [[C4L2011_rideshare|Airport Ride Share and Carpooling]]<br />
* [[C4L2011_roomshare | Hotel room share]]<br />
* [http://vote.code4lib.org/election/results/18 T-Shirt election]<br />
** [[media:Option4.jpg|winning design]]<br />
<br />
=== Code4Lib 2010 Conference ===<br />
<br />
''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2010 Code4lib2010 category]''<br />
* [http://code4lib.org/conference/2010/schedule Finalized schedule]<br />
* [[2010 Lightning Talks Signup]] - sign up to give a lightning talk<br />
* [[2010 Breakout Sessions]] - suggest a breakout here<br />
* '''[[2010 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff'''<br />
* [[C4L2010_social_activities|Social Activities]] - ideas & sign-up<br />
* [[Committees sign-up page]] - '''Volunteer to help'''<br />
* [[C4L2011_planning_wishlist|'''Put your ideas for 2011 here!''']]<br />
* [[Asheville Airport to Hotel Van Manifest]] <br />
* [[C4L2010rideshare|General shared travel/transportation planning]]<br />
* [[C4L2010planning:RoommatesRidesEtc|Roommates, Rides, Etc]]<br />
* [[C4L2010_manning_discount|Manning Publications Discount]] - discount code (40% off) for use by attendees through Feb. 28, 2010<br />
* Thanks also to our other sponsors!<br />
* [[C4L2010planning|2010 Planning]]<br />
* [[C4L2010planning:_wishlist | 2010 Planning Wishlist]] - planning page for issues, expectations, etc. for the 2010 conference<br />
* [http://vote.code4lib.org/election/results/14 T-Shirt election]<br />
** [[media:Code4lib2010_P-Hochstenbach.png|winning design]]<br />
<br />
=== Code4Lib 2009 Conference ===<br />
<br />
* [[BookRaffle]] - coordinate begging publishers for books to raffle off at the conference<br />
* [http://inkdroid.org/c4l2009/attendees Get FOAFed] - add your FOAF profile to the network of c4l2009 attendees<br />
* PreConferences:<br />
** [[GIS_preconf_code4libcon2009]] - Open source GIS just like mom used to make<br />
** [[LinkedData]] - A proposal for a linked-data code4lib2009 pre-conference<br />
** [[LibX_Preconference]] - Proposal for a half-day pre-conference targeted at developers who wish to use the LibX 2.0 platform<br />
** [http://code4lib.org/2009/oclc-precon OCLC Grid Services Preconference]<br />
* [[RoommatesRidesEtc]] - Find roommates for Code4Lib 2009, share rides, etc.<br />
* [[2009 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff<br />
* [http://vote.code4lib.org/election/results/8 T-Shirt election]<br />
** [http://code4lib.org/files/the%20whole%20world%20is%20in%20here_black.png winning design]<br />
<br />
=== Older Conference T-Shirt Designs ===<br />
* [http://www.code4lib.org/node/235 2008 (Portland, Oregon)] - [http://code4lib.org/files/code4lib08.gif winning design]<br />
* [http://code4lib.org/node/146 2007 (Athens, Georgia)] - [http://code4lib.org/files/code4lib2007-7.jpg winning design]<br />
* [http://code4lib.org/tshirts 2006 (Corvalis, Oregon)] - [http://code4lib.org/files/t-shirt.png winning design]<br />
<br />
=== Other workshops ===<br />
* [http://barcamp.org/SearchCampDC SearchCampDC] - barcamp style event in DC with usual suspects from code4lib<br />
* [[code4lib/elag2010]] - 1-day code4lib preconference at elag2010<br />
<br />
== Archived topics ==<br />
<br />
* [[Logo Design Process]]<br />
<br />
<br />
[[AdminToDo]] - ideas and tasks for maintaining the Code4Lib sites</div>No replyhttps://wiki.code4lib.org/index.php?title=2015_Hosting_Proposals&diff=406282015 Hosting Proposals2014-03-12T00:55:28Z<p>No reply: /* Portland, OR */</p>
<hr />
<div>==Schedule==<br />
Proposal period opens: Wednesday January 29th, 2014<br />
<br />
Proposal period closes: Wednesday March 12th, 2014<br />
<br />
<br />
Voting opens: Friday March 14th, 2014<br />
<br />
Voting closes: Friday March 21st, 2014<br />
<br />
<br />
<br />
Please list your proposal below;<br />
<br />
<br />
==Los Angeles==<br />
Proposal details coming soon...<br />
<br />
==[http://osulp.github.io/code4lib-pdx/ Portland, OR]==<br />
Oregon State University hosted the first Code4Lib conference in Corvallis, Oregon in 2005. In the spirit of celebrating the conference's 10th year, OSU wants to bring Code4Lib back to Oregon! See http://osulp.github.io/code4lib-pdx/ for details.</div>No replyhttps://wiki.code4lib.org/index.php?title=2015_Hosting_Proposals&diff=406272015 Hosting Proposals2014-03-12T00:54:47Z<p>No reply: PDX</p>
<hr />
<div>==Schedule==<br />
Proposal period opens: Wednesday January 29th, 2014<br />
<br />
Proposal period closes: Wednesday March 12th, 2014<br />
<br />
<br />
Voting opens: Friday March 14th, 2014<br />
<br />
Voting closes: Friday March 21st, 2014<br />
<br />
<br />
<br />
Please list your proposal below;<br />
<br />
<br />
==Los Angeles==<br />
Proposal details coming soon...<br />
<br />
==[http://osulp.github.io/code4lib-pdx/ Portland, OR]==<br />
Oregon State University hosted the first Code4Lib conference in Corvallis, Oregon in 2005. In the spirit of celebrating the conference's 10th year, OSU wants to bring Code4Lib back to Oregon.</div>No replyhttps://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39376Code4Lib 2014 Conference Planning Volunteers2013-07-31T00:37:08Z<p>No reply: /* Program Committee */ Accepted.</p>
<hr />
<div>= Code4Lib 2014 Committees =<br />
<br />
If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br />
<br />
We hope to include at least one local person on each committee.<br />
<br />
A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. It has been shared with code4libcon and code4lib2014 google groups.<br />
<br />
== Book Give-Away Committee ==<br />
<br />
This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br />
<br />
Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br />
<br />
* Kevin S. Clarke (O'Reilly) and general wrangling (nominated as lead)<br />
* Michael B. Klein (Pragmatic) and winner-picker app<br />
<br />
== Keynote Speakers Committee ==<br />
<br />
This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br />
<br />
Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013<br /><br />
Keynote speaker voting - September 9, 2013 - September 20, 2013<br /><br />
Have speakers finalized by November 15, 2013<br />
<br />
* Jason Casden (NCSU) -- lead<br />
* Tom Johnson (Johnson.tom@gmail.com)<br />
* Bret Davidson (NCSU)<br />
* Jeff Campbell (UNC)<br />
<br />
== Onsite Volunteer Committee ==<br />
<br />
This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br />
<br />
* Kevin S. Clarke<br />
* Kevin Beswick (NCSU)<br />
* Yan Wang (NCCU)<br />
<br />
== Pre-conference Committee ==<br />
<br />
This committee plans the pre-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.<br />
<br />
Call for pre-conf proposals -- October 14, 2013<br /><br />
Deadline for pre-conf proposals -- December 6, 2013 <br /><br />
Finalize pre-confs before registration opens -- January 3, 2014<br /><br />
Send rosters to pre-conf organizers -- by February 21, 2014<br />
<br />
* Adam Constabaris (NCSU) -- nominated as lead<br />
* Tim Shearer (UNC)<br />
<br />
== Program Committee ==<br />
<br />
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.<br />
<br />
Call for talk proposals -- October 14 - November 8, 2013<br /><br />
First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013<br /><br />
Voting on talks -- November 18, 203 - December 6, 2013<br /><br />
Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013<br /><br />
Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)<br /><br />
Post final program schedule with talks - January 13, 2014<br />
<br />
* Tom Johnson (Johnson.tom@gmail.com) -- lead<br />
* Kevin Beswick (NCSU)<br />
* Ranti Junus (MSU)<br />
* Roy Tennant (OCLC)<br />
<br />
== Scholarships Committee ==<br />
<br />
This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.<br />
<br />
Call for applicants -- November 18, 2013 - December 13, 2013<br /><br />
Determine winners -- December 14, 2014 - January 5, 2014<br /><br />
Notify winners -- January 6, 2014 (must be before registration)<br />
<br />
* Jason Ronallo (NCSU) -- nominated as lead<br />
* Cory Lown (NCSU)<br />
<br />
== Social Activities Committee ==<br />
<br />
The committee plans, proposes, and organizes the evening activities.<br />
<br />
* Jason Raitz<br />
* Rosalyn Metz<br />
* Dre<br />
* Becky Yoose<br />
<br />
== Sponsorships Committee ==<br />
<br />
This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br />
<br />
* Tim McGeary (lead worrier)<br />
* Roy Tennant (OCLC)<br />
* Shaun Ellis (shaune@princeton.edu)<br />
* Robert H. McDonald (Indiana)<br />
* Sean Chen (Duke)<br />
* Thomas Dowling (Wake Forest)<br />
* Will Sexton (Duke)<br />
* Jeff Campbell (UNC-CH)<br />
* Brett Bonfield (Collingswood Public)<br />
<br />
== Streaming Video Committee ==<br />
<br />
This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br />
<br />
Work with local team to get solid A/V estimates by late November 2013 to use for final budget.<br />
<br />
- Francis Kayiwa<br />
* Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br />
<br />
== T-Shirt Committee ==<br />
<br />
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.<br />
<br />
Call for T-shirt designs - December 2, 2014 - January 3, 2014<br /><br />
Voting on T-shirt designs - January 13, 2014 - January 24, 2014<br /><br />
Get bids based on sizes and design - January 27, 2014 - February 14, 2014<br /><br />
Order t-shirts by February 17, 2014<br />
<br />
*Charlie Morris (NCSU) -- nominated as lead<br />
<br />
== Voting Activities Committee ==<br />
<br />
This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br />
<br />
*Adam Constabaris (NCSU)<br />
<br />
== Whatever Committee ==<br />
<br />
This committee does whatever the organizers can't talk anyone else into doing.<br />
<br />
* Francis Kayiwa<br />
* Kevin S. Clarke<br />
* Dre<br />
* Ranti Junus<br />
<br />
== Wifi / Electrical / IRC Committee==<br />
<br />
This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br />
<br />
* [[User:highermath|Cary Gordon]], cgordon@chillco.com<br />
<br />
This is a newly proposed committee.<br />
<br />
= Documentation =<br />
To help with documention, no need to sign up, just start editing.<br />
* [[How To Plan A Code4LibCon]]<br />
<br />
== Documentation Interest Group ==<br />
Promote ongoing documentation efforts.<br />
<br />
[[Category: Code4Lib2014]]</div>No replyhttps://wiki.code4lib.org/index.php?title=2013_breakout_sessions_reports&diff=367592013 breakout sessions reports2013-02-13T22:37:45Z<p>No reply: /* Wednesday, Feb.13, 2013 */</p>
<hr />
<div>== Tuesday, Feb.12, 2013 ==<br />
* CodeCraft - Writing better code - '''location: Room D''' [[2013_codecraft_breakout]]<br />
* Code4Lib Journal discussion of editorial process (open to anyone) - '''Main Room, front right corner''' <br />
* Tools for instruction: Guide on the Side, LMS integration, subject / course guides, etc. - '''Main Room, rear right corner''' Minutes: [[2013_instruction_breakout]] <br />
* Marc4J, SolrMarc, and MARC -> Solr in general -- Next steps - '''Room E''' Minutes: [[2013_marc_breakout]]<br />
* Building / Keeping relevant skills - How do you access training, develop skills, and keep current while still doing your day job - '''Room F''' Minutes: [[2013_breakout_remaining_relevant]]<br />
* Cupcakes4Lib -- A Pilgrimage - '''Registration Table''' -- We ate cupcakes. It was amazing. We felt that we chose the right break out session. Photos of the yumminess can be found here. https://www.dropbox.com/sc/qe7uh2jmrs2mhmm/PJ3FjjMR9r<br />
* relevance ranking and testing - '''Main room, left rear corner'''<br />
* Fedora4Lib: Developer Challenge! (http://fedora4lib.org/hack/) - '''Main room, left front corner'''<br />
* Nap4Lib: [http://www.youtube.com/watch?v=CVmGBoPx6Ms zzzzzzzzzzzzzzzzzzzzz]<br />
<br />
== Wednesday, Feb.13, 2013 ==<br />
* CORAL meetup: Are you using CORAL -- '''main room center back (by Francis' recording platform)''' [[2013_coral_meetup]]<br />
* Open Library: status, needs, and infogami as a platform for experimentation -- '''Room F''' [http://okfnpad.org/c4l2013-ol notes]<br />
* VuFind Update / Discussion -- '''main room front left''' [http://lullapad.com/84oT6fXhM6]<br />
* Project Ride Sharing Board -- '''main room back left''' [[2013_project_rideshare_breakout]]<br />
* Use cases, relevancy, and usability -- '''Room D''' [https://docs.google.com/document/d/1KtQlPIqdppw4a6HkrX7dfX1SxU3k6h9hFNVzpMeKKvg/edit notes]<br />
* Lone technologists at small libraries -- '''Room E'''<br />
* [https://docs.google.com/document/d/1BFaBIfhEctcVLUuQiwsKvJdWTN8Mujj8L88Wy7T39Ng/edit Archival Description Discovery Systems (EAD+beyond)] -- '''main room front right'''<br />
* BorrowDirect, CIC, other lending cooperatives using Relais and IndexData tools -- '''main room back right'''<br />
* Internally facing tools for institutional staff -- '''main room center front'''<br />
[[Category:Code4Lib2013]]</div>No replyhttps://wiki.code4lib.org/index.php?title=2013_breakout_sessions_reports&diff=367582013 breakout sessions reports2013-02-13T22:37:31Z<p>No reply: /* Wednesday, Feb.13, 2013 */</p>
<hr />
<div>== Tuesday, Feb.12, 2013 ==<br />
* CodeCraft - Writing better code - '''location: Room D''' [[2013_codecraft_breakout]]<br />
* Code4Lib Journal discussion of editorial process (open to anyone) - '''Main Room, front right corner''' <br />
* Tools for instruction: Guide on the Side, LMS integration, subject / course guides, etc. - '''Main Room, rear right corner''' Minutes: [[2013_instruction_breakout]] <br />
* Marc4J, SolrMarc, and MARC -> Solr in general -- Next steps - '''Room E''' Minutes: [[2013_marc_breakout]]<br />
* Building / Keeping relevant skills - How do you access training, develop skills, and keep current while still doing your day job - '''Room F''' Minutes: [[2013_breakout_remaining_relevant]]<br />
* Cupcakes4Lib -- A Pilgrimage - '''Registration Table''' -- We ate cupcakes. It was amazing. We felt that we chose the right break out session. Photos of the yumminess can be found here. https://www.dropbox.com/sc/qe7uh2jmrs2mhmm/PJ3FjjMR9r<br />
* relevance ranking and testing - '''Main room, left rear corner'''<br />
* Fedora4Lib: Developer Challenge! (http://fedora4lib.org/hack/) - '''Main room, left front corner'''<br />
* Nap4Lib: [http://www.youtube.com/watch?v=CVmGBoPx6Ms zzzzzzzzzzzzzzzzzzzzz]<br />
<br />
== Wednesday, Feb.13, 2013 ==<br />
* CORAL meetup: Are you using CORAL -- '''main room center back (by Francis' recording platform)''' [[2013_coral_meetup]]<br />
* Open Library: status, needs, and infogami as a platform for experimentation -- '''Room F''' [[http://okfnpad.org/c4l2013-ol notes]]<br />
* VuFind Update / Discussion -- '''main room front left''' [http://lullapad.com/84oT6fXhM6]<br />
* Project Ride Sharing Board -- '''main room back left''' [[2013_project_rideshare_breakout]]<br />
* Use cases, relevancy, and usability -- '''Room D''' [https://docs.google.com/document/d/1KtQlPIqdppw4a6HkrX7dfX1SxU3k6h9hFNVzpMeKKvg/edit notes]<br />
* Lone technologists at small libraries -- '''Room E'''<br />
* [https://docs.google.com/document/d/1BFaBIfhEctcVLUuQiwsKvJdWTN8Mujj8L88Wy7T39Ng/edit Archival Description Discovery Systems (EAD+beyond)] -- '''main room front right'''<br />
* BorrowDirect, CIC, other lending cooperatives using Relais and IndexData tools -- '''main room back right'''<br />
* Internally facing tools for institutional staff -- '''main room center front'''<br />
[[Category:Code4Lib2013]]</div>No replyhttps://wiki.code4lib.org/index.php?title=2013_breakout_sessions_reports&diff=367562013 breakout sessions reports2013-02-13T22:36:59Z<p>No reply: /* Wednesday, Feb.13, 2013 */</p>
<hr />
<div>== Tuesday, Feb.12, 2013 ==<br />
* CodeCraft - Writing better code - '''location: Room D''' [[2013_codecraft_breakout]]<br />
* Code4Lib Journal discussion of editorial process (open to anyone) - '''Main Room, front right corner''' <br />
* Tools for instruction: Guide on the Side, LMS integration, subject / course guides, etc. - '''Main Room, rear right corner''' Minutes: [[2013_instruction_breakout]] <br />
* Marc4J, SolrMarc, and MARC -> Solr in general -- Next steps - '''Room E''' Minutes: [[2013_marc_breakout]]<br />
* Building / Keeping relevant skills - How do you access training, develop skills, and keep current while still doing your day job - '''Room F''' Minutes: [[2013_breakout_remaining_relevant]]<br />
* Cupcakes4Lib -- A Pilgrimage - '''Registration Table''' -- We ate cupcakes. It was amazing. We felt that we chose the right break out session. Photos of the yumminess can be found here. https://www.dropbox.com/sc/qe7uh2jmrs2mhmm/PJ3FjjMR9r<br />
* relevance ranking and testing - '''Main room, left rear corner'''<br />
* Fedora4Lib: Developer Challenge! (http://fedora4lib.org/hack/) - '''Main room, left front corner'''<br />
* Nap4Lib: [http://www.youtube.com/watch?v=CVmGBoPx6Ms zzzzzzzzzzzzzzzzzzzzz]<br />
<br />
== Wednesday, Feb.13, 2013 ==<br />
* CORAL meetup: Are you using CORAL -- '''main room center back (by Francis' recording platform)''' [[2013_coral_meetup]]<br />
* Open Library: status, needs, and infogami as a platform for experimentation -- '''Room F''' [[http://okfnpad.org/c4l2013-ol]]<br />
* VuFind Update / Discussion -- '''main room front left''' [http://lullapad.com/84oT6fXhM6]<br />
* Project Ride Sharing Board -- '''main room back left''' [[2013_project_rideshare_breakout]]<br />
* Use cases, relevancy, and usability -- '''Room D''' [https://docs.google.com/document/d/1KtQlPIqdppw4a6HkrX7dfX1SxU3k6h9hFNVzpMeKKvg/edit notes]<br />
* Lone technologists at small libraries -- '''Room E'''<br />
* [https://docs.google.com/document/d/1BFaBIfhEctcVLUuQiwsKvJdWTN8Mujj8L88Wy7T39Ng/edit Archival Description Discovery Systems (EAD+beyond)] -- '''main room front right'''<br />
* BorrowDirect, CIC, other lending cooperatives using Relais and IndexData tools -- '''main room back right'''<br />
* Internally facing tools for institutional staff -- '''main room center front'''<br />
[[Category:Code4Lib2013]]</div>No replyhttps://wiki.code4lib.org/index.php?title=2013_social_activities&diff=366832013 social activities2013-02-13T01:25:23Z<p>No reply: /* Newcomer Dinner, Tuesday 2/12 */</p>
<hr />
<div>== Ideas ==<br />
<br />
* Aviary: super-crazy cocktails. http://www.molecularrecipes.com/molecular-mixology/aviary-cocktails/ . List your name if you're interested, whether Sunday, Monday, and/or Tuesday (after newcomer dinners) work, and whether you're just interested in stopping by, or doing a 7 cocktail tasting flight.*<br />
** statsfool: sunday/monday/tuesday, either drinks or flight.<br />
** Amyhannah: monday/tuesday, drinks, probably not the flight.<br />
** anarchivist: sunday/monday, prefer drinks over flight but could be convinced<br />
** [[User:highermath|highermath]]: monday (could use 10 cocktails after Drupal subCon, I am sure). Uber now works in Chicago, so I would do the flight.<br />
** [[User:pberry|pberry]]: any night but Wednesday (that's Goose Island night) and I'd be up for drinks or flight, although leaning away from flight.<br />
** [[User:thatandromeda|thatandromeda]] oh my gosh yes, any time, probably not the flight.<br />
** [[User:Gdave|gdave]] beautiful site, I would be interested, Sun,Mon,Tues. either drink or flight.<br />
** [[User:shawnc12|shawnc12]]: sunday/monday, either drink or flight<br />
** wdenton: any night, either drink or flight<br />
** beatricep: sunday/monday drink, highly susceptible to flight by peer pressure..<br />
** ryan hess: sunday/monday drink or flight<br />
** infosoph: sunday/monday yes/yes!!<br />
** [[User:Pfeeley|Pfeeley]]: sunday/monday/tuesday, either drink or flight<br />
** [[User:Ksprague|Ksprague]]: tuesday, drink or flight<br />
** [[User:schwartzray|schwartzray]]: anything on any day<br />
* Brewery tour - some possible candidates would be Goose Island, Brew Bus http://www.chicagobrewbus.com/, Piece, Revolution, Half Acre.<br />
* Library field trips - because we're library geeks. Possible places include Newberry and Read/Write.--Read/Write Library confirmed for February 11.--Newberry Library confirmed for February 14.<br />
* Art Institute of Chicago - Only open until 5pm, but possible for people coming in early enough on Sunday. There seems to be enough interest here to actually have a group, when and where should we meet? I added my email so that we could discuss details off the wiki.<br />
** escowles: I'm getting in around noon on Sunday, and interested in this.<br />
** pgrayove at gmail dot com: I'm getting in around noon on Sunday too. I'm interested.<br />
** ranti: And I am. <br />
** tshearerlib: Coming in at around the same time and hope to get to the museum by 1:00. Lunch first?<br />
* Local Option http://localoptionbier.com/ - So you've heard of Hopleaf, you've heard of Maproom. Come to Chicago's *ahem* best kept secret for good food and an evening session on Monday. We will need a tally to make requisite arrangements. Target for arrival at bar: 7ish. Probably a group gathering to head north around 6:30 in hotel lobby (if you want to take the #8 Halsted bus that is).<br />
** kayiwa<br />
** Linda Ballinger<br />
** Courtney Greene<br />
** John Pillans<br />
** +6 from NCSU incl one Bret Davidson<br />
** Megan Kudzia<br />
** Andrew Darby<br />
** erinrwhite<br />
** Will Clarke<br />
** Cody Hanson<br />
** Jesse Brown<br />
** Matt Cordial +1 (my friend and I were already planning a Monday trip here)<br />
** Ray Schwartz<br />
** Eric Larson<br />
** David Cliff<br />
** Ken Irwin<br />
** Dileshni Jayasinghe<br />
<br />
== Planned Events ==<br />
<br />
===Read/Write Library Field Trip, Monday 2/11===<br />
Field trip to the [http://readwritelibrary.org/ Read/Write Library] 6:30PM-9PM <br />
<br />
Drop in whenever during this time.<br />
<br />
Come help catalog the Read/Write Library catalog and hack on the library catalog. We will get food or go to a nearby restaurant depending on interest. We will also invite friends from Code for America to hang out and talk civic data. Bring your laptop along if you have one.<br />
<br />
Let us know if you are coming so we can figure out food:<br />
* Margaret Heller<br />
* Ranti Junus<br />
* Wayne Schneider<br />
* jrochkind will try to make it<br />
* emily shaw (may be a little late)<br />
* <strike>kenirwin - bailed on acct of pre-conf brain death</strike><br />
* Andromeda - yes, unless someone gets Aviary reservations<br />
* Chris Clement - may attend<br />
(hey, there are great bars in that neighborhood!)<br />
* wdenton<br />
<br />
'''Directions to the library from UIC:'''<br />
<br />
''Bus''<br />
<br />
Take the #8 Halsted Bus north to Chicago (Bus will say "#8 Halsted/79th North to Broadway/Waveland")<br />
Take the #66 Chicago Bus west to California (Bus will say either "#66 Chicago west to Austin" or "#66 Chicago West to Pulaski." You can take either one because both Austin and Pulaski are further west than we are so both stop at California)<br />
The Chicago bus stops on the west side of California, which is the side of the street we're on. On California, walk a block north to Walton.<br />
<br />
''Train + Bus (slightly faster/more reliable, but only by about 5-10 minutes)''<br />
<br />
Walk to the UIC/Halsted Blue Line <br />
Take the O'Hare train (toward the Loop) and go all the way through the Loop and back west. Get off at Chicago and use the exit that says "North side of Chicago Ave" (or something similar — I don't remember exactly).<br />
Take the #66 Chicago Bus west to California (Bus will say either "#66 Chicago west to Austin" or "#66 Chicago West to Pulaski." You can take either one because both Austin and Pulaski are further west than we are so both stop at California)<br />
The Chicago bus stops on the west side of California, which is the side of the street we're on. On California, walk a block north to Walton.<br />
<br />
=== Newcomer Dinner, Tuesday 2/12 ===<br />
<br />
First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating <strike>discussions about</strike> demonstrations of the many uses of <strike>bacon</strike> <strike>dongles</strike> XML.<br />
<br />
Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!<br />
<br />
'''Plans'''<br />
* When: Tuesday evening (2/12)<br />
* Time: 6 PM (ish) or whenever you can get your group together<br />
* Mastermind (if you have any questions): [mailto:yoosebec@grinnell.edu Becky Yoose]<br />
<br />
''Guidelines:''<br />
*Max of '''6''' per group<br />
**Please, no waitlisting<br />
*ID yourselves so we can get a good mix of new people and veterans in each group<br />
**New folks - n<br />
**c4l vets - v<br />
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group''')<br />
**Leader duties<br />
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library tech type folks<br />
***Herd folks from hotel to restaurant (know where you're going!)<br />
<br />
<br />
'''Restaurants'''<br />
<br />
<br />
'''Restaurants within .25 miles of the hotel'''<br />
<br />
[http://www.athenarestaurantchicago.com/index.php Athena] (Greek)<br />
<br />
* Al Cornish - v (leader)<br />
* Carolyn Cole - n<br />
* Dileshni Jayasinghe - v<br />
* Will Clark - n<br />
* Adam Constabaris - v<br />
* Patrick Hogan - n<br />
* '''Capped at 6'''<br />
We will meet in the hotel lobby. Leave at 6:15 PM, reservation for six at the Athena at 6:30 PM. It is a short walk down Halsted. <br />
<br />
[http://www.dinerestaurant.com/ Dine] (Contemporary)<br />
<br />
<del>[http://www.girlandthegoat.com/ Girl and the Goat] (American) Top Chef fans take note! This is Stephanie Izard's award-winning resto.</del> Totally booked.<br />
<br />
[http://littlegoatchicago.com/ Little Goat]<br />
<br />
Izard just opened a diner across the street from G&G that is walk-in only. (very good, probably a wait but they also have a bar in the back --wickr)<br />
<br />
We'll meet in the lobby of the hotel at 6:30 and walk over. No reservations.<br />
<br />
* Mark Matienzo (leader) - v<br />
* Andromeda Yelton - n<br />
* Hillel Arnold (intern) - veteran newbie<br />
* Kelly Lucas (will meet at restaurant) - n<br />
* Chris Clement - n<br />
* Erin Fahey (will meet at restaurant) -n<br />
* Beatrice Pulliam - n <br />
* '''CAPPED AT 7'''<br />
<br />
[http://www.haymarketbrewing.com/ Haymarket Pub & Brewery] (Pub food) - Reservations at 6:30pm. Meet in conference hotel lobby at 6:10pm<br />
<br />
* Ryan Wick (leader) - v<br />
* Dan Fehrenbach - n<br />
* Pierre Nault - n<br />
* Minh-Quang Nguyen - n<br />
* Matt Bernhardt - n<br />
* David Gonzalez - n<br />
* '''Capped at 7'''<br />
<br />
[http://www.karynsongreen.com/ Karyn’s on Green] (Vegan)<br />
Completely vegan and close to the conference hotel. We'll meet in the conference hotel at around 6:45 (reservation at 7:00 for 6). Google maps says it is a 5 minute walk.<br />
<br />
*Jason Ronallo (leader)- v<br />
*Alicia Cozine - n<br />
*Mark Mounts - v<br />
*Amy Deschenes - n<br />
*Adam Strohm - n<br />
*Jacob Reed - n<br />
* '''Capped at 6'''<br />
<br />
[http://niarestaurant.com/nia-restaurant-mediterranean-cuisine/ Nia] (Mediterranean tapas)<br />
<br />
[http://www.pegasuschicago.com/index.php Pegasus] (Greek) - reservation at 6:30 for 6. We'll meet in the hotel lobby at 6:15 and walk down.<br />
*Erin White (leader) - v<br />
* Don Mennerich -n<br />
* John MacGillivray <br />
* Santi Thompson - n<br />
* Jan Waterhouse - n<br />
* Nell Taylor - v<br />
*'''Capped at 6'''<br />
<br />
[http://www.roditys.com/index.html Roditys] (Greek) -- Reservations made for 6:30pm. Let's meet in the hotel lobby at 6pm and walk over from there. Its ok if you're a bit late to the lobby, we'll wait. If you have any questions email Rosalyn (Rosy) rosalynmetz at gmail dot com<br />
<br />
* Rosalyn Metz (leader) - v<br />
* [[User:highermath|Cary Gordon]] - v<br />
* [[User:Jacobandresen|Jacob Andresen]] - n<br />
* Karen Miller - n<br />
* Dre - v<br />
* Mahria Lebow - n<br />
* '''Capped at 6'''<br />
<br />
'''Restaurants between .25 miles and .5 miles of the hotel'''<br />
<br />
Code4lib Chicago Celery Salt Society - [http://www.alsbeef.com/ Al's Beef]<br />
<br />
* Jason Casden (leader) - v - No reservations. We can walk from the hotel at 7.<br />
* Charlie Morris - n<br />
* Cory Lown - v<br />
* Carolina Garcia - n<br />
* Cody Hanson - n<br />
* Ken Varnum - v<br />
* '''Capped at 6'''<br />
<br />
[http://avecrestaurant.com/# Avec] (Small plate)<br />
Family-style small plate and tapas. Great Yelp reviews. We'll meet in the conference hotel at 6:00 <strike>6:45</strike> (they don't take reservations, but have stuff to sip on if there's a wait). Less than 10 minute walk from hotel.<br />
<br />
* Shaun Ellis (leader) - v<br />
* Jon Stroop - v<br />
* Paula Gray-Overtoom - n<br />
* Emily Zervas - n<br />
* Cynthia Ng - neither<br />
* Sarah Dooley - n<br />
* '''Capped at 6'''<br />
<br />
[http://www.babavillage.com/ Baba’s Village] (Indian/Pakistani)<br />
<br />
[http://blackbirdrestaurant.com/ Blackbird] (Contemporary)<br />
<br />
(Since the reservation is late, does anyone want to meet for drink in the hotel bar beforehand? There's really no place to wait at the restaurant, and there's no nice bar nearby that I can recall. cm)<br />
* Justin Coyne (reserver) - v - Reservation for Blackbird for 6 at 8:30pm (justin at curationexperts.com)<br />
* Matt Cordial - v<br />
* [http://wiki.code4lib.org/index.php/User:Camcclure Christine McClure - n]<br />
* Devin Higgins - n (devinhiggins at gmail)<br />
* Ken Irwin<br />
* Tad Merchant - n (tadoneus @ gmail)<br />
* '''Capped at 6'''<br />
<br />
[http://www.carnivalechicago.com/menu Carnivale] (Nuevo Latino)<br />
* Nettie Lagace - n/v - reservation is at 8 pm; let's meet at the hotel bar beforehand and merge with the Blackbird group for a bit. I have a red sweater and purple glasses / nettiel at gmail dot com<br />
* Rebecca Jones - n/v<br />
* Ben Burbridge - n<br />
* Andrea Schurr - n/v<br />
* Geoff Boushey - n<br />
* James Staub - n > v<br />
* '''Capped at 6'''<br />
<br />
[http://decero.hellotacos.com/ De Cero] (Mexican)<br />
<br />
[http://www.dragonflymandarin.com/ Dragonfly] (Chinese, sushi)<br />
<br />
[http://giordanos.com/ Giordano's] (Chicago Style Pizza) This place should be able to handle multiple groups...<br />
Meet at hotel lobby at 6ish and we can walk over around 6:15-6:30.<br />
<br />
* Andrew Nagy (leader) - v<br />
* Virginia Schilling - n<br />
* Jane Sandberg - n<br />
* Richard Aroksaar - n<br />
* Jesse Brown - n (jfbrown78 at gmail dot com)<br />
* Bob Haschart -v<br />
* Alicia Morris<br />
* Ayla Stein - n<br />
* Sharona Ginsberg - n<br />
* Andrew Myers - n<br />
* Jim LeFager - n<br />
* Stephen Eisenhauer - n<br />
* Xiaoming Wang -n<br />
* Greg Murry -n<br />
<br />
<br />
[http://www.grangehallburgerbar.com/ Grange Hall Burger Bar] (Local food)<br />
<br />
[http://www.idreamoffalafel.com/ I Dream of Falafel] (Mediterranean) -- No reservations -- this is a casual place. Supposed to be an 8 minute walk from the hotel. Let's meet at 6:20pm in the Crowne Plaza lobby. I have chin-length brown hair and probably will be holding a paper scribbled with 'falafel.'<br />
<br />
* Emily Lynema (leader) - v<br />
* Christie Peterson - n<br />
* James Stuart - v<br />
* Emily Shaw - n (emilyfshaw at gmail dot com)<br />
* Ian Chan - n (ichan@csusm.edu)<br />
* Zeno Tajoli - n<br />
* '''Capped at 6'''<br />
<br />
[http://www.jaipurchicago.com/ Jaipur] (Indian; Reservation made for 6 at 6:30)<br />
-- Let's meet in the crowne plaza lobby @ 6:15; it's supposed to be a 6 minute walk<br />
<br />
* Andrew Darby (leader) - v<br />
* Josh Wilson (joshwilsonnc at gmail) - n<br />
* Tim Thompson - n<br />
* Mariela Hristova - n<br />
* ryan hess - n<br />
* Patrick Feeley - n<br />
* '''Capped at 6'''<br />
<br />
[http://lasardine.com/ La Sardine] (French)<br />
<br />
[http://www.mythaitakumi.com/index.html MyThai Takumi] (Japanese Thai) Reservation at 6:15. Meet in the hotel lobby at 6 pm. Look for the women in a trench coat and hat.<br />
<br />
*Becky Yoose (leader) b dot yoose at gmail - v<br />
*May Chan - n<br />
*David Anderson - newby<br />
*Terry Brady - new<br />
* Dave Menninger - n<br />
*Shawn Carraway -n<br />
* '''Capped at 6'''<br />
<br />
[http://www.nellcoterestaurant.com/ Nellcôte] (French)<br />
<br />
[http://chicago.provincerestaurant.com/ Province] (American with Central/South American/Spanish influence)<br />
<br />
[http://thepublicanrestaurant.com/ The Publican] (Seafood)<br />
<br />
* Jay Luker (eater) - v - Rezzie is for 8pm<br />
* <del>Mark Matienzo (tweeter) - v</del> started a new newcomer dinner!<br />
* Devon Smith (pickle eater) - repeat offender<br />
* Chris Sharp (dead horse beater) - v<br />
* Michael B. Klein (greeter) - v<br />
* Bill McMillin (meeter) - n<br />
* Tom Johnson (treater) -v<br />
* '''Capped at 6'''<br />
<br />
[http://saigonsisters.tumblr.com/ Saigon Sisters] (Vietnamese) Reservation for 6:15, meet in hotel lobby at 6. I am the one who has been running around in pink tights all day.<br />
* Margaret Heller - v and leader<br />
* Sharon Clapp - n<br />
* Meghan Finch - n<br />
* James Griffin - n<br />
* Maura Byrne - n<br />
<br />
<br />
[http://www.thaiurbankitchen.com/ Thai Urban Kitchen] (Thai, sushi)<br />
<br />
[http://www.trattoriaisabellachicago.com/rest.html Trattoria Isabella] (Italian)<br />
<br />
[http://www.vivo-chicago.com/homepage-2 Vivo] (Italian) <br />
<br />
[http://www.wishbonechicago.com/dining/westloop/ Wishbone] (Southern Reconstruction)<br />
<br />
* Rachel Shaevel (herder, self-proclaimed dictator, and reservation maker) - n (we're on for 6:15! Meet by the women's restroom when the sessions are over.)<br />
* Myrna E Morales (follower) - n<br />
* Sarah Thorngate - n<br />
* Steven Marsden - n<br />
* David Lacy - v<br />
* Luke Gaudreau - n<br />
* '''Capped at 6'''<br />
<br />
'''Restaurants between .5 miles and .75 miles of the hotel'''<br />
<br />
[http://currentsontheriver.com/ Currents on the River] (Eclectic)<br />
<br />
[http://n9ne.com/ N9NE Steakhouse] (Steak)<br />
<br />
[http://www.verachicago.com/menu Vera Chicago] (Spanish)<br />
<br />
<br />
'''Restaurants between .75 miles and 1 mile of the hotel'''<br />
<br />
[http://www.theberghoff.com/default.aspx The Berghoff] (German)<br />
* Declan Fleming - v (leader) I checked reservations, and for 6 people, the first time open after the conf is 7:30, so I grabbed that.<br />
** Let's meet in the lobby at 7p and walk over!<br />
* Dave Green - n <br />
* Steven Villereal - n<br />
* Peter Murray - v<br />
* Trey Terrell - n<br />
* Mike Giarlo - v<br />
* '''Capped at 6'''<br />
<br />
[http://www.yelp.com/biz/frontera-grill-chicago Frontera] (a Rick Bayliss Mex-American restaurant) Reservations are for 7:30, so perhaps the group could get a drink in the lobby beforehand. Either way, we'll depart at 7pm.<br />
: (''note: the drinks at the bar at frontera are very tasty.'')<br />
*Dan Suchy (leader and over-eater) - v<br />
*Matt Critchlow - v<br />
*Carmen Mitchell - v<br />
*Maureen Callahan - n<br />
*David Cliff - n<br />
* Patrick Berry - 3rd year red-shirt freshman<br />
* '''Capped at 6'''<br />
<br />
[http://www.nativefoods.com/ Native Foods] (Vegan) lots of vegan, vegetarian, gluten free options. No reservations needed. We could meet near the convention center or Daley library around 6 and take the train together. Lots of places to get drinks afterwards. <br />
<br />
I will wait at 5:30 at outside the UIC forum for anyone who wants to meet here. We'll pick up everyone else at Daley library at 6, then walk to the train station together. <br />
<br />
*Annie Pho(potential leader) - n <br />
*Lauren Magnuson - n<br />
*Bennett Magnino - n (meeting outside the Daley library sounds good)<br />
*Kelly Thompson - n<br />
*Audrey Altman - n<br />
*Mackenzie Brooks - n<br />
*Steven Bassett - n (Can't wait! Native Foods is awesome!).<br />
* '''Capped at 7''' Unless you can handle more folks!<br />
<br />
'''Restaurants more than 1 mile from the hotel'''<br />
<br />
<br />
[http://www.greenzebrachicago.com/index.html Green Zebra] (Vegan)<br />
<br />
[http://honkytonkbbqchicago.com/ Honky Tonk Barbeque] (BBQ) ---- I'm interested in Game Night this evening, so I'll make reservations for early dinner at lunch time (when there's some hope of the HT answering the phone). Please let me know if 6:30 is not OK. Lets leave from the UIC Library (front door) at 6:10. It's a moderate walk (a bit less than a mile) from campus; I also have a car, and can drive a couple people if you want.<br />
*Allan Berry (leader) - n<br />
*Jason Raitz - n (The #60 bus looks like it would save those of us with a bus pass the walk.)<br />
*Brian Wu - n (pwu14 at illinois dot edu)(EDIT: Plans sound good. I am also interested in game night. If somehow we don't make it, I have a 4 player game in my hotel room.)<br />
*Gary Maixner - n<br />
*Keith Nickum -v<br />
*<br />
* '''Capped at 6'''<br />
<br />
[http://www.karynraw.com/cooked Karyn’s Cooked] (Vegan)<br />
<br />
[http://www.latabernatapas.com/ La Taberna Tapas] (Mediterranean)<br />
<br />
[http://www.morganschicago.com/ Morgan's on Maxwell] (Pub food)<br />
<br />
[http://www.chezjoelbistro.com/ Chez Joël] (French/Tangiers food) I am leaning towards an early dinner of 6:15 as I have to take-off to make sure the Game Night takes off without a hitch. So leave the conference hotel by 5:45 if it is walk weather or 6PM if it is taxi weather.<br />
<br />
* Francis Kayiwa (knackered leader) - v<br />
* Megan O'Neill Kudzia - n<br />
* Esther Verreau - n<br />
* Michael Neidhardt - n<br />
* Rikke Willer - n<br />
* Esme Cowles - v<br />
* '''Capped at 6'''<br />
<br />
=== Veg*n Dinner ===<br />
<br />
Let's have dinner at a veg*n-friendly place one night of the conference. Folks of all eating styles welcome.<br />
<br />
Max *6* people per party this year.<br />
<br />
'''Party #1: Chicago Diner''', Wednesday Night http://www.veggiediner.com/ "meat free since '83" <br />
Will they easily be able to accommodate 6 folks walking in?<br />
We'll plan on meeting in the conference hotel at 6pm and taking the 8 bus up there (3411 N. Halsted St Chicago, IL 60657). <br />
# Jason Ronallo (jronallo@gmail.com)<br />
# Linda Ballinger (linda dot ballinger at gmail)<br />
# May Chan (msuicat at gmail dot com)<br />
# Demian Katz (demian DOT katz AT villanova DOT edu)<br />
# David Uspal (david dot uspal at villanova dot edu) In for the Country Fried StAEk and/or the Soul Bowl. Ex-Vegetarian (which may make it a crime for me to go), so if the list is full and you still want in, feel free to email me and I'll gladly turn over my spot to an actual Veg*n.<br />
# Cynthia Ng (cynthia dot s dot ng at gmail)<br />
Capped at 6<br />
<br />
=== Code4lib/Goose Island Brewing Pull Request ===<br />
'''When:''' Wednesday, 2/13, 8:00 PM to 11:00 PM<br />
<br />
More information and sign up at [https://code4lib2013-estw.eventbrite.com/|https://code4lib2013-estw.eventbrite.com/]<br />
<br />
=== Bourbon and barbecue ===<br />
'''When:''' Wednesday, 2/13, 7:00 PM<br />
<br />
Friend of mine tells me his cousin manages a Chicago restaurant, Chicago q, and I should go there and tell him my friend sent me. [http://www.chicagoqrestaurant.com/menus/dinner.php Menu] keeps talking about artisanal barbecue and extensive bourbon options. DONE.<br />
<br />
Reservation is at 7 for a party of 8. Add yourselves. <br />
<br />
We can take the number 20 bus to the Red Line. We should plan to meet in the lobby at 6:10; that way we can work with the bus tracker and make a leisurely trip over. <br />
<br />
<br />
<br />
* Andromeda Yelton<br />
* Chris Day [cday2 at saic.edu]<br />
* Abigail Goben <br />
* Rosalyn Metz [rosalynmetz at gmail dot com]<br />
* Dileshni Jayasinghe [d dot jayasinghe at utoronto dot ca]<br />
* Ray Mathew<br />
* Dre (Barbecue, yes. Bourbon... well, we'll see.) akorphan at ncsu.edu<br />
* Sean Chen schen at law.duke.edu<br />
<br />
=== Non-beery get together ===<br />
'''When:''' Wednesday, 2/13, Meet at hotel lobby at around 6:30 (and take public transport over to the park) OR meet us at the rink at 6:45, skating rink closes at 8 PM<br />
<br />
'''Where:''' [https://www.cityofchicago.org/city/en/depts/dca/supp_info/ice_skating_at_themccormicktribuneicerink.html McCormick Tribune Ice Rink]<br />
<br />
'''Contact:''' @dchud, @ranti, @yo_bj (b dot yoose at gmail), @wendyrlibrarian<br />
<br />
'''Cost:''' $10 skate rental, people watching free<br />
<br />
Come and (attempt to) skate with us! This is also a good people watching opportunity, so if you don't want to skate, there will be places to hang out around the rink and the park. There is a [http://www.parkgrillchicago.com/cafe/food-menu cafe] near the rink as well, with hot drinks and food.<br />
<br />
FYI - For those of you who want something else to munch on while hanging out, there's a [http://www.garrettpopcorn.com/chicago-locations/4-east-madison-street/ Garrett Popcorn Shop] a couple blocks away.<br />
<br />
# Chris Sharp (indicating interest)<br />
# Becky Yoose (ready to fall on her butt repeatedly for the entertainment of others)<br />
# Peter Murray<br />
# Shawn Carraway<br />
# Karen Coombs<br />
# Michael Levy<br />
# Christie Peterson<br />
# Andrew Pasterfield<br />
# Virginia Schilling<br />
# Al Cornish<br />
# Sibyl Schaefer<br />
# Kalee Sprague<br />
# Luis Baquera (ready to distract everyone with his own fantastic wipeouts while Becky composes herself)<br />
# Maccabee Levine<br />
# Sarah Shealy (I'm pretty sure I'll fall spectacularly as well :) )<br />
# Emily Lynema (interested!)<br />
# Gabriel Farrell<br />
<br />
=== Flying Trapeze ===<br />
'''When:''' Monday, 2/11, TBD<br />
<br />
'''Contact:''' rosalynmetz at gmail dot com<br />
<br />
'''Class is full.'''<br />
<br />
No this is not a joke. If you haven't heard Rosy is an aspiring trapeze artists and wants to bring the fun to her friends in Code4Lib. There is a trapeze rig in Chicago and she plans on visiting it and hopes that some of you can come along as well. If its your first time taking a trapeze class, they'll start you off learning [http://www.youtube.com/watch?v=_oqPi_zuX7A a knee hang] and depending on how that goes you might be able to catch it at the end of class. If you have any questions about whether or not this is for you, [http://chicago.trapezeschool.com/classes/trapeze.php TSNY Chicago's website] should have the answer, if not feel free to contact Rosy.<br />
<br />
Trapeze classes are $57, last 2 hours, and are limited to 10 people. Currently TSNY Chicago hasn't release their class schedule for February -- they should be doing that around Jan. 1. If we can get enough people interested before then, we can buy out a whole class. If not it'll be first come, first serve (along with the general public).<br />
<br />
If you're interested in signing up, feel free to add your name and contact info to the list below.<br />
<br />
'''''Sign Up List'''''<br />
# Jay Luker (first!)<br />
# Bill McMillin<br />
# Bess Sadler<br />
# Karen Coyle<br />
# Sibyl Schaefer<br />
# Rosalyn Metz (because I'm organizing)<br />
# Alicia Cozine<br />
# Gabriel Farrell<br />
<br />
=== Game Night! ===<br />
<br />
See the http://wiki.code4lib.org/index.php/2013_game_night page for the latest details and to sign up for individual games or add games you're willing to lead/teach!<br />
<br />
<br />
<br />
<br />
Moved this from idea to an actual event. Still getting some details, but here's what we know:<br />
<br />
Game Night! Type of games might vary due to interest and what people bring. Looks like interest right now is mostly on light to mediumish games with a dash of abstracts ;). <br />
<br />
<br />
Rough Schedule:<br />
* 7:30 setup<br />
* 7:45 start playing games!<br />
* 10:00 start winding down (don't start new games)<br />
* 10:30 all done, turn off the lights<br />
<br />
* I highly recommend that people walk in groups to get back to their respective lodgings. I'll ask folks still around at the end to help me clean up so we can walk back to the conference hotel*<br />
<br />
Please bring your badge with. (You don't need to wear it on the way, but that'll help us make sure everyone in the room is supposed to be there.)<br />
<br />
We have a conference room (1-470) at the UIC library (Richard J. Daley Library, 801 S. Morgan, Chicago) reserved for 7:30 on Tuesday the 11th. I'll try to show up at the lobby and hang out there for at about 7:15. I'll be the guy with a code4lib nametag and a box of games ;). Not sure how late we'll play, it looks like the library is open till 1:00am, but I suspect I will for now put a rough ending time of 11pm. <br />
<br />
(Note, there's also some discussion on Cards Against Humanity. I will try to make sure there's an alternative game, but I don't know if I want to prohibit any games. I would say though to remember to be respectful and courteous to those around you. I will probably be pondering this issue for a while)<br />
<br />
<br />
The original list of people who signed up is below.<br />
<br />
I (Jon Gorman) will bring some board games and pick up some cards. Add your name to the list below if you're interested in attending. Also not if you can bring games. Bringing games is NOT REQUIRED. If you can bring a game you can teach, that's great and will make sure we're not just stuck playing the games I bring.<br />
<br />
(I've added some comments to the game lists below)<br />
* jtgorman, aka Jon Gorman: I'll bring Time's Up: Total Recall, Tsuro, Hey, That's My Fish, Hive, and some more I haven't decided on yet. (My profile over at http://www.boardgamegeek.com/ is jtgorman as well if you want to browse my games and make requests)<br />
* yo_bj: I have some games I can bring as well (Kill Doctor Lucky, Fluxx, Godzilla: Stomp, Munchkin Zombies, etc.). Monday doesn't have anything major planned... <br />
*danwho: I 'll bring the Cards Against Humanity set.<br />
*escowles (Mon/Tue preferred): I've got lots of games I could bring like Settlers of Catan, Carcassonne, Ticket to Ride, Age of Renaissance, Elfenland, Agricola, Le Havre, Smallworld, RoboRally, etc. etc. <br />
** Take your pick! All good games. I'll try to finalize my list of games before Friday - JonG <br />
*jen_young: I'm local and I have quite a few games. Just about every version of Fluxx, Bananagrams, Gloom, Munchkin Cthulu,Cards Against Humanity, Apples to Apples, Risk, Last Night on Earth, etc.) <br />
**All good games! If you don't mind bringing a box that would be awesome. I particularly like Apples to Apples, Last Night on Earth and Gloom - JonG<br />
* decasm: Interested in Go (aka igo, weiqi, baduk) anytime, not just game night. I can do Catan as well. (And as much as I love it, Cards Against Humanity is probably a violation of the new Code of Conduct.) <br />
** I look forward to losing my first game of Go to you ;) - JonG<br />
** I'd love to learn Go. <del>Perhaps after the newcomer dinner?</del> Oof... won't make for Tues. But would still be interested to learn. --ranti.<br />
* csharp: I'm interested in playing games - whatever people bring. I almost always travel with a pack or two of playing cards ;-). Monday or Tuesday nights are fine.<br />
* moneill: I would love to join in! I have a version of Catchphrase floating around somewhere, and I think I have Battleship...I need to go weed around in that drawer and see what else presents itself. Tuesday would be my preferred night, but I will make it work! <br />
** Don't worry too much about bringing a game if transportation is a problem. One thing I've done w/ stuff like catchphrase is not take the box but to put pieces and cards in a bag - JOn G<br />
* demiankatz: I'm always up for a game. I'm hoping to travel light so probably shouldn't bring anything, but if there's a local game shop, I might be persuaded to pick up something new as a souvenir. <br />
** Don't worry, I think there will be plenty of games - JonG<br />
* sekjal: I've got [http://boardgamegeek.com/boardgame/36218/dominion Dominion], [http://boardgamegeek.com/boardgame/68448/7-wonders 7 Wonders], [http://boardgamegeek.com/boardgame/30933/bang-the-bullet Bang!], [http://boardgamegeek.com/boardgame/18333/ecofluxx EcoFluxx] and [http://boardgamegeek.com/boardgame/116/guillotine Guillotine] that I can bring. ++ on Cards against Humanity! Prefer non-conflict with beer night. <br />
** Also all good games. I have 7 Wonders, but can bring some other games if you bring that. - Jon G<br />
* arty: so totally interested. Unfortunately, I have no games to contribute.<br />
** No prob.<br />
* sanderson: I would be interested. I can bring [http://boardgamegeek.com/boardgame/478/citadels Citadels] (2-7 players)<br />
** Citadels would be awesome and means I don't have to bring it ;) - JonG<br />
* dvdndrsn: Definitely in! Can bring Innovation, Tichu, Dominion, but Cards Against Humanity sounds good. <br />
** I'll put in a vote for Tichu, heard good things about it - Jon G <br />
* smkiewel: I'm likely to join. Can bring Arkham Horror and Munchkin.<br />
** Arkham Horror seems rather bulky to travel with, but if you want to play bring it ;) - Jon G<br />
** mbutler: If someone actually brings Arkham Horror I'd throw down. Otherwise, whateve. <br />
* jkwilson: I'd like to attend Monday or Tuesday. I have a bunch of games but I'd prefer not to travel with them, and anyway it sounds like they're covered above. I'll bring the 5-6 player Catan extension.<br />
* ejlynema: Interested, but will probably attend Newcomer dinner on Tuesday. Like Dominion and 7 Wonders, but probably don't have room to bring in suitcase. Anyone bringing Tsuro? <br />
** I can bring Tsuro - Jon G<br />
* Christie Peterson (save4use): Also interested, but also probably attending newcomer dinner on Tuesday. Can bring [http://boardgamegeek.com/boardgame/11/bohnanza Bohnanza] and one deck of [http://en.wikipedia.org/wiki/Set_%28game%29 Set]. <br />
**Bohnanza and Set would be awesome - JonG<br />
**Done! I will bring them both -- C<br />
* dgcliff: I'd be interested. Can bring Ticket to Ride.<br />
* mbklein: definitely interested. Will check on my (currently unpacked) games. I am dying to play Cards Against Humanity. If we can't find a way to reconcile it with the Code of Conduct, we need a different Code of Conduct.<br />
** Considering that this is a public event, and that no one knows everyone's sensitivity levels in the room, it might not be a good idea to break out a crass, adult version of apples to apples in the middle of the gaming room. :cP (yo_bj)<br />
* duspal: In. My board game collection is small but mighty (Arkham Horror, Catan, Vampire: Prince of the City, Deadlands: Battle for Slaughter Gulch, Arabian Nights, Diplomacy, Shogun, and Cosmic Encounter off the top of my head, amongst a few others). Let me know ahead of time if anyone is interested, since they're all relatively big... <br />
** If you really want to play Cosmic Encounter, I can bring my copy (Fantasy Flight edition, 3 expansions), just let me know - JonG<br />
*librarywebchic: I'm willing to bring a set and teach folks how to play Majhong. Need at least three to play though.<br />
**beatricep: Uno gets no respect. ;-) @librarywebchic: I have always wanted to learn to play Majhong. If you're still bringing it, I'm in!<br />
** Agreed, I don't know Majhong and I love learning new games. - JonG<br />
** I actually know a few different rule sets. It's too bad I don't have a travel set or I'd bring a 2nd one -Arty<br />
** I'm local and can bring a mahjong set. I've had no one to play with for years, so have probably forgotten how. -Linda B<br />
* jcraitz: I'm in after the newcomer dinner. I'll bring Citadels and Bang! <br />
**I think someone higher in the list offered to bring citadels, but won't hurt to have two copies just in case one of you don't show ;) - JonG<br />
**Aww no. left my games at the office. Looks like I'll have to jump in someone else's game.<br />
* julia: I'll be the freeloader who showed up and didn't bring any games.<br />
* kenirwin: interested in attending<br />
* sdellis: attending<br />
* ianc: interested in attending, a little rusty but definitely up for a couple rounds of Mahjong, also want to try something new too!<br />
* haschart: Interested in attending, if I can make it work with the newcomer dinner. Big fan of Dominion lately, but probably cannot bring it `cause the "Big Box" with the base game and two expansion sets is bigger than my suitcase. I could bring "Race for the Galaxy" if there's any interest.<br />
* jessebrown: Interested in attending. I can bring Set and Zombie Fluxx.<br />
* terrywbrady: I would like to attend<br />
* dan fehrenbach (dnfehren): I would like to attend, can bring Pandemic if anyone is interested.<br />
* dileshni: interested in attending. <br />
* Corey Harper: definitely interested in attending if space allows.<br />
* saverkamp: interested in attending.<br />
* Emily Shaw: I like games. <br />
* Alan Dyck: I play Carcassonne and Munchkin among others. I see those listed so I'm bringing a game some friends and I have been creating: Wandering Monster.<br />
* Heidi Frank (hf36@nyu.edu) - I love card games like gin/rummy, but am open to anything.<br />
* Sibyl Schaefer - attending, and will bring anything that fits in my carry-on<br />
* cpsarason - I'm up for whatever!<br />
<br />
-- *Please, please, please, if you're signing up on this list, also sign up for a paritcular game slot to start out the evening or put your game in: http://wiki.code4lib.org/index.php/2013_game_night<br />
we're having so many people sign up after Jan. 14th we're in risk of overflowing the room. (I should have put in a cap limit, but given how late I realized this, I haven't *<br />
<br />
I have to confess, I started trying to organize what games certain people were bringing, but it got confusing fast and I don't want anyone to feel compelled to bring anything or feel bad if they can't make it. So if there is something you're dying to play, let me know and I'll try to bring it if I have it.<br />
<br />
== Social Map - Places of Interest==<br />
<br />
https://maps.google.com/maps/ms?msid=213549257652679418473.0004ce6c25e6cdeb0319d&msa=0<br />
<br />
== Layar: augmented reality Code4Lib view of Chicago ==<br />
<br />
There's a "Code4Lib 2013" layer in [http://www.layar.com/ Layar], an augmented reality app that runs on both Android and iOS. You can use it to scan around the city to see two kinds of things: 1) tweets using the #c4l13 or #code4lib hashtag (if the tweets are geolocated so they can be<br />
nailed to a point) and 2) points of interest from the [https://maps.google.com/maps/ms?msid=213549257652679418473.0004ce6c25e6cdeb0319d&msa=0 shared Google Map]. <br />
<br />
To use it:<br />
<br />
* install Layar on your phone<br />
* run it and click to go into Geo Layers mode<br />
* search for "code4lib 2013"<br />
* launch the layer and look around<br />
<br />
See Code4Lib people and events overlaid on top of Chicago, in real time! See an alternate view of the city that's all about libraries and coders!<br />
<br />
To make your own tweets appear, use the #c4l13 hashtag and make sure the tweet is geolocated. In Twitter's client you need to do this by enabling geolocation in settings and then enabling it for each tweet.<br />
<br />
Source code running this: [https://github.com/wdenton/laertes Laertes]. Bill Denton set it up and is very curious to find out if it's useful, so let him know if you try it out.<br />
<br />
== Local Events ==<br />
Events Listings<br />
* Chicago Reader http://www.chicagoreader.com/<br />
* The City of Chicago’s Events Guide: http://www.choosechicago.com/ <br />
* Metromix Chicago: http://chicago.metromix.com/events <br />
* Timeout Chicago: http://timeoutchicago.com/<br />
* Chicago Studio Club's [http://www.google.com/calendar/embed?title=LIVE%20MUSIC%20in%20Chicagoland%20via%20Chicago%20Studio%20Club!%20&height=1000&wkst=1&hl=en&bgcolor=%2399ff99&src=info%40chicagostudioclub.net&color=%237A367A&ctz=America%2FChicago Live Music Google Calendar]<br />
<br />
== Local Food ==<br />
== Local Drinks ==<br />
==Chicago Events Feb 10-14==<br />
<br />
=== Sunday February 10===<br />
Theater - [http://www.neofuturists.org/ Too Much Light Makes the Baby Go Blind] "...with its ever-changing "menu," is an attempt to perform 30 plays in 60 minutes. " 7pm.<br />
<br />
Theater - [http://www.chicagoreader.com/chicago/chunks/Event?oid=8557720 Chunks] : Funny, Heartbreaking, Gross. 7pm & BYOB!<br />
<br />
===Monday February 11===<br />
<br />
Music - [http://www.hideoutchicago.com/event/208497-robbie-fulks-michael-miles-chicago/ Robbie Fulks at the Hideout]<br />
<br />
[http://fedora4lib.org/ fedora4lib] - 7 pm to whenever<br />
<br />
===Tuesday, February 12===<br />
<br />
Concert - [http://www.thefatbabies.com/ The Fat Babies] playing at an awesome venue, [http://greenmilljazz.com/ The Green Mill].<br />
<br />
[http://fedora4lib.org/ fedora4lib] - 7 pm to whenever<br />
<br />
===Wednesday, February 13===<br />
===Thursday, February 14===<br />
Tour of the [http://www.newberry.org/ Newberry Library] -- 3:30 p.m.<br />
This will be a special tour for Code4Lib attendees, so please sign up below if you are interested, as I'll need to give the tour guide an estimate of how many people will come. Details on how to get to the Newberry will follow. Questions? Contact ballingerl at newberry dot org<br />
<br />
'''''Directions: '''''<br />
The Newberry is at 60 W Walton St. It could take half an hour to get there from the conference hotel via CTA, so those of you who wish to take public transit as a group can meet me in the hotel lobby by 3:00. We will then go to the UIC-Halsted El stop (5 blocks from hotel), change trains in the Loop, then walk 3-4 blocks to the Newberry. Otherwise, plan on making your preferred way there and meet in the Newberry lobby by 3:30.<br />
<br />
'''''Sign Up List'''''<br />
# Michael Doran - doran@uta.edu<br />
# William Denton - wtd@pobox.com<br />
# Wayne Schneider - wschneider@hclib.org<br />
# Matt Cordial - rev3lator [at] gmail.com<br />
# ryan hess - mhess8 [at] depaul.edu<br />
# [[User:ianc|Ian Chan]] ichan@csusm.edu<br />
# Richard Aroksaar - richard_aroksaar@nps.gov<br />
# [name] - [email address]<br />
# Laurie Lee Moses - lmoses [at] colum.edu<br />
# Ray Schwartz - schwartzr2@wpunj.edu<br />
<br />
== Music ==<br />
<br />
There's a [http://www.rdio.com/people/wdenton/playlists/2229053/Code4Lib_2013_in_Chicago/ Code4Lib 2013 in Chicago] collaborative playlist on Rdio. If you're a subscriber, have a look, and add something you think everyone would like to hear or use as their personal soundtrack while they're hacking and exploring Chicago.<br />
<br />
<br />
<br />
[[Category:Code4Lib2013]]</div>No replyhttps://wiki.code4lib.org/index.php?title=2013_social_activities&diff=365702013 social activities2013-02-12T18:49:09Z<p>No reply: /* Newcomer Dinner, Tuesday 2/12 */</p>
<hr />
<div>== Ideas ==<br />
<br />
* Aviary: super-crazy cocktails. http://www.molecularrecipes.com/molecular-mixology/aviary-cocktails/ . List your name if you're interested, whether Sunday, Monday, and/or Tuesday (after newcomer dinners) work, and whether you're just interested in stopping by, or doing a 7 cocktail tasting flight.*<br />
** statsfool: sunday/monday/tuesday, either drinks or flight.<br />
** Amyhannah: monday/tuesday, drinks, probably not the flight.<br />
** anarchivist: sunday/monday, prefer drinks over flight but could be convinced<br />
** [[User:highermath|highermath]]: monday (could use 10 cocktails after Drupal subCon, I am sure). Uber now works in Chicago, so I would do the flight.<br />
** [[User:pberry|pberry]]: any night but Wednesday (that's Goose Island night) and I'd be up for drinks or flight, although leaning away from flight.<br />
** [[User:thatandromeda|thatandromeda]] oh my gosh yes, any time, probably not the flight.<br />
** [[User:Gdave|gdave]] beautiful site, I would be interested, Sun,Mon,Tues. either drink or flight.<br />
** [[User:shawnc12|shawnc12]]: sunday/monday, either drink or flight<br />
** wdenton: any night, either drink or flight<br />
** beatricep: sunday/monday drink, highly susceptible to flight by peer pressure..<br />
** ryan hess: sunday/monday drink or flight<br />
** infosoph: sunday/monday yes/yes!!<br />
** [[User:Pfeeley|Pfeeley]]: sunday/monday/tuesday, either drink or flight<br />
** [[User:Ksprague|Ksprague]]: tuesday, drink or flight<br />
** [[User:schwartzray|schwartzray]]: anything on any day<br />
* Brewery tour - some possible candidates would be Goose Island, Brew Bus http://www.chicagobrewbus.com/, Piece, Revolution, Half Acre.<br />
* Library field trips - because we're library geeks. Possible places include Newberry and Read/Write.--Read/Write Library confirmed for February 11.--Newberry Library confirmed for February 14.<br />
* Art Institute of Chicago - Only open until 5pm, but possible for people coming in early enough on Sunday. There seems to be enough interest here to actually have a group, when and where should we meet? I added my email so that we could discuss details off the wiki.<br />
** escowles: I'm getting in around noon on Sunday, and interested in this.<br />
** pgrayove at gmail dot com: I'm getting in around noon on Sunday too. I'm interested.<br />
** ranti: And I am. <br />
** tshearerlib: Coming in at around the same time and hope to get to the museum by 1:00. Lunch first?<br />
* Local Option http://localoptionbier.com/ - So you've heard of Hopleaf, you've heard of Maproom. Come to Chicago's *ahem* best kept secret for good food and an evening session on Monday. We will need a tally to make requisite arrangements. Target for arrival at bar: 7ish. Probably a group gathering to head north around 6:30 in hotel lobby (if you want to take the #8 Halsted bus that is).<br />
** kayiwa<br />
** Linda Ballinger<br />
** Courtney Greene<br />
** John Pillans<br />
** +6 from NCSU incl one Bret Davidson<br />
** Megan Kudzia<br />
** Andrew Darby<br />
** erinrwhite<br />
** Will Clarke<br />
** Cody Hanson<br />
** Jesse Brown<br />
** Matt Cordial +1 (my friend and I were already planning a Monday trip here)<br />
** Ray Schwartz<br />
** Eric Larson<br />
** David Cliff<br />
** Ken Irwin<br />
** Dileshni Jayasinghe<br />
<br />
== Planned Events ==<br />
<br />
===Read/Write Library Field Trip, Monday 2/11===<br />
Field trip to the [http://readwritelibrary.org/ Read/Write Library] 6:30PM-9PM <br />
<br />
Drop in whenever during this time.<br />
<br />
Come help catalog the Read/Write Library catalog and hack on the library catalog. We will get food or go to a nearby restaurant depending on interest. We will also invite friends from Code for America to hang out and talk civic data. Bring your laptop along if you have one.<br />
<br />
Let us know if you are coming so we can figure out food:<br />
* Margaret Heller<br />
* Ranti Junus<br />
* Wayne Schneider<br />
* jrochkind will try to make it<br />
* emily shaw (may be a little late)<br />
* <strike>kenirwin - bailed on acct of pre-conf brain death</strike><br />
* Andromeda - yes, unless someone gets Aviary reservations<br />
* Chris Clement - may attend<br />
(hey, there are great bars in that neighborhood!)<br />
* wdenton<br />
<br />
'''Directions to the library from UIC:'''<br />
<br />
''Bus''<br />
<br />
Take the #8 Halsted Bus north to Chicago (Bus will say "#8 Halsted/79th North to Broadway/Waveland")<br />
Take the #66 Chicago Bus west to California (Bus will say either "#66 Chicago west to Austin" or "#66 Chicago West to Pulaski." You can take either one because both Austin and Pulaski are further west than we are so both stop at California)<br />
The Chicago bus stops on the west side of California, which is the side of the street we're on. On California, walk a block north to Walton.<br />
<br />
''Train + Bus (slightly faster/more reliable, but only by about 5-10 minutes)''<br />
<br />
Walk to the UIC/Halsted Blue Line <br />
Take the O'Hare train (toward the Loop) and go all the way through the Loop and back west. Get off at Chicago and use the exit that says "North side of Chicago Ave" (or something similar — I don't remember exactly).<br />
Take the #66 Chicago Bus west to California (Bus will say either "#66 Chicago west to Austin" or "#66 Chicago West to Pulaski." You can take either one because both Austin and Pulaski are further west than we are so both stop at California)<br />
The Chicago bus stops on the west side of California, which is the side of the street we're on. On California, walk a block north to Walton.<br />
<br />
=== Newcomer Dinner, Tuesday 2/12 ===<br />
<br />
First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating <strike>discussions about</strike> demonstrations of the many uses of <strike>bacon</strike> <strike>dongles</strike> XML.<br />
<br />
Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!<br />
<br />
'''Plans'''<br />
* When: Tuesday evening (2/12)<br />
* Time: 6 PM (ish) or whenever you can get your group together<br />
* Mastermind (if you have any questions): [mailto:yoosebec@grinnell.edu Becky Yoose]<br />
<br />
''Guidelines:''<br />
*Max of '''6''' per group<br />
**Please, no waitlisting<br />
*ID yourselves so we can get a good mix of new people and veterans in each group<br />
**New folks - n<br />
**c4l vets - v<br />
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group''')<br />
**Leader duties<br />
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library tech type folks<br />
***Herd folks from hotel to restaurant (know where you're going!)<br />
<br />
<br />
'''Restaurants'''<br />
<br />
<br />
'''Restaurants within .25 miles of the hotel'''<br />
<br />
[http://www.athenarestaurantchicago.com/index.php Athena] (Greek)<br />
<br />
* Al Cornish - v (leader)<br />
* Carolyn Cole - n<br />
* Dileshni Jayasinghe - v<br />
* Will Clark - n<br />
* Adam Constabaris - v<br />
* Patrick Hogan - n<br />
* '''Capped at 6'''<br />
<br />
[http://www.dinerestaurant.com/ Dine] (Contemporary)<br />
<br />
<del>[http://www.girlandthegoat.com/ Girl and the Goat] (American) Top Chef fans take note! This is Stephanie Izard's award-winning resto.</del> Totally booked.<br />
<br />
[http://littlegoatchicago.com/ Little Goat]<br />
<br />
Izard just opened a diner across the street from G&G that is walk-in only. (very good, probably a wait but they also have a bar in the back --wickr)<br />
<br />
We'll meet in the lobby of the hotel at 6:30 and walk over. No reservations.<br />
<br />
* Mark Matienzo (leader) - v<br />
* Andromeda Yelton - n<br />
* Hillel Arnold (intern) - veteran newbie<br />
* Kelly Lucas - n<br />
* Chris Clement - n<br />
* Erin Fahey -n<br />
* Beatrice Pulliam - n <br />
* '''CAPPED AT 7'''<br />
<br />
[http://www.haymarketbrewing.com/ Haymarket Pub & Brewery] (Pub food) - Reservations at 6:30pm. Meet in conference hotel lobby at 6:10pm<br />
<br />
* Ryan Wick (leader) - v<br />
* Sean Purcell - v<br />
* Dan Fehrenbach - n<br />
* Pierre Nault - n<br />
* Minh-Quang Nguyen - n<br />
* Matt Bernhardt - n<br />
* David Gonzalez - n<br />
* '''Capped at 7'''<br />
<br />
[http://www.karynsongreen.com/ Karyn’s on Green] (Vegan)<br />
Completely vegan and close to the conference hotel. We'll meet in the conference hotel at around 6:45 (reservation at 7:00 for 6). Google maps says it is a 5 minute walk.<br />
<br />
*Jason Ronallo (leader)- v<br />
*Alicia Cozine - n<br />
*Mark Mounts - v<br />
*Amy Deschenes - n<br />
*Adam Strohm - n<br />
*Jacob Reed - n<br />
* '''Capped at 6'''<br />
<br />
[http://niarestaurant.com/nia-restaurant-mediterranean-cuisine/ Nia] (Mediterranean tapas)<br />
<br />
[http://www.pegasuschicago.com/index.php Pegasus] (Greek) - reservation at 6:30 for 6. We'll meet in the hotel lobby at 6:15 and walk down.<br />
*Erin White (leader) - v<br />
* Don Mennerich -n<br />
* John MacGillivray <br />
* Santi Thompson - n<br />
*<br />
*<br />
*'''Capped at 6'''<br />
<br />
[http://www.roditys.com/index.html Roditys] (Greek) -- Reservations made for 6:30pm. Let's meet in the hotel lobby at 6pm and walk over from there. Its ok if you're a bit late to the lobby, we'll wait. If you have any questions email Rosalyn (Rosy) rosalynmetz at gmail dot com<br />
<br />
* Rosalyn Metz (leader) - v<br />
* [[User:highermath|Cary Gordon]] - v<br />
* [[User:Jacobandresen|Jacob Andresen]] - n<br />
* Karen Miller - n<br />
* Dre - v<br />
* Mahria Lebow - n<br />
* '''Capped at 6'''<br />
<br />
'''Restaurants between .25 miles and .5 miles of the hotel'''<br />
<br />
Code4lib Chicago Celery Salt Society - [http://www.alsbeef.com/ Al's Beef]<br />
<br />
* Jason Casden (leader) - v - No reservations. We can walk from the hotel at 7.<br />
* Charlie Morris - n<br />
* Cory Lown - v<br />
* Carolina Garcia - n<br />
* Cody Hanson - n<br />
* Ken Varnum - v<br />
* '''Capped at 6'''<br />
<br />
[http://avecrestaurant.com/# Avec] (Small plate)<br />
Family-style small plate and tapas. Great Yelp reviews. We'll meet in the conference hotel at 6:00 <strike>6:45</strike> (they don't take reservations, but have stuff to sip on if there's a wait). Less than 10 minute walk from hotel.<br />
<br />
* Shaun Ellis (leader) - v<br />
* Jon Stroop - v<br />
* Paula Gray-Overtoom - n<br />
* Emily Zervas - n<br />
* Cynthia Ng - neither<br />
* Sarah Dooley - n<br />
* '''Capped at 6'''<br />
<br />
[http://www.babavillage.com/ Baba’s Village] (Indian/Pakistani)<br />
<br />
[http://blackbirdrestaurant.com/ Blackbird] (Contemporary)<br />
<br />
(Since the reservation is late, does anyone want to meet for drink in the hotel bar beforehand? There's really no place to wait at the restaurant, and there's no nice bar nearby that I can recall. cm)<br />
* Justin Coyne (reserver) - v - Reservation for Blackbird for 6 at 8:30pm (justin at curationexperts.com)<br />
* Matt Cordial - v<br />
* [http://wiki.code4lib.org/index.php/User:Camcclure Christine McClure - n]<br />
* Devin Higgins - n (devinhiggins at gmail)<br />
* Ken Irwin<br />
* Tad Merchant - n (tadoneus @ gmail)<br />
* '''Capped at 6'''<br />
<br />
[http://www.carnivalechicago.com/menu Carnivale] (Nuevo Latino)<br />
* Nettie Lagace (OpenTable says they can seat 6 at 8 pm or 6 pm - I'll reserve the 8 pm and will call directly this pm) - n/v<br />
* Rebecca Jones - n/v<br />
* Ben Burbridge - n<br />
* Andrea Schurr - n/v<br />
* Susan Price - n<br />
* James Staub - n > v<br />
* '''Capped at 6'''<br />
<br />
[http://decero.hellotacos.com/ De Cero] (Mexican)<br />
<br />
[http://www.dragonflymandarin.com/ Dragonfly] (Chinese, sushi)<br />
<br />
[http://giordanos.com/ Giordano's] (Chicago Style Pizza) This place should be able to handle multiple groups...<br />
<br />
* Andrew Nagy (leader) - v<br />
* Virginia Schilling - n<br />
* Jane Sandberg - n<br />
* Richard Aroksaar - n<br />
* Jesse Brown - n (jfbrown78 at gmail dot com)<br />
* Bob Haschart -v<br />
* Alicia Morris<br />
* Ayla Stein - n<br />
* Sharona Ginsberg - n<br />
* Andrew Myers - n<br />
* Jim LeFager - n<br />
<br />
Giordano's Group Z (three newbies welcome to join, including folks from above if you want). <br />
* Jonathan Rochkind (leader) -v<br />
* rsinger -v<br />
* ndushay -v<br />
* hnayak -n<br />
* Xiaoming Wang -n<br />
* Greg Murry -n<br />
* '''Capped at 6'''<br />
<br />
[http://www.grangehallburgerbar.com/ Grange Hall Burger Bar] (Local food)<br />
<br />
[http://www.idreamoffalafel.com/ I Dream of Falafel] (Mediterranean) -- No reservations -- this is a casual place. Supposed to be an 8 minute walk from the hotel. Let's meet at 6:20pm in the Crowne Plaza lobby. I have chin-length brown hair and probably will be holding a paper scribbled with 'falafel.'<br />
<br />
* Emily Lynema (leader) - v<br />
* Christie Peterson - n<br />
* James Stuart - v<br />
* Emily Shaw - n (emilyfshaw at gmail dot com)<br />
* Ian Chan - n (ichan@csusm.edu)<br />
* Zeno Tajoli - n<br />
* '''Capped at 6'''<br />
<br />
[http://www.jaipurchicago.com/ Jaipur] (Indian; Reservation made for 6 at 6:30)<br />
-- Let's meet in the crowne plaza lobby @ 6:15; it's supposed to be a 6 minute walk<br />
<br />
* Andrew Darby (leader) - v<br />
* Josh Wilson (joshwilsonnc at gmail) - n<br />
* Tim Thompson - n<br />
* Mariela Hristova - n<br />
* ryan hess - n<br />
* Patrick Feeley - n<br />
* '''Capped at 6'''<br />
<br />
[http://lasardine.com/ La Sardine] (French)<br />
<br />
[http://www.mythaitakumi.com/index.html MyThai Takumi] (Japanese Thai) Reservation at 6:15. Meet in the hotel lobby at 6 pm. Look for the women in a trench coat and hat.<br />
<br />
*Becky Yoose (leader) b dot yoose at gmail - v<br />
*May Chan - n<br />
*David Anderson - newby<br />
*Terry Brady - new<br />
* Dave Menninger - n<br />
*Shawn Carraway -n<br />
* '''Capped at 6'''<br />
<br />
[http://www.nellcoterestaurant.com/ Nellcôte] (French)<br />
<br />
[http://chicago.provincerestaurant.com/ Province] (American with Central/South American/Spanish influence)<br />
<br />
[http://thepublicanrestaurant.com/ The Publican] (Seafood)<br />
<br />
* Jay Luker (eater) - v - Rezzie is for 8pm<br />
* <del>Mark Matienzo (tweeter) - v</del> started a new newcomer dinner!<br />
* Devon Smith (pickle eater) - repeat offender<br />
* Chris Sharp (dead horse beater) - v<br />
* Michael B. Klein (greeter) - v<br />
* Bill McMillin (meeter) - n<br />
* Tom Johnson<br />
<br />
[http://saigonsisters.tumblr.com/ Saigon Sisters] (Vietnamese) Reservation for 6:15, meet in hotel lobby<br />
* Margaret Heller - v and leader<br />
* Sharon Clapp - n<br />
* Sean Crowe - n<br />
* Meghan Finch - n<br />
* Maccabee Levine - v<br />
* James Griffin - n<br />
* '''Capped at 6'''<br />
<br />
[http://www.thaiurbankitchen.com/ Thai Urban Kitchen] (Thai, sushi)<br />
<br />
[http://www.trattoriaisabellachicago.com/rest.html Trattoria Isabella] (Italian)<br />
<br />
[http://www.vivo-chicago.com/homepage-2 Vivo] (Italian) <br />
<br />
[http://www.wishbonechicago.com/dining/westloop/ Wishbone] (Southern Reconstruction)<br />
<br />
* Rachel Shaevel (herder, self-proclaimed dictator, and reservation maker) - n (we're on for 6:15!)<br />
* Myrna E Morales (follower) - n<br />
* Sarah Thorngate - n<br />
* Steven Marsden - n<br />
* David Lacy - v<br />
* Luke Gaudreau - n<br />
* '''Capped at 6'''<br />
<br />
'''Restaurants between .5 miles and .75 miles of the hotel'''<br />
<br />
[http://currentsontheriver.com/ Currents on the River] (Eclectic)<br />
<br />
[http://n9ne.com/ N9NE Steakhouse] (Steak)<br />
<br />
[http://www.verachicago.com/menu Vera Chicago] (Spanish)<br />
<br />
<br />
'''Restaurants between .75 miles and 1 mile of the hotel'''<br />
<br />
[http://www.theberghoff.com/default.aspx The Berghoff] (German)<br />
* Declan Fleming - v (leader) I checked reservations, and for 6 people, the first time open after the conf is 7:30, so I grabbed that.<br />
** Let's meet in the lobby at 7p and cab over (or would people rather walk?)<br />
* Dave Green - n <br />
* Steven Villereal - n<br />
* Peter Murray - v<br />
* Trey Terrell - n<br />
* Mike Giarlo - v<br />
* '''Capped at 6'''<br />
<br />
[http://www.yelp.com/biz/frontera-grill-chicago Frontera] (a Rick Bayliss Mex-American restaurant) Reservations are for 7:30, so perhaps the group could get a drink in the lobby beforehand. Either way, we'll depart at 7pm.<br />
: (''note: the drinks at the bar at frontera are very tasty.'')<br />
*Dan Suchy (leader and over-eater) - v<br />
*Matt Critchlow - v<br />
*Carmen Mitchell - v<br />
*Maureen Callahan - n<br />
*David Cliff - n<br />
* Patrick Berry - 3rd year red-shirt freshman<br />
* '''Capped at 6'''<br />
<br />
[http://www.nativefoods.com/ Native Foods] (Vegan) lots of vegan, vegetarian, gluten free options. No reservations needed. We could meet near the convention center or Daley library around 6 and take the train together. Lots of places to get drinks afterwards. <br />
<br />
I will wait at 5:30 at outside the UIC forum for anyone who wants to meet here. We'll pick up everyone else at Daley library at 6, then walk to the train station together. <br />
<br />
*Annie Pho(potential leader) - n <br />
*Lauren Magnuson - n<br />
*Bennett Magnino - n (meeting outside the Daley library sounds good)<br />
*Kelly Thompson - n<br />
*Audrey Altman - n<br />
*Mackenzie Brooks - n<br />
*Steven Bassett - n (Can't wait! Native Foods is awesome!).<br />
* '''Capped at 7''' Unless you can handle more folks!<br />
<br />
'''Restaurants more than 1 mile from the hotel'''<br />
<br />
<br />
[http://www.greenzebrachicago.com/index.html Green Zebra] (Vegan)<br />
<br />
[http://honkytonkbbqchicago.com/ Honky Tonk Barbeque] (BBQ) ---- I'm interested in Game Night this evening, so I'll make reservations for early dinner at lunch time (when there's some hope of the HT answering the phone). Please let me know if 6:30 is not OK. Lets leave from the UIC Library (front door) at 6:10. It's a moderate walk (a bit less than a mile) from campus; I also have a car, and can drive a couple people if you want.<br />
*Allan Berry (leader) - n<br />
*Jason Raitz - n<br />
*Brian Wu - n (pwu14 at illinois dot edu)(EDIT: Plans sound good. I am also interested in game night. If somehow we don't make it, I have a 4 player game in my hotel room.)<br />
*Gary Maixner - n<br />
*Keith Nickum -v<br />
*<br />
* '''Capped at 6'''<br />
<br />
[http://www.karynraw.com/cooked Karyn’s Cooked] (Vegan)<br />
<br />
[http://www.latabernatapas.com/ La Taberna Tapas] (Mediterranean)<br />
<br />
[http://www.morganschicago.com/ Morgan's on Maxwell] (Pub food)<br />
<br />
[http://www.chezjoelbistro.com/ Chez Joël] (French/Tangiers food) I am leaning towards an early dinner of 6:15 as I have to take-off to make sure the Game Night takes off without a hitch. So leave the conference hotel by 5:45 if it is walk weather or 6PM if it is taxi weather.<br />
<br />
* Francis Kayiwa (knackered leader) - v<br />
* Megan O'Neill Kudzia - n<br />
* Esther Verreau - n<br />
* Michael Neidhardt - n<br />
* Rikke Willer - n<br />
* Esme Cowles - v<br />
* '''Capped at 6'''<br />
<br />
=== Veg*n Dinner ===<br />
<br />
Let's have dinner at a veg*n-friendly place one night of the conference. Folks of all eating styles welcome.<br />
<br />
Max *6* people per party this year.<br />
<br />
'''Party #1: Chicago Diner''', Wednesday Night http://www.veggiediner.com/ "meat free since '83" <br />
Will they easily be able to accommodate 6 folks walking in?<br />
We'll plan on meeting in the conference hotel at 6pm and taking the 8 bus up there (3411 N. Halsted St Chicago, IL 60657). <br />
# Jason Ronallo (jronallo@gmail.com)<br />
# Linda Ballinger (linda dot ballinger at gmail)<br />
# May Chan (msuicat at gmail dot com)<br />
# Demian Katz (demian DOT katz AT villanova DOT edu)<br />
# David Uspal (david dot uspal at villanova dot edu) In for the Country Fried StAEk and/or the Soul Bowl. Ex-Vegetarian (which may make it a crime for me to go), so if the list is full and you still want in, feel free to email me and I'll gladly turn over my spot to an actual Veg*n.<br />
# Cynthia Ng (cynthia dot s dot ng at gmail)<br />
Capped at 6<br />
<br />
=== Code4lib/Goose Island Brewing Pull Request ===<br />
'''When:''' Wednesday, 2/13, 8:00 PM to 11:00 PM<br />
<br />
More information and sign up at [https://code4lib2013-estw.eventbrite.com/|https://code4lib2013-estw.eventbrite.com/]<br />
<br />
=== Bourbon and barbecue ===<br />
'''When:''' Wednesday, 2/13, 7:00 PM<br />
<br />
Friend of mine tells me his cousin manages a Chicago restaurant, Chicago q, and I should go there and tell him my friend sent me. [http://www.chicagoqrestaurant.com/menus/dinner.php Menu] keeps talking about artisanal barbecue and extensive bourbon options. DONE.<br />
<br />
Reservation is at 7 for a party of 8. Add yourselves. <br />
<br />
We can take the number 20 bus to the Red Line. We should plan to meet in the lobby at 6:10; that way we can work with the bus tracker and make a leisurely trip over. <br />
<br />
<br />
<br />
* Andromeda Yelton<br />
* Chris Day [cday2 at saic.edu]<br />
* Abigail Goben <br />
* Rosalyn Metz [rosalynmetz at gmail dot com]<br />
* Dileshni Jayasinghe [d dot jayasinghe at utoronto dot ca]<br />
* Ray Mathew<br />
* Dre (Barbecue, yes. Bourbon... well, we'll see.) akorphan at ncsu.edu<br />
* Sean Chen schen at law.duke.edu<br />
<br />
=== Non-beery get together ===<br />
'''When:''' Wednesday, 2/13, Meet at hotel lobby at around 6:30 (and take public transport over to the park) OR meet us at the rink at 6:45, skating rink closes at 8 PM<br />
<br />
'''Where:''' [https://www.cityofchicago.org/city/en/depts/dca/supp_info/ice_skating_at_themccormicktribuneicerink.html McCormick Tribune Ice Rink]<br />
<br />
'''Contact:''' @dchud, @ranti, @yo_bj (b dot yoose at gmail), @wendyrlibrarian<br />
<br />
'''Cost:''' $10 skate rental, people watching free<br />
<br />
Come and (attempt to) skate with us! This is also a good people watching opportunity, so if you don't want to skate, there will be places to hang out around the rink and the park. There is a [http://www.parkgrillchicago.com/cafe/food-menu cafe] near the rink as well, with hot drinks and food.<br />
<br />
FYI - For those of you who want something else to munch on while hanging out, there's a [http://www.garrettpopcorn.com/chicago-locations/4-east-madison-street/ Garrett Popcorn Shop] a couple blocks away.<br />
<br />
# Chris Sharp (indicating interest)<br />
# Becky Yoose (ready to fall on her butt repeatedly for the entertainment of others)<br />
# Peter Murray<br />
# Shawn Carraway<br />
# Karen Coombs<br />
# Michael Levy<br />
# Christie Peterson<br />
# Andrew Pasterfield<br />
# Virginia Schilling<br />
# Al Cornish<br />
# Sibyl Schaefer<br />
# Kalee Sprague<br />
# Luis Baquera (ready to distract everyone with his own fantastic wipeouts while Becky composes herself)<br />
# Maccabee Levine<br />
# Sarah Shealy (I'm pretty sure I'll fall spectacularly as well :) )<br />
# Emily Lynema (interested!)<br />
<br />
=== Flying Trapeze ===<br />
'''When:''' Monday, 2/11, TBD<br />
<br />
'''Contact:''' rosalynmetz at gmail dot com<br />
<br />
'''Class is full.'''<br />
<br />
No this is not a joke. If you haven't heard Rosy is an aspiring trapeze artists and wants to bring the fun to her friends in Code4Lib. There is a trapeze rig in Chicago and she plans on visiting it and hopes that some of you can come along as well. If its your first time taking a trapeze class, they'll start you off learning [http://www.youtube.com/watch?v=_oqPi_zuX7A a knee hang] and depending on how that goes you might be able to catch it at the end of class. If you have any questions about whether or not this is for you, [http://chicago.trapezeschool.com/classes/trapeze.php TSNY Chicago's website] should have the answer, if not feel free to contact Rosy.<br />
<br />
Trapeze classes are $57, last 2 hours, and are limited to 10 people. Currently TSNY Chicago hasn't release their class schedule for February -- they should be doing that around Jan. 1. If we can get enough people interested before then, we can buy out a whole class. If not it'll be first come, first serve (along with the general public).<br />
<br />
If you're interested in signing up, feel free to add your name and contact info to the list below.<br />
<br />
'''''Sign Up List'''''<br />
# Jay Luker (first!)<br />
# Bill McMillin<br />
# Bess Sadler<br />
# Karen Coyle<br />
# Sibyl Schaefer<br />
# Rosalyn Metz (because I'm organizing)<br />
# Alicia Cozine<br />
# Gabriel Farrell<br />
<br />
=== Game Night! ===<br />
<br />
See the http://wiki.code4lib.org/index.php/2013_game_night page for the latest details and to sign up for individual games or add games you're willing to lead/teach!<br />
<br />
<br />
<br />
<br />
Moved this from idea to an actual event. Still getting some details, but here's what we know:<br />
<br />
Game Night! Type of games might vary due to interest and what people bring. Looks like interest right now is mostly on light to mediumish games with a dash of abstracts ;). <br />
<br />
<br />
Rough Schedule:<br />
* 7:30 setup<br />
* 7:45 start playing games!<br />
* 10:00 start winding down (don't start new games)<br />
* 10:30 all done, turn off the lights<br />
<br />
* I highly recommend that people walk in groups to get back to their respective lodgings. I'll ask folks still around at the end to help me clean up so we can walk back to the conference hotel*<br />
<br />
Please bring your badge with. (You don't need to wear it on the way, but that'll help us make sure everyone in the room is supposed to be there.)<br />
<br />
We have a conference room at the UIC library (Richard J. Daley Library MC 234, 801 S. Morgan, Chicago) reserved for 7:30 on Tuesday the 11th. I'll try to show up at the lobby and hang out there for at about 7:15. I'll be the guy with a code4lib nametag and a box of games ;). Not sure how late we'll play, it looks like the library is open till 1:00am, but I suspect I will for now put a rough ending time of 11pm. <br />
<br />
(Note, there's also some discussion on Cards Against Humanity. I will try to make sure there's an alternative game, but I don't know if I want to prohibit any games. I would say though to remember to be respectful and courteous to those around you. I will probably be pondering this issue for a while)<br />
<br />
<br />
The original list of people who signed up is below.<br />
<br />
I (Jon Gorman) will bring some board games and pick up some cards. Add your name to the list below if you're interested in attending. Also not if you can bring games. Bringing games is NOT REQUIRED. If you can bring a game you can teach, that's great and will make sure we're not just stuck playing the games I bring.<br />
<br />
(I've added some comments to the game lists below)<br />
* jtgorman, aka Jon Gorman: I'll bring Time's Up: Total Recall, Tsuro, Hey, That's My Fish, Hive, and some more I haven't decided on yet. (My profile over at http://www.boardgamegeek.com/ is jtgorman as well if you want to browse my games and make requests)<br />
* yo_bj: I have some games I can bring as well (Kill Doctor Lucky, Fluxx, Godzilla: Stomp, Munchkin Zombies, etc.). Monday doesn't have anything major planned... <br />
*danwho: I 'll bring the Cards Against Humanity set.<br />
*escowles (Mon/Tue preferred): I've got lots of games I could bring like Settlers of Catan, Carcassonne, Ticket to Ride, Age of Renaissance, Elfenland, Agricola, Le Havre, Smallworld, RoboRally, etc. etc. <br />
** Take your pick! All good games. I'll try to finalize my list of games before Friday - JonG <br />
*jen_young: I'm local and I have quite a few games. Just about every version of Fluxx, Bananagrams, Gloom, Munchkin Cthulu,Cards Against Humanity, Apples to Apples, Risk, Last Night on Earth, etc.) <br />
**All good games! If you don't mind bringing a box that would be awesome. I particularly like Apples to Apples, Last Night on Earth and Gloom - JonG<br />
* decasm: Interested in Go (aka igo, weiqi, baduk) anytime, not just game night. I can do Catan as well. (And as much as I love it, Cards Against Humanity is probably a violation of the new Code of Conduct.) <br />
** I look forward to losing my first game of Go to you ;) - JonG<br />
** I'd love to learn Go. <del>Perhaps after the newcomer dinner?</del> Oof... won't make for Tues. But would still be interested to learn. --ranti.<br />
* csharp: I'm interested in playing games - whatever people bring. I almost always travel with a pack or two of playing cards ;-). Monday or Tuesday nights are fine.<br />
* moneill: I would love to join in! I have a version of Catchphrase floating around somewhere, and I think I have Battleship...I need to go weed around in that drawer and see what else presents itself. Tuesday would be my preferred night, but I will make it work! <br />
** Don't worry too much about bringing a game if transportation is a problem. One thing I've done w/ stuff like catchphrase is not take the box but to put pieces and cards in a bag - JOn G<br />
* demiankatz: I'm always up for a game. I'm hoping to travel light so probably shouldn't bring anything, but if there's a local game shop, I might be persuaded to pick up something new as a souvenir. <br />
** Don't worry, I think there will be plenty of games - JonG<br />
* sekjal: I've got [http://boardgamegeek.com/boardgame/36218/dominion Dominion], [http://boardgamegeek.com/boardgame/68448/7-wonders 7 Wonders], [http://boardgamegeek.com/boardgame/30933/bang-the-bullet Bang!], [http://boardgamegeek.com/boardgame/18333/ecofluxx EcoFluxx] and [http://boardgamegeek.com/boardgame/116/guillotine Guillotine] that I can bring. ++ on Cards against Humanity! Prefer non-conflict with beer night. <br />
** Also all good games. I have 7 Wonders, but can bring some other games if you bring that. - Jon G<br />
* arty: so totally interested. Unfortunately, I have no games to contribute.<br />
** No prob.<br />
* sanderson: I would be interested. I can bring [http://boardgamegeek.com/boardgame/478/citadels Citadels] (2-7 players)<br />
** Citadels would be awesome and means I don't have to bring it ;) - JonG<br />
* dvdndrsn: Definitely in! Can bring Innovation, Tichu, Dominion, but Cards Against Humanity sounds good. <br />
** I'll put in a vote for Tichu, heard good things about it - Jon G <br />
* smkiewel: I'm likely to join. Can bring Arkham Horror and Munchkin.<br />
** Arkham Horror seems rather bulky to travel with, but if you want to play bring it ;) - Jon G<br />
** mbutler: If someone actually brings Arkham Horror I'd throw down. Otherwise, whateve. <br />
* jkwilson: I'd like to attend Monday or Tuesday. I have a bunch of games but I'd prefer not to travel with them, and anyway it sounds like they're covered above. I'll bring the 5-6 player Catan extension.<br />
* ejlynema: Interested, but will probably attend Newcomer dinner on Tuesday. Like Dominion and 7 Wonders, but probably don't have room to bring in suitcase. Anyone bringing Tsuro? <br />
** I can bring Tsuro - Jon G<br />
* Christie Peterson (save4use): Also interested, but also probably attending newcomer dinner on Tuesday. Can bring [http://boardgamegeek.com/boardgame/11/bohnanza Bohnanza] and one deck of [http://en.wikipedia.org/wiki/Set_%28game%29 Set]. <br />
**Bohnanza and Set would be awesome - JonG<br />
**Done! I will bring them both -- C<br />
* dgcliff: I'd be interested. Can bring Ticket to Ride.<br />
* mbklein: definitely interested. Will check on my (currently unpacked) games. I am dying to play Cards Against Humanity. If we can't find a way to reconcile it with the Code of Conduct, we need a different Code of Conduct.<br />
** Considering that this is a public event, and that no one knows everyone's sensitivity levels in the room, it might not be a good idea to break out a crass, adult version of apples to apples in the middle of the gaming room. :cP (yo_bj)<br />
* duspal: In. My board game collection is small but mighty (Arkham Horror, Catan, Vampire: Prince of the City, Deadlands: Battle for Slaughter Gulch, Arabian Nights, Diplomacy, Shogun, and Cosmic Encounter off the top of my head, amongst a few others). Let me know ahead of time if anyone is interested, since they're all relatively big... <br />
** If you really want to play Cosmic Encounter, I can bring my copy (Fantasy Flight edition, 3 expansions), just let me know - JonG<br />
*librarywebchic: I'm willing to bring a set and teach folks how to play Majhong. Need at least three to play though.<br />
**beatricep: Uno gets no respect. ;-) @librarywebchic: I have always wanted to learn to play Majhong. If you're still bringing it, I'm in!<br />
** Agreed, I don't know Majhong and I love learning new games. - JonG<br />
** I actually know a few different rule sets. It's too bad I don't have a travel set or I'd bring a 2nd one -Arty<br />
** I'm local and can bring a mahjong set. I've had no one to play with for years, so have probably forgotten how. -Linda B<br />
* jcraitz: I'm in after the newcomer dinner. I'll bring Citadels and Bang! <br />
**I think someone higher in the list offered to bring citadels, but won't hurt to have two copies just in case one of you don't show ;) - JonG<br />
**Aww no. left my games at the office. Looks like I'll have to jump in someone else's game.<br />
* julia: I'll be the freeloader who showed up and didn't bring any games.<br />
* kenirwin: interested in attending<br />
* sdellis: attending<br />
* ianc: interested in attending, a little rusty but definitely up for a couple rounds of Mahjong, also want to try something new too!<br />
* haschart: Interested in attending, if I can make it work with the newcomer dinner. Big fan of Dominion lately, but probably cannot bring it `cause the "Big Box" with the base game and two expansion sets is bigger than my suitcase. I could bring "Race for the Galaxy" if there's any interest.<br />
* jessebrown: Interested in attending. I can bring Set and Zombie Fluxx.<br />
* terrywbrady: I would like to attend<br />
* dan fehrenbach (dnfehren): I would like to attend, can bring Pandemic if anyone is interested.<br />
* dileshni: interested in attending. <br />
* Corey Harper: definitely interested in attending if space allows.<br />
* saverkamp: interested in attending.<br />
* Emily Shaw: I like games. <br />
* Alan Dyck: I play Carcassonne and Munchkin among others. I see those listed so I'm bringing a game some friends and I have been creating: Wandering Monster.<br />
* Heidi Frank (hf36@nyu.edu) - I love card games like gin/rummy, but am open to anything.<br />
* Sibyl Schaefer - attending, and will bring anything that fits in my carry-on<br />
* Gary Maixner - Joining. Have a copy of Savage Worlds for roleplaying if anyone's interested.<br />
* cpsarason - I'm up for whatever!<br />
<br />
-- *Please, please, please, if you're signing up on this list, also sign up for a paritcular game slot to start out the evening or put your game in: http://wiki.code4lib.org/index.php/2013_game_night<br />
we're having so many people sign up after Jan. 14th we're in risk of overflowing the room. (I should have put in a cap limit, but given how late I realized this, I haven't *<br />
<br />
I have to confess, I started trying to organize what games certain people were bringing, but it got confusing fast and I don't want anyone to feel compelled to bring anything or feel bad if they can't make it. So if there is something you're dying to play, let me know and I'll try to bring it if I have it.<br />
<br />
== Social Map - Places of Interest==<br />
<br />
https://maps.google.com/maps/ms?msid=213549257652679418473.0004ce6c25e6cdeb0319d&msa=0<br />
<br />
== Layar: augmented reality Code4Lib view of Chicago ==<br />
<br />
There's a "Code4Lib 2013" layer in [http://www.layar.com/ Layar], an augmented reality app that runs on both Android and iOS. You can use it to scan around the city to see two kinds of things: 1) tweets using the #c4l13 or #code4lib hashtag (if the tweets are geolocated so they can be<br />
nailed to a point) and 2) points of interest from the [https://maps.google.com/maps/ms?msid=213549257652679418473.0004ce6c25e6cdeb0319d&msa=0 shared Google Map]. <br />
<br />
To use it:<br />
<br />
* install Layar on your phone<br />
* run it and click to go into Geo Layers mode<br />
* search for "code4lib 2013"<br />
* launch the layer and look around<br />
<br />
See Code4Lib people and events overlaid on top of Chicago, in real time! See an alternate view of the city that's all about libraries and coders!<br />
<br />
To make your own tweets appear, use the #c4l13 hashtag and make sure the tweet is geolocated. In Twitter's client you need to do this by enabling geolocation in settings and then enabling it for each tweet.<br />
<br />
Source code running this: [https://github.com/wdenton/laertes Laertes]. Bill Denton set it up and is very curious to find out if it's useful, so let him know if you try it out.<br />
<br />
== Local Events ==<br />
Events Listings<br />
* Chicago Reader http://www.chicagoreader.com/<br />
* The City of Chicago’s Events Guide: http://www.choosechicago.com/ <br />
* Metromix Chicago: http://chicago.metromix.com/events <br />
* Timeout Chicago: http://timeoutchicago.com/<br />
* Chicago Studio Club's [http://www.google.com/calendar/embed?title=LIVE%20MUSIC%20in%20Chicagoland%20via%20Chicago%20Studio%20Club!%20&height=1000&wkst=1&hl=en&bgcolor=%2399ff99&src=info%40chicagostudioclub.net&color=%237A367A&ctz=America%2FChicago Live Music Google Calendar]<br />
<br />
== Local Food ==<br />
== Local Drinks ==<br />
==Chicago Events Feb 10-14==<br />
<br />
=== Sunday February 10===<br />
Theater - [http://www.neofuturists.org/ Too Much Light Makes the Baby Go Blind] "...with its ever-changing "menu," is an attempt to perform 30 plays in 60 minutes. " 7pm.<br />
<br />
Theater - [http://www.chicagoreader.com/chicago/chunks/Event?oid=8557720 Chunks] : Funny, Heartbreaking, Gross. 7pm & BYOB!<br />
<br />
===Monday February 11===<br />
<br />
Music - [http://www.hideoutchicago.com/event/208497-robbie-fulks-michael-miles-chicago/ Robbie Fulks at the Hideout]<br />
<br />
[http://fedora4lib.org/ fedora4lib] - 7 pm to whenever<br />
<br />
===Tuesday, February 12===<br />
<br />
Concert - [http://www.thefatbabies.com/ The Fat Babies] playing at an awesome venue, [http://greenmilljazz.com/ The Green Mill].<br />
<br />
[http://fedora4lib.org/ fedora4lib] - 7 pm to whenever<br />
<br />
===Wednesday, February 13===<br />
===Thursday, February 14===<br />
Tour of the [http://www.newberry.org/ Newberry Library] -- 3:30 p.m.<br />
This will be a special tour for Code4Lib attendees, so please sign up below if you are interested, as I'll need to give the tour guide an estimate of how many people will come. Details on how to get to the Newberry will follow. Questions? Contact ballingerl at newberry dot org<br />
<br />
'''''Directions: '''''<br />
The Newberry is at 60 W Walton St. It could take half an hour to get there from the conference hotel via CTA, so those of you who wish to take public transit as a group can meet me in the hotel lobby by 3:00. We will then go to the UIC-Halsted El stop (5 blocks from hotel), change trains in the Loop, then walk 3-4 blocks to the Newberry. Otherwise, plan on making your preferred way there and meet in the Newberry lobby by 3:30.<br />
<br />
'''''Sign Up List'''''<br />
# Michael Doran - doran@uta.edu<br />
# William Denton - wtd@pobox.com<br />
# Wayne Schneider - wschneider@hclib.org<br />
# Matt Cordial - rev3lator [at] gmail.com<br />
# ryan hess - mhess8 [at] depaul.edu<br />
# [[User:ianc|Ian Chan]] ichan@csusm.edu<br />
# Richard Aroksaar - richard_aroksaar@nps.gov<br />
# [name] - [email address]<br />
# Laurie Lee Moses - lmoses [at] colum.edu<br />
# Ray Schwartz - schwartzr2@wpunj.edu<br />
<br />
== Music ==<br />
<br />
There's a [http://www.rdio.com/people/wdenton/playlists/2229053/Code4Lib_2013_in_Chicago/ Code4Lib 2013 in Chicago] collaborative playlist on Rdio. If you're a subscriber, have a look, and add something you think everyone would like to hear or use as their personal soundtrack while they're hacking and exploring Chicago.<br />
<br />
<br />
<br />
[[Category:Code4Lib2013]]</div>No replyhttps://wiki.code4lib.org/index.php?title=2013_committees_sign-up_page&diff=200502013 committees sign-up page2012-08-02T23:31:36Z<p>No reply: /* Program Committee */</p>
<hr />
<div>= Code4Lib 2013 Committees =<br />
<br />
If you are interested in helping out with a particular part of the Code4Lib 2013 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br />
<br />
[[During the Conference Volunteers]]<br />
<br />
== Book Give-Away Committee ==<br />
*Kevin S. Clarke, ksclarke@gmail.com<br />
*Anjanette Young<br />
<br />
== Sponsorships Committee ==<br />
<br />
This committee organizes the sponsorship activities. Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br />
<br />
* Margaret Heller mheller@dom.edu<br />
* [[User:DataGazetteer|Peter Murray]], peter.murray@lyrasis.org<br />
* Kyle Banerjee banerjek@uoregon.edu<br />
* Bohyun Kim kimb et fiu dot edu<br />
* [http://roytennant.com/ Roy Tennant], roytennant@gmail.com<br />
* [http://twitter.com/TheRealArty Cynthia Ng], cynthia.s.ng at gmail<br />
* [[User:highermath|Cary Gordon]], cgordon@chillco.com<br />
<br />
== Keynote Speakers Committee ==<br />
<br />
This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community) and work with the speakers to arrange their travel and arrangements.<br />
<br />
*Francis Kayiwa kayiwa@ YOU EYE SEE DOT edu<br />
*Anjanette Young<br />
<br />
== Program Committee ==<br />
<br />
This committee plans the structure of the program, arranges the voting on presentations, etc. These folks will also announce speakers, etc.<br />
* [[User:DataGazetteer|Peter Murray]], peter.murray@lyrasis.org<br />
* [http://twitter.com/ranti Ranti Junus], ranti.junus@gmail.com<br />
* Ray Schwartz, schwartzr2@wpunj.edu<br />
* [http://twitter.com/TheRealArty Cynthia Ng], cynthia.s.ng at gmail<br />
* Tom Johnson, thomas.johnson@oregonstate.edu<br />
<br />
== Scholarships Committee ==<br />
<br />
This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.<br />
<br />
<br />
== T-Shirt Committee ==<br />
<br />
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes.<br />
<br />
* akorphan (akorphan AT ncsu DOT edu)<br />
* [[User:Pberry|Pberry]] Patrick Berry (pberry@csuchico.edu)<br />
<br />
== Social Activities Committee ==<br />
<br />
The committee plans, proposes, and organizes the evening activities.<br />
<br />
*Francis Kayiwa kayiwa@ YOU EYE SEE DOT edu<br />
*Ray Schwartz, schwartzr2@wpunj.edu<br />
*Bohyun Kim kimb et fiu dot edu<br />
*Shane Beers, sbeers depaul edu<br />
*[[User:JonGorman|Jon Gorman]], jtgorman @ illinois dot edu<br />
<br />
== Voting Activities Committee ==<br />
<br />
This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br />
* [http://twitter.com/jlefager Jim LeFager], jameslefager at gmail<br />
<br />
== Whatever Committee ==<br />
<br />
This committee does whatever the organizers can't talk anyone else into doing.<br />
<br />
* [[User:highermath|Cary Gordon]], cgordon@chillco.com<br />
* [http://twitter.com/jlefager Jim LeFager], jameslefager at gmail<br />
* [[User:Wolf29|Wolf Halton]], wolf.halton@lyrasis.org./dev/null<br />
<br />
= Documentation =<br />
To help with documention, no need to sign up, just start editing.<br />
* [[How To Plan A Code4LibCon]]<br />
<br />
== Documentation Interest Group ==<br />
Promote ongoing documentation efforts.<br />
<br />
[[Category: Code4Lib2013]]</div>No replyhttps://wiki.code4lib.org/index.php?title=2013_committees_sign-up_page&diff=200492013 committees sign-up page2012-08-02T23:31:25Z<p>No reply: /* Program Committee */</p>
<hr />
<div>= Code4Lib 2013 Committees =<br />
<br />
If you are interested in helping out with a particular part of the Code4Lib 2013 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br />
<br />
[[During the Conference Volunteers]]<br />
<br />
== Book Give-Away Committee ==<br />
*Kevin S. Clarke, ksclarke@gmail.com<br />
*Anjanette Young<br />
<br />
== Sponsorships Committee ==<br />
<br />
This committee organizes the sponsorship activities. Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br />
<br />
* Margaret Heller mheller@dom.edu<br />
* [[User:DataGazetteer|Peter Murray]], peter.murray@lyrasis.org<br />
* Kyle Banerjee banerjek@uoregon.edu<br />
* Bohyun Kim kimb et fiu dot edu<br />
* [http://roytennant.com/ Roy Tennant], roytennant@gmail.com<br />
* [http://twitter.com/TheRealArty Cynthia Ng], cynthia.s.ng at gmail<br />
* [[User:highermath|Cary Gordon]], cgordon@chillco.com<br />
<br />
== Keynote Speakers Committee ==<br />
<br />
This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community) and work with the speakers to arrange their travel and arrangements.<br />
<br />
*Francis Kayiwa kayiwa@ YOU EYE SEE DOT edu<br />
*Anjanette Young<br />
<br />
== Program Committee ==<br />
<br />
This committee plans the structure of the program, arranges the voting on presentations, etc. These folks will also announce speakers, etc.<br />
* [[User:DataGazetteer|Peter Murray]], peter.murray@lyrasis.org<br />
* [http://twitter.com/ranti Ranti Junus], ranti.junus@gmail.com<br />
* Ray Schwartz, schwartzr2@wpunj.edu<br />
* [http://twitter.com/TheRealArty Cynthia Ng], cynthia.s.ng at gmail<br />
* [Tom Johnson], thomas.johnson@oregonstate.edu<br />
<br />
== Scholarships Committee ==<br />
<br />
This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.<br />
<br />
<br />
== T-Shirt Committee ==<br />
<br />
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes.<br />
<br />
* akorphan (akorphan AT ncsu DOT edu)<br />
* [[User:Pberry|Pberry]] Patrick Berry (pberry@csuchico.edu)<br />
<br />
== Social Activities Committee ==<br />
<br />
The committee plans, proposes, and organizes the evening activities.<br />
<br />
*Francis Kayiwa kayiwa@ YOU EYE SEE DOT edu<br />
*Ray Schwartz, schwartzr2@wpunj.edu<br />
*Bohyun Kim kimb et fiu dot edu<br />
*Shane Beers, sbeers depaul edu<br />
*[[User:JonGorman|Jon Gorman]], jtgorman @ illinois dot edu<br />
<br />
== Voting Activities Committee ==<br />
<br />
This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br />
* [http://twitter.com/jlefager Jim LeFager], jameslefager at gmail<br />
<br />
== Whatever Committee ==<br />
<br />
This committee does whatever the organizers can't talk anyone else into doing.<br />
<br />
* [[User:highermath|Cary Gordon]], cgordon@chillco.com<br />
* [http://twitter.com/jlefager Jim LeFager], jameslefager at gmail<br />
* [[User:Wolf29|Wolf Halton]], wolf.halton@lyrasis.org./dev/null<br />
<br />
= Documentation =<br />
To help with documention, no need to sign up, just start editing.<br />
* [[How To Plan A Code4LibCon]]<br />
<br />
== Documentation Interest Group ==<br />
Promote ongoing documentation efforts.<br />
<br />
[[Category: Code4Lib2013]]</div>No reply