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

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&amp;diff=42398</id>
		<title>2015 Preconference Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&amp;diff=42398"/>
				<updated>2015-01-07T21:27:00Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* Linked Data Workshop */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Preconference Schedule (draft) ==&lt;br /&gt;
&lt;br /&gt;
Session titles in Italics means they have not been confirmed yet by presenters/workshop leaders.&lt;br /&gt;
&lt;br /&gt;
This is a draft, and there may be some room switching when registration opens. Rooms will be confirmed the week before Code4Lib.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1:30 PM - 4:30 PM)&lt;br /&gt;
|-&lt;br /&gt;
| '''Parlor A (30''') || Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable (Needs: projector, internet connection, and power strips) || Intro to Git &amp;amp; possibly beyond (Needs: projector/screen)&lt;br /&gt;
|-&lt;br /&gt;
| '''Parlor B (30)''' || Code Retreat (Needs whiteboard, dry-erase markers, projector) || Code Retreat (Needs whiteboard, dry-erase markers, projector) &lt;br /&gt;
|-&lt;br /&gt;
| '''Parlor C (30)''' || code4lib/Write The Docs barcamp (Needs: projector/screen, flipboard/whiteboard, power sources for laptops) ||  code4lib/Write The Docs barcamp&lt;br /&gt;
|-&lt;br /&gt;
| '''Grand Ballroom''' I (320) || CANCELLED: [UXtravaganza] || Presentations workshop (Needs: projector/screen)&lt;br /&gt;
|-&lt;br /&gt;
| '''Grand Ballroom''' II (200) || Visualizing Library Data (Needs: projector)  || DPLA API Workshop (Bringing their own projector)&lt;br /&gt;
|-&lt;br /&gt;
| '''Galleria I (35)''' || Coding Custom Solutions for Every Department in the Library with File Analyzer (Needs PC laptop projection, monitor, internet access/wifi, attendees bring laptops) || Fail4Lib 2015 (Needs: projector/screen; Requested: Conference table seating, limit 20 attendants)&lt;br /&gt;
|-&lt;br /&gt;
| '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (Needs: internet/wifi, overhead projection) || CollectionSpace: Getting it up and running at your museum (Needs: Projector)&lt;br /&gt;
|-&lt;br /&gt;
| '''Galleria III (35)''' || Replace yourself with a painfully complex bash script...or try Ansible (Confirmed with Chad; No given setup needs yet) || Intro to Docker&lt;br /&gt;
|-&lt;br /&gt;
| '''Studio (35)''' || Linked Data Workshop (Bringing their own projector) || Dive into Hydra (Needs: projector/screen; Requests: classroom style seating)&lt;br /&gt;
|-&lt;br /&gt;
| '''Directors (35)''' || Code4Arc (Needs: projector) || Code4Arc (Needs: projector)&lt;br /&gt;
|-&lt;br /&gt;
| '''Council (45)''' || Delivering and Preserving GIS Data (Projector, Video connector for MacBook Pro, wifi, power outlets) || A hands-on introduction to GeoBlacklight (Needs: projector, outlets; Requests: list of attendees)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Instructions ==&lt;br /&gt;
Thank you for considering proposing a pre-conference! Here are a few details:&lt;br /&gt;
&lt;br /&gt;
* We will be taking pre-conference proposals until '''November 7, 2014'''&lt;br /&gt;
* 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&lt;br /&gt;
* Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]&lt;br /&gt;
* 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!)&lt;br /&gt;
* 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&lt;br /&gt;
* '''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&lt;br /&gt;
* Please use the template for proposals provided in the pre-formatted block below&lt;br /&gt;
&lt;br /&gt;
== Pre-conferences ==&lt;br /&gt;
&lt;br /&gt;
===MORNING:===&lt;br /&gt;
&lt;br /&gt;
=== Delivering and Preserving GIS Data ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Morning]'''&lt;br /&gt;
&lt;br /&gt;
* Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Jack Reed, Stanford University, pjreed@stanford.edu&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# [[User:Ssimpkin|Sarah Simpkin]]&lt;br /&gt;
# Vicky Steeves&lt;br /&gt;
# Andrew Battista&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
# &lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== A hands-on introduction to GeoBlacklight ===&lt;br /&gt;
&lt;br /&gt;
'''Half Day [Afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Jack Reed, Stanford University, pjreed@stanford.edu&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;Delivering and Preserving GIS Data&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# [[User:Ssimpkin|Sarah Simpkin]]&lt;br /&gt;
# Vicky Steeves&lt;br /&gt;
# Andrew Battista&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
# &lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
===RailsBridge: Intro to programming in Ruby on Rails===&lt;br /&gt;
&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
&lt;br /&gt;
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu&lt;br /&gt;
* Laney McGlohon, Stanford University, laneymcg@stanford.edu&lt;br /&gt;
* Additional instructors welcome&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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].&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Maura Carbone&lt;br /&gt;
#Vicky Steeves&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
# Mike Price&lt;br /&gt;
# Jean Rainwater&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Margaret Heller&lt;br /&gt;
# Bohyun Kim&lt;br /&gt;
# Mark Jarrell&lt;br /&gt;
# Bojana Skarich&lt;br /&gt;
=== Replace yourself with a painfully complex bash script...or try Ansible ===&lt;br /&gt;
&lt;br /&gt;
'''Half Day [Morning]'''&lt;br /&gt;
&lt;br /&gt;
* Chad Nelson, chad dot nelson @ lyrasis dot org&lt;br /&gt;
* Blake Carver, Blake dot carver @lyrasis dot org&lt;br /&gt;
&lt;br /&gt;
Abstract: &lt;br /&gt;
&lt;br /&gt;
[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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Kevin S. Clarke&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Andy Mardesich&lt;br /&gt;
# Anna Headley&lt;br /&gt;
# Chelsea Lobdell&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Chris Sharp&lt;br /&gt;
# Heidi Frank&lt;br /&gt;
# Anjanette Young&lt;br /&gt;
&lt;br /&gt;
=== Intro to Docker ===&lt;br /&gt;
&lt;br /&gt;
'''Half Day [Whenever]'''&lt;br /&gt;
&lt;br /&gt;
* John Fink, McMaster University, john dot fink at gmail dot com&lt;br /&gt;
* Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
[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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
#  Jim Hahn&lt;br /&gt;
#  Joshua Gomez&lt;br /&gt;
#  Bobbi Fox&lt;br /&gt;
#  Ray Schwartz&lt;br /&gt;
#  Megan Kudzia&lt;br /&gt;
# Coral Sheldon-Hess (pleeeeaaase put this in a different slot from Ansible!)&lt;br /&gt;
# Cary Gordon (uses Docker in production on AWS)&lt;br /&gt;
# Eric Phetteplace&lt;br /&gt;
# Esther Verreau&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Anna Headley (voting for afternoon, compliments ansible)&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Matt Critchlow&lt;br /&gt;
# Ray Henry&lt;br /&gt;
# Eric Frierson&lt;br /&gt;
# Sara Amato&lt;br /&gt;
# David Lacy&lt;br /&gt;
# David Uspal&lt;br /&gt;
# Matt Bernhardt&lt;br /&gt;
# Brendan Quinn&lt;br /&gt;
# Anjanette Young&lt;br /&gt;
&lt;br /&gt;
=== Code Retreat ===&lt;br /&gt;
&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu&lt;br /&gt;
* Additional facilitators welcome; Especially if you have CodeRetreat experience.&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.&lt;br /&gt;
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.&lt;br /&gt;
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.&amp;quot; [http://coderetreat.org/about About Code Retreat]&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
# Mike Giarlo&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Devon Smith&lt;br /&gt;
# Barbara Hui&lt;br /&gt;
# Carol Bean&lt;br /&gt;
# Matt Connolly&lt;br /&gt;
# James Van Mil&lt;br /&gt;
# Glen Horton&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Presentations workshop ===&lt;br /&gt;
 &lt;br /&gt;
'''&amp;quot;Half Day [Afternoon]&amp;quot;'''  (but could be expanded based on interest)&lt;br /&gt;
&lt;br /&gt;
* Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
* Additional facilitators welcome.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
 &lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#Vicky Steeves&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Dive into Hydra  ===&lt;br /&gt;
 &lt;br /&gt;
'''&amp;quot;Half Day [Afternoon]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Justin Coyne, Data Curation Experts, justin@curationexperts.com&lt;br /&gt;
* Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;RailsBridge&amp;quot; prior to this workshop.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Maura Carbone&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
# Mike Price&lt;br /&gt;
# Jean Rainwater&lt;br /&gt;
# Sara Amato&lt;br /&gt;
# David Bass&lt;br /&gt;
# Scott Fisher&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== code4lib/Write The Docs barcamp ===&lt;br /&gt;
&lt;br /&gt;
'''&amp;quot;Full Day&amp;quot;''', with options for jumping in for half a day&lt;br /&gt;
&lt;br /&gt;
* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu&lt;br /&gt;
* Write the Docs contacts: TBA&lt;br /&gt;
&lt;br /&gt;
Abstract&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Remember, like metadata, documentation is a love note to the future.&lt;br /&gt;
&lt;br /&gt;
More information about Write the Docs at http://conf.writethedocs.org/&lt;br /&gt;
&lt;br /&gt;
There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). &lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
'''Full day'''&lt;br /&gt;
# &lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
'''Morning'''&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
# Mita Williams&lt;br /&gt;
# Whitni Watkins&lt;br /&gt;
# Jason Raitz&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
'''Afternoon'''&lt;br /&gt;
# Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon. &lt;br /&gt;
# Kevin S. Clarke&lt;br /&gt;
# Chris Sharp&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Linked Data Workshop ===&lt;br /&gt;
&lt;br /&gt;
'''&amp;quot;Half Day [morning]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Karen Estlund, University of Oregon, kestlund@uoregon.edu&lt;br /&gt;
* Tom Johnson, DPLA, tom@dp.la&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Logan Cox&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Chris Hallberg&lt;br /&gt;
# Derek Merleaux&lt;br /&gt;
# Steven Anderson&lt;br /&gt;
# Eben English&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Heather Pitts&lt;br /&gt;
# Andrew Woods&lt;br /&gt;
# Carol Bean&lt;br /&gt;
# Naomi Dushay (probably)&lt;br /&gt;
# David Lacy&lt;br /&gt;
# David Uspal&lt;br /&gt;
# David Bass&lt;br /&gt;
# Brendan Quinn&lt;br /&gt;
# Chrissy Rissmeyer&lt;br /&gt;
# Sharon Clapp&lt;br /&gt;
# Anjanette Young&lt;br /&gt;
&lt;br /&gt;
=== Code4Arc ===&lt;br /&gt;
&lt;br /&gt;
'''&amp;quot;Full Day&amp;quot;''' (with options for half day participation)&lt;br /&gt;
&lt;br /&gt;
* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com&lt;br /&gt;
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com&lt;br /&gt;
* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org&lt;br /&gt;
* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? &lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
&lt;br /&gt;
* Panel type conversations about the State of Art in Archives &lt;br /&gt;
* Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed &lt;br /&gt;
* Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
When signing up, please indicate if you are an end-user or a developer.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Laney McGlohon - developer&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Ryan Rotter&lt;br /&gt;
# Matt LaChance&lt;br /&gt;
# Maureen Callahan - archivist, often-times product owner&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Fail4Lib 2015 ===&lt;br /&gt;
&lt;br /&gt;
'''Half Day [TBD, probably afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Andreas Orphanides, akorphan (at) ncsu.edu&lt;br /&gt;
* Jason Casden, jmcasden (at) ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
&lt;br /&gt;
* Case studies. Avoid our own mistakes by bearing witness to the failures of others.&lt;br /&gt;
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
''Interested in attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Emily Lynema&lt;br /&gt;
# Bret Davidson&lt;br /&gt;
# Hannah Sommers&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Coding Custom Solutions for Every Department in the Library with File Analyzer ===&lt;br /&gt;
 &lt;br /&gt;
'''&amp;quot;Half Day [Morning]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Terry Brady, Georgetown University Library, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
Abstract&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Analyzing Marc Records for the Cataloging department&lt;br /&gt;
* Transferring ILS invoices for the University Account System for the Acquisitions department &lt;br /&gt;
* Delivering patron fines to the Bursar’s office for the Access Service department&lt;br /&gt;
* Summarizing student worker timesheet data for the Finance department&lt;br /&gt;
* Validating counter compliant reports for the Electronic Resources department&lt;br /&gt;
* Preparing ingest packages for the Digital Services department&lt;br /&gt;
* Validating checksums for the Preservation department&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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].&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#  Megan Kudzia&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Whenever]'''&lt;br /&gt;
&lt;br /&gt;
* Karen A. Coombs, OCLC, coombsk@oclc.org&lt;br /&gt;
&lt;br /&gt;
Abstract&lt;br /&gt;
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.&lt;br /&gt;
 &lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Josh Wilson&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== CANCELLED: ''UXtravaganza'' ===&lt;br /&gt;
'''&amp;quot;Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]&amp;quot;'''&lt;br /&gt;
&lt;br /&gt;
* William Hicks, University of North Texas, William.hicks@unt.edu&lt;br /&gt;
* Volunteers?&lt;br /&gt;
&lt;br /&gt;
Abstract&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
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&amp;quot;, 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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your&lt;br /&gt;
name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Andy Mardesich&lt;br /&gt;
# Chelsea Lobdell&lt;br /&gt;
# Eben English (1/2 day)&lt;br /&gt;
# Shaun Ellis (as attendee or volunteer)&lt;br /&gt;
# Whitni Watkins (as attendee or volunteer)&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Intro to Git &amp;amp; possibly beyond ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Whenever]'''&lt;br /&gt;
&lt;br /&gt;
* Erin Fahy, Stanford University, efahy@stanford.edu&lt;br /&gt;
* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
* What is a Distributed Version Control System?&lt;br /&gt;
* What's the difference between Git and Github.com?&lt;br /&gt;
* How to initialize new Git projects locally and on a remote server/Github&lt;br /&gt;
* Cloning/Forking existing projects and keeping up to date&lt;br /&gt;
* The wonderful world of Git branches&lt;br /&gt;
* Interactive rebasing&lt;br /&gt;
* Contributing code to existing projects &amp;amp; what pull requests are&lt;br /&gt;
* How to handle merge conflicts&lt;br /&gt;
* Overview of workflows and branch best practices&lt;br /&gt;
* (time allowing) Advanced git: pre/post hooks, submodules, anything else?&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Jeannie Graham&lt;br /&gt;
# Derek Merleaux&lt;br /&gt;
# Laurie Reeves&lt;br /&gt;
# Bojana Skarich&lt;br /&gt;
# Heidi Frank&lt;br /&gt;
# Jason Raitz&lt;br /&gt;
# Emily Lynema&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Visualizing Library Data ===&lt;br /&gt;
 &lt;br /&gt;
'''&amp;quot;Half Day [Morning||Afternoon]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Ashley Blewer!&lt;br /&gt;
# Bobbi Fox&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
# Eric Phetteplace&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Andy Mardesich&lt;br /&gt;
# Tao Zhao&lt;br /&gt;
# Chris Hallberg&lt;br /&gt;
# Derek Merleaux&lt;br /&gt;
# Bohyun Kim&lt;br /&gt;
# Mark Jarrell&lt;br /&gt;
# Eben English&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Sarah Simpkin&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Kathryn Stine&lt;br /&gt;
# Steve Meyer&lt;br /&gt;
# Matt Critchlow&lt;br /&gt;
# Andrew Pasterfield&lt;br /&gt;
# Ray Henry&lt;br /&gt;
# Bret Davidson&lt;br /&gt;
# Naomi Dushay (maybe)&lt;br /&gt;
# Eric Frierson&lt;br /&gt;
# Matt Bernhardt&lt;br /&gt;
# Greg Bem (Morning only)&lt;br /&gt;
&lt;br /&gt;
=== CollectionSpace: Getting it up and running at your museum ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org&lt;br /&gt;
* Becky Escamilla, Oakland Museum of California, rescamilla@museumca.org&lt;br /&gt;
&lt;br /&gt;
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&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Terry Brady&lt;br /&gt;
# Sharon Clapp&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== DPLA API Workshop: ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Afternoon]''' &lt;br /&gt;
&lt;br /&gt;
* Audrey Altman, DPLA&lt;br /&gt;
* Mark Breedlove, DPLA&lt;br /&gt;
* Mark Matienzo, DPLA&lt;br /&gt;
* Tom Johnson, DPLA&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
# Jean Rainwater&lt;br /&gt;
# Mita Williams&lt;br /&gt;
# Margaret Heller&lt;br /&gt;
# Bohyun Kim&lt;br /&gt;
# Steven Anderson&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Sarah Simpkin&lt;br /&gt;
# Mark Jarrell&lt;br /&gt;
# Heather Pitts&lt;br /&gt;
# Kathryn Stine&lt;br /&gt;
# Andrew Woods&lt;br /&gt;
# Greg Bem&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&amp;diff=42397</id>
		<title>2015 Preconference Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&amp;diff=42397"/>
				<updated>2015-01-07T21:26:15Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* Intro to Docker */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Preconference Schedule (draft) ==&lt;br /&gt;
&lt;br /&gt;
Session titles in Italics means they have not been confirmed yet by presenters/workshop leaders.&lt;br /&gt;
&lt;br /&gt;
This is a draft, and there may be some room switching when registration opens. Rooms will be confirmed the week before Code4Lib.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1:30 PM - 4:30 PM)&lt;br /&gt;
|-&lt;br /&gt;
| '''Parlor A (30''') || Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable (Needs: projector, internet connection, and power strips) || Intro to Git &amp;amp; possibly beyond (Needs: projector/screen)&lt;br /&gt;
|-&lt;br /&gt;
| '''Parlor B (30)''' || Code Retreat (Needs whiteboard, dry-erase markers, projector) || Code Retreat (Needs whiteboard, dry-erase markers, projector) &lt;br /&gt;
|-&lt;br /&gt;
| '''Parlor C (30)''' || code4lib/Write The Docs barcamp (Needs: projector/screen, flipboard/whiteboard, power sources for laptops) ||  code4lib/Write The Docs barcamp&lt;br /&gt;
|-&lt;br /&gt;
| '''Grand Ballroom''' I (320) || CANCELLED: [UXtravaganza] || Presentations workshop (Needs: projector/screen)&lt;br /&gt;
|-&lt;br /&gt;
| '''Grand Ballroom''' II (200) || Visualizing Library Data (Needs: projector)  || DPLA API Workshop (Bringing their own projector)&lt;br /&gt;
|-&lt;br /&gt;
| '''Galleria I (35)''' || Coding Custom Solutions for Every Department in the Library with File Analyzer (Needs PC laptop projection, monitor, internet access/wifi, attendees bring laptops) || Fail4Lib 2015 (Needs: projector/screen; Requested: Conference table seating, limit 20 attendants)&lt;br /&gt;
|-&lt;br /&gt;
| '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (Needs: internet/wifi, overhead projection) || CollectionSpace: Getting it up and running at your museum (Needs: Projector)&lt;br /&gt;
|-&lt;br /&gt;
| '''Galleria III (35)''' || Replace yourself with a painfully complex bash script...or try Ansible (Confirmed with Chad; No given setup needs yet) || Intro to Docker&lt;br /&gt;
|-&lt;br /&gt;
| '''Studio (35)''' || Linked Data Workshop (Bringing their own projector) || Dive into Hydra (Needs: projector/screen; Requests: classroom style seating)&lt;br /&gt;
|-&lt;br /&gt;
| '''Directors (35)''' || Code4Arc (Needs: projector) || Code4Arc (Needs: projector)&lt;br /&gt;
|-&lt;br /&gt;
| '''Council (45)''' || Delivering and Preserving GIS Data (Projector, Video connector for MacBook Pro, wifi, power outlets) || A hands-on introduction to GeoBlacklight (Needs: projector, outlets; Requests: list of attendees)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Instructions ==&lt;br /&gt;
Thank you for considering proposing a pre-conference! Here are a few details:&lt;br /&gt;
&lt;br /&gt;
* We will be taking pre-conference proposals until '''November 7, 2014'''&lt;br /&gt;
* 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&lt;br /&gt;
* Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]&lt;br /&gt;
* 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!)&lt;br /&gt;
* 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&lt;br /&gt;
* '''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&lt;br /&gt;
* Please use the template for proposals provided in the pre-formatted block below&lt;br /&gt;
&lt;br /&gt;
== Pre-conferences ==&lt;br /&gt;
&lt;br /&gt;
===MORNING:===&lt;br /&gt;
&lt;br /&gt;
=== Delivering and Preserving GIS Data ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Morning]'''&lt;br /&gt;
&lt;br /&gt;
* Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Jack Reed, Stanford University, pjreed@stanford.edu&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# [[User:Ssimpkin|Sarah Simpkin]]&lt;br /&gt;
# Vicky Steeves&lt;br /&gt;
# Andrew Battista&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
# &lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== A hands-on introduction to GeoBlacklight ===&lt;br /&gt;
&lt;br /&gt;
'''Half Day [Afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Jack Reed, Stanford University, pjreed@stanford.edu&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;Delivering and Preserving GIS Data&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# [[User:Ssimpkin|Sarah Simpkin]]&lt;br /&gt;
# Vicky Steeves&lt;br /&gt;
# Andrew Battista&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
# &lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
===RailsBridge: Intro to programming in Ruby on Rails===&lt;br /&gt;
&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
&lt;br /&gt;
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu&lt;br /&gt;
* Laney McGlohon, Stanford University, laneymcg@stanford.edu&lt;br /&gt;
* Additional instructors welcome&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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].&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Maura Carbone&lt;br /&gt;
#Vicky Steeves&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
# Mike Price&lt;br /&gt;
# Jean Rainwater&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Margaret Heller&lt;br /&gt;
# Bohyun Kim&lt;br /&gt;
# Mark Jarrell&lt;br /&gt;
# Bojana Skarich&lt;br /&gt;
=== Replace yourself with a painfully complex bash script...or try Ansible ===&lt;br /&gt;
&lt;br /&gt;
'''Half Day [Morning]'''&lt;br /&gt;
&lt;br /&gt;
* Chad Nelson, chad dot nelson @ lyrasis dot org&lt;br /&gt;
* Blake Carver, Blake dot carver @lyrasis dot org&lt;br /&gt;
&lt;br /&gt;
Abstract: &lt;br /&gt;
&lt;br /&gt;
[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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Kevin S. Clarke&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Andy Mardesich&lt;br /&gt;
# Anna Headley&lt;br /&gt;
# Chelsea Lobdell&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Chris Sharp&lt;br /&gt;
# Heidi Frank&lt;br /&gt;
# Anjanette Young&lt;br /&gt;
&lt;br /&gt;
=== Intro to Docker ===&lt;br /&gt;
&lt;br /&gt;
'''Half Day [Whenever]'''&lt;br /&gt;
&lt;br /&gt;
* John Fink, McMaster University, john dot fink at gmail dot com&lt;br /&gt;
* Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
[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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
#  Jim Hahn&lt;br /&gt;
#  Joshua Gomez&lt;br /&gt;
#  Bobbi Fox&lt;br /&gt;
#  Ray Schwartz&lt;br /&gt;
#  Megan Kudzia&lt;br /&gt;
# Coral Sheldon-Hess (pleeeeaaase put this in a different slot from Ansible!)&lt;br /&gt;
# Cary Gordon (uses Docker in production on AWS)&lt;br /&gt;
# Eric Phetteplace&lt;br /&gt;
# Esther Verreau&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Anna Headley (voting for afternoon, compliments ansible)&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Matt Critchlow&lt;br /&gt;
# Ray Henry&lt;br /&gt;
# Eric Frierson&lt;br /&gt;
# Sara Amato&lt;br /&gt;
# David Lacy&lt;br /&gt;
# David Uspal&lt;br /&gt;
# Matt Bernhardt&lt;br /&gt;
# Brendan Quinn&lt;br /&gt;
# Anjanette Young&lt;br /&gt;
&lt;br /&gt;
=== Code Retreat ===&lt;br /&gt;
&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu&lt;br /&gt;
* Additional facilitators welcome; Especially if you have CodeRetreat experience.&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.&lt;br /&gt;
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.&lt;br /&gt;
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.&amp;quot; [http://coderetreat.org/about About Code Retreat]&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
# Mike Giarlo&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Devon Smith&lt;br /&gt;
# Barbara Hui&lt;br /&gt;
# Carol Bean&lt;br /&gt;
# Matt Connolly&lt;br /&gt;
# James Van Mil&lt;br /&gt;
# Glen Horton&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Presentations workshop ===&lt;br /&gt;
 &lt;br /&gt;
'''&amp;quot;Half Day [Afternoon]&amp;quot;'''  (but could be expanded based on interest)&lt;br /&gt;
&lt;br /&gt;
* Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
* Additional facilitators welcome.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
 &lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#Vicky Steeves&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Dive into Hydra  ===&lt;br /&gt;
 &lt;br /&gt;
'''&amp;quot;Half Day [Afternoon]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Justin Coyne, Data Curation Experts, justin@curationexperts.com&lt;br /&gt;
* Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;RailsBridge&amp;quot; prior to this workshop.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Maura Carbone&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
# Mike Price&lt;br /&gt;
# Jean Rainwater&lt;br /&gt;
# Sara Amato&lt;br /&gt;
# David Bass&lt;br /&gt;
# Scott Fisher&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== code4lib/Write The Docs barcamp ===&lt;br /&gt;
&lt;br /&gt;
'''&amp;quot;Full Day&amp;quot;''', with options for jumping in for half a day&lt;br /&gt;
&lt;br /&gt;
* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu&lt;br /&gt;
* Write the Docs contacts: TBA&lt;br /&gt;
&lt;br /&gt;
Abstract&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Remember, like metadata, documentation is a love note to the future.&lt;br /&gt;
&lt;br /&gt;
More information about Write the Docs at http://conf.writethedocs.org/&lt;br /&gt;
&lt;br /&gt;
There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). &lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
'''Full day'''&lt;br /&gt;
# &lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
'''Morning'''&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
# Mita Williams&lt;br /&gt;
# Whitni Watkins&lt;br /&gt;
# Jason Raitz&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
'''Afternoon'''&lt;br /&gt;
# Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon. &lt;br /&gt;
# Kevin S. Clarke&lt;br /&gt;
# Chris Sharp&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Linked Data Workshop ===&lt;br /&gt;
&lt;br /&gt;
'''&amp;quot;Half Day [morning]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Karen Estlund, University of Oregon, kestlund@uoregon.edu&lt;br /&gt;
* Tom Johnson, DPLA, tom@dp.la&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Logan Cox&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Chris Hallberg&lt;br /&gt;
# Derek Merleaux&lt;br /&gt;
# Steven Anderson&lt;br /&gt;
# Eben English&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Heather Pitts&lt;br /&gt;
# Andrew Woods&lt;br /&gt;
# Carol Bean&lt;br /&gt;
# Naomi Dushay (probably)&lt;br /&gt;
# David Lacy&lt;br /&gt;
# David Uspal&lt;br /&gt;
# David Bass&lt;br /&gt;
# Brendan Quinn&lt;br /&gt;
# Chrissy Rissmeyer&lt;br /&gt;
# Sharon Clapp&lt;br /&gt;
&lt;br /&gt;
=== Code4Arc ===&lt;br /&gt;
&lt;br /&gt;
'''&amp;quot;Full Day&amp;quot;''' (with options for half day participation)&lt;br /&gt;
&lt;br /&gt;
* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com&lt;br /&gt;
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com&lt;br /&gt;
* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org&lt;br /&gt;
* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? &lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
&lt;br /&gt;
* Panel type conversations about the State of Art in Archives &lt;br /&gt;
* Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed &lt;br /&gt;
* Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
When signing up, please indicate if you are an end-user or a developer.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Laney McGlohon - developer&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Ryan Rotter&lt;br /&gt;
# Matt LaChance&lt;br /&gt;
# Maureen Callahan - archivist, often-times product owner&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Fail4Lib 2015 ===&lt;br /&gt;
&lt;br /&gt;
'''Half Day [TBD, probably afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Andreas Orphanides, akorphan (at) ncsu.edu&lt;br /&gt;
* Jason Casden, jmcasden (at) ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
&lt;br /&gt;
* Case studies. Avoid our own mistakes by bearing witness to the failures of others.&lt;br /&gt;
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
''Interested in attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Emily Lynema&lt;br /&gt;
# Bret Davidson&lt;br /&gt;
# Hannah Sommers&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Coding Custom Solutions for Every Department in the Library with File Analyzer ===&lt;br /&gt;
 &lt;br /&gt;
'''&amp;quot;Half Day [Morning]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Terry Brady, Georgetown University Library, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
Abstract&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Analyzing Marc Records for the Cataloging department&lt;br /&gt;
* Transferring ILS invoices for the University Account System for the Acquisitions department &lt;br /&gt;
* Delivering patron fines to the Bursar’s office for the Access Service department&lt;br /&gt;
* Summarizing student worker timesheet data for the Finance department&lt;br /&gt;
* Validating counter compliant reports for the Electronic Resources department&lt;br /&gt;
* Preparing ingest packages for the Digital Services department&lt;br /&gt;
* Validating checksums for the Preservation department&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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].&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#  Megan Kudzia&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Whenever]'''&lt;br /&gt;
&lt;br /&gt;
* Karen A. Coombs, OCLC, coombsk@oclc.org&lt;br /&gt;
&lt;br /&gt;
Abstract&lt;br /&gt;
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.&lt;br /&gt;
 &lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Josh Wilson&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== CANCELLED: ''UXtravaganza'' ===&lt;br /&gt;
'''&amp;quot;Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]&amp;quot;'''&lt;br /&gt;
&lt;br /&gt;
* William Hicks, University of North Texas, William.hicks@unt.edu&lt;br /&gt;
* Volunteers?&lt;br /&gt;
&lt;br /&gt;
Abstract&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
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&amp;quot;, 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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your&lt;br /&gt;
name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Andy Mardesich&lt;br /&gt;
# Chelsea Lobdell&lt;br /&gt;
# Eben English (1/2 day)&lt;br /&gt;
# Shaun Ellis (as attendee or volunteer)&lt;br /&gt;
# Whitni Watkins (as attendee or volunteer)&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Intro to Git &amp;amp; possibly beyond ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Whenever]'''&lt;br /&gt;
&lt;br /&gt;
* Erin Fahy, Stanford University, efahy@stanford.edu&lt;br /&gt;
* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
* What is a Distributed Version Control System?&lt;br /&gt;
* What's the difference between Git and Github.com?&lt;br /&gt;
* How to initialize new Git projects locally and on a remote server/Github&lt;br /&gt;
* Cloning/Forking existing projects and keeping up to date&lt;br /&gt;
* The wonderful world of Git branches&lt;br /&gt;
* Interactive rebasing&lt;br /&gt;
* Contributing code to existing projects &amp;amp; what pull requests are&lt;br /&gt;
* How to handle merge conflicts&lt;br /&gt;
* Overview of workflows and branch best practices&lt;br /&gt;
* (time allowing) Advanced git: pre/post hooks, submodules, anything else?&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Jeannie Graham&lt;br /&gt;
# Derek Merleaux&lt;br /&gt;
# Laurie Reeves&lt;br /&gt;
# Bojana Skarich&lt;br /&gt;
# Heidi Frank&lt;br /&gt;
# Jason Raitz&lt;br /&gt;
# Emily Lynema&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Visualizing Library Data ===&lt;br /&gt;
 &lt;br /&gt;
'''&amp;quot;Half Day [Morning||Afternoon]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Ashley Blewer!&lt;br /&gt;
# Bobbi Fox&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
# Eric Phetteplace&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Andy Mardesich&lt;br /&gt;
# Tao Zhao&lt;br /&gt;
# Chris Hallberg&lt;br /&gt;
# Derek Merleaux&lt;br /&gt;
# Bohyun Kim&lt;br /&gt;
# Mark Jarrell&lt;br /&gt;
# Eben English&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Sarah Simpkin&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Kathryn Stine&lt;br /&gt;
# Steve Meyer&lt;br /&gt;
# Matt Critchlow&lt;br /&gt;
# Andrew Pasterfield&lt;br /&gt;
# Ray Henry&lt;br /&gt;
# Bret Davidson&lt;br /&gt;
# Naomi Dushay (maybe)&lt;br /&gt;
# Eric Frierson&lt;br /&gt;
# Matt Bernhardt&lt;br /&gt;
# Greg Bem (Morning only)&lt;br /&gt;
&lt;br /&gt;
=== CollectionSpace: Getting it up and running at your museum ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org&lt;br /&gt;
* Becky Escamilla, Oakland Museum of California, rescamilla@museumca.org&lt;br /&gt;
&lt;br /&gt;
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&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Terry Brady&lt;br /&gt;
# Sharon Clapp&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== DPLA API Workshop: ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Afternoon]''' &lt;br /&gt;
&lt;br /&gt;
* Audrey Altman, DPLA&lt;br /&gt;
* Mark Breedlove, DPLA&lt;br /&gt;
* Mark Matienzo, DPLA&lt;br /&gt;
* Tom Johnson, DPLA&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
# Jean Rainwater&lt;br /&gt;
# Mita Williams&lt;br /&gt;
# Margaret Heller&lt;br /&gt;
# Bohyun Kim&lt;br /&gt;
# Steven Anderson&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Sarah Simpkin&lt;br /&gt;
# Mark Jarrell&lt;br /&gt;
# Heather Pitts&lt;br /&gt;
# Kathryn Stine&lt;br /&gt;
# Andrew Woods&lt;br /&gt;
# Greg Bem&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&amp;diff=42396</id>
		<title>2015 Preconference Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&amp;diff=42396"/>
				<updated>2015-01-07T21:25:28Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* Replace yourself with a painfully complex bash script...or try Ansible */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Preconference Schedule (draft) ==&lt;br /&gt;
&lt;br /&gt;
Session titles in Italics means they have not been confirmed yet by presenters/workshop leaders.&lt;br /&gt;
&lt;br /&gt;
This is a draft, and there may be some room switching when registration opens. Rooms will be confirmed the week before Code4Lib.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1:30 PM - 4:30 PM)&lt;br /&gt;
|-&lt;br /&gt;
| '''Parlor A (30''') || Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable (Needs: projector, internet connection, and power strips) || Intro to Git &amp;amp; possibly beyond (Needs: projector/screen)&lt;br /&gt;
|-&lt;br /&gt;
| '''Parlor B (30)''' || Code Retreat (Needs whiteboard, dry-erase markers, projector) || Code Retreat (Needs whiteboard, dry-erase markers, projector) &lt;br /&gt;
|-&lt;br /&gt;
| '''Parlor C (30)''' || code4lib/Write The Docs barcamp (Needs: projector/screen, flipboard/whiteboard, power sources for laptops) ||  code4lib/Write The Docs barcamp&lt;br /&gt;
|-&lt;br /&gt;
| '''Grand Ballroom''' I (320) || CANCELLED: [UXtravaganza] || Presentations workshop (Needs: projector/screen)&lt;br /&gt;
|-&lt;br /&gt;
| '''Grand Ballroom''' II (200) || Visualizing Library Data (Needs: projector)  || DPLA API Workshop (Bringing their own projector)&lt;br /&gt;
|-&lt;br /&gt;
| '''Galleria I (35)''' || Coding Custom Solutions for Every Department in the Library with File Analyzer (Needs PC laptop projection, monitor, internet access/wifi, attendees bring laptops) || Fail4Lib 2015 (Needs: projector/screen; Requested: Conference table seating, limit 20 attendants)&lt;br /&gt;
|-&lt;br /&gt;
| '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (Needs: internet/wifi, overhead projection) || CollectionSpace: Getting it up and running at your museum (Needs: Projector)&lt;br /&gt;
|-&lt;br /&gt;
| '''Galleria III (35)''' || Replace yourself with a painfully complex bash script...or try Ansible (Confirmed with Chad; No given setup needs yet) || Intro to Docker&lt;br /&gt;
|-&lt;br /&gt;
| '''Studio (35)''' || Linked Data Workshop (Bringing their own projector) || Dive into Hydra (Needs: projector/screen; Requests: classroom style seating)&lt;br /&gt;
|-&lt;br /&gt;
| '''Directors (35)''' || Code4Arc (Needs: projector) || Code4Arc (Needs: projector)&lt;br /&gt;
|-&lt;br /&gt;
| '''Council (45)''' || Delivering and Preserving GIS Data (Projector, Video connector for MacBook Pro, wifi, power outlets) || A hands-on introduction to GeoBlacklight (Needs: projector, outlets; Requests: list of attendees)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Instructions ==&lt;br /&gt;
Thank you for considering proposing a pre-conference! Here are a few details:&lt;br /&gt;
&lt;br /&gt;
* We will be taking pre-conference proposals until '''November 7, 2014'''&lt;br /&gt;
* 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&lt;br /&gt;
* Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]&lt;br /&gt;
* 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!)&lt;br /&gt;
* 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&lt;br /&gt;
* '''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&lt;br /&gt;
* Please use the template for proposals provided in the pre-formatted block below&lt;br /&gt;
&lt;br /&gt;
== Pre-conferences ==&lt;br /&gt;
&lt;br /&gt;
===MORNING:===&lt;br /&gt;
&lt;br /&gt;
=== Delivering and Preserving GIS Data ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Morning]'''&lt;br /&gt;
&lt;br /&gt;
* Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Jack Reed, Stanford University, pjreed@stanford.edu&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# [[User:Ssimpkin|Sarah Simpkin]]&lt;br /&gt;
# Vicky Steeves&lt;br /&gt;
# Andrew Battista&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
# &lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== A hands-on introduction to GeoBlacklight ===&lt;br /&gt;
&lt;br /&gt;
'''Half Day [Afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Jack Reed, Stanford University, pjreed@stanford.edu&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;Delivering and Preserving GIS Data&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# [[User:Ssimpkin|Sarah Simpkin]]&lt;br /&gt;
# Vicky Steeves&lt;br /&gt;
# Andrew Battista&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
# &lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
===RailsBridge: Intro to programming in Ruby on Rails===&lt;br /&gt;
&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
&lt;br /&gt;
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu&lt;br /&gt;
* Laney McGlohon, Stanford University, laneymcg@stanford.edu&lt;br /&gt;
* Additional instructors welcome&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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].&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Maura Carbone&lt;br /&gt;
#Vicky Steeves&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
# Mike Price&lt;br /&gt;
# Jean Rainwater&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Margaret Heller&lt;br /&gt;
# Bohyun Kim&lt;br /&gt;
# Mark Jarrell&lt;br /&gt;
# Bojana Skarich&lt;br /&gt;
=== Replace yourself with a painfully complex bash script...or try Ansible ===&lt;br /&gt;
&lt;br /&gt;
'''Half Day [Morning]'''&lt;br /&gt;
&lt;br /&gt;
* Chad Nelson, chad dot nelson @ lyrasis dot org&lt;br /&gt;
* Blake Carver, Blake dot carver @lyrasis dot org&lt;br /&gt;
&lt;br /&gt;
Abstract: &lt;br /&gt;
&lt;br /&gt;
[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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Kevin S. Clarke&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Andy Mardesich&lt;br /&gt;
# Anna Headley&lt;br /&gt;
# Chelsea Lobdell&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Chris Sharp&lt;br /&gt;
# Heidi Frank&lt;br /&gt;
# Anjanette Young&lt;br /&gt;
&lt;br /&gt;
=== Intro to Docker ===&lt;br /&gt;
&lt;br /&gt;
'''Half Day [Whenever]'''&lt;br /&gt;
&lt;br /&gt;
* John Fink, McMaster University, john dot fink at gmail dot com&lt;br /&gt;
* Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
[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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
#  Jim Hahn&lt;br /&gt;
#  Joshua Gomez&lt;br /&gt;
#  Bobbi Fox&lt;br /&gt;
#  Ray Schwartz&lt;br /&gt;
#  Megan Kudzia&lt;br /&gt;
# Coral Sheldon-Hess (pleeeeaaase put this in a different slot from Ansible!)&lt;br /&gt;
# Cary Gordon (uses Docker in production on AWS)&lt;br /&gt;
# Eric Phetteplace&lt;br /&gt;
# Esther Verreau&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Anna Headley (voting for afternoon, compliments ansible)&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Matt Critchlow&lt;br /&gt;
# Ray Henry&lt;br /&gt;
# Eric Frierson&lt;br /&gt;
# Sara Amato&lt;br /&gt;
# David Lacy&lt;br /&gt;
# David Uspal&lt;br /&gt;
# Matt Bernhardt&lt;br /&gt;
# Brendan Quinn&lt;br /&gt;
&lt;br /&gt;
=== Code Retreat ===&lt;br /&gt;
&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu&lt;br /&gt;
* Additional facilitators welcome; Especially if you have CodeRetreat experience.&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.&lt;br /&gt;
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.&lt;br /&gt;
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.&amp;quot; [http://coderetreat.org/about About Code Retreat]&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
# Mike Giarlo&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Devon Smith&lt;br /&gt;
# Barbara Hui&lt;br /&gt;
# Carol Bean&lt;br /&gt;
# Matt Connolly&lt;br /&gt;
# James Van Mil&lt;br /&gt;
# Glen Horton&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Presentations workshop ===&lt;br /&gt;
 &lt;br /&gt;
'''&amp;quot;Half Day [Afternoon]&amp;quot;'''  (but could be expanded based on interest)&lt;br /&gt;
&lt;br /&gt;
* Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
* Additional facilitators welcome.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
 &lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#Vicky Steeves&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Dive into Hydra  ===&lt;br /&gt;
 &lt;br /&gt;
'''&amp;quot;Half Day [Afternoon]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Justin Coyne, Data Curation Experts, justin@curationexperts.com&lt;br /&gt;
* Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;RailsBridge&amp;quot; prior to this workshop.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Maura Carbone&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
# Mike Price&lt;br /&gt;
# Jean Rainwater&lt;br /&gt;
# Sara Amato&lt;br /&gt;
# David Bass&lt;br /&gt;
# Scott Fisher&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== code4lib/Write The Docs barcamp ===&lt;br /&gt;
&lt;br /&gt;
'''&amp;quot;Full Day&amp;quot;''', with options for jumping in for half a day&lt;br /&gt;
&lt;br /&gt;
* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu&lt;br /&gt;
* Write the Docs contacts: TBA&lt;br /&gt;
&lt;br /&gt;
Abstract&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Remember, like metadata, documentation is a love note to the future.&lt;br /&gt;
&lt;br /&gt;
More information about Write the Docs at http://conf.writethedocs.org/&lt;br /&gt;
&lt;br /&gt;
There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). &lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
'''Full day'''&lt;br /&gt;
# &lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
'''Morning'''&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
# Mita Williams&lt;br /&gt;
# Whitni Watkins&lt;br /&gt;
# Jason Raitz&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
'''Afternoon'''&lt;br /&gt;
# Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon. &lt;br /&gt;
# Kevin S. Clarke&lt;br /&gt;
# Chris Sharp&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Linked Data Workshop ===&lt;br /&gt;
&lt;br /&gt;
'''&amp;quot;Half Day [morning]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Karen Estlund, University of Oregon, kestlund@uoregon.edu&lt;br /&gt;
* Tom Johnson, DPLA, tom@dp.la&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Logan Cox&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Chris Hallberg&lt;br /&gt;
# Derek Merleaux&lt;br /&gt;
# Steven Anderson&lt;br /&gt;
# Eben English&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Heather Pitts&lt;br /&gt;
# Andrew Woods&lt;br /&gt;
# Carol Bean&lt;br /&gt;
# Naomi Dushay (probably)&lt;br /&gt;
# David Lacy&lt;br /&gt;
# David Uspal&lt;br /&gt;
# David Bass&lt;br /&gt;
# Brendan Quinn&lt;br /&gt;
# Chrissy Rissmeyer&lt;br /&gt;
# Sharon Clapp&lt;br /&gt;
&lt;br /&gt;
=== Code4Arc ===&lt;br /&gt;
&lt;br /&gt;
'''&amp;quot;Full Day&amp;quot;''' (with options for half day participation)&lt;br /&gt;
&lt;br /&gt;
* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com&lt;br /&gt;
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com&lt;br /&gt;
* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org&lt;br /&gt;
* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? &lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
&lt;br /&gt;
* Panel type conversations about the State of Art in Archives &lt;br /&gt;
* Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed &lt;br /&gt;
* Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
When signing up, please indicate if you are an end-user or a developer.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Laney McGlohon - developer&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Ryan Rotter&lt;br /&gt;
# Matt LaChance&lt;br /&gt;
# Maureen Callahan - archivist, often-times product owner&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Fail4Lib 2015 ===&lt;br /&gt;
&lt;br /&gt;
'''Half Day [TBD, probably afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Andreas Orphanides, akorphan (at) ncsu.edu&lt;br /&gt;
* Jason Casden, jmcasden (at) ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
&lt;br /&gt;
* Case studies. Avoid our own mistakes by bearing witness to the failures of others.&lt;br /&gt;
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
''Interested in attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Emily Lynema&lt;br /&gt;
# Bret Davidson&lt;br /&gt;
# Hannah Sommers&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Coding Custom Solutions for Every Department in the Library with File Analyzer ===&lt;br /&gt;
 &lt;br /&gt;
'''&amp;quot;Half Day [Morning]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Terry Brady, Georgetown University Library, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
Abstract&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Analyzing Marc Records for the Cataloging department&lt;br /&gt;
* Transferring ILS invoices for the University Account System for the Acquisitions department &lt;br /&gt;
* Delivering patron fines to the Bursar’s office for the Access Service department&lt;br /&gt;
* Summarizing student worker timesheet data for the Finance department&lt;br /&gt;
* Validating counter compliant reports for the Electronic Resources department&lt;br /&gt;
* Preparing ingest packages for the Digital Services department&lt;br /&gt;
* Validating checksums for the Preservation department&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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].&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#  Megan Kudzia&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Whenever]'''&lt;br /&gt;
&lt;br /&gt;
* Karen A. Coombs, OCLC, coombsk@oclc.org&lt;br /&gt;
&lt;br /&gt;
Abstract&lt;br /&gt;
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.&lt;br /&gt;
 &lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Josh Wilson&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== CANCELLED: ''UXtravaganza'' ===&lt;br /&gt;
'''&amp;quot;Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]&amp;quot;'''&lt;br /&gt;
&lt;br /&gt;
* William Hicks, University of North Texas, William.hicks@unt.edu&lt;br /&gt;
* Volunteers?&lt;br /&gt;
&lt;br /&gt;
Abstract&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
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&amp;quot;, 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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your&lt;br /&gt;
name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Andy Mardesich&lt;br /&gt;
# Chelsea Lobdell&lt;br /&gt;
# Eben English (1/2 day)&lt;br /&gt;
# Shaun Ellis (as attendee or volunteer)&lt;br /&gt;
# Whitni Watkins (as attendee or volunteer)&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Intro to Git &amp;amp; possibly beyond ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Whenever]'''&lt;br /&gt;
&lt;br /&gt;
* Erin Fahy, Stanford University, efahy@stanford.edu&lt;br /&gt;
* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
* What is a Distributed Version Control System?&lt;br /&gt;
* What's the difference between Git and Github.com?&lt;br /&gt;
* How to initialize new Git projects locally and on a remote server/Github&lt;br /&gt;
* Cloning/Forking existing projects and keeping up to date&lt;br /&gt;
* The wonderful world of Git branches&lt;br /&gt;
* Interactive rebasing&lt;br /&gt;
* Contributing code to existing projects &amp;amp; what pull requests are&lt;br /&gt;
* How to handle merge conflicts&lt;br /&gt;
* Overview of workflows and branch best practices&lt;br /&gt;
* (time allowing) Advanced git: pre/post hooks, submodules, anything else?&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Jeannie Graham&lt;br /&gt;
# Derek Merleaux&lt;br /&gt;
# Laurie Reeves&lt;br /&gt;
# Bojana Skarich&lt;br /&gt;
# Heidi Frank&lt;br /&gt;
# Jason Raitz&lt;br /&gt;
# Emily Lynema&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Visualizing Library Data ===&lt;br /&gt;
 &lt;br /&gt;
'''&amp;quot;Half Day [Morning||Afternoon]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Ashley Blewer!&lt;br /&gt;
# Bobbi Fox&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
# Eric Phetteplace&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Andy Mardesich&lt;br /&gt;
# Tao Zhao&lt;br /&gt;
# Chris Hallberg&lt;br /&gt;
# Derek Merleaux&lt;br /&gt;
# Bohyun Kim&lt;br /&gt;
# Mark Jarrell&lt;br /&gt;
# Eben English&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Sarah Simpkin&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Kathryn Stine&lt;br /&gt;
# Steve Meyer&lt;br /&gt;
# Matt Critchlow&lt;br /&gt;
# Andrew Pasterfield&lt;br /&gt;
# Ray Henry&lt;br /&gt;
# Bret Davidson&lt;br /&gt;
# Naomi Dushay (maybe)&lt;br /&gt;
# Eric Frierson&lt;br /&gt;
# Matt Bernhardt&lt;br /&gt;
# Greg Bem (Morning only)&lt;br /&gt;
&lt;br /&gt;
=== CollectionSpace: Getting it up and running at your museum ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org&lt;br /&gt;
* Becky Escamilla, Oakland Museum of California, rescamilla@museumca.org&lt;br /&gt;
&lt;br /&gt;
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&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Terry Brady&lt;br /&gt;
# Sharon Clapp&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== DPLA API Workshop: ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Afternoon]''' &lt;br /&gt;
&lt;br /&gt;
* Audrey Altman, DPLA&lt;br /&gt;
* Mark Breedlove, DPLA&lt;br /&gt;
* Mark Matienzo, DPLA&lt;br /&gt;
* Tom Johnson, DPLA&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
# Jean Rainwater&lt;br /&gt;
# Mita Williams&lt;br /&gt;
# Margaret Heller&lt;br /&gt;
# Bohyun Kim&lt;br /&gt;
# Steven Anderson&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Sarah Simpkin&lt;br /&gt;
# Mark Jarrell&lt;br /&gt;
# Heather Pitts&lt;br /&gt;
# Kathryn Stine&lt;br /&gt;
# Andrew Woods&lt;br /&gt;
# Greg Bem&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_committees_sign-up_page&amp;diff=35550</id>
		<title>2013 committees sign-up page</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_committees_sign-up_page&amp;diff=35550"/>
				<updated>2013-02-01T18:15:25Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* Book Give-Away Committee */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2013 Committees =&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
'''[[2013 During the Conference Volunteers | During the Conference Volunteers]]''' - If you're going to be at the conference, sign up to help out!&lt;br /&gt;
&lt;br /&gt;
== Book Give-Away Committee ==&lt;br /&gt;
&lt;br /&gt;
== Sponsorships Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Margaret Heller mheller@dom.edu&lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]], peter.murray@lyrasis.org&lt;br /&gt;
* Kyle Banerjee banerjek@uoregon.edu&lt;br /&gt;
* Bohyun Kim kimb et fiu dot edu&lt;br /&gt;
* [http://roytennant.com/ Roy Tennant], roytennant@gmail.com&lt;br /&gt;
* [http://twitter.com/TheRealArty Cynthia Ng], cynthia.s.ng at gmail&lt;br /&gt;
* [[User:highermath|Cary Gordon]], cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
== Keynote Speakers Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
*Francis Kayiwa kayiwa@ YOU EYE SEE DOT edu&lt;br /&gt;
*Anjanette Young&lt;br /&gt;
*Kevin Reiss kr2 @ princeton . edu&lt;br /&gt;
*Jim Rible rible@sou.edu&lt;br /&gt;
&lt;br /&gt;
== Program Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee plans the structure of the program, arranges the voting on presentations, etc. These folks will also announce speakers, etc.&lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]], peter.murray@lyrasis.org&lt;br /&gt;
* [http://twitter.com/ranti Ranti Junus], ranti.junus@gmail.com&lt;br /&gt;
* Ray Schwartz, schwartzr2@wpunj.edu&lt;br /&gt;
* [http://twitter.com/TheRealArty Cynthia Ng], cynthia.s.ng at gmail&lt;br /&gt;
* Tom Johnson, thomas.johnson@oregonstate.edu&lt;br /&gt;
* Tod Olson, tod at uchicago dot edu&lt;br /&gt;
&lt;br /&gt;
== Scholarships Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
* [http://jodischneider.com/jodi.html Jodi Schneider]&lt;br /&gt;
* [http://ecorrado.us/ Edward M. Corrado]&lt;br /&gt;
* Santi Thompson, sathompson3@uh.edu&lt;br /&gt;
* Christina Salazar (christina.salazar AT csuci DOT edu)&lt;br /&gt;
&lt;br /&gt;
== T-Shirt Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes.&lt;br /&gt;
&lt;br /&gt;
* akorphan (akorphan AT ncsu DOT edu)&lt;br /&gt;
* [[User:Pberry|Pberry]] Patrick Berry (pberry@csuchico.edu)&lt;br /&gt;
* Shaun Ellis (shaune@princeton.edu)&lt;br /&gt;
&lt;br /&gt;
== Social Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
The committee plans, proposes, and organizes the evening activities.&lt;br /&gt;
&lt;br /&gt;
*Francis Kayiwa kayiwa@ YOU EYE SEE DOT edu&lt;br /&gt;
*Ray Schwartz, schwartzr2@wpunj.edu&lt;br /&gt;
*Bohyun Kim kimb et fiu dot edu&lt;br /&gt;
*Shane Beers, sbeers depaul edu&lt;br /&gt;
*[[User:JonGorman|Jon Gorman]], jtgorman @ illinois dot edu&lt;br /&gt;
*Becky Yoose, b.yoose cinnamon roll gmail speck com&lt;br /&gt;
* [http://twitter.com/danwho Dan &amp;quot;lampshade&amp;quot; Suchy], dansuchy at gmail&lt;br /&gt;
*Margaret Heller, mheller@dom.edu&lt;br /&gt;
&lt;br /&gt;
== Voting Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
* [http://twitter.com/jlefager Jim LeFager], jameslefager at gmail&lt;br /&gt;
&lt;br /&gt;
== Whatever Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee does whatever the organizers can't talk anyone else into doing.&lt;br /&gt;
&lt;br /&gt;
* [[User:highermath|Cary Gordon]], cgordon@chillco.com&lt;br /&gt;
* [http://twitter.com/jlefager Jim LeFager], jameslefager at gmail&lt;br /&gt;
* [[User:Wolf29|Wolf Halton]], wolf.halton@lyrasis.org./dev/null&lt;br /&gt;
* [[User:crowesn|Sean Crowe]], sean.crowe@ uc dot edu&lt;br /&gt;
* [[User:shawnc12|Shawn Carraway]], carraways@ midlandstech dot edu&lt;br /&gt;
* [[User:mackeral|Michael Lindsey]], mackeral at gmail&lt;br /&gt;
* [[User:Mnorth|Michael North]], m-north AT northwestern DOT edu&lt;br /&gt;
* [[User:Tracy.seneca|Tracy Seneca]], tjseneca at uic dot edu&lt;br /&gt;
&lt;br /&gt;
= Documentation =&lt;br /&gt;
To help with documention, no need to sign up, just start editing.&lt;br /&gt;
* [[How To Plan A Code4LibCon]]&lt;br /&gt;
&lt;br /&gt;
== Documentation Interest Group ==&lt;br /&gt;
Promote ongoing documentation efforts.&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2013]]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_Invited_Speakers_Nominations&amp;diff=21001</id>
		<title>2013 Invited Speakers Nominations</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_Invited_Speakers_Nominations&amp;diff=21001"/>
				<updated>2012-08-13T16:16:18Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Nominations for invited speakers/keynotes for Code4Lib 2013. Alphabetical order. Suggestions will close on August 31, 2012, 5pm CDT, so all names can be tossed into some type of voting mechanism. &lt;br /&gt;
&lt;br /&gt;
==Tim Berners-Lee==&lt;br /&gt;
Active on the Linked Open Data listserv. Also, invented http.&lt;br /&gt;
&lt;br /&gt;
==Cory Doctorow==&lt;br /&gt;
BoingBoing.com, craphound.com. Author of sci-fi, copyright activist, etc. http://en.wikipedia.org/wiki/Cory_Doctorow&lt;br /&gt;
&lt;br /&gt;
==Jeri Ellsworth==&lt;br /&gt;
All around badass. &amp;quot;Jeri Ellsworth is an American entrepreneur and self-taught computer chip designer.&amp;quot;  http://en.wikipedia.org/wiki/Jeri_Ellsworth&lt;br /&gt;
&lt;br /&gt;
==Jason Scott==&lt;br /&gt;
Archivist and filmaker on a mission to archive everything. http://ascii.textfiles.com/speaking&lt;br /&gt;
&lt;br /&gt;
==Mark Surman==&lt;br /&gt;
Executive Director of the Mozilla Foundation with focus on open source and education https://commonspace.wordpress.com/about/&lt;br /&gt;
&lt;br /&gt;
==Richard Stallman==&lt;br /&gt;
&lt;br /&gt;
==Jon Voss==&lt;br /&gt;
Jon Voss has innovated solutions and community engagement on “big picture” problems for 15 years. In the mid-‘90s, his early work on social responsibility led him to develop new business practices for music festivals and rock stars through his work with the Tibetan Freedom Concerts and artists like the Beastie Boys, David Crosby, and Wyclef Jean. A decade later, he helped religious communities and other institutions develop and implement technology infrastructure and strategies that fit with their beliefs, cultures, and daily practice. He served as the IT Director for the San Francisco Zen Center before running his own IT consulting firm for 7 years.&lt;br /&gt;
&lt;br /&gt;
Today, Jon is the Historypin Strategic Partnerships Director at We Are What We Do, a global not-for-profit behavior change agency. He is helping to build an open ecosystem of historical data across libraries, archives, and museums worldwide through his work with Historypin and as one of the organizers of the International Linked Open Data in Libraries, Archives, and Museums Summit. (For more about Jon: http://about.me/jonvoss.)&lt;br /&gt;
&lt;br /&gt;
Stolen from SAA website&lt;br /&gt;
&lt;br /&gt;
==Kam Woods==&lt;br /&gt;
Postdoctoral Research Scientist at the University of North Carolina at Chapel Hill.&lt;br /&gt;
&lt;br /&gt;
Kam is currently developing modified open source digital forensics tools for digital archivists. He works with&lt;br /&gt;
archivists, librarians, forensics researchers, and other development groups to identify core needs in analyzing&lt;br /&gt;
and preparing digital content for preservation -- specifically needs that can be addressed using existing&lt;br /&gt;
high-performance forensic technologies (with a little tweaking). He is also interested in developing datasets&lt;br /&gt;
and teaching technologies to support education and professional training in digital archiving.&lt;br /&gt;
&lt;br /&gt;
http://digitalcorpora.org/&lt;br /&gt;
More info: http://www.digpres.com/&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2013]]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

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

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_Invited_Speakers_Nominations&amp;diff=20829</id>
		<title>2013 Invited Speakers Nominations</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_Invited_Speakers_Nominations&amp;diff=20829"/>
				<updated>2012-08-10T16:19:21Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: New page: Nominations for invited speakers for Code4Lib 2013. Alphabetical order.  ==Jeri Ellsworth== All around badass. &amp;quot;Jeri Ellsworth is an American entrepreneur and self-taught computer chip des...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Nominations for invited speakers for Code4Lib 2013. Alphabetical order.&lt;br /&gt;
&lt;br /&gt;
==Jeri Ellsworth==&lt;br /&gt;
All around badass. &amp;quot;Jeri Ellsworth is an American entrepreneur and self-taught computer chip designer.&amp;quot;  http://en.wikipedia.org/wiki/Jeri_Ellsworth&lt;br /&gt;
&lt;br /&gt;
==Jason Scott==&lt;br /&gt;
Archivist and filmaker on a mission to archive everything. http://ascii.textfiles.com/speaking&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

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

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_committees_sign-up_page&amp;diff=19826</id>
		<title>2013 committees sign-up page</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_committees_sign-up_page&amp;diff=19826"/>
				<updated>2012-07-31T15:10:03Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* Keynote Speakers Committee */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2013 Committees =&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[During the Conference Volunteers]]&lt;br /&gt;
&lt;br /&gt;
== Book Give-Away Committee ==&lt;br /&gt;
*Kevin S. Clarke, ksclarke@gmail.com&lt;br /&gt;
*Anjanette Young&lt;br /&gt;
&lt;br /&gt;
== Sponsorships Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Margaret Heller mheller@dom.edu&lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]], peter.murray@lyrasis.org&lt;br /&gt;
* Kyle Banerjee banerjek@uoregon.edu&lt;br /&gt;
* Bohyun Kim kimb et fiu dot edu&lt;br /&gt;
* [http://roytennant.com/ Roy Tennant], roytennant@gmail.com&lt;br /&gt;
* [http://twitter.com/TheRealArty Cynthia Ng], cynthia.s.ng at gmail&lt;br /&gt;
* [[User:highermath|Cary Gordon]], cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
== Keynote Speakers Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
*Francis Kayiwa kayiwa@ YOU EYE SEE DOT edu&lt;br /&gt;
*Anjanette Young&lt;br /&gt;
&lt;br /&gt;
== Program Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee plans the structure of the program, arranges the voting on presentations, etc. These folks will also announce speakers, etc.&lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]], peter.murray@lyrasis.org&lt;br /&gt;
* [http://twitter.com/ranti Ranti Junus], ranti.junus@gmail.com&lt;br /&gt;
* Ray Schwartz, schwartzr2@wpunj.edu&lt;br /&gt;
* [http://twitter.com/TheRealArty Cynthia Ng], cynthia.s.ng at gmail&lt;br /&gt;
&lt;br /&gt;
== Scholarships Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== T-Shirt Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes.&lt;br /&gt;
&lt;br /&gt;
* akorphan (akorphan AT ncsu DOT edu)&lt;br /&gt;
* [[User:Pberry|Pberry]] Patrick Berry (pberry@csuchico.edu)&lt;br /&gt;
&lt;br /&gt;
== Social Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
The committee plans, proposes, and organizes the evening activities.&lt;br /&gt;
&lt;br /&gt;
*Francis Kayiwa kayiwa@ YOU EYE SEE DOT edu&lt;br /&gt;
*Ray Schwartz, schwartzr2@wpunj.edu&lt;br /&gt;
*Bohyun Kim kimb et fiu dot edu&lt;br /&gt;
*Shane Beers, sbeers depaul edu&lt;br /&gt;
*[[User:JonGorman|Jon Gorman]], jtgorman @ illinois dot edu&lt;br /&gt;
&lt;br /&gt;
== Voting Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
* [http://twitter.com/jlefager Jim LeFager], jameslefager at gmail&lt;br /&gt;
&lt;br /&gt;
== Whatever Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee does whatever the organizers can't talk anyone else into doing.&lt;br /&gt;
&lt;br /&gt;
* [[User:highermath|Cary Gordon]], cgordon@chillco.com&lt;br /&gt;
* [http://twitter.com/jlefager Jim LeFager], jameslefager at gmail&lt;br /&gt;
* [[User:Wolf29|Wolf Halton]], wolf.halton@lyrasis.org./dev/null&lt;br /&gt;
&lt;br /&gt;
= Documentation =&lt;br /&gt;
To help with documention, no need to sign up, just start editing.&lt;br /&gt;
* [[How To Plan A Code4LibCon]]&lt;br /&gt;
&lt;br /&gt;
== Documentation Interest Group ==&lt;br /&gt;
Promote ongoing documentation efforts.&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2013]]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_committees_sign-up_page&amp;diff=19825</id>
		<title>2013 committees sign-up page</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_committees_sign-up_page&amp;diff=19825"/>
				<updated>2012-07-31T15:09:42Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* Book Give-Away Committee */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2013 Committees =&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[During the Conference Volunteers]]&lt;br /&gt;
&lt;br /&gt;
== Book Give-Away Committee ==&lt;br /&gt;
*Kevin S. Clarke, ksclarke@gmail.com&lt;br /&gt;
*Anjanette Young&lt;br /&gt;
&lt;br /&gt;
== Sponsorships Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Margaret Heller mheller@dom.edu&lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]], peter.murray@lyrasis.org&lt;br /&gt;
* Kyle Banerjee banerjek@uoregon.edu&lt;br /&gt;
* Bohyun Kim kimb et fiu dot edu&lt;br /&gt;
* [http://roytennant.com/ Roy Tennant], roytennant@gmail.com&lt;br /&gt;
* [http://twitter.com/TheRealArty Cynthia Ng], cynthia.s.ng at gmail&lt;br /&gt;
* [[User:highermath|Cary Gordon]], cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
== Keynote Speakers Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
*Francis Kayiwa kayiwa@ YOU EYE SEE DOT edu&lt;br /&gt;
&lt;br /&gt;
== Program Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee plans the structure of the program, arranges the voting on presentations, etc. These folks will also announce speakers, etc.&lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]], peter.murray@lyrasis.org&lt;br /&gt;
* [http://twitter.com/ranti Ranti Junus], ranti.junus@gmail.com&lt;br /&gt;
* Ray Schwartz, schwartzr2@wpunj.edu&lt;br /&gt;
* [http://twitter.com/TheRealArty Cynthia Ng], cynthia.s.ng at gmail&lt;br /&gt;
&lt;br /&gt;
== Scholarships Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== T-Shirt Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes.&lt;br /&gt;
&lt;br /&gt;
* akorphan (akorphan AT ncsu DOT edu)&lt;br /&gt;
* [[User:Pberry|Pberry]] Patrick Berry (pberry@csuchico.edu)&lt;br /&gt;
&lt;br /&gt;
== Social Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
The committee plans, proposes, and organizes the evening activities.&lt;br /&gt;
&lt;br /&gt;
*Francis Kayiwa kayiwa@ YOU EYE SEE DOT edu&lt;br /&gt;
*Ray Schwartz, schwartzr2@wpunj.edu&lt;br /&gt;
*Bohyun Kim kimb et fiu dot edu&lt;br /&gt;
*Shane Beers, sbeers depaul edu&lt;br /&gt;
*[[User:JonGorman|Jon Gorman]], jtgorman @ illinois dot edu&lt;br /&gt;
&lt;br /&gt;
== Voting Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
* [http://twitter.com/jlefager Jim LeFager], jameslefager at gmail&lt;br /&gt;
&lt;br /&gt;
== Whatever Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee does whatever the organizers can't talk anyone else into doing.&lt;br /&gt;
&lt;br /&gt;
* [[User:highermath|Cary Gordon]], cgordon@chillco.com&lt;br /&gt;
* [http://twitter.com/jlefager Jim LeFager], jameslefager at gmail&lt;br /&gt;
* [[User:Wolf29|Wolf Halton]], wolf.halton@lyrasis.org./dev/null&lt;br /&gt;
&lt;br /&gt;
= Documentation =&lt;br /&gt;
To help with documention, no need to sign up, just start editing.&lt;br /&gt;
* [[How To Plan A Code4LibCon]]&lt;br /&gt;
&lt;br /&gt;
== Documentation Interest Group ==&lt;br /&gt;
Promote ongoing documentation efforts.&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2013]]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_committees_sign-up_page&amp;diff=19824</id>
		<title>2013 committees sign-up page</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_committees_sign-up_page&amp;diff=19824"/>
				<updated>2012-07-31T15:09:09Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* Book Give-Away Committee */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2013 Committees =&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[During the Conference Volunteers]]&lt;br /&gt;
&lt;br /&gt;
== Book Give-Away Committee ==&lt;br /&gt;
Kevin S. Clarke, ksclarke@gmail.com&lt;br /&gt;
Anjanette Young&lt;br /&gt;
&lt;br /&gt;
== Sponsorships Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Margaret Heller mheller@dom.edu&lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]], peter.murray@lyrasis.org&lt;br /&gt;
* Kyle Banerjee banerjek@uoregon.edu&lt;br /&gt;
* Bohyun Kim kimb et fiu dot edu&lt;br /&gt;
* [http://roytennant.com/ Roy Tennant], roytennant@gmail.com&lt;br /&gt;
* [http://twitter.com/TheRealArty Cynthia Ng], cynthia.s.ng at gmail&lt;br /&gt;
* [[User:highermath|Cary Gordon]], cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
== Keynote Speakers Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
*Francis Kayiwa kayiwa@ YOU EYE SEE DOT edu&lt;br /&gt;
&lt;br /&gt;
== Program Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee plans the structure of the program, arranges the voting on presentations, etc. These folks will also announce speakers, etc.&lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]], peter.murray@lyrasis.org&lt;br /&gt;
* [http://twitter.com/ranti Ranti Junus], ranti.junus@gmail.com&lt;br /&gt;
* Ray Schwartz, schwartzr2@wpunj.edu&lt;br /&gt;
* [http://twitter.com/TheRealArty Cynthia Ng], cynthia.s.ng at gmail&lt;br /&gt;
&lt;br /&gt;
== Scholarships Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== T-Shirt Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes.&lt;br /&gt;
&lt;br /&gt;
* akorphan (akorphan AT ncsu DOT edu)&lt;br /&gt;
* [[User:Pberry|Pberry]] Patrick Berry (pberry@csuchico.edu)&lt;br /&gt;
&lt;br /&gt;
== Social Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
The committee plans, proposes, and organizes the evening activities.&lt;br /&gt;
&lt;br /&gt;
*Francis Kayiwa kayiwa@ YOU EYE SEE DOT edu&lt;br /&gt;
*Ray Schwartz, schwartzr2@wpunj.edu&lt;br /&gt;
*Bohyun Kim kimb et fiu dot edu&lt;br /&gt;
*Shane Beers, sbeers depaul edu&lt;br /&gt;
*[[User:JonGorman|Jon Gorman]], jtgorman @ illinois dot edu&lt;br /&gt;
&lt;br /&gt;
== Voting Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
* [http://twitter.com/jlefager Jim LeFager], jameslefager at gmail&lt;br /&gt;
&lt;br /&gt;
== Whatever Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee does whatever the organizers can't talk anyone else into doing.&lt;br /&gt;
&lt;br /&gt;
* [[User:highermath|Cary Gordon]], cgordon@chillco.com&lt;br /&gt;
* [http://twitter.com/jlefager Jim LeFager], jameslefager at gmail&lt;br /&gt;
* [[User:Wolf29|Wolf Halton]], wolf.halton@lyrasis.org./dev/null&lt;br /&gt;
&lt;br /&gt;
= Documentation =&lt;br /&gt;
To help with documention, no need to sign up, just start editing.&lt;br /&gt;
* [[How To Plan A Code4LibCon]]&lt;br /&gt;
&lt;br /&gt;
== Documentation Interest Group ==&lt;br /&gt;
Promote ongoing documentation efforts.&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2013]]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_Lightning_Talks_Signup&amp;diff=11476</id>
		<title>2012 Lightning Talks Signup</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_Lightning_Talks_Signup&amp;diff=11476"/>
				<updated>2012-02-27T18:14:52Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* Tuesday, 4:10-5:10pm [12 slots] */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Sign up for Lightning Talks!!'''&lt;br /&gt;
&lt;br /&gt;
Lightning talks are scheduled on all three days of the conference. A lightning talk is a fast-paced 5 minute talk on a topic of your choosing. Sign-ups for lightning talks will open at 10 am on Tuesday, February 7, immediately following the first keynote.&lt;br /&gt;
&lt;br /&gt;
Mark Jason Dominus has a nice page [http://perl.plover.com/lt/lightning-talks.html about lightning talks], which includes this summary of why you might want to do one:&lt;br /&gt;
&lt;br /&gt;
''Maybe you've never given a talk before, and you'd like to start small. For a Lightning Talk, you don't need to make slides, and if you do decide to make slides, you only need to make three.''&lt;br /&gt;
&lt;br /&gt;
''Maybe you're nervous and you're afraid you'll mess up. It's a lot easier to plan and deliver a five minute talk than it is to deliver a long talk. And if you do mess up, at least the painful part will be over quickly.''&lt;br /&gt;
&lt;br /&gt;
''Maybe you don't have much to say. Maybe you just want to ask a question, or invite people to help you with your project, or boast about something you did, or tell a short cautionary story. These things are all interesting and worth talking about, but there might not be enough to say about them to fill up thirty minutes.''&lt;br /&gt;
&lt;br /&gt;
You might also like Mark Fowler's's [http://www.perl.com/pub/2004/07/30/lightningtalk.html Advice for Giving a Lightning Talk].&lt;br /&gt;
&lt;br /&gt;
'''LIGHTNING TALK SIGNUPS OPEN AT 10 AM PST ON FEBRUARY 7'''&lt;br /&gt;
&lt;br /&gt;
=== Tuesday, 4:10-5:10pm [12 slots] ===&lt;br /&gt;
&lt;br /&gt;
Enter ''Name'' -- ''Title of Talk''&lt;br /&gt;
&lt;br /&gt;
# Al Cornish / [https://s3.amazonaws.com/professional-akc/xtfLightning2012.pdf XTF in 300 seconds] &lt;br /&gt;
# Makoto OKamoto / [http://savemlak.jp/wiki/saveMLAK/en?lang=en&amp;amp;uselang=en saveMLAK] - Aid activities for the Great East Japan Earthquake through collaboration via Wiki ([http://www.slideshare.net/arg_editor/code4lib201220120207 Slide])&lt;br /&gt;
# Andrew Nagy / Vendors Suck&lt;br /&gt;
# akorphan - [https://docs.google.com/open?id=0B8qxz6BpsdaqOGYxYmI4ZmItZDU4Yy00YTgzLWFhMjQtYWM3ZDNiYzBiNmIw Heat maps... not just for input analysis]&lt;br /&gt;
# Gabriel Farrell / ElasticSearch&lt;br /&gt;
# nettie lagace - identifying and solving interoperability problems through cooperation&lt;br /&gt;
# Eric Larson -- [http://speakerdeck.com/u/ewlarson/p/finding-images-in-book-page-images Finding images in book page images] [https://mywebspace.wisc.edu/ewlarson/web/finding_images.pdf PDF]&lt;br /&gt;
# adam wead / Blacklight at the Rock Hall&lt;br /&gt;
# Kelley McGrath -- [http://code4lib.org/files/FRBR&amp;amp;Facets_C4L2012.pptx FRBR, facets, moving images] Updated [http://pages.uoregon.edu/kelleym/publications/FRBR&amp;amp;Facets_C4L2012.pdf pdf] - 20120227&lt;br /&gt;
# Bohyun Kim -- [http://www.slideshare.net/bohyunkim Web Usability in terms of words]&lt;br /&gt;
# Simon Spero.  - [http://code4lib.org/files/froz.pdf Restriction Classes, Bitches]&lt;br /&gt;
# Cynthia Ng / [http://processing.org/ Processing] &amp;amp; [http://processingjs.org/ ProcessingJS]&lt;br /&gt;
&lt;br /&gt;
=== Wednesday, 4:00-5:00pm [12 slots] ===&lt;br /&gt;
&lt;br /&gt;
Enter ''Name'' -- ''Title of Talk''&lt;br /&gt;
&lt;br /&gt;
# Scott Hanrath -- [http://www.slideshare.net/rshanrath/zotero-and-sherpromeo Zotero and SHERPA/RoMEO API mashup]&lt;br /&gt;
# [[User:DataGazetteer|Peter Murray]] -- [http://code4lib.org/files/FOSS4LIB5-minuteSpring2012.ppt Introducing FOSS4LIB.org]&lt;br /&gt;
# Mark Matienzo -- [http://anarchivist-c4l12.heroku.com/#1 I've Got Good News]&lt;br /&gt;
# Mike Durbin -- [http://code4lib.org/files/DurbinCode4lib2012LightningTalk-EdgeCases.pptx Edge Cases - Digitizing and delivering undescribed items in EAD]&lt;br /&gt;
# [http://marlag.com/walker David Walker] -- [http://www.slideshare.net/dswalker/basic-lti Basic Learning Tool Interoperability (LTI) Protocol]&lt;br /&gt;
# Ryuuji Yoshimoto -- Introducing [http://calil.jp/ CALIL.JP], scraping/mashup all of OPACs in JAPAN! [http://dl.dropbox.com/u/3580301/Introducing_CALIL_JP.pdf PDF]&lt;br /&gt;
# Kåre Fiedler Christiansen (@kaarefc) -- Chucking all the software components in a library together to present recorded radio and tv [http://dl.dropbox.com/u/3558261/c4l12presentation.pdf PDF]&lt;br /&gt;
# Joel Richard -- [http://code4lib.org/files/JoelRichard-LightningTalk.pptx introducing Macaw metadata collection tool]&lt;br /&gt;
# Rachel Frick - [http://code4lib.org/files/FrickLightning.pptx LOD-LAM Incubator Project]&lt;br /&gt;
# Mao Tsunekawa - Project Shizuku : Making Friends in libraries [http://dl.dropbox.com/u/262075/Code4LibConference2012_LT_Tsunekawa.pdf PDF]&lt;br /&gt;
# Keith Folsom - Archivists' Toolkit Database Server on an Amazon EC2 Instance&lt;br /&gt;
# Rebecca Jones -- call for services&lt;br /&gt;
&lt;br /&gt;
=== Thursday, 10:15-11:00am [9 slots] ===&lt;br /&gt;
&lt;br /&gt;
Enter ''Name'' -- ''Title of Talk''&lt;br /&gt;
&lt;br /&gt;
# David Uspal -- [http://code4lib.org/files/INTGTW.ppt Project Grab Bag]&lt;br /&gt;
# Robert Haschart -- [http://code4lib.org/files/PlunderingPublicly-AccessibleHathiTrustItems.pptx Adding publicly-accessible Hathi Trust items to your Solr-based discovery system].&lt;br /&gt;
# Jeremy Nelson -- [http://code4lib.org/files/AristotlePresentation.pdf Aristotle a Django based Discovery Layer]&lt;br /&gt;
# Dennis Schafroth - Turbo MARC in YAZ Library [http://www.indexdata.com/sites/indexdata.com/files/TurboMARC.pdf PDF]&lt;br /&gt;
# Yuka Egusa, Masao Takaku -- Recovery of [http://www.facebook.com/MinamisanrikuTempLib Minamisanriku Town Library] from Tsunami Disaster ([http://www.slideshare.net/yegusa/20100209recovery-of-minamisanriku-town-library-from-tsunami-disaster Slide])&lt;br /&gt;
# Hillel Arnold -- Occupy Wall Street documentation&lt;br /&gt;
# Erik Hetzner -- [http://code4lib.org/files/lightning-voting.pdf Strategy for c4l voting]&lt;br /&gt;
# Ed Summers -- jobs.code4lib.org&lt;br /&gt;
# Christopher Spalding -- [http://code4lib.org/files/SPALDING_EX_LIBRIS.pptx Search in a Blender]&lt;br /&gt;
&lt;br /&gt;
===If only we had more time===&lt;br /&gt;
# Tim Shearer - Mass Digitization Update: EAD, Ajax, and CONTENTdm&lt;br /&gt;
# Jason Clark - BookMeUp (Book Suggestions App) http://bit.ly/zRmmvA &lt;br /&gt;
# &lt;br /&gt;
# &lt;br /&gt;
# &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_Lightning_Talks_Signup&amp;diff=11453</id>
		<title>2012 Lightning Talks Signup</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_Lightning_Talks_Signup&amp;diff=11453"/>
				<updated>2012-02-24T00:39:28Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* Thursday, 10:15-11:00am [9 slots] */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Sign up for Lightning Talks!!'''&lt;br /&gt;
&lt;br /&gt;
Lightning talks are scheduled on all three days of the conference. A lightning talk is a fast-paced 5 minute talk on a topic of your choosing. Sign-ups for lightning talks will open at 10 am on Tuesday, February 7, immediately following the first keynote.&lt;br /&gt;
&lt;br /&gt;
Mark Jason Dominus has a nice page [http://perl.plover.com/lt/lightning-talks.html about lightning talks], which includes this summary of why you might want to do one:&lt;br /&gt;
&lt;br /&gt;
''Maybe you've never given a talk before, and you'd like to start small. For a Lightning Talk, you don't need to make slides, and if you do decide to make slides, you only need to make three.''&lt;br /&gt;
&lt;br /&gt;
''Maybe you're nervous and you're afraid you'll mess up. It's a lot easier to plan and deliver a five minute talk than it is to deliver a long talk. And if you do mess up, at least the painful part will be over quickly.''&lt;br /&gt;
&lt;br /&gt;
''Maybe you don't have much to say. Maybe you just want to ask a question, or invite people to help you with your project, or boast about something you did, or tell a short cautionary story. These things are all interesting and worth talking about, but there might not be enough to say about them to fill up thirty minutes.''&lt;br /&gt;
&lt;br /&gt;
You might also like Mark Fowler's's [http://www.perl.com/pub/2004/07/30/lightningtalk.html Advice for Giving a Lightning Talk].&lt;br /&gt;
&lt;br /&gt;
'''LIGHTNING TALK SIGNUPS OPEN AT 10 AM PST ON FEBRUARY 7'''&lt;br /&gt;
&lt;br /&gt;
=== Tuesday, 4:10-5:10pm [12 slots] ===&lt;br /&gt;
&lt;br /&gt;
Enter ''Name'' -- ''Title of Talk''&lt;br /&gt;
&lt;br /&gt;
# Al Cornish / [https://s3.amazonaws.com/professional-akc/xtfLightning2012.pdf XTF in 300 seconds] &lt;br /&gt;
# Makoto OKamoto / [http://savemlak.jp/wiki/saveMLAK/en?lang=en&amp;amp;uselang=en saveMLAK] - Aid activities for the Great East Japan Earthquake through collaboration via Wiki ([http://www.slideshare.net/arg_editor/code4lib201220120207 Slide])&lt;br /&gt;
# Andrew Nagy / Vendors Suck&lt;br /&gt;
# akorphan - [https://docs.google.com/open?id=0B8qxz6BpsdaqOGYxYmI4ZmItZDU4Yy00YTgzLWFhMjQtYWM3ZDNiYzBiNmIw Heat maps... not just for input analysis]&lt;br /&gt;
# Gabriel Farrell / ElasticSearch&lt;br /&gt;
# nettie lagace - identifying and solving interoperability problems through cooperation&lt;br /&gt;
# Eric Larson -- [http://speakerdeck.com/u/ewlarson/p/finding-images-in-book-page-images Finding images in book page images] [https://mywebspace.wisc.edu/ewlarson/web/finding_images.pdf PDF]&lt;br /&gt;
# adam wead / Blacklight at the Rock Hall&lt;br /&gt;
# Kelley McGrath -- [http://code4lib.org/files/FRBR&amp;amp;Facets_C4L2012.pptx FRBR, facets, moving images]&lt;br /&gt;
# Bohyun Kim -- [http://www.slideshare.net/bohyunkim Web Usability in terms of words]&lt;br /&gt;
# Simon Spero.  - [http://code4lib.org/files/froz.pdf Restriction Classes, Bitches]&lt;br /&gt;
# Cynthia Ng / [http://processing.org/ Processing] &amp;amp; [http://processingjs.org/ ProcessingJS]&lt;br /&gt;
&lt;br /&gt;
=== Wednesday, 4:00-5:00pm [12 slots] ===&lt;br /&gt;
&lt;br /&gt;
Enter ''Name'' -- ''Title of Talk''&lt;br /&gt;
&lt;br /&gt;
# Scott Hanrath -- [http://www.slideshare.net/rshanrath/zotero-and-sherpromeo Zotero and SHERPA/RoMEO API mashup]&lt;br /&gt;
# [[User:DataGazetteer|Peter Murray]] -- [http://code4lib.org/files/FOSS4LIB5-minuteSpring2012.ppt Introducing FOSS4LIB.org]&lt;br /&gt;
# Mark Matienzo -- [http://anarchivist-c4l12.heroku.com/#1 I've Got Good News]&lt;br /&gt;
# Mike Durbin -- [http://code4lib.org/files/DurbinCode4lib2012LightningTalk-EdgeCases.pptx Edge Cases - Digitizing and delivering undescribed items in EAD]&lt;br /&gt;
# [http://marlag.com/walker David Walker] -- [http://www.slideshare.net/dswalker/basic-lti Basic Learning Tool Interoperability (LTI) Protocol]&lt;br /&gt;
# Ryuuji Yoshimoto -- Introducing [http://calil.jp/ CALIL.JP], scraping/mashup all of OPACs in JAPAN! [http://dl.dropbox.com/u/3580301/Introducing_CALIL_JP.pdf PDF]&lt;br /&gt;
# Kåre Fiedler Christiansen (@kaarefc) -- Chucking all the software components in a library together to present recorded radio and tv [http://dl.dropbox.com/u/3558261/c4l12presentation.pdf PDF]&lt;br /&gt;
# Joel Richard -- [http://code4lib.org/files/JoelRichard-LightningTalk.pptx introducing Macaw metadata collection tool]&lt;br /&gt;
# Rachel Frick - [http://code4lib.org/files/FrickLightning.pptx LOD-LAM Incubator Project]&lt;br /&gt;
# Mao Tsunekawa - Project Shizuku : Making Friends in libraries [http://dl.dropbox.com/u/262075/Code4LibConference2012_LT_Tsunekawa.pdf PDF]&lt;br /&gt;
# Keith Folsom - Archivists' Toolkit Database Server on an Amazon EC2 Instance&lt;br /&gt;
# Rebecca Jones -- call for services&lt;br /&gt;
&lt;br /&gt;
=== Thursday, 10:15-11:00am [9 slots] ===&lt;br /&gt;
&lt;br /&gt;
Enter ''Name'' -- ''Title of Talk''&lt;br /&gt;
&lt;br /&gt;
# David Uspal -- [http://code4lib.org/files/INTGTW.ppt Project Grab Bag]&lt;br /&gt;
# Robert Haschart -- [http://code4lib.org/files/PlunderingPublicly-AccessibleHathiTrustItems.pptx Adding publicly-accessible Hathi Trust items to your Solr-based discovery system].&lt;br /&gt;
# Jeremy Nelson -- [http://code4lib.org/files/AristotlePresentation.pdf Aristotle a Django based Discovery Layer]&lt;br /&gt;
# Dennis Schafroth - Turbo MARC in YAZ Library [http://www.indexdata.com/sites/indexdata.com/files/TurboMARC.pdf PDF]&lt;br /&gt;
# Yuka Egusa, Masao Takaku -- Recovery of [http://www.facebook.com/MinamisanrikuTempLib Minamisanriku Town Library] from Tsunami Disaster ([http://www.slideshare.net/yegusa/20100209recovery-of-minamisanriku-town-library-from-tsunami-disaster Slide])&lt;br /&gt;
# Hillel Arnold -- Occupy Wall Street documentation&lt;br /&gt;
# Erik Hetzner -- [http://code4lib.org/files/lightning-voting.pdf Strategy for c4l voting]&lt;br /&gt;
# Ed Summers -- jobs.code4lib.org&lt;br /&gt;
# Christopher Spalding -- [http://code4lib.org/files/SPALDING_EX_LIBRIS.pptx Search in a Blender]&lt;br /&gt;
&lt;br /&gt;
===If only we had more time===&lt;br /&gt;
# Tim Shearer - Mass Digitization Update: EAD, Ajax, and CONTENTdm&lt;br /&gt;
# Jason Clark - BookMeUp (Book Suggestions App) http://bit.ly/zRmmvA &lt;br /&gt;
# &lt;br /&gt;
# &lt;br /&gt;
# &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_Lightning_Talks_Signup&amp;diff=11452</id>
		<title>2012 Lightning Talks Signup</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_Lightning_Talks_Signup&amp;diff=11452"/>
				<updated>2012-02-24T00:19:43Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* Wednesday, 4:00-5:00pm [12 slots] */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Sign up for Lightning Talks!!'''&lt;br /&gt;
&lt;br /&gt;
Lightning talks are scheduled on all three days of the conference. A lightning talk is a fast-paced 5 minute talk on a topic of your choosing. Sign-ups for lightning talks will open at 10 am on Tuesday, February 7, immediately following the first keynote.&lt;br /&gt;
&lt;br /&gt;
Mark Jason Dominus has a nice page [http://perl.plover.com/lt/lightning-talks.html about lightning talks], which includes this summary of why you might want to do one:&lt;br /&gt;
&lt;br /&gt;
''Maybe you've never given a talk before, and you'd like to start small. For a Lightning Talk, you don't need to make slides, and if you do decide to make slides, you only need to make three.''&lt;br /&gt;
&lt;br /&gt;
''Maybe you're nervous and you're afraid you'll mess up. It's a lot easier to plan and deliver a five minute talk than it is to deliver a long talk. And if you do mess up, at least the painful part will be over quickly.''&lt;br /&gt;
&lt;br /&gt;
''Maybe you don't have much to say. Maybe you just want to ask a question, or invite people to help you with your project, or boast about something you did, or tell a short cautionary story. These things are all interesting and worth talking about, but there might not be enough to say about them to fill up thirty minutes.''&lt;br /&gt;
&lt;br /&gt;
You might also like Mark Fowler's's [http://www.perl.com/pub/2004/07/30/lightningtalk.html Advice for Giving a Lightning Talk].&lt;br /&gt;
&lt;br /&gt;
'''LIGHTNING TALK SIGNUPS OPEN AT 10 AM PST ON FEBRUARY 7'''&lt;br /&gt;
&lt;br /&gt;
=== Tuesday, 4:10-5:10pm [12 slots] ===&lt;br /&gt;
&lt;br /&gt;
Enter ''Name'' -- ''Title of Talk''&lt;br /&gt;
&lt;br /&gt;
# Al Cornish / [https://s3.amazonaws.com/professional-akc/xtfLightning2012.pdf XTF in 300 seconds] &lt;br /&gt;
# Makoto OKamoto / [http://savemlak.jp/wiki/saveMLAK/en?lang=en&amp;amp;uselang=en saveMLAK] - Aid activities for the Great East Japan Earthquake through collaboration via Wiki ([http://www.slideshare.net/arg_editor/code4lib201220120207 Slide])&lt;br /&gt;
# Andrew Nagy / Vendors Suck&lt;br /&gt;
# akorphan - [https://docs.google.com/open?id=0B8qxz6BpsdaqOGYxYmI4ZmItZDU4Yy00YTgzLWFhMjQtYWM3ZDNiYzBiNmIw Heat maps... not just for input analysis]&lt;br /&gt;
# Gabriel Farrell / ElasticSearch&lt;br /&gt;
# nettie lagace - identifying and solving interoperability problems through cooperation&lt;br /&gt;
# Eric Larson -- [http://speakerdeck.com/u/ewlarson/p/finding-images-in-book-page-images Finding images in book page images] [https://mywebspace.wisc.edu/ewlarson/web/finding_images.pdf PDF]&lt;br /&gt;
# adam wead / Blacklight at the Rock Hall&lt;br /&gt;
# Kelley McGrath -- [http://code4lib.org/files/FRBR&amp;amp;Facets_C4L2012.pptx FRBR, facets, moving images]&lt;br /&gt;
# Bohyun Kim -- [http://www.slideshare.net/bohyunkim Web Usability in terms of words]&lt;br /&gt;
# Simon Spero.  - [http://code4lib.org/files/froz.pdf Restriction Classes, Bitches]&lt;br /&gt;
# Cynthia Ng / [http://processing.org/ Processing] &amp;amp; [http://processingjs.org/ ProcessingJS]&lt;br /&gt;
&lt;br /&gt;
=== Wednesday, 4:00-5:00pm [12 slots] ===&lt;br /&gt;
&lt;br /&gt;
Enter ''Name'' -- ''Title of Talk''&lt;br /&gt;
&lt;br /&gt;
# Scott Hanrath -- [http://www.slideshare.net/rshanrath/zotero-and-sherpromeo Zotero and SHERPA/RoMEO API mashup]&lt;br /&gt;
# [[User:DataGazetteer|Peter Murray]] -- [http://code4lib.org/files/FOSS4LIB5-minuteSpring2012.ppt Introducing FOSS4LIB.org]&lt;br /&gt;
# Mark Matienzo -- [http://anarchivist-c4l12.heroku.com/#1 I've Got Good News]&lt;br /&gt;
# Mike Durbin -- [http://code4lib.org/files/DurbinCode4lib2012LightningTalk-EdgeCases.pptx Edge Cases - Digitizing and delivering undescribed items in EAD]&lt;br /&gt;
# [http://marlag.com/walker David Walker] -- [http://www.slideshare.net/dswalker/basic-lti Basic Learning Tool Interoperability (LTI) Protocol]&lt;br /&gt;
# Ryuuji Yoshimoto -- Introducing [http://calil.jp/ CALIL.JP], scraping/mashup all of OPACs in JAPAN! [http://dl.dropbox.com/u/3580301/Introducing_CALIL_JP.pdf PDF]&lt;br /&gt;
# Kåre Fiedler Christiansen (@kaarefc) -- Chucking all the software components in a library together to present recorded radio and tv [http://dl.dropbox.com/u/3558261/c4l12presentation.pdf PDF]&lt;br /&gt;
# Joel Richard -- [http://code4lib.org/files/JoelRichard-LightningTalk.pptx introducing Macaw metadata collection tool]&lt;br /&gt;
# Rachel Frick - [http://code4lib.org/files/FrickLightning.pptx LOD-LAM Incubator Project]&lt;br /&gt;
# Mao Tsunekawa - Project Shizuku : Making Friends in libraries [http://dl.dropbox.com/u/262075/Code4LibConference2012_LT_Tsunekawa.pdf PDF]&lt;br /&gt;
# Keith Folsom - Archivists' Toolkit Database Server on an Amazon EC2 Instance&lt;br /&gt;
# Rebecca Jones -- call for services&lt;br /&gt;
&lt;br /&gt;
=== Thursday, 10:15-11:00am [9 slots] ===&lt;br /&gt;
&lt;br /&gt;
Enter ''Name'' -- ''Title of Talk''&lt;br /&gt;
&lt;br /&gt;
# David Uspal -- Project Grab Bag&lt;br /&gt;
# Robert Haschart -- Adding publicly-accessible Hathi Trust items to your Solr-based discovery system.&lt;br /&gt;
# Jeremy Nelson -- Aristotle a Django based Discovery Layer&lt;br /&gt;
# Dennis Schafroth - Turbo MARC in YAZ Library [http://www.indexdata.com/sites/indexdata.com/files/TurboMARC.pdf PDF]&lt;br /&gt;
# Yuka Egusa, Masao Takaku -- Recovery of [http://www.facebook.com/MinamisanrikuTempLib Minamisanriku Town Library] from Tsunami Disaster ([http://www.slideshare.net/yegusa/20100209recovery-of-minamisanriku-town-library-from-tsunami-disaster Slide])&lt;br /&gt;
# Hillel Arnold -- Occupy Wall Street documentation&lt;br /&gt;
# Erik Hetzner -- Strategy for c4l voting&lt;br /&gt;
# Ed Summers -- jobs.code4lib.org&lt;br /&gt;
# Christopher Spalding -- Search in a Blender&lt;br /&gt;
&lt;br /&gt;
===If only we had more time===&lt;br /&gt;
# Tim Shearer - Mass Digitization Update: EAD, Ajax, and CONTENTdm&lt;br /&gt;
# Jason Clark - BookMeUp (Book Suggestions App) http://bit.ly/zRmmvA &lt;br /&gt;
# &lt;br /&gt;
# &lt;br /&gt;
# &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_Lightning_Talks_Signup&amp;diff=11451</id>
		<title>2012 Lightning Talks Signup</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_Lightning_Talks_Signup&amp;diff=11451"/>
				<updated>2012-02-24T00:04:30Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* Wednesday, 4:00-5:00pm [12 slots] */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Sign up for Lightning Talks!!'''&lt;br /&gt;
&lt;br /&gt;
Lightning talks are scheduled on all three days of the conference. A lightning talk is a fast-paced 5 minute talk on a topic of your choosing. Sign-ups for lightning talks will open at 10 am on Tuesday, February 7, immediately following the first keynote.&lt;br /&gt;
&lt;br /&gt;
Mark Jason Dominus has a nice page [http://perl.plover.com/lt/lightning-talks.html about lightning talks], which includes this summary of why you might want to do one:&lt;br /&gt;
&lt;br /&gt;
''Maybe you've never given a talk before, and you'd like to start small. For a Lightning Talk, you don't need to make slides, and if you do decide to make slides, you only need to make three.''&lt;br /&gt;
&lt;br /&gt;
''Maybe you're nervous and you're afraid you'll mess up. It's a lot easier to plan and deliver a five minute talk than it is to deliver a long talk. And if you do mess up, at least the painful part will be over quickly.''&lt;br /&gt;
&lt;br /&gt;
''Maybe you don't have much to say. Maybe you just want to ask a question, or invite people to help you with your project, or boast about something you did, or tell a short cautionary story. These things are all interesting and worth talking about, but there might not be enough to say about them to fill up thirty minutes.''&lt;br /&gt;
&lt;br /&gt;
You might also like Mark Fowler's's [http://www.perl.com/pub/2004/07/30/lightningtalk.html Advice for Giving a Lightning Talk].&lt;br /&gt;
&lt;br /&gt;
'''LIGHTNING TALK SIGNUPS OPEN AT 10 AM PST ON FEBRUARY 7'''&lt;br /&gt;
&lt;br /&gt;
=== Tuesday, 4:10-5:10pm [12 slots] ===&lt;br /&gt;
&lt;br /&gt;
Enter ''Name'' -- ''Title of Talk''&lt;br /&gt;
&lt;br /&gt;
# Al Cornish / [https://s3.amazonaws.com/professional-akc/xtfLightning2012.pdf XTF in 300 seconds] &lt;br /&gt;
# Makoto OKamoto / [http://savemlak.jp/wiki/saveMLAK/en?lang=en&amp;amp;uselang=en saveMLAK] - Aid activities for the Great East Japan Earthquake through collaboration via Wiki ([http://www.slideshare.net/arg_editor/code4lib201220120207 Slide])&lt;br /&gt;
# Andrew Nagy / Vendors Suck&lt;br /&gt;
# akorphan - [https://docs.google.com/open?id=0B8qxz6BpsdaqOGYxYmI4ZmItZDU4Yy00YTgzLWFhMjQtYWM3ZDNiYzBiNmIw Heat maps... not just for input analysis]&lt;br /&gt;
# Gabriel Farrell / ElasticSearch&lt;br /&gt;
# nettie lagace - identifying and solving interoperability problems through cooperation&lt;br /&gt;
# Eric Larson -- [http://speakerdeck.com/u/ewlarson/p/finding-images-in-book-page-images Finding images in book page images] [https://mywebspace.wisc.edu/ewlarson/web/finding_images.pdf PDF]&lt;br /&gt;
# adam wead / Blacklight at the Rock Hall&lt;br /&gt;
# Kelley McGrath -- [http://code4lib.org/files/FRBR&amp;amp;Facets_C4L2012.pptx FRBR, facets, moving images]&lt;br /&gt;
# Bohyun Kim -- [http://www.slideshare.net/bohyunkim Web Usability in terms of words]&lt;br /&gt;
# Simon Spero.  - [http://code4lib.org/files/froz.pdf Restriction Classes, Bitches]&lt;br /&gt;
# Cynthia Ng / [http://processing.org/ Processing] &amp;amp; [http://processingjs.org/ ProcessingJS]&lt;br /&gt;
&lt;br /&gt;
=== Wednesday, 4:00-5:00pm [12 slots] ===&lt;br /&gt;
&lt;br /&gt;
Enter ''Name'' -- ''Title of Talk''&lt;br /&gt;
&lt;br /&gt;
# Scott Hanrath -- [http://www.slideshare.net/rshanrath/zotero-and-sherpromeo Zotero and SHERPA/RoMEO API mashup]&lt;br /&gt;
# [[User:DataGazetteer|Peter Murray]] -- [http://code4lib.org/files/FOSS4LIB5-minuteSpring2012.ppt Introducing FOSS4LIB.org]&lt;br /&gt;
# Mark Matienzo -- I've Got Good News&lt;br /&gt;
# Mike Durbin -- [http://code4lib.org/files/DurbinCode4lib2012LightningTalk-EdgeCases.pptx Edge Cases - Digitizing and delivering undescribed items in EAD]&lt;br /&gt;
# [http://marlag.com/walker David Walker] -- [http://www.slideshare.net/dswalker/basic-lti Basic Learning Tool Interoperability (LTI) Protocol]&lt;br /&gt;
# Ryuuji Yoshimoto -- Introducing [http://calil.jp/ CALIL.JP], scraping/mashup all of OPACs in JAPAN! [http://dl.dropbox.com/u/3580301/Introducing_CALIL_JP.pdf PDF]&lt;br /&gt;
# Kåre Fiedler Christiansen (@kaarefc) -- Chucking all the software components in a library together to present recorded radio and tv [http://dl.dropbox.com/u/3558261/c4l12presentation.pdf PDF]&lt;br /&gt;
# Joel Richard -- [http://code4lib.org/files/JoelRichard-LightningTalk.pptx introducing Macaw metadata collection tool]&lt;br /&gt;
# Rachel Frick - [http://code4lib.org/files/FrickLightning.pptx LOD-LAM Incubator Project]&lt;br /&gt;
# Mao Tsunekawa - Project Shizuku : Making Friends in libraries [http://dl.dropbox.com/u/262075/Code4LibConference2012_LT_Tsunekawa.pdf PDF]&lt;br /&gt;
# Keith Folsom - Archivists' Toolkit Database Server on an Amazon EC2 Instance&lt;br /&gt;
# Rebecca Jones -- call for services&lt;br /&gt;
&lt;br /&gt;
=== Thursday, 10:15-11:00am [9 slots] ===&lt;br /&gt;
&lt;br /&gt;
Enter ''Name'' -- ''Title of Talk''&lt;br /&gt;
&lt;br /&gt;
# David Uspal -- Project Grab Bag&lt;br /&gt;
# Robert Haschart -- Adding publicly-accessible Hathi Trust items to your Solr-based discovery system.&lt;br /&gt;
# Jeremy Nelson -- Aristotle a Django based Discovery Layer&lt;br /&gt;
# Dennis Schafroth - Turbo MARC in YAZ Library [http://www.indexdata.com/sites/indexdata.com/files/TurboMARC.pdf PDF]&lt;br /&gt;
# Yuka Egusa, Masao Takaku -- Recovery of [http://www.facebook.com/MinamisanrikuTempLib Minamisanriku Town Library] from Tsunami Disaster ([http://www.slideshare.net/yegusa/20100209recovery-of-minamisanriku-town-library-from-tsunami-disaster Slide])&lt;br /&gt;
# Hillel Arnold -- Occupy Wall Street documentation&lt;br /&gt;
# Erik Hetzner -- Strategy for c4l voting&lt;br /&gt;
# Ed Summers -- jobs.code4lib.org&lt;br /&gt;
# Christopher Spalding -- Search in a Blender&lt;br /&gt;
&lt;br /&gt;
===If only we had more time===&lt;br /&gt;
# Tim Shearer - Mass Digitization Update: EAD, Ajax, and CONTENTdm&lt;br /&gt;
# Jason Clark - BookMeUp (Book Suggestions App) http://bit.ly/zRmmvA &lt;br /&gt;
# &lt;br /&gt;
# &lt;br /&gt;
# &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_Lightning_Talks_Signup&amp;diff=11450</id>
		<title>2012 Lightning Talks Signup</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_Lightning_Talks_Signup&amp;diff=11450"/>
				<updated>2012-02-23T23:30:46Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Sign up for Lightning Talks!!'''&lt;br /&gt;
&lt;br /&gt;
Lightning talks are scheduled on all three days of the conference. A lightning talk is a fast-paced 5 minute talk on a topic of your choosing. Sign-ups for lightning talks will open at 10 am on Tuesday, February 7, immediately following the first keynote.&lt;br /&gt;
&lt;br /&gt;
Mark Jason Dominus has a nice page [http://perl.plover.com/lt/lightning-talks.html about lightning talks], which includes this summary of why you might want to do one:&lt;br /&gt;
&lt;br /&gt;
''Maybe you've never given a talk before, and you'd like to start small. For a Lightning Talk, you don't need to make slides, and if you do decide to make slides, you only need to make three.''&lt;br /&gt;
&lt;br /&gt;
''Maybe you're nervous and you're afraid you'll mess up. It's a lot easier to plan and deliver a five minute talk than it is to deliver a long talk. And if you do mess up, at least the painful part will be over quickly.''&lt;br /&gt;
&lt;br /&gt;
''Maybe you don't have much to say. Maybe you just want to ask a question, or invite people to help you with your project, or boast about something you did, or tell a short cautionary story. These things are all interesting and worth talking about, but there might not be enough to say about them to fill up thirty minutes.''&lt;br /&gt;
&lt;br /&gt;
You might also like Mark Fowler's's [http://www.perl.com/pub/2004/07/30/lightningtalk.html Advice for Giving a Lightning Talk].&lt;br /&gt;
&lt;br /&gt;
'''LIGHTNING TALK SIGNUPS OPEN AT 10 AM PST ON FEBRUARY 7'''&lt;br /&gt;
&lt;br /&gt;
=== Tuesday, 4:10-5:10pm [12 slots] ===&lt;br /&gt;
&lt;br /&gt;
Enter ''Name'' -- ''Title of Talk''&lt;br /&gt;
&lt;br /&gt;
# Al Cornish / [https://s3.amazonaws.com/professional-akc/xtfLightning2012.pdf XTF in 300 seconds] &lt;br /&gt;
# Makoto OKamoto / [http://savemlak.jp/wiki/saveMLAK/en?lang=en&amp;amp;uselang=en saveMLAK] - Aid activities for the Great East Japan Earthquake through collaboration via Wiki ([http://www.slideshare.net/arg_editor/code4lib201220120207 Slide])&lt;br /&gt;
# Andrew Nagy / Vendors Suck&lt;br /&gt;
# akorphan - [https://docs.google.com/open?id=0B8qxz6BpsdaqOGYxYmI4ZmItZDU4Yy00YTgzLWFhMjQtYWM3ZDNiYzBiNmIw Heat maps... not just for input analysis]&lt;br /&gt;
# Gabriel Farrell / ElasticSearch&lt;br /&gt;
# nettie lagace - identifying and solving interoperability problems through cooperation&lt;br /&gt;
# Eric Larson -- [http://speakerdeck.com/u/ewlarson/p/finding-images-in-book-page-images Finding images in book page images] [https://mywebspace.wisc.edu/ewlarson/web/finding_images.pdf PDF]&lt;br /&gt;
# adam wead / Blacklight at the Rock Hall&lt;br /&gt;
# Kelley McGrath -- [http://code4lib.org/files/FRBR&amp;amp;Facets_C4L2012.pptx FRBR, facets, moving images]&lt;br /&gt;
# Bohyun Kim -- [http://www.slideshare.net/bohyunkim Web Usability in terms of words]&lt;br /&gt;
# Simon Spero.  - [http://code4lib.org/files/froz.pdf Restriction Classes, Bitches]&lt;br /&gt;
# Cynthia Ng / [http://processing.org/ Processing] &amp;amp; [http://processingjs.org/ ProcessingJS]&lt;br /&gt;
&lt;br /&gt;
=== Wednesday, 4:00-5:00pm [12 slots] ===&lt;br /&gt;
&lt;br /&gt;
Enter ''Name'' -- ''Title of Talk''&lt;br /&gt;
&lt;br /&gt;
# Scott Hanrath -- [http://www.slideshare.net/rshanrath/zotero-and-sherpromeo Zotero and SHERPA/RoMEO API mashup]&lt;br /&gt;
# [[User:DataGazetteer|Peter Murray]] -- Introducing FOSS4LIB.org&lt;br /&gt;
# Mark Matienzo -- I've Got Good News&lt;br /&gt;
# Mike Durbin -- Edge Cases - Digitizing and delivering undescribed items in EAD&lt;br /&gt;
# [http://marlag.com/walker David Walker] -- [http://www.slideshare.net/dswalker/basic-lti Basic Learning Tool Interoperability (LTI) Protocol]&lt;br /&gt;
# Ryuuji Yoshimoto -- Introducing [http://calil.jp/ CALIL.JP], scraping/mashup all of OPACs in JAPAN! [http://dl.dropbox.com/u/3580301/Introducing_CALIL_JP.pdf PDF]&lt;br /&gt;
# Kåre Fiedler Christiansen (@kaarefc) -- Chucking all the software components in a library together to present recorded radio and tv [http://dl.dropbox.com/u/3558261/c4l12presentation.pdf PDF]&lt;br /&gt;
# Joel Richard -- introducing Macaw metadata collection tool &lt;br /&gt;
# Rachel Frick - LOD-LAM Incubator Project&lt;br /&gt;
# Mao Tsunekawa - Project Shizuku : Making Friends in libraries [http://dl.dropbox.com/u/262075/Code4LibConference2012_LT_Tsunekawa.pdf PDF]&lt;br /&gt;
# Keith Folsom - Archivists' Toolkit Database Server on an Amazon EC2 Instance&lt;br /&gt;
# Rebecca Jones -- call for services&lt;br /&gt;
&lt;br /&gt;
=== Thursday, 10:15-11:00am [9 slots] ===&lt;br /&gt;
&lt;br /&gt;
Enter ''Name'' -- ''Title of Talk''&lt;br /&gt;
&lt;br /&gt;
# David Uspal -- Project Grab Bag&lt;br /&gt;
# Robert Haschart -- Adding publicly-accessible Hathi Trust items to your Solr-based discovery system.&lt;br /&gt;
# Jeremy Nelson -- Aristotle a Django based Discovery Layer&lt;br /&gt;
# Dennis Schafroth - Turbo MARC in YAZ Library [http://www.indexdata.com/sites/indexdata.com/files/TurboMARC.pdf PDF]&lt;br /&gt;
# Yuka Egusa, Masao Takaku -- Recovery of [http://www.facebook.com/MinamisanrikuTempLib Minamisanriku Town Library] from Tsunami Disaster ([http://www.slideshare.net/yegusa/20100209recovery-of-minamisanriku-town-library-from-tsunami-disaster Slide])&lt;br /&gt;
# Hillel Arnold -- Occupy Wall Street documentation&lt;br /&gt;
# Erik Hetzner -- Strategy for c4l voting&lt;br /&gt;
# Ed Summers -- jobs.code4lib.org&lt;br /&gt;
# Christopher Spalding -- Search in a Blender&lt;br /&gt;
&lt;br /&gt;
===If only we had more time===&lt;br /&gt;
# Tim Shearer - Mass Digitization Update: EAD, Ajax, and CONTENTdm&lt;br /&gt;
# Jason Clark - BookMeUp (Book Suggestions App) http://bit.ly/zRmmvA &lt;br /&gt;
# &lt;br /&gt;
# &lt;br /&gt;
# &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

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

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_c4l2012_social_activities&amp;diff=10847</id>
		<title>2012 c4l2012 social activities</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_c4l2012_social_activities&amp;diff=10847"/>
				<updated>2012-02-04T15:17:05Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* Sunday, February 5, 2012 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Ideas==&lt;br /&gt;
* Woodinville distillery tour&lt;br /&gt;
* Seattle distillery tour&lt;br /&gt;
* Favorite local breweries&lt;br /&gt;
* Favorite local tea houses&lt;br /&gt;
* Favorite local used bookstores&lt;br /&gt;
* Visit hackerspace&lt;br /&gt;
** +1&lt;br /&gt;
* Evergreen/Koha - Open Source ILS brewery/tea house meetup&lt;br /&gt;
&lt;br /&gt;
==Planned events==&lt;br /&gt;
&lt;br /&gt;
===Pre-Newcomer + Veterans dinner /drink-up Monday===&lt;br /&gt;
Early in town for pre-conference? &lt;br /&gt;
First time at code4lib? &lt;br /&gt;
Don't know anyone at code4lib?&lt;br /&gt;
Join fellow c4l newbies + 2nd + 3rd timers + veterans. &lt;br /&gt;
You will gain a bunch of new/veteran code4libbers in one night!&lt;br /&gt;
Sign up below (NO CAP). You can show up only for dinner or drinks or both! &lt;br /&gt;
&lt;br /&gt;
But put your name so that we have a rough idea about the number of ppl who will show up =)&lt;br /&gt;
&lt;br /&gt;
'''Plans'''&lt;br /&gt;
* When: Monday evening (2/6) &lt;br /&gt;
* For Dinner: Meet at 6PM (ish)at the hotel lobby&lt;br /&gt;
* For Drinks: show up at Hideout between 8 -10 PM for local art, fancy cocktails, or Belgian beer&lt;br /&gt;
* For Hospitality suite intro chat/hangout: show up at 10 PM - midnight? at hospitality suite&lt;br /&gt;
&lt;br /&gt;
Dinner: [http://www.yelp.com/biz/kastoori-grill-seattle Kastoori Grill -Indian &amp;amp; Himalayan/Nepalese/Tibetan (vegetarian-friendly)]&lt;br /&gt;
0.8 miles 15 min. walk&lt;br /&gt;
* Bohyun Kim - n/v (2nd-timer) (leader)&lt;br /&gt;
* Jason Clark - leader&lt;br /&gt;
* Margaret Heller&lt;br /&gt;
* Sarah Johnston - n&lt;br /&gt;
* Andrea Schurr - n/v (2nd-timer)&lt;br /&gt;
* Jason Ronallo&lt;br /&gt;
* Karen Coombs - v&lt;br /&gt;
* Eric James&lt;br /&gt;
* Misty De Meo - n&lt;br /&gt;
* Keri Thompson - n&lt;br /&gt;
&lt;br /&gt;
Drinks: [http://www.yelp.com/biz/the-hideout-seattle Hideout Lounge] for local art, fancy cocktails, and Belgian beer&lt;br /&gt;
0.3 miles 8 min. walk&lt;br /&gt;
* Bohyun Kim - n/v (2nd-timer) (leader)&lt;br /&gt;
* Jason Clark - leader&lt;br /&gt;
* Lisa Kurt - n&lt;br /&gt;
* Margaret Heller&lt;br /&gt;
* Andrea Schurr - n/v (2nd-timer)&lt;br /&gt;
* Anoop Atre (Would love to if back from MS visit)&lt;br /&gt;
* Heather Pitts (maybe) - n&lt;br /&gt;
* Evviva Weinraub - Hope to join up if back from MS visit)&lt;br /&gt;
* Megan Banasek -n&lt;br /&gt;
* Misty De Meo (maybe) - n&lt;br /&gt;
* Keri Thompson (definitely)&lt;br /&gt;
* David Drexler (likely) - n&lt;br /&gt;
&lt;br /&gt;
Hospitality suite intro chat/ hangout: just show up at the hospitality suite - no sign up required.&lt;br /&gt;
&lt;br /&gt;
===Morning Run Tuesday===&lt;br /&gt;
I (Ray Schwartz) am organizing a morning run for anyone that would like to join me.  It will be around 5 to 6 miles.  I usually run a 10 minute per mile pace. And I would like to start around 7am.  Select which days Tuesday or Wednesday or both mornings.  Choose the date you wish via this Doodle link http://www.doodle.com/3tbigutqvkda5ib8&lt;br /&gt;
&lt;br /&gt;
I will map out a course when I arrive and will post it on the wiki.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Newcomer dinner Tuesday===&lt;br /&gt;
First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating &amp;lt;strike&amp;gt;discussions about&amp;lt;/strike&amp;gt; demonstrations of the many uses of &amp;lt;strike&amp;gt;bacon&amp;lt;/strike&amp;gt; &amp;lt;strike&amp;gt;dongles&amp;lt;/strike&amp;gt; XML.&lt;br /&gt;
&lt;br /&gt;
Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!&lt;br /&gt;
&lt;br /&gt;
'''Plans'''&lt;br /&gt;
* When: Tuesday evening (2/7) '''Note that this year's dinner is on Tuesday'''&lt;br /&gt;
* Time: 6 PM (ish) or whenever you can get your group together&lt;br /&gt;
* Mastermind (if you have any questions): [mailto:yoosebec@grinnell.edu Becky Yoose]&lt;br /&gt;
&lt;br /&gt;
''Guidelines:''&lt;br /&gt;
*Max of '''6''' per group&lt;br /&gt;
**Please, no waitlisting :(&lt;br /&gt;
*ID yourselves so we can get a good mix of new people and veterans in each group&lt;br /&gt;
**New folks - n&lt;br /&gt;
**c4l vets - v&lt;br /&gt;
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group :)''')&lt;br /&gt;
**Leader duties&lt;br /&gt;
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library coders &lt;br /&gt;
***Herd folks from hotel to restaurant (know where you're going!)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Restaurants'''&lt;br /&gt;
&lt;br /&gt;
'''Restaurants within .25 miles of the hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://www.sazeracrestaurant.com/index.php Sazerac] (AWESOME happy hour menu that runs until 8)&lt;br /&gt;
* Martin Haye - n&lt;br /&gt;
* William Gunn - n&lt;br /&gt;
* Rebecca Jones - n&lt;br /&gt;
* Chick Markley - v&lt;br /&gt;
* Al Cornish - v&lt;br /&gt;
* Keri Thompson - n&lt;br /&gt;
*'''capped at 6''' ''(So, who's the fearless leader of this group? ~yo_bj)''&lt;br /&gt;
&lt;br /&gt;
[http://oasiankitchen.com/ O'Asian Kitchen and Lounge]  (Asian) &lt;br /&gt;
&lt;br /&gt;
'''Restaurants between .25 miles and .5 miles of the hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://www.pikebrewing.com/index_html.shtml Pike Brewing] (local brewery, pub food)&lt;br /&gt;
* Ken Varnum - n&lt;br /&gt;
* Chad Nelson - n&lt;br /&gt;
* Ed Summers - v&lt;br /&gt;
* Tommy Ingulfsen - n&lt;br /&gt;
* Adam Wead - v or .5n&lt;br /&gt;
* Dan Coughlin - n&lt;br /&gt;
*'''capped at 6''' ''(So, who's the fearless leader of this group? ~yo_bj)''&lt;br /&gt;
&lt;br /&gt;
[http://www.rockbottom.com/ The Rock Bottom Restaurant &amp;amp; Brewery] (American)&lt;br /&gt;
&lt;br /&gt;
[http://www.wildginger.net/ Wild Ginger] (Asian, a bit overpriced)&lt;br /&gt;
* Tamar Sadeh - n&lt;br /&gt;
* Kevin Clarke - v&lt;br /&gt;
&lt;br /&gt;
[http://www.thepurplecafe.com/index.html Purple Cafe] (American, Wine Bar) ''reservation made under Calvin Mah for 6:30pm for the 6 of us.  I'll be meeting in the hotel lobby at 6pm with some sort of sign.  See you then!''&lt;br /&gt;
* Calvin Mah - (leader) - v&lt;br /&gt;
* David Isaak - n&lt;br /&gt;
* Aaron Collier - n&lt;br /&gt;
* Sean Hannan - v&lt;br /&gt;
* Joshua Gomez - v&lt;br /&gt;
* Charlie Morris - n&lt;br /&gt;
* '''capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.cafepaloma.com/ Cafe Paloma] (Mediterranean)&lt;br /&gt;
* Jean Rainwater (leader) - v&lt;br /&gt;
* Kelley McGrath - n&lt;br /&gt;
* Lori Robare - n&lt;br /&gt;
* Emily Lynema - v&lt;br /&gt;
* Sarah Johnston - n&lt;br /&gt;
&lt;br /&gt;
[http://www.thecollinspub.com/ Collins Pub] (Pub Food, great beer selection)&lt;br /&gt;
* Francis Kayiwa - (leader) &amp;quot;(get hold of me at first dot last name at goog as the date gets closer with your mobile)&amp;quot; v&lt;br /&gt;
* Michael Lindsey - v&lt;br /&gt;
* Dan Suchy - v&lt;br /&gt;
* David Drexler - n&lt;br /&gt;
* Laura Smart - n&lt;br /&gt;
* Heather Pitts - n&lt;br /&gt;
*'''capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.mcmenamins.com/311-six-arms-home Six Arms - McMenamins] (Pub Food &amp;amp; they brew their own beer) ''Meet in the Lobby at 6pm. I've also emailed you. --Joel''&lt;br /&gt;
* Joel Richard (richardjm AT si.edu) (leader) - v&lt;br /&gt;
* Margaret Heller - v&lt;br /&gt;
* Sibyl Schaefer (sschaefer AT rockarch . org) - v&lt;br /&gt;
* Tim Lepczyk (timlepczyk AT gmail.com) - n&lt;br /&gt;
* Ray Schwartz (schwartzr2@wpunj.edu) - v&lt;br /&gt;
* Andrea Schurr (andrea-schurr AT utc DOT edu) - v(2nd-timer)&lt;br /&gt;
* '''capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.611supreme.com/ 611 Supreme] (Crepes and Full Bar) ''Reservation for 6 at 6:30. Meet in the conference hotel lobby at 6pm. Look for the short woman in a trench coat and wide brim hat ~Becky''&lt;br /&gt;
&lt;br /&gt;
*Becky Yoose (leader) - v &lt;br /&gt;
*Cynthia Ng - n&lt;br /&gt;
*Zoe Chao - v&lt;br /&gt;
*Stephanie Collett - n (2nd-timer)&lt;br /&gt;
*Bethany Nowviskie - n&lt;br /&gt;
* Ben Shum - n&lt;br /&gt;
*'''capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.panafricamarket.com/wp/ Pan Africa Restaurant &amp;amp; Bar] (Pan African) &lt;br /&gt;
CLOSED TUESDAYS!!!!!!!!!!!!!!!!!!&lt;br /&gt;
Sorry for the confusion. I have moved everyone to Long Provincial, so that you'll have a place held in case you want it. If Long Provincial doesn't suit you, please remove your name in case someone else wants the spot. Again, I'm sorry. --Jason&lt;br /&gt;
&lt;br /&gt;
[http://longprovincial.com/ Long Provincial] Vietnamese (.7 miles from hotel; 15 minute walk)&lt;br /&gt;
&lt;br /&gt;
Reservation for 6 for 6:30 (and I have a confirmation number!). Meet in the hotel lobby at 6 to allow for a strolling pace to walk over there.&lt;br /&gt;
&lt;br /&gt;
Has a jellyfish tank.&lt;br /&gt;
&lt;br /&gt;
*Jason Ronallo (leader?) - v?&lt;br /&gt;
*Nettie Lagace - n&lt;br /&gt;
*Bohyun Kim - n/v (2nd-timer)&lt;br /&gt;
*Wendy Robertson - n&lt;br /&gt;
*Jennifer Bowen - n/v (3rd timer)&lt;br /&gt;
*James Stuart - n&lt;br /&gt;
*'''capped at six'''&lt;br /&gt;
&lt;br /&gt;
'''Restaurants between .5 and 1 mile from hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://momijiseattle.com/ Momiji] New Japanese restaurant in Seattle - [http://www.concierge.com/tools/blogs/unpacked/2011/10/momiji-seattle.html Reviewed in Concierge.com]&lt;br /&gt;
&lt;br /&gt;
* Andrew Nagy (leader) - v&lt;br /&gt;
* Cory Lown - v&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[http://tomdouglas.com/index.php?page=palace-kitchen-dinner Palace Kitchen] (another Tom Douglas restaurant, w/ a focus on meat).  ''I have made a reservation for 6 at 8pm. Let's meet in the conference lobby at 6:30pm and make our way slowly over; we will find things to do in the interim. Look for Mike Giarlo, a man who may be holding a sign that says &amp;quot;HI I'M MIKE GIARLO&amp;quot; or otherwise shouting his name or looking confused.''&lt;br /&gt;
&lt;br /&gt;
* Mike Giarlo (leader) - v&lt;br /&gt;
* Carmen Mitchell - n&lt;br /&gt;
* Daniel Lovins - v&lt;br /&gt;
* Cary Gordon - v &lt;br /&gt;
* Declan Fleming - v&lt;br /&gt;
* Amy Unger - n&lt;br /&gt;
* (CAPPED AT SIX!)&lt;br /&gt;
&lt;br /&gt;
[http://sitkaandspruce.com/ Sitka and Spruce] (Eclectic, super-local and super-seasonal.) ''We have a reservation for 6 at 8:15pm. We'll meet in the conference lobby at 6:30 pm and head over - the owners also run [http://www.ferdinandthebar.com/home/ Bar Ferd'nand], a wine shop/bar in the same building, and we can kill time there before we eat. Look for Mark Matienzo or Hillel Arnold.''&lt;br /&gt;
&lt;br /&gt;
* Mark Matienzo (leader) - v&lt;br /&gt;
* Hillel Arnold - sophomore&lt;br /&gt;
* Devon Smith - v&lt;br /&gt;
* bernardo gomez - n&lt;br /&gt;
* Derek Merleaux - sophmore&lt;br /&gt;
* Jennifer Weintraub - n&lt;br /&gt;
* (CAPPED AT SIX!)&lt;br /&gt;
&lt;br /&gt;
[http://www.yelp.com/biz/japonessa-seattle Japonessa Restaurant] (Japanese + full bar)&lt;br /&gt;
* Kate Zwaard - n&lt;br /&gt;
* Joe Atzberger - v&lt;br /&gt;
* Scott Fisher - n (2nd-timer)&lt;br /&gt;
* Anoop Atre - n&lt;br /&gt;
&lt;br /&gt;
[http://tomdouglas.com/index.php?page=serious-pie Serious Pie] (Tom Douglas restaurant, inventive pizzas, good local beer list). &lt;br /&gt;
&lt;br /&gt;
* Christopher Spalding (leader) - v&lt;br /&gt;
* Robin Schaaf - n&lt;br /&gt;
* Jason Stirnaman - v&lt;br /&gt;
* Christina Morris - n&lt;br /&gt;
* Lisa Kurt - n&lt;br /&gt;
&lt;br /&gt;
[http://www.allmenus.com/wa/seattle/204592-ballet-restaurant/menu/ Ballet] (Vietnamese)&lt;br /&gt;
&lt;br /&gt;
[http://www.kokebrestaurant.com/ Kokeb Ethiopian Restaurant] (Ethiopian) ''Let's say meet at the lobby at 6pm like everyone else. Woohoo!''&lt;br /&gt;
&lt;br /&gt;
''We have reservations for 6 at 6:45.''&lt;br /&gt;
&lt;br /&gt;
* Andreas Orphanides (leader) - v&lt;br /&gt;
* Mark Mounts - v&lt;br /&gt;
* Joe Montibello - n&lt;br /&gt;
* Justin Littman - n&lt;br /&gt;
* Ron Peterson&lt;br /&gt;
* Bobbi Fox - sophmore&lt;br /&gt;
* (CAPPED AT SIX!)&lt;br /&gt;
Crashing the [http://www.seattlerb.org/ Seattle Ruby] meetup, which meets on Capital Hill at 7:00 on Tuesdays. Eat at [http://www.yelp.com/biz/poppy-seattle Poppy] before.  Leaving from the hotel lobby at 6:00.  ''If you dig Ruby, come to this.  Seattle ruby produced Nokogiri, Vlad, Rubygems.org ....''&lt;br /&gt;
* Matt Zumwalt (leader) - v&lt;br /&gt;
* *Justin Coyne - n&lt;br /&gt;
* Misty De Meo - n&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://tomdouglas.com/index.php?page=dahlia-lounge Dahlia Lounge] (Pacific Northwest cuisine, $$$)&lt;br /&gt;
&lt;br /&gt;
[http://www.mattsinthemarket.com/ Matt's in the Market] (Northwest Cuisine, $$$)&lt;br /&gt;
&lt;br /&gt;
[http://www.placepigalle-seattle.com/ Place Pigalle] (French)&lt;br /&gt;
&lt;br /&gt;
[http://www.chezshea.com/ Chez Shea] (French)&lt;br /&gt;
&lt;br /&gt;
[http://www.elysianbrewing.com/elysian.html Elysian Breweries and Pubs] (Pub Food)&lt;br /&gt;
&lt;br /&gt;
[http://www.mezaseattle.com/index.html Meza] (Latin Fare)&lt;br /&gt;
* Tara Robertson - n&lt;br /&gt;
* Shawn Averkamp - sophomore&lt;br /&gt;
* Corey Harper - v&lt;br /&gt;
* Shaun Ellis - sophomore&lt;br /&gt;
* Jon Stroop - fifth year senior&lt;br /&gt;
* Birkin James Diana - v (hi Jon!; hey newcomers, I'm taking the 6th slot, but, if you're stuck for a signup, plz do feel free to bump/overwrite me - seriously!)&lt;br /&gt;
* '''capped at 6'''''(So, who's the fearless leader of this group? ~yo_bj)''&lt;br /&gt;
&lt;br /&gt;
[http://inthebowlbistro.com/index.php In the Bowl] (Veg*n, Asian)&lt;br /&gt;
&lt;br /&gt;
[http://www.plumbistro.com/ Plumb Bistro] (Veg*n)&lt;br /&gt;
&lt;br /&gt;
[http://highlineseattle.com/ Highline] (Veg*n, bar)&lt;br /&gt;
  &lt;br /&gt;
'''Restaurants more than 1 miles from the hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://bravehorsetavern.com/ Brave Horse Tavern] (another Tom Douglas, good regional beer list, yummy food. Near South Lake Union. Would require a ride on the South Lake Union Trolley (SLUT), but it's easy to get to/use from downtown. &lt;br /&gt;
&lt;br /&gt;
[http://www.temperodobrasil.net/ Tempero do Brasil] I was excited to see Ipanema Grill 6 blocks from the hotel, unfortunately it seems to be closed for good.  So this restaurant which is a 10 minute ($15) cab ride away and which also serves Brazilian cuisine (including the ever-tasty feijoada) will have to do.&lt;br /&gt;
* Robert Haschart - leader - v third year&lt;br /&gt;
* Molly Pickral - n&lt;br /&gt;
&lt;br /&gt;
[http://flyingfishrestaurant.com/ Flying Fish] (Seafood)&lt;br /&gt;
&lt;br /&gt;
[http://www.allmenus.com/wa/seattle/3437-cafe-flora/menu/dinner/ Cafe Flora] (FANTASTIC Veg*n restaurant. Use Metro bus #11 to get there)&lt;br /&gt;
&lt;br /&gt;
[http://www.teapotvegetarianhouse.com/index.htm Teapot Vegetarian House] (Veg*n, Asian)&lt;br /&gt;
&lt;br /&gt;
[http://spaceneedle.com/restaurant/ Space Needle] (American, Pricy; but what the heck, listed it anyway for those who want the experience)&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Get Lamp&amp;quot; viewing Tuesday (9 PM) ===&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Tuesday, February 7, 9 PM or shortly after -Courtyard Ballroom&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Adam Wead and Michael Klein are organizing a viewing of [http://www.getlamp.com/ Get Lamp: The Text Adventure Documentary]&lt;br /&gt;
&lt;br /&gt;
It's not about Linux, Apache, MySQL or PHP, but if you don't have a one, you might get eaten by a grue.&lt;br /&gt;
&lt;br /&gt;
If there is additional interest, there may be another viewing this week.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Morning Run Wednesday===&lt;br /&gt;
I (Ray Schwartz) am organizing a morning run for anyone that would like to join me.  It will be around 5 to 6 miles.  I usually run a 10 minute per mile pace. And I would like to start around 7am.  Select which days Tuesday or Wednesday or both mornings.  Choose the date you wish via this Doodle link http://www.doodle.com/3tbigutqvkda5ib8&lt;br /&gt;
&lt;br /&gt;
I will map out a course when I arrive and will post it on the wiki.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Veg*n Dinner Wednesday===&lt;br /&gt;
&lt;br /&gt;
We'll pick a place with lots of veg*n options to go eat Wednesday for dinner. Vegetarians and non-vegetarians welcome.&lt;br /&gt;
&lt;br /&gt;
*[http://lovinghut.us/seattle/index.html Loving Hut] Modest price. 1 mile from hotel. Will do bill splitting if we let them know up front. &lt;br /&gt;
&lt;br /&gt;
Talked with Loving Hut and made a reservation for 15 for 6:30. Meet in the hotel lobby at 6.&lt;br /&gt;
&lt;br /&gt;
*Jason Ronallo (jronallo AT gmail.com)&lt;br /&gt;
*Sean Hannan&lt;br /&gt;
*Ed Summers&lt;br /&gt;
*James Stuart&lt;br /&gt;
*Bohyun Kim&lt;br /&gt;
*Bethany Nowviskie&lt;br /&gt;
*Margaret Heller&lt;br /&gt;
*Laura Smart&lt;br /&gt;
*Sibyl Schaefer&lt;br /&gt;
*Cynthia Ng&lt;br /&gt;
*Andrea Shurr&lt;br /&gt;
*Eric James&lt;br /&gt;
*Birkin James Diana&lt;br /&gt;
*Sheree F&lt;br /&gt;
*Misty De Meo&lt;br /&gt;
*Reservation is for 15.&lt;br /&gt;
&lt;br /&gt;
===Meat-Up Dinner Wednesday===&lt;br /&gt;
&lt;br /&gt;
[http://www.bokaseattle.com/ BOKA Kitchen + Bar], 1010 1st Ave (between Spring St &amp;amp; Madison St) - about 1/3 mile/5 min from hotel. We head over from the Amazon Technology Open House and get there by 8PM.&lt;br /&gt;
Very much a eat-local place. Beecher cheddar - yum. Nice, mellow room. We should be back in plenty of time to hit the Drink-Up.&lt;br /&gt;
&lt;br /&gt;
* Cary Gordon&lt;br /&gt;
* Anoop Atre&lt;br /&gt;
&lt;br /&gt;
Note that they have some excellent non-meat options for any meat groupies that want to hang with us.&lt;br /&gt;
&lt;br /&gt;
(if you do not find a suitable burger joint, there are also some top-notch steakhouses in Seattle. Both the Metropolitan Grill and El Gaucho are delightful if folks are OK with $50 steaks. Just FYI, not trying to hijack your meat-up, Cary!. -mjgiarlo)&lt;br /&gt;
&lt;br /&gt;
===[[2012 Craft Brew Drinkup|Craft Brew Drinkup]], Wednesday (9 PM)===&lt;br /&gt;
&lt;br /&gt;
'''Wednesday, February 8, 9 PM-ish -Hospitality Suite'''&lt;br /&gt;
&lt;br /&gt;
Like good beer? Bring some in your luggage! Some of us are planning to bring some of our favorite local, special, or homebrewed beers to share. Interested? Sign up on the [[2012 Craft Brew Drinkup]] page!&lt;br /&gt;
&lt;br /&gt;
===Dim Sum Lunch Thursday===&lt;br /&gt;
&lt;br /&gt;
For those of you staying in town after the last session on Thursday, [http://oasiankitchen.com/ O'Asian Kitchen] has dim sum service during the weekdays. Meet up around 12:35, meeting location tba. Bring cash for easier bill splitting.&lt;br /&gt;
&lt;br /&gt;
*Becky Yoose&lt;br /&gt;
* Declan Fleming - love me some Dim Sum!&lt;br /&gt;
* Adam Wead&lt;br /&gt;
* Heather Pitts&lt;br /&gt;
* Sibyl Schaefer&lt;br /&gt;
* Anoop Atre&lt;br /&gt;
* Dan Suchy&lt;br /&gt;
* Carmen Mitchell&lt;br /&gt;
* Tara Robertson&lt;br /&gt;
* Ray Schwartz&lt;br /&gt;
* Cynthia Ng&lt;br /&gt;
* Corey Harper&lt;br /&gt;
* Joshua Gomez&lt;br /&gt;
* Cary Gordon&lt;br /&gt;
* Mike Giarlo&lt;br /&gt;
* Joe Atzberger&lt;br /&gt;
* Dileshni Jayasinghe&lt;br /&gt;
* Ryan Wick&lt;br /&gt;
&lt;br /&gt;
==Social Map - places of interest==&lt;br /&gt;
[http://g.co/maps/4m5pk Code4lib 2012 - Seattle - social events, hangouts, and places to see]&lt;br /&gt;
&lt;br /&gt;
==Seattle Events Feb 5-9==&lt;br /&gt;
===Saturday, February 4, 2012===&lt;br /&gt;
In case you are showing up really early.&lt;br /&gt;
* Belgianfest: http://www.washingtonbeer.com/belgianfest/&lt;br /&gt;
===Sunday, February 5, 2012===&lt;br /&gt;
* Clinton Fearon &amp;amp; The Boogie Brown Band/Live Wyya/Adrian Xavier/Selecta Raiford/DJ Courtland, Neumos: http://neumos.com/neumos.php&lt;br /&gt;
* Michael The Blind/The Els, Skylark: http://www.skylarkcafe.com/&lt;br /&gt;
* Addaura/Alda/Hallow, Comet&lt;br /&gt;
* &amp;quot;I Am My Own Wife&amp;quot; 7:30pm at Seattle Repertory Theatre (Seattle Center) http://www.seattlerep.org/Plays/1112/IM/&lt;br /&gt;
* Science Fiction + Fantasy short film festival, Encore screening. http://www.empmuseum.org/programs/index.asp?categoryID=216&lt;br /&gt;
&lt;br /&gt;
===Monday, February 6, 2012===&lt;br /&gt;
* Silent Movie Mondays:  Last Command 1928, http://stgpresents.org/artists/?artist=1829#, Show at 7:00pm, The Paramount Theatre $10&lt;br /&gt;
This all-classic film series, First Oscars, is accompanied by live music from the historic Mighty Wurlitzer organ, one of the last three remaining organs of its kind to reside in its original environment, played by critically acclaimed organist Jim Riggs.&lt;br /&gt;
&lt;br /&gt;
===Tuesday, February 7, 2012===&lt;br /&gt;
* Lionize/Maylene &amp;amp; The Sons Of Disaster, El Corazon: http://elcorazonseattle.com/&lt;br /&gt;
* The Pulltab Playboys/Rachel Lyn Harrington &amp;amp; The Knock Outs/The James Low Western Front, Sunset: http://sunsettavern.com/&lt;br /&gt;
* Twin Sister, Vera: http://theveraproject.org/shows/&lt;br /&gt;
* The Features, Chop Suey: http://www.chopsuey.com/&lt;br /&gt;
* Wilco/White Denim, Paramount Theatre: http://stgpresents.org/&lt;br /&gt;
* &amp;quot;I Am My Own Wife&amp;quot; 7:30pm at Seattle Repertory Theatre (Seattle Center) http://www.seattlerep.org/Plays/1112/IM/&lt;br /&gt;
* Intro to Arduino Workshop, 7pm at Metrix Create Space http://metrixcreatespace.com/&lt;br /&gt;
&lt;br /&gt;
===Wednesday, February 8, 2012===&lt;br /&gt;
* The Golden Blondes/The Jet Age/Mr. Drinx &amp;amp; The Pot Heads, Sunset: http://sunsettavern.com/&lt;br /&gt;
* Pipsisewah/The Chasers/The Magic Mirrors, Tractor: http://www.tractortavern.com/ &lt;br /&gt;
* Dengue Fever vs Secret Chiefs 3, Moe Bar http://bit.ly/yJtfXv  (how could you pass the opportunity to see someone play this thing :http://bit.ly/wB5AgZ&lt;br /&gt;
* Amazon Tech in Seattle is having an open house next Wednesday at 5:30 PM with Werner Vogels and David Friedberg of the Climate Corporation. https://aws.amazon.com/amazon-open-house-february-2012/ ([http://g.co/maps/adpnt map])&lt;br /&gt;
&lt;br /&gt;
===Thursday, February 9, 2012===&lt;br /&gt;
* SAM Opening - Gauguin and Polynesia: An Elusive Paradise: http://www.seattleartmuseum.org/gauguin&lt;br /&gt;
* The Jayhawks, Neptune Theater: http://stgpresents.org/&lt;br /&gt;
* Digital Leather, Comet &lt;br /&gt;
* Savani World Quintet/Super Sones, Columbia City Theater: http://www.columbiacitytheater.com/&lt;br /&gt;
* Blvd Park {album release}/Nettle Honey/Creeping Time, Tractor: http://www.tractortavern.com/&lt;br /&gt;
* Eleanor Friedberger, Crocodile: http://thecrocodile.com/index.html&lt;br /&gt;
&lt;br /&gt;
===Ongoing Events===&lt;br /&gt;
* Seattle Art Museum: Tours are every Saturday &amp;amp; Sunday at noon, and the First Thursday of every month at 10:30, 11:30 am, 12:30 &amp;amp; 1:30 pm.&lt;br /&gt;
* EMP:  Exhibits on display include: Battlestar Galactica, Nirvana, Avatar, and Can’t Look Away: The Lure of Horror Film&lt;br /&gt;
* Teatro ZinZanni: ¡Caliente! http://dreams.zinzanni.org/&lt;br /&gt;
* Pacific NW Ballet: performing Don Quixote at McCaw Hall http://www.pnb.org/&lt;br /&gt;
* Oklahoma!, Sunday matinee and nightly: 5th Avenue Theatre, 1308 Fifth Avenue http://www.5thavenue.org/show/oklahoma&lt;br /&gt;
&lt;br /&gt;
==Local events/places==&lt;br /&gt;
* Metrix Create Space&lt;br /&gt;
* Ada's Technical Books&lt;br /&gt;
* Northwest Outdoor Center&lt;br /&gt;
* Center for Wooden Boats&lt;br /&gt;
* Empty Sea Studios acoustic music&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Local Beer Places==&lt;br /&gt;
* Map of [http://beermapping.com/maps/citymaps.php?m=seattle#lat=47.66723703450515&amp;amp;lng=-122.28263854980469&amp;amp;z=5 beer venues] maintained at Beermapping.com.&lt;br /&gt;
* List of [http://www.washingtonbeer.com/breweries/seattle-king-co/ local breweries] ([http://maps.google.com/maps/ms?hl=en&amp;amp;ie=UTF8&amp;amp;msa=0&amp;amp;msid=201783184139227541123.0004813e64758434cb054&amp;amp;source=embed&amp;amp;ll=47.558921,-122.106171&amp;amp;spn=0.442982,1.234589&amp;amp;z=10&amp;amp;source=embed map]) maintained by the Washington Beer Commission&lt;br /&gt;
* Map of [http://www.ratebeer.com/Places/RegionMap.asp?rid=7600 beer venues] maintained by Ratebeer.com.&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
[http://orbiscascade.org/index/c4l-things-to-do-in-seattle Things to do in Seattle, from the hosts]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_Craft_Brew_Drinkup&amp;diff=10802</id>
		<title>2012 Craft Brew Drinkup</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_Craft_Brew_Drinkup&amp;diff=10802"/>
				<updated>2012-02-03T16:33:27Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* Buying Beer in Seattle */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Wednesday, February 8, after 9 PM, in hospitality suite'''&lt;br /&gt;
&lt;br /&gt;
The Craft Brew Drinkup at Code4lib 2012 is all about sharing and enjoying good beer with fellow conference attendees. The idea is to bring bottles of your favorite beers.&lt;br /&gt;
&lt;br /&gt;
While you're not obligated to bring ''local beers'' from whereever you're from, participants are definitely encouraged to bring beer that you think is special and might be somewhat hard for others outside your area to find. Homebrew is especially welcome. Sign up below with your name, where you're from, and list a few brews or bottles you're thinking about (but not necessarily committing to) bringing along. You can also request that people bring specific beer if you so desire, but don't necessarily expect that your wishes will be granted.&lt;br /&gt;
&lt;br /&gt;
''If you do not check bags or otherwise cannot arrange to bring beer from where you call home, you may be interested in buying beer from a local beer store. See the &amp;quot;Buying Beer in Seattle&amp;quot; section below for suggestions.''&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=== Sign up ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; class=&amp;quot;sortable&amp;quot; &lt;br /&gt;
! Name&lt;br /&gt;
! Location&lt;br /&gt;
! Brews or Breweries I might bring&lt;br /&gt;
! Requests&lt;br /&gt;
|-&lt;br /&gt;
| anarchivist&lt;br /&gt;
| New Haven CT/Brooklyn NY&lt;br /&gt;
| '''Purchased''': Element Brewing Dark Element, Element Brewing Extra Special Oak, Olde Burnside Ten Penny Ale Reserve, Cisco Captain Swain's Extra Stout&lt;br /&gt;
'''Special bottles''': Who knows? Something special.&lt;br /&gt;
| Imperial porters/stouts; really funky-/Brett-tasting beers or wild ales; highly-hopped stuff; interesting session beers&lt;br /&gt;
|-&lt;br /&gt;
| kayiwa&lt;br /&gt;
| Chicago IL&lt;br /&gt;
| Bourbon County Stout; New Glarus Barleywine&lt;br /&gt;
| Barleywines; Aged Stouts; Anything from Deschutes&lt;br /&gt;
(psst, Francis: I've got some homebrewed barleywine aging in the basement; i won't be in Seattle but I'll bring some to C4L-Midwest -[[User:Kenirwin|Kenirwin]] 13:26, 29 January 2012 (PST))&lt;br /&gt;
|-&lt;br /&gt;
| danwho&lt;br /&gt;
| San Diego, CA&lt;br /&gt;
| Alpine Brewery Exponential Hoppiness; Iron Fist; maybe Lost Abbey; Bud Light&lt;br /&gt;
| hoppy imperials, sours, funky farmhouses.  Also, I'd vote Wednesday or Tuesday evening since a lot of folks are doing the Microsoft tour and/or newcomer dinners Monday&lt;br /&gt;
|-&lt;br /&gt;
| declan&lt;br /&gt;
| San Diego, CA&lt;br /&gt;
| hmm, looking over the cellar... Parabola, Black Tuesday, Cherry Adam, Angel Share, Captain stout, Silva.... we'll see!&lt;br /&gt;
| dark, black stuff.  like my heart.  Or sours.  Or Belgies.  Founders, Bells, New Glaris, Goose Island.&lt;br /&gt;
|-&lt;br /&gt;
| awead&lt;br /&gt;
| Cleveland, OH&lt;br /&gt;
| Founders Porter, some new IPA I found...&lt;br /&gt;
| Stuff that doesn't suck.&lt;br /&gt;
|-&lt;br /&gt;
|bibliotechy&lt;br /&gt;
|Atlanta, Ga&lt;br /&gt;
|Some Terrapin beers... Hopsecutioner,  Sweetwater Brewery Exodus Porter if it is still around&lt;br /&gt;
|Boreale noire, rousse or cuivre from Montreal! &lt;br /&gt;
|-&lt;br /&gt;
|sdellis&lt;br /&gt;
|Lambertville, NJ&lt;br /&gt;
|Riverhorse... (possibly Hop Hazard, but I'll see what's fresh).  Maybe Lionshead (pilsner) from Doylestown, PA (legend has it you can drink as much as you want and never get a hangover).&lt;br /&gt;
|Bitters, pub style, IPAs, brown ales&lt;br /&gt;
|-&lt;br /&gt;
|jastirn&lt;br /&gt;
|Kansas City, KS&lt;br /&gt;
|Whatever I can get from Wilderness Brewing (KC), Free State (Lawrence, KS), Schlafly Imperial Stout (St. Louis), and Blvd Smokestack (KC) (for Danwho)&lt;br /&gt;
| More blueberry stout, stouts, lagers, spicy&lt;br /&gt;
|-&lt;br /&gt;
|HLPitts&lt;br /&gt;
|Salem, OR&lt;br /&gt;
|Hopworks barleywine, Rogue Chocolate Stout, Seven Brides porter, Wandering Aengus cider, and a small variety from Deschutes (including Obsidian for anarchivist)&lt;br /&gt;
|stouts/porters, sours, red ales&lt;br /&gt;
|-&lt;br /&gt;
|bohyunkim&lt;br /&gt;
|Miami, FL&lt;br /&gt;
|same as last year - canned bears from Oskar Blues brewery in Colorado unless I spot something better&lt;br /&gt;
|cider, Rogue Dead Guy, malty, fruity, blonde/gloden ale &lt;br /&gt;
|-&lt;br /&gt;
|carmendarlene&lt;br /&gt;
|San Diego, CA&lt;br /&gt;
|something from SoCal...Maybe more Alpine. Going shopping at the Best Damn Beer Store later this week.&lt;br /&gt;
|New Glaris, Goose Island, Three Floyds, Cantillon...stuff that I can't get in San Diego. &lt;br /&gt;
|-&lt;br /&gt;
|flyingzumwalt &amp;amp; jcoyne&lt;br /&gt;
|Minneapolis, MN&lt;br /&gt;
|Surly Coffee Bender &amp;amp; Surly Cynic, Bell's Two Hearted, Lift Bridge Farm Girl, Crispin Cider&lt;br /&gt;
|Revivalist beers (ie. [http://www.yardsbrewing.com/ales_poor-richards-tavern-spruce.asp Yard's Revolutionary Beers] ), New Glarus, Yuengling&lt;br /&gt;
|-&lt;br /&gt;
|singlesoliloquy&lt;br /&gt;
|St. Louis, MO&lt;br /&gt;
|Schlafly, Six Row.&lt;br /&gt;
|Good pilsners.&lt;br /&gt;
|-&lt;br /&gt;
|pberry&lt;br /&gt;
|Chico, CA&lt;br /&gt;
|Hope to buy Chico stuff in SEA, Bigfoot was just released.&lt;br /&gt;
|Ales&lt;br /&gt;
|-&lt;br /&gt;
|calvinmah&lt;br /&gt;
|Vancouver, Canada&lt;br /&gt;
|driving to SEA so I'll bring a crate&lt;br /&gt;
|Beer&lt;br /&gt;
|-&lt;br /&gt;
|tara robertson&lt;br /&gt;
|Vancouver, Canada&lt;br /&gt;
|two limited release beers from [http://gib.ca/beer/ Granville Island Brewing]: Fresh Hop ESP, Imperial IPA&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|younga, ward, jeff&lt;br /&gt;
|Seattle, WA&lt;br /&gt;
|Random assortment of growlers: Georgetown Brewery, Big Time, Fremont, Epic Ales.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|lrobare&lt;br /&gt;
|Eugene, OR&lt;br /&gt;
|Ninkasi, probably Total Domination and something else&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|scollett&lt;br /&gt;
|Seattle, WA&lt;br /&gt;
|Live in Berkeley, CA, but will buy local or raid the beer stash of my Seattle relatives.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|lisapisa77&lt;br /&gt;
|Reno, NV&lt;br /&gt;
|Ichthyosaur &amp;quot;Icky&amp;quot; IPA from Great Basin and probably something else&lt;br /&gt;
|Alagash or Victory or brown ales&lt;br /&gt;
|-&lt;br /&gt;
|-&lt;br /&gt;
|chrpr&lt;br /&gt;
|New York, NY&lt;br /&gt;
|Brooklyn Sorachi Ace, Southhampton Saison, Probably some other stuff&lt;br /&gt;
|Sours, Farmhouse, Misc. high abv goodness...&lt;br /&gt;
|-&lt;br /&gt;
|carboy&lt;br /&gt;
|Arlington, TX&lt;br /&gt;
|Yeti, Mephistopheles&lt;br /&gt;
|Imperial stout, IPA, barleywine&lt;br /&gt;
|-&lt;br /&gt;
|mbaggett&lt;br /&gt;
|Knoxville, TN&lt;br /&gt;
|I won't be checking a bag, but I'll be raiding all the Seattle beer spots this weekend. I hope to surprise everyone with a bottle of Pliny the Elder or at least the new Oak Aged Espresso Yeti.&lt;br /&gt;
|Double IPAs, West Coast IPAs, Saisons and Sours&lt;br /&gt;
|-&lt;br /&gt;
|dlovins&lt;br /&gt;
|New York,  NY&lt;br /&gt;
| Not sure. Something local&lt;br /&gt;
|&amp;lt;del&amp;gt;Maybe a hefeweizen of some sort&amp;lt;/del&amp;gt; something good in any case&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Suggestions ===&lt;br /&gt;
&lt;br /&gt;
'''Add using the following format: (person who you are making the request of): (your request) - (your name)'''&lt;br /&gt;
&lt;br /&gt;
* Unnamed persons from the Keystone State: Sly Fox, any special Weyerbacher - anarchivist&lt;br /&gt;
* anyone: Boulevard smokestack series - danwho&lt;br /&gt;
* whosoever brought blueberry stout last year, more of that please - jastirn&lt;br /&gt;
* Oregonians/PNW folks: Deschutes Hop Henge (cuz it's seasonal) and Obsidian (cuz I like it) - anarchivist&lt;br /&gt;
* younga/Seattlites: Georgetown Donkey Deux; Georgetown Braggott - anarchivist&lt;br /&gt;
* if by chance anyone is coming from Salt Lake City: I would love Big Bad Baptist from Epic. Or the Wit if it's available again (I think it's the wrong season though). - HLPitts&lt;br /&gt;
&lt;br /&gt;
=== Buying Beer in Seattle ===&lt;br /&gt;
&lt;br /&gt;
from an email to the code4lib list: &lt;br /&gt;
&lt;br /&gt;
: I can think of three good bottleshops (all w/ taps in case you want a growler) that are located on bus lines from downtown:&lt;br /&gt;
:&lt;br /&gt;
: * [http://bottleworksbeerstore.blogspot.com/ Bottleworks]: Probably the shop I frequent the most. Take the 16 to Wallingford.&lt;br /&gt;
: * [http://www.lastdropbeershop.com/ Last Drop]: Take the 71,72, or 73 north from downtown and get off at 80th.&lt;br /&gt;
: * [http://www.seattlebeerauthority.com/ Beer Authority]: probably the quickest trip from downtown on the 522. get off at the 125th St stop in Lake City and walk north a couple of blocks.&lt;br /&gt;
: * [http://www.fullthrottlebottles.com/ Full Throttle Bottles]: Buses 131, 106, 23 --about 30 minute ride. &lt;br /&gt;
: * Also, QFC (large grocery store chain) usually has a great selection.&lt;br /&gt;
: * Lots of other pub/beer places noted on [http://g.co/maps/4m5pk the map]&lt;br /&gt;
&lt;br /&gt;
=== Disclaimers === &lt;br /&gt;
&lt;br /&gt;
* This is an unofficial event organized by attendees of Code4lib 2012.&lt;br /&gt;
* All guests at the Drinkup must be 21 years of age or over with a [http://www.cherylslastcall.com/pdfs/Acceptable-ID-Forms.pdf valid form of ID].&lt;br /&gt;
* Any participation in the Drinkup is at your own risk.&lt;br /&gt;
* All guests are expected to drink responsibly and behave appropriately.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Packing and Shipping Beer ===&lt;br /&gt;
&lt;br /&gt;
If you're flying to Code4lib, you will have to consider how to bring your beer. Some attendees in past years have packed beer in their checked luggage, and others have purchased a beer shipper that was checked separately as luggage. In any event, '''you will not be able to bring beer in carryon luggage.'''&lt;br /&gt;
&lt;br /&gt;
The following are links to resources that provide info on packing your beer for transit.&lt;br /&gt;
&lt;br /&gt;
* [http://barlowbrewing.com/2010/11/11/how-to-pack-and-ship-beer/ How to pack and ship beer]&lt;br /&gt;
* [http://baltimoresnacker.blogspot.com/2009/06/how-to-pack-beer-and-wine-into-your.html How to pack beer and wine into your luggage]&lt;br /&gt;
* [http://beeradvocate.com/forum/read/3880083 Flying With Beer (Beer Advocate forums)]&lt;br /&gt;
* [http://beeradvocate.com/forum/read/4364472 Shipping beer while on business travel (Beer Advocate forums)]&lt;br /&gt;
* [http://www.mrboxonline.com/bottle-styrofoam-beer-shipper-p-7579.html A sample styrofoam beer shipper/box combo]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_Craft_Brew_Drinkup&amp;diff=10801</id>
		<title>2012 Craft Brew Drinkup</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_Craft_Brew_Drinkup&amp;diff=10801"/>
				<updated>2012-02-03T16:32:59Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* Buying Beer in Seattle */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Wednesday, February 8, after 9 PM, in hospitality suite'''&lt;br /&gt;
&lt;br /&gt;
The Craft Brew Drinkup at Code4lib 2012 is all about sharing and enjoying good beer with fellow conference attendees. The idea is to bring bottles of your favorite beers.&lt;br /&gt;
&lt;br /&gt;
While you're not obligated to bring ''local beers'' from whereever you're from, participants are definitely encouraged to bring beer that you think is special and might be somewhat hard for others outside your area to find. Homebrew is especially welcome. Sign up below with your name, where you're from, and list a few brews or bottles you're thinking about (but not necessarily committing to) bringing along. You can also request that people bring specific beer if you so desire, but don't necessarily expect that your wishes will be granted.&lt;br /&gt;
&lt;br /&gt;
''If you do not check bags or otherwise cannot arrange to bring beer from where you call home, you may be interested in buying beer from a local beer store. See the &amp;quot;Buying Beer in Seattle&amp;quot; section below for suggestions.''&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=== Sign up ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; class=&amp;quot;sortable&amp;quot; &lt;br /&gt;
! Name&lt;br /&gt;
! Location&lt;br /&gt;
! Brews or Breweries I might bring&lt;br /&gt;
! Requests&lt;br /&gt;
|-&lt;br /&gt;
| anarchivist&lt;br /&gt;
| New Haven CT/Brooklyn NY&lt;br /&gt;
| '''Purchased''': Element Brewing Dark Element, Element Brewing Extra Special Oak, Olde Burnside Ten Penny Ale Reserve, Cisco Captain Swain's Extra Stout&lt;br /&gt;
'''Special bottles''': Who knows? Something special.&lt;br /&gt;
| Imperial porters/stouts; really funky-/Brett-tasting beers or wild ales; highly-hopped stuff; interesting session beers&lt;br /&gt;
|-&lt;br /&gt;
| kayiwa&lt;br /&gt;
| Chicago IL&lt;br /&gt;
| Bourbon County Stout; New Glarus Barleywine&lt;br /&gt;
| Barleywines; Aged Stouts; Anything from Deschutes&lt;br /&gt;
(psst, Francis: I've got some homebrewed barleywine aging in the basement; i won't be in Seattle but I'll bring some to C4L-Midwest -[[User:Kenirwin|Kenirwin]] 13:26, 29 January 2012 (PST))&lt;br /&gt;
|-&lt;br /&gt;
| danwho&lt;br /&gt;
| San Diego, CA&lt;br /&gt;
| Alpine Brewery Exponential Hoppiness; Iron Fist; maybe Lost Abbey; Bud Light&lt;br /&gt;
| hoppy imperials, sours, funky farmhouses.  Also, I'd vote Wednesday or Tuesday evening since a lot of folks are doing the Microsoft tour and/or newcomer dinners Monday&lt;br /&gt;
|-&lt;br /&gt;
| declan&lt;br /&gt;
| San Diego, CA&lt;br /&gt;
| hmm, looking over the cellar... Parabola, Black Tuesday, Cherry Adam, Angel Share, Captain stout, Silva.... we'll see!&lt;br /&gt;
| dark, black stuff.  like my heart.  Or sours.  Or Belgies.  Founders, Bells, New Glaris, Goose Island.&lt;br /&gt;
|-&lt;br /&gt;
| awead&lt;br /&gt;
| Cleveland, OH&lt;br /&gt;
| Founders Porter, some new IPA I found...&lt;br /&gt;
| Stuff that doesn't suck.&lt;br /&gt;
|-&lt;br /&gt;
|bibliotechy&lt;br /&gt;
|Atlanta, Ga&lt;br /&gt;
|Some Terrapin beers... Hopsecutioner,  Sweetwater Brewery Exodus Porter if it is still around&lt;br /&gt;
|Boreale noire, rousse or cuivre from Montreal! &lt;br /&gt;
|-&lt;br /&gt;
|sdellis&lt;br /&gt;
|Lambertville, NJ&lt;br /&gt;
|Riverhorse... (possibly Hop Hazard, but I'll see what's fresh).  Maybe Lionshead (pilsner) from Doylestown, PA (legend has it you can drink as much as you want and never get a hangover).&lt;br /&gt;
|Bitters, pub style, IPAs, brown ales&lt;br /&gt;
|-&lt;br /&gt;
|jastirn&lt;br /&gt;
|Kansas City, KS&lt;br /&gt;
|Whatever I can get from Wilderness Brewing (KC), Free State (Lawrence, KS), Schlafly Imperial Stout (St. Louis), and Blvd Smokestack (KC) (for Danwho)&lt;br /&gt;
| More blueberry stout, stouts, lagers, spicy&lt;br /&gt;
|-&lt;br /&gt;
|HLPitts&lt;br /&gt;
|Salem, OR&lt;br /&gt;
|Hopworks barleywine, Rogue Chocolate Stout, Seven Brides porter, Wandering Aengus cider, and a small variety from Deschutes (including Obsidian for anarchivist)&lt;br /&gt;
|stouts/porters, sours, red ales&lt;br /&gt;
|-&lt;br /&gt;
|bohyunkim&lt;br /&gt;
|Miami, FL&lt;br /&gt;
|same as last year - canned bears from Oskar Blues brewery in Colorado unless I spot something better&lt;br /&gt;
|cider, Rogue Dead Guy, malty, fruity, blonde/gloden ale &lt;br /&gt;
|-&lt;br /&gt;
|carmendarlene&lt;br /&gt;
|San Diego, CA&lt;br /&gt;
|something from SoCal...Maybe more Alpine. Going shopping at the Best Damn Beer Store later this week.&lt;br /&gt;
|New Glaris, Goose Island, Three Floyds, Cantillon...stuff that I can't get in San Diego. &lt;br /&gt;
|-&lt;br /&gt;
|flyingzumwalt &amp;amp; jcoyne&lt;br /&gt;
|Minneapolis, MN&lt;br /&gt;
|Surly Coffee Bender &amp;amp; Surly Cynic, Bell's Two Hearted, Lift Bridge Farm Girl, Crispin Cider&lt;br /&gt;
|Revivalist beers (ie. [http://www.yardsbrewing.com/ales_poor-richards-tavern-spruce.asp Yard's Revolutionary Beers] ), New Glarus, Yuengling&lt;br /&gt;
|-&lt;br /&gt;
|singlesoliloquy&lt;br /&gt;
|St. Louis, MO&lt;br /&gt;
|Schlafly, Six Row.&lt;br /&gt;
|Good pilsners.&lt;br /&gt;
|-&lt;br /&gt;
|pberry&lt;br /&gt;
|Chico, CA&lt;br /&gt;
|Hope to buy Chico stuff in SEA, Bigfoot was just released.&lt;br /&gt;
|Ales&lt;br /&gt;
|-&lt;br /&gt;
|calvinmah&lt;br /&gt;
|Vancouver, Canada&lt;br /&gt;
|driving to SEA so I'll bring a crate&lt;br /&gt;
|Beer&lt;br /&gt;
|-&lt;br /&gt;
|tara robertson&lt;br /&gt;
|Vancouver, Canada&lt;br /&gt;
|two limited release beers from [http://gib.ca/beer/ Granville Island Brewing]: Fresh Hop ESP, Imperial IPA&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|younga, ward, jeff&lt;br /&gt;
|Seattle, WA&lt;br /&gt;
|Random assortment of growlers: Georgetown Brewery, Big Time, Fremont, Epic Ales.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|lrobare&lt;br /&gt;
|Eugene, OR&lt;br /&gt;
|Ninkasi, probably Total Domination and something else&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|scollett&lt;br /&gt;
|Seattle, WA&lt;br /&gt;
|Live in Berkeley, CA, but will buy local or raid the beer stash of my Seattle relatives.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|lisapisa77&lt;br /&gt;
|Reno, NV&lt;br /&gt;
|Ichthyosaur &amp;quot;Icky&amp;quot; IPA from Great Basin and probably something else&lt;br /&gt;
|Alagash or Victory or brown ales&lt;br /&gt;
|-&lt;br /&gt;
|-&lt;br /&gt;
|chrpr&lt;br /&gt;
|New York, NY&lt;br /&gt;
|Brooklyn Sorachi Ace, Southhampton Saison, Probably some other stuff&lt;br /&gt;
|Sours, Farmhouse, Misc. high abv goodness...&lt;br /&gt;
|-&lt;br /&gt;
|carboy&lt;br /&gt;
|Arlington, TX&lt;br /&gt;
|Yeti, Mephistopheles&lt;br /&gt;
|Imperial stout, IPA, barleywine&lt;br /&gt;
|-&lt;br /&gt;
|mbaggett&lt;br /&gt;
|Knoxville, TN&lt;br /&gt;
|I won't be checking a bag, but I'll be raiding all the Seattle beer spots this weekend. I hope to surprise everyone with a bottle of Pliny the Elder or at least the new Oak Aged Espresso Yeti.&lt;br /&gt;
|Double IPAs, West Coast IPAs, Saisons and Sours&lt;br /&gt;
|-&lt;br /&gt;
|dlovins&lt;br /&gt;
|New York,  NY&lt;br /&gt;
| Not sure. Something local&lt;br /&gt;
|&amp;lt;del&amp;gt;Maybe a hefeweizen of some sort&amp;lt;/del&amp;gt; something good in any case&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Suggestions ===&lt;br /&gt;
&lt;br /&gt;
'''Add using the following format: (person who you are making the request of): (your request) - (your name)'''&lt;br /&gt;
&lt;br /&gt;
* Unnamed persons from the Keystone State: Sly Fox, any special Weyerbacher - anarchivist&lt;br /&gt;
* anyone: Boulevard smokestack series - danwho&lt;br /&gt;
* whosoever brought blueberry stout last year, more of that please - jastirn&lt;br /&gt;
* Oregonians/PNW folks: Deschutes Hop Henge (cuz it's seasonal) and Obsidian (cuz I like it) - anarchivist&lt;br /&gt;
* younga/Seattlites: Georgetown Donkey Deux; Georgetown Braggott - anarchivist&lt;br /&gt;
* if by chance anyone is coming from Salt Lake City: I would love Big Bad Baptist from Epic. Or the Wit if it's available again (I think it's the wrong season though). - HLPitts&lt;br /&gt;
&lt;br /&gt;
=== Buying Beer in Seattle ===&lt;br /&gt;
&lt;br /&gt;
from an email to the code4lib list: &lt;br /&gt;
&lt;br /&gt;
: I can think of three good bottleshops (all w/ taps in case you want a growler) that are located on bus lines from downtown:&lt;br /&gt;
:&lt;br /&gt;
: * [http://bottleworksbeerstore.blogspot.com/ Bottleworks]: Probably the shop I frequent the most. Take the 16 to Wallingford.&lt;br /&gt;
: * [http://www.lastdropbeershop.com/ Last Drop]: Take the 71,72, or 73 north from downtown and get off at 80th.&lt;br /&gt;
: * [http://www.seattlebeerauthority.com/ Beer Authority]: probably the quickest trip from downtown on the 522. get off at the 125th St stop in Lake City and walk north a couple of blocks.&lt;br /&gt;
: * [http://www.fullthrottlebottles.com/]: Buses 131, 106, 23 --about 30 minute ride. &lt;br /&gt;
: * Also, QFC (large grocery store chain) usually has a great selection.&lt;br /&gt;
: * Lots of other pub/beer places noted on [http://g.co/maps/4m5pk the map]&lt;br /&gt;
&lt;br /&gt;
=== Disclaimers === &lt;br /&gt;
&lt;br /&gt;
* This is an unofficial event organized by attendees of Code4lib 2012.&lt;br /&gt;
* All guests at the Drinkup must be 21 years of age or over with a [http://www.cherylslastcall.com/pdfs/Acceptable-ID-Forms.pdf valid form of ID].&lt;br /&gt;
* Any participation in the Drinkup is at your own risk.&lt;br /&gt;
* All guests are expected to drink responsibly and behave appropriately.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Packing and Shipping Beer ===&lt;br /&gt;
&lt;br /&gt;
If you're flying to Code4lib, you will have to consider how to bring your beer. Some attendees in past years have packed beer in their checked luggage, and others have purchased a beer shipper that was checked separately as luggage. In any event, '''you will not be able to bring beer in carryon luggage.'''&lt;br /&gt;
&lt;br /&gt;
The following are links to resources that provide info on packing your beer for transit.&lt;br /&gt;
&lt;br /&gt;
* [http://barlowbrewing.com/2010/11/11/how-to-pack-and-ship-beer/ How to pack and ship beer]&lt;br /&gt;
* [http://baltimoresnacker.blogspot.com/2009/06/how-to-pack-beer-and-wine-into-your.html How to pack beer and wine into your luggage]&lt;br /&gt;
* [http://beeradvocate.com/forum/read/3880083 Flying With Beer (Beer Advocate forums)]&lt;br /&gt;
* [http://beeradvocate.com/forum/read/4364472 Shipping beer while on business travel (Beer Advocate forums)]&lt;br /&gt;
* [http://www.mrboxonline.com/bottle-styrofoam-beer-shipper-p-7579.html A sample styrofoam beer shipper/box combo]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_c4l2012_social_activities&amp;diff=10633</id>
		<title>2012 c4l2012 social activities</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_c4l2012_social_activities&amp;diff=10633"/>
				<updated>2012-01-31T23:36:44Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* Seattle Events Feb 5-9 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Ideas==&lt;br /&gt;
* Woodinville distillery tour&lt;br /&gt;
* Seattle distillery tour&lt;br /&gt;
* Favorite local breweries&lt;br /&gt;
* Favorite local tea houses&lt;br /&gt;
* Favorite local used bookstores&lt;br /&gt;
* Visit hackerspace&lt;br /&gt;
** +1&lt;br /&gt;
* Evergreen/Koha - Open Source ILS brewery/tea house meetup&lt;br /&gt;
&lt;br /&gt;
==Planned events==&lt;br /&gt;
&lt;br /&gt;
===[[2012 Craft Brew Drinkup|Craft Brew Drinkup]]===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time TBA; to be held in the Hospitality Suite.'''&lt;br /&gt;
&lt;br /&gt;
Like good beer? Bring some in your luggage! Some of us are planning to bring some of our favorite local, special, or homebrewed beers to share. Interested? Sign up on the [[2012 Craft Brew Drinkup]] page!&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Get Lamp&amp;quot; showing===&lt;br /&gt;
&lt;br /&gt;
Some attendees are organizing a showing of [http://www.getlamp.com/ Get Lamp: The Text Adventure Documentary] in the hospitality suite.&lt;br /&gt;
&lt;br /&gt;
To indicate your preference of time and date for the showing, please fill out [http://www.doodle.com/p4c32i3b2ybsrkbh this Doodle poll].&lt;br /&gt;
&lt;br /&gt;
===Newcomer dinner Tuesday===&lt;br /&gt;
First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating &amp;lt;strike&amp;gt;discussions about&amp;lt;/strike&amp;gt; demonstrations of the many uses of &amp;lt;strike&amp;gt;bacon&amp;lt;/strike&amp;gt; &amp;lt;strike&amp;gt;dongles&amp;lt;/strike&amp;gt; XML.&lt;br /&gt;
&lt;br /&gt;
Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!&lt;br /&gt;
&lt;br /&gt;
'''Plans'''&lt;br /&gt;
* When: Tuesday evening (2/7) '''Note that this year's dinner is on Tuesday'''&lt;br /&gt;
* Time: 6 PM (ish) or whenever you can get your group together&lt;br /&gt;
* Mastermind (if you have any questions): [mailto:yoosebec@grinnell.edu Becky Yoose]&lt;br /&gt;
&lt;br /&gt;
''Guidelines:''&lt;br /&gt;
*Max of '''6''' per group&lt;br /&gt;
**Please, no waitlisting :(&lt;br /&gt;
*ID yourselves so we can get a good mix of new people and veterans in each group&lt;br /&gt;
**New folks - n&lt;br /&gt;
**c4l vets - v&lt;br /&gt;
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group :)''')&lt;br /&gt;
**Leader duties&lt;br /&gt;
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library coders &lt;br /&gt;
***Herd folks from hotel to restaurant (know where you're going!)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Happenings'''&lt;br /&gt;
&lt;br /&gt;
Crashing the [http://www.seattlerb.org/ Seattle Ruby] meetup, which meets on Capital Hill at 7:00 on Tuesdays. Eat at [http://www.yelp.com/biz/poppy-seattle Poppy] before.  Leaving from the hotel lobby at 6:00.  &lt;br /&gt;
* Matt Zumwalt (leader) - v&lt;br /&gt;
''If you dig Ruby, come to this.  Seattle ruby produced Nokogiri, Vlad, Rubygems.org ....''&lt;br /&gt;
&lt;br /&gt;
'''Restaurants'''&lt;br /&gt;
&lt;br /&gt;
'''Restaurants within .25 miles of the hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://www.sazeracrestaurant.com/index.php Sazerac] (AWESOME happy hour menu that runs until 8)&lt;br /&gt;
* Martin Haye - n&lt;br /&gt;
* William Gunn - n&lt;br /&gt;
* Rebecca Jones - n&lt;br /&gt;
* Chick Markley - v&lt;br /&gt;
* Al Cornish - v&lt;br /&gt;
* Keri Thompson - n&lt;br /&gt;
*'''capped at 6''' ''(So, who's the fearless leader of this group? ~yo_bj)''&lt;br /&gt;
&lt;br /&gt;
[http://oasiankitchen.com/ O'Asian Kitchen and Lounge]  (Asian) &lt;br /&gt;
&lt;br /&gt;
'''Restaurants between .25 miles and .5 miles of the hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://www.pikebrewing.com/index_html.shtml Pike Brewing] (local brewery, pub food)&lt;br /&gt;
* Ken Varnum - n&lt;br /&gt;
* Chad Nelson - n&lt;br /&gt;
* Ed Summers - v&lt;br /&gt;
* Tommy Ingulfsen - n&lt;br /&gt;
* Adam Wead - v or .5n&lt;br /&gt;
*''(So, who's the fearless leader of this group? ~yo_bj)''&lt;br /&gt;
&lt;br /&gt;
[http://www.rockbottom.com/ The Rock Bottom Restaurant &amp;amp; Brewery] (American)&lt;br /&gt;
&lt;br /&gt;
[http://www.wildginger.net/ Wild Ginger] (Asian, a bit overpriced)&lt;br /&gt;
&lt;br /&gt;
[http://www.thepurplecafe.com/index.html Purple Cafe] (American, Wine Bar)&lt;br /&gt;
* Calvin Mah - (leader) - v&lt;br /&gt;
* David Isaak - n&lt;br /&gt;
* Aaron Collier - n&lt;br /&gt;
&lt;br /&gt;
[http://www.cafepaloma.com/ Cafe Paloma] (Mediterranean)&lt;br /&gt;
* Jean Rainwater (leader) - v&lt;br /&gt;
* Kelley McGrath - n&lt;br /&gt;
* Lori Robare - n&lt;br /&gt;
&lt;br /&gt;
[http://www.thecollinspub.com/ Collins Pub] (Pub Food, great beer selection)&lt;br /&gt;
* Francis Kayiwa - (leader) &amp;quot;(get hold of me at first dot last name at goog as the date gets closer with your mobile)&amp;quot; v&lt;br /&gt;
* Michael Lindsey - v&lt;br /&gt;
* Dan Suchy - v&lt;br /&gt;
* David Drexler - n&lt;br /&gt;
* Laura Smart - n&lt;br /&gt;
* Heather Pitts - n&lt;br /&gt;
*'''capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.mcmenamins.com/311-six-arms-home Six Arms - McMenamins] (Pub Food &amp;amp; they brew their own beer) ''Meeting place TBA. Leave email and I'll coordinate late next week. --Joel''&lt;br /&gt;
* Joel Richard (richardjm AT si.edu) (leader) - v&lt;br /&gt;
* Margaret Heller - v&lt;br /&gt;
* Sibyl Schaefer (sschaefer AT rockarch . org) - v&lt;br /&gt;
* Tim Lepczyk (timlepczyk AT gmail.com) - n&lt;br /&gt;
* Ray Schwartz (schwartzr2@wpunj.edu) - v&lt;br /&gt;
* Andrea Schurr (andrea-schurr AT utc DOT edu) - v(2nd-timer)&lt;br /&gt;
* '''capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.611supreme.com/ 611 Supreme] (Crepes and Full Bar) ''Meet in the conference hotel lobby at 6pm. Look for the short woman in a trench coat and wide brim hat ~Becky''&lt;br /&gt;
&lt;br /&gt;
*Becky Yoose (leader) - v &lt;br /&gt;
*Cynthia Ng - n&lt;br /&gt;
*Zoe Chao - v&lt;br /&gt;
*Justin Coyne - n&lt;br /&gt;
*Stephanie Collett - n&lt;br /&gt;
*Bethany Nowviskie - n&lt;br /&gt;
*'''capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.panafricamarket.com/wp/ Pan Africa Restaurant &amp;amp; Bar] (Pan African) CLOSED MONDAYS ''Veg and non-veg options available. Located in the Pike Place Market, so we can explore a bit too, though the fish flinging will be over by then. Meet in the conference hotel lobby at 6PM.''&lt;br /&gt;
&lt;br /&gt;
*Jason Ronallo (leader; happy to lead to any other veg-friendly place as an alternative) - v&lt;br /&gt;
*Nettie Lagace - n&lt;br /&gt;
*Bohyun Kim - n/v (2nd-timer)&lt;br /&gt;
*Wendy Robertson - n&lt;br /&gt;
*Jennifer Bowen - n/v (3rd timer)&lt;br /&gt;
&lt;br /&gt;
'''Restaurants between .5 and 1 mile from hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://tomdouglas.com/index.php?page=palace-kitchen-dinner Palace Kitchen] (another Tom Douglas restaurant, w/ a focus on meat).  ''I have made a reservation for 6 at 8pm. Let's meet in the conference lobby at 6:30pm and make our way slowly over; we will find things to do in the interim. Look for Mike Giarlo, a man who may be holding a sign that says &amp;quot;HI I'M MIKE GIARLO&amp;quot; or otherwise shouting his name or looking confused.''&lt;br /&gt;
&lt;br /&gt;
* Mike Giarlo (leader) - v&lt;br /&gt;
* Carmen Mitchell - n&lt;br /&gt;
* Daniel Lovins - v&lt;br /&gt;
* Cary Gordon - v &lt;br /&gt;
* Declan Fleming - v&lt;br /&gt;
* Amy Unger - n&lt;br /&gt;
* (CAPPED AT SIX!)&lt;br /&gt;
&lt;br /&gt;
[http://sitkaandspruce.com/ Sitka and Spruce] (Eclectic, super-local and super-seasonal.) ''We have a reservation for 6 at 8:15pm. We'll meet in the conference lobby at 6:30 pm and head over - the owners also run [http://www.ferdinandthebar.com/home/ Bar Ferd'nand], a wine shop/bar in the same building, and we can kill time there before we eat. Look for Mark Matienzo or Hillel Arnold.''&lt;br /&gt;
&lt;br /&gt;
* Mark Matienzo (leader) - v&lt;br /&gt;
* Hillel Arnold - sophomore&lt;br /&gt;
* Devon Smith - v&lt;br /&gt;
* bernardo gomez - n&lt;br /&gt;
* Derek Merleaux - sophmore&lt;br /&gt;
* Jennifer Weintraub - n&lt;br /&gt;
* (CAPPED AT SIX!)&lt;br /&gt;
&lt;br /&gt;
[http://www.yelp.com/biz/japonessa-seattle Japonessa Restaurant] (Japanese + full bar)&lt;br /&gt;
&lt;br /&gt;
[http://tomdouglas.com/index.php?page=serious-pie Serious Pie] (Tom Douglas restaurant, inventive pizzas, good local beer list). &lt;br /&gt;
&lt;br /&gt;
[http://www.allmenus.com/wa/seattle/204592-ballet-restaurant/menu/ Ballet] (Vietnamese)&lt;br /&gt;
&lt;br /&gt;
[http://www.kokebrestaurant.com/ Kokeb Ethiopian Restaurant] (Ethiopian) ''Let's say meet at the lobby at 6pm like everyone else. Woohoo!''&lt;br /&gt;
&lt;br /&gt;
* Andreas Orphanides (leader) - v&lt;br /&gt;
* Mark Mounts - v&lt;br /&gt;
* Joe Montibello - n&lt;br /&gt;
* Andrew Darby - v&lt;br /&gt;
&lt;br /&gt;
[http://tomdouglas.com/index.php?page=dahlia-lounge Dahlia Lounge] (Pacific Northwest cuisine, $$$)&lt;br /&gt;
&lt;br /&gt;
[http://www.mattsinthemarket.com/ Matt's in the Market] (Northwest Cuisine, $$$)&lt;br /&gt;
&lt;br /&gt;
[http://www.placepigalle-seattle.com/ Place Pigalle] (French)&lt;br /&gt;
&lt;br /&gt;
[http://www.chezshea.com/ Chez Shea] (French)&lt;br /&gt;
&lt;br /&gt;
[http://www.elysianbrewing.com/elysian.html Elysian Breweries and Pubs] (Pub Food)&lt;br /&gt;
&lt;br /&gt;
[http://www.mezaseattle.com/index.html Meza] (Latin Fare)&lt;br /&gt;
* Tara Robertson - n&lt;br /&gt;
&lt;br /&gt;
[http://lovinghut.us/seattle/index.html Loving Hut] (Vietnamese/Veg*n)&lt;br /&gt;
&lt;br /&gt;
[http://inthebowlbistro.com/index.php In the Bowl] (Veg*n, Asian)&lt;br /&gt;
&lt;br /&gt;
[http://www.plumbistro.com/ Plumb Bistro] (Veg*n)&lt;br /&gt;
&lt;br /&gt;
[http://highlineseattle.com/ Highline] (Veg*n, bar)&lt;br /&gt;
  &lt;br /&gt;
'''Restaurants more than 1 miles from the hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://bravehorsetavern.com/ Brave Horse Tavern] (another Tom Douglas, good regional beer list, yummy food. Near South Lake Union. Would require a ride on the South Lake Union Trolley (SLUT), but it's easy to get to/use from downtown. &lt;br /&gt;
&lt;br /&gt;
[http://flyingfishrestaurant.com/ Flying Fish] (Seafood)&lt;br /&gt;
&lt;br /&gt;
[http://www.allmenus.com/wa/seattle/3437-cafe-flora/menu/dinner/ Cafe Flora] (FANTASTIC Veg*n restaurant. Use Metro bus #11 to get there)&lt;br /&gt;
&lt;br /&gt;
[http://www.teapotvegetarianhouse.com/index.htm Teapot Vegetarian House] (Veg*n, Asian)&lt;br /&gt;
&lt;br /&gt;
[http://spaceneedle.com/restaurant/ Space Needle] (American, Pricy; but what the heck, listed it anyway for those who want the experience)&lt;br /&gt;
&lt;br /&gt;
===Veg*n Dinner Wednesday===&lt;br /&gt;
&lt;br /&gt;
We'll pick a place with lots of veg*n options to go eat Wednesday for dinner. Vegetarians and non-vegetarians welcome.&lt;br /&gt;
&lt;br /&gt;
(I probably won't make it but DO YOURSELVES A FAVOR AND '''GO TO CAFÉ FLORA''', SRSLY. -mjgiarlo)&lt;br /&gt;
&lt;br /&gt;
*Jason Ronallo&lt;br /&gt;
*Sean Hannan&lt;br /&gt;
*Ed Summers&lt;br /&gt;
*Becky Yoose (carnivore ambassador)&lt;br /&gt;
*Bohyun Kim&lt;br /&gt;
*Bethany Nowviskie&lt;br /&gt;
*Margaret Heller&lt;br /&gt;
*Laura Smart&lt;br /&gt;
*Sibyl Schaefer&lt;br /&gt;
*WOAH! Didn't expect such a big response! Let's cap this one until we decide on a place that can accomodate us.&lt;br /&gt;
&lt;br /&gt;
===Dim Sum Lunch Thursday===&lt;br /&gt;
&lt;br /&gt;
For those of you staying in town after the last session on Thursday, [http://oasiankitchen.com/ O'Asian Kitchen] has dim sum service during the weekdays. Meet up around 12:35, meeting location tba. Bring cash for easier bill splitting.&lt;br /&gt;
&lt;br /&gt;
*Becky Yoose&lt;br /&gt;
* Declan Fleming - love me some Dim Sum!&lt;br /&gt;
* Adam Wead&lt;br /&gt;
* Heather Pitts&lt;br /&gt;
* Sibyl Schaefer&lt;br /&gt;
* Anoop Atre&lt;br /&gt;
* Dan Suchy&lt;br /&gt;
* Carmen Mitchell&lt;br /&gt;
* Tara Robertson&lt;br /&gt;
* Ray Schwartz&lt;br /&gt;
&lt;br /&gt;
==Social Map - places of interest==&lt;br /&gt;
[http://g.co/maps/4m5pk Code4lib 2012 - Seattle - social events, hangouts, and places to see]&lt;br /&gt;
&lt;br /&gt;
==Seattle Events Feb 5-9==&lt;br /&gt;
===Saturday, February 4, 2012===&lt;br /&gt;
In case you are showing up really early.&lt;br /&gt;
* Belgianfest: http://www.washingtonbeer.com/belgianfest/&lt;br /&gt;
===Sunday, February 5, 2012===&lt;br /&gt;
* Clinton Fearon &amp;amp; The Boogie Brown Band/Live Wyya/Adrian Xavier/Selecta Raiford/DJ Courtland, Neumos: http://neumos.com/neumos.php&lt;br /&gt;
* Michael The Blind/The Els, Skylark: http://www.skylarkcafe.com/&lt;br /&gt;
* Addaura/Alda/Hallow, Comet&lt;br /&gt;
* &amp;quot;I Am My Own Wife&amp;quot; 7:30pm at Seattle Repertory Theatre (Seattle Center) http://www.seattlerep.org/Plays/1112/IM/&lt;br /&gt;
&lt;br /&gt;
===Monday, February 6, 2012===&lt;br /&gt;
* Silent Movie Mondays:  Last Command 1928, http://stgpresents.org/artists/?artist=1829#, Show at 7:00pm, The Paramount Theatre $10&lt;br /&gt;
This all-classic film series, First Oscars, is accompanied by live music from the historic Mighty Wurlitzer organ, one of the last three remaining organs of its kind to reside in its original environment, played by critically acclaimed organist Jim Riggs.&lt;br /&gt;
&lt;br /&gt;
===Tuesday, February 7, 2012===&lt;br /&gt;
* Lionize/Maylene &amp;amp; The Sons Of Disaster, El Corazon: http://elcorazonseattle.com/&lt;br /&gt;
* The Pulltab Playboys/Rachel Lyn Harrington &amp;amp; The Knock Outs/The James Low Western Front, Sunset: http://sunsettavern.com/&lt;br /&gt;
* Twin Sister, Vera: http://theveraproject.org/shows/&lt;br /&gt;
* The Features, Chop Suey: http://www.chopsuey.com/&lt;br /&gt;
* Wilco/White Denim, Paramount Theatre: http://stgpresents.org/&lt;br /&gt;
* &amp;quot;I Am My Own Wife&amp;quot; 7:30pm at Seattle Repertory Theatre (Seattle Center) http://www.seattlerep.org/Plays/1112/IM/&lt;br /&gt;
* Intro to Arduino Workshop, 7pm at Metrix Create Space http://metrixcreatespace.com/&lt;br /&gt;
&lt;br /&gt;
===Wednesday, February 8, 2012===&lt;br /&gt;
* The Golden Blondes/The Jet Age/Mr. Drinx &amp;amp; The Pot Heads, Sunset: http://sunsettavern.com/&lt;br /&gt;
* Pipsisewah/The Chasers/The Magic Mirrors, Tractor: http://www.tractortavern.com/ &lt;br /&gt;
* Dengue Fever vs Secret Chiefs 3, Moe Bar :http://bit.ly/yJtfXv  (how could you pass the opportunity to see someone play this thing :http://bit.ly/wB5AgZ&lt;br /&gt;
&lt;br /&gt;
===Thursday, February 9, 2012===&lt;br /&gt;
* SAM Opening - Gauguin and Polynesia: An Elusive Paradise: http://www.seattleartmuseum.org/gauguin&lt;br /&gt;
* The Jayhawks, Neptune Theater: http://stgpresents.org/&lt;br /&gt;
* Digital Leather, Comet &lt;br /&gt;
* Savani World Quintet/Super Sones, Columbia City Theater: http://www.columbiacitytheater.com/&lt;br /&gt;
* Blvd Park {album release}/Nettle Honey/Creeping Time, Tractor: http://www.tractortavern.com/&lt;br /&gt;
* Eleanor Friedberger, Crocodile: http://thecrocodile.com/index.html&lt;br /&gt;
&lt;br /&gt;
===Ongoing Events===&lt;br /&gt;
* Seattle Art Museum: Tours are every Saturday &amp;amp; Sunday at noon, and the First Thursday of every month at 10:30, 11:30 am, 12:30 &amp;amp; 1:30 pm.&lt;br /&gt;
* EMP:  Exhibits on display include: Battlestar Galactica, Nirvana, Avatar, and Can’t Look Away: The Lure of Horror Film&lt;br /&gt;
* Teatro ZinZanni: ¡Caliente! http://dreams.zinzanni.org/&lt;br /&gt;
* Pacific NW Ballet: performing Don Quixote at McCaw Hall http://www.pnb.org/&lt;br /&gt;
* Oklahoma!, Sunday matinee and nightly: 5th Avenue Theatre, 1308 Fifth Avenue http://www.5thavenue.org/show/oklahoma&lt;br /&gt;
&lt;br /&gt;
==Local events/places==&lt;br /&gt;
* Metrix Create Space&lt;br /&gt;
* Ada's Technical Books&lt;br /&gt;
* Northwest Outdoor Center&lt;br /&gt;
* Center for Wooden Boats&lt;br /&gt;
* Empty Sea Studios acoustic music&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Local Beer Places==&lt;br /&gt;
* Map of [http://beermapping.com/maps/citymaps.php?m=seattle#lat=47.66723703450515&amp;amp;lng=-122.28263854980469&amp;amp;z=5 beer venues] maintained at Beermapping.com.&lt;br /&gt;
* List of [http://www.washingtonbeer.com/breweries/seattle-king-co/ local breweries] ([http://maps.google.com/maps/ms?hl=en&amp;amp;ie=UTF8&amp;amp;msa=0&amp;amp;msid=201783184139227541123.0004813e64758434cb054&amp;amp;source=embed&amp;amp;ll=47.558921,-122.106171&amp;amp;spn=0.442982,1.234589&amp;amp;z=10&amp;amp;source=embed map]) maintained by the Washington Beer Commission&lt;br /&gt;
* Map of [http://www.ratebeer.com/Places/RegionMap.asp?rid=7600 beer venues] maintained by Ratebeer.com.&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
[http://orbiscascade.org/index/c4l-things-to-do-in-seattle Things to do in Seattle, from the hosts]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_c4l2012_social_activities&amp;diff=10631</id>
		<title>2012 c4l2012 social activities</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_c4l2012_social_activities&amp;diff=10631"/>
				<updated>2012-01-31T22:45:40Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* Tuesday, February 7, 2012 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Ideas==&lt;br /&gt;
* Woodinville distillery tour&lt;br /&gt;
* Seattle distillery tour&lt;br /&gt;
* Favorite local breweries&lt;br /&gt;
* Favorite local tea houses&lt;br /&gt;
* Favorite local used bookstores&lt;br /&gt;
* Visit hackerspace&lt;br /&gt;
** +1&lt;br /&gt;
* Evergreen/Koha - Open Source ILS brewery/tea house meetup&lt;br /&gt;
&lt;br /&gt;
==Planned events==&lt;br /&gt;
&lt;br /&gt;
===[[2012 Craft Brew Drinkup|Craft Brew Drinkup]]===&lt;br /&gt;
&lt;br /&gt;
'''Date/Time TBA; to be held in the Hospitality Suite.'''&lt;br /&gt;
&lt;br /&gt;
Like good beer? Bring some in your luggage! Some of us are planning to bring some of our favorite local, special, or homebrewed beers to share. Interested? Sign up on the [[2012 Craft Brew Drinkup]] page!&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Get Lamp&amp;quot; showing===&lt;br /&gt;
&lt;br /&gt;
Some attendees are organizing a showing of [http://www.getlamp.com/ Get Lamp: The Text Adventure Documentary] in the hospitality suite.&lt;br /&gt;
&lt;br /&gt;
To indicate your preference of time and date for the showing, please fill out [http://www.doodle.com/p4c32i3b2ybsrkbh this Doodle poll].&lt;br /&gt;
&lt;br /&gt;
===Newcomer dinner Tuesday===&lt;br /&gt;
First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating &amp;lt;strike&amp;gt;discussions about&amp;lt;/strike&amp;gt; demonstrations of the many uses of &amp;lt;strike&amp;gt;bacon&amp;lt;/strike&amp;gt; &amp;lt;strike&amp;gt;dongles&amp;lt;/strike&amp;gt; XML.&lt;br /&gt;
&lt;br /&gt;
Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!&lt;br /&gt;
&lt;br /&gt;
'''Plans'''&lt;br /&gt;
* When: Tuesday evening (2/7) '''Note that this year's dinner is on Tuesday'''&lt;br /&gt;
* Time: 6 PM (ish) or whenever you can get your group together&lt;br /&gt;
* Mastermind (if you have any questions): [mailto:yoosebec@grinnell.edu Becky Yoose]&lt;br /&gt;
&lt;br /&gt;
''Guidelines:''&lt;br /&gt;
*Max of '''6''' per group&lt;br /&gt;
**Please, no waitlisting :(&lt;br /&gt;
*ID yourselves so we can get a good mix of new people and veterans in each group&lt;br /&gt;
**New folks - n&lt;br /&gt;
**c4l vets - v&lt;br /&gt;
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group :)''')&lt;br /&gt;
**Leader duties&lt;br /&gt;
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library coders &lt;br /&gt;
***Herd folks from hotel to restaurant (know where you're going!)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Happenings'''&lt;br /&gt;
&lt;br /&gt;
Crashing the [http://www.seattlerb.org/ Seattle Ruby] meetup, which meets on Capital Hill at 7:00 on Tuesdays. Eat at [http://www.yelp.com/biz/poppy-seattle Poppy] before.  Leaving from the hotel lobby at 6:00.  &lt;br /&gt;
* Matt Zumwalt (leader) - v&lt;br /&gt;
''If you dig Ruby, come to this.  Seattle ruby produced Nokogiri, Vlad, Rubygems.org ....''&lt;br /&gt;
&lt;br /&gt;
'''Restaurants'''&lt;br /&gt;
&lt;br /&gt;
'''Restaurants within .25 miles of the hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://www.sazeracrestaurant.com/index.php Sazerac] (AWESOME happy hour menu that runs until 8)&lt;br /&gt;
* Martin Haye - n&lt;br /&gt;
* William Gunn - n&lt;br /&gt;
* Rebecca Jones - n&lt;br /&gt;
* Chick Markley - v&lt;br /&gt;
* Al Cornish - v&lt;br /&gt;
* Keri Thompson - n&lt;br /&gt;
*'''capped at 6''' ''(So, who's the fearless leader of this group? ~yo_bj)''&lt;br /&gt;
&lt;br /&gt;
[http://oasiankitchen.com/ O'Asian Kitchen and Lounge]  (Asian) &lt;br /&gt;
&lt;br /&gt;
'''Restaurants between .25 miles and .5 miles of the hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://www.pikebrewing.com/index_html.shtml Pike Brewing] (local brewery, pub food)&lt;br /&gt;
* Ken Varnum - n&lt;br /&gt;
* Chad Nelson - n&lt;br /&gt;
* Ed Summers - v&lt;br /&gt;
* Tommy Ingulfsen - n&lt;br /&gt;
* Adam Wead - v or .5n&lt;br /&gt;
* Aaron Collier - n&lt;br /&gt;
*'''capped at 6''' ''(So, who's the fearless leader of this group? ~yo_bj)''&lt;br /&gt;
&lt;br /&gt;
[http://www.rockbottom.com/ The Rock Bottom Restaurant &amp;amp; Brewery] (American)&lt;br /&gt;
&lt;br /&gt;
[http://www.wildginger.net/ Wild Ginger] (Asian, a bit overpriced)&lt;br /&gt;
&lt;br /&gt;
[http://www.thepurplecafe.com/index.html Purple Cafe] (American, Wine Bar)&lt;br /&gt;
* Calvin Mah - (leader) - v&lt;br /&gt;
* David Isaak - n&lt;br /&gt;
&lt;br /&gt;
[http://www.cafepaloma.com/ Cafe Paloma] (Mediterranean)&lt;br /&gt;
* Jean Rainwater (leader) - v&lt;br /&gt;
* Kelley McGrath - n&lt;br /&gt;
* Lori Robare - n&lt;br /&gt;
&lt;br /&gt;
[http://www.thecollinspub.com/ Collins Pub] (Pub Food, great beer selection)&lt;br /&gt;
* Francis Kayiwa - (leader) &amp;quot;(get hold of me at first dot last name at goog as the date gets closer with your mobile)&amp;quot; v&lt;br /&gt;
* Michael Lindsey - v&lt;br /&gt;
* Dan Suchy - v&lt;br /&gt;
* David Drexler - n&lt;br /&gt;
* Laura Smart - n&lt;br /&gt;
* Heather Pitts - n&lt;br /&gt;
*'''capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.mcmenamins.com/311-six-arms-home Six Arms - McMenamins] (Pub Food &amp;amp; they brew their own beer) ''Meeting place TBA. Leave email and I'll coordinate late next week. --Joel''&lt;br /&gt;
* Joel Richard (richardjm AT si.edu) (leader) - v&lt;br /&gt;
* Margaret Heller - v&lt;br /&gt;
* Sibyl Schaefer (sschaefer AT rockarch . org) - v&lt;br /&gt;
* Tim Lepczyk (timlepczyk AT gmail.com) - n&lt;br /&gt;
* Ray Schwartz (schwartzr2@wpunj.edu) - v&lt;br /&gt;
* Andrea Schurr (andrea-schurr AT utc DOT edu) - v(2nd-timer)&lt;br /&gt;
* '''capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.611supreme.com/ 611 Supreme] (Crepes and Full Bar) ''Meet in the conference hotel lobby at 6pm. Look for the short woman in a trench coat and wide brim hat ~Becky''&lt;br /&gt;
&lt;br /&gt;
*Becky Yoose (leader) - v &lt;br /&gt;
*Cynthia Ng - n&lt;br /&gt;
*Zoe Chao - v&lt;br /&gt;
*Justin Coyne - n&lt;br /&gt;
*Stephanie Collett - n&lt;br /&gt;
*Bethany Nowviskie - n&lt;br /&gt;
*'''capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.panafricamarket.com/wp/ Pan Africa Restaurant &amp;amp; Bar] (Pan African) CLOSED MONDAYS ''Veg and non-veg options available. Located in the Pike Place Market, so we can explore a bit too, though the fish flinging will be over by then. Meet in the conference hotel lobby at 6PM.''&lt;br /&gt;
&lt;br /&gt;
*Jason Ronallo (leader; happy to lead to any other veg-friendly place as an alternative) - v&lt;br /&gt;
*Nettie Lagace - n&lt;br /&gt;
*Bohyun Kim - n/v (2nd-timer)&lt;br /&gt;
*Wendy Robertson - n&lt;br /&gt;
*Jennifer Bowen - n/v (3rd timer)&lt;br /&gt;
&lt;br /&gt;
'''Restaurants between .5 and 1 mile from hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://tomdouglas.com/index.php?page=palace-kitchen-dinner Palace Kitchen] (another Tom Douglas restaurant, w/ a focus on meat).  ''I have made a reservation for 6 at 8pm. Let's meet in the conference lobby at 6:30pm and make our way slowly over; we will find things to do in the interim. Look for Mike Giarlo, a man who may be holding a sign that says &amp;quot;HI I'M MIKE GIARLO&amp;quot; or otherwise shouting his name or looking confused.''&lt;br /&gt;
&lt;br /&gt;
* Mike Giarlo (leader) - v&lt;br /&gt;
* Carmen Mitchell - n&lt;br /&gt;
* Daniel Lovins - v&lt;br /&gt;
* Cary Gordon - v &lt;br /&gt;
* Declan Fleming - v&lt;br /&gt;
* Amy Unger - n&lt;br /&gt;
* (CAPPED AT SIX!)&lt;br /&gt;
&lt;br /&gt;
[http://sitkaandspruce.com/ Sitka and Spruce] (Eclectic, super-local and super-seasonal.) ''We have a reservation for 6 at 8:15pm. We'll meet in the conference lobby at 6:30 pm and head over - the owners also run [http://www.ferdinandthebar.com/home/ Bar Ferd'nand], a wine shop/bar in the same building, and we can kill time there before we eat. Look for Mark Matienzo or Hillel Arnold.''&lt;br /&gt;
&lt;br /&gt;
* Mark Matienzo (leader) - v&lt;br /&gt;
* Hillel Arnold - sophomore&lt;br /&gt;
* Devon Smith - v&lt;br /&gt;
* bernardo gomez - n&lt;br /&gt;
* Derek Merleaux - sophmore&lt;br /&gt;
* Jennifer Weintraub - n&lt;br /&gt;
* (CAPPED AT SIX!)&lt;br /&gt;
&lt;br /&gt;
[http://www.yelp.com/biz/japonessa-seattle Japonessa Restaurant] (Japanese + full bar)&lt;br /&gt;
&lt;br /&gt;
[http://tomdouglas.com/index.php?page=serious-pie Serious Pie] (Tom Douglas restaurant, inventive pizzas, good local beer list). &lt;br /&gt;
&lt;br /&gt;
[http://www.allmenus.com/wa/seattle/204592-ballet-restaurant/menu/ Ballet] (Vietnamese)&lt;br /&gt;
&lt;br /&gt;
[http://www.kokebrestaurant.com/ Kokeb Ethiopian Restaurant] (Ethiopian) ''Let's say meet at the lobby at 6pm like everyone else. Woohoo!''&lt;br /&gt;
&lt;br /&gt;
* Andreas Orphanides (leader) - v&lt;br /&gt;
* Mark Mounts - v&lt;br /&gt;
* Joe Montibello - n&lt;br /&gt;
* Andrew Darby - v&lt;br /&gt;
&lt;br /&gt;
[http://tomdouglas.com/index.php?page=dahlia-lounge Dahlia Lounge] (Pacific Northwest cuisine, $$$)&lt;br /&gt;
&lt;br /&gt;
[http://www.mattsinthemarket.com/ Matt's in the Market] (Northwest Cuisine, $$$)&lt;br /&gt;
&lt;br /&gt;
[http://www.placepigalle-seattle.com/ Place Pigalle] (French)&lt;br /&gt;
&lt;br /&gt;
[http://www.chezshea.com/ Chez Shea] (French)&lt;br /&gt;
&lt;br /&gt;
[http://www.elysianbrewing.com/elysian.html Elysian Breweries and Pubs] (Pub Food)&lt;br /&gt;
&lt;br /&gt;
[http://www.mezaseattle.com/index.html Meza] (Latin Fare)&lt;br /&gt;
* Tara Robertson - n&lt;br /&gt;
&lt;br /&gt;
[http://lovinghut.us/seattle/index.html Loving Hut] (Vietnamese/Veg*n)&lt;br /&gt;
&lt;br /&gt;
[http://inthebowlbistro.com/index.php In the Bowl] (Veg*n, Asian)&lt;br /&gt;
&lt;br /&gt;
[http://www.plumbistro.com/ Plumb Bistro] (Veg*n)&lt;br /&gt;
&lt;br /&gt;
[http://highlineseattle.com/ Highline] (Veg*n, bar)&lt;br /&gt;
  &lt;br /&gt;
'''Restaurants more than 1 miles from the hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://bravehorsetavern.com/ Brave Horse Tavern] (another Tom Douglas, good regional beer list, yummy food. Near South Lake Union. Would require a ride on the South Lake Union Trolley (SLUT), but it's easy to get to/use from downtown. &lt;br /&gt;
&lt;br /&gt;
[http://flyingfishrestaurant.com/ Flying Fish] (Seafood)&lt;br /&gt;
&lt;br /&gt;
[http://www.allmenus.com/wa/seattle/3437-cafe-flora/menu/dinner/ Cafe Flora] (FANTASTIC Veg*n restaurant. Use Metro bus #11 to get there)&lt;br /&gt;
&lt;br /&gt;
[http://www.teapotvegetarianhouse.com/index.htm Teapot Vegetarian House] (Veg*n, Asian)&lt;br /&gt;
&lt;br /&gt;
[http://spaceneedle.com/restaurant/ Space Needle] (American, Pricy; but what the heck, listed it anyway for those who want the experience)&lt;br /&gt;
&lt;br /&gt;
===Veg*n Dinner Wednesday===&lt;br /&gt;
&lt;br /&gt;
We'll pick a place with lots of veg*n options to go eat Wednesday for dinner. Vegetarians and non-vegetarians welcome.&lt;br /&gt;
&lt;br /&gt;
(I probably won't make it but DO YOURSELVES A FAVOR AND '''GO TO CAFÉ FLORA''', SRSLY. -mjgiarlo)&lt;br /&gt;
&lt;br /&gt;
*Jason Ronallo&lt;br /&gt;
*Sean Hannan&lt;br /&gt;
*Ed Summers&lt;br /&gt;
*Becky Yoose (carnivore ambassador)&lt;br /&gt;
*Bohyun Kim&lt;br /&gt;
*Bethany Nowviskie&lt;br /&gt;
*Margaret Heller&lt;br /&gt;
*Laura Smart&lt;br /&gt;
*Sibyl Schaefer&lt;br /&gt;
*WOAH! Didn't expect such a big response! Let's cap this one until we decide on a place that can accomodate us.&lt;br /&gt;
&lt;br /&gt;
===Dim Sum Lunch Thursday===&lt;br /&gt;
&lt;br /&gt;
For those of you staying in town after the last session on Thursday, [http://oasiankitchen.com/ O'Asian Kitchen] has dim sum service during the weekdays. Meet up around 12:35, meeting location tba. Bring cash for easier bill splitting.&lt;br /&gt;
&lt;br /&gt;
*Becky Yoose&lt;br /&gt;
* Declan Fleming - love me some Dim Sum!&lt;br /&gt;
* Adam Wead&lt;br /&gt;
* Heather Pitts&lt;br /&gt;
* Sibyl Schaefer&lt;br /&gt;
* Anoop Atre&lt;br /&gt;
* Dan Suchy&lt;br /&gt;
* Carmen Mitchell&lt;br /&gt;
* Tara Robertson&lt;br /&gt;
* Ray Schwartz&lt;br /&gt;
&lt;br /&gt;
==Social Map - places of interest==&lt;br /&gt;
[http://g.co/maps/4m5pk Code4lib 2012 - Seattle - social events, hangouts, and places to see]&lt;br /&gt;
&lt;br /&gt;
==Seattle Events Feb 5-9==&lt;br /&gt;
===Sunday, February 5, 2012===&lt;br /&gt;
* Clinton Fearon &amp;amp; The Boogie Brown Band/Live Wyya/Adrian Xavier/Selecta Raiford/DJ Courtland, Neumos: http://neumos.com/neumos.php&lt;br /&gt;
* Michael The Blind/The Els, Skylark: http://www.skylarkcafe.com/&lt;br /&gt;
* Addaura/Alda/Hallow, Comet&lt;br /&gt;
* &amp;quot;I Am My Own Wife&amp;quot; 7:30pm at Seattle Repertory Theatre (Seattle Center) http://www.seattlerep.org/Plays/1112/IM/&lt;br /&gt;
&lt;br /&gt;
===Monday, February 6, 2012===&lt;br /&gt;
* Silent Movie Mondays:  Last Command 1928, http://stgpresents.org/artists/?artist=1829#, Show at 7:00pm, The Paramount Theatre $10&lt;br /&gt;
This all-classic film series, First Oscars, is accompanied by live music from the historic Mighty Wurlitzer organ, one of the last three remaining organs of its kind to reside in its original environment, played by critically acclaimed organist Jim Riggs.&lt;br /&gt;
&lt;br /&gt;
===Tuesday, February 7, 2012===&lt;br /&gt;
* Lionize/Maylene &amp;amp; The Sons Of Disaster, El Corazon: http://elcorazonseattle.com/&lt;br /&gt;
* The Pulltab Playboys/Rachel Lyn Harrington &amp;amp; The Knock Outs/The James Low Western Front, Sunset: http://sunsettavern.com/&lt;br /&gt;
* Twin Sister, Vera: http://theveraproject.org/shows/&lt;br /&gt;
* The Features, Chop Suey: http://www.chopsuey.com/&lt;br /&gt;
* Wilco/White Denim, Paramount Theatre: http://stgpresents.org/&lt;br /&gt;
* &amp;quot;I Am My Own Wife&amp;quot; 7:30pm at Seattle Repertory Theatre (Seattle Center) http://www.seattlerep.org/Plays/1112/IM/&lt;br /&gt;
* Intro to Arduino Workshop, 7pm at Metrix Create Space http://metrixcreatespace.com/&lt;br /&gt;
&lt;br /&gt;
===Wednesday, February 8, 2012===&lt;br /&gt;
* The Golden Blondes/The Jet Age/Mr. Drinx &amp;amp; The Pot Heads, Sunset: http://sunsettavern.com/&lt;br /&gt;
* Pipsisewah/The Chasers/The Magic Mirrors, Tractor: http://www.tractortavern.com/ &lt;br /&gt;
* Dengue Fever vs Secret Chiefs 3, Moe Bar :http://bit.ly/yJtfXv  (how could you pass the opportunity to see someone play this thing :http://bit.ly/wB5AgZ&lt;br /&gt;
&lt;br /&gt;
===Thursday, February 9, 2012===&lt;br /&gt;
* SAM Opening - Gauguin and Polynesia: An Elusive Paradise: http://www.seattleartmuseum.org/gauguin&lt;br /&gt;
* The Jayhawks, Neptune Theater: http://stgpresents.org/&lt;br /&gt;
* Digital Leather, Comet &lt;br /&gt;
* Savani World Quintet/Super Sones, Columbia City Theater: http://www.columbiacitytheater.com/&lt;br /&gt;
* Blvd Park {album release}/Nettle Honey/Creeping Time, Tractor: http://www.tractortavern.com/&lt;br /&gt;
* Eleanor Friedberger, Crocodile: http://thecrocodile.com/index.html&lt;br /&gt;
&lt;br /&gt;
===Ongoing Events===&lt;br /&gt;
* Seattle Art Museum: Tours are every Saturday &amp;amp; Sunday at noon, and the First Thursday of every month at 10:30, 11:30 am, 12:30 &amp;amp; 1:30 pm.&lt;br /&gt;
* EMP:  Exhibits on display include: Battlestar Galactica, Nirvana, Avatar, and Can’t Look Away: The Lure of Horror Film&lt;br /&gt;
* Teatro ZinZanni: ¡Caliente! http://dreams.zinzanni.org/&lt;br /&gt;
* Pacific NW Ballet: performing Don Quixote at McCaw Hall http://www.pnb.org/&lt;br /&gt;
* Oklahoma!, Sunday matinee and nightly: 5th Avenue Theatre, 1308 Fifth Avenue http://www.5thavenue.org/show/oklahoma&lt;br /&gt;
&lt;br /&gt;
==Local events/places==&lt;br /&gt;
* Metrix Create Space&lt;br /&gt;
* Ada's Technical Books&lt;br /&gt;
* Northwest Outdoor Center&lt;br /&gt;
* Center for Wooden Boats&lt;br /&gt;
* Empty Sea Studios acoustic music&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Local Beer Places==&lt;br /&gt;
* Map of [http://beermapping.com/maps/citymaps.php?m=seattle#lat=47.66723703450515&amp;amp;lng=-122.28263854980469&amp;amp;z=5 beer venues] maintained at Beermapping.com.&lt;br /&gt;
* List of [http://www.washingtonbeer.com/breweries/seattle-king-co/ local breweries] ([http://maps.google.com/maps/ms?hl=en&amp;amp;ie=UTF8&amp;amp;msa=0&amp;amp;msid=201783184139227541123.0004813e64758434cb054&amp;amp;source=embed&amp;amp;ll=47.558921,-122.106171&amp;amp;spn=0.442982,1.234589&amp;amp;z=10&amp;amp;source=embed map]) maintained by the Washington Beer Commission&lt;br /&gt;
* Map of [http://www.ratebeer.com/Places/RegionMap.asp?rid=7600 beer venues] maintained by Ratebeer.com.&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
[http://orbiscascade.org/index/c4l-things-to-do-in-seattle Things to do in Seattle, from the hosts]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_Craft_Brew_Drinkup&amp;diff=10629</id>
		<title>2012 Craft Brew Drinkup</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_Craft_Brew_Drinkup&amp;diff=10629"/>
				<updated>2012-01-31T22:13:14Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* Sign up */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Date/Time TBA; to be held in hospitality suite'''&lt;br /&gt;
&lt;br /&gt;
The Craft Brew Drinkup at Code4lib 2012 is all about sharing and enjoying good beer with fellow conference attendees. The idea is to bring bottles of your favorite beers.&lt;br /&gt;
&lt;br /&gt;
While you're not obligated to bring ''local beers'' from whereever you're from, participants are definitely encouraged to bring beer that you think is special and might be somewhat hard for others outside your area to find. Homebrew is especially welcome. Sign up below with your name, where you're from, and list a few brews or bottles you're thinking about (but not necessarily committing to) bringing along. You can also request that people bring specific beer if you so desire, but don't necessarily expect that your wishes will be granted.&lt;br /&gt;
&lt;br /&gt;
''If you do not check bags or otherwise cannot arrange to bring beer from where you call home, you may be interested in buying beer from a local beer store. See the &amp;quot;Buying Beer in Seattle&amp;quot; section below for suggestions.''&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=== Sign up ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; class=&amp;quot;sortable&amp;quot; &lt;br /&gt;
! Name&lt;br /&gt;
! Location&lt;br /&gt;
! Brews or Breweries I might bring&lt;br /&gt;
! Requests&lt;br /&gt;
|-&lt;br /&gt;
| anarchivist&lt;br /&gt;
| New Haven CT/Brooklyn NY&lt;br /&gt;
| 3 Floyds Dark Lord 2011; maybe Westvleteren Blonde; Berkshire Brewing company&lt;br /&gt;
| Imperial porters/stouts; really funky-/Brett-tasting beers or wild ales; highly-hopped stuff; interesting session beers&lt;br /&gt;
|-&lt;br /&gt;
| kayiwa&lt;br /&gt;
| Chicago IL&lt;br /&gt;
| Bourbon County Stout; New Glarus Barleywine&lt;br /&gt;
| Barleywines; Aged Stouts; Anything from Deschutes&lt;br /&gt;
(psst, Francis: I've got some homebrewed barleywine aging in the basement; i won't be in Seattle but I'll bring some to C4L-Midwest -[[User:Kenirwin|Kenirwin]] 13:26, 29 January 2012 (PST))&lt;br /&gt;
|-&lt;br /&gt;
| danwho&lt;br /&gt;
| San Diego, CA&lt;br /&gt;
| Alpine Brewery Exponential Hoppiness; Iron Fist; maybe Lost Abbey; Bud Light&lt;br /&gt;
| hoppy imperials, sours, funky farmhouses.  Also, I'd vote Wednesday or Tuesday evening since a lot of folks are doing the Microsoft tour and/or newcomer dinners Monday&lt;br /&gt;
|-&lt;br /&gt;
| declan&lt;br /&gt;
| San Diego, CA&lt;br /&gt;
| hmm, looking over the cellar... Parabola, Black Tuesday, Cherry Adam, Angel Share, Captain stout, Silva.... we'll see!&lt;br /&gt;
| dark, black stuff.  like my heart.  Or sours.  Or Belgies.  Founders, Bells, New Glaris, Goose Island.&lt;br /&gt;
|-&lt;br /&gt;
| awead&lt;br /&gt;
| Cleveland, OH&lt;br /&gt;
| Founders Porter, some new IPA I found...&lt;br /&gt;
| Stuff that doesn't suck.&lt;br /&gt;
|-&lt;br /&gt;
|bibliotechy&lt;br /&gt;
|Atlanta, Ga&lt;br /&gt;
|Some Terrapin beers... Hopsecutioner,  Sweetwater Brewery Exodus Porter if it is still around&lt;br /&gt;
|Boreale noire, rousse or cuivre from Montreal! &lt;br /&gt;
|-&lt;br /&gt;
|sdellis&lt;br /&gt;
|Lambertville, NJ&lt;br /&gt;
|Riverhorse... (possibly Hop Hazard, but I'll see what's fresh).  Maybe Lionshead (pilsner) from Doylestown, PA (legend has it you can drink as much as you want and never get a hangover).&lt;br /&gt;
|Bitters, pub style, IPAs, brown ales&lt;br /&gt;
|-&lt;br /&gt;
|jastirn&lt;br /&gt;
|Kansas City, KS&lt;br /&gt;
|Whatever I can get from Wilderness Brewing (KC), Free State (Lawrence, KS), Schlafly Imperial Stout (St. Louis), and Blvd Smokestack (KC) (for Danwho)&lt;br /&gt;
| More blueberry stout, stouts, lagers, spicy&lt;br /&gt;
|-&lt;br /&gt;
|HLPitts&lt;br /&gt;
|Salem, OR&lt;br /&gt;
|tbd, but probably something from Gilgamesh, and if we're lucky The Abyss from Deschutes.  Ooh, and I already have a barleywine from Hopworks that I will bring.&lt;br /&gt;
|stouts/porters, sours, red ales&lt;br /&gt;
|-&lt;br /&gt;
|bohyunkim&lt;br /&gt;
|Miami, FL&lt;br /&gt;
|same as last year - canned bears from Oskar Blues brewery in Colorado unless I spot something better&lt;br /&gt;
|cider, Rogue Dead Guy, malty, fruity, blonde/gloden ale &lt;br /&gt;
|-&lt;br /&gt;
|carmendarlene&lt;br /&gt;
|San Diego, CA&lt;br /&gt;
|something from SoCal...Maybe more Alpine. Going shopping at the Best Damn Beer Store later this week.&lt;br /&gt;
|New Glaris, Goose Island, Three Floyds, Cantillon...stuff that I can't get in San Diego. &lt;br /&gt;
|-&lt;br /&gt;
|flyingzumwalt &amp;amp; jcoyne&lt;br /&gt;
|Minneapolis, MN&lt;br /&gt;
|Surly Coffee Bender &amp;amp; Surly Cynic, Bell's Two Hearted, Lift Bridge Farm Girl, Crispin Cider&lt;br /&gt;
|Revivalist beers (ie. [http://www.yardsbrewing.com/ales_poor-richards-tavern-spruce.asp Yard's Revolutionary Beers] ), New Glarus, Yuengling&lt;br /&gt;
|-&lt;br /&gt;
|singlesoliloquy&lt;br /&gt;
|St. Louis, MO&lt;br /&gt;
|Schlafly, Six Row.&lt;br /&gt;
|Good pilsners.&lt;br /&gt;
|-&lt;br /&gt;
|pberry&lt;br /&gt;
|Chico, CA&lt;br /&gt;
|Hope to buy Chico stuff in SEA, Bigfoot was just released.&lt;br /&gt;
|Ales&lt;br /&gt;
|-&lt;br /&gt;
|calvinmah&lt;br /&gt;
|Vancouver, Canada&lt;br /&gt;
|driving to SEA so I'll bring a crate&lt;br /&gt;
|Beer&lt;br /&gt;
|-&lt;br /&gt;
|tara robertson&lt;br /&gt;
|Vancouver, Canada&lt;br /&gt;
|two limited release beers from [http://gib.ca/beer/ Granville Island Brewing]: Fresh Hop ESP, Imperial IPA&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|younga, ward, jeff&lt;br /&gt;
|Seattle, WA&lt;br /&gt;
|Random assortment of growlers: Georgetown Brewery, Big Time, Fremont, Epic Ales.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Suggestions ===&lt;br /&gt;
&lt;br /&gt;
'''Add using the following format: (person who you are making the request of): (your request) - (your name)'''&lt;br /&gt;
&lt;br /&gt;
* Unnamed persons from the Keystone State: Sly Fox, any special Weyerbacher - anarchivist&lt;br /&gt;
* anyone: Boulevard smokestack series - danwho&lt;br /&gt;
* whosoever brought blueberry stout last year, more of that please - jastirn&lt;br /&gt;
&lt;br /&gt;
=== Buying Beer in Seattle ===&lt;br /&gt;
&lt;br /&gt;
from an email to the code4lib list: &lt;br /&gt;
&lt;br /&gt;
: I can think of three good bottleshops (all w/ taps in case you want a growler) that are located on bus lines from downtown:&lt;br /&gt;
:&lt;br /&gt;
: * [http://bottleworksbeerstore.blogspot.com/ Bottleworks]: Probably the shop I frequent the most. Take the 16 to Wallingford.&lt;br /&gt;
: * [http://www.lastdropbeershop.com/ Last Drop]: Take the 71,72, or 73 north from downtown and get off at 80th.&lt;br /&gt;
: * [http://www.seattlebeerauthority.com/ Beer Authority]: probably the quickest trip from downtown on the 522. get off at the 125th St stop in Lake City and walk north a couple of blocks.&lt;br /&gt;
: * Lots of other pub/beer places noted on [http://g.co/maps/4m5pk the map]&lt;br /&gt;
&lt;br /&gt;
=== Disclaimers === &lt;br /&gt;
&lt;br /&gt;
* This is an unofficial event organized by attendees of Code4lib 2012.&lt;br /&gt;
* All guests at the Drinkup must be 21 years of age or over with a [http://www.cherylslastcall.com/pdfs/Acceptable-ID-Forms.pdf valid form of ID].&lt;br /&gt;
* Any participation in the Drinkup is at your own risk.&lt;br /&gt;
* All guests are expected to drink responsibly and behave appropriately.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Packing and Shipping Beer ===&lt;br /&gt;
&lt;br /&gt;
If you're flying to Code4lib, you will have to consider how to bring your beer. Some attendees in past years have packed beer in their checked luggage, and others have purchased a beer shipper that was checked separately as luggage. In any event, '''you will not be able to bring beer in carryon luggage.'''&lt;br /&gt;
&lt;br /&gt;
The following are links to resources that provide info on packing your beer for transit.&lt;br /&gt;
&lt;br /&gt;
* [http://barlowbrewing.com/2010/11/11/how-to-pack-and-ship-beer/ How to pack and ship beer]&lt;br /&gt;
* [http://baltimoresnacker.blogspot.com/2009/06/how-to-pack-beer-and-wine-into-your.html How to pack beer and wine into your luggage]&lt;br /&gt;
* [http://beeradvocate.com/forum/read/3880083 Flying With Beer (Beer Advocate forums)]&lt;br /&gt;
* [http://beeradvocate.com/forum/read/4364472 Shipping beer while on business travel (Beer Advocate forums)]&lt;br /&gt;
* [http://www.mrboxonline.com/bottle-styrofoam-beer-shipper-p-7579.html A sample styrofoam beer shipper/box combo]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=During_the_Conference_Volunteers&amp;diff=10401</id>
		<title>During the Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=During_the_Conference_Volunteers&amp;diff=10401"/>
				<updated>2012-01-25T16:17:05Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* Session Timer Volunteers */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;code4lib 2012 Volunteers&lt;br /&gt;
&lt;br /&gt;
== Hospitality Suite Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee makes arrangements for any hospitality suite amenities (technology, snacks, games, icebreakers...) we may want&lt;br /&gt;
&lt;br /&gt;
* Mike Giarlo -- Penn State [Glad to be a keyholder, room-sitter, and general tidier-upper]&lt;br /&gt;
* Tom Johnson -- Oregon State University&lt;br /&gt;
* Lisa Kurt [lkurt at unr dot edu]-- University of Nevada, Reno&lt;br /&gt;
* Carmen Mitchell -- California State University San Marcos&lt;br /&gt;
* Declan Fleming -- UCSD&lt;br /&gt;
* Becky Yoose -- Grinnell College&lt;br /&gt;
* Devon Smith &lt;br /&gt;
&lt;br /&gt;
== Welcome Wagon Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Becky Yoose(b.yoose at gmail dot com) -- Grinnell College&lt;br /&gt;
* Bohyun Kim(kimb at fiu dot edu) -- Florida International University&lt;br /&gt;
* Jason Clark (jaclark at montana dot edu) Montana State University&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
Responsible for non-IRC social networking presence.&lt;br /&gt;
&lt;br /&gt;
*Rowena McKernan (rmckernan at whatcom dot ctc dot edu) ~ Whatcom Community College&lt;br /&gt;
&lt;br /&gt;
== IRC Evangelists ==&lt;br /&gt;
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.&lt;br /&gt;
&lt;br /&gt;
* Sam Kome (skome) Claremont Colleges&lt;br /&gt;
* Gabriel Farrell (gsf) (gsf747@gmail.com) Drexel University&lt;br /&gt;
* Michael Klein (mbklein) (mbklein@gmail.com) Stanford University&lt;br /&gt;
* Jon Gorman University of Illinois&lt;br /&gt;
&lt;br /&gt;
== IRC Access ==&lt;br /&gt;
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful.&lt;br /&gt;
&lt;br /&gt;
* Michael B. Klein -- emailed Freenode with IP block for conference.&lt;br /&gt;
* Cary Gordon (highermath) (cgordon at chillco.com) -- The Cherry Hill Company&lt;br /&gt;
&lt;br /&gt;
== Video Committee ==&lt;br /&gt;
Video archiving and video streaming possibilities.&lt;br /&gt;
&lt;br /&gt;
* Corey Harper corey dot harper gmail&lt;br /&gt;
* Shaun Ellis shaune@princeton.edu&lt;br /&gt;
* Cary Gordon (cgordon at chillco.com) -- The Cherry Hill Company&lt;br /&gt;
&lt;br /&gt;
==Registration Desk Volunteers==&lt;br /&gt;
We need 1-2 volunteers to hang out at the registration desk for 2-hour shifts.  Also on Monday and Tuesday, an additional volunteer with wireless access knowledge would be helpful on the Registration Desk to answer tech questions.&lt;br /&gt;
&lt;br /&gt;
* Dan Suchy (dansuchy at gmail) -- UC San Diego&lt;br /&gt;
* Doris Munson (dmunson at ewu.edu) -- Eastern Washington University&lt;br /&gt;
* Tod Robbins (todd.d.robbins at gmail) -- University of Washington&lt;br /&gt;
&lt;br /&gt;
===Registration Desk Schedule===&lt;br /&gt;
Monday&lt;br /&gt;
7-9 am&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
* (wireless expert)&lt;br /&gt;
Monday 9-11 am&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
Tuesday&lt;br /&gt;
7-9 am&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
* (wireless expert)&lt;br /&gt;
Tuesday 9-11 am&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
Tuesday AM&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
Tuesday PM&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
Wednesday AM&lt;br /&gt;
* Becky Yoose&lt;br /&gt;
&lt;br /&gt;
Wednesday PM&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
Thursday AM&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
== Microphone Runners==&lt;br /&gt;
&lt;br /&gt;
Run wireless handheld microphones to audience members asking questions.&lt;br /&gt;
*Jeanne Kliewer (jkliewer at emporia dot edu) Emporia State University&lt;br /&gt;
&lt;br /&gt;
== Session Timer Volunteers ==&lt;br /&gt;
&lt;br /&gt;
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop with a stopwatch program).&lt;br /&gt;
&lt;br /&gt;
* Ann Gleason (amwhit24 at uw dot edu) - University of Washington -- Not registered.&lt;br /&gt;
* Carmen Mitchell (carmenmitchell at gmail dot com) - California State University San Marcos&lt;br /&gt;
* Tod Robbins (todd.d.robbins at gmail) - University of Washington -- Not registered.&lt;br /&gt;
&lt;br /&gt;
'''Schedule for Session Timers'''&lt;br /&gt;
&lt;br /&gt;
== Raffles ==&lt;br /&gt;
* Kyle Banerjee (calling awardees)&lt;br /&gt;
* (backup)&lt;br /&gt;
* Michael B. Klein, Stanford University (mbklein@gmail.com) (program)&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=During_the_Conference_Volunteers&amp;diff=10400</id>
		<title>During the Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=During_the_Conference_Volunteers&amp;diff=10400"/>
				<updated>2012-01-25T16:09:21Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* IRC Access */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;code4lib 2012 Volunteers&lt;br /&gt;
&lt;br /&gt;
== Hospitality Suite Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee makes arrangements for any hospitality suite amenities (technology, snacks, games, icebreakers...) we may want&lt;br /&gt;
&lt;br /&gt;
* Mike Giarlo -- Penn State [Glad to be a keyholder, room-sitter, and general tidier-upper]&lt;br /&gt;
* Tom Johnson -- Oregon State University&lt;br /&gt;
* Lisa Kurt [lkurt at unr dot edu]-- University of Nevada, Reno&lt;br /&gt;
* Carmen Mitchell -- California State University San Marcos&lt;br /&gt;
* Declan Fleming -- UCSD&lt;br /&gt;
* Becky Yoose -- Grinnell College&lt;br /&gt;
* Devon Smith &lt;br /&gt;
&lt;br /&gt;
== Welcome Wagon Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Becky Yoose(b.yoose at gmail dot com) -- Grinnell College&lt;br /&gt;
* Bohyun Kim(kimb at fiu dot edu) -- Florida International University&lt;br /&gt;
* Jason Clark (jaclark at montana dot edu) Montana State University&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
Responsible for non-IRC social networking presence.&lt;br /&gt;
&lt;br /&gt;
*Rowena McKernan (rmckernan at whatcom dot ctc dot edu) ~ Whatcom Community College&lt;br /&gt;
&lt;br /&gt;
== IRC Evangelists ==&lt;br /&gt;
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.&lt;br /&gt;
&lt;br /&gt;
* Sam Kome (skome) Claremont Colleges&lt;br /&gt;
* Gabriel Farrell (gsf) (gsf747@gmail.com) Drexel University&lt;br /&gt;
* Michael Klein (mbklein) (mbklein@gmail.com) Stanford University&lt;br /&gt;
* Jon Gorman University of Illinois&lt;br /&gt;
&lt;br /&gt;
== IRC Access ==&lt;br /&gt;
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful.&lt;br /&gt;
&lt;br /&gt;
* Michael B. Klein -- emailed Freenode with IP block for conference.&lt;br /&gt;
* Cary Gordon (highermath) (cgordon at chillco.com) -- The Cherry Hill Company&lt;br /&gt;
&lt;br /&gt;
== Video Committee ==&lt;br /&gt;
Video archiving and video streaming possibilities.&lt;br /&gt;
&lt;br /&gt;
* Corey Harper corey dot harper gmail&lt;br /&gt;
* Shaun Ellis shaune@princeton.edu&lt;br /&gt;
* Cary Gordon (cgordon at chillco.com) -- The Cherry Hill Company&lt;br /&gt;
&lt;br /&gt;
==Registration Desk Volunteers==&lt;br /&gt;
We need 1-2 volunteers to hang out at the registration desk for 2-hour shifts.  Also on Monday and Tuesday, an additional volunteer with wireless access knowledge would be helpful on the Registration Desk to answer tech questions.&lt;br /&gt;
&lt;br /&gt;
* Dan Suchy (dansuchy at gmail) -- UC San Diego&lt;br /&gt;
* Doris Munson (dmunson at ewu.edu) -- Eastern Washington University&lt;br /&gt;
* Tod Robbins (todd.d.robbins at gmail) -- University of Washington&lt;br /&gt;
&lt;br /&gt;
===Registration Desk Schedule===&lt;br /&gt;
Monday&lt;br /&gt;
7-9 am&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
* (wireless expert)&lt;br /&gt;
Monday 9-11 am&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
Tuesday&lt;br /&gt;
7-9 am&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
* (wireless expert)&lt;br /&gt;
Tuesday 9-11 am&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
Tuesday AM&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
Tuesday PM&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
Wednesday AM&lt;br /&gt;
* Becky Yoose&lt;br /&gt;
&lt;br /&gt;
Wednesday PM&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
Thursday AM&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
== Microphone Runners==&lt;br /&gt;
&lt;br /&gt;
Run wireless handheld microphones to audience members asking questions.&lt;br /&gt;
*Jeanne Kliewer (jkliewer at emporia dot edu) Emporia State University&lt;br /&gt;
&lt;br /&gt;
== Session Timer Volunteers ==&lt;br /&gt;
&lt;br /&gt;
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop with a stopwatch program).&lt;br /&gt;
&lt;br /&gt;
* Ann Gleason (amwhit24 at uw dot edu) - University of Washington&lt;br /&gt;
* Carmen Mitchell (carmenmitchell at gmail dot com) - California State University San Marcos&lt;br /&gt;
* Tod Robbins (todd.d.robbins at gmail) - University of Washington&lt;br /&gt;
&lt;br /&gt;
'''Schedule for Session Timers'''&lt;br /&gt;
&lt;br /&gt;
== Raffles ==&lt;br /&gt;
* Kyle Banerjee (calling awardees)&lt;br /&gt;
* (backup)&lt;br /&gt;
* Michael B. Klein, Stanford University (mbklein@gmail.com) (program)&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_committees_sign-up_page&amp;diff=10399</id>
		<title>2012 committees sign-up page</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_committees_sign-up_page&amp;diff=10399"/>
				<updated>2012-01-25T16:08:31Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* Book Give-Away Committee */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2012 Committees =&lt;br /&gt;
&lt;br /&gt;
If you are interested in helping out with a particular part of the Code4Lib 2012 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.&lt;br /&gt;
&lt;br /&gt;
[[During the Conference Volunteers]]&lt;br /&gt;
&lt;br /&gt;
== Book Give-Away Committee ==&lt;br /&gt;
&lt;br /&gt;
* Kevin S. Clarke (ksclarke@gmail.com) -- McHenry Library, UC Santa Cruz -- Asking O'Reilly&lt;br /&gt;
* Chandos Publishing. Yes.&lt;br /&gt;
* No Starch. Yes.&lt;br /&gt;
* [http://www.seattletechnicalbooks.com Ada's Technical Books]. Woohoo.&lt;br /&gt;
* Andrew Nagy -- oXygen XML Editor (5 Licenses to give away)&lt;br /&gt;
* [[BookRaffle|Suggestions for Book Raffle.]]&lt;br /&gt;
&lt;br /&gt;
== Sponsorships Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Kyle Banerjee (banerjek@uoregon.edu) -- Orbis Cascade Alliance&lt;br /&gt;
* Anjanette Young -- University of Washington&lt;br /&gt;
* Mike Giarlo -- Penn State&lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]] -- LYRASIS (likely sponsor)&lt;br /&gt;
* Andrew Nagy -- Serials Solutions&lt;br /&gt;
* Roy Tennant -- OCLC&lt;br /&gt;
&lt;br /&gt;
== Keynote Speakers Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Ann Lally (alally at uw dot edu) University of Washington&lt;br /&gt;
* Dre (akorphan at ncsu dot edu) North Carolina State University&lt;br /&gt;
&lt;br /&gt;
== Program Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee plans the structure of the program, arranges the voting on presentations, etc. These folks will also announce speakers, etc.&lt;br /&gt;
&lt;br /&gt;
* Jeremy Frumkin (frumkinj at u dot library dot arizona dot edu) - University of Arizona&lt;br /&gt;
* Ranti Junus (ranti.junus at gmail) - Michigan State University&lt;br /&gt;
* John Fink (john.fink at gmail) - McMaster University&lt;br /&gt;
* Tom Johnson (thomas dot johnson at oregonstate dot edu) - Oregon State University&lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]] - LYRASIS&lt;br /&gt;
&lt;br /&gt;
== Scholarships Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Jeremy Frumkin (frumkinj at u dot library dot arizona dot edu) - University of Arizona&lt;br /&gt;
* Jodi Schneider - DERI, NUI Galway&lt;br /&gt;
* Becky Yoose [yoosebec] at grinnell dot edu - Grinnell College&lt;br /&gt;
* Ed Corrado - Binghamton University&lt;br /&gt;
* Terry Reese - Oregon State University&lt;br /&gt;
* Ranti Junus - Michigan State University&lt;br /&gt;
&lt;br /&gt;
== T-Shirt Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes.&lt;br /&gt;
&lt;br /&gt;
* Ann Lally (alally at uw dot edu) University of Washington&lt;br /&gt;
* Angie Beiriger (beiriger at reed dot edu) Reed college&lt;br /&gt;
&lt;br /&gt;
== Social Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
The committee plans, proposes, and organizes the evening activities.&lt;br /&gt;
&lt;br /&gt;
* Jennifer Ward (jlward1 at uw dot edu) -- University of Washington&lt;br /&gt;
* Jeff Sherwood (jeffs3 at uw dot edu) -- University of Washington&lt;br /&gt;
&lt;br /&gt;
== Voting Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
= Documentation =&lt;br /&gt;
To help with documention, no need to sign up, just start editing.&lt;br /&gt;
* [[How To Plan A Code4LibCon]]&lt;br /&gt;
&lt;br /&gt;
== Documentation Interest Group ==&lt;br /&gt;
Promote ongoing documentation efforts.&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_committees_sign-up_page&amp;diff=9985</id>
		<title>2012 committees sign-up page</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_committees_sign-up_page&amp;diff=9985"/>
				<updated>2011-12-13T17:39:22Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2012 Committees =&lt;br /&gt;
&lt;br /&gt;
If you are interested in helping out with a particular part of the Code4Lib 2012 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.&lt;br /&gt;
&lt;br /&gt;
== Book Give-Away Committee ==&lt;br /&gt;
&lt;br /&gt;
* Kevin S. Clarke (ksclarke@gmail.com) -- McHenry Library, UC Santa Cruz -- Asking O'Reilly&lt;br /&gt;
* Chandos Publishing. Yes.&lt;br /&gt;
* Anjanette -- Asking Manning (via Erik Hatcher)&lt;br /&gt;
* No Starch. Yes.&lt;br /&gt;
* [http://www.seattletechnicalbooks.com Ada's Technical Books]. Woohoo.&lt;br /&gt;
* Andrew Nagy -- oXygen XML Editor (5 Licenses to give away)&lt;br /&gt;
* [[BookRaffle|Suggestions for Book Raffle.]]&lt;br /&gt;
&lt;br /&gt;
== Sponsorships Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Kyle Banerjee (banerjek@uoregon.edu) -- Orbis Cascade Alliance&lt;br /&gt;
* Anjanette Young -- University of Washington&lt;br /&gt;
* Mike Giarlo -- Penn State&lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]] -- LYRASIS (likely sponsor)&lt;br /&gt;
* Andrew Nagy -- Serials Solutions&lt;br /&gt;
* Roy Tennant -- OCLC&lt;br /&gt;
&lt;br /&gt;
== Keynote Speakers Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Ann Lally (alally at uw dot edu) University of Washington&lt;br /&gt;
* Dre (akorphan at ncsu dot edu) North Carolina State University&lt;br /&gt;
&lt;br /&gt;
== Program Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee plans the structure of the program, arranges the voting on presentations, etc. These folks will also announce speakers, etc.&lt;br /&gt;
&lt;br /&gt;
* Jeremy Frumkin (frumkinj at u dot library dot arizona dot edu) - University of Arizona&lt;br /&gt;
* Ranti Junus (ranti.junus at gmail) - Michigan State University&lt;br /&gt;
* John Fink (john.fink at gmail) - McMaster University&lt;br /&gt;
* Tom Johnson (thomas dot johnson at oregonstate dot edu) - Oregon State University&lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]] - LYRASIS&lt;br /&gt;
&lt;br /&gt;
== Scholarships Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Jeremy Frumkin (frumkinj at u dot library dot arizona dot edu) - University of Arizona&lt;br /&gt;
* Jodi Schneider - DERI, NUI Galway&lt;br /&gt;
* Becky Yoose [yoosebec] at grinnell dot edu - Grinnell College&lt;br /&gt;
* Ed Corrado - Binghamton University&lt;br /&gt;
* Terry Reese - Oregon State University&lt;br /&gt;
* Ranti Junus - Michigan State University&lt;br /&gt;
&lt;br /&gt;
== T-Shirt Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes.&lt;br /&gt;
&lt;br /&gt;
* Ann Lally (alally at uw dot edu) University of Washington&lt;br /&gt;
* Angie Beiriger (beiriger at reed dot edu) Reed college&lt;br /&gt;
&lt;br /&gt;
== Social Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
The committee plans, proposes, and organizes the evening activities.&lt;br /&gt;
&lt;br /&gt;
* Jennifer Ward (jlward1 at uw dot edu) -- University of Washington&lt;br /&gt;
* Jeff Sherwood (jeffs3 at uw dot edu) -- University of Washington&lt;br /&gt;
&lt;br /&gt;
== Voting Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Hospitality Suite Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee makes arrangements for any hospitality suite amenities (technology, snacks, games, icebreakers...) we may want&lt;br /&gt;
&lt;br /&gt;
* Mike Giarlo -- Penn State [Glad to be a keyholder, room-sitter, and general tidier-upper]&lt;br /&gt;
* Tom Johnson -- Oregon State University&lt;br /&gt;
* Lisa Kurt [lkurt at unr dot edu]-- University of Nevada, Reno&lt;br /&gt;
* Carmen Mitchell -- California State University San Marcos&lt;br /&gt;
&lt;br /&gt;
== Welcome Wagon Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Becky Yoose(b.yoose at gmail dot com) -- Grinnell College&lt;br /&gt;
* Bohyun Kim(kimb at fiu dot edu) -- Florida International University&lt;br /&gt;
* Jason Clark (jaclark at montana dot edu) Montana State University&lt;br /&gt;
* Mariela Gunn (gunn at oakland dot edu) -- Oakland University&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
Responsible for non-IRC social networking presence.&lt;br /&gt;
&lt;br /&gt;
*Rowena McKernan (rmckernan at whatcom dot ctc dot edu) ~ Whatcom Community College&lt;br /&gt;
&lt;br /&gt;
== IRC Evangelists ==&lt;br /&gt;
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.&lt;br /&gt;
&lt;br /&gt;
* Sam Kome (skome) Claremont Colleges&lt;br /&gt;
* Gabriel Farrell (gsf) (gsf747@gmail.com) Drexel University&lt;br /&gt;
&lt;br /&gt;
== IRC Access ==&lt;br /&gt;
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful.&lt;br /&gt;
&lt;br /&gt;
* Cary Gordon (cgordon at chillco.com) -- The Cherry Hill Company&lt;br /&gt;
&lt;br /&gt;
== Video Committee ==&lt;br /&gt;
Video archiving and video streaming possibilities.&lt;br /&gt;
&lt;br /&gt;
* Corey Harper corey dot harper gmail&lt;br /&gt;
&lt;br /&gt;
==Registration Desk Volunteers==&lt;br /&gt;
We need 1-2 volunteers to hang out at the registration desk for 2-hour shifts.  Also on Monday and Tuesday, an additional volunteer with wireless access knowledge would be helpful on the Registration Desk to answer tech questions.&lt;br /&gt;
&lt;br /&gt;
* Dan Suchy (dansuchy at gmail) -- UC San Diego&lt;br /&gt;
* Doris Munson (dmunson at ewu.edu) -- Eastern Washington University&lt;br /&gt;
* Tod Robbins (todd.d.robbins at gmail) -- University of Washington&lt;br /&gt;
&lt;br /&gt;
== Microphone Runners==&lt;br /&gt;
&lt;br /&gt;
Run wireless handheld microphones to audience members asking questions.&lt;br /&gt;
*Jeanne Kliewer (jkliewer at emporia dot edu) Emporia State University&lt;br /&gt;
&lt;br /&gt;
== Session Timer Volunteers ==&lt;br /&gt;
&lt;br /&gt;
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop with a stopwatch program).&lt;br /&gt;
&lt;br /&gt;
* Ann Gleason (amwhit24 at uw dot edu) - University of Washington&lt;br /&gt;
* Carmen Mitchell (carmenmitchell at gmail dot com) - California State University San Marcos&lt;br /&gt;
* Tod Robbins (todd.d.robbins at gmail) - University of Washington&lt;br /&gt;
* Mariela Gunn (gunn at oakland dot edu) - Oakland University&lt;br /&gt;
&lt;br /&gt;
'''Schedule for Session Timers'''&lt;br /&gt;
&lt;br /&gt;
== Raffles ==&lt;br /&gt;
 (calling awardees)&lt;br /&gt;
 (backup)&lt;br /&gt;
 (program)&lt;br /&gt;
&lt;br /&gt;
= Documentation =&lt;br /&gt;
To help with documention, no need to sign up, just start editing.&lt;br /&gt;
* [[How To Plan A Code4LibCon]]&lt;br /&gt;
&lt;br /&gt;
== Documentation Interest Group ==&lt;br /&gt;
Promote ongoing documentation efforts.&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=C4l2012_t-shirtcontest&amp;diff=9972</id>
		<title>C4l2012 t-shirtcontest</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=C4l2012_t-shirtcontest&amp;diff=9972"/>
				<updated>2011-12-09T16:04:19Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Deadline, November 21, 2011, for t-shirt design submissions has passed. &lt;br /&gt;
&lt;br /&gt;
[http://vote.code4lib.org/election/22 It's time to vote!] -- You will need your code4lib.org username and password.&lt;br /&gt;
&lt;br /&gt;
It's time to submit designs for the Code4Lib 2012 conference T-shirt!&lt;br /&gt;
Your design should somehow capture the awesomeness of the code4lib community and be something you'd be proud to wear.&lt;br /&gt;
&lt;br /&gt;
The design submissions are for the front of the shirt and may be as large as 11&amp;quot; by 15&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Keep in mind that these will be printed in one color on a shirt of another color, so please make your design accordingly.&lt;br /&gt;
&lt;br /&gt;
The vendor indicated that they preferred Adobe Illustrator or EPS formatted files, though we can convert other formats.  Please send&lt;br /&gt;
submissions to me (e-mail address below) by Monday November 21st, at which point they'll be posted for your review and voting [probably&lt;br /&gt;
after the Thanksgiving holiday here in the U.S.]&lt;br /&gt;
&lt;br /&gt;
--&lt;br /&gt;
Ann Lally&lt;br /&gt;
Head, Digital Initiatives&lt;br /&gt;
University of Washington Libraries&lt;br /&gt;
alally_at_uw.edu&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=C4l2012_t-shirtcontest&amp;diff=9943</id>
		<title>C4l2012 t-shirtcontest</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=C4l2012_t-shirtcontest&amp;diff=9943"/>
				<updated>2011-12-01T17:48:24Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Deadline, November 21, 2011, for t-shirt design submissions has passed.&lt;br /&gt;
&lt;br /&gt;
It's time to submit designs for the Code4Lib 2012 conference T-shirt!&lt;br /&gt;
Your design should somehow capture the awesomeness of the code4lib community and be something you'd be proud to wear.&lt;br /&gt;
&lt;br /&gt;
The design submissions are for the front of the shirt and may be as large as 11&amp;quot; by 15&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Keep in mind that these will be printed in one color on a shirt of another color, so please make your design accordingly.&lt;br /&gt;
&lt;br /&gt;
The vendor indicated that they preferred Adobe Illustrator or EPS formatted files, though we can convert other formats.  Please send&lt;br /&gt;
submissions to me (e-mail address below) by Monday November 21st, at which point they'll be posted for your review and voting [probably&lt;br /&gt;
after the Thanksgiving holiday here in the U.S.]&lt;br /&gt;
&lt;br /&gt;
--&lt;br /&gt;
Ann Lally&lt;br /&gt;
Head, Digital Initiatives&lt;br /&gt;
University of Washington Libraries&lt;br /&gt;
alally_at_uw.edu&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_preconference_proposals&amp;diff=9907</id>
		<title>2012 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_preconference_proposals&amp;diff=9907"/>
				<updated>2011-11-21T16:21:43Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Proposals for 2012 Code4LibCon Preconferences=&lt;br /&gt;
Proposals closed Sunday, November 20, 2011, so we can finalize the list and add them to registration! (The deadline for preconference proposals has passed.)&lt;br /&gt;
&lt;br /&gt;
Spaces available: main meeting room (max 275) + 5 breakout rooms (max 30-50). &lt;br /&gt;
&lt;br /&gt;
'''Please include a &amp;quot;Contact/Responsible Individual&amp;quot; name and email address so we know who is willing to put on the proposed precon.&lt;br /&gt;
'''&lt;br /&gt;
==Full Day==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Hacking Content ===&lt;br /&gt;
&lt;br /&gt;
What is the future of getting library information and resources into users’ hands at the right time and with appropriate context and relevancy.  Learning management systems, library guides, Web-scale discovery systems-plenty of tools to choose from and still we see lots of opportunities for improvement. Let’s pick them apart and brainstorm ideas for projects that could address weaknesses in one or all of these systems. If you’re interested in these issues, challenges and conundrums join us for a day of thinking, dreaming and scheming. All skill sets and backgrounds needed. &lt;br /&gt;
&lt;br /&gt;
Speakers/Facilitators will be:&lt;br /&gt;
 - Thom Cox - Manager of Library Information Technology Services - Tufts University&lt;br /&gt;
 - Ken Varnum – Web Systems Manager - University of Michigan Libraries&lt;br /&gt;
 - Evviva Weinraub – Director, Emerging Technologies and Services - Oregon State University Libraries &lt;br /&gt;
&lt;br /&gt;
Contact:  Margaret Mellinger - margaret dot mellinger at oregonstate dot edu&lt;br /&gt;
&lt;br /&gt;
=== Developing applications using REST web services ===&lt;br /&gt;
&lt;br /&gt;
Been hearing about web services but don’t know where to start to build something? Have you built applications that use read services but are stumped by OAuth, Content Negotiation and HTTP Headers? Come dig in and learn how to build applications that interact with both read and write REST services. We’ll cover the basic principles and practices of REST services and discuss the Atom Publishing Protocol as a REST service and its extensibility. The group will examine and test the CouchDB HTTP API by building a simple list creation tool. You’ll learn how OCLC’s platform web services leverage Atom to expose the data and business processes from OCLC’s library systems. By the end of the session, you’ll know the basic principles of REST services, be able to perform Create, Read, Update and Delete operations via REST and be able to authenticate to REST services via API keys and OAuth.&lt;br /&gt;
&lt;br /&gt;
Come ready to learn and code!&lt;br /&gt;
&lt;br /&gt;
Presenter: Karen Coombs - coombsk at oclc dot org&lt;br /&gt;
&lt;br /&gt;
==Half Day Morning==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Linkfest ===&lt;br /&gt;
&lt;br /&gt;
We've had talks and sessions galore about Linked Data at code4lib in past years.  Let's focus on linking.  Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web.  At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there.  May a kajillion links bloom!&lt;br /&gt;
&lt;br /&gt;
If you need an &amp;quot;intro to linked data&amp;quot; we can prep a good list of readings/talks to review before you come.  But please come ready to link!&lt;br /&gt;
&lt;br /&gt;
Organizer type person:  Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu&lt;br /&gt;
&lt;br /&gt;
=== What's New in Solr ===&lt;br /&gt;
&lt;br /&gt;
This session will bring folks up to speed on the latest developments in Lucene and Solr.  There's always a lot of new capabilities as well as tips and tricks on using Solr in clever and powerful ways.  &lt;br /&gt;
&lt;br /&gt;
Presenter: Erik Hatcher - erik . hatcher @ lucidimagination dot com&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Half Day Afternoon==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Git -r done === &lt;br /&gt;
&lt;br /&gt;
A session to cover all things Git, everyone's favourite distributed version control system.  This session should cover a little bit of the history of Git, how it works, and how it's different than other version controls systems like SVN.  Practical application should also be covered, including how to clone existing repos and contribute code back to them, how to host your own repository, and best practices for setting up a distributed network.&lt;br /&gt;
&lt;br /&gt;
Looking for attendees with real-life Git experience to share it, so we can all broaden our understanding of possible use-cases and nifty advanced features.&lt;br /&gt;
&lt;br /&gt;
Coordinator:  Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com&lt;br /&gt;
&lt;br /&gt;
=== Blacklight ===&lt;br /&gt;
&lt;br /&gt;
This session will be walk-through of the architecture of Blacklight and what we have been improving since the rails 3 upgrade.  In addition to the architecture of the software, we will also briefly discuss the architecture of the Blacklight community and what has made it successful so far.&lt;br /&gt;
&lt;br /&gt;
For part of the session we will install Blacklight live and get it up and running.  This install demo will include a How-To on basic customizations in Blacklight using a test-driven approach (one of the cornerstones of the Blacklight community).&lt;br /&gt;
&lt;br /&gt;
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).  We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.&lt;br /&gt;
&lt;br /&gt;
Presenters: Jessie Keck, Stanford University - jkeck at stanford dot edu | Molly Pickral, University of Virginia - mpc3c at virginia dot edu&lt;br /&gt;
&lt;br /&gt;
=== DACS and EAD Overview ===&lt;br /&gt;
&lt;br /&gt;
This session will look at what DACS (Describing Archives: a Content Standard) is and describe the ten required elements.  Then there will be an overview of what EAD is, how it works, and the required elements.  The final part will be a practice session on taking a paper finding aid and coding it using DACS and EAD.&lt;br /&gt;
&lt;br /&gt;
Presenter:  Doris Munson, Eastern Washington University, dmunson at ewu dot edu&lt;br /&gt;
(please feel free to contact me if you are interested in being a co-presenter)&lt;br /&gt;
&lt;br /&gt;
=== Digging into metadata: context, code, and collaboration ===&lt;br /&gt;
&lt;br /&gt;
Working with library/archival metadata is difficult. This preconference will tackle pressing questions and will show some of the intricacies of metadata (including AACR2/MARC) with exercises to demonstrate why inconsistencies exist in the data. What steps can the cataloging &amp;amp; metadata community take to help improve the quality of this data?  What tools &amp;amp; techniques could help?  Rules have evolved over time leaving dirty legacy data.  Systems have impacted--and will continue to impact--data structure &amp;amp; design.  How can this data be aggregated and refined for use in a new emerging data environments?  What assumptions can safely be made and when do you need to inquire about local practice?  We will end with a hack-fest where you can ask questions of experienced catalogers and get help with your metadata related problems.  Bring your laptops and data.   &lt;br /&gt;
&lt;br /&gt;
Person Herder: Becky Yoose, Grinnell College, yoosebec at grinnell dot edu&lt;br /&gt;
&lt;br /&gt;
Collaborators/Facilitators: Corey Harper, New York University - corey dot harper at nyu dot edu | Shana L. McDanold, University of Pennsylvania - 	&lt;br /&gt;
mcdanold at pobox dot upenn dot edu  | Laura Smart, Caltech - laura at library dot caltech dot edu&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_talks_proposals&amp;diff=9906</id>
		<title>2012 talks proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_talks_proposals&amp;diff=9906"/>
				<updated>2011-11-21T16:19:17Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Deadline for talk submission was ''Sunday, November 20''. (The deadline for 2012 Talks proposals is now closed.)&lt;br /&gt;
&lt;br /&gt;
Prepared talks are 20 minutes (including setup and questions), and focus on one or more of the following areas:&lt;br /&gt;
 * tools (some cool new software, software library or integration platform)&lt;br /&gt;
 * specs (how to get the most out of some protocols, or proposals for new ones)&lt;br /&gt;
 * challenges (one or more big problems we should collectively address)&lt;br /&gt;
&lt;br /&gt;
The community will vote on proposals using the criteria of:&lt;br /&gt;
 * usefulness&lt;br /&gt;
 * newness&lt;br /&gt;
 * geekiness&lt;br /&gt;
 * diversity of topics&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Talk Title: ==&lt;br /&gt;
 &lt;br /&gt;
* Speaker's name, affiliation, and email address&lt;br /&gt;
* Second speaker's name, affiliation, email address, if second speaker&lt;br /&gt;
&lt;br /&gt;
Abstract of no more than 500 words.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== VuFind 2.0: Why and How? ==&lt;br /&gt;
&lt;br /&gt;
* Demian Katz, Villanova University, demian.katz@villanova.edu&lt;br /&gt;
&lt;br /&gt;
A major new version of the VuFind discovery software is currently in development.  While VuFind 1.x remains extremely popular, some of its components are beginning to show their age.  VuFind 2.0 aims to retain all the strengths of the previous version of the software while making the architecture cleaner, more modern and more standards-based.  This presentation will examine the motivation behind the update, preview some of the new features to look forward to, and discuss the challenges of creating a developer-friendly open source package in PHP.&lt;br /&gt;
&lt;br /&gt;
== Open Source Software Registry ==&lt;br /&gt;
&lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]], LYRASIS, Peter.Murray@lyrasis.org&lt;br /&gt;
&lt;br /&gt;
LYRASIS is creating and shepherding a [[Registry_E-R_Diagram|registry of library open source software]] as part of its [http://www.lyrasis.org/News/Press-Releases/2011/LYRASIS-Receives-Grant-to-Support-Open-Source.aspx grant from the Mellon Foundation to support the adoption of open source software by libraries].  &lt;br /&gt;
The goal of the grant is to help libraries of all types determine if open source software is right for them, and what combination of software, hosting, training, and consulting works for their situation.  &lt;br /&gt;
The registry is intended to become a community exchange point and stimulant for growth of the library open source ecosystem by connecting libraries with projects, service providers, and events.&lt;br /&gt;
&lt;br /&gt;
The first half of this session will demonstrate the registry functions and describe how projects and providers can get involved.  &lt;br /&gt;
The second half of the session will be a brainstorming suggestion of how to expand the functionality and usefulness of the registry.&lt;br /&gt;
&lt;br /&gt;
== Property Graphs And TinkerPop Applications in Digital Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Brian Tingle, California Digital Library, brian.tingle.cdlib.org@gmail.com&lt;br /&gt;
&lt;br /&gt;
[http://www.tinkerpop.com/ TinkerPop] is an open source software development group focusing on technologies in the [http://en.wikipedia.org/wiki/Graph_database graph database] space.   &lt;br /&gt;
This talk will provide a general introduction to the TinkerPop Graph Stack and the [https://github.com/tinkerpop/gremlin/wiki/Defining-a-Property-Graph property graph model] is uses.  The introduction will include code examples and explanations of the property graph models used by the [http://socialarchive.iath.virginia.edu/ Social Networks in Archival Context] project and show how the historical social graph is exposed as a JSON/REST API implemented by a TinkerPop [https://github.com/tinkerpop/rexster rexster] [https://github.com/tinkerpop/rexster-kibbles Kibble] that contains the application's graph theory logic.  Other graph database applications possible with TinkerPop such as RDF support, and citation analysis will also be discussed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Security in Mind ==&lt;br /&gt;
 &lt;br /&gt;
* Erin Germ, United States Naval Academy, Nimitz Library, germ@usna.edu&lt;br /&gt;
&lt;br /&gt;
I would like to talk about security of library software.&lt;br /&gt;
&lt;br /&gt;
Over the Summer, I discovered a critical vulnerability in a vendor’s software that (verified) allowed me to assume any user’s identity for that site, (verified) switch to any user, and to (unverified, meaning I didn’t not perform this as I didn’t want to “hack” another library’s site) assume the role of any user for any other library who used this particular vendor's software.&lt;br /&gt;
&lt;br /&gt;
Within a 3 hour period, I discovered a 2 vulnerabilities: 1) minor one allowing me to access any backups from any library site, and 2) a critical vulnerability.  From start to finish, the examination, discovery in the vulnerability, and execution of a working exploit was done in less than 2 hours. The vulnerability was a result of poor cookie implementation. The exploit itself revolved around modifying the cookie, and then altering the browser’s permissions by assuming the role of another user.&lt;br /&gt;
&lt;br /&gt;
I do not intend on stating which vendor it was, but I will show how I was able to perform this. If needed, I can do further research and “investigation” into other vendor's software to see what I can “find”.&lt;br /&gt;
&lt;br /&gt;
''If selected, I will contact the vendor to inform them that I will present about this at C4L2012. I do not intend on releasing the name of the vendor.''&lt;br /&gt;
&lt;br /&gt;
== Search Engines and Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Greg Lindahl, blekko CTO, greg@blekko.com&lt;br /&gt;
&lt;br /&gt;
[https://blekko.com blekko] is a new web-scale search engine which enables end-users to create vertical search engines, through a feature called [http://help.blekko.com/index.php/category/slashtags/ slashtags]. Slashtags can contain as few as 1 or as many as tens of thousands of websites relevant to a narrow or broad topic. We have an extensive set of slashtags curated by a combination of volunteers and an in-house librarian team, or end-users can create and share their own. This talk will cover examples of slashtag creation relevant to libraries, and show how to embed this search into a library website, either using javascript or via our API.&lt;br /&gt;
&lt;br /&gt;
''We have exhibited at a couple of library conferences, and have received a lot of interest. blekko is a free service.''&lt;br /&gt;
&lt;br /&gt;
== Beyond code: Versioning data with Git and Mercurial. ==&lt;br /&gt;
&lt;br /&gt;
* Stephanie Collett, California Digital Library, stephanie.collett@ucop.edu&lt;br /&gt;
* Martin Haye, California Digital Library, martin.haye@ucop.edu&lt;br /&gt;
&lt;br /&gt;
Within a relatively short time since their introduction, [http://en.wikipedia.org/wiki/Distributed_Version_Control_System distributed version control systems] (DVCS) like [http://git-scm.com/ Git] and [http://mercurial.selenic.com/ Mercurial] have enjoyed widespread adoption for versioning code. It didn’t take long for the library development community to start discussing the potential for using DVCS within our applications and repositories to version data. After all, many of the features that have made some of these systems popular in the open source community to version code (e.g. lightweight, file-based, compressed, reliable) also make them compelling options for versioning data.  And why write an entire versioning system from scratch if a DVCS solution can be a drop-in solution? At the [http://www.cdlib.org/ California Digital Library] (CDL) we’ve started using Git and Mercurial in some of our applications to version data. This has proven effective in some situations and unworkable in others. This presentation will be a practical case study of CDL’s experiences with using DVCS to version data. We will explain how we’re incorporating Git and Mercurial in our applications, describe our successes and failures and consider the issues involved in repurposing these systems for data versioning.&lt;br /&gt;
&lt;br /&gt;
==Design for Developers==&lt;br /&gt;
&lt;br /&gt;
*Lisa Kurt, University of Nevada, Reno, lkurt@unr.edu&lt;br /&gt;
&lt;br /&gt;
Users expect good design. This talk will delve into what makes really great design, what to look for, and how to do it. Learn the principles of great design to take your applications, user interfaces, and projects to a higher level. With years of experience in graphic design and illustration, Lisa will discuss design principles, trends, process, tools, and development. Design examples will be from her own projects as well as a variety from industry. You’ll walk away with design knowledge that you can apply immediately to a variety of applications and a number of top notch go-to resources to get you up and running.&lt;br /&gt;
&lt;br /&gt;
==Building research applications with Mendeley==&lt;br /&gt;
&lt;br /&gt;
William Gunn, Mendeley william.gunn@mendeley.com (@mrgunn)&lt;br /&gt;
&lt;br /&gt;
This is partly a tool talk and partly a big idea one.&lt;br /&gt;
&lt;br /&gt;
Mendeley has built the world's largest open database of research and we've now begun to collect some interesting social metadata around the document metadata. I would like to share with the Code4Lib attendees information about using this resource to do things within your application that have previously been impossible for the library community, or in some cases impossible without expensive database subscriptions. One thing that's now possible is to augment catalog search by surfacing information about content usage, allowing people to not only find things matching a query, but popular things or things read by their colleagues. In addition to augmenting search, you can also use this information to augment discovery. Imagine an online exhibit of artifacts from a newly discovered dig not just linking to papers which discuss the artifact, but linking to really good interesting papers about the place and the people who made the artifacts. So the big idea is, &amp;quot;How will looking at the literature from a broader perspective than simple citation analysis change how research is done and communicated? How can we build tools that make this process easier and faster?&amp;quot; I can show some examples of applications that have been built using the Mendeley and PLoS APIs to begin to address this question, and I can also present results from Mendeley's developer challenge which shows what kinds of applications researchers are looking for, what kind of applications peope are building, and illustrates some interesting places where the two don't overlap.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Your UI can make or break the application (to the user, anyway)==&lt;br /&gt;
&lt;br /&gt;
* Robin Schaaf, University of Notre Dame, schaaf.4@nd.edu&lt;br /&gt;
&lt;br /&gt;
UI development is hard and too often ends up as an after-thought to computer programmers - if you were a CS major in college I'll bet you didn't have many, if any, design courses.  I'll talk about how to involve the users upfront with design and some common pitfalls of this approach.  I'll also make a case for why you should do the screen design before a single line of code is written.  And I'll throw in some ideas for increasing usability and attractiveness of your web applications.  I'd like to make a case study of the UI development of our open source ERMS.&lt;br /&gt;
&lt;br /&gt;
==Why Nobody Knows How Big The Library Really Is - Perspective of a Library Outside Turned Insider==&lt;br /&gt;
&lt;br /&gt;
* Patrick Berry, California State University, Chico, pberry@csuchico.edu&lt;br /&gt;
&lt;br /&gt;
In this talk I would like to bring the perspective of an &amp;quot;outsider&amp;quot; (although an avowed IT insider) to let you know that people don't understand the full scope of the library.  As we &amp;quot;rethink education&amp;quot;, it is incumbent upon us to help educate our institutions as to the scope of the library.  I will present some of the tactics I'm employing to help people outside, and in some cases inside, the library to understand our size and the value we bring to the institution.&lt;br /&gt;
&lt;br /&gt;
==Building a URL Management Module using the Concrete5 Package Architecture==&lt;br /&gt;
&lt;br /&gt;
* David Uspal, Villanova University, david.uspal@villanova.edu&lt;br /&gt;
&lt;br /&gt;
Keeping track of URLs utilized across a large website such as a university library, and keeping that content up to date for subject and course guides, can be a pain, and as an open source shop, we’d like to have open source solution for this issue.  For this talk, I intend to detail our solution to this issue by walking step-by-step through the building process for our URL Management module -- including why a new solution was necessary; a quick rundown of our CMS ([http://www.concrete5.org Concrete5], a CMS that isn’t Drupal); utilizing the Concrete5 APIs to isolate our solution from core code (to avoid complications caused by core updates); how our solution was integrated into the CMS architecture for easy installation; and our future plans on the project.&lt;br /&gt;
&lt;br /&gt;
==Building an NCIP connector to OpenSRF to facilitate resource sharing==&lt;br /&gt;
&lt;br /&gt;
* Jon Scott, Lyrasis, jon_scott@wsu.edu and Kyle Banerjee, Orbis Cascade Alliance, banerjek@uoregon.edu &lt;br /&gt;
&lt;br /&gt;
How do you reverse engineer any protocol to provide a new service? Humans (and worse yet, committees) often design verbose protocols built around use cases that don't line up current reality. To compound difficulties, the contents of protocol containers are not sufficiently defined/predictable and the only assistance available is sketchy documentation and kind individuals on the internet willing to share what they learned via trial by fire.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCIP (Niso Circulation Interchange Protocol) is an open standard that defines a set of messages to support exchange of circulation data between disparate circulation, interlibrary loan, and related applications -- widespread adoption of NCIP would eliminate huge amounts of duplicate processing in separate systems. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This presentation discusses how we learned enough about NCIP and OpenSRF from scratch to build an NCIP responder for Evergreen to facilitate resource sharing in a large consortium that relies on over 20 different ILSes.&lt;br /&gt;
&lt;br /&gt;
==Practical Agile: What's Working for Stanford, Blacklight, and Hydra==&lt;br /&gt;
&lt;br /&gt;
* Naomi Dushay, Stanford University Libraries, ndushay@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Agile development techniques can be difficult to adopt in the context of library software development.  Maybe your shop has only one or two developers, or you always have too many simultaneous projects.   Maybe your new projects can’t be started until 27 librarians reach consensus on the specifications.&lt;br /&gt;
&lt;br /&gt;
This talk will present successful Agile- and Silicon-Valley-inspired practices we’ve adopted at Stanford and/or in the Blacklight and Hydra projects.  We’ve targeted developer happiness as well as improved productivity with our recent changes.  User stories, dead week, sight lines … it’ll be a grab bag of goodies to bring back to your institution, including some ideas on how to adopt these practices without overt management buy in.&lt;br /&gt;
&lt;br /&gt;
==Quick and &amp;lt;strike&amp;gt;Dirty&amp;lt;/strike&amp;gt; Clean Usability: Rapid Prototyping with Bootstrap==&lt;br /&gt;
&lt;br /&gt;
* Shaun Ellis, Princeton University Libraries, shaune@princeton.edu &lt;br /&gt;
&lt;br /&gt;
''&amp;quot;The code itself is unimportant; a project is only as useful as people actually find it.&amp;quot;  - Linus Torvalds'' [http://bit.ly/p4uuyy]&lt;br /&gt;
&lt;br /&gt;
Usability has been a buzzword for some time now, but what is the process for making the the transition toward a better user experience, and hence, better designed library sites?  I will discuss the one facet of the process my team is using to redesign the Finding Aids site for Princeton University Libraries (still in development).  The approach involves the use of rapid prototyping, with Bootstrap [http://twitter.github.com/bootstrap/], to make sure we are on track with what users and stakeholders expect up front, and throughout the development process.&lt;br /&gt;
&lt;br /&gt;
Because Bootstrap allows for early and iterative user feedback, it is more effective than the historic Photoshop mockups/wireframe technique.  The Photoshop approach allows stakeholders to test the look, but not the feel -- and often leaves developers scratching their heads.  Being a CSS/HTML/Javascript grid-based framework, Bootstrap makes it easy for anyone with a bit of HTML/CSS chops to quickly build slick, interactive prototypes right in the browser -- tangible solutions which can be shared, evaluated, revised, and followed by all stakeholders (see Minimum Viable Products [http://en.wikipedia.org/wiki/Minimum_viable_product]).  Efficiency is multiplied because the customized prototypes can flow directly into production use, as is the goal with iterative development approaches, such as the Agile methodology.&lt;br /&gt;
&lt;br /&gt;
While Bootstrap is not the only framework that offers grid-based layout, development is expedited and usability is enhanced by Bootstraps use of of &amp;quot;prefabbed&amp;quot; conventional UI patterns, clean typography, and lean Javascript for interactivity.   Furthermore, out-of-the box Bootstrap comes in a fairly neutral palette, so focus remains on usability, and does not devolve into premature discussions of color or branding choices.  Finally, using Less can be a powerful tool in conjunction with Bootstrap, but is not necessary.  I will discuss the pros and cons, and offer examples for how to getting up and running with or without Less.&lt;br /&gt;
&lt;br /&gt;
==Search Engine Relevancy Tuning - A Static Rank Framework for Solr/Lucene==&lt;br /&gt;
&lt;br /&gt;
* Mike Schultz, Amazon.com (formerly Summon Search Architect) mike.schultz@gmail.com&lt;br /&gt;
&lt;br /&gt;
Solr/Lucene provides a lot of flexibility for adjusting relevancy scoring and improving search results.  Roughly speaking there are two areas of concern: Firstly, a 'dynamic rank' calculation that is a function of the user query and document text fields.  And secondly, a 'static rank' which is independent of the query and generally is a function of non-text document metadata.  In this talk I will outline an easily understood, hand-tunable static rank system with a minimal number of parameters.&lt;br /&gt;
&lt;br /&gt;
The obvious major feature of a search engine is to return results relevant to a user query.  Perhaps less obvious is the huge role query independent document features play in achieving that. Google's PageRank is an example of a static ranking of web pages based on links and other secret sauce.  In the Summon service, our 800 million documents have features like publication date, document type, citation count and Boolean features like the-article-is-peer-reviewed.  These fields aren't textual and remain 'static' from query to query, but need to influence a document's relevancy score.  In our search results, with all query related features being equal, we'd rather have more recent documents above older ones, Journals above Newspapers, and articles that are peer reviewed above those that are not. The static rank system I will describe achieves this and has the following features:&lt;br /&gt;
&lt;br /&gt;
* Query-time only calculation - nothing is baked into the index - with parameters adjustable at query time.&lt;br /&gt;
* The system is based on a signal metaphor where components are 'wired' together.  System components allow multiplexing, amplifying, summing, tunable band-pass filtering, string-to-value-mapping all with a bare minimum of parameters.&lt;br /&gt;
* An intuitive approach for mixing dynamic and static rank that is more effective than simple adding or multiplying.&lt;br /&gt;
* A way of equating disparate static metadata types that leads to understandable results ordering.&lt;br /&gt;
&lt;br /&gt;
==Submitting Digitized Book-like things to the Internet Archive==&lt;br /&gt;
&lt;br /&gt;
* Joel Richard, Smithsonian Institution Libraries, richardjm@si.edu&lt;br /&gt;
&lt;br /&gt;
The Smithsonian Libraries has submitted thousands of out-of-copyright items to the Internet Archive over the years. Specifically in relation to the Biodiversity Heritage Library, we have developed an in-house boutique scanning and upload process that became a learning experience in automated uploading to the Archive. As part of the software development, we created a whitepaper that details the combined learning experiences of the Smithsonian Libraries and the Missouri Botanical Garden. We will discuss some of the the contents of this whitepaper in the context of our scanning process and the manner in which we upload items to the Archive. &lt;br /&gt;
&lt;br /&gt;
Our talk will include a discussion of the types of files and their formats used by the Archive, processes that the Archive performs on uploaded items, ways of interacting and affecting those processes, potential pitfalls and solutions that you may encounter when uploading, and tools that the Archive provides to help monitor and manage your uploaded documents. &lt;br /&gt;
&lt;br /&gt;
Finally, we'll wrap up with a brief summary of how to use things that are on the Internet Archive in your own websites.&lt;br /&gt;
&lt;br /&gt;
== So... you think you want to Host a Code4Lib National Conference, do you? ==&lt;br /&gt;
&lt;br /&gt;
* Elizabeth Duell, Orbis Cascade Alliance, eduell@uoregon.edu&lt;br /&gt;
&lt;br /&gt;
Are you interested in hosting your own Code4Lib Conference? Do you know what it would take? What does BEO stands for? What does F&amp;amp;B Minimum mean? Who would you talk to for support/mentoring? There are so many things to think about: internet support, venue size, rooming blocks, contracts, dietary restrictions and coffee (can't forget the coffee!) just to name a few. Putting together a conference of any size can look daunting, so let's take the scary out of it and replace it with a can do attitude!&lt;br /&gt;
&lt;br /&gt;
Be a step ahead of the game by learning from the people behind the curtain. Ask questions and be given templates/ cheat sheets! &lt;br /&gt;
&lt;br /&gt;
== HTML5 Microdata and Schema.org ==&lt;br /&gt;
 &lt;br /&gt;
* Jason Ronallo, North Carolina State University Libraries, jason_ronallo@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
When the big search engines announced support for HTML5 microdata and the schema.org vocabularies, the balance of power for semantic markup in HTML shifted. &lt;br /&gt;
* What is microdata? &lt;br /&gt;
* Where does microdata fit with regards to other approaches like RDFa and microformats? &lt;br /&gt;
* Where do libraries stand in the worldview of Schema.org and what can they do about it? &lt;br /&gt;
* How can implementing microdata and schema.org optimize your sites for search engines?&lt;br /&gt;
* What tools are available?&lt;br /&gt;
&lt;br /&gt;
== Stack View: A Library Browsing Tool ==&lt;br /&gt;
 &lt;br /&gt;
* Annie Cain, Harvard Library Innovation Lab, acain@law.harvard.edu&lt;br /&gt;
&lt;br /&gt;
In an effort to recreate and build upon the traditional method of browsing a physical library, we used catalog data, including dimensions and page count, to create a [http://librarylab.law.harvard.edu/projects/stackview/ virtual shelf].&lt;br /&gt;
&lt;br /&gt;
This CSS and JavaScript backed visualization allows items to sit on any number of different shelves, really taking advantage of its digital nature.  See how we built Stack View on top of our data and learn how you can create shelves of your own using our open source code.&lt;br /&gt;
&lt;br /&gt;
== “Linked-Data-Ready” Software for Libraries ==&lt;br /&gt;
&lt;br /&gt;
* Jennifer Bowen, University of Rochester River Campus Libraries, jbowen@library.rochester.edu&lt;br /&gt;
&lt;br /&gt;
Linked data is poised to replace MARC as the basis for the new library bibliographic framework.  For libraries to benefit from linked data, they must learn about it, experiment with it, demonstrate its usefulness, and take a leadership role in its deployment. &lt;br /&gt;
&lt;br /&gt;
The eXtensible Catalog Organization (XCO) offers open-source software for libraries that is “linked-data-ready.” XC software prepares MARC and Dublin Core metadata for exposure to the semantic web, incorporating FRBR Group 1 entities and registered vocabularies for RDA elements and roles. This presentation will include a software demonstration, proposed software architecture for creation and management of linked data, a vision for how libraries can migrate from MARC to linked data, and an update on XCO progress toward linked data goals.&lt;br /&gt;
&lt;br /&gt;
== How people search the library from a single search box ==&lt;br /&gt;
&lt;br /&gt;
* Cory Lown, North Carolina State University Libraries, cory_lown@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Searching the library is complex. There's the catalog, article databases, journal title and database title look-ups, the library website, finding aids, knowledge bases, etc. How would users search if they could get to all of these resources from a single search box? I'll share what we've learned about single search at NCSU Libraries by tracking use of QuickSearch (http://www.lib.ncsu.edu/search/index.php?q=aerospace+engineering), our home-grown unified search application. As part of this talk I will suggest low-cost ways to collect real world use data that can be applied to improve search. I will try to convince you that data collection must be carefully planned and designed to be an effective tool to help you understand what your users are telling you through their behavior. I will talk about how the fragmented library resource environment challenges us to provide useful and understandable search environments. Finally, I will share findings from analyzing millions of user transactions about how people search the library from a production single search box at a large university library.&lt;br /&gt;
&lt;br /&gt;
== An Incremental Approach to Archival Description and Access ==&lt;br /&gt;
&lt;br /&gt;
* Chela Scott Weber, New York University Libraries, chelascott@gmail.com&lt;br /&gt;
* Mark A. Matienzo, Yale University Library, mark@matienzo.org&lt;br /&gt;
&lt;br /&gt;
An ongoing problem for many archives and special collections units is a lack of technological infrastructure and ongoing support. Funding for many archival programs arrives on a project-by-project basis, often in the form of grants. One of the largest concerns for archivist, therefore, is ensuring the sustainability of any solutions or processes that support core operations, such as archival description and access systems.&lt;br /&gt;
&lt;br /&gt;
The presenters will describe their experience developing an iterative and sustainable approach to archival description and access at the library of a small historical society. Starting with mostly OCRed legacy finding aids and no online access to collections, and ending with structured data about the entirety of their holdings available online over three years time, we will detail the evolution of the work from problem-solving through to the resulting phases of descriptive work and development of a basic online access portal created in WordPress. We will discuss making reasonable and sustainable choices in an environment with little monetary and technical support, and how the organization's staff were able to build a system and processes that could leverage messy legacy metadata initially and grow to use structured, standardized data as it was created. We will also discuss the specific technical solutions we developed (the WordPress instance and supporting plugins) and our experience with how bugs and barriers outside of our control changed our insights.&lt;br /&gt;
&lt;br /&gt;
== Making the Easy Things Easy: A Generic ILS API ==&lt;br /&gt;
&lt;br /&gt;
* Wayne Schneider, Hennepin County Library, wschneider@hclib.org&lt;br /&gt;
&lt;br /&gt;
Some stuff we try to do is complicated, because, let's face it, library data is hard. Some stuff, on the other hand, should be easy. Given an item identifier, I should be able to look at item availability. Given a title identifier, I should be able to place a request. And no, I shouldn't have to parse through the NCIP specification or write a SIP client to do it.&lt;br /&gt;
&lt;br /&gt;
This talk will present work we have done on a web services approach to an API for traditional library transactional data, including example applications.&lt;br /&gt;
&lt;br /&gt;
== Your Catalog in Linked Data==&lt;br /&gt;
&lt;br /&gt;
* Tom Johnson, Oregon State University Libraries, thomas.johnson@oregonstate.edu&lt;br /&gt;
&lt;br /&gt;
Linked Library Data activity over the last year has seen bibliographic data sets and vocabularies proliferating from traditional library&lt;br /&gt;
sources. We've reached a point where regular libraries don't have to go it alone to be on the Semantic Web. There is a quickly growing pool of things we can actually ''link to'', and everyone's existing data can be immediately enriched by participating.&lt;br /&gt;
&lt;br /&gt;
This is a quick and dirty road to getting your catalog onto the Linked Data web. The talk  will take you from start to finish, using Free Software tools to establish a namespace, put up a SPARQL endpoint, make a simple data model, convert MARC records to RDF, and link the results to major existing data sets (skipping conveniently over pesky processing time). A small amount of &amp;quot;why linked data?&amp;quot; content will be covered, but the primary goal is to leave you able to reproduce the process and start linking your catalog into the web of data. Appropriate documentation will be on the web.&lt;br /&gt;
&lt;br /&gt;
== Getting the Library into the Learning Management System using Basic LTI == &lt;br /&gt;
&lt;br /&gt;
* David Walker, California State University, dwalker@calstate.edu&lt;br /&gt;
&lt;br /&gt;
The integration of library resources into learning management systems (LMS) has long been something of a holy grail for academic libraries.  The ability to deliver targeted library systems and services to students and faculty directly within their online course would greatly simplify access to library resources.  Yet, the technical barriers to achieving that goal have to date been formidable.  &lt;br /&gt;
&lt;br /&gt;
The recently released Learning Tool Interoperability (LTI) protocol, developed by IMS, now greatly simplifies this process by allowing libraries (and others) to develop and maintain “tools” that function like a native plugin or building block within the LMS, but ultimately live outside of it.  In this presentation, David will provide an overview of Basic LTI, a simplified subset (or profile) of the wider LTI protocol, showing how libraries can use this to easily integrate their external systems into any major LMS.  He’ll showcase the work Cal State has done to do just that.&lt;br /&gt;
&lt;br /&gt;
== Turn your Library Proxy Server into a Honeypot ==&lt;br /&gt;
 &lt;br /&gt;
* Calvin Mah, Simon Fraser University, calvinm@sfu.ca (@calvinmah)&lt;br /&gt;
&lt;br /&gt;
Ezproxy has provided libraries with a useful tool for providing patrons with offsite online access to licensed electronic resources.  This has not gone unnoticed for the unscrupulous users of the Internet who are either unwilling or unable to obtain legitimate access to these materials for themselves.  Instead, they buy or share hacked university computing accounts for unauthorized access.  When undetected, abuse of compromised university accounts can lead to abuse of vendor resources which lead to the blocking of the entire campus block of IP addresses from accessing that resource.&lt;br /&gt;
&lt;br /&gt;
Simon Fraser University Library has been pro actively detecting and thwarting unauthorized attempts through log analysis.  Since SFU has begun analysing our ezproxy logs, the number of new SFU login credentials which are posted and shared in publicly accessible forums has been reduced to zero.   Since our log monitoring began in 2008, the annual average number of SFU login credentials  that are compromised or hacked is 140.  Instead of being a single point of weakness in campus IT security, the library’s proxy server is a honeypot exposing weak passwords, keystroke logging trojans installed on patron PCs and campus network password sniffers.&lt;br /&gt;
&lt;br /&gt;
This talk will discuss techniques such as geomapping login attempts, strategies such as seeding phishing attempts and tools such as statistical log analysis used in detecting compromised login credentials.  &lt;br /&gt;
&lt;br /&gt;
== Relevance Ranking in the Scholarly Domain ==&lt;br /&gt;
&lt;br /&gt;
* Tamar Sadeh, PhD, Ex Libris Group, tamar.sadeh@exlibrisgroup.com&lt;br /&gt;
&lt;br /&gt;
The greatest challenge for discovery systems is how to provide users with the most relevant search results, given the immense landscape of available content. In a manner that is similar to human interaction between two parties, in which each person adjusts to the other in tone, language, and subject matter, discovery systems would ideally be sophisticated and flexible enough to adjust their algorithms to individual users and each user’s information needs. &lt;br /&gt;
&lt;br /&gt;
When evaluating the relevance of an item to a specific user in a specific context, relevance-ranking algorithms need to take into account, in addition to the degree to which the item matches the query, information that is not embodied in the item itself. Such information, which includes the item’s scholarly value, the type of search that the user is conducting (e.g., an exploratory search or a known-item search), and other factors, enables a discovery system to fulfill user expectations that have been shaped by experience with Web search engines.  &lt;br /&gt;
&lt;br /&gt;
The session will focus on the challenges of developing and evaluating relevance-ranking algorithms for the scholarly domain. Examples will be drawn mainly from the relevance-ranking technology deployed by the Ex Libris Primo discovery solution. &lt;br /&gt;
&lt;br /&gt;
== Mobile Library Catalog using Z39.50 ==&lt;br /&gt;
 &lt;br /&gt;
* James Paul Muir, The Ohio State University, muir.29@osu.edu&lt;br /&gt;
&lt;br /&gt;
A talk about putting a new spin on an age-old technology, creating a universal interface, which exposes any Z39.50 capable library catalog as a simple, useful and universal REST API for use in native mobile apps and mobile web.&lt;br /&gt;
&lt;br /&gt;
The talk includes the exploration and demonstration of the Ohio State University’s native app “OSU Mobile” for iOS and Android and shows how the library catalog search was integrated.&lt;br /&gt;
&lt;br /&gt;
The backbone of the project is a REST API, which was created in a weekend using a PHP framework that translates OPAC XML results from the Z39.50 interface into mobile-friendly JSON formatting.&lt;br /&gt;
&lt;br /&gt;
Raw Z39.50 search results contain all MARC information as well as local holdings.  &lt;br /&gt;
Configurable search fields and the ability to select which fields to include in the JSON output make this solution a perfect fit for any Z39.50-capable library catalog.&lt;br /&gt;
  &lt;br /&gt;
Looking forward, possibilities for expansion include the use of Off Campus Sign-In for online resources so mobile patrons can directly access online resources from a smartphone (included in the Android version of OSU Mobile) as well as integration with library patron account.&lt;br /&gt;
&lt;br /&gt;
Enjoy this alternative to writing a custom OPAC adapter or using a 3rd party service for exposing library records and use the proven and universal Z39.50 interface directly against your library catalog. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== DMPTool: Guidance and resources to build a data management plan ==&lt;br /&gt;
 &lt;br /&gt;
* Marisa Strong, California Digital Libary, marisa.strong@ucop.edu&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A number of U.S. funding agencies such as the National Science Foundation require researchers to supply detailed plans for managing research data, called Data Management Plans. To help researchers with this requirement, the California Digital Library (CDL) along with several organizations, collaborated to develop the DMPTool. The goal is to provide researchers with guidance, links to resources and help with writing data management plans.&lt;br /&gt;
&lt;br /&gt;
This open-source, Ruby on Rails software tool is hosted on a SLES VM by CDL. The tool is integrated with Shibboleth, federated single sign-on software, which allows users to login via their home institutions. We had a geographically distributed development team sharing their code on Bitbucket.&lt;br /&gt;
&lt;br /&gt;
This talk will demo features of the application, the Shibboleth login architecture, as well as highlight the agile development practices and methods used to successfully design and build the application on an aggressive schedule.&lt;br /&gt;
&lt;br /&gt;
== Lies, Damned Lies, and Lines of Code Per Day ==&lt;br /&gt;
 &lt;br /&gt;
* James Stuart, Columbia University, james.stuart@columbia.edu&lt;br /&gt;
&lt;br /&gt;
We've all heard about that one study that showed that Pair Programming was 20% efficient than working alone. Or maybe you saw on a blog that study that showed that programmers who write fewer lines of code per day are more efficient...or was it less efficient? And of course, we all know that programmers who work in (Ruby|Python|Java|C|Erlang) have been shown to be more efficient.&lt;br /&gt;
&lt;br /&gt;
A quick examination of some of the research surrounding programming efficiency and methodology, with a focus on personal productivity, and how to incorporate the more believable research into your own team's workflow.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==An Anatomy of a Book Viewer==&lt;br /&gt;
&lt;br /&gt;
*Mohammed Abuouda, Bibliotheca Alexandrina, mohammed.abuouda@bibalex.org&lt;br /&gt;
&lt;br /&gt;
Bibliotheca Alexandria (BA) hosts 210,000 digital books in different languages available at http://dar.bibalex.org. It includes the largest collection of digitized Arabic books. Using open source  tools, BA has developed a modular book viewer that can be deployed in any environment to provide the users with a great personalized reading experience. BA’s book viewer provides several services that make this possible: morphological search in different languages, localization, server load balancing, scalability and image processing. Personalization features includes different types of annotation such as sticky notes, highlighting and underlining. It also provides the ability to embed the viewer in any webpage and change its skin.&lt;br /&gt;
&lt;br /&gt;
In this talk we will describe the book viewer architecture, its modular design and how to incorporate it in your current environment.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Carrier: Digital Signage System ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:jmspargu|Justin Spargur]], The University of Arizona, spargurj@u.library.arizona.edu&lt;br /&gt;
 &lt;br /&gt;
Carrier is a web-based digital signage application written using JavaScript, PHP, MySQL that can be used on any device with an internet connection and a web browser. Used across the University of Arizona Libraries campuses, Carrier can display any web-based content, allowing users to promote new library collections and services via images, web pages, or videos. Users can easily manage the order in which slides are delivered, manage the length that slides are displayed for, set dates for when slides should be shown, and even specify specific locations where slides should be presented. &lt;br /&gt;
 &lt;br /&gt;
In addition to marketing purposes, Carrier can be used to send both low and high priority alerts to patrons. Alerts can be sent through the administrative interface, via RSS feeds, and even through a Twitter feed, allowing for easy integration with existing campus emergency notification systems.&lt;br /&gt;
 &lt;br /&gt;
I will describe the technical underpinnings of Carrier, challenges that we’ve faced since its implementation, enhancements planned for the next release of the software, and discuss our plans for releasing this software for others to use '''for free'''.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== We Built It.  They Came.  Now What? ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:evviva|Evviva Weinraub]], Oregon State University, evviva.weinraub@oregonstate.edu&lt;br /&gt;
 &lt;br /&gt;
You have a great idea for something new or useful.  You build it, put it out there on GitHub, do a couple of presentations, maybe a press release and BAM, suddenly you’ve created a successful Open Source tool that others are using.  Great!&lt;br /&gt;
&lt;br /&gt;
Fast-forward 3 years. &lt;br /&gt;
&lt;br /&gt;
You still believe in the product, but you can no longer be solely responsible for taking care of it.  Just putting it out there has made it a tool others use, but how do you find a community of folks who believe in the product as much as you do and are willing to commit the time and energy into building, sustaining and moving this project forward.  Or just figuring out if you should bother trying?&lt;br /&gt;
&lt;br /&gt;
In 2006, OSU Libraries built an Interactive Course Assignment system called Library a la Carte – think LibGuides only Open Source.  We now find ourselves in just this predicament.  &lt;br /&gt;
&lt;br /&gt;
What can we do as a community to move beyond our build-first-ask-questions-later mentality and embed sustainability into our new and existing ideas and products without moving toward commercialization?  I fully expect we’ll end up with more questions than answers, but let’s spend some talking about our predicament and yours and think about how we can come out the other side. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Contextually Rich Collections Without the Risk: Digital Forensics and Automated Data Triage for Digital Collections ==&lt;br /&gt;
&lt;br /&gt;
* [[User:kamwoods|Kam Woods]], University of North Carolina at Chapel Hill, kamwoods@email.unc.edu&lt;br /&gt;
* Cal Lee, University of North Carolina at Chapel Hill, callee -- at -- ils -- unc -- edu&lt;br /&gt;
&lt;br /&gt;
Digital libraries and archives are increasingly faced with a significant backlog of unprocessed data along with an accelerating stream of incoming material. These data often arrive from donor organizations, institutions, and individuals on hard drives, optical and magnetic disks, flash memory devices, and even complete hardware (traditional desktop computers and mobile systems). &lt;br /&gt;
&lt;br /&gt;
Information on these devices may be sensitive, obscured by operating system arcana, or require specialized tools and procedures to parse. Furthermore, the sheer volume of materials being handled means that even simple tasks such as providing useful content reports can be impractical (or impossible) in current workflows.&lt;br /&gt;
&lt;br /&gt;
Many of the tasks currently associated with data triage and analysis can be simplified and performed with improved coverage and accuracy through the use of open source digital forensics tools. In this talk we will discuss recent developments in providing digital librarians and archivists with simple, open source tools to accomplish these tasks.  We will discuss tools and methods be tested, developed and packaged as part of the [http://bitcurator.net BitCurator] project.  These tools can be used to reduce or eliminate laborious, error-prone tasks in existing workflows and put valuable time back into the hands of digital librarians and archivists -- time better used to identify and tackle complex tasks that *cannot* be solved by software.&lt;br /&gt;
&lt;br /&gt;
== Finding Movies with FRBR and Facets ==&lt;br /&gt;
 &lt;br /&gt;
* Kelley McGrath, University of Oregon, kelleym@uoregon.edu&lt;br /&gt;
&lt;br /&gt;
How might the Functional Requirements for Bibliographic Records (FRBR) model and faceted navigation improve access to film and video in libraries? I will describe the design and implementation of a FRBR-inspired prototype discovery interface ([http://blazing-sunset-24.heroku.com/ http://blazing-sunset-24.heroku.com/]) using Solr and Blacklight . This approach demonstrates how FRBR can enable a work-centric view that is focused on the original movie or program while supporting users in selecting an appropriate version.&lt;br /&gt;
&lt;br /&gt;
The prototype features two sets of facets, which independently address two important information needs: (1) &amp;quot;What kind of movie or program do you want to watch?&amp;quot; (e.g., a 1970s TV sitcom, something directed by Kurosawa, or an early German horror film); (2) &amp;quot;How do you want to watch it? Where do you want to get it from?&amp;quot; (e.g., on Blu-ray, with Spanish subtitles, available at the local public library). This structure enables patrons to narrow, broaden and pivot across facet values instead of limiting them to the tree-structured hierarchy common with existing FRBR applications. &lt;br /&gt;
&lt;br /&gt;
This type of interface requires controlled data values mapped to FRBR group 1 entities, which in many cases are not available in existing MARC bibliographic records. I will discuss ongoing work using the XC Metadata Services Toolkit ([http://www.extensiblecatalog.org/ http://www.extensiblecatalog.org/]) to extract and normalize data from existing MARC records for videos in order to populate a FRBRized, faceted discovery interface.&lt;br /&gt;
&lt;br /&gt;
==Escaping the Black Box — Building a Platform to Foster Collaborative Innovation==&lt;br /&gt;
&lt;br /&gt;
* Karen Coombs, OCLC, coombsk@oclc.org&lt;br /&gt;
* Kathryn Harnish, OCLC harnishk@oclc.org&lt;br /&gt;
&lt;br /&gt;
Exposed Web services offer an unprecedented opportunity for collaborative innovation — that’s one of the hallmarks of Web-based services like Amazon, Google, and Facebook.  These environments are popular not only for their native feature sets, but also for the array of community-developed apps that can run in them.  The creativity of the development communities that work in these systems brings new value to all types of users.&lt;br /&gt;
&lt;br /&gt;
What if the library community could realize this same level of collaborative innovation around its systems?  What kinds of support would be necessary to transform library systems from “black boxes” to more open, accessible environments in which value is created and multiplied by the user community?&lt;br /&gt;
&lt;br /&gt;
In this session, we’ll discuss the challenges and opportunities OCLC faced in creating just that kind of environment.  The recently-released OCLC “cooperative platform” provides improved access to a wide variety of OCLC’s data and services, allowing library developers and other interested partners to collaborate, innovate, and share new solutions with fellow libraries.  We’ll describe the open standards and technologies we’ve put in play in as we:&lt;br /&gt;
* exposed robust Web services that provide access to both data and business logic; &lt;br /&gt;
* created an architecture for integrating community-built applications in OCLC (and other) products; and &lt;br /&gt;
* developed an infrastructure to support community development, collaboration, and app sharing&lt;br /&gt;
&lt;br /&gt;
Learn how OCLC is helping to open the “black box” -- and give libraries the freedom to become true partners in the evolution of their library systems.&lt;br /&gt;
&lt;br /&gt;
== Code inheritance; or, The Ghosts of Perls Past  ==&lt;br /&gt;
&lt;br /&gt;
* Jon Gorman, University of Illinois, jtgorman@illinois.ed&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Any organization has a history not found in its archives or museums. Mysteries exist that origins are lost to the collective institutional knowledge.  Despite what has been forgotten by humans, our servers and computers still keep running. Instructions crafted long ago execute like digital ghosts following orders of masters who have long since left.&lt;br /&gt;
&lt;br /&gt;
The University of Illinois has a fair amount of Perl code created by several different developers. This code includes software that handles our data feeds coming both in and out of campus, reports against our Voyager system, some web applications, and more.&lt;br /&gt;
&lt;br /&gt;
I'll touch a little on the historical legacy and why Perl is used. From there I'll share some tips, best practices, and some of the mistakes I've made in trying to maintain this code. Most of the advice will transition to any language, but code and libraries discussed will be Perl. The presentation will also touch on some internal debate on whether or not to port parts of our Perl codebase.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Recorded Radio/TV broadcasts streamed for library users ==&lt;br /&gt;
&lt;br /&gt;
* Kåre Fiedler Christiansen, The State and University Library Denmark, kfc@statsbiblioteket.dk&lt;br /&gt;
* Mads Villadsen, The State and University Library Denmark, mv@statsbiblioteket.dk&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Provide online access to the Radio/TV collection,&amp;quot; my boss said. About 500,000&lt;br /&gt;
hours of Danish broacast radio and TV. Easy, right? Well, half a year later &lt;br /&gt;
we'd done it, but it turned out to involve practically every it employee in the &lt;br /&gt;
library and quite a few non-technical people as well.&lt;br /&gt;
&lt;br /&gt;
Combining our Fedora-based DOMS repository system with our Lucene-based Summa&lt;br /&gt;
search system with our WAYF-based single-signon system with an upgrade of our&lt;br /&gt;
SAN system for enough speed to deliver the content with an ffmpeg-based &lt;br /&gt;
transcoding workflow system with a Wowza-based streaming server, and sprinkling&lt;br /&gt;
it all with a nice user-friendly web frontend turned out to be quite a challenge,&lt;br /&gt;
but also one of the most engaging experiences for a long time.&lt;br /&gt;
&lt;br /&gt;
Of course we were immidiately shut down, since the legal details weren't quite&lt;br /&gt;
as clear as we thought they were, but take an exclusive preview at &lt;br /&gt;
http://developer.statsbiblioteket.dk/kultur/ - username/password: code4lib.&lt;br /&gt;
&lt;br /&gt;
== NoSQL Bibliographic Records: Implementing a Native FRBR Datastore with Redis ==&lt;br /&gt;
* Jeremy Nelson, Colorado College, jeremy.nelson@coloradocollege.edu&lt;br /&gt;
&lt;br /&gt;
In October, the Library of Congress issued a news release, &amp;quot;A Bibliographic Framework for the Digital Age&amp;quot; outlining a list of requirements for a New Bibliographic Framework Environment. Responding to this challenge, this talk will demonstrate a Redis (http://redis.io) FRBR datastore proof-of-concept that, with a lightweight python-based interface, can meet these requirements. &lt;br /&gt;
&lt;br /&gt;
Because FRBR is an Entity-Relationship model; it is easily implemented as key-value within the primitive data structures provided by Redis.  Redis' flexibility makes it easy to associate arbitrary metadata and vocabularies, like MARC, METS, VRA or MODS, with FRBR entities and inter-operate with legacy and emerging standards and practices like RDA Vocabularies and LinkedData.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Upgrading from Catalog to Discovery Environment: A Consortial Approach ==&lt;br /&gt;
 &lt;br /&gt;
* Spencer Lamm, Swarthmore College, slamm1@swarthmore.edu&lt;br /&gt;
* Chelsea Lobdell, Swarthmore College, clobdel1@swarthmore.edu&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Almost two years ago the Tri-College Consortium of Haverford, Swarthmore, and Bryn Mawr Colleges embarked upon a journey to provide enhanced end-user experience and discoverability with our library applications. Our solution was to implement an integration of ExLibris's Primo Central into Villanova's VuFind for a dual-channel searching experience. We present a case study of the collaborative and technical aspects of our process.&lt;br /&gt;
&lt;br /&gt;
At a high level we will describe our approach to project management and decision making.  We used a multi-tiered structure of working groups with an iterative design-feedback implementation cycle.  We will relay lessons learned from our experience: successes, failures, and unexpected hurdles.&lt;br /&gt;
&lt;br /&gt;
At a lower, technical level we will discuss the vufind search module architecture; the workflow of creating a new search channel; a Primo API parser; and the data structures of the Primo API response and the Primo SearchObject. Time permitting, we will also outline how we modified VuFind's Innovative driver to work with our ILS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Improving geospatial data access for researchers and students ==&lt;br /&gt;
 &lt;br /&gt;
* Dileshni Jayasinghe, Scholars Portal, University of Toronto, d.jayasinghe@utoronto.ca&lt;br /&gt;
* Sepehr Mavedati, Scholars Portal, University of Toronto, sepehr.mavedati@utoronto.ca&lt;br /&gt;
&lt;br /&gt;
Scholars GeoPortal (http://geo.scholarsportal.info) was created as a platform for online delivery of geospatial data resources to the Ontario Council of University Libraries community. Prior to the start of this project, each institution was storing data locally, and had its own practice for distributing datasets to users. This ranged from home grown online data delivery systems to burning data on to DVDs for each individual request. Most institutions had limited resources and expertise to create and maintain a sophisticated delivery system on their own. Led by OCUL Map, GIS librarians, staff at Scholars Portal in partnership with the Government of Ontario, the GeoPortal project began in 2009.&lt;br /&gt;
&lt;br /&gt;
Our talk will focus on the design and architecture of Scholars Portal's solution to support maps and geospatial data, and how we distribute these data collections to our users. &lt;br /&gt;
&lt;br /&gt;
The system consists of 4 main components: metadata management system, map server, spatial database, and the web application.&lt;br /&gt;
&lt;br /&gt;
*Metadata Management: customized metadata editor with data hosted in MarkLogic, providing text and spatial queries&lt;br /&gt;
*Map Server: ArcGIS Server&lt;br /&gt;
*Spatial database: MS SQL Server with spatial extension&lt;br /&gt;
*Web application: Javascript web application using Dojo and Esri’s Javascript API&lt;br /&gt;
 &lt;br /&gt;
For other code4libbers who are interested in a similar system, we will also discuss the open source alternatives for each component (GeoNetwork, MapServer, etc.), and challenges and limitations we faced trying to use some of these tools. We'd also like to pick your brains on how we can make this application better. What can we do differently?&lt;br /&gt;
&lt;br /&gt;
== LibX 2.0 ==&lt;br /&gt;
 &lt;br /&gt;
* Godmar Back, Virginia Tech, godmar@gmail.com&lt;br /&gt;
&lt;br /&gt;
We would like to provide the Code4Lib community with an update on what we've accomplished with LibX (which we last presented in 2009) - where we've gone, what our users are thinking, and how both its technology and its adapter community can be included in the code4lib world. We've grown to our 200,00 users, have a sleek, newly designed user interface, support for Google Chrome. We're now directly consuming many web services. Our Libapp Builders allows anyone to place results, cue, tutorials and other library-related information into pages.&lt;br /&gt;
&lt;br /&gt;
== Introducing the DuraSpace Incubator ==&lt;br /&gt;
&lt;br /&gt;
* Jonathan Markow, DuraSpace, jjmarkow@duraspace.org&lt;br /&gt;
&lt;br /&gt;
DuraSpace is planning to launch a new incubation program for the benefit of open source projects that wish to become part of our organization, in the interest of helping them to become sustainable, community-driven projects and supporting them afterwards with umbrella services that help them to thrive.  From time to time DuraSpace becomes aware of open source software projects in the preservation, archiving, or repository space that are in search of a community “home”.  The motivation might be that the project is simply trying to attract more developers, that it would like to develop a more robust community of users and service providers, that its current organizational sponsorship is in question, or that it would like to take advantage of an existing and compatible organization's best practices and administrative infrastructure rather than create a new one of its own. DuraSpace is now prepared to leverage its resources, experience, and reputation in the community to help these projects become, or continue to be, successful. Projects emerging from incubation will become officially recognized as DuraSpace projects.  This briefing presents highlights of the DuraSpace Incubator and invites questions and feedback from participants.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== In-browser data storage and me ==&lt;br /&gt;
&lt;br /&gt;
* Jason Casden, North Carolina State University Libraries, jason_casden@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
When it comes to storing data in web browsers on a semi-persistent basis, there are several partially-adopted, semi-deprecated, product-specific, or even universally accepted options. These include models such as key-value stores, relational databases, and object stores. I will present some of these options and discuss possible applications of these technologies in library services. In addition to quoting heavily from Mark Pilgrim's excellent chapter on this topic, I will weave in my own experience utilizing in-browser data storage in an iPad-based data collection tool to successfully improve performance and data stability while reducing network dependence. See also: HTML5.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Coding for the past, archiving for the future … and the Salman Rushdie Papers ==&lt;br /&gt;
 &lt;br /&gt;
* Peter Hornsby, Emory University Libraries, phornsb@emory.edu&lt;br /&gt;
&lt;br /&gt;
Cultural heritage production is moving to the digital medium and libraries use of repository solutions such as Fedora Commons and DSpace are a solid response to this change. But how do we go from, for instance a selection of 90's computing technology to  a collection of digital objects ready for ingest into your institution's local repository? Once you have ingested your digital objects how are you going to provide access to these resources? The arrival of the Salman Rushdie Papers, which contain 10 years of Sir Salman Rushdie's digital life, gave Emory University Libraries the opportunity to explore these questions. I would like to to talk about the approach the Emory University Libraries adopted, what we learned and the coding challenges that remain.&lt;br /&gt;
&lt;br /&gt;
==  Indexing big data with Tika, Solr &amp;amp; map-reduce ==&lt;br /&gt;
&lt;br /&gt;
* Scott Fisher, California Digital Library, scott.fisher AT ucop BORK edu&lt;br /&gt;
* Erik Hetzner, California Digital Library, erik.hetzner AT ucop BORK edu&lt;br /&gt;
&lt;br /&gt;
The Web Archiving Service at the California Digital Library has&lt;br /&gt;
crawled a large amount of data, in every format found on the web: 30&lt;br /&gt;
TB, comprising about 600 million fetched URLs. In this talk we will&lt;br /&gt;
discuss how we parsed this data using Tika and map-reduce, and how we&lt;br /&gt;
indexed this data with Solr, tweaked the relevance ranking, and were&lt;br /&gt;
able to provide our users with a better search experience.&lt;br /&gt;
&lt;br /&gt;
== ALL TEH METADATAS! or How we use RDF to keep all of the digital object metadata formats thrown at us. ==&lt;br /&gt;
&lt;br /&gt;
* Declan Fleming, University of California, San Diego, dfleming AT ucsd DING edu&lt;br /&gt;
&lt;br /&gt;
What's the right metadata standard to use for a digital repository?  There isn't just one standard that fits documents, videos, newspapers, audio files, local data, etc.  And there is no standard to rule them all.  So what do you do?  At UC San Diego Libraries, we went down a conceptual level and attempted to hold every piece of metadata and give each holding place some context, hopefully in a common namespace.  RDF has proven to be the ideal solution, and allows us to work with MODS, PREMIS, MIX, and just about anything else we've tried.  It also opens up the potential for data re-use and authority control as other metadata owners start thinking about and expressing their data in the same way.  I'll talk about our workflow which takes metadata from a stew of various sources (CSV dumps, spreadsheet data of varying richness, MARC data, and MODS data), normalizes them into METS by our Metadata Specialists who create an assembly plan, and then ingests them into our digital asset management system.  The result is a [http://dl.dropbox.com/u/6923768/Work/DAMS%20object%20rdf%20graph.png beautiful graph] of RDF triples with metadata poised to be expressed as [https://libraries.ucsd.edu/digital/ HTML], RSS, METS, XML, and opens linked data possibilities that we are just starting to explore.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== HathiTrust Large Scale Search: Scalability meets Usability ==&lt;br /&gt;
&lt;br /&gt;
* Tom Burton-West, DLPS, University of Michigan Library, tburtonw AT umich edu&lt;br /&gt;
&lt;br /&gt;
[http://www.hathitrust.org/ HathiTrust Large-Scale search] provides full-text search services over  nearly 10 million full-text books using Solr for the back-end.  Our index is around 5-6 TB in size and each shard contains over 3 billion unique terms due to content in over 400 languages and dirty OCR.&lt;br /&gt;
&lt;br /&gt;
Searching the full-text of 10 million books often results in very large result sets.  By conference time a number of [http://www.hathitrust.org/full-text-search-features-and-analysis features] designed to help users narrow down large result sets and to do exploratory searching will either be in production or in preparation for release. There are often trade-offs between implementing desirable user features and keeping response time reasonable in addition to the traditional search trade-offs of precision versus recall.  &lt;br /&gt;
&lt;br /&gt;
We will discuss various [http://www.hathitrust.org/blogs/large-scale-search scalability] and usability issues including:&lt;br /&gt;
* Trade-offs between desirable user features and keeping response time reasonable and scalable &lt;br /&gt;
* Our solution to providing the ability to search within the 10 million books and also search within each book&lt;br /&gt;
* Migrating the [http://babel.hathitrust.org/cgi/mb personal collection builder application] from a separate Solr instance to an app which uses the same back-end as full-text search.&lt;br /&gt;
* Design of a scalable multilingual spelling suggester&lt;br /&gt;
* Providing advanced search features combining MARC metadata with OCR&lt;br /&gt;
** The dismax mm and tie parameters&lt;br /&gt;
** Weighting issues and tuning relevance ranking&lt;br /&gt;
* Displaying  only the most &amp;quot;relevant&amp;quot; facets&lt;br /&gt;
* Tuning relevance ranking &lt;br /&gt;
* Dirty OCR issues&lt;br /&gt;
* CJK tokenizing and other multilingual issues.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== DMPTool: Guidance and resources to build a data management plan ==&lt;br /&gt;
Marisa Strong, California Digital Libary, marisa.strong@ucop.edu&lt;br /&gt;
&lt;br /&gt;
A number of U.S. funding agencies such as the National Science Foundation require researchers to supply detailed plans for managing research data, called Data Management Plans. To help researchers with this requirement, the California Digital Library (CDL) along with several organizations, collaborated to develop the DMPTool. The goal is to provide researchers with guidance, links to resources and help with writing data management plans.&lt;br /&gt;
This open-source, Ruby on Rails software tool is hosted on a SLES VM by CDL. The tool is integrated with Shibboleth, federated single sign-on software, which allows users to login via their home institutions. We had a geographically distributed development team sharing their code on Bitbucket.&lt;br /&gt;
This talk will demo features of the application, the Shibboleth login architecture, as well as highlight the agile development practices and methods used to successfully design and build the application on an aggressive schedule.&lt;br /&gt;
&lt;br /&gt;
== The Islandora Open Source Framework for Digital Asset Management ==&lt;br /&gt;
&lt;br /&gt;
* Keith Folsom, Orbis Cascade Alliance, kfolsom@uoregon.edu&lt;br /&gt;
&lt;br /&gt;
Managing digital content is a challenging task—becoming even more so &lt;br /&gt;
as the volumes and types of content increase at what seems an exponential &lt;br /&gt;
rate.  Though there are good commercial management systems available, &lt;br /&gt;
having competing and potentially more configurable open source options is ideal.  &lt;br /&gt;
One such option is Islandora—an open source framework that wraps a Drupal &lt;br /&gt;
front-end around the Fedora digital object management and storage system.  &lt;br /&gt;
&lt;br /&gt;
My talk will serve as an introduction to the Islandora framework—including a&lt;br /&gt;
discussion of Fedora’s digital object model and content model architecture; &lt;br /&gt;
how Islandora exposes the power of Fedora for storage, discovery, and retrieval &lt;br /&gt;
of data; and the wide variety of underlying open source software and technology &lt;br /&gt;
that enables the system.   I will also give a quick tour of a stock Islandora &lt;br /&gt;
installation and provide tips on navigating the documentation for set-up and &lt;br /&gt;
use of this powerful framework.&lt;br /&gt;
&lt;br /&gt;
== What do the NISO IOTA OpenURL quality reports tell us about the future of OpenURL linking? ==&lt;br /&gt;
&lt;br /&gt;
* Adam Chandler, Cornell University, alc28@cornell.edu&lt;br /&gt;
&lt;br /&gt;
NISO IOTA (http://openurlquality.niso.org/) is an initiative that makes use of log files from various institutions and vendors to analyze element frequency and patterns contained within OpenURL requests.  The reports created from this analysis inform vendors about where to make improvements to their OpenURLs.  In this talk, the chair of the IOTA working group will share what the group has learned about the differences in quality across OpenURL sources.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;quot;CALIL.JP&amp;quot; Open Libraries by web-scraping. - Introducing Library API from Japan ==&lt;br /&gt;
&lt;br /&gt;
* Ryuuji Yoshimoto, Nota Inc. Engineer, ryuuji@notaland.com&lt;br /&gt;
&lt;br /&gt;
I am an engineer at Nota Inc., a start-up company for web services. &amp;quot;CALIL&amp;quot; (http://calil.jp/) is a web service for library users in Japan. (Not only for librarians but also for general patrons.)&lt;br /&gt;
&lt;br /&gt;
CALIL allows users search books from multiple libraries nearby, and get realtime holding status. Our service supports over 5,800 libraries. &lt;br /&gt;
CALIL supports public, university, and other many special libraries in Japan. The service can search 88% of collections of all public libraries in Japan.&lt;br /&gt;
Public libraries in Japan do not have an unified catalogue like OCLC.&lt;br /&gt;
Web OPACs in Japan are generally very slow and their usability is low. &lt;br /&gt;
We develop a comprehensive scraping service over 2000 web OPACs and it supports recognize real-time holding status on them as well.&lt;br /&gt;
This service can be used as for substitution of OPACs provided by libraries. It provides more useful, speedy and open service.&lt;br /&gt;
&lt;br /&gt;
Our scraping platform also provides API for free.&lt;br /&gt;
Any developer can access realtime holding status at almost all the libraries in Japan by one API.&lt;br /&gt;
Since the launch in 2010, many apps on iPhone and Android are developed by many third party developers.&lt;br /&gt;
And it allows many web service connect to library (book shelf, review etc).&lt;br /&gt;
&lt;br /&gt;
CALIL is written by 100% pure Python and running on Google App Engine.&lt;br /&gt;
&lt;br /&gt;
I will introduce about &amp;quot;CALIL&amp;quot;, &amp;quot;CALIL Library API&amp;quot;, and its methodology. Open Libraries in Japan to World-Coders!!&lt;br /&gt;
&lt;br /&gt;
== Discovering Digital Library User Behavior with Google Analytics==&lt;br /&gt;
&lt;br /&gt;
* Kirk Hess, Digital Humanities Specialist, University of Illinois Urbana-Champaign, kirkhess@illinois.edu&lt;br /&gt;
&lt;br /&gt;
Digital library administrators are frequently asked questions like &amp;quot;How many times was that document downloaded&amp;quot;, or &amp;quot;What’s the most popular book in our collection?&amp;quot; Conventional web logging software, such as AWStats, can only answer those questions some of the time, and there’s always the question of whether or not the data is polluted by non-users, such as spiders and crawlers. Google Analytics, (http://google.com/analytics/ ) , a JavaScript-based solution that excludes most crawlers and bots, shows how users found your site and how they explored it.&lt;br /&gt;
 &lt;br /&gt;
The presentation will review tracking search queries, adding events such as clicking external links or downloading files, and custom variables, to track user behavior that is normally difficult to track. We'll also discuss using jQuery scripts to add tracking code to the page without having to modify the underlying web application. Once you've collected data, you may use the Google Analytics API to extract data and integrate it with data from your digital repository to show granular data about individual items in your Digital Library. Finally, we'll discuss how this information allows you to improve the user experience, and summarize some of the research we are doing with our digital repository and the data gathered from Google Analytics.&lt;br /&gt;
&lt;br /&gt;
== Introducing Kuali OLE 0.3==&lt;br /&gt;
&lt;br /&gt;
* Rich Slabach, Quality Assurance Manager, Kuali OLE, rlslabac at indiana dot edu&lt;br /&gt;
* Nianli Ma, Technical Architect, Kuali OLE, Indiana University, nianma at indiana dot edu&lt;br /&gt;
&lt;br /&gt;
This research update will feature technical staff from the Kuali Open Library Environment (OLE) project, which is in its second year of building a community-source library management environment. Operating since July 2010, and supported by The Andrew W. Mellon Foundation, Kuali OLE is the one of the largest academic library software collaborations in the United States. In this presentation we will discuss the Kuali OLE Year 2 Roadmap as well as key components of the system architecture, additionally we will demonstrate our Kuali OLE 0.3 release from November 2011 with our cloud-based test drive implementation and our well documented driver's manual. This will lead to a better understanding of how this code base could support library management at your home institution.&lt;br /&gt;
 &lt;br /&gt;
We will also discuss opportunities for engagement with Kuali OLE and for adoption and use of the software as well as hear more about our plans for long-term sustainability. For more on our current software see - https://wiki.kuali.org/display/OLE/OLE+and+Docstore+Server+Installation&lt;br /&gt;
&lt;br /&gt;
== UDFR: Building a Registry using Open-Source Semantic Software ==&lt;br /&gt;
&lt;br /&gt;
* Stephen Abrams, Associate Director, UC3, California Digital Library, stephen.abrams AT ucop DING edu&lt;br /&gt;
* Lisa Dawn Colvin, UDFR Project Manager, California Digital Library, lisa.colvin AT ucop DING edu&lt;br /&gt;
&lt;br /&gt;
Fundamental to effective long-term preservation analysis, planning, and intervention is the deep understanding of the diverse digital formats used to represent content. The Unified Digital Format Registry project (UDFR, https://bitbucket.org/udfr/main/wiki/Home) will provide an open source platform for an online, semantically-enabled registry of significant format representation information.&lt;br /&gt;
&lt;br /&gt;
We will give an introduction to the UDFR tool and its use within a preservation process.&lt;br /&gt;
&lt;br /&gt;
We will also discuss our experiences of integrating disparate data sources and models into RDF: describing our iterative data modeling process and decisions around integrating vocabularies, data sources and provenance representation. &lt;br /&gt;
&lt;br /&gt;
Finally, we will share how we extended an existing open-source semantic wiki tool, OntoWiki, to create the registry.&lt;br /&gt;
&lt;br /&gt;
== Sirsi Symphony: Developing a &amp;quot;web service&amp;quot; to provide real time bibliographic information to Blacklight. ==&lt;br /&gt;
&lt;br /&gt;
* John Pillans, Enterprise Software, Library Systems, Configuration Manager Kuali OLE, Indiana University, jpillan@indiana.edu&lt;br /&gt;
&lt;br /&gt;
Indiana University Libraries is currently in the process of implementing Blacklight as its discovery layer on top of Sirsi Symphony.  One aspect of Blacklight that must be developed locally is providing circulation status and holdings information to the user.  We have developed a &amp;quot;web service&amp;quot; which provides the bibliographic data, formatted MARC holdings data (if present), and item data with current circulation information to the Blacklight system in XML.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Open Sourcing the Dream: Making the Read/Write Library ==&lt;br /&gt;
 &lt;br /&gt;
* Margaret Heller, Read/Write Library Chicago and Dominican University, mheller@dom.edu&lt;br /&gt;
&lt;br /&gt;
You met the Chicago Underground Library last year, now meet The Read/Write Library Chicago.It's a new name, a new space, and new opportunities to develop our catalog. We are working on creating the open source version of our ideas with a distributed team of interested volunteers, plus experimenting with innovative partnerships with the Chicago technology community. This talk will share what the team and open source project look like, what we are doing with our data, and how we finally learned to stop worrying and love Git. &lt;br /&gt;
&lt;br /&gt;
== Interactive maps: an easy-to-maintain and scalable approach ==&lt;br /&gt;
 &lt;br /&gt;
* Mariela Gunn, Oakland University, gunn@oakland.edu&lt;br /&gt;
&lt;br /&gt;
Developing interactive maps of a library building presents a unique challenge in an institution with limited web services personnel. Our technical expectations are high: we want the maps to have engaging interactivity, to be modular so we can link to different services represented in them, and to be scalable so that we can integrate data-driven elements. Our content needs are ever changing: we want to have distributed authorship of content through a user-friendly interface that can be used by all librarians without a steep learning curve.&lt;br /&gt;
&lt;br /&gt;
This talk will focus on the design of interactive maps by a group of our undergraduate student interns who selected a web application -- Maps Alive -- for the task with ease of use and scalability in mind and set up a structure that can grow and change. The pros and cons of the application will be discussed, as well as tips on how to evaluate potential tools and make the best use of them through a modular and flexible approach to interactive maps. Involving students as designers and decision-makers in technology-related projects will be highlighted too.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Getting the Content out of CONTENTdm: Building a Modular UI Template for Digital Collections  ==&lt;br /&gt;
 &lt;br /&gt;
* Devin Becker, University of Idaho, dbecker@uidaho.edu&lt;br /&gt;
&lt;br /&gt;
With the advent of iterations 6 and 6.1, CONTENTdm redesigned the basic user interfaces for individual collections, improving on what was already a robust and reliable system for archiving and displaying digital items. The majority of the items in these collections, however, still rarely see the light of a user's screen. Moreover, the typical modes for browsing these collections within the system are geared primarily to those who are already familiar with such systems or who have a specific need to see certain items.  &lt;br /&gt;
&lt;br /&gt;
To invite more casual browsing and easier discovery of our collections, the University of Idaho Library's Digital Initiatives department designed a scalable and modular interface for all of our collections with an increased emphasis on the time, location, and larger display of our images and other digital items. To do so, we used free and easy-to-use Javascript libraries and online applications (including Jquery, Google Fusion Tables, Simile Timeline, ImageFlow, and Tagcrowd.com), together with several, simple XSL stylesheets that utilize the metadata and persistent linking capabilities of the CONTENTdm database, to design a basic template with several browsing options (timeline, map, tag cloud, etc.) that can be used for any collection. This talk will detail the coding, methods, and metadata implemented for the redesign.&lt;br /&gt;
&lt;br /&gt;
== saveMLAK: How Librarians, Curators, Archivists and Library Engineers Work Together with Semantic MediaWiki after the Great Earthquake of Japan ==&lt;br /&gt;
&lt;br /&gt;
* Yuka Egusa, Senior Researcher of National Institute of Educational Policy Research, yuka_at_nier.go.jp&lt;br /&gt;
* Makoto Okamoto, Chief Editor of Academic Resource Guide (ARG), arg.editor_at_gmail.com&lt;br /&gt;
&lt;br /&gt;
In March 11th 2011, the biggest earthquake and tsunami in the history attacked a large area of northern east region of Japan. A lot of people have worked together to save people in the area. For library community, a wiki named &amp;quot;savelibrary&amp;quot; was launched for sharing information on damages and rescues on the next day of the earthquake. Later then people from museum curators, archivists and community learning centers started similar projects. In April we joined to a project &amp;quot;saveMLAK&amp;quot;, and launched a wiki site using Semantic MediaWiki under http://savemlak.jp/.&lt;br /&gt;
&lt;br /&gt;
As of November 2011, information on over 13,000 cultural organizations are posted on the site by 269 contributors since the launch. The gathered information are organized along with Wiki categories of each type of facilities such library, museum, school, etc. We have held eight edit-a-thons to encourage people to contribute to the wiki.&lt;br /&gt;
&lt;br /&gt;
We will report our activity, how the libraries and museums were damaged and have been recovered with lots of efforts, and how we can do a new style of collaboration with MLAK community, Wiki and other voluntary communities at the crisis.&lt;br /&gt;
&lt;br /&gt;
== Kill the search button II - the handheld devices are coming ==&lt;br /&gt;
&lt;br /&gt;
* Jørn Thøgersen, Statsbiblioteket/State and University Library, Aarhus, Denmark. jt@statsbiblioteket.dk&lt;br /&gt;
* Michael Poltorak Nielsen, Statsbiblioteket/State and University Library, Aarhus, Denmark. mn@statsbiblioteket.dk, (aka the Danes - some of them).&lt;br /&gt;
&lt;br /&gt;
Web based library search engines are traditionally operated using keys, input fields, buttons, and links. Being equipped with touch screens, accelerometers, GPS's, and cameras, smartphones and tablets offer a whole new range of input options.&lt;br /&gt;
&lt;br /&gt;
In this talk we'll demonstrate some of our ideas of how to&lt;br /&gt;
utilise these new input options interacting with a search engine. The basic idea is to have no traditional GUI input elements, but only use touch interactions (pinch, zoom, swipe, long-press, etc) and gestures (shake, tilt, turn, etc.). Using these interactions, we’ll demonstrate how to:&lt;br /&gt;
&lt;br /&gt;
* do searches&lt;br /&gt;
* toggle search result views&lt;br /&gt;
* switch pages&lt;br /&gt;
* request materials, add to favourites&lt;br /&gt;
* interact with your stuff, renew items &lt;br /&gt;
&lt;br /&gt;
We'll also show you some (conceptual) ideas about using the device camera for locating and checking out materials.&lt;br /&gt;
&lt;br /&gt;
On a general level, what we are trying to achieve is a move away from a web based paradigm and establish new ways of interaction better suited to the new devices and on their own terms. The demonstration will feature working mobile prototypes including both native apps (iPhone) and web apps. In both cases they will run on live data from our OPAC on www.statsbiblioteket.dk/search/&lt;br /&gt;
&lt;br /&gt;
This talk is actually also a continuation of our Code4Lib 2010 talk called &amp;quot;Kill The Search Button&amp;quot; (http://code4lib.org/conference/2010/schedule), which we unfortunately never got around to do, due to a Danish blizzard.&lt;br /&gt;
&lt;br /&gt;
==Speaking in code: talking tech with humans (and librarians)==&lt;br /&gt;
* Erin White, Virginia Commonwealth University Libraries, erwhite@vcu.edu&lt;br /&gt;
&lt;br /&gt;
We do awesome work, right? But what's the best way to communicate that work with non-geek stakeholders within our organizations? I'll present some ideas on how to communicate tech with those who don't always speak the language fluently. This'll include pitching new projects; communicating about existing projects; and dealing with project maintenance and problem-solving. I'll share some tips for explaining systems changes and problems, how to use help tickets as teachable moments for you or librarians, updating documentation, etc.&lt;br /&gt;
&lt;br /&gt;
== Building a Code4Lib 2012 Conference Mobile App with the Kuali Mobility Framework ==&lt;br /&gt;
&lt;br /&gt;
* Michelle Suranofsky, Lehigh University, michelle dot suranofsky at lehigh dot edu&lt;br /&gt;
* Tod Olson, University of Chicago, tod at uchicago dot edu&lt;br /&gt;
&lt;br /&gt;
Hot off the heals of the Kuali Days 2011 Conference, we thought it would be fun to take the newly released Kuali Mobility for Enterprise framework for a test drive by creating a Code4Lib Conference Mobile App.  &lt;br /&gt;
&lt;br /&gt;
[http://kuali.org/mobility Kuali Mobility for Enterprise (KME)] is an open source framework for developing and deploying applications to connect mobile devices to an institution's information resources.  Applications may be deployed as mobile websites or as installable apps.  The KME framework makes heavy use of HTML5, CSS, and Javascript, and builds on other open source projects like PhoneGap and JQuery Mobile.  &lt;br /&gt;
&lt;br /&gt;
We will discuss the mechanics of the Kuali Mobility framework along with the experience using it to create a mobile app. for the Code4Lib conference.&lt;br /&gt;
&lt;br /&gt;
== The ARCHIVEMATICA digital preservation system ==&lt;br /&gt;
 &lt;br /&gt;
* Peter Van Garderen, Archivematica Project Manager, [http://artefactual.com Artefactual Systems], peter at artefactual dot com&lt;br /&gt;
* Courtney Mumma, Archivematica Community Manager, courtney at artefactual dot com&lt;br /&gt;
&lt;br /&gt;
The open source (AGPL3) [http://archivematica.org Archivematica] digital preservation system uses a micro-services architecture to integrate a suite of Linux utilities into workflow pipelines. It is designed as a backend tool for archivists and librarians managing digital collections and digital preservation responsibilities. We use Google Gearman for job scheduling and load balancing as well as Django (python) for a web-based administration interface that monitors and controls the processing of files in the pipelines. The system creates standards-compliant (e.g. METS, PREMIS, Bagit) archival packages as well as a registry interface to monitor format policies. This system is designed to provide the technical component for ISO 14721 (OAIS) and ISO 16363 (TRAC) compliant Trusthworthy Digital Repositories. The recent 0.8 release is the last alpha. Over winter 2012 we are continuing with scalability testing and tuning, adding ElasticSearch indexing, SWORD deposit support, interfaces for Dspace, ContentDM, XTF; all for inclusion in the 0.9-beta release sometime in Spring 2012. The presentation will give a quick demo of Archivematica's features as well as discuss technical architecture, APIs, development roadmap, user base, community building, project management, etc.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Virtual Integrated Search - on-the-fly merging of relevancy ranked searches ==&lt;br /&gt;
&lt;br /&gt;
* Mads Villadsen, The State and University Library Denmark, mv@statsbiblioteket.dk&lt;br /&gt;
&lt;br /&gt;
What do you do when you have an integrated search system and the users want data at the article level? What we did was to try and get the data from the publishers - and when that failed we went with Summon for the article data while keeping our bibliographic records (and more) in our own system.&lt;br /&gt;
&lt;br /&gt;
So how’s that working out for us?&lt;br /&gt;
&lt;br /&gt;
We didn’t want to give up on our overall goal of having a single unified result set which meant we had to do something out of the ordinary.&lt;br /&gt;
&lt;br /&gt;
We struck a deal with Serials Solutions that allowed us to apply our technical know-how and sprinkle fairy dust on our queries thereby achieving a proper relevancy ranked merging of results from our own index with the results from Summon. We gave a lightning talk about some of these ideas at last year's code4lib.&lt;br /&gt;
&lt;br /&gt;
We have been running this &amp;quot;Virtual Integrated Search&amp;quot; in production since August and the end users haven't come at us with their pitch forks yet so we assume they are still able to find what they are looking for.&lt;br /&gt;
&lt;br /&gt;
Just to be sure we will be performing a usability test in November 2011 that will hopefully guide our future development.&lt;br /&gt;
&lt;br /&gt;
I will cover what goes into making fairy dust (&amp;quot;how it works&amp;quot;, &amp;quot;what doesn't work&amp;quot;) as well as some of the results from the usability test (&amp;quot;does it actually work?&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
http://www.statsbiblioteket.dk/search/&lt;br /&gt;
&lt;br /&gt;
== Kuali Rice and preparing for OLE ==&lt;br /&gt;
&lt;br /&gt;
* Tod Olson, University of Chicago, tod at uchicago dot edu&lt;br /&gt;
* Michelle Suranofsky, Lehigh University, michelle dot suranofsky at lehigh dot edu&lt;br /&gt;
&lt;br /&gt;
Kuali Rice provides some of the fundamental underlying services  for Kuali OLE and other Kuali software, services such as workflows, a service bus, integration with campus identity management, and more. In preparation for OLE, some partner libraries are developing their own simple Rice-base applications to provide some useful automation now while gaining experience that will prepare us for running Rice as part of OLE. This talk will give a brief overview of Kuali Rice and then discuss the construction of a real-but-simple Rice application.&lt;br /&gt;
&lt;br /&gt;
== Argo and DOR Services: The developer and administrative interfaces to Stanford's Digital Object Registry ==&lt;br /&gt;
&lt;br /&gt;
* Michael B. Klein, Library Infrastructure Engineer, Stanford University Libraries, mbklein at stanford dot edu&lt;br /&gt;
&lt;br /&gt;
Argo is the administrative interface for Stanford's Digital Object Registry (DOR), the central repository of information about digital assets owned or managed by Stanford University Libraries and Academic Information Resources (SULAIR). Built on Blacklight, with help from other pieces of the Hydra repository framework, Argo provides a top-down, source-independent, application-agnostic view of items working their way through various stages of registration, submission, description, digitization, accessioning, publication, shelving, and preservation.&lt;br /&gt;
&lt;br /&gt;
Argo's functionality is provided through three separate layers:&lt;br /&gt;
&lt;br /&gt;
* A traditional web application, which provides UI-based bulk and individual item registration, management, and reporting functions&lt;br /&gt;
* A web service, which provides RESTful access to several of the same functions&lt;br /&gt;
* A DOR services Ruby gem which opens most of this functionality to other Ruby code, from Rails applications to accessioning daemons to one-off scripts&lt;br /&gt;
&lt;br /&gt;
This presentation will explore Argo's full stack, from the underlying DOR Services gem (encapsulating a number of other disparate library infrastructure functions) to its use by SULAIR developers, contractors, digitization lab staff, project managers, and SULAIR technical staff.&lt;br /&gt;
   &lt;br /&gt;
&lt;br /&gt;
== The Way to Bulid C4L Activities in Your Homeland - Based on the Experience of Code4Lib JAPAN. ==&lt;br /&gt;
&lt;br /&gt;
* Makoto Okamoto, Chief Editor of Academic Resource Guide (ARG) and Executive Officer of Code4Lib JAPAN, arg.editor_at_gmail.com &lt;br /&gt;
&lt;br /&gt;
In August 2010, We launched the &amp;quot;Code4Lib JAPAN&amp;quot;, a kind of local activities of Code4Lib in JAPAN after preparation for 6 months. Since then, Code4Lib JAPAN did a great sucess and growth. Approximately, activities of Code4Lib JAPAN are divided into 4 parts like operation of orgnization and activities, offer training program, proposing some guidelines, dispatching a mission to Code4Lib Conference and selection of good practice.&lt;br /&gt;
&lt;br /&gt;
In this presentation, some key facters of our sucess and growth will be explained by Executive Officer of Code4Lib JAPAN. Those key facters like getting money from outside grant, indutrial sponsers and personal supporters, operation of orgnization and activities on a self-supporting basis will be very helpful for those who are wishing to launch local activitiy in their homeland. We can offer variuus tiips to spread value and activities of Code4Lib in the world.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Golden Road (To Unlimited Devotion): Building a Socially Constructed Archive of Grateful Dead Artifacts ==&lt;br /&gt;
&lt;br /&gt;
* Robin Chandler, University of California (Santa Cruz), chandler [at] ucsc [dot] edu&lt;br /&gt;
* Susan Chesley Perry, University of California (Santa Cruz), chesley [at] ucsc [dot] edu&lt;br /&gt;
* Kevin S. Clarke, University of California (Santa Cruz), ksclarke [at] ucsc [dot] edu&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Grateful Dead Archive at the University of California (Santa Cruz) is a collection of over 600 linear feet of material, including: business records, photographs, posters, fan envelopes, tickets, video, audio (oral histories, interviews and music) and 3-d objects such as stage props and band merchandise.  In addition, with the release of the ''Grateful Dead Archive Online'' website in 2012, the Archive will start actively collecting artifacts from an enthusiastic community of Grateful Dead fans.&lt;br /&gt;
&lt;br /&gt;
This talk will discuss the challenges of merging a traditional archive with a socially constructed one.  We will also present the first round of development and explain how we're using tools like Omeka, ContentDM, UC3 Merritt, djatoka, Kaltura, Google Maps, and Solr to lay the foundation for a robust and engaging site.  Future directions, like the integration/development of better curation tools and what we hope to learn from opening the archive to contributions from a large community of fans, will also be discussed.&lt;br /&gt;
&lt;br /&gt;
== Library News - A gathering place for library and tech news, and more ==&lt;br /&gt;
&lt;br /&gt;
* Matt Phillips, Harvard Library Innovation Lab, mphillips@law.harvard.edu&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://news.librarycloud.org Library News] is gathering place for people to share and discuss news from the technology and library worlds. Think [http://news.ycombinator.com Hacker News], but for library dorks instead of startup dorks.&lt;br /&gt;
&lt;br /&gt;
Library News is more than a news and discussion site, it analyzes submitted links and shares its observations. One example of this sharing is the exposure of popular blogs: Library News tracks submitted blog entries and tallies them up, creating a list of most popular blogs in the community. This most popular list is exposed as an HTML document and as an [http://en.wikipedia.org/wiki/OPML OPML] download (The OPML file can be loaded directly into an RSS reader and be used as an always up-to-date &amp;quot;starter pack&amp;quot; of popular blogs in the library and tech spaces). &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
My rough talk outline:&lt;br /&gt;
* Demo Library News&lt;br /&gt;
* Present how Library News goes beyond normal discussion sites (the tools that allow to explore community submitted links)&lt;br /&gt;
* Discuss where Library News fits with the current library news ecosystem&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Find more information about Library News at the [http://news.librarycloud.org/faq Library News FAQ]&lt;br /&gt;
&lt;br /&gt;
== Data-Mining Repository Contents to Auto-populate Scholarly Research Repository Submission Metadata ==&lt;br /&gt;
* Mark Diggory, Head of U.S. Operations&lt;br /&gt;
&lt;br /&gt;
The existing body of Open Access scholarly research is a well classified and described dataset.  However, in Institutional Repositories it can be the case that there are insufficient resources to invest for cataloging and maintaining rich metadata descriptions of contributed content. This is especially the case when collections are populated and maintained by non-librarians.  A great deal of classifiable detail preexists within files that are submitted to scholarly repositories.  Utilizing existing Open Source technologies capable of extracting this information, a process can be provided to submitters and repository maintainers to suggest appropriate subject classifications and types for descriptive metadata during submission and update of repository items.  This talk will provide an overview of an approach for utilizing machine learning as a tool for the auto population of subject classifications and content types.&lt;br /&gt;
&lt;br /&gt;
== Mining Wikipedia for Book Articles ==&lt;br /&gt;
* Paul Deschner, Harvard Library Innovation Lab, deschner@law.harvard.edu&lt;br /&gt;
&lt;br /&gt;
Suppose you were developing a browsing tool for library materials and wanted to include Wikipedia articles and categories whenever available -- how would you do it?  There is no API or other data service which one can use to get a comprehensive listing of every page in Wikipedia devoted to the discussion of a book.  &lt;br /&gt;
&lt;br /&gt;
This talk will focus on the tools, workflows and data sources we have used to approach this problem.  Tools and workflows include the use of Infobox ISBN's and other standard identifiers, analysis of Wikipedia categories and category hierarchies, exploitation of article abstracts and titles, and Mechanical Turk resources.  Data sources include Dbpedia triple stores and Wikimedia XML/SQL dumps.  So far, we have harvested around 60,000 book articles.  This is an exploration in dealing with open, relatively unstructured Web content, and in aggregating answers to the same question using quite diverse techniques.&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_preconference_proposals&amp;diff=9902</id>
		<title>2012 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_preconference_proposals&amp;diff=9902"/>
				<updated>2011-11-21T14:10:26Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Proposals for 2012 Code4LibCon Preconferences=&lt;br /&gt;
Proposals will close Sunday, November 20 so we can finalize the list and add them to registration! (The deadline for preconference proposals has passed.)&lt;br /&gt;
&lt;br /&gt;
Spaces available: main meeting room (max 275) + 5 breakout rooms (max 30-50). &lt;br /&gt;
&lt;br /&gt;
'''Please include a &amp;quot;Contact/Responsible Individual&amp;quot; name and email address so we know who is willing to put on the proposed precon.&lt;br /&gt;
'''&lt;br /&gt;
==Full Day==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Hacking Content ===&lt;br /&gt;
&lt;br /&gt;
What is the future of getting library information and resources into users’ hands at the right time and with appropriate context and relevancy.  Learning management systems, library guides, Web-scale discovery systems-plenty of tools to choose from and still we see lots of opportunities for improvement. Let’s pick them apart and brainstorm ideas for projects that could address weaknesses in one or all of these systems. If you’re interested in these issues, challenges and conundrums join us for a day of thinking, dreaming and scheming. All skill sets and backgrounds needed. &lt;br /&gt;
&lt;br /&gt;
Speakers/Facilitators will be:&lt;br /&gt;
 - Thom Cox - Manager of Library Information Technology Services - Tufts University&lt;br /&gt;
 - Ken Varnum – Web Systems Manager - University of Michigan Libraries&lt;br /&gt;
 - Evviva Weinraub – Director, Emerging Technologies and Services - Oregon State University Libraries &lt;br /&gt;
&lt;br /&gt;
Contact:  Margaret Mellinger - margaret dot mellinger at oregonstate dot edu&lt;br /&gt;
&lt;br /&gt;
=== Developing applications using REST web services ===&lt;br /&gt;
&lt;br /&gt;
Been hearing about web services but don’t know where to start to build something? Have you built applications that use read services but are stumped by OAuth, Content Negotiation and HTTP Headers? Come dig in and learn how to build applications that interact with both read and write REST services. We’ll cover the basic principles and practices of REST services and discuss the Atom Publishing Protocol as a REST service and its extensibility. The group will examine and test the CouchDB HTTP API by building a simple list creation tool. You’ll learn how OCLC’s platform web services leverage Atom to expose the data and business processes from OCLC’s library systems. By the end of the session, you’ll know the basic principles of REST services, be able to perform Create, Read, Update and Delete operations via REST and be able to authenticate to REST services via API keys and OAuth.&lt;br /&gt;
&lt;br /&gt;
Come ready to learn and code!&lt;br /&gt;
&lt;br /&gt;
Presenter: Karen Coombs - coombsk at oclc dot org&lt;br /&gt;
&lt;br /&gt;
==Half Day Morning==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Linkfest ===&lt;br /&gt;
&lt;br /&gt;
We've had talks and sessions galore about Linked Data at code4lib in past years.  Let's focus on linking.  Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web.  At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there.  May a kajillion links bloom!&lt;br /&gt;
&lt;br /&gt;
If you need an &amp;quot;intro to linked data&amp;quot; we can prep a good list of readings/talks to review before you come.  But please come ready to link!&lt;br /&gt;
&lt;br /&gt;
Organizer type person:  Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu&lt;br /&gt;
&lt;br /&gt;
=== What's New in Solr ===&lt;br /&gt;
&lt;br /&gt;
This session will bring folks up to speed on the latest developments in Lucene and Solr.  There's always a lot of new capabilities as well as tips and tricks on using Solr in clever and powerful ways.  &lt;br /&gt;
&lt;br /&gt;
Presenter: Erik Hatcher - erik . hatcher @ lucidimagination dot com&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Half Day Afternoon==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Git -r done === &lt;br /&gt;
&lt;br /&gt;
A session to cover all things Git, everyone's favourite distributed version control system.  This session should cover a little bit of the history of Git, how it works, and how it's different than other version controls systems like SVN.  Practical application should also be covered, including how to clone existing repos and contribute code back to them, how to host your own repository, and best practices for setting up a distributed network.&lt;br /&gt;
&lt;br /&gt;
Looking for attendees with real-life Git experience to share it, so we can all broaden our understanding of possible use-cases and nifty advanced features.&lt;br /&gt;
&lt;br /&gt;
Coordinator:  Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com&lt;br /&gt;
&lt;br /&gt;
=== Blacklight ===&lt;br /&gt;
&lt;br /&gt;
This session will be walk-through of the architecture of Blacklight and what we have been improving since the rails 3 upgrade.  In addition to the architecture of the software, we will also briefly discuss the architecture of the Blacklight community and what has made it successful so far.&lt;br /&gt;
&lt;br /&gt;
For part of the session we will install Blacklight live and get it up and running.  This install demo will include a How-To on basic customizations in Blacklight using a test-driven approach (one of the cornerstones of the Blacklight community).&lt;br /&gt;
&lt;br /&gt;
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).  We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.&lt;br /&gt;
&lt;br /&gt;
Presenters: Jessie Keck, Stanford University - jkeck at stanford dot edu | Molly Pickral, University of Virginia - mpc3c at virginia dot edu&lt;br /&gt;
&lt;br /&gt;
=== DACS and EAD Overview ===&lt;br /&gt;
&lt;br /&gt;
This session will look at what DACS (Describing Archives: a Content Standard) is and describe the ten required elements.  Then there will be an overview of what EAD is, how it works, and the required elements.  The final part will be a practice session on taking a paper finding aid and coding it using DACS and EAD.&lt;br /&gt;
&lt;br /&gt;
Presenter:  Doris Munson, Eastern Washington University, dmunson at ewu dot edu&lt;br /&gt;
(please feel free to contact me if you are interested in being a co-presenter)&lt;br /&gt;
&lt;br /&gt;
=== Digging into metadata: context, code, and collaboration ===&lt;br /&gt;
&lt;br /&gt;
Working with library/archival metadata is difficult. This preconference will tackle pressing questions and will show some of the intricacies of metadata (including AACR2/MARC) with exercises to demonstrate why inconsistencies exist in the data. What steps can the cataloging &amp;amp; metadata community take to help improve the quality of this data?  What tools &amp;amp; techniques could help?  Rules have evolved over time leaving dirty legacy data.  Systems have impacted--and will continue to impact--data structure &amp;amp; design.  How can this data be aggregated and refined for use in a new emerging data environments?  What assumptions can safely be made and when do you need to inquire about local practice?  We will end with a hack-fest where you can ask questions of experienced catalogers and get help with your metadata related problems.  Bring your laptops and data.   &lt;br /&gt;
&lt;br /&gt;
Person Herder: Becky Yoose, Grinnell College, yoosebec at grinnell dot edu&lt;br /&gt;
&lt;br /&gt;
Collaborators/Facilitators: Corey Harper, New York University - corey dot harper at nyu dot edu | Shana L. McDanold, University of Pennsylvania - 	&lt;br /&gt;
mcdanold at pobox dot upenn dot edu  | Laura Smart, Caltech - laura at library dot caltech dot edu&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_talks_proposals&amp;diff=9901</id>
		<title>2012 talks proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_talks_proposals&amp;diff=9901"/>
				<updated>2011-11-21T14:09:21Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Deadline for talk submission is ''Sunday, November 20''. (The deadline for 2012 Talks proposals is now closed.)&lt;br /&gt;
&lt;br /&gt;
Prepared talks are 20 minutes (including setup and questions), and focus on one or more of the following areas:&lt;br /&gt;
 * tools (some cool new software, software library or integration platform)&lt;br /&gt;
 * specs (how to get the most out of some protocols, or proposals for new ones)&lt;br /&gt;
 * challenges (one or more big problems we should collectively address)&lt;br /&gt;
&lt;br /&gt;
The community will vote on proposals using the criteria of:&lt;br /&gt;
 * usefulness&lt;br /&gt;
 * newness&lt;br /&gt;
 * geekiness&lt;br /&gt;
 * diversity of topics&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Talk Title: ==&lt;br /&gt;
 &lt;br /&gt;
* Speaker's name, affiliation, and email address&lt;br /&gt;
* Second speaker's name, affiliation, email address, if second speaker&lt;br /&gt;
&lt;br /&gt;
Abstract of no more than 500 words.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== VuFind 2.0: Why and How? ==&lt;br /&gt;
&lt;br /&gt;
* Demian Katz, Villanova University, demian.katz@villanova.edu&lt;br /&gt;
&lt;br /&gt;
A major new version of the VuFind discovery software is currently in development.  While VuFind 1.x remains extremely popular, some of its components are beginning to show their age.  VuFind 2.0 aims to retain all the strengths of the previous version of the software while making the architecture cleaner, more modern and more standards-based.  This presentation will examine the motivation behind the update, preview some of the new features to look forward to, and discuss the challenges of creating a developer-friendly open source package in PHP.&lt;br /&gt;
&lt;br /&gt;
== Open Source Software Registry ==&lt;br /&gt;
&lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]], LYRASIS, Peter.Murray@lyrasis.org&lt;br /&gt;
&lt;br /&gt;
LYRASIS is creating and shepherding a [[Registry_E-R_Diagram|registry of library open source software]] as part of its [http://www.lyrasis.org/News/Press-Releases/2011/LYRASIS-Receives-Grant-to-Support-Open-Source.aspx grant from the Mellon Foundation to support the adoption of open source software by libraries].  &lt;br /&gt;
The goal of the grant is to help libraries of all types determine if open source software is right for them, and what combination of software, hosting, training, and consulting works for their situation.  &lt;br /&gt;
The registry is intended to become a community exchange point and stimulant for growth of the library open source ecosystem by connecting libraries with projects, service providers, and events.&lt;br /&gt;
&lt;br /&gt;
The first half of this session will demonstrate the registry functions and describe how projects and providers can get involved.  &lt;br /&gt;
The second half of the session will be a brainstorming suggestion of how to expand the functionality and usefulness of the registry.&lt;br /&gt;
&lt;br /&gt;
== Property Graphs And TinkerPop Applications in Digital Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Brian Tingle, California Digital Library, brian.tingle.cdlib.org@gmail.com&lt;br /&gt;
&lt;br /&gt;
[http://www.tinkerpop.com/ TinkerPop] is an open source software development group focusing on technologies in the [http://en.wikipedia.org/wiki/Graph_database graph database] space.   &lt;br /&gt;
This talk will provide a general introduction to the TinkerPop Graph Stack and the [https://github.com/tinkerpop/gremlin/wiki/Defining-a-Property-Graph property graph model] is uses.  The introduction will include code examples and explanations of the property graph models used by the [http://socialarchive.iath.virginia.edu/ Social Networks in Archival Context] project and show how the historical social graph is exposed as a JSON/REST API implemented by a TinkerPop [https://github.com/tinkerpop/rexster rexster] [https://github.com/tinkerpop/rexster-kibbles Kibble] that contains the application's graph theory logic.  Other graph database applications possible with TinkerPop such as RDF support, and citation analysis will also be discussed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Security in Mind ==&lt;br /&gt;
 &lt;br /&gt;
* Erin Germ, United States Naval Academy, Nimitz Library, germ@usna.edu&lt;br /&gt;
&lt;br /&gt;
I would like to talk about security of library software.&lt;br /&gt;
&lt;br /&gt;
Over the Summer, I discovered a critical vulnerability in a vendor’s software that (verified) allowed me to assume any user’s identity for that site, (verified) switch to any user, and to (unverified, meaning I didn’t not perform this as I didn’t want to “hack” another library’s site) assume the role of any user for any other library who used this particular vendor's software.&lt;br /&gt;
&lt;br /&gt;
Within a 3 hour period, I discovered a 2 vulnerabilities: 1) minor one allowing me to access any backups from any library site, and 2) a critical vulnerability.  From start to finish, the examination, discovery in the vulnerability, and execution of a working exploit was done in less than 2 hours. The vulnerability was a result of poor cookie implementation. The exploit itself revolved around modifying the cookie, and then altering the browser’s permissions by assuming the role of another user.&lt;br /&gt;
&lt;br /&gt;
I do not intend on stating which vendor it was, but I will show how I was able to perform this. If needed, I can do further research and “investigation” into other vendor's software to see what I can “find”.&lt;br /&gt;
&lt;br /&gt;
''If selected, I will contact the vendor to inform them that I will present about this at C4L2012. I do not intend on releasing the name of the vendor.''&lt;br /&gt;
&lt;br /&gt;
== Search Engines and Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Greg Lindahl, blekko CTO, greg@blekko.com&lt;br /&gt;
&lt;br /&gt;
[https://blekko.com blekko] is a new web-scale search engine which enables end-users to create vertical search engines, through a feature called [http://help.blekko.com/index.php/category/slashtags/ slashtags]. Slashtags can contain as few as 1 or as many as tens of thousands of websites relevant to a narrow or broad topic. We have an extensive set of slashtags curated by a combination of volunteers and an in-house librarian team, or end-users can create and share their own. This talk will cover examples of slashtag creation relevant to libraries, and show how to embed this search into a library website, either using javascript or via our API.&lt;br /&gt;
&lt;br /&gt;
''We have exhibited at a couple of library conferences, and have received a lot of interest. blekko is a free service.''&lt;br /&gt;
&lt;br /&gt;
== Beyond code: Versioning data with Git and Mercurial. ==&lt;br /&gt;
&lt;br /&gt;
* Stephanie Collett, California Digital Library, stephanie.collett@ucop.edu&lt;br /&gt;
* Martin Haye, California Digital Library, martin.haye@ucop.edu&lt;br /&gt;
&lt;br /&gt;
Within a relatively short time since their introduction, [http://en.wikipedia.org/wiki/Distributed_Version_Control_System distributed version control systems] (DVCS) like [http://git-scm.com/ Git] and [http://mercurial.selenic.com/ Mercurial] have enjoyed widespread adoption for versioning code. It didn’t take long for the library development community to start discussing the potential for using DVCS within our applications and repositories to version data. After all, many of the features that have made some of these systems popular in the open source community to version code (e.g. lightweight, file-based, compressed, reliable) also make them compelling options for versioning data.  And why write an entire versioning system from scratch if a DVCS solution can be a drop-in solution? At the [http://www.cdlib.org/ California Digital Library] (CDL) we’ve started using Git and Mercurial in some of our applications to version data. This has proven effective in some situations and unworkable in others. This presentation will be a practical case study of CDL’s experiences with using DVCS to version data. We will explain how we’re incorporating Git and Mercurial in our applications, describe our successes and failures and consider the issues involved in repurposing these systems for data versioning.&lt;br /&gt;
&lt;br /&gt;
==Design for Developers==&lt;br /&gt;
&lt;br /&gt;
*Lisa Kurt, University of Nevada, Reno, lkurt@unr.edu&lt;br /&gt;
&lt;br /&gt;
Users expect good design. This talk will delve into what makes really great design, what to look for, and how to do it. Learn the principles of great design to take your applications, user interfaces, and projects to a higher level. With years of experience in graphic design and illustration, Lisa will discuss design principles, trends, process, tools, and development. Design examples will be from her own projects as well as a variety from industry. You’ll walk away with design knowledge that you can apply immediately to a variety of applications and a number of top notch go-to resources to get you up and running.&lt;br /&gt;
&lt;br /&gt;
==Building research applications with Mendeley==&lt;br /&gt;
&lt;br /&gt;
William Gunn, Mendeley william.gunn@mendeley.com (@mrgunn)&lt;br /&gt;
&lt;br /&gt;
This is partly a tool talk and partly a big idea one.&lt;br /&gt;
&lt;br /&gt;
Mendeley has built the world's largest open database of research and we've now begun to collect some interesting social metadata around the document metadata. I would like to share with the Code4Lib attendees information about using this resource to do things within your application that have previously been impossible for the library community, or in some cases impossible without expensive database subscriptions. One thing that's now possible is to augment catalog search by surfacing information about content usage, allowing people to not only find things matching a query, but popular things or things read by their colleagues. In addition to augmenting search, you can also use this information to augment discovery. Imagine an online exhibit of artifacts from a newly discovered dig not just linking to papers which discuss the artifact, but linking to really good interesting papers about the place and the people who made the artifacts. So the big idea is, &amp;quot;How will looking at the literature from a broader perspective than simple citation analysis change how research is done and communicated? How can we build tools that make this process easier and faster?&amp;quot; I can show some examples of applications that have been built using the Mendeley and PLoS APIs to begin to address this question, and I can also present results from Mendeley's developer challenge which shows what kinds of applications researchers are looking for, what kind of applications peope are building, and illustrates some interesting places where the two don't overlap.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Your UI can make or break the application (to the user, anyway)==&lt;br /&gt;
&lt;br /&gt;
* Robin Schaaf, University of Notre Dame, schaaf.4@nd.edu&lt;br /&gt;
&lt;br /&gt;
UI development is hard and too often ends up as an after-thought to computer programmers - if you were a CS major in college I'll bet you didn't have many, if any, design courses.  I'll talk about how to involve the users upfront with design and some common pitfalls of this approach.  I'll also make a case for why you should do the screen design before a single line of code is written.  And I'll throw in some ideas for increasing usability and attractiveness of your web applications.  I'd like to make a case study of the UI development of our open source ERMS.&lt;br /&gt;
&lt;br /&gt;
==Why Nobody Knows How Big The Library Really Is - Perspective of a Library Outside Turned Insider==&lt;br /&gt;
&lt;br /&gt;
* Patrick Berry, California State University, Chico, pberry@csuchico.edu&lt;br /&gt;
&lt;br /&gt;
In this talk I would like to bring the perspective of an &amp;quot;outsider&amp;quot; (although an avowed IT insider) to let you know that people don't understand the full scope of the library.  As we &amp;quot;rethink education&amp;quot;, it is incumbent upon us to help educate our institutions as to the scope of the library.  I will present some of the tactics I'm employing to help people outside, and in some cases inside, the library to understand our size and the value we bring to the institution.&lt;br /&gt;
&lt;br /&gt;
==Building a URL Management Module using the Concrete5 Package Architecture==&lt;br /&gt;
&lt;br /&gt;
* David Uspal, Villanova University, david.uspal@villanova.edu&lt;br /&gt;
&lt;br /&gt;
Keeping track of URLs utilized across a large website such as a university library, and keeping that content up to date for subject and course guides, can be a pain, and as an open source shop, we’d like to have open source solution for this issue.  For this talk, I intend to detail our solution to this issue by walking step-by-step through the building process for our URL Management module -- including why a new solution was necessary; a quick rundown of our CMS ([http://www.concrete5.org Concrete5], a CMS that isn’t Drupal); utilizing the Concrete5 APIs to isolate our solution from core code (to avoid complications caused by core updates); how our solution was integrated into the CMS architecture for easy installation; and our future plans on the project.&lt;br /&gt;
&lt;br /&gt;
==Building an NCIP connector to OpenSRF to facilitate resource sharing==&lt;br /&gt;
&lt;br /&gt;
* Jon Scott, Lyrasis, jon_scott@wsu.edu and Kyle Banerjee, Orbis Cascade Alliance, banerjek@uoregon.edu &lt;br /&gt;
&lt;br /&gt;
How do you reverse engineer any protocol to provide a new service? Humans (and worse yet, committees) often design verbose protocols built around use cases that don't line up current reality. To compound difficulties, the contents of protocol containers are not sufficiently defined/predictable and the only assistance available is sketchy documentation and kind individuals on the internet willing to share what they learned via trial by fire.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCIP (Niso Circulation Interchange Protocol) is an open standard that defines a set of messages to support exchange of circulation data between disparate circulation, interlibrary loan, and related applications -- widespread adoption of NCIP would eliminate huge amounts of duplicate processing in separate systems. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This presentation discusses how we learned enough about NCIP and OpenSRF from scratch to build an NCIP responder for Evergreen to facilitate resource sharing in a large consortium that relies on over 20 different ILSes.&lt;br /&gt;
&lt;br /&gt;
==Practical Agile: What's Working for Stanford, Blacklight, and Hydra==&lt;br /&gt;
&lt;br /&gt;
* Naomi Dushay, Stanford University Libraries, ndushay@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Agile development techniques can be difficult to adopt in the context of library software development.  Maybe your shop has only one or two developers, or you always have too many simultaneous projects.   Maybe your new projects can’t be started until 27 librarians reach consensus on the specifications.&lt;br /&gt;
&lt;br /&gt;
This talk will present successful Agile- and Silicon-Valley-inspired practices we’ve adopted at Stanford and/or in the Blacklight and Hydra projects.  We’ve targeted developer happiness as well as improved productivity with our recent changes.  User stories, dead week, sight lines … it’ll be a grab bag of goodies to bring back to your institution, including some ideas on how to adopt these practices without overt management buy in.&lt;br /&gt;
&lt;br /&gt;
==Quick and &amp;lt;strike&amp;gt;Dirty&amp;lt;/strike&amp;gt; Clean Usability: Rapid Prototyping with Bootstrap==&lt;br /&gt;
&lt;br /&gt;
* Shaun Ellis, Princeton University Libraries, shaune@princeton.edu &lt;br /&gt;
&lt;br /&gt;
''&amp;quot;The code itself is unimportant; a project is only as useful as people actually find it.&amp;quot;  - Linus Torvalds'' [http://bit.ly/p4uuyy]&lt;br /&gt;
&lt;br /&gt;
Usability has been a buzzword for some time now, but what is the process for making the the transition toward a better user experience, and hence, better designed library sites?  I will discuss the one facet of the process my team is using to redesign the Finding Aids site for Princeton University Libraries (still in development).  The approach involves the use of rapid prototyping, with Bootstrap [http://twitter.github.com/bootstrap/], to make sure we are on track with what users and stakeholders expect up front, and throughout the development process.&lt;br /&gt;
&lt;br /&gt;
Because Bootstrap allows for early and iterative user feedback, it is more effective than the historic Photoshop mockups/wireframe technique.  The Photoshop approach allows stakeholders to test the look, but not the feel -- and often leaves developers scratching their heads.  Being a CSS/HTML/Javascript grid-based framework, Bootstrap makes it easy for anyone with a bit of HTML/CSS chops to quickly build slick, interactive prototypes right in the browser -- tangible solutions which can be shared, evaluated, revised, and followed by all stakeholders (see Minimum Viable Products [http://en.wikipedia.org/wiki/Minimum_viable_product]).  Efficiency is multiplied because the customized prototypes can flow directly into production use, as is the goal with iterative development approaches, such as the Agile methodology.&lt;br /&gt;
&lt;br /&gt;
While Bootstrap is not the only framework that offers grid-based layout, development is expedited and usability is enhanced by Bootstraps use of of &amp;quot;prefabbed&amp;quot; conventional UI patterns, clean typography, and lean Javascript for interactivity.   Furthermore, out-of-the box Bootstrap comes in a fairly neutral palette, so focus remains on usability, and does not devolve into premature discussions of color or branding choices.  Finally, using Less can be a powerful tool in conjunction with Bootstrap, but is not necessary.  I will discuss the pros and cons, and offer examples for how to getting up and running with or without Less.&lt;br /&gt;
&lt;br /&gt;
==Search Engine Relevancy Tuning - A Static Rank Framework for Solr/Lucene==&lt;br /&gt;
&lt;br /&gt;
* Mike Schultz, Amazon.com (formerly Summon Search Architect) mike.schultz@gmail.com&lt;br /&gt;
&lt;br /&gt;
Solr/Lucene provides a lot of flexibility for adjusting relevancy scoring and improving search results.  Roughly speaking there are two areas of concern: Firstly, a 'dynamic rank' calculation that is a function of the user query and document text fields.  And secondly, a 'static rank' which is independent of the query and generally is a function of non-text document metadata.  In this talk I will outline an easily understood, hand-tunable static rank system with a minimal number of parameters.&lt;br /&gt;
&lt;br /&gt;
The obvious major feature of a search engine is to return results relevant to a user query.  Perhaps less obvious is the huge role query independent document features play in achieving that. Google's PageRank is an example of a static ranking of web pages based on links and other secret sauce.  In the Summon service, our 800 million documents have features like publication date, document type, citation count and Boolean features like the-article-is-peer-reviewed.  These fields aren't textual and remain 'static' from query to query, but need to influence a document's relevancy score.  In our search results, with all query related features being equal, we'd rather have more recent documents above older ones, Journals above Newspapers, and articles that are peer reviewed above those that are not. The static rank system I will describe achieves this and has the following features:&lt;br /&gt;
&lt;br /&gt;
* Query-time only calculation - nothing is baked into the index - with parameters adjustable at query time.&lt;br /&gt;
* The system is based on a signal metaphor where components are 'wired' together.  System components allow multiplexing, amplifying, summing, tunable band-pass filtering, string-to-value-mapping all with a bare minimum of parameters.&lt;br /&gt;
* An intuitive approach for mixing dynamic and static rank that is more effective than simple adding or multiplying.&lt;br /&gt;
* A way of equating disparate static metadata types that leads to understandable results ordering.&lt;br /&gt;
&lt;br /&gt;
==Submitting Digitized Book-like things to the Internet Archive==&lt;br /&gt;
&lt;br /&gt;
* Joel Richard, Smithsonian Institution Libraries, richardjm@si.edu&lt;br /&gt;
&lt;br /&gt;
The Smithsonian Libraries has submitted thousands of out-of-copyright items to the Internet Archive over the years. Specifically in relation to the Biodiversity Heritage Library, we have developed an in-house boutique scanning and upload process that became a learning experience in automated uploading to the Archive. As part of the software development, we created a whitepaper that details the combined learning experiences of the Smithsonian Libraries and the Missouri Botanical Garden. We will discuss some of the the contents of this whitepaper in the context of our scanning process and the manner in which we upload items to the Archive. &lt;br /&gt;
&lt;br /&gt;
Our talk will include a discussion of the types of files and their formats used by the Archive, processes that the Archive performs on uploaded items, ways of interacting and affecting those processes, potential pitfalls and solutions that you may encounter when uploading, and tools that the Archive provides to help monitor and manage your uploaded documents. &lt;br /&gt;
&lt;br /&gt;
Finally, we'll wrap up with a brief summary of how to use things that are on the Internet Archive in your own websites.&lt;br /&gt;
&lt;br /&gt;
== So... you think you want to Host a Code4Lib National Conference, do you? ==&lt;br /&gt;
&lt;br /&gt;
* Elizabeth Duell, Orbis Cascade Alliance, eduell@uoregon.edu&lt;br /&gt;
&lt;br /&gt;
Are you interested in hosting your own Code4Lib Conference? Do you know what it would take? What does BEO stands for? What does F&amp;amp;B Minimum mean? Who would you talk to for support/mentoring? There are so many things to think about: internet support, venue size, rooming blocks, contracts, dietary restrictions and coffee (can't forget the coffee!) just to name a few. Putting together a conference of any size can look daunting, so let's take the scary out of it and replace it with a can do attitude!&lt;br /&gt;
&lt;br /&gt;
Be a step ahead of the game by learning from the people behind the curtain. Ask questions and be given templates/ cheat sheets! &lt;br /&gt;
&lt;br /&gt;
== HTML5 Microdata and Schema.org ==&lt;br /&gt;
 &lt;br /&gt;
* Jason Ronallo, North Carolina State University Libraries, jason_ronallo@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
When the big search engines announced support for HTML5 microdata and the schema.org vocabularies, the balance of power for semantic markup in HTML shifted. &lt;br /&gt;
* What is microdata? &lt;br /&gt;
* Where does microdata fit with regards to other approaches like RDFa and microformats? &lt;br /&gt;
* Where do libraries stand in the worldview of Schema.org and what can they do about it? &lt;br /&gt;
* How can implementing microdata and schema.org optimize your sites for search engines?&lt;br /&gt;
* What tools are available?&lt;br /&gt;
&lt;br /&gt;
== Stack View: A Library Browsing Tool ==&lt;br /&gt;
 &lt;br /&gt;
* Annie Cain, Harvard Library Innovation Lab, acain@law.harvard.edu&lt;br /&gt;
&lt;br /&gt;
In an effort to recreate and build upon the traditional method of browsing a physical library, we used catalog data, including dimensions and page count, to create a [http://librarylab.law.harvard.edu/projects/stackview/ virtual shelf].&lt;br /&gt;
&lt;br /&gt;
This CSS and JavaScript backed visualization allows items to sit on any number of different shelves, really taking advantage of its digital nature.  See how we built Stack View on top of our data and learn how you can create shelves of your own using our open source code.&lt;br /&gt;
&lt;br /&gt;
== “Linked-Data-Ready” Software for Libraries ==&lt;br /&gt;
&lt;br /&gt;
* Jennifer Bowen, University of Rochester River Campus Libraries, jbowen@library.rochester.edu&lt;br /&gt;
&lt;br /&gt;
Linked data is poised to replace MARC as the basis for the new library bibliographic framework.  For libraries to benefit from linked data, they must learn about it, experiment with it, demonstrate its usefulness, and take a leadership role in its deployment. &lt;br /&gt;
&lt;br /&gt;
The eXtensible Catalog Organization (XCO) offers open-source software for libraries that is “linked-data-ready.” XC software prepares MARC and Dublin Core metadata for exposure to the semantic web, incorporating FRBR Group 1 entities and registered vocabularies for RDA elements and roles. This presentation will include a software demonstration, proposed software architecture for creation and management of linked data, a vision for how libraries can migrate from MARC to linked data, and an update on XCO progress toward linked data goals.&lt;br /&gt;
&lt;br /&gt;
== How people search the library from a single search box ==&lt;br /&gt;
&lt;br /&gt;
* Cory Lown, North Carolina State University Libraries, cory_lown@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Searching the library is complex. There's the catalog, article databases, journal title and database title look-ups, the library website, finding aids, knowledge bases, etc. How would users search if they could get to all of these resources from a single search box? I'll share what we've learned about single search at NCSU Libraries by tracking use of QuickSearch (http://www.lib.ncsu.edu/search/index.php?q=aerospace+engineering), our home-grown unified search application. As part of this talk I will suggest low-cost ways to collect real world use data that can be applied to improve search. I will try to convince you that data collection must be carefully planned and designed to be an effective tool to help you understand what your users are telling you through their behavior. I will talk about how the fragmented library resource environment challenges us to provide useful and understandable search environments. Finally, I will share findings from analyzing millions of user transactions about how people search the library from a production single search box at a large university library.&lt;br /&gt;
&lt;br /&gt;
== An Incremental Approach to Archival Description and Access ==&lt;br /&gt;
&lt;br /&gt;
* Chela Scott Weber, New York University Libraries, chelascott@gmail.com&lt;br /&gt;
* Mark A. Matienzo, Yale University Library, mark@matienzo.org&lt;br /&gt;
&lt;br /&gt;
An ongoing problem for many archives and special collections units is a lack of technological infrastructure and ongoing support. Funding for many archival programs arrives on a project-by-project basis, often in the form of grants. One of the largest concerns for archivist, therefore, is ensuring the sustainability of any solutions or processes that support core operations, such as archival description and access systems.&lt;br /&gt;
&lt;br /&gt;
The presenters will describe their experience developing an iterative and sustainable approach to archival description and access at the library of a small historical society. Starting with mostly OCRed legacy finding aids and no online access to collections, and ending with structured data about the entirety of their holdings available online over three years time, we will detail the evolution of the work from problem-solving through to the resulting phases of descriptive work and development of a basic online access portal created in WordPress. We will discuss making reasonable and sustainable choices in an environment with little monetary and technical support, and how the organization's staff were able to build a system and processes that could leverage messy legacy metadata initially and grow to use structured, standardized data as it was created. We will also discuss the specific technical solutions we developed (the WordPress instance and supporting plugins) and our experience with how bugs and barriers outside of our control changed our insights.&lt;br /&gt;
&lt;br /&gt;
== Making the Easy Things Easy: A Generic ILS API ==&lt;br /&gt;
&lt;br /&gt;
* Wayne Schneider, Hennepin County Library, wschneider@hclib.org&lt;br /&gt;
&lt;br /&gt;
Some stuff we try to do is complicated, because, let's face it, library data is hard. Some stuff, on the other hand, should be easy. Given an item identifier, I should be able to look at item availability. Given a title identifier, I should be able to place a request. And no, I shouldn't have to parse through the NCIP specification or write a SIP client to do it.&lt;br /&gt;
&lt;br /&gt;
This talk will present work we have done on a web services approach to an API for traditional library transactional data, including example applications.&lt;br /&gt;
&lt;br /&gt;
== Your Catalog in Linked Data==&lt;br /&gt;
&lt;br /&gt;
* Tom Johnson, Oregon State University Libraries, thomas.johnson@oregonstate.edu&lt;br /&gt;
&lt;br /&gt;
Linked Library Data activity over the last year has seen bibliographic data sets and vocabularies proliferating from traditional library&lt;br /&gt;
sources. We've reached a point where regular libraries don't have to go it alone to be on the Semantic Web. There is a quickly growing pool of things we can actually ''link to'', and everyone's existing data can be immediately enriched by participating.&lt;br /&gt;
&lt;br /&gt;
This is a quick and dirty road to getting your catalog onto the Linked Data web. The talk  will take you from start to finish, using Free Software tools to establish a namespace, put up a SPARQL endpoint, make a simple data model, convert MARC records to RDF, and link the results to major existing data sets (skipping conveniently over pesky processing time). A small amount of &amp;quot;why linked data?&amp;quot; content will be covered, but the primary goal is to leave you able to reproduce the process and start linking your catalog into the web of data. Appropriate documentation will be on the web.&lt;br /&gt;
&lt;br /&gt;
== Getting the Library into the Learning Management System using Basic LTI == &lt;br /&gt;
&lt;br /&gt;
* David Walker, California State University, dwalker@calstate.edu&lt;br /&gt;
&lt;br /&gt;
The integration of library resources into learning management systems (LMS) has long been something of a holy grail for academic libraries.  The ability to deliver targeted library systems and services to students and faculty directly within their online course would greatly simplify access to library resources.  Yet, the technical barriers to achieving that goal have to date been formidable.  &lt;br /&gt;
&lt;br /&gt;
The recently released Learning Tool Interoperability (LTI) protocol, developed by IMS, now greatly simplifies this process by allowing libraries (and others) to develop and maintain “tools” that function like a native plugin or building block within the LMS, but ultimately live outside of it.  In this presentation, David will provide an overview of Basic LTI, a simplified subset (or profile) of the wider LTI protocol, showing how libraries can use this to easily integrate their external systems into any major LMS.  He’ll showcase the work Cal State has done to do just that.&lt;br /&gt;
&lt;br /&gt;
== Turn your Library Proxy Server into a Honeypot ==&lt;br /&gt;
 &lt;br /&gt;
* Calvin Mah, Simon Fraser University, calvinm@sfu.ca (@calvinmah)&lt;br /&gt;
&lt;br /&gt;
Ezproxy has provided libraries with a useful tool for providing patrons with offsite online access to licensed electronic resources.  This has not gone unnoticed for the unscrupulous users of the Internet who are either unwilling or unable to obtain legitimate access to these materials for themselves.  Instead, they buy or share hacked university computing accounts for unauthorized access.  When undetected, abuse of compromised university accounts can lead to abuse of vendor resources which lead to the blocking of the entire campus block of IP addresses from accessing that resource.&lt;br /&gt;
&lt;br /&gt;
Simon Fraser University Library has been pro actively detecting and thwarting unauthorized attempts through log analysis.  Since SFU has begun analysing our ezproxy logs, the number of new SFU login credentials which are posted and shared in publicly accessible forums has been reduced to zero.   Since our log monitoring began in 2008, the annual average number of SFU login credentials  that are compromised or hacked is 140.  Instead of being a single point of weakness in campus IT security, the library’s proxy server is a honeypot exposing weak passwords, keystroke logging trojans installed on patron PCs and campus network password sniffers.&lt;br /&gt;
&lt;br /&gt;
This talk will discuss techniques such as geomapping login attempts, strategies such as seeding phishing attempts and tools such as statistical log analysis used in detecting compromised login credentials.  &lt;br /&gt;
&lt;br /&gt;
== Relevance Ranking in the Scholarly Domain ==&lt;br /&gt;
&lt;br /&gt;
* Tamar Sadeh, PhD, Ex Libris Group, tamar.sadeh@exlibrisgroup.com&lt;br /&gt;
&lt;br /&gt;
The greatest challenge for discovery systems is how to provide users with the most relevant search results, given the immense landscape of available content. In a manner that is similar to human interaction between two parties, in which each person adjusts to the other in tone, language, and subject matter, discovery systems would ideally be sophisticated and flexible enough to adjust their algorithms to individual users and each user’s information needs. &lt;br /&gt;
&lt;br /&gt;
When evaluating the relevance of an item to a specific user in a specific context, relevance-ranking algorithms need to take into account, in addition to the degree to which the item matches the query, information that is not embodied in the item itself. Such information, which includes the item’s scholarly value, the type of search that the user is conducting (e.g., an exploratory search or a known-item search), and other factors, enables a discovery system to fulfill user expectations that have been shaped by experience with Web search engines.  &lt;br /&gt;
&lt;br /&gt;
The session will focus on the challenges of developing and evaluating relevance-ranking algorithms for the scholarly domain. Examples will be drawn mainly from the relevance-ranking technology deployed by the Ex Libris Primo discovery solution. &lt;br /&gt;
&lt;br /&gt;
== Mobile Library Catalog using Z39.50 ==&lt;br /&gt;
 &lt;br /&gt;
* James Paul Muir, The Ohio State University, muir.29@osu.edu&lt;br /&gt;
&lt;br /&gt;
A talk about putting a new spin on an age-old technology, creating a universal interface, which exposes any Z39.50 capable library catalog as a simple, useful and universal REST API for use in native mobile apps and mobile web.&lt;br /&gt;
&lt;br /&gt;
The talk includes the exploration and demonstration of the Ohio State University’s native app “OSU Mobile” for iOS and Android and shows how the library catalog search was integrated.&lt;br /&gt;
&lt;br /&gt;
The backbone of the project is a REST API, which was created in a weekend using a PHP framework that translates OPAC XML results from the Z39.50 interface into mobile-friendly JSON formatting.&lt;br /&gt;
&lt;br /&gt;
Raw Z39.50 search results contain all MARC information as well as local holdings.  &lt;br /&gt;
Configurable search fields and the ability to select which fields to include in the JSON output make this solution a perfect fit for any Z39.50-capable library catalog.&lt;br /&gt;
  &lt;br /&gt;
Looking forward, possibilities for expansion include the use of Off Campus Sign-In for online resources so mobile patrons can directly access online resources from a smartphone (included in the Android version of OSU Mobile) as well as integration with library patron account.&lt;br /&gt;
&lt;br /&gt;
Enjoy this alternative to writing a custom OPAC adapter or using a 3rd party service for exposing library records and use the proven and universal Z39.50 interface directly against your library catalog. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== DMPTool: Guidance and resources to build a data management plan ==&lt;br /&gt;
 &lt;br /&gt;
* Marisa Strong, California Digital Libary, marisa.strong@ucop.edu&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A number of U.S. funding agencies such as the National Science Foundation require researchers to supply detailed plans for managing research data, called Data Management Plans. To help researchers with this requirement, the California Digital Library (CDL) along with several organizations, collaborated to develop the DMPTool. The goal is to provide researchers with guidance, links to resources and help with writing data management plans.&lt;br /&gt;
&lt;br /&gt;
This open-source, Ruby on Rails software tool is hosted on a SLES VM by CDL. The tool is integrated with Shibboleth, federated single sign-on software, which allows users to login via their home institutions. We had a geographically distributed development team sharing their code on Bitbucket.&lt;br /&gt;
&lt;br /&gt;
This talk will demo features of the application, the Shibboleth login architecture, as well as highlight the agile development practices and methods used to successfully design and build the application on an aggressive schedule.&lt;br /&gt;
&lt;br /&gt;
== Lies, Damned Lies, and Lines of Code Per Day ==&lt;br /&gt;
 &lt;br /&gt;
* James Stuart, Columbia University, james.stuart@columbia.edu&lt;br /&gt;
&lt;br /&gt;
We've all heard about that one study that showed that Pair Programming was 20% efficient than working alone. Or maybe you saw on a blog that study that showed that programmers who write fewer lines of code per day are more efficient...or was it less efficient? And of course, we all know that programmers who work in (Ruby|Python|Java|C|Erlang) have been shown to be more efficient.&lt;br /&gt;
&lt;br /&gt;
A quick examination of some of the research surrounding programming efficiency and methodology, with a focus on personal productivity, and how to incorporate the more believable research into your own team's workflow.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==An Anatomy of a Book Viewer==&lt;br /&gt;
&lt;br /&gt;
*Mohammed Abuouda, Bibliotheca Alexandrina, mohammed.abuouda@bibalex.org&lt;br /&gt;
&lt;br /&gt;
Bibliotheca Alexandria (BA) hosts 210,000 digital books in different languages available at http://dar.bibalex.org. It includes the largest collection of digitized Arabic books. Using open source  tools, BA has developed a modular book viewer that can be deployed in any environment to provide the users with a great personalized reading experience. BA’s book viewer provides several services that make this possible: morphological search in different languages, localization, server load balancing, scalability and image processing. Personalization features includes different types of annotation such as sticky notes, highlighting and underlining. It also provides the ability to embed the viewer in any webpage and change its skin.&lt;br /&gt;
&lt;br /&gt;
In this talk we will describe the book viewer architecture, its modular design and how to incorporate it in your current environment.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Carrier: Digital Signage System ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:jmspargu|Justin Spargur]], The University of Arizona, spargurj@u.library.arizona.edu&lt;br /&gt;
 &lt;br /&gt;
Carrier is a web-based digital signage application written using JavaScript, PHP, MySQL that can be used on any device with an internet connection and a web browser. Used across the University of Arizona Libraries campuses, Carrier can display any web-based content, allowing users to promote new library collections and services via images, web pages, or videos. Users can easily manage the order in which slides are delivered, manage the length that slides are displayed for, set dates for when slides should be shown, and even specify specific locations where slides should be presented. &lt;br /&gt;
 &lt;br /&gt;
In addition to marketing purposes, Carrier can be used to send both low and high priority alerts to patrons. Alerts can be sent through the administrative interface, via RSS feeds, and even through a Twitter feed, allowing for easy integration with existing campus emergency notification systems.&lt;br /&gt;
 &lt;br /&gt;
I will describe the technical underpinnings of Carrier, challenges that we’ve faced since its implementation, enhancements planned for the next release of the software, and discuss our plans for releasing this software for others to use '''for free'''.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== We Built It.  They Came.  Now What? ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:evviva|Evviva Weinraub]], Oregon State University, evviva.weinraub@oregonstate.edu&lt;br /&gt;
 &lt;br /&gt;
You have a great idea for something new or useful.  You build it, put it out there on GitHub, do a couple of presentations, maybe a press release and BAM, suddenly you’ve created a successful Open Source tool that others are using.  Great!&lt;br /&gt;
&lt;br /&gt;
Fast-forward 3 years. &lt;br /&gt;
&lt;br /&gt;
You still believe in the product, but you can no longer be solely responsible for taking care of it.  Just putting it out there has made it a tool others use, but how do you find a community of folks who believe in the product as much as you do and are willing to commit the time and energy into building, sustaining and moving this project forward.  Or just figuring out if you should bother trying?&lt;br /&gt;
&lt;br /&gt;
In 2006, OSU Libraries built an Interactive Course Assignment system called Library a la Carte – think LibGuides only Open Source.  We now find ourselves in just this predicament.  &lt;br /&gt;
&lt;br /&gt;
What can we do as a community to move beyond our build-first-ask-questions-later mentality and embed sustainability into our new and existing ideas and products without moving toward commercialization?  I fully expect we’ll end up with more questions than answers, but let’s spend some talking about our predicament and yours and think about how we can come out the other side. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Contextually Rich Collections Without the Risk: Digital Forensics and Automated Data Triage for Digital Collections ==&lt;br /&gt;
&lt;br /&gt;
* [[User:kamwoods|Kam Woods]], University of North Carolina at Chapel Hill, kamwoods@email.unc.edu&lt;br /&gt;
* Cal Lee, University of North Carolina at Chapel Hill, callee -- at -- ils -- unc -- edu&lt;br /&gt;
&lt;br /&gt;
Digital libraries and archives are increasingly faced with a significant backlog of unprocessed data along with an accelerating stream of incoming material. These data often arrive from donor organizations, institutions, and individuals on hard drives, optical and magnetic disks, flash memory devices, and even complete hardware (traditional desktop computers and mobile systems). &lt;br /&gt;
&lt;br /&gt;
Information on these devices may be sensitive, obscured by operating system arcana, or require specialized tools and procedures to parse. Furthermore, the sheer volume of materials being handled means that even simple tasks such as providing useful content reports can be impractical (or impossible) in current workflows.&lt;br /&gt;
&lt;br /&gt;
Many of the tasks currently associated with data triage and analysis can be simplified and performed with improved coverage and accuracy through the use of open source digital forensics tools. In this talk we will discuss recent developments in providing digital librarians and archivists with simple, open source tools to accomplish these tasks.  We will discuss tools and methods be tested, developed and packaged as part of the [http://bitcurator.net BitCurator] project.  These tools can be used to reduce or eliminate laborious, error-prone tasks in existing workflows and put valuable time back into the hands of digital librarians and archivists -- time better used to identify and tackle complex tasks that *cannot* be solved by software.&lt;br /&gt;
&lt;br /&gt;
== Finding Movies with FRBR and Facets ==&lt;br /&gt;
 &lt;br /&gt;
* Kelley McGrath, University of Oregon, kelleym@uoregon.edu&lt;br /&gt;
&lt;br /&gt;
How might the Functional Requirements for Bibliographic Records (FRBR) model and faceted navigation improve access to film and video in libraries? I will describe the design and implementation of a FRBR-inspired prototype discovery interface ([http://blazing-sunset-24.heroku.com/ http://blazing-sunset-24.heroku.com/]) using Solr and Blacklight . This approach demonstrates how FRBR can enable a work-centric view that is focused on the original movie or program while supporting users in selecting an appropriate version.&lt;br /&gt;
&lt;br /&gt;
The prototype features two sets of facets, which independently address two important information needs: (1) &amp;quot;What kind of movie or program do you want to watch?&amp;quot; (e.g., a 1970s TV sitcom, something directed by Kurosawa, or an early German horror film); (2) &amp;quot;How do you want to watch it? Where do you want to get it from?&amp;quot; (e.g., on Blu-ray, with Spanish subtitles, available at the local public library). This structure enables patrons to narrow, broaden and pivot across facet values instead of limiting them to the tree-structured hierarchy common with existing FRBR applications. &lt;br /&gt;
&lt;br /&gt;
This type of interface requires controlled data values mapped to FRBR group 1 entities, which in many cases are not available in existing MARC bibliographic records. I will discuss ongoing work using the XC Metadata Services Toolkit ([http://www.extensiblecatalog.org/ http://www.extensiblecatalog.org/]) to extract and normalize data from existing MARC records for videos in order to populate a FRBRized, faceted discovery interface.&lt;br /&gt;
&lt;br /&gt;
==Escaping the Black Box — Building a Platform to Foster Collaborative Innovation==&lt;br /&gt;
&lt;br /&gt;
* Karen Coombs, OCLC, coombsk@oclc.org&lt;br /&gt;
* Kathryn Harnish, OCLC harnishk@oclc.org&lt;br /&gt;
&lt;br /&gt;
Exposed Web services offer an unprecedented opportunity for collaborative innovation — that’s one of the hallmarks of Web-based services like Amazon, Google, and Facebook.  These environments are popular not only for their native feature sets, but also for the array of community-developed apps that can run in them.  The creativity of the development communities that work in these systems brings new value to all types of users.&lt;br /&gt;
&lt;br /&gt;
What if the library community could realize this same level of collaborative innovation around its systems?  What kinds of support would be necessary to transform library systems from “black boxes” to more open, accessible environments in which value is created and multiplied by the user community?&lt;br /&gt;
&lt;br /&gt;
In this session, we’ll discuss the challenges and opportunities OCLC faced in creating just that kind of environment.  The recently-released OCLC “cooperative platform” provides improved access to a wide variety of OCLC’s data and services, allowing library developers and other interested partners to collaborate, innovate, and share new solutions with fellow libraries.  We’ll describe the open standards and technologies we’ve put in play in as we:&lt;br /&gt;
* exposed robust Web services that provide access to both data and business logic; &lt;br /&gt;
* created an architecture for integrating community-built applications in OCLC (and other) products; and &lt;br /&gt;
* developed an infrastructure to support community development, collaboration, and app sharing&lt;br /&gt;
&lt;br /&gt;
Learn how OCLC is helping to open the “black box” -- and give libraries the freedom to become true partners in the evolution of their library systems.&lt;br /&gt;
&lt;br /&gt;
== Code inheritance; or, The Ghosts of Perls Past  ==&lt;br /&gt;
&lt;br /&gt;
* Jon Gorman, University of Illinois, jtgorman@illinois.ed&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Any organization has a history not found in its archives or museums. Mysteries exist that origins are lost to the collective institutional knowledge.  Despite what has been forgotten by humans, our servers and computers still keep running. Instructions crafted long ago execute like digital ghosts following orders of masters who have long since left.&lt;br /&gt;
&lt;br /&gt;
The University of Illinois has a fair amount of Perl code created by several different developers. This code includes software that handles our data feeds coming both in and out of campus, reports against our Voyager system, some web applications, and more.&lt;br /&gt;
&lt;br /&gt;
I'll touch a little on the historical legacy and why Perl is used. From there I'll share some tips, best practices, and some of the mistakes I've made in trying to maintain this code. Most of the advice will transition to any language, but code and libraries discussed will be Perl. The presentation will also touch on some internal debate on whether or not to port parts of our Perl codebase.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Recorded Radio/TV broadcasts streamed for library users ==&lt;br /&gt;
&lt;br /&gt;
* Kåre Fiedler Christiansen, The State and University Library Denmark, kfc@statsbiblioteket.dk&lt;br /&gt;
* Mads Villadsen, The State and University Library Denmark, mv@statsbiblioteket.dk&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Provide online access to the Radio/TV collection,&amp;quot; my boss said. About 500,000&lt;br /&gt;
hours of Danish broacast radio and TV. Easy, right? Well, half a year later &lt;br /&gt;
we'd done it, but it turned out to involve practically every it employee in the &lt;br /&gt;
library and quite a few non-technical people as well.&lt;br /&gt;
&lt;br /&gt;
Combining our Fedora-based DOMS repository system with our Lucene-based Summa&lt;br /&gt;
search system with our WAYF-based single-signon system with an upgrade of our&lt;br /&gt;
SAN system for enough speed to deliver the content with an ffmpeg-based &lt;br /&gt;
transcoding workflow system with a Wowza-based streaming server, and sprinkling&lt;br /&gt;
it all with a nice user-friendly web frontend turned out to be quite a challenge,&lt;br /&gt;
but also one of the most engaging experiences for a long time.&lt;br /&gt;
&lt;br /&gt;
Of course we were immidiately shut down, since the legal details weren't quite&lt;br /&gt;
as clear as we thought they were, but take an exclusive preview at &lt;br /&gt;
http://developer.statsbiblioteket.dk/kultur/ - username/password: code4lib.&lt;br /&gt;
&lt;br /&gt;
== NoSQL Bibliographic Records: Implementing a Native FRBR Datastore with Redis ==&lt;br /&gt;
* Jeremy Nelson, Colorado College, jeremy.nelson@coloradocollege.edu&lt;br /&gt;
&lt;br /&gt;
In October, the Library of Congress issued a news release, &amp;quot;A Bibliographic Framework for the Digital Age&amp;quot; outlining a list of requirements for a New Bibliographic Framework Environment. Responding to this challenge, this talk will demonstrate a Redis (http://redis.io) FRBR datastore proof-of-concept that, with a lightweight python-based interface, can meet these requirements. &lt;br /&gt;
&lt;br /&gt;
Because FRBR is an Entity-Relationship model; it is easily implemented as key-value within the primitive data structures provided by Redis.  Redis' flexibility makes it easy to associate arbitrary metadata and vocabularies, like MARC, METS, VRA or MODS, with FRBR entities and inter-operate with legacy and emerging standards and practices like RDA Vocabularies and LinkedData.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Upgrading from Catalog to Discovery Environment: A Consortial Approach ==&lt;br /&gt;
 &lt;br /&gt;
* Spencer Lamm, Swarthmore College, slamm1@swarthmore.edu&lt;br /&gt;
* Chelsea Lobdell, Swarthmore College, clobdel1@swarthmore.edu&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Almost two years ago the Tri-College Consortium of Haverford, Swarthmore, and Bryn Mawr Colleges embarked upon a journey to provide enhanced end-user experience and discoverability with our library applications. Our solution was to implement an integration of ExLibris's Primo Central into Villanova's VuFind for a dual-channel searching experience. We present a case study of the collaborative and technical aspects of our process.&lt;br /&gt;
&lt;br /&gt;
At a high level we will describe our approach to project management and decision making.  We used a multi-tiered structure of working groups with an iterative design-feedback implementation cycle.  We will relay lessons learned from our experience: successes, failures, and unexpected hurdles.&lt;br /&gt;
&lt;br /&gt;
At a lower, technical level we will discuss the vufind search module architecture; the workflow of creating a new search channel; a Primo API parser; and the data structures of the Primo API response and the Primo SearchObject. Time permitting, we will also outline how we modified VuFind's Innovative driver to work with our ILS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Improving geospatial data access for researchers and students ==&lt;br /&gt;
 &lt;br /&gt;
* Dileshni Jayasinghe, Scholars Portal, University of Toronto, d.jayasinghe@utoronto.ca&lt;br /&gt;
* Sepehr Mavedati, Scholars Portal, University of Toronto, sepehr.mavedati@utoronto.ca&lt;br /&gt;
&lt;br /&gt;
Scholars GeoPortal (http://geo.scholarsportal.info) was created as a platform for online delivery of geospatial data resources to the Ontario Council of University Libraries community. Prior to the start of this project, each institution was storing data locally, and had its own practice for distributing datasets to users. This ranged from home grown online data delivery systems to burning data on to DVDs for each individual request. Most institutions had limited resources and expertise to create and maintain a sophisticated delivery system on their own. Led by OCUL Map, GIS librarians, staff at Scholars Portal in partnership with the Government of Ontario, the GeoPortal project began in 2009.&lt;br /&gt;
&lt;br /&gt;
Our talk will focus on the design and architecture of Scholars Portal's solution to support maps and geospatial data, and how we distribute these data collections to our users. &lt;br /&gt;
&lt;br /&gt;
The system consists of 4 main components: metadata management system, map server, spatial database, and the web application.&lt;br /&gt;
&lt;br /&gt;
*Metadata Management: customized metadata editor with data hosted in MarkLogic, providing text and spatial queries&lt;br /&gt;
*Map Server: ArcGIS Server&lt;br /&gt;
*Spatial database: MS SQL Server with spatial extension&lt;br /&gt;
*Web application: Javascript web application using Dojo and Esri’s Javascript API&lt;br /&gt;
 &lt;br /&gt;
For other code4libbers who are interested in a similar system, we will also discuss the open source alternatives for each component (GeoNetwork, MapServer, etc.), and challenges and limitations we faced trying to use some of these tools. We'd also like to pick your brains on how we can make this application better. What can we do differently?&lt;br /&gt;
&lt;br /&gt;
== LibX 2.0 ==&lt;br /&gt;
 &lt;br /&gt;
* Godmar Back, Virginia Tech, godmar@gmail.com&lt;br /&gt;
&lt;br /&gt;
We would like to provide the Code4Lib community with an update on what we've accomplished with LibX (which we last presented in 2009) - where we've gone, what our users are thinking, and how both its technology and its adapter community can be included in the code4lib world. We've grown to our 200,00 users, have a sleek, newly designed user interface, support for Google Chrome. We're now directly consuming many web services. Our Libapp Builders allows anyone to place results, cue, tutorials and other library-related information into pages.&lt;br /&gt;
&lt;br /&gt;
== Introducing the DuraSpace Incubator ==&lt;br /&gt;
&lt;br /&gt;
* Jonathan Markow, DuraSpace, jjmarkow@duraspace.org&lt;br /&gt;
&lt;br /&gt;
DuraSpace is planning to launch a new incubation program for the benefit of open source projects that wish to become part of our organization, in the interest of helping them to become sustainable, community-driven projects and supporting them afterwards with umbrella services that help them to thrive.  From time to time DuraSpace becomes aware of open source software projects in the preservation, archiving, or repository space that are in search of a community “home”.  The motivation might be that the project is simply trying to attract more developers, that it would like to develop a more robust community of users and service providers, that its current organizational sponsorship is in question, or that it would like to take advantage of an existing and compatible organization's best practices and administrative infrastructure rather than create a new one of its own. DuraSpace is now prepared to leverage its resources, experience, and reputation in the community to help these projects become, or continue to be, successful. Projects emerging from incubation will become officially recognized as DuraSpace projects.  This briefing presents highlights of the DuraSpace Incubator and invites questions and feedback from participants.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== In-browser data storage and me ==&lt;br /&gt;
&lt;br /&gt;
* Jason Casden, North Carolina State University Libraries, jason_casden@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
When it comes to storing data in web browsers on a semi-persistent basis, there are several partially-adopted, semi-deprecated, product-specific, or even universally accepted options. These include models such as key-value stores, relational databases, and object stores. I will present some of these options and discuss possible applications of these technologies in library services. In addition to quoting heavily from Mark Pilgrim's excellent chapter on this topic, I will weave in my own experience utilizing in-browser data storage in an iPad-based data collection tool to successfully improve performance and data stability while reducing network dependence. See also: HTML5.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Coding for the past, archiving for the future … and the Salman Rushdie Papers ==&lt;br /&gt;
 &lt;br /&gt;
* Peter Hornsby, Emory University Libraries, phornsb@emory.edu&lt;br /&gt;
&lt;br /&gt;
Cultural heritage production is moving to the digital medium and libraries use of repository solutions such as Fedora Commons and DSpace are a solid response to this change. But how do we go from, for instance a selection of 90's computing technology to  a collection of digital objects ready for ingest into your institution's local repository? Once you have ingested your digital objects how are you going to provide access to these resources? The arrival of the Salman Rushdie Papers, which contain 10 years of Sir Salman Rushdie's digital life, gave Emory University Libraries the opportunity to explore these questions. I would like to to talk about the approach the Emory University Libraries adopted, what we learned and the coding challenges that remain.&lt;br /&gt;
&lt;br /&gt;
==  Indexing big data with Tika, Solr &amp;amp; map-reduce ==&lt;br /&gt;
&lt;br /&gt;
* Scott Fisher, California Digital Library, scott.fisher AT ucop BORK edu&lt;br /&gt;
* Erik Hetzner, California Digital Library, erik.hetzner AT ucop BORK edu&lt;br /&gt;
&lt;br /&gt;
The Web Archiving Service at the California Digital Library has&lt;br /&gt;
crawled a large amount of data, in every format found on the web: 30&lt;br /&gt;
TB, comprising about 600 million fetched URLs. In this talk we will&lt;br /&gt;
discuss how we parsed this data using Tika and map-reduce, and how we&lt;br /&gt;
indexed this data with Solr, tweaked the relevance ranking, and were&lt;br /&gt;
able to provide our users with a better search experience.&lt;br /&gt;
&lt;br /&gt;
== ALL TEH METADATAS! or How we use RDF to keep all of the digital object metadata formats thrown at us. ==&lt;br /&gt;
&lt;br /&gt;
* Declan Fleming, University of California, San Diego, dfleming AT ucsd DING edu&lt;br /&gt;
&lt;br /&gt;
What's the right metadata standard to use for a digital repository?  There isn't just one standard that fits documents, videos, newspapers, audio files, local data, etc.  And there is no standard to rule them all.  So what do you do?  At UC San Diego Libraries, we went down a conceptual level and attempted to hold every piece of metadata and give each holding place some context, hopefully in a common namespace.  RDF has proven to be the ideal solution, and allows us to work with MODS, PREMIS, MIX, and just about anything else we've tried.  It also opens up the potential for data re-use and authority control as other metadata owners start thinking about and expressing their data in the same way.  I'll talk about our workflow which takes metadata from a stew of various sources (CSV dumps, spreadsheet data of varying richness, MARC data, and MODS data), normalizes them into METS by our Metadata Specialists who create an assembly plan, and then ingests them into our digital asset management system.  The result is a [http://dl.dropbox.com/u/6923768/Work/DAMS%20object%20rdf%20graph.png beautiful graph] of RDF triples with metadata poised to be expressed as [https://libraries.ucsd.edu/digital/ HTML], RSS, METS, XML, and opens linked data possibilities that we are just starting to explore.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== HathiTrust Large Scale Search: Scalability meets Usability ==&lt;br /&gt;
&lt;br /&gt;
* Tom Burton-West, DLPS, University of Michigan Library, tburtonw AT umich edu&lt;br /&gt;
&lt;br /&gt;
[http://www.hathitrust.org/ HathiTrust Large-Scale search] provides full-text search services over  nearly 10 million full-text books using Solr for the back-end.  Our index is around 5-6 TB in size and each shard contains over 3 billion unique terms due to content in over 400 languages and dirty OCR.&lt;br /&gt;
&lt;br /&gt;
Searching the full-text of 10 million books often results in very large result sets.  By conference time a number of [http://www.hathitrust.org/full-text-search-features-and-analysis features] designed to help users narrow down large result sets and to do exploratory searching will either be in production or in preparation for release. There are often trade-offs between implementing desirable user features and keeping response time reasonable in addition to the traditional search trade-offs of precision versus recall.  &lt;br /&gt;
&lt;br /&gt;
We will discuss various [http://www.hathitrust.org/blogs/large-scale-search scalability] and usability issues including:&lt;br /&gt;
* Trade-offs between desirable user features and keeping response time reasonable and scalable &lt;br /&gt;
* Our solution to providing the ability to search within the 10 million books and also search within each book&lt;br /&gt;
* Migrating the [http://babel.hathitrust.org/cgi/mb personal collection builder application] from a separate Solr instance to an app which uses the same back-end as full-text search.&lt;br /&gt;
* Design of a scalable multilingual spelling suggester&lt;br /&gt;
* Providing advanced search features combining MARC metadata with OCR&lt;br /&gt;
** The dismax mm and tie parameters&lt;br /&gt;
** Weighting issues and tuning relevance ranking&lt;br /&gt;
* Displaying  only the most &amp;quot;relevant&amp;quot; facets&lt;br /&gt;
* Tuning relevance ranking &lt;br /&gt;
* Dirty OCR issues&lt;br /&gt;
* CJK tokenizing and other multilingual issues.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== DMPTool: Guidance and resources to build a data management plan ==&lt;br /&gt;
Marisa Strong, California Digital Libary, marisa.strong@ucop.edu&lt;br /&gt;
&lt;br /&gt;
A number of U.S. funding agencies such as the National Science Foundation require researchers to supply detailed plans for managing research data, called Data Management Plans. To help researchers with this requirement, the California Digital Library (CDL) along with several organizations, collaborated to develop the DMPTool. The goal is to provide researchers with guidance, links to resources and help with writing data management plans.&lt;br /&gt;
This open-source, Ruby on Rails software tool is hosted on a SLES VM by CDL. The tool is integrated with Shibboleth, federated single sign-on software, which allows users to login via their home institutions. We had a geographically distributed development team sharing their code on Bitbucket.&lt;br /&gt;
This talk will demo features of the application, the Shibboleth login architecture, as well as highlight the agile development practices and methods used to successfully design and build the application on an aggressive schedule.&lt;br /&gt;
&lt;br /&gt;
== The Islandora Open Source Framework for Digital Asset Management ==&lt;br /&gt;
&lt;br /&gt;
* Keith Folsom, Orbis Cascade Alliance, kfolsom@uoregon.edu&lt;br /&gt;
&lt;br /&gt;
Managing digital content is a challenging task—becoming even more so &lt;br /&gt;
as the volumes and types of content increase at what seems an exponential &lt;br /&gt;
rate.  Though there are good commercial management systems available, &lt;br /&gt;
having competing and potentially more configurable open source options is ideal.  &lt;br /&gt;
One such option is Islandora—an open source framework that wraps a Drupal &lt;br /&gt;
front-end around the Fedora digital object management and storage system.  &lt;br /&gt;
&lt;br /&gt;
My talk will serve as an introduction to the Islandora framework—including a&lt;br /&gt;
discussion of Fedora’s digital object model and content model architecture; &lt;br /&gt;
how Islandora exposes the power of Fedora for storage, discovery, and retrieval &lt;br /&gt;
of data; and the wide variety of underlying open source software and technology &lt;br /&gt;
that enables the system.   I will also give a quick tour of a stock Islandora &lt;br /&gt;
installation and provide tips on navigating the documentation for set-up and &lt;br /&gt;
use of this powerful framework.&lt;br /&gt;
&lt;br /&gt;
== What do the NISO IOTA OpenURL quality reports tell us about the future of OpenURL linking? ==&lt;br /&gt;
&lt;br /&gt;
* Adam Chandler, Cornell University, alc28@cornell.edu&lt;br /&gt;
&lt;br /&gt;
NISO IOTA (http://openurlquality.niso.org/) is an initiative that makes use of log files from various institutions and vendors to analyze element frequency and patterns contained within OpenURL requests.  The reports created from this analysis inform vendors about where to make improvements to their OpenURLs.  In this talk, the chair of the IOTA working group will share what the group has learned about the differences in quality across OpenURL sources.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &amp;quot;CALIL.JP&amp;quot; Open Libraries by web-scraping. - Introducing Library API from Japan ==&lt;br /&gt;
&lt;br /&gt;
* Ryuuji Yoshimoto, Nota Inc. Engineer, ryuuji@notaland.com&lt;br /&gt;
&lt;br /&gt;
I am an engineer at Nota Inc., a start-up company for web services. &amp;quot;CALIL&amp;quot; (http://calil.jp/) is a web service for library users in Japan. (Not only for librarians but also for general patrons.)&lt;br /&gt;
&lt;br /&gt;
CALIL allows users search books from multiple libraries nearby, and get realtime holding status. Our service supports over 5,800 libraries. &lt;br /&gt;
CALIL supports public, university, and other many special libraries in Japan. The service can search 88% of collections of all public libraries in Japan.&lt;br /&gt;
Public libraries in Japan do not have an unified catalogue like OCLC.&lt;br /&gt;
Web OPACs in Japan are generally very slow and their usability is low. &lt;br /&gt;
We develop a comprehensive scraping service over 2000 web OPACs and it supports recognize real-time holding status on them as well.&lt;br /&gt;
This service can be used as for substitution of OPACs provided by libraries. It provides more useful, speedy and open service.&lt;br /&gt;
&lt;br /&gt;
Our scraping platform also provides API for free.&lt;br /&gt;
Any developer can access realtime holding status at almost all the libraries in Japan by one API.&lt;br /&gt;
Since the launch in 2010, many apps on iPhone and Android are developed by many third party developers.&lt;br /&gt;
And it allows many web service connect to library (book shelf, review etc).&lt;br /&gt;
&lt;br /&gt;
CALIL is written by 100% pure Python and running on Google App Engine.&lt;br /&gt;
&lt;br /&gt;
I will introduce about &amp;quot;CALIL&amp;quot;, &amp;quot;CALIL Library API&amp;quot;, and its methodology. Open Libraries in Japan to World-Coders!!&lt;br /&gt;
&lt;br /&gt;
== Discovering Digital Library User Behavior with Google Analytics==&lt;br /&gt;
&lt;br /&gt;
* Kirk Hess, Digital Humanities Specialist, University of Illinois Urbana-Champaign, kirkhess@illinois.edu&lt;br /&gt;
&lt;br /&gt;
Digital library administrators are frequently asked questions like &amp;quot;How many times was that document downloaded&amp;quot;, or &amp;quot;What’s the most popular book in our collection?&amp;quot; Conventional web logging software, such as AWStats, can only answer those questions some of the time, and there’s always the question of whether or not the data is polluted by non-users, such as spiders and crawlers. Google Analytics, (http://google.com/analytics/ ) , a JavaScript-based solution that excludes most crawlers and bots, shows how users found your site and how they explored it.&lt;br /&gt;
 &lt;br /&gt;
The presentation will review tracking search queries, adding events such as clicking external links or downloading files, and custom variables, to track user behavior that is normally difficult to track. We'll also discuss using jQuery scripts to add tracking code to the page without having to modify the underlying web application. Once you've collected data, you may use the Google Analytics API to extract data and integrate it with data from your digital repository to show granular data about individual items in your Digital Library. Finally, we'll discuss how this information allows you to improve the user experience, and summarize some of the research we are doing with our digital repository and the data gathered from Google Analytics.&lt;br /&gt;
&lt;br /&gt;
== Introducing Kuali OLE 0.3==&lt;br /&gt;
&lt;br /&gt;
* Rich Slabach, Quality Assurance Manager, Kuali OLE, rlslabac at indiana dot edu&lt;br /&gt;
* Nianli Ma, Technical Architect, Kuali OLE, Indiana University, nianma at indiana dot edu&lt;br /&gt;
&lt;br /&gt;
This research update will feature technical staff from the Kuali Open Library Environment (OLE) project, which is in its second year of building a community-source library management environment. Operating since July 2010, and supported by The Andrew W. Mellon Foundation, Kuali OLE is the one of the largest academic library software collaborations in the United States. In this presentation we will discuss the Kuali OLE Year 2 Roadmap as well as key components of the system architecture, additionally we will demonstrate our Kuali OLE 0.3 release from November 2011 with our cloud-based test drive implementation and our well documented driver's manual. This will lead to a better understanding of how this code base could support library management at your home institution.&lt;br /&gt;
 &lt;br /&gt;
We will also discuss opportunities for engagement with Kuali OLE and for adoption and use of the software as well as hear more about our plans for long-term sustainability. For more on our current software see - https://wiki.kuali.org/display/OLE/OLE+and+Docstore+Server+Installation&lt;br /&gt;
&lt;br /&gt;
== UDFR: Building a Registry using Open-Source Semantic Software ==&lt;br /&gt;
&lt;br /&gt;
* Stephen Abrams, Associate Director, UC3, California Digital Library, stephen.abrams AT ucop DING edu&lt;br /&gt;
* Lisa Dawn Colvin, UDFR Project Manager, California Digital Library, lisa.colvin AT ucop DING edu&lt;br /&gt;
&lt;br /&gt;
Fundamental to effective long-term preservation analysis, planning, and intervention is the deep understanding of the diverse digital formats used to represent content. The Unified Digital Format Registry project (UDFR, https://bitbucket.org/udfr/main/wiki/Home) will provide an open source platform for an online, semantically-enabled registry of significant format representation information.&lt;br /&gt;
&lt;br /&gt;
We will give an introduction to the UDFR tool and its use within a preservation process.&lt;br /&gt;
&lt;br /&gt;
We will also discuss our experiences of integrating disparate data sources and models into RDF: describing our iterative data modeling process and decisions around integrating vocabularies, data sources and provenance representation. &lt;br /&gt;
&lt;br /&gt;
Finally, we will share how we extended an existing open-source semantic wiki tool, OntoWiki, to create the registry.&lt;br /&gt;
&lt;br /&gt;
== Sirsi Symphony: Developing a &amp;quot;web service&amp;quot; to provide real time bibliographic information to Blacklight. ==&lt;br /&gt;
&lt;br /&gt;
* John Pillans, Enterprise Software, Library Systems, Configuration Manager Kuali OLE, Indiana University, jpillan@indiana.edu&lt;br /&gt;
&lt;br /&gt;
Indiana University Libraries is currently in the process of implementing Blacklight as its discovery layer on top of Sirsi Symphony.  One aspect of Blacklight that must be developed locally is providing circulation status and holdings information to the user.  We have developed a &amp;quot;web service&amp;quot; which provides the bibliographic data, formatted MARC holdings data (if present), and item data with current circulation information to the Blacklight system in XML.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Open Sourcing the Dream: Making the Read/Write Library ==&lt;br /&gt;
 &lt;br /&gt;
* Margaret Heller, Read/Write Library Chicago and Dominican University, mheller@dom.edu&lt;br /&gt;
&lt;br /&gt;
You met the Chicago Underground Library last year, now meet The Read/Write Library Chicago.It's a new name, a new space, and new opportunities to develop our catalog. We are working on creating the open source version of our ideas with a distributed team of interested volunteers, plus experimenting with innovative partnerships with the Chicago technology community. This talk will share what the team and open source project look like, what we are doing with our data, and how we finally learned to stop worrying and love Git. &lt;br /&gt;
&lt;br /&gt;
== Interactive maps: an easy-to-maintain and scalable approach ==&lt;br /&gt;
 &lt;br /&gt;
* Mariela Gunn, Oakland University, gunn@oakland.edu&lt;br /&gt;
&lt;br /&gt;
Developing interactive maps of a library building presents a unique challenge in an institution with limited web services personnel. Our technical expectations are high: we want the maps to have engaging interactivity, to be modular so we can link to different services represented in them, and to be scalable so that we can integrate data-driven elements. Our content needs are ever changing: we want to have distributed authorship of content through a user-friendly interface that can be used by all librarians without a steep learning curve.&lt;br /&gt;
&lt;br /&gt;
This talk will focus on the design of interactive maps by a group of our undergraduate student interns who selected a web application -- Maps Alive -- for the task with ease of use and scalability in mind and set up a structure that can grow and change. The pros and cons of the application will be discussed, as well as tips on how to evaluate potential tools and make the best use of them through a modular and flexible approach to interactive maps. Involving students as designers and decision-makers in technology-related projects will be highlighted too.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Getting the Content out of CONTENTdm: Building a Modular UI Template for Digital Collections  ==&lt;br /&gt;
 &lt;br /&gt;
* Devin Becker, University of Idaho, dbecker@uidaho.edu&lt;br /&gt;
&lt;br /&gt;
With the advent of iterations 6 and 6.1, CONTENTdm redesigned the basic user interfaces for individual collections, improving on what was already a robust and reliable system for archiving and displaying digital items. The majority of the items in these collections, however, still rarely see the light of a user's screen. Moreover, the typical modes for browsing these collections within the system are geared primarily to those who are already familiar with such systems or who have a specific need to see certain items.  &lt;br /&gt;
&lt;br /&gt;
To invite more casual browsing and easier discovery of our collections, the University of Idaho Library's Digital Initiatives department designed a scalable and modular interface for all of our collections with an increased emphasis on the time, location, and larger display of our images and other digital items. To do so, we used free and easy-to-use Javascript libraries and online applications (including Jquery, Google Fusion Tables, Simile Timeline, ImageFlow, and Tagcrowd.com), together with several, simple XSL stylesheets that utilize the metadata and persistent linking capabilities of the CONTENTdm database, to design a basic template with several browsing options (timeline, map, tag cloud, etc.) that can be used for any collection. This talk will detail the coding, methods, and metadata implemented for the redesign.&lt;br /&gt;
&lt;br /&gt;
== saveMLAK: How Librarians, Curators, Archivists and Library Engineers Work Together with Semantic MediaWiki after the Great Earthquake of Japan ==&lt;br /&gt;
&lt;br /&gt;
* Yuka Egusa, Senior Researcher of National Institute of Educational Policy Research, yuka_at_nier.go.jp&lt;br /&gt;
* Makoto Okamoto, Chief Editor of Academic Resource Guide (ARG), arg.editor_at_gmail.com&lt;br /&gt;
&lt;br /&gt;
In March 11th 2011, the biggest earthquake and tsunami in the history attacked a large area of northern east region of Japan. A lot of people have worked together to save people in the area. For library community, a wiki named &amp;quot;savelibrary&amp;quot; was launched for sharing information on damages and rescues on the next day of the earthquake. Later then people from museum curators, archivists and community learning centers started similar projects. In April we joined to a project &amp;quot;saveMLAK&amp;quot;, and launched a wiki site using Semantic MediaWiki under http://savemlak.jp/.&lt;br /&gt;
&lt;br /&gt;
As of November 2011, information on over 13,000 cultural organizations are posted on the site by 269 contributors since the launch. The gathered information are organized along with Wiki categories of each type of facilities such library, museum, school, etc. We have held eight edit-a-thons to encourage people to contribute to the wiki.&lt;br /&gt;
&lt;br /&gt;
We will report our activity, how the libraries and museums were damaged and have been recovered with lots of efforts, and how we can do a new style of collaboration with MLAK community, Wiki and other voluntary communities at the crisis.&lt;br /&gt;
&lt;br /&gt;
== Kill the search button II - the handheld devices are coming ==&lt;br /&gt;
&lt;br /&gt;
* Jørn Thøgersen, Statsbiblioteket/State and University Library, Aarhus, Denmark. jt@statsbiblioteket.dk&lt;br /&gt;
* Michael Poltorak Nielsen, Statsbiblioteket/State and University Library, Aarhus, Denmark. mn@statsbiblioteket.dk, (aka the Danes - some of them).&lt;br /&gt;
&lt;br /&gt;
Web based library search engines are traditionally operated using keys, input fields, buttons, and links. Being equipped with touch screens, accelerometers, GPS's, and cameras, smartphones and tablets offer a whole new range of input options.&lt;br /&gt;
&lt;br /&gt;
In this talk we'll demonstrate some of our ideas of how to&lt;br /&gt;
utilise these new input options interacting with a search engine. The basic idea is to have no traditional GUI input elements, but only use touch interactions (pinch, zoom, swipe, long-press, etc) and gestures (shake, tilt, turn, etc.). Using these interactions, we’ll demonstrate how to:&lt;br /&gt;
&lt;br /&gt;
* do searches&lt;br /&gt;
* toggle search result views&lt;br /&gt;
* switch pages&lt;br /&gt;
* request materials, add to favourites&lt;br /&gt;
* interact with your stuff, renew items &lt;br /&gt;
&lt;br /&gt;
We'll also show you some (conceptual) ideas about using the device camera for locating and checking out materials.&lt;br /&gt;
&lt;br /&gt;
On a general level, what we are trying to achieve is a move away from a web based paradigm and establish new ways of interaction better suited to the new devices and on their own terms. The demonstration will feature working mobile prototypes including both native apps (iPhone) and web apps. In both cases they will run on live data from our OPAC on www.statsbiblioteket.dk/search/&lt;br /&gt;
&lt;br /&gt;
This talk is actually also a continuation of our Code4Lib 2010 talk called &amp;quot;Kill The Search Button&amp;quot; (http://code4lib.org/conference/2010/schedule), which we unfortunately never got around to do, due to a Danish blizzard.&lt;br /&gt;
&lt;br /&gt;
==Speaking in code: talking tech with humans (and librarians)==&lt;br /&gt;
* Erin White, Virginia Commonwealth University Libraries, erwhite@vcu.edu&lt;br /&gt;
&lt;br /&gt;
We do awesome work, right? But what's the best way to communicate that work with non-geek stakeholders within our organizations? I'll present some ideas on how to communicate tech with those who don't always speak the language fluently. This'll include pitching new projects; communicating about existing projects; and dealing with project maintenance and problem-solving. I'll share some tips for explaining systems changes and problems, how to use help tickets as teachable moments for you or librarians, updating documentation, etc.&lt;br /&gt;
&lt;br /&gt;
== Building a Code4Lib 2012 Conference Mobile App with the Kuali Mobility Framework ==&lt;br /&gt;
&lt;br /&gt;
* Michelle Suranofsky, Lehigh University, michelle dot suranofsky at lehigh dot edu&lt;br /&gt;
* Tod Olson, University of Chicago, tod at uchicago dot edu&lt;br /&gt;
&lt;br /&gt;
Hot off the heals of the Kuali Days 2011 Conference, we thought it would be fun to take the newly released Kuali Mobility for Enterprise framework for a test drive by creating a Code4Lib Conference Mobile App.  &lt;br /&gt;
&lt;br /&gt;
[http://kuali.org/mobility Kuali Mobility for Enterprise (KME)] is an open source framework for developing and deploying applications to connect mobile devices to an institution's information resources.  Applications may be deployed as mobile websites or as installable apps.  The KME framework makes heavy use of HTML5, CSS, and Javascript, and builds on other open source projects like PhoneGap and JQuery Mobile.  &lt;br /&gt;
&lt;br /&gt;
We will discuss the mechanics of the Kuali Mobility framework along with the experience using it to create a mobile app. for the Code4Lib conference.&lt;br /&gt;
&lt;br /&gt;
== The ARCHIVEMATICA digital preservation system ==&lt;br /&gt;
 &lt;br /&gt;
* Peter Van Garderen, Archivematica Project Manager, [http://artefactual.com Artefactual Systems], peter at artefactual dot com&lt;br /&gt;
* Courtney Mumma, Archivematica Community Manager, courtney at artefactual dot com&lt;br /&gt;
&lt;br /&gt;
The open source (AGPL3) [http://archivematica.org Archivematica] digital preservation system uses a micro-services architecture to integrate a suite of Linux utilities into workflow pipelines. It is designed as a backend tool for archivists and librarians managing digital collections and digital preservation responsibilities. We use Google Gearman for job scheduling and load balancing as well as Django (python) for a web-based administration interface that monitors and controls the processing of files in the pipelines. The system creates standards-compliant (e.g. METS, PREMIS, Bagit) archival packages as well as a registry interface to monitor format policies. This system is designed to provide the technical component for ISO 14721 (OAIS) and ISO 16363 (TRAC) compliant Trusthworthy Digital Repositories. The recent 0.8 release is the last alpha. Over winter 2012 we are continuing with scalability testing and tuning, adding ElasticSearch indexing, SWORD deposit support, interfaces for Dspace, ContentDM, XTF; all for inclusion in the 0.9-beta release sometime in Spring 2012. The presentation will give a quick demo of Archivematica's features as well as discuss technical architecture, APIs, development roadmap, user base, community building, project management, etc.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Virtual Integrated Search - on-the-fly merging of relevancy ranked searches ==&lt;br /&gt;
&lt;br /&gt;
* Mads Villadsen, The State and University Library Denmark, mv@statsbiblioteket.dk&lt;br /&gt;
&lt;br /&gt;
What do you do when you have an integrated search system and the users want data at the article level? What we did was to try and get the data from the publishers - and when that failed we went with Summon for the article data while keeping our bibliographic records (and more) in our own system.&lt;br /&gt;
&lt;br /&gt;
So how’s that working out for us?&lt;br /&gt;
&lt;br /&gt;
We didn’t want to give up on our overall goal of having a single unified result set which meant we had to do something out of the ordinary.&lt;br /&gt;
&lt;br /&gt;
We struck a deal with Serials Solutions that allowed us to apply our technical know-how and sprinkle fairy dust on our queries thereby achieving a proper relevancy ranked merging of results from our own index with the results from Summon. We gave a lightning talk about some of these ideas at last year's code4lib.&lt;br /&gt;
&lt;br /&gt;
We have been running this &amp;quot;Virtual Integrated Search&amp;quot; in production since August and the end users haven't come at us with their pitch forks yet so we assume they are still able to find what they are looking for.&lt;br /&gt;
&lt;br /&gt;
Just to be sure we will be performing a usability test in November 2011 that will hopefully guide our future development.&lt;br /&gt;
&lt;br /&gt;
I will cover what goes into making fairy dust (&amp;quot;how it works&amp;quot;, &amp;quot;what doesn't work&amp;quot;) as well as some of the results from the usability test (&amp;quot;does it actually work?&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
http://www.statsbiblioteket.dk/search/&lt;br /&gt;
&lt;br /&gt;
== Kuali Rice and preparing for OLE ==&lt;br /&gt;
&lt;br /&gt;
* Tod Olson, University of Chicago, tod at uchicago dot edu&lt;br /&gt;
* Michelle Suranofsky, Lehigh University, michelle dot suranofsky at lehigh dot edu&lt;br /&gt;
&lt;br /&gt;
Kuali Rice provides some of the fundamental underlying services  for Kuali OLE and other Kuali software, services such as workflows, a service bus, integration with campus identity management, and more. In preparation for OLE, some partner libraries are developing their own simple Rice-base applications to provide some useful automation now while gaining experience that will prepare us for running Rice as part of OLE. This talk will give a brief overview of Kuali Rice and then discuss the construction of a real-but-simple Rice application.&lt;br /&gt;
&lt;br /&gt;
== Argo and DOR Services: The developer and administrative interfaces to Stanford's Digital Object Registry ==&lt;br /&gt;
&lt;br /&gt;
* Michael B. Klein, Library Infrastructure Engineer, Stanford University Libraries, mbklein at stanford dot edu&lt;br /&gt;
&lt;br /&gt;
Argo is the administrative interface for Stanford's Digital Object Registry (DOR), the central repository of information about digital assets owned or managed by Stanford University Libraries and Academic Information Resources (SULAIR). Built on Blacklight, with help from other pieces of the Hydra repository framework, Argo provides a top-down, source-independent, application-agnostic view of items working their way through various stages of registration, submission, description, digitization, accessioning, publication, shelving, and preservation.&lt;br /&gt;
&lt;br /&gt;
Argo's functionality is provided through three separate layers:&lt;br /&gt;
&lt;br /&gt;
* A traditional web application, which provides UI-based bulk and individual item registration, management, and reporting functions&lt;br /&gt;
* A web service, which provides RESTful access to several of the same functions&lt;br /&gt;
* A DOR services Ruby gem which opens most of this functionality to other Ruby code, from Rails applications to accessioning daemons to one-off scripts&lt;br /&gt;
&lt;br /&gt;
This presentation will explore Argo's full stack, from the underlying DOR Services gem (encapsulating a number of other disparate library infrastructure functions) to its use by SULAIR developers, contractors, digitization lab staff, project managers, and SULAIR technical staff.&lt;br /&gt;
   &lt;br /&gt;
&lt;br /&gt;
== The Way to Bulid C4L Activities in Your Homeland - Based on the Experience of Code4Lib JAPAN. ==&lt;br /&gt;
&lt;br /&gt;
* Makoto Okamoto, Chief Editor of Academic Resource Guide (ARG) and Executive Officer of Code4Lib JAPAN, arg.editor_at_gmail.com &lt;br /&gt;
&lt;br /&gt;
In August 2010, We launched the &amp;quot;Code4Lib JAPAN&amp;quot;, a kind of local activities of Code4Lib in JAPAN after preparation for 6 months. Since then, Code4Lib JAPAN did a great sucess and growth. Approximately, activities of Code4Lib JAPAN are divided into 4 parts like operation of orgnization and activities, offer training program, proposing some guidelines, dispatching a mission to Code4Lib Conference and selection of good practice.&lt;br /&gt;
&lt;br /&gt;
In this presentation, some key facters of our sucess and growth will be explained by Executive Officer of Code4Lib JAPAN. Those key facters like getting money from outside grant, indutrial sponsers and personal supporters, operation of orgnization and activities on a self-supporting basis will be very helpful for those who are wishing to launch local activitiy in their homeland. We can offer variuus tiips to spread value and activities of Code4Lib in the world.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== The Golden Road (To Unlimited Devotion): Building a Socially Contructed Archive of Grateful Dead Artifacts ==&lt;br /&gt;
&lt;br /&gt;
* Robin Chandler, University of California (Santa Cruz), chandler [at] ucsc [dot] edu&lt;br /&gt;
* Susan Chesley Perry, University of California (Santa Cruz), chesley [at] ucsc [dot] edu&lt;br /&gt;
* Kevin S. Clarke, University of California (Santa Cruz), ksclarke [at] ucsc [dot] edu&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Grateful Dead Archive at the University of California (Santa Cruz) is a collection of over 600 linear feet of material, including: business records, photographs, posters, fan envelopes, tickets, video, audio (oral histories, interviews and music) and 3-d objects such as stage props and band merchandise.  In addition, with the release of the ''Grateful Dead Archive Online'' website in 2012, the Archive will start actively collecting artifacts from an enthusiastic community of Grateful Dead fans.&lt;br /&gt;
&lt;br /&gt;
This talk will discuss the challenges of merging a traditional archive with a socially constructed one.  We will also present the first round of development and explain how we're using tools like Omeka, ContentDM, UC3 Merritt, djatoka, Kaltura, Google Maps, and Solr to lay the foundation for a robust and engaging site.  Future directions, like the integration/development of better curation tools and what we hope to learn from opening the archive to contributions from a large community of fans, will also be discussed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Library News - A gathering place for library and tech news, and more ==&lt;br /&gt;
&lt;br /&gt;
* Matt Phillips, Harvard Library Innovation Lab, mphillips@law.harvard.edu&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://news.librarycloud.org Library News] is gathering place for people to share and discuss news from the technology and library worlds. Think [http://news.ycombinator.com Hacker News], but for library dorks instead of startup dorks.&lt;br /&gt;
&lt;br /&gt;
Library News is more than a news and discussion site, it analyzes submitted links and shares its observations. One example of this sharing is the exposure of popular blogs: Library News tracks submitted blog entries and tallies them up, creating a list of most popular blogs in the community. This most popular list is exposed as an HTML document and as an [http://en.wikipedia.org/wiki/OPML OPML] download (The OPML file can be loaded directly into an RSS reader and be used as an always up-to-date &amp;quot;starter pack&amp;quot; of popular blogs in the library and tech spaces). &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
My rough talk outline:&lt;br /&gt;
* Demo Library News&lt;br /&gt;
* Present how Library News goes beyond normal discussion sites (the tools that allow to explore community submitted links)&lt;br /&gt;
* Discuss where Library News fits with the current library news ecosystem&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Find more information about Library News at the [http://news.librarycloud.org/faq Library News FAQ]&lt;br /&gt;
&lt;br /&gt;
== Data-Mining Repository Contents to Auto-populate Scholarly Research Repository Submission Metadata ==&lt;br /&gt;
* Mark Diggory, Head of U.S. Operations&lt;br /&gt;
&lt;br /&gt;
The existing body of Open Access scholarly research is a well classified and described dataset.  However, in Institutional Repositories it can be the case that there are insufficient resources to invest for cataloging and maintaining rich metadata descriptions of contributed content. This is especially the case when collections are populated and maintained by non-librarians.  A great deal of classifiable detail preexists within files that are submitted to scholarly repositories.  Utilizing existing Open Source technologies capable of extracting this information, a process can be provided to submitters and repository maintainers to suggest appropriate subject classifications and types for descriptive metadata during submission and update of repository items.  This talk will provide an overview of an approach for utilizing machine learning as a tool for the auto population of subject classifications and content types.&lt;br /&gt;
&lt;br /&gt;
== Mining Wikipedia for Book Articles ==&lt;br /&gt;
* Paul Deschner, Harvard Library Innovation Lab, deschner@law.harvard.edu&lt;br /&gt;
&lt;br /&gt;
Suppose you were developing a browsing tool for library materials and wanted to include Wikipedia articles and categories whenever available -- how would you do it?  There is no API or other data service which one can use to get a comprehensive listing of every page in Wikipedia devoted to the discussion of a book.  &lt;br /&gt;
&lt;br /&gt;
This talk will focus on the tools, workflows and data sources we have used to approach this problem.  Tools and workflows include the use of Infobox ISBN's and other standard identifiers, analysis of Wikipedia categories and category hierarchies, exploitation of article abstracts and titles, and Mechanical Turk resources.  Data sources include Dbpedia triple stores and Wikimedia XML/SQL dumps.  So far, we have harvested around 60,000 book articles.  This is an exploration in dealing with open, relatively unstructured Web content, and in aggregating answers to the same question using quite diverse techniques.&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=C4l2012_rideshare&amp;diff=9792</id>
		<title>C4l2012 rideshare</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=C4l2012_rideshare&amp;diff=9792"/>
				<updated>2011-11-18T19:06:27Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* Nearby */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Seattle Tacoma International Airport ===&lt;br /&gt;
&lt;br /&gt;
See also [http://orbiscascade.org/index/c4l-transportation travel advice from the hosts]&lt;br /&gt;
&lt;br /&gt;
'''Arrivals'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; class=&amp;quot;sortable&amp;quot; &lt;br /&gt;
|- style=&amp;quot;text-align: left;&amp;quot;&lt;br /&gt;
! Name !! Flight Arriving  !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?&lt;br /&gt;
|-&lt;br /&gt;
| yourname/email|| date/time || yes/no|| yes/no || yes/no || who's the driver?||yes/no||# of people you can take&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Departures'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; class=&amp;quot;sortable&amp;quot; &lt;br /&gt;
|- style=&amp;quot;text-align: left;&amp;quot;&lt;br /&gt;
! Name !! Flight Departing !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?&lt;br /&gt;
|-&lt;br /&gt;
| yourname/email|| date/time || yes/no|| yes/no || yes/no || who's the driver?||yes/no||# of people you can take&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Public Transit from the Airport===&lt;br /&gt;
Light Rail: The [http://www.soundtransit.org/Schedules/Central-Link-light-rail.xml Central Link Light Rail station] will be located near the northeast corner of the main airport parking garage, directly connecting pedestrians to the airport ticketing concourse and SeaTac's City Center. The light rail offers a 36-minute ride from the airport to Downtown Seattle. &lt;br /&gt;
&lt;br /&gt;
Get off at the Pioneer Square station.  The hotel is 7 blocks from the station (0.4 miles) and the walk includes a steep hill, so plan to take a bus, a cab, or be out of breath by the time you get to the hotel.  The easiest transit connection is to walk up Third to Marion, and take the #12 up the hill.  It's a free ride till 7 p.m. Trolley stops across the street (6th Ave) from the hotel.&lt;br /&gt;
&lt;br /&gt;
Fare: &amp;lt;$3 for light rail&lt;br /&gt;
&lt;br /&gt;
=== Roommates ===&lt;br /&gt;
==== Looking ====&lt;br /&gt;
* [http://jodischneider.com/jodi.html JodiS] -- looking for a female roommate, ideally &amp;lt; $70/night (any women who get the $138 a night  government employee rate looking for a share?)&lt;br /&gt;
&lt;br /&gt;
==== Offering ====&lt;br /&gt;
* [https://twitter.com/#!/skome samk] -- Have 2 double beds at the conference hotel, need only one. Human male, typically easy going.&lt;br /&gt;
&lt;br /&gt;
=== Other places to stay ===&lt;br /&gt;
[http://www.tripadvisor.com/Hotels-g60878-Seattle_Washington-Hotels.html| TripAdvisor]&lt;br /&gt;
Also if anyone has suggestions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Nearby====&lt;br /&gt;
* [http://www.monaco-seattle.com/ Hotel Monaco] - .2 mi (1101 4th Avenue, Seattle, WA)&lt;br /&gt;
* [http://www.greentortoise.net/ Green Tortise Hostel],  $28.50 - $32.50/person in shared dorm rooms - .6 mi (105 1/2 Pike St)&lt;br /&gt;
* [http://www.executivehotels.net/downtownseattlehotel/s_seattle_accommodation.cgi Executive Hotel Pacific] $99 (Also available a 20% discount with advance purchase - full payment upfront required) - .1 miles (400 Spring St).&lt;br /&gt;
* [http://www.kimptonhotels.com/hotels/factsheets/hotel-vintage-park-seattle/ Hotel Vintage Park], $153 (king) and $143 (queen) with AAA discount. Might have government rates, not sure.&lt;br /&gt;
&lt;br /&gt;
====Bus distance====&lt;br /&gt;
* College Inn (bus ride away)&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=C4l2012_t-shirtcontest&amp;diff=9724</id>
		<title>C4l2012 t-shirtcontest</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=C4l2012_t-shirtcontest&amp;diff=9724"/>
				<updated>2011-11-16T17:28:31Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: New page: It's time to submit designs for the Code4Lib 2012 conference T-shirt! Your design should somehow capture the awesomeness of the code4lib community and be something you'd be proud to wear. ...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;It's time to submit designs for the Code4Lib 2012 conference T-shirt!&lt;br /&gt;
Your design should somehow capture the awesomeness of the code4lib community and be something you'd be proud to wear.&lt;br /&gt;
&lt;br /&gt;
The design submissions are for the front of the shirt and may be as large as 11&amp;quot; by 15&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Keep in mind that these will be printed in one color on a shirt of another color, so please make your design accordingly.&lt;br /&gt;
&lt;br /&gt;
The vendor indicated that they preferred Adobe Illustrator or EPS formatted files, though we can convert other formats.  Please send&lt;br /&gt;
submissions to me (e-mail address below) by Monday November 21st, at which point they'll be posted for your review and voting [probably&lt;br /&gt;
after the Thanksgiving holiday here in the U.S.]&lt;br /&gt;
&lt;br /&gt;
--&lt;br /&gt;
Ann Lally&lt;br /&gt;
Head, Digital Initiatives&lt;br /&gt;
University of Washington Libraries&lt;br /&gt;
alally_at_uw.edu&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

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

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=C4l2012_rideshare&amp;diff=9718</id>
		<title>C4l2012 rideshare</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=C4l2012_rideshare&amp;diff=9718"/>
				<updated>2011-11-16T00:02:35Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* Other places to stay */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Seattle Tacoma International Airport ===&lt;br /&gt;
&lt;br /&gt;
'''Arrivals'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; class=&amp;quot;sortable&amp;quot; &lt;br /&gt;
|- style=&amp;quot;text-align: left;&amp;quot;&lt;br /&gt;
! Name !! Flight Arriving  !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?&lt;br /&gt;
|-&lt;br /&gt;
| yourname/email|| date/time || yes/no|| yes/no || yes/no || who's the driver?||yes/no||# of people you can take&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Departures'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; class=&amp;quot;sortable&amp;quot; &lt;br /&gt;
|- style=&amp;quot;text-align: left;&amp;quot;&lt;br /&gt;
! Name !! Flight Departing !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?&lt;br /&gt;
|-&lt;br /&gt;
| yourname/email|| date/time || yes/no|| yes/no || yes/no || who's the driver?||yes/no||# of people you can take&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Roommates ===&lt;br /&gt;
==== Looking ====&lt;br /&gt;
==== Offering ====&lt;br /&gt;
&lt;br /&gt;
=== Other places to stay ===&lt;br /&gt;
[http://www.tripadvisor.com/Hotels-g60878-Seattle_Washington-Hotels.html| TripAdvisor]&lt;br /&gt;
Also if anyone has suggestions.&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=C4l2012_rideshare&amp;diff=9717</id>
		<title>C4l2012 rideshare</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=C4l2012_rideshare&amp;diff=9717"/>
				<updated>2011-11-16T00:01:39Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: /* Other places to stay */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Seattle Tacoma International Airport ===&lt;br /&gt;
&lt;br /&gt;
'''Arrivals'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; class=&amp;quot;sortable&amp;quot; &lt;br /&gt;
|- style=&amp;quot;text-align: left;&amp;quot;&lt;br /&gt;
! Name !! Flight Arriving  !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?&lt;br /&gt;
|-&lt;br /&gt;
| yourname/email|| date/time || yes/no|| yes/no || yes/no || who's the driver?||yes/no||# of people you can take&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Departures'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; class=&amp;quot;sortable&amp;quot; &lt;br /&gt;
|- style=&amp;quot;text-align: left;&amp;quot;&lt;br /&gt;
! Name !! Flight Departing !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?&lt;br /&gt;
|-&lt;br /&gt;
| yourname/email|| date/time || yes/no|| yes/no || yes/no || who's the driver?||yes/no||# of people you can take&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Roommates ===&lt;br /&gt;
==== Looking ====&lt;br /&gt;
==== Offering ====&lt;br /&gt;
&lt;br /&gt;
=== Other places to stay ===&lt;br /&gt;
[[http://www.tripadvisor.com/Hotels-g60878-Seattle_Washington-Hotels.html|TripAdvisor]]&lt;br /&gt;
Also if anyone has suggestions.&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=C4l2012_rideshare&amp;diff=9716</id>
		<title>C4l2012 rideshare</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=C4l2012_rideshare&amp;diff=9716"/>
				<updated>2011-11-16T00:00:59Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Seattle Tacoma International Airport ===&lt;br /&gt;
&lt;br /&gt;
'''Arrivals'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; class=&amp;quot;sortable&amp;quot; &lt;br /&gt;
|- style=&amp;quot;text-align: left;&amp;quot;&lt;br /&gt;
! Name !! Flight Arriving  !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?&lt;br /&gt;
|-&lt;br /&gt;
| yourname/email|| date/time || yes/no|| yes/no || yes/no || who's the driver?||yes/no||# of people you can take&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Departures'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; class=&amp;quot;sortable&amp;quot; &lt;br /&gt;
|- style=&amp;quot;text-align: left;&amp;quot;&lt;br /&gt;
! Name !! Flight Departing !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?&lt;br /&gt;
|-&lt;br /&gt;
| yourname/email|| date/time || yes/no|| yes/no || yes/no || who's the driver?||yes/no||# of people you can take&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Roommates ===&lt;br /&gt;
==== Looking ====&lt;br /&gt;
==== Offering ====&lt;br /&gt;
&lt;br /&gt;
=== Other places to stay ===&lt;br /&gt;
[[http://www.tripadvisor.com/Hotels-g60878-Seattle_Washington-Hotels.html|Link to TripAdvisor]]&lt;br /&gt;
Also if anyone has suggestions.&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

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

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

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=C4l2012_rideshare&amp;diff=9712</id>
		<title>C4l2012 rideshare</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=C4l2012_rideshare&amp;diff=9712"/>
				<updated>2011-11-15T23:33:27Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: New page: === Seattle Tacoma International Airport ===  '''Arrivals''' {| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; class=&amp;quot;sortable&amp;quot;  |- style=&amp;quot;text-align: left;&amp;quot; ! Name !! Flight Arriving  !! Renting Car? !! Shar...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Seattle Tacoma International Airport ===&lt;br /&gt;
&lt;br /&gt;
'''Arrivals'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; class=&amp;quot;sortable&amp;quot; &lt;br /&gt;
|- style=&amp;quot;text-align: left;&amp;quot;&lt;br /&gt;
! Name !! Flight Arriving  !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?&lt;br /&gt;
|-&lt;br /&gt;
| yourname/email|| date/time || yes/no|| yes/no || yes/no || who's the driver?||yes/no||# of people you can take&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Departures'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; class=&amp;quot;sortable&amp;quot; &lt;br /&gt;
|- style=&amp;quot;text-align: left;&amp;quot;&lt;br /&gt;
! Name !! Flight Departing !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?&lt;br /&gt;
|-&lt;br /&gt;
| yourname/email|| date/time || yes/no|| yes/no || yes/no || who's the driver?||yes/no||# of people you can take&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

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

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

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

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_c4l2012_social_activities&amp;diff=9705</id>
		<title>2012 c4l2012 social activities</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_c4l2012_social_activities&amp;diff=9705"/>
				<updated>2011-11-15T19:26:59Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Ideas==&lt;br /&gt;
* Woodinville distillery tour&lt;br /&gt;
* Seattle distillery tour&lt;br /&gt;
* Favorite local breweries&lt;br /&gt;
* Favorite local tea houses&lt;br /&gt;
* Visit hackerspace.&lt;br /&gt;
&lt;br /&gt;
==Planned events==&lt;br /&gt;
Newcomer dinners&lt;br /&gt;
&lt;br /&gt;
==Local events/places==&lt;br /&gt;
* Metrix Create Space&lt;br /&gt;
* Ada's Technical Books&lt;br /&gt;
* Northwest Outdoor Center&lt;br /&gt;
* Center for Wooden Boats&lt;br /&gt;
&lt;br /&gt;
==Recommended Restaurants/Bars (no particular order)==&lt;br /&gt;
* Pub at Third Place&lt;br /&gt;
* Leary Traveler&lt;br /&gt;
* Stumbling Monk&lt;br /&gt;
* The Dray&lt;br /&gt;
* Norm's&lt;br /&gt;
* Elysian&lt;br /&gt;
* Nine Pound Hammer&lt;br /&gt;
* Meza&lt;br /&gt;
* Revel&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_c4l2012_social_activities&amp;diff=9704</id>
		<title>2012 c4l2012 social activities</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_c4l2012_social_activities&amp;diff=9704"/>
				<updated>2011-11-15T19:26:23Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: New page: ==Code4Lib 2011 social activities ==  ==Ideas== * Woodinville distillery tour * Seattle distillery tour * Favorite local breweries * Favorite local tea houses * Visit hackerspace.  ==Plann...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Code4Lib 2011 social activities ==&lt;br /&gt;
&lt;br /&gt;
==Ideas==&lt;br /&gt;
* Woodinville distillery tour&lt;br /&gt;
* Seattle distillery tour&lt;br /&gt;
* Favorite local breweries&lt;br /&gt;
* Favorite local tea houses&lt;br /&gt;
* Visit hackerspace.&lt;br /&gt;
&lt;br /&gt;
==Planned events==&lt;br /&gt;
Newcomer dinners&lt;br /&gt;
&lt;br /&gt;
==Local events/places==&lt;br /&gt;
* Metrix Create Space&lt;br /&gt;
* Ada's Technical Books&lt;br /&gt;
* Northwest Outdoor Center&lt;br /&gt;
* Center for Wooden Boats&lt;br /&gt;
&lt;br /&gt;
==Recommended Restaurants/Bars (no particular order)==&lt;br /&gt;
* Pub at Third Place&lt;br /&gt;
* Leary Traveler&lt;br /&gt;
* Stumbling Monk&lt;br /&gt;
* The Dray&lt;br /&gt;
* Norm's&lt;br /&gt;
* Elysian&lt;br /&gt;
* Nine Pound Hammer&lt;br /&gt;
* Meza&lt;br /&gt;
* Revel&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

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

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_committees_sign-up_page&amp;diff=9487</id>
		<title>2012 committees sign-up page</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_committees_sign-up_page&amp;diff=9487"/>
				<updated>2011-10-14T15:16:08Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2012 Committees =&lt;br /&gt;
&lt;br /&gt;
If you are interested in helping out with a particular part of the Code4Lib 2012 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.&lt;br /&gt;
&lt;br /&gt;
== Book Give-Away Committee ==&lt;br /&gt;
&lt;br /&gt;
* Kevin S. Clarke (ksclarke@gmail.com) -- McHenry Library, UC Santa Cruz -- Asking O'Reilly&lt;br /&gt;
* Chandos Publishing. Yes.&lt;br /&gt;
* Anjanette -- Asking Manning (via Erik Hatcher)&lt;br /&gt;
* No Starch. Yes.&lt;br /&gt;
* [http://www.seattletechnicalbooks.com Ada's Technical Books]. Woohoo.&lt;br /&gt;
* Andrew Nagy -- oXygen XML Editor (5 Licenses to give away)&lt;br /&gt;
* [[BookRaffle|Suggestions for Book Raffle.]]&lt;br /&gt;
&lt;br /&gt;
== Sponsorships Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Kyle Banerjee (banerjek@uoregon.edu) -- Orbis Cascade Alliance&lt;br /&gt;
* Anjanette Young -- University of Washington&lt;br /&gt;
* Mike Giarlo -- Penn State&lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]] -- LYRASIS (likely sponsor)&lt;br /&gt;
* Andrew Nagy -- Serials Solutions&lt;br /&gt;
* Roy Tennant -- OCLC&lt;br /&gt;
&lt;br /&gt;
== Keynote Speakers Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Ann Lally (alally at uw dot edu) University of Washington&lt;br /&gt;
* Dre (akorphan at ncsu dot edu) North Carolina State University&lt;br /&gt;
&lt;br /&gt;
== Program Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee plans the structure of the program, arranges the voting on presentations, etc. These folks will also announce speakers, etc.&lt;br /&gt;
&lt;br /&gt;
* Jeremy Frumkin (frumkinj at u dot library dot arizona dot edu) - University of Arizona&lt;br /&gt;
* Ranti Junus (ranti.junus at gmail) - Michigan State University&lt;br /&gt;
* John Fink (john.fink at gmail) - McMaster University&lt;br /&gt;
* Tom Johnson (thomas dot johnson at oregonstate dot edu) - Oregon State University&lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]] - LYRASIS&lt;br /&gt;
&lt;br /&gt;
== Scholarships Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Jeremy Frumkin (frumkinj at u dot library dot arizona dot edu) - University of Arizona&lt;br /&gt;
* Jodi Schneider - DERI, NUI Galway&lt;br /&gt;
&lt;br /&gt;
== T-Shirt Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes.&lt;br /&gt;
&lt;br /&gt;
* Ann Lally (alally at uw dot edu) University of Washington&lt;br /&gt;
* Angie Beiriger (beiriger at reed dot edu) Reed college&lt;br /&gt;
&lt;br /&gt;
== Social Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
The committee plans, proposes, and organizes the evening activities.&lt;br /&gt;
&lt;br /&gt;
* Jennifer Ward (jlward1 at uw dot edu) -- University of Washington&lt;br /&gt;
* Jeff Sherwood (jeffs3 at uw dot edu) -- University of Washington&lt;br /&gt;
&lt;br /&gt;
== Voting Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Hospitality Suite Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee makes arrangements for any hospitality suite amenities (technology, snacks, games, icebreakers...) we may want&lt;br /&gt;
&lt;br /&gt;
* Mike Giarlo -- Penn State [Glad to be a keyholder, room-sitter, and general tidier-upper]&lt;br /&gt;
* Tom Johnson -- Oregon State University&lt;br /&gt;
* Lisa Kurt [lkurt at unr dot edu]-- University of Nevada, Reno&lt;br /&gt;
&lt;br /&gt;
== Welcome Wagon Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Becky Yoose(b.yoose at gmail dot com) -- Grinnell College&lt;br /&gt;
* Bohyun Kim(kimb at fiu dot edu) -- Florida International University&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
Responsible for non-IRC social networking presence.&lt;br /&gt;
&lt;br /&gt;
*Rowena McKernan (rmckernan at whatcom dot ctc dot edu) ~ Whatcom Community College&lt;br /&gt;
&lt;br /&gt;
== IRC Evangelists ==&lt;br /&gt;
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.&lt;br /&gt;
&lt;br /&gt;
* Sam Kome (skome) Claremont Colleges&lt;br /&gt;
&lt;br /&gt;
== IRC Access ==&lt;br /&gt;
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful.&lt;br /&gt;
&lt;br /&gt;
* Cary Gordon (cgordon at chillco.com) -- The Cherry Hill Company&lt;br /&gt;
&lt;br /&gt;
==Registration Desk Volunteers==&lt;br /&gt;
We need 1-2 volunteers to hang out at the registration desk for 2-hour shifts.  Also on Monday and Tuesday, an additional volunteer with wireless access knowledge would be helpful on the Registration Desk to answer tech questions.&lt;br /&gt;
&lt;br /&gt;
* Dan Suchy (dansuchy at gmail) -- UC San Diego&lt;br /&gt;
&lt;br /&gt;
== Microphone Runners==&lt;br /&gt;
&lt;br /&gt;
Run wireless handheld microphones to audience members asking questions.&lt;br /&gt;
&lt;br /&gt;
== Session Timer Volunteers ==&lt;br /&gt;
&lt;br /&gt;
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop with a stopwatch program).&lt;br /&gt;
&lt;br /&gt;
* Ann Gleason (amwhit24 at uw dot edu) - University of Washington&lt;br /&gt;
&lt;br /&gt;
'''Schedule for Session Timers'''&lt;br /&gt;
&lt;br /&gt;
== Raffles ==&lt;br /&gt;
 (calling awardees)&lt;br /&gt;
 (backup)&lt;br /&gt;
 (program)&lt;br /&gt;
&lt;br /&gt;
= Documentation =&lt;br /&gt;
To help with documention, no need to sign up, just start editing.&lt;br /&gt;
* [[How To Plan A Code4LibCon]]&lt;br /&gt;
&lt;br /&gt;
== Documentation Interest Group ==&lt;br /&gt;
Promote ongoing documentation efforts.&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_committees_sign-up_page&amp;diff=9486</id>
		<title>2012 committees sign-up page</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_committees_sign-up_page&amp;diff=9486"/>
				<updated>2011-10-14T15:15:46Z</updated>
		
		<summary type="html">&lt;p&gt;Younga3: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2012 Committees =&lt;br /&gt;
&lt;br /&gt;
If you are interested in helping out with a particular part of the Code4Lib 2012 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.&lt;br /&gt;
&lt;br /&gt;
== Book Give-Away Committee ==&lt;br /&gt;
&lt;br /&gt;
* Kevin S. Clarke (ksclarke@gmail.com) -- McHenry Library, UC Santa Cruz -- Asking O'Reilly&lt;br /&gt;
* Chandos Publishing. Yes.&lt;br /&gt;
* Anjanette -- Asking Manning (via Erik Hatcher)&lt;br /&gt;
* Anjanette -- No Starch. Yes.&lt;br /&gt;
* [http://www.seattletechnicalbooks.com Ada's Technical Books]. Woohoo.&lt;br /&gt;
* Andrew Nagy -- oXygen XML Editor (5 Licenses to give away)&lt;br /&gt;
* [[BookRaffle|Suggestions for Book Raffle.]]&lt;br /&gt;
&lt;br /&gt;
== Sponsorships Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Kyle Banerjee (banerjek@uoregon.edu) -- Orbis Cascade Alliance&lt;br /&gt;
* Anjanette Young -- University of Washington&lt;br /&gt;
* Mike Giarlo -- Penn State&lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]] -- LYRASIS (likely sponsor)&lt;br /&gt;
* Andrew Nagy -- Serials Solutions&lt;br /&gt;
* Roy Tennant -- OCLC&lt;br /&gt;
&lt;br /&gt;
== Keynote Speakers Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Ann Lally (alally at uw dot edu) University of Washington&lt;br /&gt;
* Dre (akorphan at ncsu dot edu) North Carolina State University&lt;br /&gt;
&lt;br /&gt;
== Program Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee plans the structure of the program, arranges the voting on presentations, etc. These folks will also announce speakers, etc.&lt;br /&gt;
&lt;br /&gt;
* Jeremy Frumkin (frumkinj at u dot library dot arizona dot edu) - University of Arizona&lt;br /&gt;
* Ranti Junus (ranti.junus at gmail) - Michigan State University&lt;br /&gt;
* John Fink (john.fink at gmail) - McMaster University&lt;br /&gt;
* Tom Johnson (thomas dot johnson at oregonstate dot edu) - Oregon State University&lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]] - LYRASIS&lt;br /&gt;
&lt;br /&gt;
== Scholarships Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Jeremy Frumkin (frumkinj at u dot library dot arizona dot edu) - University of Arizona&lt;br /&gt;
* Jodi Schneider - DERI, NUI Galway&lt;br /&gt;
&lt;br /&gt;
== T-Shirt Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes.&lt;br /&gt;
&lt;br /&gt;
* Ann Lally (alally at uw dot edu) University of Washington&lt;br /&gt;
* Angie Beiriger (beiriger at reed dot edu) Reed college&lt;br /&gt;
&lt;br /&gt;
== Social Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
The committee plans, proposes, and organizes the evening activities.&lt;br /&gt;
&lt;br /&gt;
* Jennifer Ward (jlward1 at uw dot edu) -- University of Washington&lt;br /&gt;
* Jeff Sherwood (jeffs3 at uw dot edu) -- University of Washington&lt;br /&gt;
&lt;br /&gt;
== Voting Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Hospitality Suite Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee makes arrangements for any hospitality suite amenities (technology, snacks, games, icebreakers...) we may want&lt;br /&gt;
&lt;br /&gt;
* Mike Giarlo -- Penn State [Glad to be a keyholder, room-sitter, and general tidier-upper]&lt;br /&gt;
* Tom Johnson -- Oregon State University&lt;br /&gt;
* Lisa Kurt [lkurt at unr dot edu]-- University of Nevada, Reno&lt;br /&gt;
&lt;br /&gt;
== Welcome Wagon Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Becky Yoose(b.yoose at gmail dot com) -- Grinnell College&lt;br /&gt;
* Bohyun Kim(kimb at fiu dot edu) -- Florida International University&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
Responsible for non-IRC social networking presence.&lt;br /&gt;
&lt;br /&gt;
*Rowena McKernan (rmckernan at whatcom dot ctc dot edu) ~ Whatcom Community College&lt;br /&gt;
&lt;br /&gt;
== IRC Evangelists ==&lt;br /&gt;
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.&lt;br /&gt;
&lt;br /&gt;
* Sam Kome (skome) Claremont Colleges&lt;br /&gt;
&lt;br /&gt;
== IRC Access ==&lt;br /&gt;
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful.&lt;br /&gt;
&lt;br /&gt;
* Cary Gordon (cgordon at chillco.com) -- The Cherry Hill Company&lt;br /&gt;
&lt;br /&gt;
==Registration Desk Volunteers==&lt;br /&gt;
We need 1-2 volunteers to hang out at the registration desk for 2-hour shifts.  Also on Monday and Tuesday, an additional volunteer with wireless access knowledge would be helpful on the Registration Desk to answer tech questions.&lt;br /&gt;
&lt;br /&gt;
* Dan Suchy (dansuchy at gmail) -- UC San Diego&lt;br /&gt;
&lt;br /&gt;
== Microphone Runners==&lt;br /&gt;
&lt;br /&gt;
Run wireless handheld microphones to audience members asking questions.&lt;br /&gt;
&lt;br /&gt;
== Session Timer Volunteers ==&lt;br /&gt;
&lt;br /&gt;
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop with a stopwatch program).&lt;br /&gt;
&lt;br /&gt;
* Ann Gleason (amwhit24 at uw dot edu) - University of Washington&lt;br /&gt;
&lt;br /&gt;
'''Schedule for Session Timers'''&lt;br /&gt;
&lt;br /&gt;
== Raffles ==&lt;br /&gt;
 (calling awardees)&lt;br /&gt;
 (backup)&lt;br /&gt;
 (program)&lt;br /&gt;
&lt;br /&gt;
= Documentation =&lt;br /&gt;
To help with documention, no need to sign up, just start editing.&lt;br /&gt;
* [[How To Plan A Code4LibCon]]&lt;br /&gt;
&lt;br /&gt;
== Documentation Interest Group ==&lt;br /&gt;
Promote ongoing documentation efforts.&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Younga3</name></author>	</entry>

	</feed>