<?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=Rshanrath</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=Rshanrath"/>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/Special:Contributions/Rshanrath"/>
		<updated>2026-06-09T15:30:38Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.26.2</generator>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&amp;diff=40134</id>
		<title>2014 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&amp;diff=40134"/>
				<updated>2013-12-12T14:41:34Z</updated>
		
		<summary type="html">&lt;p&gt;Rshanrath: /* Obey the Testing Goat!: Test Driven Web Development From The Ground Up */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= PROPOSALS ARE CLOSED : PLEASE DO NOT ADD NEW PRECONFERENCES TO THIS PAGE =&lt;br /&gt;
&lt;br /&gt;
Proposals were accepted through December 6th, 2013.&lt;br /&gt;
&lt;br /&gt;
It would be really, super duper helpful if folks who think they might want to attend a pre-conference could indicate interest by adding your name to a session below. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Note===&lt;br /&gt;
Attendance at a pre-conference will require a small fee ''due at the time of conference registration&amp;quot;.&lt;br /&gt;
 &lt;br /&gt;
Although this was specified in the email announcements relating to pre-conferences, it was not added to this page until December 2nd.  I (Adam C.) apologize for the omission and I hope this will not cause any &amp;quot;sticker shock.&amp;quot;  Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.&lt;br /&gt;
&lt;br /&gt;
Please put your pre-conference on the list in the following format:&lt;br /&gt;
&lt;br /&gt;
=Code4Lib 2014 Pre-Conference Proposals=&lt;br /&gt;
&lt;br /&gt;
===Drupal4lib Sub-con Barcamp===&lt;br /&gt;
=====Full Day=====&lt;br /&gt;
&lt;br /&gt;
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.&lt;br /&gt;
&lt;br /&gt;
This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).&lt;br /&gt;
&lt;br /&gt;
[[resources to help you learn drupal]]&lt;br /&gt;
&lt;br /&gt;
====Interested in Attending:====&lt;br /&gt;
&lt;br /&gt;
=====All Day=====&lt;br /&gt;
&lt;br /&gt;
* Renna Tuten &lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
&lt;br /&gt;
* Kevin Reiss&lt;br /&gt;
* Charlie Morris (NCSU) - glad to see this again this year!&lt;br /&gt;
* Paula Gray-Overtoom&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Open Refine Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot;'''&lt;br /&gt;
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com&lt;br /&gt;
&lt;br /&gt;
[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control&lt;br /&gt;
&lt;br /&gt;
The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. &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;
&amp;lt;ol&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Adam Constabaris&lt;br /&gt;
&amp;lt;li&amp;gt;Ray Schwartz&lt;br /&gt;
&amp;lt;li&amp;gt;Jason Stirnaman&lt;br /&gt;
&amp;lt;li&amp;gt;Joshua Gomez&lt;br /&gt;
&amp;lt;li&amp;gt;Sam Kome&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Responsive Design Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day [Afternoon]&amp;quot;''' &lt;br /&gt;
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com&lt;br /&gt;
* Contact David Ward, University of Illinois, dh-ward@illinois.edu&lt;br /&gt;
&lt;br /&gt;
This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. &lt;br /&gt;
&lt;br /&gt;
Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.&lt;br /&gt;
&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;
&lt;br /&gt;
=== Intro to Blacklight ===&lt;br /&gt;
'''&amp;quot;Half-Day [Morning]&amp;quot;''' &lt;br /&gt;
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
* TA: Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
This session will be walk-through of the architecture of Blacklight, the community, and an introduction to building a Blacklight-based application. Each participant will have the opportunity to build a simple Blacklight application, and make basic customizations, while using a test-driven approach.&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;
&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;
# Bret Davidson&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Cory Lown&lt;br /&gt;
# Emily Daly&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Blacklight Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day [Afternoon]&amp;quot;''' &lt;br /&gt;
* Contact Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
&lt;br /&gt;
This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.&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 ).&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;
# Shaun Ellis&lt;br /&gt;
# Kevin Reiss&lt;br /&gt;
# Megan Kudzia&lt;br /&gt;
# Erik Hatcher&lt;br /&gt;
# Emily Daly&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
===RailsBridge: Intro to programming in Ruby on Rails===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
* Contact Justin Coyne, Data Curation Experts, justin@curationexperts.com&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! 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 Blacklight and Hydra.&lt;br /&gt;
&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;
1. Ayla Stein&lt;br /&gt;
&lt;br /&gt;
2. Heidi Dowding&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===&lt;br /&gt;
'''Full-Day'''&lt;br /&gt;
&lt;br /&gt;
Contact: &lt;br /&gt;
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com&lt;br /&gt;
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu&lt;br /&gt;
&lt;br /&gt;
This will be a full day session on project management.  We'll cover&lt;br /&gt;
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment&lt;br /&gt;
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets&lt;br /&gt;
* '''Executing the Project''' -- status meeting, status reports, issue management&lt;br /&gt;
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product&lt;br /&gt;
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.&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;
# Robin Dean&lt;br /&gt;
# Erin White&lt;br /&gt;
# Andrew Darby&lt;br /&gt;
# Sam Kome&lt;br /&gt;
# Ryan Scherle&lt;br /&gt;
# Will Shaw&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
# Cynthia &amp;quot;Arty&amp;quot; Ng&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Fail4Lib 2014===&lt;br /&gt;
'''Half Day [TBD, probably afternoon]'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Andreas Orphanides, akorphan (at) ncsu.edu&lt;br /&gt;
* Jason Casden, jmcasden (at) ncsu.edu&lt;br /&gt;
&lt;br /&gt;
The task of design (and the work that we do as library coders) is intimately tied to failure. Failures, both big and small, motivate us to create and improve. Failures are also occasionally the result of our work. Understanding and embracing failure, encouraging enlightened risk-taking, and seeking out opportunities to fail and learn are essential to success in our field. 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 feared.&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
&lt;br /&gt;
* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?&lt;br /&gt;
* Confessionals, for those willing to share. Talk about your own experiences with rough starts, labor pains, and doomed projects in your own work: What can we learn from our own (and each others') failures?&lt;br /&gt;
* Group therapy. Let's talk about how to deal with risk management, failed projects, experimental endeavors, and more: How can we make ourselves, our colleagues, and our organizations more fault tolerant? How do we make sure we fail as productively as possible?&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;
#Bret Davidson&lt;br /&gt;
#Mike Graves&lt;br /&gt;
#Ray Schwartz&lt;br /&gt;
#Jason Stirnaman&lt;br /&gt;
#Julia Bauder&lt;br /&gt;
#Linda Ballinger&lt;br /&gt;
#Scott Hanrath&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===CLLAM @ code4lib===&lt;br /&gt;
'''(Computational Linguistics for Libraries, Archives and Museums)'''&lt;br /&gt;
&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Douglas W. Oard (primary), oard (at) umd.edu &lt;br /&gt;
* Corey Harper, corey (dot) harper (at) nyu.edu&lt;br /&gt;
* Robert Sanderson, azaroth42 (at) gmail.com &lt;br /&gt;
* Robert Warren, rwarren (at) math.carleton.ca&lt;br /&gt;
&lt;br /&gt;
We will hack at the intersection of diverse content from Libraries, Archives and Museums and bleeding edge tools from computational linguistics for slicing and dicing that content. Did you just acquire the email archives of a startup company? Maybe you can automatically build an org chart. Have you got metadata in a slew of languages? Perhaps you can search it all using one query. Is name authority control for e-resources getting too costly? Let’s see if entity linking techniques can help. These are just a few teasers. &lt;br /&gt;
&lt;br /&gt;
There’ll be plenty of content and tools supplied, but please bring your own [data] too -- you’ll hack with it in new ways throughout the day. We’ll get started with some lightning talks on what we’ve brought,then we’ll break up into groups to experiment and work on the ideas that appeal. Three guaranteed outcomes: you’ll walk away with new ideas, new tools, and new people you’ll have met.&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;
# Devon Smith&lt;br /&gt;
# Kevin S. Clarke&lt;br /&gt;
# Jason Stirnaman&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== GeoHydra: Managing geospatial content ===&lt;br /&gt;
&lt;br /&gt;
'''Half-day [Afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Contact: Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Moderator: Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,&lt;br /&gt;
etc., all of which you want to integrate into your digital repository? In this&lt;br /&gt;
workshop, we will discuss how Hydra can provide discovery, delivery, and&lt;br /&gt;
management services for geospatial assets, as well as solicit questions about&lt;br /&gt;
your own GIS projects. We aim to help answer the following questions you might have about putting geospatial data into your Hydra-based digital library:&lt;br /&gt;
&lt;br /&gt;
* What are the types of geospatial data?&lt;br /&gt;
* How to dive into Hydra?&lt;br /&gt;
* How to model geospatial holdings with Hydra?&lt;br /&gt;
* How to discover and view geospatial data?&lt;br /&gt;
* How to build a geospatial data infrastructure?&lt;br /&gt;
* What are common approaches and problems?&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;
# Esmé Cowles&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Technology, Librarianship, and Gender: Moving the conversation forward===&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]&lt;br /&gt;
&lt;br /&gt;
'''Description'''&lt;br /&gt;
&lt;br /&gt;
Librarianship is largely made up of women, yet women are significantly underrepresented in tech positions, on any level, within libraries themselves. Why? What are we doing to encourage women to become more involved in STEM within librarianship? What kind of message are we sending when library technology keynotes remain almost resolutely male? How are we changing the face of technology, not only within libraries, but with the field itself? How are we training our staff and colleagues in the areas of fairness and removal of bias? Our vendors?&lt;br /&gt;
&lt;br /&gt;
Lots of tough questions.&lt;br /&gt;
&lt;br /&gt;
While the conversation has been going on via various blogs and articles within the last few years, it was given a public face at [http://infotoday.com/il2013/day.asp?day=Monday#session_D105 Internet Librarian 2013] where a panel of 7 (four women, three men) gave personal experiences on the above and then opened up the conversation to the audience. As eye opening and enriching the conversation was, a 45 minute panel was not enough. One thing remains clear: We need to keep the conversation moving forward and start making some radical changes in the way we think, act, and how we need to harness this to start making real changes within librarianship itself.&lt;br /&gt;
&lt;br /&gt;
Topics to include:  Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems,  mentoring, ally support, and more&lt;br /&gt;
&lt;br /&gt;
Those attending should expect: Begin with opening up the conversation of experiences and talking about what is most needed, spending remaining time putting together live, usable solutions to start implementing as well as pushing the conversation forward at local levels&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;
=====All Day=====&lt;br /&gt;
1. Kate Kosturski&lt;br /&gt;
&lt;br /&gt;
2. Valerie Aurora&lt;br /&gt;
&lt;br /&gt;
3. Declan Fleming (I'd be good with a half day too)&lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
1. Shaun Ellis&lt;br /&gt;
&lt;br /&gt;
2. Jason Casden&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
1. Ayla Stein&lt;br /&gt;
&lt;br /&gt;
2. Heidi Dowding&lt;br /&gt;
&lt;br /&gt;
3. Coral Sheldon-Hess&lt;br /&gt;
&lt;br /&gt;
4. Cory Lown&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===FileAnalyzer: Rapid Development of File Manipulation Tasks===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
* Contact Terry Brady, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The FileAnalyzer (https://github.com/Georgetown-University-Libraries/File-Analyzer) is an application designed to solve a number of library automation challenges:&lt;br /&gt;
&lt;br /&gt;
* validating digitized and reformatted files&lt;br /&gt;
* validating vendor statistics for counter compliance&lt;br /&gt;
* preparing collections of digital files for archiving and ingest&lt;br /&gt;
* manipulating ILS import and export files&lt;br /&gt;
&lt;br /&gt;
The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census. After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform. Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.&lt;br /&gt;
&lt;br /&gt;
The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules. As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.&lt;br /&gt;
&lt;br /&gt;
The first half of this session will be targeted to potential users and developers.  The second half of the session will be targeted towards developers who are interested in developing custom rules for the application.&lt;br /&gt;
&lt;br /&gt;
''Session Overview''&lt;br /&gt;
* Overview of the application&lt;br /&gt;
* Running sample file tests/transformations through the application&lt;br /&gt;
* Compiling and building the application&lt;br /&gt;
* Coding a custom file processing task&lt;br /&gt;
&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;
----&lt;br /&gt;
&lt;br /&gt;
===Collecting social media data with Social Feed Manager===&lt;br /&gt;
'''Half-Day [Morning]'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Dan Chudnov, GW Libraries, dchud (at) gwu.edu&lt;br /&gt;
* Dan Kerchner, GW Libraries, kerchner (at) gwu.edu&lt;br /&gt;
* Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu&lt;br /&gt;
&lt;br /&gt;
Social media data is a popular material for research and a new format for building collections.  What does it take to collect meaningfully from Twitter, Tumblr, YouTube, Weibo, Facebook, and other sites?  We will:&lt;br /&gt;
* Introduce options for collections, including both high- and low-end commercial offerings. Discuss what it means to collect these resources, covering boundaries, policies, and workflows required to develop a social media collection program in your institution.&lt;br /&gt;
* Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them&lt;br /&gt;
* Help you get started using the free [http://gwu-libraries.github.io/social-feed-manager Social Feed Manager] (SFM) app we're developing at GW to create your first collections. We’ll demo its use and demo a clean install (those w/environments can follow along)&lt;br /&gt;
&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;
# Declan Fleming&lt;br /&gt;
# Esmé Cowles&lt;br /&gt;
# Jason Stirnaman&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Intro to Git ===&lt;br /&gt;
'''&amp;quot;Half-Day [tbd - probably afternoon]&amp;quot;''' &lt;br /&gt;
* Contact: Erin Fahy, Stanford University, efahy at stanford.edu&lt;br /&gt;
* TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu&lt;br /&gt;
&lt;br /&gt;
This session will cover the fundamentals of git by discussing/going through (time allowing):&lt;br /&gt;
* what is a distributed version control system&lt;br /&gt;
* what is git and github&lt;br /&gt;
* initializing a repo on a remote server/github&lt;br /&gt;
* cloning an existing repo&lt;br /&gt;
* creating a branch&lt;br /&gt;
* contributing code to a repo&lt;br /&gt;
* how to handle merge conflicts&lt;br /&gt;
&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;
# Sam Kome&lt;br /&gt;
# Paula Gray-Overtoom&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Archival discovery and use ===&lt;br /&gt;
'''Full Day''' &lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Tim Shearer, UNC Chapel Hill, tshearer at email.unc.edu, &lt;br /&gt;
* Will Sexton, Duke, will.sexton at duke.edu&lt;br /&gt;
&lt;br /&gt;
This is a full day pre-conference about archival collections and will cover the intersections of archives, workflows, technologies, discovery, and use.&lt;br /&gt;
&lt;br /&gt;
Morning agenda: focused talks around (but not limited to) issues such as:&lt;br /&gt;
* Crowd-sourcing description to enhance collecitons&lt;br /&gt;
* Linked data and authority&lt;br /&gt;
* Mass digitization and sustainable workflows&lt;br /&gt;
* Digitized objects in context (images and other objects in finding aids)&lt;br /&gt;
* Too many cooks in the kitchen: versioning&lt;br /&gt;
* Global-, intra-, and inter- discovery of archival materials via finding aids &lt;br /&gt;
* and more...&lt;br /&gt;
&lt;br /&gt;
Afternoon agenda:  Focused talks around specific tools followed by general discussion, connections, opportunities, aspirations, and planning.&lt;br /&gt;
&lt;br /&gt;
Tool examples:&lt;br /&gt;
* Archivespace&lt;br /&gt;
* STEADy&lt;br /&gt;
* &amp;quot;RAMP&amp;quot; (Remixing Archival Metadata Project)&lt;br /&gt;
* OpenRefine&lt;br /&gt;
* Aeon&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;
Morning:&lt;br /&gt;
* Julia Bauder&lt;br /&gt;
&lt;br /&gt;
Afternoon:&lt;br /&gt;
* your name&lt;br /&gt;
&lt;br /&gt;
All day:&lt;br /&gt;
&lt;br /&gt;
# Josh Wilson&lt;br /&gt;
# Sam Kome&lt;br /&gt;
# Linda Ballinger&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===AV Content Slam===&lt;br /&gt;
'''Half-Day [morning]'''&lt;br /&gt;
Contacts:&lt;br /&gt;
* Kara Van Malssen, kara (at) avpreserve.com&lt;br /&gt;
* Lauren Sorenson, laurens (at) bavc.org&lt;br /&gt;
* Steven Villereal , villereal (at) gmail.com&lt;br /&gt;
A morning BarCamp/unconference for practitioners and coders who work with audiovisual content. The agenda will be attendee-driven, with a focus on sharing, synthesizing, and improving workflow strategies and documentation for software-based approaches to wrangling and providing access to audio and video content.&lt;br /&gt;
Possible topics of discussion might include:&lt;br /&gt;
* Use of format id and characterization/metadata extraction tools for AV&lt;br /&gt;
* Creating and using time-based metadata&lt;br /&gt;
* Managing (moving, fixity checking, etc) massive files (like uncompressed video)&lt;br /&gt;
For a better idea of the topics and concerns that have informed some past AV-themed events, check out the event wikis for [http://wiki.curatecamp.org/index.php/CURATEcamp_AVpres_2013 CURATEcamp AVpres 2013] as well as the [http://wiki.curatecamp.org/index.php/Association_of_Moving_Image_Archivists_%26_Digital_Library_Federation_Hack_Day_2013 AMIA/DLF 2013 Hack Day] .&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;
----&lt;br /&gt;
&lt;br /&gt;
===OCLC Web Services Hackfest===&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Half-Day&amp;quot; [afternoon]&lt;br /&gt;
&lt;br /&gt;
Contact: Shelley Hostetler, Community Manager, Developer Network hostetls[at]oclc.org&lt;br /&gt;
&lt;br /&gt;
This half-day hackfest will explore some of the OCLC Developer Network web services. We will provide an overview of some of the common topics such as the general REST-based architecture for most services and how to use some new authentication clients. The group can then decide to take a deep dive into a particular API and/or write a client library for the community.&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;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Obey the Testing Goat!: Test Driven Web Development From The Ground Up===&lt;br /&gt;
'''Half-Day [tbd - probably afternoon]'''&lt;br /&gt;
* Contact [[User:Mredar|Mark Redar]], mredar[at]gmail.com&lt;br /&gt;
&lt;br /&gt;
Test driven development is a proven method for producing better quality code. But I've found it hard to follow a strict TDD methodology when starting new web projects. How do you write that first test when there is no code or web pages created yet.&lt;br /&gt;
&lt;br /&gt;
In this session, we will follow the excellent book [http://shop.oreilly.com/product/0636920029533.do &amp;quot;Test-Driven Web Development with Python&amp;quot;] to create a simple web site in Django following TDD from the first character typed. Come ready to code and test. No prior knowledge of python or Django required.&lt;br /&gt;
&lt;br /&gt;
By the end of this session, you should be able to  [http://www.obeythetestinggoat.com/ &amp;quot;Obey the Testing Goat&amp;quot;] from the start to finish for your next project.&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;
# Charlie Morris (NCSU)&lt;br /&gt;
# Jason Stirnaman&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
# Scott Hanrath&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Summon Camp===&lt;br /&gt;
Placeholder by Tim McGeary for Gillian Cain (Serials Solutions)&lt;br /&gt;
Description to be provided by Gillian after account issues resolved. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
[[:Category:Code4Lib2014]]&lt;/div&gt;</summary>
		<author><name>Rshanrath</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&amp;diff=40132</id>
		<title>2014 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&amp;diff=40132"/>
				<updated>2013-12-12T14:39:32Z</updated>
		
		<summary type="html">&lt;p&gt;Rshanrath: /* Fail4Lib 2014 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= PROPOSALS ARE CLOSED : PLEASE DO NOT ADD NEW PRECONFERENCES TO THIS PAGE =&lt;br /&gt;
&lt;br /&gt;
Proposals were accepted through December 6th, 2013.&lt;br /&gt;
&lt;br /&gt;
It would be really, super duper helpful if folks who think they might want to attend a pre-conference could indicate interest by adding your name to a session below. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Note===&lt;br /&gt;
Attendance at a pre-conference will require a small fee ''due at the time of conference registration&amp;quot;.&lt;br /&gt;
 &lt;br /&gt;
Although this was specified in the email announcements relating to pre-conferences, it was not added to this page until December 2nd.  I (Adam C.) apologize for the omission and I hope this will not cause any &amp;quot;sticker shock.&amp;quot;  Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.&lt;br /&gt;
&lt;br /&gt;
Please put your pre-conference on the list in the following format:&lt;br /&gt;
&lt;br /&gt;
=Code4Lib 2014 Pre-Conference Proposals=&lt;br /&gt;
&lt;br /&gt;
===Drupal4lib Sub-con Barcamp===&lt;br /&gt;
=====Full Day=====&lt;br /&gt;
&lt;br /&gt;
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.&lt;br /&gt;
&lt;br /&gt;
This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).&lt;br /&gt;
&lt;br /&gt;
[[resources to help you learn drupal]]&lt;br /&gt;
&lt;br /&gt;
====Interested in Attending:====&lt;br /&gt;
&lt;br /&gt;
=====All Day=====&lt;br /&gt;
&lt;br /&gt;
* Renna Tuten &lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
&lt;br /&gt;
* Kevin Reiss&lt;br /&gt;
* Charlie Morris (NCSU) - glad to see this again this year!&lt;br /&gt;
* Paula Gray-Overtoom&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Open Refine Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot;'''&lt;br /&gt;
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com&lt;br /&gt;
&lt;br /&gt;
[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control&lt;br /&gt;
&lt;br /&gt;
The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. &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;
&amp;lt;ol&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Adam Constabaris&lt;br /&gt;
&amp;lt;li&amp;gt;Ray Schwartz&lt;br /&gt;
&amp;lt;li&amp;gt;Jason Stirnaman&lt;br /&gt;
&amp;lt;li&amp;gt;Joshua Gomez&lt;br /&gt;
&amp;lt;li&amp;gt;Sam Kome&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Responsive Design Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day [Afternoon]&amp;quot;''' &lt;br /&gt;
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com&lt;br /&gt;
* Contact David Ward, University of Illinois, dh-ward@illinois.edu&lt;br /&gt;
&lt;br /&gt;
This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. &lt;br /&gt;
&lt;br /&gt;
Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.&lt;br /&gt;
&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;
&lt;br /&gt;
=== Intro to Blacklight ===&lt;br /&gt;
'''&amp;quot;Half-Day [Morning]&amp;quot;''' &lt;br /&gt;
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
* TA: Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
This session will be walk-through of the architecture of Blacklight, the community, and an introduction to building a Blacklight-based application. Each participant will have the opportunity to build a simple Blacklight application, and make basic customizations, while using a test-driven approach.&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;
&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;
# Bret Davidson&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Cory Lown&lt;br /&gt;
# Emily Daly&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Blacklight Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day [Afternoon]&amp;quot;''' &lt;br /&gt;
* Contact Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
&lt;br /&gt;
This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.&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 ).&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;
# Shaun Ellis&lt;br /&gt;
# Kevin Reiss&lt;br /&gt;
# Megan Kudzia&lt;br /&gt;
# Erik Hatcher&lt;br /&gt;
# Emily Daly&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
===RailsBridge: Intro to programming in Ruby on Rails===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
* Contact Justin Coyne, Data Curation Experts, justin@curationexperts.com&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! 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 Blacklight and Hydra.&lt;br /&gt;
&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;
1. Ayla Stein&lt;br /&gt;
&lt;br /&gt;
2. Heidi Dowding&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===&lt;br /&gt;
'''Full-Day'''&lt;br /&gt;
&lt;br /&gt;
Contact: &lt;br /&gt;
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com&lt;br /&gt;
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu&lt;br /&gt;
&lt;br /&gt;
This will be a full day session on project management.  We'll cover&lt;br /&gt;
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment&lt;br /&gt;
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets&lt;br /&gt;
* '''Executing the Project''' -- status meeting, status reports, issue management&lt;br /&gt;
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product&lt;br /&gt;
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.&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;
# Robin Dean&lt;br /&gt;
# Erin White&lt;br /&gt;
# Andrew Darby&lt;br /&gt;
# Sam Kome&lt;br /&gt;
# Ryan Scherle&lt;br /&gt;
# Will Shaw&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
# Cynthia &amp;quot;Arty&amp;quot; Ng&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Fail4Lib 2014===&lt;br /&gt;
'''Half Day [TBD, probably afternoon]'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Andreas Orphanides, akorphan (at) ncsu.edu&lt;br /&gt;
* Jason Casden, jmcasden (at) ncsu.edu&lt;br /&gt;
&lt;br /&gt;
The task of design (and the work that we do as library coders) is intimately tied to failure. Failures, both big and small, motivate us to create and improve. Failures are also occasionally the result of our work. Understanding and embracing failure, encouraging enlightened risk-taking, and seeking out opportunities to fail and learn are essential to success in our field. 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 feared.&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
&lt;br /&gt;
* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?&lt;br /&gt;
* Confessionals, for those willing to share. Talk about your own experiences with rough starts, labor pains, and doomed projects in your own work: What can we learn from our own (and each others') failures?&lt;br /&gt;
* Group therapy. Let's talk about how to deal with risk management, failed projects, experimental endeavors, and more: How can we make ourselves, our colleagues, and our organizations more fault tolerant? How do we make sure we fail as productively as possible?&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;
#Bret Davidson&lt;br /&gt;
#Mike Graves&lt;br /&gt;
#Ray Schwartz&lt;br /&gt;
#Jason Stirnaman&lt;br /&gt;
#Julia Bauder&lt;br /&gt;
#Linda Ballinger&lt;br /&gt;
#Scott Hanrath&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===CLLAM @ code4lib===&lt;br /&gt;
'''(Computational Linguistics for Libraries, Archives and Museums)'''&lt;br /&gt;
&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Douglas W. Oard (primary), oard (at) umd.edu &lt;br /&gt;
* Corey Harper, corey (dot) harper (at) nyu.edu&lt;br /&gt;
* Robert Sanderson, azaroth42 (at) gmail.com &lt;br /&gt;
* Robert Warren, rwarren (at) math.carleton.ca&lt;br /&gt;
&lt;br /&gt;
We will hack at the intersection of diverse content from Libraries, Archives and Museums and bleeding edge tools from computational linguistics for slicing and dicing that content. Did you just acquire the email archives of a startup company? Maybe you can automatically build an org chart. Have you got metadata in a slew of languages? Perhaps you can search it all using one query. Is name authority control for e-resources getting too costly? Let’s see if entity linking techniques can help. These are just a few teasers. &lt;br /&gt;
&lt;br /&gt;
There’ll be plenty of content and tools supplied, but please bring your own [data] too -- you’ll hack with it in new ways throughout the day. We’ll get started with some lightning talks on what we’ve brought,then we’ll break up into groups to experiment and work on the ideas that appeal. Three guaranteed outcomes: you’ll walk away with new ideas, new tools, and new people you’ll have met.&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;
# Devon Smith&lt;br /&gt;
# Kevin S. Clarke&lt;br /&gt;
# Jason Stirnaman&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== GeoHydra: Managing geospatial content ===&lt;br /&gt;
&lt;br /&gt;
'''Half-day [Afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Contact: Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Moderator: Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,&lt;br /&gt;
etc., all of which you want to integrate into your digital repository? In this&lt;br /&gt;
workshop, we will discuss how Hydra can provide discovery, delivery, and&lt;br /&gt;
management services for geospatial assets, as well as solicit questions about&lt;br /&gt;
your own GIS projects. We aim to help answer the following questions you might have about putting geospatial data into your Hydra-based digital library:&lt;br /&gt;
&lt;br /&gt;
* What are the types of geospatial data?&lt;br /&gt;
* How to dive into Hydra?&lt;br /&gt;
* How to model geospatial holdings with Hydra?&lt;br /&gt;
* How to discover and view geospatial data?&lt;br /&gt;
* How to build a geospatial data infrastructure?&lt;br /&gt;
* What are common approaches and problems?&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;
# Esmé Cowles&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Technology, Librarianship, and Gender: Moving the conversation forward===&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]&lt;br /&gt;
&lt;br /&gt;
'''Description'''&lt;br /&gt;
&lt;br /&gt;
Librarianship is largely made up of women, yet women are significantly underrepresented in tech positions, on any level, within libraries themselves. Why? What are we doing to encourage women to become more involved in STEM within librarianship? What kind of message are we sending when library technology keynotes remain almost resolutely male? How are we changing the face of technology, not only within libraries, but with the field itself? How are we training our staff and colleagues in the areas of fairness and removal of bias? Our vendors?&lt;br /&gt;
&lt;br /&gt;
Lots of tough questions.&lt;br /&gt;
&lt;br /&gt;
While the conversation has been going on via various blogs and articles within the last few years, it was given a public face at [http://infotoday.com/il2013/day.asp?day=Monday#session_D105 Internet Librarian 2013] where a panel of 7 (four women, three men) gave personal experiences on the above and then opened up the conversation to the audience. As eye opening and enriching the conversation was, a 45 minute panel was not enough. One thing remains clear: We need to keep the conversation moving forward and start making some radical changes in the way we think, act, and how we need to harness this to start making real changes within librarianship itself.&lt;br /&gt;
&lt;br /&gt;
Topics to include:  Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems,  mentoring, ally support, and more&lt;br /&gt;
&lt;br /&gt;
Those attending should expect: Begin with opening up the conversation of experiences and talking about what is most needed, spending remaining time putting together live, usable solutions to start implementing as well as pushing the conversation forward at local levels&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;
=====All Day=====&lt;br /&gt;
1. Kate Kosturski&lt;br /&gt;
&lt;br /&gt;
2. Valerie Aurora&lt;br /&gt;
&lt;br /&gt;
3. Declan Fleming (I'd be good with a half day too)&lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
1. Shaun Ellis&lt;br /&gt;
&lt;br /&gt;
2. Jason Casden&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
1. Ayla Stein&lt;br /&gt;
&lt;br /&gt;
2. Heidi Dowding&lt;br /&gt;
&lt;br /&gt;
3. Coral Sheldon-Hess&lt;br /&gt;
&lt;br /&gt;
4. Cory Lown&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===FileAnalyzer: Rapid Development of File Manipulation Tasks===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
* Contact Terry Brady, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The FileAnalyzer (https://github.com/Georgetown-University-Libraries/File-Analyzer) is an application designed to solve a number of library automation challenges:&lt;br /&gt;
&lt;br /&gt;
* validating digitized and reformatted files&lt;br /&gt;
* validating vendor statistics for counter compliance&lt;br /&gt;
* preparing collections of digital files for archiving and ingest&lt;br /&gt;
* manipulating ILS import and export files&lt;br /&gt;
&lt;br /&gt;
The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census. After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform. Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.&lt;br /&gt;
&lt;br /&gt;
The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules. As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.&lt;br /&gt;
&lt;br /&gt;
The first half of this session will be targeted to potential users and developers.  The second half of the session will be targeted towards developers who are interested in developing custom rules for the application.&lt;br /&gt;
&lt;br /&gt;
''Session Overview''&lt;br /&gt;
* Overview of the application&lt;br /&gt;
* Running sample file tests/transformations through the application&lt;br /&gt;
* Compiling and building the application&lt;br /&gt;
* Coding a custom file processing task&lt;br /&gt;
&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;
----&lt;br /&gt;
&lt;br /&gt;
===Collecting social media data with Social Feed Manager===&lt;br /&gt;
'''Half-Day [Morning]'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Dan Chudnov, GW Libraries, dchud (at) gwu.edu&lt;br /&gt;
* Dan Kerchner, GW Libraries, kerchner (at) gwu.edu&lt;br /&gt;
* Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu&lt;br /&gt;
&lt;br /&gt;
Social media data is a popular material for research and a new format for building collections.  What does it take to collect meaningfully from Twitter, Tumblr, YouTube, Weibo, Facebook, and other sites?  We will:&lt;br /&gt;
* Introduce options for collections, including both high- and low-end commercial offerings. Discuss what it means to collect these resources, covering boundaries, policies, and workflows required to develop a social media collection program in your institution.&lt;br /&gt;
* Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them&lt;br /&gt;
* Help you get started using the free [http://gwu-libraries.github.io/social-feed-manager Social Feed Manager] (SFM) app we're developing at GW to create your first collections. We’ll demo its use and demo a clean install (those w/environments can follow along)&lt;br /&gt;
&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;
# Declan Fleming&lt;br /&gt;
# Esmé Cowles&lt;br /&gt;
# Jason Stirnaman&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Intro to Git ===&lt;br /&gt;
'''&amp;quot;Half-Day [tbd - probably afternoon]&amp;quot;''' &lt;br /&gt;
* Contact: Erin Fahy, Stanford University, efahy at stanford.edu&lt;br /&gt;
* TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu&lt;br /&gt;
&lt;br /&gt;
This session will cover the fundamentals of git by discussing/going through (time allowing):&lt;br /&gt;
* what is a distributed version control system&lt;br /&gt;
* what is git and github&lt;br /&gt;
* initializing a repo on a remote server/github&lt;br /&gt;
* cloning an existing repo&lt;br /&gt;
* creating a branch&lt;br /&gt;
* contributing code to a repo&lt;br /&gt;
* how to handle merge conflicts&lt;br /&gt;
&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;
# Sam Kome&lt;br /&gt;
# Paula Gray-Overtoom&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Archival discovery and use ===&lt;br /&gt;
'''Full Day''' &lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Tim Shearer, UNC Chapel Hill, tshearer at email.unc.edu, &lt;br /&gt;
* Will Sexton, Duke, will.sexton at duke.edu&lt;br /&gt;
&lt;br /&gt;
This is a full day pre-conference about archival collections and will cover the intersections of archives, workflows, technologies, discovery, and use.&lt;br /&gt;
&lt;br /&gt;
Morning agenda: focused talks around (but not limited to) issues such as:&lt;br /&gt;
* Crowd-sourcing description to enhance collecitons&lt;br /&gt;
* Linked data and authority&lt;br /&gt;
* Mass digitization and sustainable workflows&lt;br /&gt;
* Digitized objects in context (images and other objects in finding aids)&lt;br /&gt;
* Too many cooks in the kitchen: versioning&lt;br /&gt;
* Global-, intra-, and inter- discovery of archival materials via finding aids &lt;br /&gt;
* and more...&lt;br /&gt;
&lt;br /&gt;
Afternoon agenda:  Focused talks around specific tools followed by general discussion, connections, opportunities, aspirations, and planning.&lt;br /&gt;
&lt;br /&gt;
Tool examples:&lt;br /&gt;
* Archivespace&lt;br /&gt;
* STEADy&lt;br /&gt;
* &amp;quot;RAMP&amp;quot; (Remixing Archival Metadata Project)&lt;br /&gt;
* OpenRefine&lt;br /&gt;
* Aeon&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;
Morning:&lt;br /&gt;
* Julia Bauder&lt;br /&gt;
&lt;br /&gt;
Afternoon:&lt;br /&gt;
* your name&lt;br /&gt;
&lt;br /&gt;
All day:&lt;br /&gt;
&lt;br /&gt;
# Josh Wilson&lt;br /&gt;
# Sam Kome&lt;br /&gt;
# Linda Ballinger&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===AV Content Slam===&lt;br /&gt;
'''Half-Day [morning]'''&lt;br /&gt;
Contacts:&lt;br /&gt;
* Kara Van Malssen, kara (at) avpreserve.com&lt;br /&gt;
* Lauren Sorenson, laurens (at) bavc.org&lt;br /&gt;
* Steven Villereal , villereal (at) gmail.com&lt;br /&gt;
A morning BarCamp/unconference for practitioners and coders who work with audiovisual content. The agenda will be attendee-driven, with a focus on sharing, synthesizing, and improving workflow strategies and documentation for software-based approaches to wrangling and providing access to audio and video content.&lt;br /&gt;
Possible topics of discussion might include:&lt;br /&gt;
* Use of format id and characterization/metadata extraction tools for AV&lt;br /&gt;
* Creating and using time-based metadata&lt;br /&gt;
* Managing (moving, fixity checking, etc) massive files (like uncompressed video)&lt;br /&gt;
For a better idea of the topics and concerns that have informed some past AV-themed events, check out the event wikis for [http://wiki.curatecamp.org/index.php/CURATEcamp_AVpres_2013 CURATEcamp AVpres 2013] as well as the [http://wiki.curatecamp.org/index.php/Association_of_Moving_Image_Archivists_%26_Digital_Library_Federation_Hack_Day_2013 AMIA/DLF 2013 Hack Day] .&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;
----&lt;br /&gt;
&lt;br /&gt;
===OCLC Web Services Hackfest===&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Half-Day&amp;quot; [afternoon]&lt;br /&gt;
&lt;br /&gt;
Contact: Shelley Hostetler, Community Manager, Developer Network hostetls[at]oclc.org&lt;br /&gt;
&lt;br /&gt;
This half-day hackfest will explore some of the OCLC Developer Network web services. We will provide an overview of some of the common topics such as the general REST-based architecture for most services and how to use some new authentication clients. The group can then decide to take a deep dive into a particular API and/or write a client library for the community.&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;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Obey the Testing Goat!: Test Driven Web Development From The Ground Up===&lt;br /&gt;
'''Half-Day [tbd - probably afternoon]'''&lt;br /&gt;
* Contact [[User:Mredar|Mark Redar]], mredar[at]gmail.com&lt;br /&gt;
&lt;br /&gt;
Test driven development is a proven method for producing better quality code. But I've found it hard to follow a strict TDD methodology when starting new web projects. How do you write that first test when there is no code or web pages created yet.&lt;br /&gt;
&lt;br /&gt;
In this session, we will follow the excellent book [http://shop.oreilly.com/product/0636920029533.do &amp;quot;Test-Driven Web Development with Python&amp;quot;] to create a simple web site in Django following TDD from the first character typed. Come ready to code and test. No prior knowledge of python or Django required.&lt;br /&gt;
&lt;br /&gt;
By the end of this session, you should be able to  [http://www.obeythetestinggoat.com/ &amp;quot;Obey the Testing Goat&amp;quot;] from the start to finish for your next project.&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;
# Charlie Morris (NCSU)&lt;br /&gt;
# Jason Stirnaman&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Summon Camp===&lt;br /&gt;
Placeholder by Tim McGeary for Gillian Cain (Serials Solutions)&lt;br /&gt;
Description to be provided by Gillian after account issues resolved. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
[[:Category:Code4Lib2014]]&lt;/div&gt;</summary>
		<author><name>Rshanrath</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_Code4Lib_Midwest_Conference&amp;diff=39541</id>
		<title>2013 Code4Lib Midwest Conference</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_Code4Lib_Midwest_Conference&amp;diff=39541"/>
				<updated>2013-09-11T21:32:35Z</updated>
		
		<summary type="html">&lt;p&gt;Rshanrath: /* Registration */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Code4Lib Midwest 2013==&lt;br /&gt;
Please join us Sunday, October 13, and Monday, October 14, in Iowa City for the Code4Lib Midwest 2013 conference! This informal conference will feature short lightning talks, longer presentations, workshops, and breakout discussion sessions covering technology in libraries, archives and museums in the Midwest. Each Code4Lib conference is different; take a look through the main [http://code4lib.org/about Code4Lib Wiki] to learn more about this volunteer-driven collective.&lt;br /&gt;
* Twitter hash tag: [http://twitter.com/#!/search/%23c4lmw #c4lmw]&lt;br /&gt;
===Location===&lt;br /&gt;
Code4Lib MidWest meeting will be hosted by [http://lib.uiowa.edu University of Iowa Libraries].&lt;br /&gt;
* '''When''' - Sunday, October 13th - Monday, October 14th&lt;br /&gt;
* '''Where''' - [http://www.uiowa.edu/~maps/p/pbb1.htm John Pappajohn Business Building, University of Iowa], Room W401 &lt;br /&gt;
* '''Registration Cost''' - Free!&lt;br /&gt;
* '''Planning Committee''' - Emily Shaw (emily-f-shaw@uiowa.edu), Shawn Averkamp (shawn-averkamp@uiowa.edu), Becky Yoose(YOOSEBEC@grinnell.edu), Julia Bauder (BAUDERJ@grinnell.edu), Wendy Robertson (wendy-robertson@uiowa.edu), Matthew Butler (matthew-butler@uiowa.edu)&lt;br /&gt;
&lt;br /&gt;
===Logistics===&lt;br /&gt;
* Lodging&lt;br /&gt;
** We have blocked off rooms for 10/13 &amp;amp; 10/14 at the [http://www.sheratoniowacity.com/ Sheraton Iowa City] as the official hotel. The group name is &amp;quot;Code4Lib&amp;quot;. You can either call and let them know you're part of this group, or book online through [https://www.starwoodmeeting.com/StarGroupsWeb/booking/reservation?id=1308068499&amp;amp;key=3130C this event registration page]. These rooms are available at a discounted rate ($99/night, wifi included), and are held on a first come first served basis. Reservations must be booked by '''September 14, 2013''' or the rooms will be released back to the public. It's a pretty nice hotel, and a pleasant, easy walk through downtown Iowa City to the room where we'll be meeting. The Sheraton has an attached parking garage; ask about parking when you call to reserve a room.&lt;br /&gt;
&lt;br /&gt;
* Transportation&lt;br /&gt;
** '''Bus -''' [http://www.greyhound.com/ Greyhound], [http://us.megabus.com/ Megabus] (routes to Iowa City from Chicago, Omaha, Des Moines)&lt;br /&gt;
** '''Air - ''' [http://www.eiairport.org/ Eastern Iowa Airport](CID, in Cedar Rapids) is the closest airport (22 miles); [http://www.crshuttle.com/ Cedar Rapids Airport Shuttle] can get you to and from the airport (reserve in advance). [http://www.qcairport.com/ Quad City International Airport] (MLI) is 66 miles away, but flights are often cheaper; unfortunately, a shuttle or taxi to/from there might cost you almost as much as your flight. &lt;br /&gt;
** '''Driving -''' Iowa City is off of I-80, which every Midwesterner should know how to get to :)   There are several [http://en.parkopedia.com/parking/building/john-pappajohn-business-building-johnson-ia/ public parking structures] around campus, in easy walking distance to both the Sheraton (conference hotel) and Pappajohn Business Building (meeting room).&lt;br /&gt;
&lt;br /&gt;
==Programming Sign-up==&lt;br /&gt;
&lt;br /&gt;
Share what you are working on! We would also love to hear some ideas for a Sunday morning workshop/hackfest. Add your name and a description below.&lt;br /&gt;
&lt;br /&gt;
===Workshops/Hackfest===&lt;br /&gt;
List your name and what you want to hack, teach, or see someone else teach.&lt;br /&gt;
*Shawn Averkamp -- Linked Data Tool Share: Let's share tips and tricks for making/publishing/consuming linked data. How to set up a SPARQL server? How to use parsers and serializers? I don't have that many tricks up my sleeve yet, so add your name and comments here if you'd like to help organize.&lt;br /&gt;
*Emily Shaw (UIowa) - CurateCamp, anyone? I've participated in a grand total of 1 before, but it was great and I'd be glad to facilitate if others are interested.&lt;br /&gt;
*Ian Mason (UIowa) -- Displaying data on Google charts or maps with Python?&lt;br /&gt;
*&lt;br /&gt;
more...&lt;br /&gt;
&lt;br /&gt;
===Presentations===&lt;br /&gt;
15-20 minutes suggested, but feel free to propose a longer talk.&lt;br /&gt;
* Mark McFate (Grinnell College) - The Status of Islandora and Digital.Grinnell -- Islandora and http://Digital.Grinnell.edu are evolving rapidly.  See what's new in Islandora and get a glimpse of how it’s used in Digital.Grinnell.    &lt;br /&gt;
* Alan Schmitz (Iowa State University - SILO Program) - Iowa Heritage Digital Collections and Omeka -- http://www.iowaheritage.org/&lt;br /&gt;
* Jason Paulios (Iowa City Public Library) - ICPL Local Music Project -- http://music.icpl.org/&lt;br /&gt;
* Brian Zelip (UIUC, GSLIS) - Support Community Memory! [http://localwiki.org LocalWiki] &amp;amp; Library Engagement&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
more...&lt;br /&gt;
&lt;br /&gt;
===Lightning Talks===&lt;br /&gt;
5 minutes suggested. We'll open more slots at the conference.&lt;br /&gt;
# Logan Jewett -- ETD conversion project (Sunday)&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;
==Schedule==&lt;br /&gt;
&lt;br /&gt;
===Sunday, October 13===&lt;br /&gt;
&lt;br /&gt;
====Mingling (9:00am - 9:30am)====&lt;br /&gt;
&lt;br /&gt;
====Workshops/Hackfest (9:30am - 12:00pm):====&lt;br /&gt;
Pitch an idea above.&lt;br /&gt;
&lt;br /&gt;
====Lunch (12:00pm - 1:30pm)====&lt;br /&gt;
Lunch on your own. &lt;br /&gt;
&lt;br /&gt;
====Talks (1:30pm - 5:00pm)====&lt;br /&gt;
&lt;br /&gt;
====Social Outing (5:30pm)====&lt;br /&gt;
TBD&lt;br /&gt;
&lt;br /&gt;
===Monday, October 14===&lt;br /&gt;
&lt;br /&gt;
====Coffee (8:30am - 9:00am)====&lt;br /&gt;
Get your name badge, drink some coffee, eat a snack, and meet some library folks.&lt;br /&gt;
&lt;br /&gt;
====Talks (9:00am - 12:00pm)====&lt;br /&gt;
&lt;br /&gt;
====Lunch (12:00pm - 1:30pm)====&lt;br /&gt;
Lunch on your own&lt;br /&gt;
&lt;br /&gt;
====More Talks (1:30pm - 4:00pm)====&lt;br /&gt;
&lt;br /&gt;
==Registration==&lt;br /&gt;
&lt;br /&gt;
'''Registration is free.''' We have tables and chairs for about 50 people, but we have plenty of perimeter seating if you sign up too late. List your name, affiliation, and email address here to register for the meeting. If you signed up and are unable to attend please remove your name or contact us, so that we can make room for others.&lt;br /&gt;
&lt;br /&gt;
Contact Ryan Wick (ryanwick@gmail.com) with your preferred username to set up a Code4Lib wiki account, or ask Shawn Averkamp (shawn-averkamp@uiowa.edu) to add your name to this list if you prefer not to set up an account.:&lt;br /&gt;
&lt;br /&gt;
# Matthew Butler, University of Iowa, matthew-butler@uiowa.edu&lt;br /&gt;
# Becky Yoose, Grinnell College, yoosebec at grinnell dot edu (maybe on Sunday, definitely on Monday)&lt;br /&gt;
# Julia Bauder, Grinnell College, bauderj at grinnell dot edu&lt;br /&gt;
# Samantha Helmick, Burlington Public Library, shelmick@burlington.lib.ia.us&lt;br /&gt;
# Kelly Thompson, Iowa State University, kellyt@iastate.edu&lt;br /&gt;
# Jason Stirnaman, University of Kansas Medical Center (KC), jstirnaman@kumc.edu&lt;br /&gt;
# Sarah Park, Northwest Missouri State University, gopark at nwmissouri dot edu&lt;br /&gt;
# Ian Mason, University of Iowa, ian-mason@uiowa.edu&lt;br /&gt;
# Shannon Cody, University of Iowa, shannon-cody@uiowa.edu&lt;br /&gt;
# Jillian Phillips, University of Iowa, jillian-phillips@uiowa.edu&lt;br /&gt;
# Kathy Magarrell, University of Iowa, kathy-magarrell@uiowa.edu&lt;br /&gt;
# Wendy Robertson, University of Iowa, wendy-robertson@uiowa.edu&lt;br /&gt;
# Audrey Altman, University of Iowa, audrey-altman@uiowa.edu&lt;br /&gt;
# Micah Bateman, University of Iowa, micah-bateman@uiowa.edu&lt;br /&gt;
# Alan Schmitz, Iowa State University, aschmitz@silo.lib.ia.us&lt;br /&gt;
# Jerry Balmer, Iowa State University, jbalmer@silo.lib.ia.us&lt;br /&gt;
# Paul Ertz, Iowa State University, pertz@silo.lib.ia.us&lt;br /&gt;
# Marie Harms, Iowa Library Services, marie.harms@lib.state.ia.us&lt;br /&gt;
# Mark McFate, Grinnell College, mcfatem at grinnell dot edu&lt;br /&gt;
# Robert Manaster, University of Illinois (UC), manaster at illinois dot edu&lt;br /&gt;
# Brett Cloyd, University of Iowa, brett-cloyd@uiowa.edu&lt;br /&gt;
# Sue Julich, University of Iowa, suzanne-julich@uiowa.edu&lt;br /&gt;
# Melody Dworak, Iowa City Public Library, melody-dworak@icpl.org&lt;br /&gt;
# Deana Greenfield, National Louis University Chicago, deana.greenfield@nl.edu&lt;br /&gt;
# Colleen Theisen, University of Iowa Special Collections &amp;amp; University Archives, colleen-theisen@uiowa.edu&lt;br /&gt;
# Ben Rodriguez, University of Illinois Urbana Champaign, benrodriguez9@gmail.com&lt;br /&gt;
# Christine Vivian, University of Iowa, christine-vivian@uiowa.edu&lt;br /&gt;
# Roberto Arteaga, University of Iowa, roberto-arteaga@uiowa.edu&lt;br /&gt;
# Beth Kamp, Freelance Librarian, beth-kamp@uiowa.edu&lt;br /&gt;
# Jon Gorman, University of Illinois - Urbana Champaign, jtgorman@illinois.edu&lt;br /&gt;
# Kirk Hess, University of Illinois at Urbana-Champaign, kirkhess@illinois.edu&lt;br /&gt;
# Amy Weidner, Benedictine University, aweidner@ben.edu&lt;br /&gt;
# Sara Pitcher, Coralville Public Library, spitcher@coralville.lib.ia.us&lt;br /&gt;
# Amy LeFager, National Louis University, amy.lefager@nl.edu&lt;br /&gt;
# Mark Baldwin, University of Illinois at Urbana-Champaign, mbaldwi2@illinois.edu&lt;br /&gt;
# Olivia Husman, University of Illinois at Urbana-Champaign, husman2@illinois.edu&lt;br /&gt;
# Wesley Teal, University of Iowa, wesley-teal@uiowa.edu&lt;br /&gt;
# Carol Marquardsen, carol.marquardsen@gmail.com&lt;br /&gt;
# Cate Kompare, cmkompare@gmail.com&lt;br /&gt;
# Peg Lawrence, Minnesota State University, Mankato margaret.lawrence@mnsu.edu&lt;br /&gt;
# Graham Hukill, Wayne State University, graham.hukill@wayne.edu&lt;br /&gt;
# Cole Hudson, Wayne State University, cole.hudson@wayne.edu&lt;br /&gt;
# Lynne Weber, Minnesota State University, Mankato, lnweber@mnsu.edu&lt;br /&gt;
# Amber Carlson, Davenport Public Library, acarlson@davenportlibrary.com&lt;br /&gt;
# Stephen Wynn, Truman State University, swynn@truman.edu&lt;br /&gt;
# Rebecca Pfenning, Dominican University &amp;amp; Calumet City Public Library, rebeccapfenning@gmail.com&lt;br /&gt;
# Larry Palmquist, University of Kansas, l-palmquist@ku.edu&lt;br /&gt;
# Benjamin Klahn, Joliet Public Library, bklahn@jolietlibrary.org&lt;br /&gt;
# Torii Moré, McLean County Museum of History, TMore@mchistory.org&lt;br /&gt;
# Logan Jewett, Iowa State University, lejewett@iastate.edu (Sunday only)&lt;br /&gt;
# Susan Green, Bettendorf Public Library, sgreen@bettendorf.org&lt;br /&gt;
# Brian Zelip, University of Illinois at Urbana-Champaign, @bzelip, bzelip@illinois.edu&lt;br /&gt;
# Thomas Keyser, Iowa Library Services, thomas.keyser@lib.state.ia.us&lt;br /&gt;
# Andrew Holland, University of Iowa Libraries, andrew-holland@uiowa.edu&lt;br /&gt;
# Mollie Stanford, Arrowhead Library System (Mt. Iron, MN), molliestanford@arrowhead.lib.mn.us&lt;br /&gt;
# Vicky Maloy, Mount Mercy University, vmaloy@mtmercy.edu&lt;br /&gt;
# Steve Redmond, Davenport Public Library, sredmond@davenportlibrary.com&lt;br /&gt;
# Madison Sullivan, University of Illinois at Urbana-Champaign, mesulli3@illinois.edu&lt;br /&gt;
# Drew Parker, University of Iowa, andrew-parker-1@uiowa.edu&lt;br /&gt;
&lt;br /&gt;
The capacity of our venue requires us to cap participation at 60. Beyond that, please put your name, affiliation and email address on the wait list and we'll email you if a spot opens up for you.&lt;br /&gt;
------------------&lt;br /&gt;
Waitlist:&lt;br /&gt;
&lt;br /&gt;
# Matt Marcukaitis, Olivet Nazarene University, mwmarcukaitis@olivet.edu&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Previous C4L Midwest Regional Meetings ==&lt;br /&gt;
&lt;br /&gt;
* [[2010 (Inaugural) Code4Lib Midwest Meeting]]&lt;br /&gt;
* [[2011 Code4Lib Midwest Meeting]]&lt;br /&gt;
* [[2012 Code4Lib Midwest Meeting]]&lt;br /&gt;
&lt;br /&gt;
== Mailing list ==&lt;br /&gt;
&lt;br /&gt;
For better or for worse, Code4Lib &amp;quot;Midwest&amp;quot; has low-traffic [http://groups.google.com/group/code4lib-midwest mailing list/Google group]. Consider subscribing.&lt;/div&gt;</summary>
		<author><name>Rshanrath</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_Code4Lib_Midwest_Conference&amp;diff=39375</id>
		<title>2013 Code4Lib Midwest Conference</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_Code4Lib_Midwest_Conference&amp;diff=39375"/>
				<updated>2013-07-30T21:39:56Z</updated>
		
		<summary type="html">&lt;p&gt;Rshanrath: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Code4Lib Midwest 2013==&lt;br /&gt;
Please join us Sunday, October 13, and Monday, October 14, in Iowa City for the Code4Lib Midwest 2013 conference! This informal conference will feature short lightning talks, longer presentations, workshops, and breakout discussion sessions covering technology in libraries, archives and museums in the Midwest&lt;br /&gt;
* Twitter hash tag: [http://twitter.com/#!/search/%23c4lmw #c4lmw]&lt;br /&gt;
===Location===&lt;br /&gt;
Code4Lib MidWest meeting will be hosted by [http://lib.uiowa.edu University of Iowa Libraries].&lt;br /&gt;
* '''When''' - Sunday, October 13th - Monday, October 14th&lt;br /&gt;
* '''Where''' - [http://www.uiowa.edu/~maps/p/pbb1.htm John Pappajohn Business Building, University of Iowa], Room W401 &lt;br /&gt;
* '''Registration Cost''' - Free!&lt;br /&gt;
* '''Planning Committee''' - Emily Shaw (emily-f-shaw@uiowa.edu), Shawn Averkamp (shawn-averkamp@uiowa.edu), Becky Yoose(YOOSEBEC@grinnell.edu), Julia Bauder (BAUDERJ@grinnell.edu), Wendy Robertson (wendy-robertson@uiowa.edu), Matthew Butler (matthew-butler@uiowa.edu)&lt;br /&gt;
&lt;br /&gt;
===Logistics===&lt;br /&gt;
* Lodging&lt;br /&gt;
** We have blocked off rooms for 10/13 &amp;amp; 10/14 at the [http://www.sheratoniowacity.com/ Sheraton Iowa City] as the official hotel. The group name is &amp;quot;Code4Lib&amp;quot;. These rooms are available at a discounted rate ($99/night, wifi included), and are held on a first come first served basis. Reservations must be booked by '''September 14, 2013''' or the rooms will be released back to the public. It's a pretty nice hotel, and a pleasant, easy walk through downtown Iowa City to the room where we'll be meeting. The Sheraton has an attached parking garage; ask about parking when you call to reserve a room.&lt;br /&gt;
&lt;br /&gt;
* Transportation&lt;br /&gt;
** '''Bus -''' [http://www.greyhound.com/ Greyhound], [http://us.megabus.com/ Megabus] (routes to Iowa City from Chicago, Omaha, Des Moines)&lt;br /&gt;
** '''Air - ''' [http://www.eiairport.org/ Eastern Iowa Airport](CID, in Cedar Rapids) is the closest airport (22 miles); [http://www.crshuttle.com/ Cedar Rapids Airport Shuttle] can get you to and from the airport (reserve in advance). [http://www.qcairport.com/ Quad City International Airport] (MLI) is 66 miles away, but flights are often cheaper; unfortunately, a shuttle or taxi to/from there might cost you almost as much as your flight. &lt;br /&gt;
** '''Driving -''' Iowa City is off of I-80, which every Midwesterner should know how to get to :)   There are several [http://en.parkopedia.com/parking/building/john-pappajohn-business-building-johnson-ia/ public parking structures] around campus, in easy walking distance to both the Sheraton (conference hotel) and Pappajohn Business Building (meeting room).&lt;br /&gt;
&lt;br /&gt;
==Programming Sign-up==&lt;br /&gt;
&lt;br /&gt;
Share what you are working on! We would also love to hear some ideas for a Sunday morning workshop/hackfest. Add your name and a description below.&lt;br /&gt;
&lt;br /&gt;
===Workshops/Hackfest===&lt;br /&gt;
List your name and what you want to hack, teach, or see someone else teach.&lt;br /&gt;
*Shawn Averkamp -- Linked Data Tool Share: Let's share tips and tricks for making/publishing/consuming linked data. How to set up a SPARQL server? How to use parsers and serializers? I don't have that many tricks up my sleeve yet, so add your name and comments here if you'd like to help organize.&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
more...&lt;br /&gt;
&lt;br /&gt;
===Presentations===&lt;br /&gt;
15-20 minutes suggested, but feel free to propose a longer talk.&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
more...&lt;br /&gt;
&lt;br /&gt;
===Lightning Talks===&lt;br /&gt;
5 minutes suggested. We'll open more slots at the conference.&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;
==Schedule==&lt;br /&gt;
&lt;br /&gt;
===Sunday, October 13===&lt;br /&gt;
&lt;br /&gt;
====Mingling (9:00am - 9:30am)====&lt;br /&gt;
&lt;br /&gt;
====Workshops/Hackfest (9:30am - 12:00pm):====&lt;br /&gt;
Pitch an idea above.&lt;br /&gt;
&lt;br /&gt;
====Lunch (12:00pm - 1:30pm)====&lt;br /&gt;
Lunch on your own. &lt;br /&gt;
&lt;br /&gt;
====Talks (1:30pm - 5:00pm)====&lt;br /&gt;
&lt;br /&gt;
====Social Outing (5:30pm)====&lt;br /&gt;
Dinner at The Mill&lt;br /&gt;
&lt;br /&gt;
===Monday, October 14===&lt;br /&gt;
&lt;br /&gt;
====Coffee (8:30am - 9:00am)====&lt;br /&gt;
Get your name badge, drink some coffee, eat a snack, and meet some library folks.&lt;br /&gt;
&lt;br /&gt;
====Talks (9:00am - 12:00pm)====&lt;br /&gt;
&lt;br /&gt;
====Lunch (12:00pm - 1:30pm)====&lt;br /&gt;
Lunch on your own&lt;br /&gt;
&lt;br /&gt;
====More Talks (1:30pm - 4:00pm)====&lt;br /&gt;
&lt;br /&gt;
==Registration==&lt;br /&gt;
&lt;br /&gt;
'''Registration is free.''' We have tables and chairs for 50 people, but you're welcome to sit on the sidelines if you sign up too late. List your name, affiliation, and email address here to register for the meeting. (Contact Ryan Wick (ryanwick@gmail.com) with your preferred username to set up a Code4Lib wiki account, or ask Shawn Averkamp (shawn-averkamp@uiowa.edu) to add your name to this list if you prefer not to set up an account.):&lt;br /&gt;
&lt;br /&gt;
# Matthew Butler, University of Iowa, matthew-butler@uiowa.edu&lt;br /&gt;
# Shawn Averkamp, University of Iowa, shawn-averkamp@uiowa.edu&lt;br /&gt;
# Emily Shaw, University of Iowa, emily-f-shaw@uiowa.edu&lt;br /&gt;
# Becky Yoose, Grinnell College, yoosebec at grinnell dot edu (maybe on Sunday, definitely on Monday)&lt;br /&gt;
# Julia Bauder, Grinnell College, bauderj at grinnell dot edu&lt;br /&gt;
# Samantha Helmick, Burlington Public Library, shelmick@burlington.lib.ia.us&lt;br /&gt;
# Kelly Thompson, Iowa State University, kellyt@iastate.edu&lt;br /&gt;
# Jason Stirnaman, University of Kansas Medical Center (KC), jstirnaman@kumc.edu&lt;br /&gt;
# Sarah Park, Northwest Missouri State University, gopark at nwmissouri dot edu&lt;br /&gt;
# Scott Hanrath, University of Kansas, shanrath@ku.edu&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Previous C4L Midwest Regional Meetings ==&lt;br /&gt;
&lt;br /&gt;
* [[2010 (Inaugural) Code4Lib Midwest Meeting]]&lt;br /&gt;
* [[2011 Code4Lib Midwest Meeting]]&lt;br /&gt;
* [[2012 Code4Lib Midwest Meeting]]&lt;br /&gt;
&lt;br /&gt;
== Mailing list ==&lt;br /&gt;
&lt;br /&gt;
For better or for worse, Code4Lib &amp;quot;Midwest&amp;quot; has low-traffic [http://groups.google.com/group/code4lib-midwest mailing list/Google group]. Consider subscribing.&lt;/div&gt;</summary>
		<author><name>Rshanrath</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Midwest_2013_planning&amp;diff=39210</id>
		<title>Midwest 2013 planning</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Midwest_2013_planning&amp;diff=39210"/>
				<updated>2013-05-05T14:13:09Z</updated>
		
		<summary type="html">&lt;p&gt;Rshanrath: /* Who/When */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib Midwest 2013 planning =&lt;br /&gt;
&lt;br /&gt;
Disappointed you won't be going to Austin for Code4Lib next year? Come visit the (one true) &amp;quot;Austin of the Midwest,&amp;quot; aka Iowa City! [http://lib.uiowa.edu University of Iowa Libraries] would like to host your 2013 Code4Lib Midwest meeting, and we'd like to know how best to get you all here. We can offer dates in either August (any time from 8/1-9, 8/16-17, or 8/23-24) or in late September/early October, and we want to know when would work best for you. If you might be interested in attending, leave your name, organization, and preferred dates below (or contact us directly), so we can have an estimate for booking an appropriately sized room. More details to follow.&lt;br /&gt;
&lt;br /&gt;
==Where==&lt;br /&gt;
University of Iowa Libraries, Iowa City, IA&lt;br /&gt;
&lt;br /&gt;
==Who/When==&lt;br /&gt;
Even if you're unsure you'll be able to attend, let us know if you're interested and your preferences for dates (August--anytime from 8/1-9, 8/16-17, or 8/23-24 or in late September/early October)&lt;br /&gt;
* Shawn Averkamp, University of Iowa (no preference on dates)&lt;br /&gt;
* Emily Shaw, University of Iowa (prefer late September/early October, but could do August)&lt;br /&gt;
* Matthew Butler, University of Iowa (August)&lt;br /&gt;
* Audrey Altman, University of Iowa (August)&lt;br /&gt;
* Francis Kayiwa, University of Illinois at Chicago (late August 8/23+ or late September/early October)&lt;br /&gt;
* Linda Ballinger, Newberry Library (mid to late August [okay] or late September/early October [better])&lt;br /&gt;
* Margaret  Heller, Loyola University Chicago (no preference on dates)&lt;br /&gt;
* Aaron Collie, Michigan State University. No preferences on dates.&lt;br /&gt;
* Becky Yoose, Grinnell College (no preference, except not late August)&lt;br /&gt;
* Ranti Junus, Michigan State University (no preference)&lt;br /&gt;
* Julia Bauder, Grinnell College (prefer late September, mid-October, or mid/late August, could do early August, couldn't do October 4-6.)&lt;br /&gt;
* Esther Verreau, Skokie Public Library (no preference)&lt;br /&gt;
* John Barneson, University of Minnesota, prefer Fall&lt;br /&gt;
* Jason Stirnaman, University of Kansas Medical Center (Fall)&lt;br /&gt;
* Scott Hanrath, University of Kansas (prefer Sep/Oct)&lt;br /&gt;
&lt;br /&gt;
==Volunteer==&lt;br /&gt;
Sign up here if you'd like to help with planning.&lt;br /&gt;
* Matthew Butler&lt;br /&gt;
* Becky Yoose&lt;br /&gt;
* Julia Bauder&lt;br /&gt;
&lt;br /&gt;
==Contact==&lt;br /&gt;
* Shawn Averkamp, University of Iowa, shawn-averkamp@uiowa.edu&lt;br /&gt;
* Emily Shaw, University of Iowa, emily-f-shaw@uiowa.edu&lt;br /&gt;
&lt;br /&gt;
==Mailing List==&lt;br /&gt;
Sign up for updates and participate in planning on the [http://groups.google.com/group/code4lib-midwest Code4Lib Midwest mailing list/Google group].&lt;/div&gt;</summary>
		<author><name>Rshanrath</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_Twitter_List&amp;diff=36612</id>
		<title>2013 Twitter List</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_Twitter_List&amp;diff=36612"/>
				<updated>2013-02-12T20:04:20Z</updated>
		
		<summary type="html">&lt;p&gt;Rshanrath: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Put your twitter handle in here, if you're at Code4Lib 2013 Chicago. I'll add you to the [https://twitter.com/code4lib/attendees-2013 Attendees 2013 twitter list] for @code4lib when I get a chance. Thanks! -Sean&lt;br /&gt;
&lt;br /&gt;
# Becky Yoose (@yo_bj)&lt;br /&gt;
# Beatrice Pulliam (@beatricepulliam)&lt;br /&gt;
# Cynthia Ng (@TheRealArty)&lt;br /&gt;
# Nettie Lagace (@abugseye)&lt;br /&gt;
# Erin White (@erinrwhite)&lt;br /&gt;
# Maccabee Levine (@maccabeelevine)&lt;br /&gt;
# Steven Bassett (@bassettsj)&lt;br /&gt;
# Steve Oberg (@techsvcslib)&lt;br /&gt;
# Carmen Mitchell (@carmendarlene)&lt;br /&gt;
# Christie Peterson (@save4use)&lt;br /&gt;
# Jason Casden (@cazzerson)&lt;br /&gt;
# Michael Poltorak (@michaelpoltorak)&lt;br /&gt;
# Ron Gilmour (@gilmour70)&lt;br /&gt;
# James Staub (@jamesstaub)&lt;br /&gt;
# Curtis Thacker (@curtisthacker)&lt;br /&gt;
# Masao Takaku (@tmasao)&lt;br /&gt;
# Colin Watt (@colinmwatt)&lt;br /&gt;
# Dave Green (@icookwithwine)&lt;br /&gt;
# Alan Dyck (@Alan_Dyck)&lt;br /&gt;
# Megan O'Neill Kudzia (@meganoneill)&lt;br /&gt;
# Keith Nickum (@keithnickum)&lt;br /&gt;
# Matt Critchlow (@mattcritchlow)&lt;br /&gt;
# Matt Bernhardt (@morphosis7)&lt;br /&gt;
# May Chan (@msuicat)&lt;br /&gt;
# Courtney C. Mumma (@snarkivist, @Archivematica)&lt;br /&gt;
# Scott Hanrath (@rshanrath)&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2013]]&lt;/div&gt;</summary>
		<author><name>Rshanrath</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_preconference_proposals&amp;diff=35782</id>
		<title>2013 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_preconference_proposals&amp;diff=35782"/>
				<updated>2013-02-05T16:21:21Z</updated>
		
		<summary type="html">&lt;p&gt;Rshanrath: /* Data Visualization Hackfest */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Please sign up to attend by January 15th. Doesn't mean you can't change your mind, but we will use the host committee will use these numbers to assign rooms.&lt;br /&gt;
&lt;br /&gt;
Proposals '''now closed'''.&lt;br /&gt;
&lt;br /&gt;
Spaces available: 4+ Rooms&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
=== Talk Title ===&lt;br /&gt;
 &lt;br /&gt;
* Presenter/Leader, affiliation (optional), and email address (mandatory!)&lt;br /&gt;
* Second Presenter/Leader, affiliation, email address, if applicable&lt;br /&gt;
&lt;br /&gt;
Description.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Full Day==&lt;br /&gt;
&lt;br /&gt;
===Drupal4lib Sub-con Barcamp===&lt;br /&gt;
&lt;br /&gt;
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or &lt;br /&gt;
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.&lt;br /&gt;
&lt;br /&gt;
If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.&lt;br /&gt;
&lt;br /&gt;
This event is open to the library community. There is a nominal fee ($10) for non-Code4LibCon attendees.&lt;br /&gt;
&lt;br /&gt;
Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.&lt;br /&gt;
&lt;br /&gt;
====I plan on attending:====&lt;br /&gt;
&lt;br /&gt;
=====All Day=====&lt;br /&gt;
*Margaret Heller&lt;br /&gt;
*Mahria Lebow, mahria at uw edu&lt;br /&gt;
*Paula Gray-Overtoom, pgrayove at gmail.com&lt;br /&gt;
*Dhanushka Samarakoon, dhanu80 at g mail com&lt;br /&gt;
*Leo Robert Klein &amp;lt;del&amp;gt;(when he figures out what date this is)&amp;lt;/del&amp;gt; - 2/11 (9a-5p).  P.S. Oh Great One!  Who do we hand the 10 bucks to?&lt;br /&gt;
*Sarah Shealy, sarah.shealy at gmail.com&lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
* [[User:Kevenj|Keven Jeffery]]&lt;br /&gt;
* Sean Chen&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)&lt;br /&gt;
* Christina Salazar (afternoon only)&lt;br /&gt;
* Sarah Dooley (afternoon)&lt;br /&gt;
* Josh Wilson, joshwilsonnc at gmail (likely afternoon only)&lt;br /&gt;
* Ken Varnum, varnum at umich e-d-u&lt;br /&gt;
* Cody Hennesy, chennesy at library berkeley edu&lt;br /&gt;
* Colin Koteles, koteles at cod dot edu&lt;br /&gt;
&lt;br /&gt;
==Half Day Morning==&lt;br /&gt;
=== Open space session ===&lt;br /&gt;
&lt;br /&gt;
* Dan Chudnov, dchud at gwu edu&lt;br /&gt;
&lt;br /&gt;
The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference.  Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it.  Use it as extra prep time for your upcoming prepared or lightning talk if you want.  We'll plan the morning out a little bit at the beginning, but not too much.  What we do will be up to the people there in the room.&lt;br /&gt;
&lt;br /&gt;
If there's interest, we could start with a &amp;quot;welcome to code4lib&amp;quot; introductory session for newcomers.&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* Devon Smith&lt;br /&gt;
* Esmé Cowles, escowles@ucsd.edu&lt;br /&gt;
* Jason Casden&lt;br /&gt;
* Ryan Eby&lt;br /&gt;
* mark matienzo&lt;br /&gt;
* Donald Mennerich&lt;br /&gt;
* Patrick Berry, pberry@csuchico.edu&lt;br /&gt;
* Kåre Fiedler Christiansen, kfc@statsbiblioteket.dk&lt;br /&gt;
* Michael Poltorak Nielsen mn at statsbiblioteket dot dk&lt;br /&gt;
* Joe Atzberger, ohiocore@gmail.com&lt;br /&gt;
* Shawn Carraway carraways at midlandstech dot edu&lt;br /&gt;
* Emily F. Shaw emily-f-shaw at uiowa dot edu&lt;br /&gt;
&lt;br /&gt;
=== Delivery services ===&lt;br /&gt;
* Ted Lawless, Brown University Library, tlawless at brown edu.  &lt;br /&gt;
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.&lt;br /&gt;
&lt;br /&gt;
Are you interested in making it easier for users to obtain copies of known items?  Do you feel your OpenURL and Interlibrary Loan software could be streamlined?  This pre-conference workshop will focus on providing services that deliver content to users.  Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.  &lt;br /&gt;
&lt;br /&gt;
Possible topics/activities include:&lt;br /&gt;
* group discussion of what some libraries have done in this area&lt;br /&gt;
* comparisons of different approaches to addressing delivery &lt;br /&gt;
* overview of tools available &lt;br /&gt;
* sharing of strategies and experiences&lt;br /&gt;
* time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/heroku-360link Py360 Link]. &lt;br /&gt;
 &lt;br /&gt;
Resources and background information:&lt;br /&gt;
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway] &lt;br /&gt;
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]&lt;br /&gt;
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]&lt;br /&gt;
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* Ken Varnum, varnum at umich e-d-u&lt;br /&gt;
* Curtis Thacker&lt;br /&gt;
* Rosalyn Metz rosalynmetz at gmail com&lt;br /&gt;
* James Van Mil - james.vanmil at gmail com&lt;br /&gt;
* Andrew Nagy&lt;br /&gt;
* Ranti Junus&lt;br /&gt;
* Aaron Collier - acollier at csufresno edu&lt;br /&gt;
* Demian Katz - demian dot katz at villanova dot edu&lt;br /&gt;
* Jacob Andresen - jacob at reindex dot dk&lt;br /&gt;
* Erin White - erwhite at vcu edu&lt;br /&gt;
* Zeno Tajoli tajoli at cilea it&lt;br /&gt;
* William Hicks - William{dot}hicks{at}unt{dot}edu&lt;br /&gt;
* Beatrice Pulliam bpulliam at providence edu&lt;br /&gt;
* David Bietila dbietila at uchicago edu&lt;br /&gt;
&lt;br /&gt;
=== Intro to Blacklight CANCELLED ===&lt;br /&gt;
&lt;br /&gt;
PLEASE NOTE: This pre-conference has been cancelled in favor of joining forces with the RailsBridge workshop. The afternoon Blacklight session will still be offered.&lt;br /&gt;
&lt;br /&gt;
=== RailsBridge Intro to Ruby on Rails ===&lt;br /&gt;
* Jason Ronallo, North Carolina State University Libraries, jronallo@gmail.com&lt;br /&gt;
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)&lt;br /&gt;
* Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu&lt;br /&gt;
* Ross Singer, Talis, rossfsinger@gmail.com&lt;br /&gt;
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org&lt;br /&gt;
* Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
* James Stuart &lt;br /&gt;
* Jason Stirnaman (helper), University of Kansas Medical Center, jstirnaman@kumc.edu &lt;br /&gt;
* Anyone else want to come and help folks? Contact Jason.&lt;br /&gt;
&lt;br /&gt;
RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language and the Rails framework. Participants will build a working Rails application. &lt;br /&gt;
&lt;br /&gt;
* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby&lt;br /&gt;
&lt;br /&gt;
Location: UIC Forum&lt;br /&gt;
&lt;br /&gt;
There is some pre-preconference preparation needed so that we can effectively use our time.&lt;br /&gt;
&lt;br /&gt;
'''IMPORTANT''': From this point on if you sign up you '''must''' do the following in order to be prepared for the preconference workshop:&lt;br /&gt;
# Add your name below&lt;br /&gt;
# fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dEpxd0tzU1ZscnU5QUUtd0JGUk9qQkE6MA#gid=0 experience survey]&lt;br /&gt;
# read [https://docs.google.com/document/d/1lQEvljB6MWOdxqcibYsQDVMT2hCevk7Y5cm3143_eaU/edit the emails you have missed] &lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
# First and last name and email address&lt;br /&gt;
# John MacGillivray&lt;br /&gt;
# Christina Salazar - christina{dot}salazar{at}csuci{dot}edu&lt;br /&gt;
# Karen Coombs - coombsk{at}oclc{dot}org&lt;br /&gt;
# Becky Yoose - b dot yoose at google overlord&lt;br /&gt;
# Jeremy Morse - jgmorse at umich&lt;br /&gt;
# Julia Bauder - julia{dot}bauder{at}gmail{dot}com &lt;br /&gt;
# Chung Kang&lt;br /&gt;
# Karen Miller - k-miller3{at}northwestern{dot}edu&lt;br /&gt;
# Betsy Coles - bcoles{at}caltech{dot}edu&lt;br /&gt;
# Jay Luker - jay{dot}luker{at}gmail{dot}com&lt;br /&gt;
# Santi Thompson&lt;br /&gt;
# Sarah Dooley - sarah{at}nclive{dot}org&lt;br /&gt;
# Brandon Dudley&lt;br /&gt;
# Ken Irwin&lt;br /&gt;
# Dennis Ogg - ogg{at}ucar{dot}edu&lt;br /&gt;
# Ian Walls - iwalls{at}library{dot}umass{dot}edu&lt;br /&gt;
# Steven Villereal – villereal{at}gmail{dot}com&lt;br /&gt;
# Hillel Arnold - hillel{dot}arnold{at}gmail{dot}com&lt;br /&gt;
# Josh Wilson - joshwilsonnc at gmail&lt;br /&gt;
# Cynthia Ng - cynthia [dot] s [dot] ng [at] gmail&lt;br /&gt;
# Ian Chan&lt;br /&gt;
# Heidi Frank - hf36{at}nyu{dot}edu&lt;br /&gt;
# Mark Mounts - mark{dot}mounts{at}dartmouth{dot}edu&lt;br /&gt;
# Bill McMillin - wmcmilli{at}pratt {dot}edu&lt;br /&gt;
# David Lacy - david dot lacy at villanova dot edu&lt;br /&gt;
# Courtney Greene - crgreene at indiana dot edu&lt;br /&gt;
# Laney McGlohon - lmcglohon@getty.edu&lt;br /&gt;
# Nancy Enneking - nenneking@getty.edu&lt;br /&gt;
# Jason Raitz - jcraitz at ncsu dot edu&lt;br /&gt;
# Nick Cappadona&lt;br /&gt;
# Steven Marsden - steven.marsden@ryerson.ca&lt;br /&gt;
# Linda Ballinger - ballingerl at newberry dot org&lt;br /&gt;
# Brendan Quinn - brendan-quinn at northwestern dot edu&lt;br /&gt;
# Michael Levy - mlevy {at}ushmm {dot}org&lt;br /&gt;
# Michael North   (m-north at northwestern dot edu)&lt;br /&gt;
# Shawn Averkamp - shawnaverkamp{at}gmail{dot}com&lt;br /&gt;
# Allan Berry - allan{dot}berry{at}gmail{dot}com&lt;br /&gt;
# Cody Hennesy - chennesy at library dot berkeley dot edu&lt;br /&gt;
# Devin Higgins - higgi135 at msu dot edu&lt;br /&gt;
# Emily Zervas - emily{dot}zervas{at}gmail{dot}com&lt;br /&gt;
# Rob Dumas - rdumas {at} chipublib {dot} org&lt;br /&gt;
# Evan Boyd - eboyd /at/ ctschicago /period/ edu&lt;br /&gt;
# Lauren Ajamie - lauren dot ajamie at nd dot edu&lt;br /&gt;
# David Anderson - david dot anderson3 at nih dot gov&lt;br /&gt;
# David Bucknum - dabu at loc dot gov&lt;br /&gt;
# Dave Menninger - dave.menninger at gmail dot com&lt;br /&gt;
# Chris Day - cday2 at saic dot edu&lt;br /&gt;
# Corey Harper - corey dot harper at nyu dot edu&lt;br /&gt;
# Dileshni Jayasinghe - d dot jayasinghe at utoronto dot ca&lt;br /&gt;
# Harish Nayak - hnayak at library dot rochester dot edu&lt;br /&gt;
# David Cliff dgcliff@iu.edu&lt;br /&gt;
# Cody Hanson codyhanson@umn.edu&lt;br /&gt;
# Laurie Lee Moses lmoses{at}colum{dot}edu&lt;br /&gt;
# Sibyl Schaefer sibylschaefer at gmail dot com&lt;br /&gt;
# Alisak Sanavongsay asanavongsay{at}ucmerced.edu&lt;br /&gt;
# Wayne Schneider wschneider at hclib dot org&lt;br /&gt;
# Carolyn Caizzi - carolyn{dot}caizzi {at}northwestern{dot}edu&lt;br /&gt;
# Julie Rudder - j-rudder at northwestern dot edu&lt;br /&gt;
# Matthew Butler - matthew-butler at uiowa dot edu&lt;br /&gt;
# Andromeda Yelton - andromeda.yelton at gmail&lt;br /&gt;
# Adam Strohm - adamstrohm at gmail dot com&lt;br /&gt;
# Kelly Thompson - thompson {dot} kelly {dot} j {at} gmail {dot} com&lt;br /&gt;
# Jane Sandberg - sandbrg2 {at} illinois {dot} edu&lt;br /&gt;
# Colin Koteles - koteles at cod dot edu&lt;br /&gt;
# George Campbell - campbelg{at}oclc{dot}org&lt;br /&gt;
 &lt;br /&gt;
'''IMPORTANT''': From this point on if you sign up you '''must''' do the following in order to be prepared for the preconference workshop:&lt;br /&gt;
# Add your name above&lt;br /&gt;
# fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dEpxd0tzU1ZscnU5QUUtd0JGUk9qQkE6MA#gid=0 experience survey]&lt;br /&gt;
# read [https://docs.google.com/document/d/1lQEvljB6MWOdxqcibYsQDVMT2hCevk7Y5cm3143_eaU/edit the emails you have missed]&lt;br /&gt;
&lt;br /&gt;
===Intro to NoSQL Databases===&lt;br /&gt;
* Joshua Gomez, George Washington University, jngomez at gwu edu&lt;br /&gt;
&lt;br /&gt;
Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called &amp;quot;Big Data&amp;quot; problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, MongoDB, and Neo4j.&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* Esha Datta&lt;br /&gt;
* Trevor Thornton&lt;br /&gt;
* Michael Doran&lt;br /&gt;
* Ray Schwartz - schwartzr2@wpunj.edu&lt;br /&gt;
* Kevin Clarke&lt;br /&gt;
* Andreas Orphanides&lt;br /&gt;
* Tommy Ingulfsen - tommying{at}caltech{dot}edu&lt;br /&gt;
* Harrison Dekker&lt;br /&gt;
* Eric James eric dot james at yale dot edu&lt;br /&gt;
* Sean Crowe - sean.crowe@uc.edu&lt;br /&gt;
* Scott Hanrath - shanrath@ku.edu&lt;br /&gt;
* Erin Fahy - erin.fahy at mtholyoke edu&lt;br /&gt;
* Karen Coyle - kcoyle at kcoyle.net&lt;br /&gt;
* Charles Draper&lt;br /&gt;
* David Uspal&lt;br /&gt;
* Shawn Kiewel - smkiewel at uga dot edu&lt;br /&gt;
* Stephanie Collett - stephanie dot collett at ucop dot edu&lt;br /&gt;
* Declan Fleming - declan at declan dot net&lt;br /&gt;
* David Gonzalez - d.gonzalez26 at umiami dot edu&lt;br /&gt;
* Jeff Peterson - gpeterso at umn dot edu&lt;br /&gt;
* May Chan - msuicat at gmail dot com&lt;br /&gt;
* Kathryn Stine - kathryn dot stine at ucop dot edu&lt;br /&gt;
* Tim Thompson - t.thompson5{at}miami{dot}edu&lt;br /&gt;
* Eben English - eenglish [at] bpl dot org&lt;br /&gt;
* Marisa Strong - marisa dot strong at ucop dot edu&lt;br /&gt;
* Michael Lindsey - mackeral at gmail dot com&lt;br /&gt;
* Mike Hagedon - hagedonm at u dot library dot arizona dot edu&lt;br /&gt;
* Scott Fisher - first/last name with dot in between at ucop dot edu&lt;br /&gt;
* James Griffin - griffinj at lafayette dot edu&lt;br /&gt;
* Jesse Brown - jfbrown78 at gmail dot com&lt;br /&gt;
* [[User:gdave|Dave Green]] david dot L dot green at dartmouth dot edu&lt;br /&gt;
* Michael Poltorak Nielsen mn at statsbiblioteket dot dk&lt;br /&gt;
* Mads Villadsen, mv@statsbiblioteket.dk&lt;br /&gt;
* Jørn Thøgersen, jt@statsbiblioteket.dk&lt;br /&gt;
* Julien Gibert, gibert at abes dot fr&lt;br /&gt;
* Lisa Gonzalez, lgonzalez@ctu.edu&lt;br /&gt;
* Charles Ledvina, charles@indexdata.com&lt;br /&gt;
* Jim LeFager, jlefager@depaul.edu&lt;br /&gt;
* Debbie Maron, dmaron@purdue.edu&lt;br /&gt;
* Carolina Garcia - cg116 nyu&lt;br /&gt;
* Tracy Seneca- tjseneca@uic.edu&lt;br /&gt;
* William Denton - wtd@pobox.com&lt;br /&gt;
* Andrew Darby - agdarby at miami dot edu&lt;br /&gt;
* Gary Maixner maixner2 at uiuc dot edu&lt;br /&gt;
* Jeremy Prevost&lt;br /&gt;
* Esther Verreau everreau skokielibrary info&lt;br /&gt;
* Matthew Short, mshort@niu.edu&lt;br /&gt;
* Kate Flynn, kef@uic.edu&lt;br /&gt;
* Jon Stroop - jstroop at princeton&lt;br /&gt;
* Mark Redar&lt;br /&gt;
&lt;br /&gt;
==Half Day Afternoon==&lt;br /&gt;
=== Data Visualization Hackfest ===&lt;br /&gt;
* Chris Beer, cabeer at stanford.edu&lt;br /&gt;
* Dan Chudnov, dchud at gwu edu&lt;br /&gt;
&lt;br /&gt;
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating?  Interested in data visualization?  Well, this hackfest is for you.  Not familiar with the concept of a hackfest?  See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html &amp;quot;Where Librarians Go To Hack&amp;quot;] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest].  We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly: &lt;br /&gt;
 - we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.&lt;br /&gt;
 - we'll separate into groups and hack on stuff.&lt;br /&gt;
 - at the end of the day, we'll present our progress.&lt;br /&gt;
&lt;br /&gt;
Not a code hacker?  No worries; all skill sets and backgrounds are valuable! &lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
# Devon Smith&lt;br /&gt;
# Esha Datta&lt;br /&gt;
# Ray Schwartz - schwartzr2@wpunj.edu&lt;br /&gt;
# Karen Coombs - coombsk{at}oclc{dot}org&lt;br /&gt;
# Julia Bauder - julia{dot}bauder{at}gmail{dot}com&lt;br /&gt;
# Jason Stirnaman (jstirnaman at kumc.edu)&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Ayla Stein (astein at uh.edu)&lt;br /&gt;
# Harrison Dekker&lt;br /&gt;
# Ian Walls - iwalls{at}library{dot}umass{dot}edu&lt;br /&gt;
# Scott Hanrath - shanrath@ku.edu&lt;br /&gt;
# Annie Pho&lt;br /&gt;
# [[User:Kevenj|Keven Jeffery]]&lt;br /&gt;
# James Van Mil - james.vanmil at gmail com&lt;br /&gt;
# Sean Crowe - sean.crowe@uc.edu&lt;br /&gt;
# Karen coyle - kcoyle at kcoyle.net&lt;br /&gt;
# David Lacy - david dot lacy at villanova dot edu&lt;br /&gt;
# mark matienzo&lt;br /&gt;
# David Uspal&lt;br /&gt;
# Emily Lynema - ejlynema at ncsu dot edu&lt;br /&gt;
# Sean Chen&lt;br /&gt;
# Donald Mennerich&lt;br /&gt;
# Allan Berry - allan{dot}berry{at}gmail{dot}com&lt;br /&gt;
# Declan Fleming - declan at declan dot net&lt;br /&gt;
# Chick Markley -- chick at qrhino dot com&lt;br /&gt;
# Rosalyn Metz -- rosalynmetz at gmail com&lt;br /&gt;
# Devin Higgins - higgi135 at msu dot edu&lt;br /&gt;
# Emily Zervas emily{dot}zervas{at}gmail{dot}com&lt;br /&gt;
# May Chan -- msuicat at gmail dot com&lt;br /&gt;
# Kathryn Stine - kathryn dot stine at ucop dot edu&lt;br /&gt;
# James Griffin - griffinj at lafayette dot edu&lt;br /&gt;
# Dave Menninger dave.menninger at gmail dot com&lt;br /&gt;
# [[User:gdave|Dave Green]] david dot L dot green at dartmouth dot edu&lt;br /&gt;
# Rikke Willer - riwi at dtic dot dtu dot dk&lt;br /&gt;
# Michael Poltorak NIelsen mn at statsbiblioteket dot dk&lt;br /&gt;
# Mads Villadsen, mv@statsbiblioteket.dk&lt;br /&gt;
# Jørn Thøgersen, jt@statsbiblioteket.dk&lt;br /&gt;
# Joe Atzberger, ohiocore@gmail.com&lt;br /&gt;
# Julien Gibert, gibert at abes dot fr&lt;br /&gt;
# Christie Peterson - cpeterson at jhu dot edu&lt;br /&gt;
# Jim LeFager - jlefager@depaul.edu&lt;br /&gt;
# Harish Nayak - hnayak at library dot rochester dot edu&lt;br /&gt;
# William Denton - wtd@pobox.com&lt;br /&gt;
# Shawn Carraway carraways at midlandstech dot edu&lt;br /&gt;
# Naomi Dushay - ndushay at stanford dot edu&lt;br /&gt;
# William Hicks - William{dot}hicks{at}unt{dot}edu&lt;br /&gt;
# Beatrice Pulliam bpulliam at providence edu&lt;br /&gt;
# Matthew Short, mshort@niu.edu&lt;br /&gt;
# George Campbell, campbelg{at}oclc{dot}org&lt;br /&gt;
&lt;br /&gt;
=== Intro to Hydra ===&lt;br /&gt;
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)&lt;br /&gt;
* Justin Coyne, Data Curation Experts (justin.coyne at curationexperts.com)&lt;br /&gt;
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)&lt;br /&gt;
&lt;br /&gt;
Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content.  Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame. &lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* Jeremy Prevost&lt;br /&gt;
* Dennis Ogg - ogg{at}ucar{dot}edu&lt;br /&gt;
* Terry Brady&lt;br /&gt;
* Betsy Coles - bcoles{at}caltech{dot}edu&lt;br /&gt;
* Brendan Quinn - brendan-quinn at northwestern dot edu&lt;br /&gt;
* Shawn Kiewel - smkiewel at uga dot edu&lt;br /&gt;
* Steven Villereal – villereal{at}gmail{dot}com&lt;br /&gt;
* Ryan Eby&lt;br /&gt;
* Dean Farrell&lt;br /&gt;
* Ian Chan&lt;br /&gt;
* Mark Mounts - mark{dot}mounts{at}dartmouth{dot}edu&lt;br /&gt;
* Carl Jones&lt;br /&gt;
* Laney McGlohon - lmcglohon@getty.edu&lt;br /&gt;
* Nancy Enneking - nenneking@getty.edu&lt;br /&gt;
* Allan Berry - allan{dot}berry{at}gmail{dot}com&lt;br /&gt;
* Andrew Darby - agdarby at miami dot edu&lt;br /&gt;
* Kåre Fiedler Christiansen - kfc@statsbiblioteket.dk&lt;br /&gt;
* Corey Harper - corey dot harper at nyu dot edu&lt;br /&gt;
* Gary Maixner - maixner2 at uiuc dot edu&lt;br /&gt;
* Sibyl Schaefer - sibylschaefer at gmail dot com&lt;br /&gt;
* Emily F. Shaw - emily-f-shaw{at}uiowa{dot}edu&lt;br /&gt;
* Alicia Morris - alicia.morris@tufts.edu&lt;br /&gt;
* Tim Thompson - t.thompson5{at}miami{dot}edu&lt;br /&gt;
* Kate Flynn, kef@uic.edu&lt;br /&gt;
&lt;br /&gt;
=== Intro to Blacklight ===&lt;br /&gt;
* Bess Sadler, Stanford University Library (bess at stanford.edu)&lt;br /&gt;
* Jason Ronallo, NC State (jronallo at gmail.com)&lt;br /&gt;
* Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)&lt;br /&gt;
&lt;br /&gt;
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&amp;amp;A around local issues people might encounter. &lt;br /&gt;
&lt;br /&gt;
Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* John MacGillivray&lt;br /&gt;
* Jon Stroop&lt;br /&gt;
* Jeremy Morse - jgmorse at umich&lt;br /&gt;
* Karen Miller - k-miller3{at}northwestern{dot}edu&lt;br /&gt;
* Tommy Ingulfsen - tommying{at}caltech{dot}edu&lt;br /&gt;
* Chung Kang&lt;br /&gt;
* Santi Thompson&lt;br /&gt;
* Brandon Dudley&lt;br /&gt;
* Ken Irwin&lt;br /&gt;
* Hillel Arnold&lt;br /&gt;
* Heidi Frank - hf36{at}nyu{dot}com&lt;br /&gt;
* Chris Sharp - csharp{at}georgialibraries{dot}org&lt;br /&gt;
* Bill McMillin - wmcmilli{at} pratt{dot} edu&lt;br /&gt;
* Jason Raitz - jcraitz at ncsu dot edu&lt;br /&gt;
* Linda Ballinger - ballingerl at newberry dot org&lt;br /&gt;
* Tim Thompson - t.thompson5{at}miami{dot}edu&lt;br /&gt;
* David Gonzalez - d.gonzalez26 at umiami dot edu&lt;br /&gt;
* Courtney Greene - crgreene at indiana dot edu&lt;br /&gt;
* Evan Boyd - eboyd /at/ ctschicago /period/ edu&lt;br /&gt;
* Lauren Ajamie - lauren dot ajamie at nd dot edu&lt;br /&gt;
* David Anderson - david dot anderson3 at nih dot gov&lt;br /&gt;
* Michael Lindsey - mackeral at gmail dot com&lt;br /&gt;
* David Bucknum - dabu at loc dot gov&lt;br /&gt;
* Scott Fisher - first/last name with dot in between at ucop dot edu&lt;br /&gt;
* Chris Day - cday2 at saic dot edu&lt;br /&gt;
* Carolina Garcia - cg116 nyu&lt;br /&gt;
* David Cliff dgcliff@iu.edu&lt;br /&gt;
* Cody Hanson codyhanson@umn.edu&lt;br /&gt;
* Laurie Lee Moses lmoses{at}colum{dot}edu&lt;br /&gt;
* Alisak Sanavongsay asanavongsay{at}ucmerced.edu&lt;br /&gt;
* Wayne Schneider wschneider at hclib dot org&lt;br /&gt;
* Carolyn Caizzi carolyn{dot}caizzi{at}northwestern{dot}edu&lt;br /&gt;
* Julie Rudder - j-rudder at northwestern dot edu&lt;br /&gt;
* Andromeda Yelton - andromeda.yelton at gmail&lt;br /&gt;
* Adam Strohm - adamstrohm at gmail dot com&lt;br /&gt;
* Luke Gaudreau - luke underscore gaudreau at harvard dot edu&lt;br /&gt;
&lt;br /&gt;
=== DPLA Intro/Hacking ===&lt;br /&gt;
 &lt;br /&gt;
* Presenter(s)/Leader(s): Nate Hill (Chattanooga Public Library, DPLA Audience and Participation Co-chair), SJ Klein (Wikimedia, OLPC, DPLA Technical Aspects Co-chair), Jeff Licht (DPLA Technical Development Project Manager)&lt;br /&gt;
&lt;br /&gt;
The [http://dp.la Digital Public Library of America] (DPLA) is an open source metadata repository that provides read-only access to millions of records from across the United States via an open REST API. All API queries are returned as JSON-LD, a lightweight linked data format, and the metadata is freely reusable under a CC0 public domain license. A front-end portal is currently under development and will be launched in April 2013, though it will serve as but one way into the DPLA’s data. The DPLA encourages the development of applications and tools by developers of all skill levels and backgrounds.  In this workshop, participants will actively code against the API to make apps, visualization tools, plug-ins, and other interesting tools that make use of DPLA data. &lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* First and last name, Affiliation&lt;br /&gt;
* Justin Clark, Berkman Center for Internet and Society&lt;br /&gt;
* Anita Patel, Berkman Center for Internet and Society&lt;br /&gt;
* Peter Murray, LYRASIS&lt;br /&gt;
&lt;br /&gt;
'''I plan on making:'''&lt;br /&gt;
* App name (your name): app description&lt;br /&gt;
&lt;br /&gt;
=== Fail4lib ===&lt;br /&gt;
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)&lt;br /&gt;
* Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)&lt;br /&gt;
&lt;br /&gt;
The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans (&amp;quot;The Pivot&amp;quot;), and failing more cheaply.&lt;br /&gt;
&lt;br /&gt;
Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:&lt;br /&gt;
&lt;br /&gt;
# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.&lt;br /&gt;
# Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:&lt;br /&gt;
#* Technical failure&lt;br /&gt;
#* Failure to effectively address a real user need&lt;br /&gt;
#* Overinvestment&lt;br /&gt;
#* Outreach/Promotion failure&lt;br /&gt;
#* Design/UX failure&lt;br /&gt;
#* Project team communication failure&lt;br /&gt;
#* Missed opportunities (risk-averse failure)&lt;br /&gt;
#* Successes gleaned from failures&lt;br /&gt;
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.&lt;br /&gt;
# A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.&lt;br /&gt;
&lt;br /&gt;
I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* Becky Yoose&lt;br /&gt;
* Lisa Rabey&lt;br /&gt;
* Cynthia Ng (maybe) - cynthia [dot] s [dot] ng [at] gmail&lt;br /&gt;
* Patrick Berry, pberry@csuchico.edu&lt;br /&gt;
* Erin White, erwhite at vcu edu&lt;br /&gt;
* Ranti Junus, ranti.junus at gmail&lt;br /&gt;
&lt;br /&gt;
=== Solr 4 In Depth ===&lt;br /&gt;
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)&lt;br /&gt;
&lt;br /&gt;
The long awaited and much anticipated Solr 4 has been released!   It's a really big deal.  There are so many improvements, it makes the head spin.  This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format. Sounds like this is an evening thing that might happen at a bar somewhere?&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* First and last name&lt;br /&gt;
* Erin Fahy - erin.fahy at mtholyoke edu&lt;br /&gt;
* Esmé Cowles, escowles@ucsd.edu&lt;br /&gt;
* Jon Stroop&lt;br /&gt;
* Adam Constabars&lt;br /&gt;
* Kevin Clarke&lt;br /&gt;
* Jacob Andresen (jacob at reindex dot dk)&lt;br /&gt;
* Ted Lawless (tlawless at brown dot edu)&lt;br /&gt;
* Tom Burton-West&lt;br /&gt;
* Curtis Thacker&lt;br /&gt;
* Eric James eric dot james at yale dot edu&lt;br /&gt;
* Bess Sadler (bess at stanford dot edu)&lt;br /&gt;
* Michael North&lt;br /&gt;
* Charles Draper&lt;br /&gt;
* Nick Cappadona&lt;br /&gt;
* Stephanie Collett - stephanie dot collett at ucop dot edu&lt;br /&gt;
* Kalee Sprague - kalee dot sprague at yale dot edu&lt;br /&gt;
* Jeff Peterson - gpeterso at umn dot edu&lt;br /&gt;
* Erik Hetzner&lt;br /&gt;
* Demian Katz - demian dot katz at villanova dot edu&lt;br /&gt;
* Eben English - eenglish at bpl dot org&lt;br /&gt;
* Raman Chandrasekar &lt;br /&gt;
* Jason Ronallo - jnronall@ncsu.edu&lt;br /&gt;
* Eric Larson - elarson@library.wisc.edu&lt;br /&gt;
* Mike Hagedon - hagedonm at u dot library dot arizona dot edu&lt;br /&gt;
* Jesse Brown - jfbrown78 at gmail dot com&lt;br /&gt;
* Steven Marsden - steven.marsden@ryerson.ca&lt;br /&gt;
* Zeno Tajoli - tajoli at cilea it&lt;br /&gt;
* Charles Ledvina - charles att indexdata dott com&lt;br /&gt;
* Tracy Seneca - tjseneca@uic.edu&lt;br /&gt;
* Tod Olson - tod at uchicago dot edu&lt;br /&gt;
* Esther Verreau - everreau skokielibrary info&lt;br /&gt;
* Jane Sandberg - sandbrg2 at illinois dot edu&lt;br /&gt;
* Mark Redar&lt;br /&gt;
[[Category:Code4Lib2013]]&lt;/div&gt;</summary>
		<author><name>Rshanrath</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_preconference_proposals&amp;diff=35781</id>
		<title>2013 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_preconference_proposals&amp;diff=35781"/>
				<updated>2013-02-05T16:20:13Z</updated>
		
		<summary type="html">&lt;p&gt;Rshanrath: /* Intro to NoSQL Databases */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Please sign up to attend by January 15th. Doesn't mean you can't change your mind, but we will use the host committee will use these numbers to assign rooms.&lt;br /&gt;
&lt;br /&gt;
Proposals '''now closed'''.&lt;br /&gt;
&lt;br /&gt;
Spaces available: 4+ Rooms&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
=== Talk Title ===&lt;br /&gt;
 &lt;br /&gt;
* Presenter/Leader, affiliation (optional), and email address (mandatory!)&lt;br /&gt;
* Second Presenter/Leader, affiliation, email address, if applicable&lt;br /&gt;
&lt;br /&gt;
Description.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Full Day==&lt;br /&gt;
&lt;br /&gt;
===Drupal4lib Sub-con Barcamp===&lt;br /&gt;
&lt;br /&gt;
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or &lt;br /&gt;
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.&lt;br /&gt;
&lt;br /&gt;
If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.&lt;br /&gt;
&lt;br /&gt;
This event is open to the library community. There is a nominal fee ($10) for non-Code4LibCon attendees.&lt;br /&gt;
&lt;br /&gt;
Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.&lt;br /&gt;
&lt;br /&gt;
====I plan on attending:====&lt;br /&gt;
&lt;br /&gt;
=====All Day=====&lt;br /&gt;
*Margaret Heller&lt;br /&gt;
*Mahria Lebow, mahria at uw edu&lt;br /&gt;
*Paula Gray-Overtoom, pgrayove at gmail.com&lt;br /&gt;
*Dhanushka Samarakoon, dhanu80 at g mail com&lt;br /&gt;
*Leo Robert Klein &amp;lt;del&amp;gt;(when he figures out what date this is)&amp;lt;/del&amp;gt; - 2/11 (9a-5p).  P.S. Oh Great One!  Who do we hand the 10 bucks to?&lt;br /&gt;
*Sarah Shealy, sarah.shealy at gmail.com&lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
* [[User:Kevenj|Keven Jeffery]]&lt;br /&gt;
* Sean Chen&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)&lt;br /&gt;
* Christina Salazar (afternoon only)&lt;br /&gt;
* Sarah Dooley (afternoon)&lt;br /&gt;
* Josh Wilson, joshwilsonnc at gmail (likely afternoon only)&lt;br /&gt;
* Ken Varnum, varnum at umich e-d-u&lt;br /&gt;
* Cody Hennesy, chennesy at library berkeley edu&lt;br /&gt;
* Colin Koteles, koteles at cod dot edu&lt;br /&gt;
&lt;br /&gt;
==Half Day Morning==&lt;br /&gt;
=== Open space session ===&lt;br /&gt;
&lt;br /&gt;
* Dan Chudnov, dchud at gwu edu&lt;br /&gt;
&lt;br /&gt;
The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference.  Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it.  Use it as extra prep time for your upcoming prepared or lightning talk if you want.  We'll plan the morning out a little bit at the beginning, but not too much.  What we do will be up to the people there in the room.&lt;br /&gt;
&lt;br /&gt;
If there's interest, we could start with a &amp;quot;welcome to code4lib&amp;quot; introductory session for newcomers.&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* Devon Smith&lt;br /&gt;
* Esmé Cowles, escowles@ucsd.edu&lt;br /&gt;
* Jason Casden&lt;br /&gt;
* Ryan Eby&lt;br /&gt;
* mark matienzo&lt;br /&gt;
* Donald Mennerich&lt;br /&gt;
* Patrick Berry, pberry@csuchico.edu&lt;br /&gt;
* Kåre Fiedler Christiansen, kfc@statsbiblioteket.dk&lt;br /&gt;
* Michael Poltorak Nielsen mn at statsbiblioteket dot dk&lt;br /&gt;
* Joe Atzberger, ohiocore@gmail.com&lt;br /&gt;
* Shawn Carraway carraways at midlandstech dot edu&lt;br /&gt;
* Emily F. Shaw emily-f-shaw at uiowa dot edu&lt;br /&gt;
&lt;br /&gt;
=== Delivery services ===&lt;br /&gt;
* Ted Lawless, Brown University Library, tlawless at brown edu.  &lt;br /&gt;
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.&lt;br /&gt;
&lt;br /&gt;
Are you interested in making it easier for users to obtain copies of known items?  Do you feel your OpenURL and Interlibrary Loan software could be streamlined?  This pre-conference workshop will focus on providing services that deliver content to users.  Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.  &lt;br /&gt;
&lt;br /&gt;
Possible topics/activities include:&lt;br /&gt;
* group discussion of what some libraries have done in this area&lt;br /&gt;
* comparisons of different approaches to addressing delivery &lt;br /&gt;
* overview of tools available &lt;br /&gt;
* sharing of strategies and experiences&lt;br /&gt;
* time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/heroku-360link Py360 Link]. &lt;br /&gt;
 &lt;br /&gt;
Resources and background information:&lt;br /&gt;
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway] &lt;br /&gt;
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]&lt;br /&gt;
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]&lt;br /&gt;
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* Ken Varnum, varnum at umich e-d-u&lt;br /&gt;
* Curtis Thacker&lt;br /&gt;
* Rosalyn Metz rosalynmetz at gmail com&lt;br /&gt;
* James Van Mil - james.vanmil at gmail com&lt;br /&gt;
* Andrew Nagy&lt;br /&gt;
* Ranti Junus&lt;br /&gt;
* Aaron Collier - acollier at csufresno edu&lt;br /&gt;
* Demian Katz - demian dot katz at villanova dot edu&lt;br /&gt;
* Jacob Andresen - jacob at reindex dot dk&lt;br /&gt;
* Erin White - erwhite at vcu edu&lt;br /&gt;
* Zeno Tajoli tajoli at cilea it&lt;br /&gt;
* William Hicks - William{dot}hicks{at}unt{dot}edu&lt;br /&gt;
* Beatrice Pulliam bpulliam at providence edu&lt;br /&gt;
* David Bietila dbietila at uchicago edu&lt;br /&gt;
&lt;br /&gt;
=== Intro to Blacklight CANCELLED ===&lt;br /&gt;
&lt;br /&gt;
PLEASE NOTE: This pre-conference has been cancelled in favor of joining forces with the RailsBridge workshop. The afternoon Blacklight session will still be offered.&lt;br /&gt;
&lt;br /&gt;
=== RailsBridge Intro to Ruby on Rails ===&lt;br /&gt;
* Jason Ronallo, North Carolina State University Libraries, jronallo@gmail.com&lt;br /&gt;
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)&lt;br /&gt;
* Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu&lt;br /&gt;
* Ross Singer, Talis, rossfsinger@gmail.com&lt;br /&gt;
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org&lt;br /&gt;
* Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
* James Stuart &lt;br /&gt;
* Jason Stirnaman (helper), University of Kansas Medical Center, jstirnaman@kumc.edu &lt;br /&gt;
* Anyone else want to come and help folks? Contact Jason.&lt;br /&gt;
&lt;br /&gt;
RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language and the Rails framework. Participants will build a working Rails application. &lt;br /&gt;
&lt;br /&gt;
* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby&lt;br /&gt;
&lt;br /&gt;
Location: UIC Forum&lt;br /&gt;
&lt;br /&gt;
There is some pre-preconference preparation needed so that we can effectively use our time.&lt;br /&gt;
&lt;br /&gt;
'''IMPORTANT''': From this point on if you sign up you '''must''' do the following in order to be prepared for the preconference workshop:&lt;br /&gt;
# Add your name below&lt;br /&gt;
# fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dEpxd0tzU1ZscnU5QUUtd0JGUk9qQkE6MA#gid=0 experience survey]&lt;br /&gt;
# read [https://docs.google.com/document/d/1lQEvljB6MWOdxqcibYsQDVMT2hCevk7Y5cm3143_eaU/edit the emails you have missed] &lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
# First and last name and email address&lt;br /&gt;
# John MacGillivray&lt;br /&gt;
# Christina Salazar - christina{dot}salazar{at}csuci{dot}edu&lt;br /&gt;
# Karen Coombs - coombsk{at}oclc{dot}org&lt;br /&gt;
# Becky Yoose - b dot yoose at google overlord&lt;br /&gt;
# Jeremy Morse - jgmorse at umich&lt;br /&gt;
# Julia Bauder - julia{dot}bauder{at}gmail{dot}com &lt;br /&gt;
# Chung Kang&lt;br /&gt;
# Karen Miller - k-miller3{at}northwestern{dot}edu&lt;br /&gt;
# Betsy Coles - bcoles{at}caltech{dot}edu&lt;br /&gt;
# Jay Luker - jay{dot}luker{at}gmail{dot}com&lt;br /&gt;
# Santi Thompson&lt;br /&gt;
# Sarah Dooley - sarah{at}nclive{dot}org&lt;br /&gt;
# Brandon Dudley&lt;br /&gt;
# Ken Irwin&lt;br /&gt;
# Dennis Ogg - ogg{at}ucar{dot}edu&lt;br /&gt;
# Ian Walls - iwalls{at}library{dot}umass{dot}edu&lt;br /&gt;
# Steven Villereal – villereal{at}gmail{dot}com&lt;br /&gt;
# Hillel Arnold - hillel{dot}arnold{at}gmail{dot}com&lt;br /&gt;
# Josh Wilson - joshwilsonnc at gmail&lt;br /&gt;
# Cynthia Ng - cynthia [dot] s [dot] ng [at] gmail&lt;br /&gt;
# Ian Chan&lt;br /&gt;
# Heidi Frank - hf36{at}nyu{dot}edu&lt;br /&gt;
# Mark Mounts - mark{dot}mounts{at}dartmouth{dot}edu&lt;br /&gt;
# Bill McMillin - wmcmilli{at}pratt {dot}edu&lt;br /&gt;
# David Lacy - david dot lacy at villanova dot edu&lt;br /&gt;
# Courtney Greene - crgreene at indiana dot edu&lt;br /&gt;
# Laney McGlohon - lmcglohon@getty.edu&lt;br /&gt;
# Nancy Enneking - nenneking@getty.edu&lt;br /&gt;
# Jason Raitz - jcraitz at ncsu dot edu&lt;br /&gt;
# Nick Cappadona&lt;br /&gt;
# Steven Marsden - steven.marsden@ryerson.ca&lt;br /&gt;
# Linda Ballinger - ballingerl at newberry dot org&lt;br /&gt;
# Brendan Quinn - brendan-quinn at northwestern dot edu&lt;br /&gt;
# Michael Levy - mlevy {at}ushmm {dot}org&lt;br /&gt;
# Michael North   (m-north at northwestern dot edu)&lt;br /&gt;
# Shawn Averkamp - shawnaverkamp{at}gmail{dot}com&lt;br /&gt;
# Allan Berry - allan{dot}berry{at}gmail{dot}com&lt;br /&gt;
# Cody Hennesy - chennesy at library dot berkeley dot edu&lt;br /&gt;
# Devin Higgins - higgi135 at msu dot edu&lt;br /&gt;
# Emily Zervas - emily{dot}zervas{at}gmail{dot}com&lt;br /&gt;
# Rob Dumas - rdumas {at} chipublib {dot} org&lt;br /&gt;
# Evan Boyd - eboyd /at/ ctschicago /period/ edu&lt;br /&gt;
# Lauren Ajamie - lauren dot ajamie at nd dot edu&lt;br /&gt;
# David Anderson - david dot anderson3 at nih dot gov&lt;br /&gt;
# David Bucknum - dabu at loc dot gov&lt;br /&gt;
# Dave Menninger - dave.menninger at gmail dot com&lt;br /&gt;
# Chris Day - cday2 at saic dot edu&lt;br /&gt;
# Corey Harper - corey dot harper at nyu dot edu&lt;br /&gt;
# Dileshni Jayasinghe - d dot jayasinghe at utoronto dot ca&lt;br /&gt;
# Harish Nayak - hnayak at library dot rochester dot edu&lt;br /&gt;
# David Cliff dgcliff@iu.edu&lt;br /&gt;
# Cody Hanson codyhanson@umn.edu&lt;br /&gt;
# Laurie Lee Moses lmoses{at}colum{dot}edu&lt;br /&gt;
# Sibyl Schaefer sibylschaefer at gmail dot com&lt;br /&gt;
# Alisak Sanavongsay asanavongsay{at}ucmerced.edu&lt;br /&gt;
# Wayne Schneider wschneider at hclib dot org&lt;br /&gt;
# Carolyn Caizzi - carolyn{dot}caizzi {at}northwestern{dot}edu&lt;br /&gt;
# Julie Rudder - j-rudder at northwestern dot edu&lt;br /&gt;
# Matthew Butler - matthew-butler at uiowa dot edu&lt;br /&gt;
# Andromeda Yelton - andromeda.yelton at gmail&lt;br /&gt;
# Adam Strohm - adamstrohm at gmail dot com&lt;br /&gt;
# Kelly Thompson - thompson {dot} kelly {dot} j {at} gmail {dot} com&lt;br /&gt;
# Jane Sandberg - sandbrg2 {at} illinois {dot} edu&lt;br /&gt;
# Colin Koteles - koteles at cod dot edu&lt;br /&gt;
# George Campbell - campbelg{at}oclc{dot}org&lt;br /&gt;
 &lt;br /&gt;
'''IMPORTANT''': From this point on if you sign up you '''must''' do the following in order to be prepared for the preconference workshop:&lt;br /&gt;
# Add your name above&lt;br /&gt;
# fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dEpxd0tzU1ZscnU5QUUtd0JGUk9qQkE6MA#gid=0 experience survey]&lt;br /&gt;
# read [https://docs.google.com/document/d/1lQEvljB6MWOdxqcibYsQDVMT2hCevk7Y5cm3143_eaU/edit the emails you have missed]&lt;br /&gt;
&lt;br /&gt;
===Intro to NoSQL Databases===&lt;br /&gt;
* Joshua Gomez, George Washington University, jngomez at gwu edu&lt;br /&gt;
&lt;br /&gt;
Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called &amp;quot;Big Data&amp;quot; problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, MongoDB, and Neo4j.&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* Esha Datta&lt;br /&gt;
* Trevor Thornton&lt;br /&gt;
* Michael Doran&lt;br /&gt;
* Ray Schwartz - schwartzr2@wpunj.edu&lt;br /&gt;
* Kevin Clarke&lt;br /&gt;
* Andreas Orphanides&lt;br /&gt;
* Tommy Ingulfsen - tommying{at}caltech{dot}edu&lt;br /&gt;
* Harrison Dekker&lt;br /&gt;
* Eric James eric dot james at yale dot edu&lt;br /&gt;
* Sean Crowe - sean.crowe@uc.edu&lt;br /&gt;
* Scott Hanrath - shanrath@ku.edu&lt;br /&gt;
* Erin Fahy - erin.fahy at mtholyoke edu&lt;br /&gt;
* Karen Coyle - kcoyle at kcoyle.net&lt;br /&gt;
* Charles Draper&lt;br /&gt;
* David Uspal&lt;br /&gt;
* Shawn Kiewel - smkiewel at uga dot edu&lt;br /&gt;
* Stephanie Collett - stephanie dot collett at ucop dot edu&lt;br /&gt;
* Declan Fleming - declan at declan dot net&lt;br /&gt;
* David Gonzalez - d.gonzalez26 at umiami dot edu&lt;br /&gt;
* Jeff Peterson - gpeterso at umn dot edu&lt;br /&gt;
* May Chan - msuicat at gmail dot com&lt;br /&gt;
* Kathryn Stine - kathryn dot stine at ucop dot edu&lt;br /&gt;
* Tim Thompson - t.thompson5{at}miami{dot}edu&lt;br /&gt;
* Eben English - eenglish [at] bpl dot org&lt;br /&gt;
* Marisa Strong - marisa dot strong at ucop dot edu&lt;br /&gt;
* Michael Lindsey - mackeral at gmail dot com&lt;br /&gt;
* Mike Hagedon - hagedonm at u dot library dot arizona dot edu&lt;br /&gt;
* Scott Fisher - first/last name with dot in between at ucop dot edu&lt;br /&gt;
* James Griffin - griffinj at lafayette dot edu&lt;br /&gt;
* Jesse Brown - jfbrown78 at gmail dot com&lt;br /&gt;
* [[User:gdave|Dave Green]] david dot L dot green at dartmouth dot edu&lt;br /&gt;
* Michael Poltorak Nielsen mn at statsbiblioteket dot dk&lt;br /&gt;
* Mads Villadsen, mv@statsbiblioteket.dk&lt;br /&gt;
* Jørn Thøgersen, jt@statsbiblioteket.dk&lt;br /&gt;
* Julien Gibert, gibert at abes dot fr&lt;br /&gt;
* Lisa Gonzalez, lgonzalez@ctu.edu&lt;br /&gt;
* Charles Ledvina, charles@indexdata.com&lt;br /&gt;
* Jim LeFager, jlefager@depaul.edu&lt;br /&gt;
* Debbie Maron, dmaron@purdue.edu&lt;br /&gt;
* Carolina Garcia - cg116 nyu&lt;br /&gt;
* Tracy Seneca- tjseneca@uic.edu&lt;br /&gt;
* William Denton - wtd@pobox.com&lt;br /&gt;
* Andrew Darby - agdarby at miami dot edu&lt;br /&gt;
* Gary Maixner maixner2 at uiuc dot edu&lt;br /&gt;
* Jeremy Prevost&lt;br /&gt;
* Esther Verreau everreau skokielibrary info&lt;br /&gt;
* Matthew Short, mshort@niu.edu&lt;br /&gt;
* Kate Flynn, kef@uic.edu&lt;br /&gt;
* Jon Stroop - jstroop at princeton&lt;br /&gt;
* Mark Redar&lt;br /&gt;
&lt;br /&gt;
==Half Day Afternoon==&lt;br /&gt;
=== Data Visualization Hackfest ===&lt;br /&gt;
* Chris Beer, cabeer at stanford.edu&lt;br /&gt;
* Dan Chudnov, dchud at gwu edu&lt;br /&gt;
&lt;br /&gt;
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating?  Interested in data visualization?  Well, this hackfest is for you.  Not familiar with the concept of a hackfest?  See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html &amp;quot;Where Librarians Go To Hack&amp;quot;] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest].  We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly: &lt;br /&gt;
 - we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.&lt;br /&gt;
 - we'll separate into groups and hack on stuff.&lt;br /&gt;
 - at the end of the day, we'll present our progress.&lt;br /&gt;
&lt;br /&gt;
Not a code hacker?  No worries; all skill sets and backgrounds are valuable! &lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
# Devon Smith&lt;br /&gt;
# Esha Datta&lt;br /&gt;
# Ray Schwartz - schwartzr2@wpunj.edu&lt;br /&gt;
# Karen Coombs - coombsk{at}oclc{dot}org&lt;br /&gt;
# Julia Bauder - julia{dot}bauder{at}gmail{dot}com&lt;br /&gt;
# Jason Stirnaman (jstirnaman at kumc.edu)&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Ayla Stein (astein at uh.edu)&lt;br /&gt;
# Harrison Dekker&lt;br /&gt;
# Ian Walls - iwalls{at}library{dot}umass{dot}edu&lt;br /&gt;
# Scott Hanrath&lt;br /&gt;
# Annie Pho&lt;br /&gt;
# [[User:Kevenj|Keven Jeffery]]&lt;br /&gt;
# James Van Mil - james.vanmil at gmail com&lt;br /&gt;
# Sean Crowe - sean.crowe@uc.edu&lt;br /&gt;
# Karen coyle - kcoyle at kcoyle.net&lt;br /&gt;
# David Lacy - david dot lacy at villanova dot edu&lt;br /&gt;
# mark matienzo&lt;br /&gt;
# David Uspal&lt;br /&gt;
# Emily Lynema - ejlynema at ncsu dot edu&lt;br /&gt;
# Sean Chen&lt;br /&gt;
# Donald Mennerich&lt;br /&gt;
# Allan Berry - allan{dot}berry{at}gmail{dot}com&lt;br /&gt;
# Declan Fleming - declan at declan dot net&lt;br /&gt;
# Chick Markley -- chick at qrhino dot com&lt;br /&gt;
# Rosalyn Metz -- rosalynmetz at gmail com&lt;br /&gt;
# Devin Higgins - higgi135 at msu dot edu&lt;br /&gt;
# Emily Zervas emily{dot}zervas{at}gmail{dot}com&lt;br /&gt;
# May Chan -- msuicat at gmail dot com&lt;br /&gt;
# Kathryn Stine - kathryn dot stine at ucop dot edu&lt;br /&gt;
# James Griffin - griffinj at lafayette dot edu&lt;br /&gt;
# Dave Menninger dave.menninger at gmail dot com&lt;br /&gt;
# [[User:gdave|Dave Green]] david dot L dot green at dartmouth dot edu&lt;br /&gt;
# Rikke Willer - riwi at dtic dot dtu dot dk&lt;br /&gt;
# Michael Poltorak NIelsen mn at statsbiblioteket dot dk&lt;br /&gt;
# Mads Villadsen, mv@statsbiblioteket.dk&lt;br /&gt;
# Jørn Thøgersen, jt@statsbiblioteket.dk&lt;br /&gt;
# Joe Atzberger, ohiocore@gmail.com&lt;br /&gt;
# Julien Gibert, gibert at abes dot fr&lt;br /&gt;
# Christie Peterson - cpeterson at jhu dot edu&lt;br /&gt;
# Jim LeFager - jlefager@depaul.edu&lt;br /&gt;
# Harish Nayak - hnayak at library dot rochester dot edu&lt;br /&gt;
# William Denton - wtd@pobox.com&lt;br /&gt;
# Shawn Carraway carraways at midlandstech dot edu&lt;br /&gt;
# Naomi Dushay - ndushay at stanford dot edu&lt;br /&gt;
# William Hicks - William{dot}hicks{at}unt{dot}edu&lt;br /&gt;
# Beatrice Pulliam bpulliam at providence edu&lt;br /&gt;
# Matthew Short, mshort@niu.edu&lt;br /&gt;
# George Campbell, campbelg{at}oclc{dot}org&lt;br /&gt;
&lt;br /&gt;
=== Intro to Hydra ===&lt;br /&gt;
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)&lt;br /&gt;
* Justin Coyne, Data Curation Experts (justin.coyne at curationexperts.com)&lt;br /&gt;
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)&lt;br /&gt;
&lt;br /&gt;
Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content.  Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame. &lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* Jeremy Prevost&lt;br /&gt;
* Dennis Ogg - ogg{at}ucar{dot}edu&lt;br /&gt;
* Terry Brady&lt;br /&gt;
* Betsy Coles - bcoles{at}caltech{dot}edu&lt;br /&gt;
* Brendan Quinn - brendan-quinn at northwestern dot edu&lt;br /&gt;
* Shawn Kiewel - smkiewel at uga dot edu&lt;br /&gt;
* Steven Villereal – villereal{at}gmail{dot}com&lt;br /&gt;
* Ryan Eby&lt;br /&gt;
* Dean Farrell&lt;br /&gt;
* Ian Chan&lt;br /&gt;
* Mark Mounts - mark{dot}mounts{at}dartmouth{dot}edu&lt;br /&gt;
* Carl Jones&lt;br /&gt;
* Laney McGlohon - lmcglohon@getty.edu&lt;br /&gt;
* Nancy Enneking - nenneking@getty.edu&lt;br /&gt;
* Allan Berry - allan{dot}berry{at}gmail{dot}com&lt;br /&gt;
* Andrew Darby - agdarby at miami dot edu&lt;br /&gt;
* Kåre Fiedler Christiansen - kfc@statsbiblioteket.dk&lt;br /&gt;
* Corey Harper - corey dot harper at nyu dot edu&lt;br /&gt;
* Gary Maixner - maixner2 at uiuc dot edu&lt;br /&gt;
* Sibyl Schaefer - sibylschaefer at gmail dot com&lt;br /&gt;
* Emily F. Shaw - emily-f-shaw{at}uiowa{dot}edu&lt;br /&gt;
* Alicia Morris - alicia.morris@tufts.edu&lt;br /&gt;
* Tim Thompson - t.thompson5{at}miami{dot}edu&lt;br /&gt;
* Kate Flynn, kef@uic.edu&lt;br /&gt;
&lt;br /&gt;
=== Intro to Blacklight ===&lt;br /&gt;
* Bess Sadler, Stanford University Library (bess at stanford.edu)&lt;br /&gt;
* Jason Ronallo, NC State (jronallo at gmail.com)&lt;br /&gt;
* Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)&lt;br /&gt;
&lt;br /&gt;
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&amp;amp;A around local issues people might encounter. &lt;br /&gt;
&lt;br /&gt;
Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* John MacGillivray&lt;br /&gt;
* Jon Stroop&lt;br /&gt;
* Jeremy Morse - jgmorse at umich&lt;br /&gt;
* Karen Miller - k-miller3{at}northwestern{dot}edu&lt;br /&gt;
* Tommy Ingulfsen - tommying{at}caltech{dot}edu&lt;br /&gt;
* Chung Kang&lt;br /&gt;
* Santi Thompson&lt;br /&gt;
* Brandon Dudley&lt;br /&gt;
* Ken Irwin&lt;br /&gt;
* Hillel Arnold&lt;br /&gt;
* Heidi Frank - hf36{at}nyu{dot}com&lt;br /&gt;
* Chris Sharp - csharp{at}georgialibraries{dot}org&lt;br /&gt;
* Bill McMillin - wmcmilli{at} pratt{dot} edu&lt;br /&gt;
* Jason Raitz - jcraitz at ncsu dot edu&lt;br /&gt;
* Linda Ballinger - ballingerl at newberry dot org&lt;br /&gt;
* Tim Thompson - t.thompson5{at}miami{dot}edu&lt;br /&gt;
* David Gonzalez - d.gonzalez26 at umiami dot edu&lt;br /&gt;
* Courtney Greene - crgreene at indiana dot edu&lt;br /&gt;
* Evan Boyd - eboyd /at/ ctschicago /period/ edu&lt;br /&gt;
* Lauren Ajamie - lauren dot ajamie at nd dot edu&lt;br /&gt;
* David Anderson - david dot anderson3 at nih dot gov&lt;br /&gt;
* Michael Lindsey - mackeral at gmail dot com&lt;br /&gt;
* David Bucknum - dabu at loc dot gov&lt;br /&gt;
* Scott Fisher - first/last name with dot in between at ucop dot edu&lt;br /&gt;
* Chris Day - cday2 at saic dot edu&lt;br /&gt;
* Carolina Garcia - cg116 nyu&lt;br /&gt;
* David Cliff dgcliff@iu.edu&lt;br /&gt;
* Cody Hanson codyhanson@umn.edu&lt;br /&gt;
* Laurie Lee Moses lmoses{at}colum{dot}edu&lt;br /&gt;
* Alisak Sanavongsay asanavongsay{at}ucmerced.edu&lt;br /&gt;
* Wayne Schneider wschneider at hclib dot org&lt;br /&gt;
* Carolyn Caizzi carolyn{dot}caizzi{at}northwestern{dot}edu&lt;br /&gt;
* Julie Rudder - j-rudder at northwestern dot edu&lt;br /&gt;
* Andromeda Yelton - andromeda.yelton at gmail&lt;br /&gt;
* Adam Strohm - adamstrohm at gmail dot com&lt;br /&gt;
* Luke Gaudreau - luke underscore gaudreau at harvard dot edu&lt;br /&gt;
&lt;br /&gt;
=== DPLA Intro/Hacking ===&lt;br /&gt;
 &lt;br /&gt;
* Presenter(s)/Leader(s): Nate Hill (Chattanooga Public Library, DPLA Audience and Participation Co-chair), SJ Klein (Wikimedia, OLPC, DPLA Technical Aspects Co-chair), Jeff Licht (DPLA Technical Development Project Manager)&lt;br /&gt;
&lt;br /&gt;
The [http://dp.la Digital Public Library of America] (DPLA) is an open source metadata repository that provides read-only access to millions of records from across the United States via an open REST API. All API queries are returned as JSON-LD, a lightweight linked data format, and the metadata is freely reusable under a CC0 public domain license. A front-end portal is currently under development and will be launched in April 2013, though it will serve as but one way into the DPLA’s data. The DPLA encourages the development of applications and tools by developers of all skill levels and backgrounds.  In this workshop, participants will actively code against the API to make apps, visualization tools, plug-ins, and other interesting tools that make use of DPLA data. &lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* First and last name, Affiliation&lt;br /&gt;
* Justin Clark, Berkman Center for Internet and Society&lt;br /&gt;
* Anita Patel, Berkman Center for Internet and Society&lt;br /&gt;
* Peter Murray, LYRASIS&lt;br /&gt;
&lt;br /&gt;
'''I plan on making:'''&lt;br /&gt;
* App name (your name): app description&lt;br /&gt;
&lt;br /&gt;
=== Fail4lib ===&lt;br /&gt;
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)&lt;br /&gt;
* Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)&lt;br /&gt;
&lt;br /&gt;
The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans (&amp;quot;The Pivot&amp;quot;), and failing more cheaply.&lt;br /&gt;
&lt;br /&gt;
Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:&lt;br /&gt;
&lt;br /&gt;
# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.&lt;br /&gt;
# Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:&lt;br /&gt;
#* Technical failure&lt;br /&gt;
#* Failure to effectively address a real user need&lt;br /&gt;
#* Overinvestment&lt;br /&gt;
#* Outreach/Promotion failure&lt;br /&gt;
#* Design/UX failure&lt;br /&gt;
#* Project team communication failure&lt;br /&gt;
#* Missed opportunities (risk-averse failure)&lt;br /&gt;
#* Successes gleaned from failures&lt;br /&gt;
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.&lt;br /&gt;
# A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.&lt;br /&gt;
&lt;br /&gt;
I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* Becky Yoose&lt;br /&gt;
* Lisa Rabey&lt;br /&gt;
* Cynthia Ng (maybe) - cynthia [dot] s [dot] ng [at] gmail&lt;br /&gt;
* Patrick Berry, pberry@csuchico.edu&lt;br /&gt;
* Erin White, erwhite at vcu edu&lt;br /&gt;
* Ranti Junus, ranti.junus at gmail&lt;br /&gt;
&lt;br /&gt;
=== Solr 4 In Depth ===&lt;br /&gt;
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)&lt;br /&gt;
&lt;br /&gt;
The long awaited and much anticipated Solr 4 has been released!   It's a really big deal.  There are so many improvements, it makes the head spin.  This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format. Sounds like this is an evening thing that might happen at a bar somewhere?&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* First and last name&lt;br /&gt;
* Erin Fahy - erin.fahy at mtholyoke edu&lt;br /&gt;
* Esmé Cowles, escowles@ucsd.edu&lt;br /&gt;
* Jon Stroop&lt;br /&gt;
* Adam Constabars&lt;br /&gt;
* Kevin Clarke&lt;br /&gt;
* Jacob Andresen (jacob at reindex dot dk)&lt;br /&gt;
* Ted Lawless (tlawless at brown dot edu)&lt;br /&gt;
* Tom Burton-West&lt;br /&gt;
* Curtis Thacker&lt;br /&gt;
* Eric James eric dot james at yale dot edu&lt;br /&gt;
* Bess Sadler (bess at stanford dot edu)&lt;br /&gt;
* Michael North&lt;br /&gt;
* Charles Draper&lt;br /&gt;
* Nick Cappadona&lt;br /&gt;
* Stephanie Collett - stephanie dot collett at ucop dot edu&lt;br /&gt;
* Kalee Sprague - kalee dot sprague at yale dot edu&lt;br /&gt;
* Jeff Peterson - gpeterso at umn dot edu&lt;br /&gt;
* Erik Hetzner&lt;br /&gt;
* Demian Katz - demian dot katz at villanova dot edu&lt;br /&gt;
* Eben English - eenglish at bpl dot org&lt;br /&gt;
* Raman Chandrasekar &lt;br /&gt;
* Jason Ronallo - jnronall@ncsu.edu&lt;br /&gt;
* Eric Larson - elarson@library.wisc.edu&lt;br /&gt;
* Mike Hagedon - hagedonm at u dot library dot arizona dot edu&lt;br /&gt;
* Jesse Brown - jfbrown78 at gmail dot com&lt;br /&gt;
* Steven Marsden - steven.marsden@ryerson.ca&lt;br /&gt;
* Zeno Tajoli - tajoli at cilea it&lt;br /&gt;
* Charles Ledvina - charles att indexdata dott com&lt;br /&gt;
* Tracy Seneca - tjseneca@uic.edu&lt;br /&gt;
* Tod Olson - tod at uchicago dot edu&lt;br /&gt;
* Esther Verreau - everreau skokielibrary info&lt;br /&gt;
* Jane Sandberg - sandbrg2 at illinois dot edu&lt;br /&gt;
* Mark Redar&lt;br /&gt;
[[Category:Code4Lib2013]]&lt;/div&gt;</summary>
		<author><name>Rshanrath</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_preconference_proposals&amp;diff=29442</id>
		<title>2013 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_preconference_proposals&amp;diff=29442"/>
				<updated>2012-12-14T14:45:41Z</updated>
		
		<summary type="html">&lt;p&gt;Rshanrath: /* Data Visualization Hackfest */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Proposals '''now closed'''.&lt;br /&gt;
&lt;br /&gt;
Spaces available: 4+ Rooms&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
=== Talk Title ===&lt;br /&gt;
 &lt;br /&gt;
* Presenter/Leader, affiliation (optional), and email address (mandatory!)&lt;br /&gt;
* Second Presenter/Leader, affiliation, email address, if applicable&lt;br /&gt;
&lt;br /&gt;
Description.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Full Day==&lt;br /&gt;
&lt;br /&gt;
===Drupal4lib Sub-con Barcamp===&lt;br /&gt;
&lt;br /&gt;
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or &lt;br /&gt;
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.&lt;br /&gt;
&lt;br /&gt;
If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.&lt;br /&gt;
&lt;br /&gt;
Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.&lt;br /&gt;
&lt;br /&gt;
====I plan on attending:====&lt;br /&gt;
&lt;br /&gt;
=====All Day=====&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
* [[User:Kevenj|Keven Jeffery]]&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)&lt;br /&gt;
* Christina Salazar (afternoon only)&lt;br /&gt;
* Sarah Dooley (afternoon)&lt;br /&gt;
* Josh Wilson, joshwilsonnc at gmail (likely afternoon only)&lt;br /&gt;
&lt;br /&gt;
==Half Day Morning==&lt;br /&gt;
=== Open space session ===&lt;br /&gt;
&lt;br /&gt;
* Dan Chudnov, dchud at gwu edu&lt;br /&gt;
&lt;br /&gt;
The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference.  Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it.  Use it as extra prep time for your upcoming prepared or lightning talk if you want.  We'll plan the morning out a little bit at the beginning, but not too much.  What we do will be up to the people there in the room.&lt;br /&gt;
&lt;br /&gt;
If there's interest, we could start with a &amp;quot;welcome to code4lib&amp;quot; introductory session for newcomers.&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* Devon Smith&lt;br /&gt;
* First and last name&lt;br /&gt;
* Esmé Cowles&lt;br /&gt;
* Jason Casden&lt;br /&gt;
* Ryan Eby&lt;br /&gt;
&lt;br /&gt;
=== Delivery services ===&lt;br /&gt;
* Ted Lawless, Brown University Library, tlawless at brown edu.  &lt;br /&gt;
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.&lt;br /&gt;
&lt;br /&gt;
Are you interested in making it easier for users to obtain copies of known items?  Do you feel your OpenURL and Interlibrary Loan software could be streamlined?  This pre-conference workshop will focus on providing services that deliver content to users.  Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.  &lt;br /&gt;
&lt;br /&gt;
Possible topics/activities include:&lt;br /&gt;
* panel discussion of what some libraries have done in this area&lt;br /&gt;
* comparisons of different approaches to addressing delivery &lt;br /&gt;
* overview of tools available &lt;br /&gt;
* sharing of strategies and experiences&lt;br /&gt;
* time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/heroku-360link Py360 Link]. &lt;br /&gt;
 &lt;br /&gt;
Resources and background information:&lt;br /&gt;
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway] &lt;br /&gt;
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]&lt;br /&gt;
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]&lt;br /&gt;
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* Ken Varnum&lt;br /&gt;
* Ayla Stein&lt;br /&gt;
* Curtis Thacker&lt;br /&gt;
* Rosalyn Metz&lt;br /&gt;
* James Van Mil&lt;br /&gt;
&lt;br /&gt;
=== Intro to Blacklight ===&lt;br /&gt;
* Bess Sadler, Stanford University Library (bess at stanford.edu)&lt;br /&gt;
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)&lt;br /&gt;
&lt;br /&gt;
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&amp;amp;A around local issues people might encounter. &lt;br /&gt;
&lt;br /&gt;
Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* Linda Ballinger&lt;br /&gt;
* Terry Brady&lt;br /&gt;
* Shawn Kiewel&lt;br /&gt;
* First and last name&lt;br /&gt;
&lt;br /&gt;
=== RailsBridge Intro to Ruby on Rails ===&lt;br /&gt;
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu&lt;br /&gt;
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)&lt;br /&gt;
* Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu&lt;br /&gt;
* Ross Singer, Talis, rossfsinger@gmail.com&lt;br /&gt;
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org&lt;br /&gt;
* Anyone else want to come and help folks? Contact Jason.&lt;br /&gt;
&lt;br /&gt;
RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language, the Rails framework, and version control with git. Participants will build a working Rails application. &lt;br /&gt;
&lt;br /&gt;
There will be some pre-preconference preparation needed so that we can effectively use our time. Details to come.&lt;br /&gt;
&lt;br /&gt;
* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* First and last name&lt;br /&gt;
* Jon Stroop&lt;br /&gt;
* Christina Salazar&lt;br /&gt;
* Karen Coombs - coombsk{at}oclc{dot}org&lt;br /&gt;
* Becky Yoose&lt;br /&gt;
* Jeremy Morse&lt;br /&gt;
* Julia Bauder&lt;br /&gt;
* Chung Kang&lt;br /&gt;
* Karen Miller&lt;br /&gt;
* Betsy Coles&lt;br /&gt;
* Jay Luker&lt;br /&gt;
* Santi Thompson&lt;br /&gt;
* Sarah Dooley&lt;br /&gt;
* Brandon Dudley&lt;br /&gt;
* Ken Irwin&lt;br /&gt;
* Dennis Ogg&lt;br /&gt;
* Ian Walls&lt;br /&gt;
* Steven Villereal&lt;br /&gt;
* Hillel Arnold&lt;br /&gt;
* Josh Wilson - joshwilsonnc at gmail&lt;br /&gt;
&lt;br /&gt;
===Intro to NoSQL Databases===&lt;br /&gt;
* Joshua Gomez, George Washington University, jngomez at gwu edu&lt;br /&gt;
&lt;br /&gt;
Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called &amp;quot;Big Data&amp;quot; problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, CouchDB, and Neo4j.&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* First and last name&lt;br /&gt;
* Esha Datta&lt;br /&gt;
* Trevor Thornton&lt;br /&gt;
* Michael Doran&lt;br /&gt;
* Ray Schwartz&lt;br /&gt;
* Kevin Clarke&lt;br /&gt;
* Andreas Orphanides&lt;br /&gt;
* Tommy Ingulfsen&lt;br /&gt;
* Harrison Dekker&lt;br /&gt;
* Eric James&lt;br /&gt;
* Sean Crowe&lt;br /&gt;
* Scott Hanrath&lt;br /&gt;
&lt;br /&gt;
==Half Day Afternoon==&lt;br /&gt;
=== Data Visualization Hackfest ===&lt;br /&gt;
* Chris Beer, cabeer at stanford.edu&lt;br /&gt;
* Dan Chudnov, dchud at gwu edu&lt;br /&gt;
&lt;br /&gt;
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating?  Interested in data visualization?  Well, this hackfest is for you.  Not familiar with the concept of a hackfest?  See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html &amp;quot;Where Librarians Go To Hack&amp;quot;] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest].  We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly: &lt;br /&gt;
 - we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.&lt;br /&gt;
 - we'll separate into groups and hack on stuff.&lt;br /&gt;
 - at the end of the day, we'll present our progress.&lt;br /&gt;
&lt;br /&gt;
Not a code hacker?  No worries; all skill sets and backgrounds are valuable! &lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* First and last name&lt;br /&gt;
* Devon Smith&lt;br /&gt;
* Esha Datta&lt;br /&gt;
* Ray Schwartz&lt;br /&gt;
* Karen Coombs - coombsk{at}oclc{dot}org&lt;br /&gt;
* Julia Bauder&lt;br /&gt;
* Jason Stirnaman (jstirnaman at kumc.edu)&lt;br /&gt;
* Joshua Gomez&lt;br /&gt;
* Ayla Stein&lt;br /&gt;
* Harrison Dekker&lt;br /&gt;
* Ian Walls&lt;br /&gt;
* Scott Hanrath&lt;br /&gt;
* [[User:Kevenj|Keven Jeffery]]&lt;br /&gt;
* James Van Mil&lt;br /&gt;
* Sean Crowe&lt;br /&gt;
&lt;br /&gt;
=== Intro to Hydra ===&lt;br /&gt;
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)&lt;br /&gt;
* Mike Giarlo, Penn State Information Technology Services (michael at psu.edu)&lt;br /&gt;
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)&lt;br /&gt;
&lt;br /&gt;
Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content.  Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame. &lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* Jeremy Prevost&lt;br /&gt;
* Dennis Ogg&lt;br /&gt;
* Linda Ballinger&lt;br /&gt;
* Terry Brady&lt;br /&gt;
* Betsy Coles&lt;br /&gt;
* Brendan Quinn&lt;br /&gt;
* Shawn Kiewel&lt;br /&gt;
* Steven Villereal&lt;br /&gt;
* Ryan Eby&lt;br /&gt;
* Dean Farrell&lt;br /&gt;
* First and last name&lt;br /&gt;
&lt;br /&gt;
=== Intro to Blacklight ===&lt;br /&gt;
* Bess Sadler, Stanford University Library (bess at stanford.edu)&lt;br /&gt;
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)&lt;br /&gt;
* Jason Ronallo, NC State (jronallo at gmail.com)&lt;br /&gt;
* Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)&lt;br /&gt;
&lt;br /&gt;
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&amp;amp;A around local issues people might encounter. &lt;br /&gt;
&lt;br /&gt;
Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* First and last name&lt;br /&gt;
* Jon Stroop&lt;br /&gt;
* Jeremy Morse&lt;br /&gt;
* Karen Miller&lt;br /&gt;
* Tommy Ingulfsen&lt;br /&gt;
* Chung Kang&lt;br /&gt;
* Santi Thompson&lt;br /&gt;
* Brandon Dudley&lt;br /&gt;
* Ken Irwin&lt;br /&gt;
* Brendan Quinn&lt;br /&gt;
* Hillel Arnold&lt;br /&gt;
&lt;br /&gt;
=== DPLA Intro/Hacking ===&lt;br /&gt;
 &lt;br /&gt;
* Presenter(s)/Leader(s): TBD&lt;br /&gt;
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)&lt;br /&gt;
&lt;br /&gt;
This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* First and last name&lt;br /&gt;
&lt;br /&gt;
=== Fail4lib ===&lt;br /&gt;
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)&lt;br /&gt;
* Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)&lt;br /&gt;
&lt;br /&gt;
The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans (&amp;quot;The Pivot&amp;quot;), and failing more cheaply.&lt;br /&gt;
&lt;br /&gt;
Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:&lt;br /&gt;
&lt;br /&gt;
# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.&lt;br /&gt;
# Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:&lt;br /&gt;
#* Technical failure&lt;br /&gt;
#* Failure to effectively address a real user need&lt;br /&gt;
#* Overinvestment&lt;br /&gt;
#* Outreach/Promotion failure&lt;br /&gt;
#* Design/UX failure&lt;br /&gt;
#* Project team communication failure&lt;br /&gt;
#* Missed opportunities (risk-averse failure)&lt;br /&gt;
#* Successes gleaned from failures&lt;br /&gt;
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.&lt;br /&gt;
# A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.&lt;br /&gt;
&lt;br /&gt;
I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* First and last name&lt;br /&gt;
* Becky Yoose&lt;br /&gt;
* Lisa Rabey&lt;br /&gt;
&lt;br /&gt;
=== Solr 4 In Depth ===&lt;br /&gt;
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)&lt;br /&gt;
&lt;br /&gt;
The long awaited and much anticipated Solr 4 has been released!   It's a really big deal.  There are so many improvements, it makes the head spin.  This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format. Sounds like this is an evening thing that might happen at a bar somewhere?&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* First and last name&lt;br /&gt;
* Esmé Cowles&lt;br /&gt;
* Jon Stroop&lt;br /&gt;
* Adam Constabars&lt;br /&gt;
* Kevin Clarke&lt;br /&gt;
* Jacob Andresen&lt;br /&gt;
* Ted Lawless&lt;br /&gt;
* Jay Luker&lt;br /&gt;
* Tom Burton-West&lt;br /&gt;
* Curtis Thacker&lt;br /&gt;
* Eric James&lt;br /&gt;
* Bess Sadler&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2013]]&lt;/div&gt;</summary>
		<author><name>Rshanrath</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_preconference_proposals&amp;diff=29441</id>
		<title>2013 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_preconference_proposals&amp;diff=29441"/>
				<updated>2012-12-14T14:40:40Z</updated>
		
		<summary type="html">&lt;p&gt;Rshanrath: /* Intro to NoSQL Databases */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Proposals '''now closed'''.&lt;br /&gt;
&lt;br /&gt;
Spaces available: 4+ Rooms&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
=== Talk Title ===&lt;br /&gt;
 &lt;br /&gt;
* Presenter/Leader, affiliation (optional), and email address (mandatory!)&lt;br /&gt;
* Second Presenter/Leader, affiliation, email address, if applicable&lt;br /&gt;
&lt;br /&gt;
Description.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Full Day==&lt;br /&gt;
&lt;br /&gt;
===Drupal4lib Sub-con Barcamp===&lt;br /&gt;
&lt;br /&gt;
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or &lt;br /&gt;
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.&lt;br /&gt;
&lt;br /&gt;
If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.&lt;br /&gt;
&lt;br /&gt;
Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.&lt;br /&gt;
&lt;br /&gt;
====I plan on attending:====&lt;br /&gt;
&lt;br /&gt;
=====All Day=====&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
* [[User:Kevenj|Keven Jeffery]]&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)&lt;br /&gt;
* Christina Salazar (afternoon only)&lt;br /&gt;
* Sarah Dooley (afternoon)&lt;br /&gt;
* Josh Wilson, joshwilsonnc at gmail (likely afternoon only)&lt;br /&gt;
&lt;br /&gt;
==Half Day Morning==&lt;br /&gt;
=== Open space session ===&lt;br /&gt;
&lt;br /&gt;
* Dan Chudnov, dchud at gwu edu&lt;br /&gt;
&lt;br /&gt;
The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference.  Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it.  Use it as extra prep time for your upcoming prepared or lightning talk if you want.  We'll plan the morning out a little bit at the beginning, but not too much.  What we do will be up to the people there in the room.&lt;br /&gt;
&lt;br /&gt;
If there's interest, we could start with a &amp;quot;welcome to code4lib&amp;quot; introductory session for newcomers.&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* Devon Smith&lt;br /&gt;
* First and last name&lt;br /&gt;
* Esmé Cowles&lt;br /&gt;
* Jason Casden&lt;br /&gt;
* Ryan Eby&lt;br /&gt;
&lt;br /&gt;
=== Delivery services ===&lt;br /&gt;
* Ted Lawless, Brown University Library, tlawless at brown edu.  &lt;br /&gt;
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.&lt;br /&gt;
&lt;br /&gt;
Are you interested in making it easier for users to obtain copies of known items?  Do you feel your OpenURL and Interlibrary Loan software could be streamlined?  This pre-conference workshop will focus on providing services that deliver content to users.  Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.  &lt;br /&gt;
&lt;br /&gt;
Possible topics/activities include:&lt;br /&gt;
* panel discussion of what some libraries have done in this area&lt;br /&gt;
* comparisons of different approaches to addressing delivery &lt;br /&gt;
* overview of tools available &lt;br /&gt;
* sharing of strategies and experiences&lt;br /&gt;
* time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/heroku-360link Py360 Link]. &lt;br /&gt;
 &lt;br /&gt;
Resources and background information:&lt;br /&gt;
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway] &lt;br /&gt;
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]&lt;br /&gt;
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]&lt;br /&gt;
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* Ken Varnum&lt;br /&gt;
* Ayla Stein&lt;br /&gt;
* Curtis Thacker&lt;br /&gt;
* Rosalyn Metz&lt;br /&gt;
* James Van Mil&lt;br /&gt;
&lt;br /&gt;
=== Intro to Blacklight ===&lt;br /&gt;
* Bess Sadler, Stanford University Library (bess at stanford.edu)&lt;br /&gt;
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)&lt;br /&gt;
&lt;br /&gt;
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&amp;amp;A around local issues people might encounter. &lt;br /&gt;
&lt;br /&gt;
Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* Linda Ballinger&lt;br /&gt;
* Terry Brady&lt;br /&gt;
* Shawn Kiewel&lt;br /&gt;
* First and last name&lt;br /&gt;
&lt;br /&gt;
=== RailsBridge Intro to Ruby on Rails ===&lt;br /&gt;
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu&lt;br /&gt;
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)&lt;br /&gt;
* Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu&lt;br /&gt;
* Ross Singer, Talis, rossfsinger@gmail.com&lt;br /&gt;
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org&lt;br /&gt;
* Anyone else want to come and help folks? Contact Jason.&lt;br /&gt;
&lt;br /&gt;
RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language, the Rails framework, and version control with git. Participants will build a working Rails application. &lt;br /&gt;
&lt;br /&gt;
There will be some pre-preconference preparation needed so that we can effectively use our time. Details to come.&lt;br /&gt;
&lt;br /&gt;
* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* First and last name&lt;br /&gt;
* Jon Stroop&lt;br /&gt;
* Christina Salazar&lt;br /&gt;
* Karen Coombs - coombsk{at}oclc{dot}org&lt;br /&gt;
* Becky Yoose&lt;br /&gt;
* Jeremy Morse&lt;br /&gt;
* Julia Bauder&lt;br /&gt;
* Chung Kang&lt;br /&gt;
* Karen Miller&lt;br /&gt;
* Betsy Coles&lt;br /&gt;
* Jay Luker&lt;br /&gt;
* Santi Thompson&lt;br /&gt;
* Sarah Dooley&lt;br /&gt;
* Brandon Dudley&lt;br /&gt;
* Ken Irwin&lt;br /&gt;
* Dennis Ogg&lt;br /&gt;
* Ian Walls&lt;br /&gt;
* Steven Villereal&lt;br /&gt;
* Hillel Arnold&lt;br /&gt;
* Josh Wilson - joshwilsonnc at gmail&lt;br /&gt;
&lt;br /&gt;
===Intro to NoSQL Databases===&lt;br /&gt;
* Joshua Gomez, George Washington University, jngomez at gwu edu&lt;br /&gt;
&lt;br /&gt;
Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called &amp;quot;Big Data&amp;quot; problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, CouchDB, and Neo4j.&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* First and last name&lt;br /&gt;
* Esha Datta&lt;br /&gt;
* Trevor Thornton&lt;br /&gt;
* Michael Doran&lt;br /&gt;
* Ray Schwartz&lt;br /&gt;
* Kevin Clarke&lt;br /&gt;
* Andreas Orphanides&lt;br /&gt;
* Tommy Ingulfsen&lt;br /&gt;
* Harrison Dekker&lt;br /&gt;
* Eric James&lt;br /&gt;
* Sean Crowe&lt;br /&gt;
* Scott Hanrath&lt;br /&gt;
&lt;br /&gt;
==Half Day Afternoon==&lt;br /&gt;
=== Data Visualization Hackfest ===&lt;br /&gt;
* Chris Beer, cabeer at stanford.edu&lt;br /&gt;
* Dan Chudnov, dchud at gwu edu&lt;br /&gt;
&lt;br /&gt;
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating?  Interested in data visualization?  Well, this hackfest is for you.  Not familiar with the concept of a hackfest?  See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html &amp;quot;Where Librarians Go To Hack&amp;quot;] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest].  We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly: &lt;br /&gt;
 - we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.&lt;br /&gt;
 - we'll separate into groups and hack on stuff.&lt;br /&gt;
 - at the end of the day, we'll present our progress.&lt;br /&gt;
&lt;br /&gt;
Not a code hacker?  No worries; all skill sets and backgrounds are valuable! &lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* First and last name&lt;br /&gt;
* Devon Smith&lt;br /&gt;
* Esha Datta&lt;br /&gt;
* Ray Schwartz&lt;br /&gt;
* Karen Coombs - coombsk{at}oclc{dot}org&lt;br /&gt;
* Julia Bauder&lt;br /&gt;
* Jason Stirnaman (jstirnaman at kumc.edu)&lt;br /&gt;
* Joshua Gomez&lt;br /&gt;
* Ayla Stein&lt;br /&gt;
* Harrison Dekker&lt;br /&gt;
* Ian Walls&lt;br /&gt;
* [[User:Kevenj|Keven Jeffery]]&lt;br /&gt;
* James Van Mil&lt;br /&gt;
* Sean Crowe&lt;br /&gt;
&lt;br /&gt;
=== Intro to Hydra ===&lt;br /&gt;
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)&lt;br /&gt;
* Mike Giarlo, Penn State Information Technology Services (michael at psu.edu)&lt;br /&gt;
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)&lt;br /&gt;
&lt;br /&gt;
Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content.  Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame. &lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* Jeremy Prevost&lt;br /&gt;
* Dennis Ogg&lt;br /&gt;
* Linda Ballinger&lt;br /&gt;
* Terry Brady&lt;br /&gt;
* Betsy Coles&lt;br /&gt;
* Brendan Quinn&lt;br /&gt;
* Shawn Kiewel&lt;br /&gt;
* Steven Villereal&lt;br /&gt;
* Ryan Eby&lt;br /&gt;
* Dean Farrell&lt;br /&gt;
* First and last name&lt;br /&gt;
&lt;br /&gt;
=== Intro to Blacklight ===&lt;br /&gt;
* Bess Sadler, Stanford University Library (bess at stanford.edu)&lt;br /&gt;
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)&lt;br /&gt;
* Jason Ronallo, NC State (jronallo at gmail.com)&lt;br /&gt;
* Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)&lt;br /&gt;
&lt;br /&gt;
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&amp;amp;A around local issues people might encounter. &lt;br /&gt;
&lt;br /&gt;
Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* First and last name&lt;br /&gt;
* Jon Stroop&lt;br /&gt;
* Jeremy Morse&lt;br /&gt;
* Karen Miller&lt;br /&gt;
* Tommy Ingulfsen&lt;br /&gt;
* Chung Kang&lt;br /&gt;
* Santi Thompson&lt;br /&gt;
* Brandon Dudley&lt;br /&gt;
* Ken Irwin&lt;br /&gt;
* Brendan Quinn&lt;br /&gt;
* Hillel Arnold&lt;br /&gt;
&lt;br /&gt;
=== DPLA Intro/Hacking ===&lt;br /&gt;
 &lt;br /&gt;
* Presenter(s)/Leader(s): TBD&lt;br /&gt;
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)&lt;br /&gt;
&lt;br /&gt;
This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* First and last name&lt;br /&gt;
&lt;br /&gt;
=== Fail4lib ===&lt;br /&gt;
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)&lt;br /&gt;
* Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)&lt;br /&gt;
&lt;br /&gt;
The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans (&amp;quot;The Pivot&amp;quot;), and failing more cheaply.&lt;br /&gt;
&lt;br /&gt;
Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:&lt;br /&gt;
&lt;br /&gt;
# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.&lt;br /&gt;
# Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:&lt;br /&gt;
#* Technical failure&lt;br /&gt;
#* Failure to effectively address a real user need&lt;br /&gt;
#* Overinvestment&lt;br /&gt;
#* Outreach/Promotion failure&lt;br /&gt;
#* Design/UX failure&lt;br /&gt;
#* Project team communication failure&lt;br /&gt;
#* Missed opportunities (risk-averse failure)&lt;br /&gt;
#* Successes gleaned from failures&lt;br /&gt;
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.&lt;br /&gt;
# A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.&lt;br /&gt;
&lt;br /&gt;
I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* First and last name&lt;br /&gt;
* Becky Yoose&lt;br /&gt;
* Lisa Rabey&lt;br /&gt;
&lt;br /&gt;
=== Solr 4 In Depth ===&lt;br /&gt;
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)&lt;br /&gt;
&lt;br /&gt;
The long awaited and much anticipated Solr 4 has been released!   It's a really big deal.  There are so many improvements, it makes the head spin.  This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format. Sounds like this is an evening thing that might happen at a bar somewhere?&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* First and last name&lt;br /&gt;
* Esmé Cowles&lt;br /&gt;
* Jon Stroop&lt;br /&gt;
* Adam Constabars&lt;br /&gt;
* Kevin Clarke&lt;br /&gt;
* Jacob Andresen&lt;br /&gt;
* Ted Lawless&lt;br /&gt;
* Jay Luker&lt;br /&gt;
* Tom Burton-West&lt;br /&gt;
* Curtis Thacker&lt;br /&gt;
* Eric James&lt;br /&gt;
* Bess Sadler&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2013]]&lt;/div&gt;</summary>
		<author><name>Rshanrath</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_talks_proposals&amp;diff=28324</id>
		<title>2013 talks proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_talks_proposals&amp;diff=28324"/>
				<updated>2012-11-09T18:30:23Z</updated>
		
		<summary type="html">&lt;p&gt;Rshanrath: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Deadline has been extended by request due to the hurricane/storm.'''&lt;br /&gt;
&lt;br /&gt;
Deadline for talk submission is ''Friday, November 9'' at 11:59pm ET. We ask that no changes be made after this point, so that every voter reads the same thing. You can update your description again after voting closes.&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;
* uniqueness&lt;br /&gt;
* awesomeness&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;
== 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 applicable&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;
== All Teh Metadatas Re-Revisited ==&lt;br /&gt;
 &lt;br /&gt;
* Esme Cowles, UC San Diego Library, escowles AT ucsd DOT edu&lt;br /&gt;
* Matt Critchlow, UC San Diego Library, mcritchlow AT ucsd DOT edu&lt;br /&gt;
* Bradley Westbrook, UC San Diego Library, bdwestbrook AT ucsd DOT edu&lt;br /&gt;
&lt;br /&gt;
Last year Declan Fleming presented ALL TEH METADATAS and reviewed our UC&lt;br /&gt;
San Diego Library Digital Asset Management system and RDF data model. You&lt;br /&gt;
may be shocked to hear that all that metadata wasn't quite enough to&lt;br /&gt;
handle increasingly complex digital library and research data in an&lt;br /&gt;
elegant way. Our ad-hoc, 8-year-old data model has also been added to in&lt;br /&gt;
inconsistent ways and our librarians and developers have not always been&lt;br /&gt;
perfectly in sync in understanding how the data model has evolved over&lt;br /&gt;
time.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
In this presentation we'll review our process of locking a team of&lt;br /&gt;
librarians and developers in a room to figure out a new data model, from&lt;br /&gt;
domain definition through building and testing an OWL ontology. We¹ll also&lt;br /&gt;
cover the challenges we ran into, including the review of existing&lt;br /&gt;
controlled vocabularies and ontologies, or lack thereof, and the decisions&lt;br /&gt;
made to cover the gaps. Finally, we'll discuss how we engaged the digital&lt;br /&gt;
library community for feedback and what we have to do next. We all know&lt;br /&gt;
that Things Fall Apart, this is our attempt at Doing Better This Time.&lt;br /&gt;
&lt;br /&gt;
== Modernizing VuFind with Zend Framework 2 ==&lt;br /&gt;
&lt;br /&gt;
* Demian Katz, Villanova University, demian DOT katz AT villanova DOT edu&lt;br /&gt;
&lt;br /&gt;
When setting goals for a new major release of VuFind, use of an existing web framework was an important decision to encourage standardization and avoid reinvention of the wheel.  Zend Framework 2 was selected as providing the best balance between the cutting-edge (ZF2 was released in 2012) and stability (ZF1 has a long history and many adopters).  This talk will examine some of the architecture and features of the new framework and discuss how it has been used to improve the VuFind project.&lt;br /&gt;
&lt;br /&gt;
== Did You Really Say That Out Loud?  Tools and Techniques for Safe Public WiFi Computing  ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]], LYRASIS, Peter.Murray@lyrasis.org&lt;br /&gt;
&lt;br /&gt;
Public WiFi networks, even those that have passwords, are nothing more that an old-time [https://en.wikipedia.org/wiki/Party_line_(telephony) party line]: what every you say can be easily heard by anyone nearby.  &lt;br /&gt;
Remember [https://en.wikipedia.org/wiki/Firesheep Firesheep]?  &lt;br /&gt;
It was an extension to Firefox that demonstrated how easy it was to snag session cookies and impersonate someone else.&lt;br /&gt;
So what are you sending out over the airwaves, and what techniques are available to prevent eavesdropping?&lt;br /&gt;
This talk will demonstrate tools and techniques for desktop and mobile operating systems that you should be using right now -- right here at Code4Lib -- to protect your data and your network activity.&lt;br /&gt;
&lt;br /&gt;
== Drupal 8 Preview — Symfony and Twig ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Drupal is a great platform for building web applications. Last year, the core developers decided to adopt the Symfony PHP framework, because it would lay the groundwork for the modernization (and de-PHP4ification) of the Drupal codebase. As I write this, the Symfony ClassLoader and HttpFoundation libraries are committed to Drupal core, with more elements likely before Drupal 8 code freeze.&lt;br /&gt;
&lt;br /&gt;
It seems almost certain that the Twig templating engine will supplant PHPtemplate as the core Drupal template engine. Twig is a powerful, secure theme building tool that removes PHP from the templating system, the result being a very concise and powerful theme layer.&lt;br /&gt;
&lt;br /&gt;
Symfony and Twig have a common creator, Fabien Potencier, who's overall goal is to rid the world of the excesses of PHP 4.&lt;br /&gt;
&lt;br /&gt;
== Neat! But How Do We Do It? - The Real-world Problem of Digitizing Complex Corporate Digital Objects ==&lt;br /&gt;
&lt;br /&gt;
* Matthew Mariner, University of Colorado Denver, Auraria Library, matthew.mariner@ucdenver.edu&lt;br /&gt;
&lt;br /&gt;
Isn't it neat when you discover that you are the steward of dozens of Sanborn Fire Instance Maps, hundreds of issues of a city directory, and thousands of photographs of persons in either aforementioned medium? And it's even cooler when you decide, &amp;quot;Let's digitize these together and make them one big awesome project to support public urban history&amp;quot;?  Unfortunately it's a far more difficult process than one imagines at inception and, sadly, doesn't always come to fruition.  My goal here is to discuss the technological (and philosophical) problems librarians and archivists face when trying to create ultra-rich complex corporate digital projects, or, rather, projects consisting of at least three facets interrelated by theme.  I intend to address these problems by suggesting management solutions, web workarounds, and, perhaps, a philosophy that might help in determining whether to even move forward or not.  Expect a few case studies of &amp;quot;grand ideas crushed by technological limitations&amp;quot; and &amp;quot;projects on the right track&amp;quot; to follow.   &lt;br /&gt;
 &lt;br /&gt;
== ResCarta Tools building a standard format for audio archiving, discovery and display ==&lt;br /&gt;
&lt;br /&gt;
* [[User:sarney|John Sarnowski]], The ResCarta Foundation, john.sarnowski@rescarta.org&lt;br /&gt;
&lt;br /&gt;
The free ResCarta Toolkit has been used by libraries and archives around the world to host city directories, newspapers, and historic photographs and by aerospace companies to search and find millions of engineering documents.  Now the ResCarta team has released audio additions to the toolkit. &lt;br /&gt;
&lt;br /&gt;
Create full text searchable oral histories, news stories, interviews. or build an archive of lectures; all done to Library of Congress standards.  The included transcription editor allows for accurate correction of the data conversion tool’s output.  Build true archives of text, photos and audio.  A single audio file carries the embedded Axml metadata, transcription, and word location information. Checks with the FADGI BWF Metaedit.&lt;br /&gt;
&lt;br /&gt;
ResCarta-Web presents your audio to IE, Chome, Firefox, Safari, and Opera browsers with full playback and word search capability. Display format is OGG!! &lt;br /&gt;
&lt;br /&gt;
You have to see this tool in action.  Twenty minutes from an audio file to transcribed, text-searchable website.  Be there or be L seven (Yeah, I’m that old)   &lt;br /&gt;
&lt;br /&gt;
== Format Designation in MARC Records: A Trip Down the Rabbit-Hole ==&lt;br /&gt;
 &lt;br /&gt;
* Michael Doran, University of Texas at Arlington, doran@uta.edu&lt;br /&gt;
&lt;br /&gt;
This presentation will use a seemingly simple data point, the &amp;quot;format&amp;quot; of the item being described, to illustrate some of the complexities and challenges inherent in the parsing of MARC records.  I will talk about abstract vs. concrete forms; format designation in the Leader, 006, 007, and 008 fixed fields as well as the 245 and 300 variable fields; pseudo-formats; what is mandatory vs. optional in respect to format designation in cataloging practice; and the differences between cataloging theory and practice as observed via format-related data mining of a mid-size academic library collection. &lt;br /&gt;
&lt;br /&gt;
I understand that most of us go to code4lib to hear about the latest sexy technologies.  While MARC isn't sexy, many of the new tools being discussed still need to be populated with data gleaned from MARC records.  MARC format designation has ramifications for search and retrieval, limits, and facets, both in the ILS and further downstream in next generation OPACs and web-scale discovery tools.  Even veteran library coders will learn something from this session. &lt;br /&gt;
&lt;br /&gt;
== Touch Kiosk 2: Piezoelectric Boogaloo ==&lt;br /&gt;
&lt;br /&gt;
* Andreas Orphanides, North Carolina State University Libraries, akorphan@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
At the NCSU Libraries, we provide realtime access to information on library spaces and services through an interactive touchscreen kiosk in our Learning Commons. In the summer of 2012, two years after its initial deployment, I redeveloped the kiosk application from the ground up, with an entirely new codebase and a completely redesigned user interface. The changes I implemented were designed to remedy previously identified shortcomings in the code and the interface design [1], and to enhance overall stability and performance of the application.&lt;br /&gt;
&lt;br /&gt;
In this presentation I will outline my revision process, highlighting the lessons I learned and the practices I implemented in the course of redevelopment. I will highlight the key features of the HTML/Javascript codebase that allow for increased stability, flexibility, and ease of maintenance; and identify the changes to the user interface that resulted from the usability findings I uncovered in my previous research. Finally, I will compare the usage patterns of the new interface to the analysis of the previous implementation to examine the practical effect of the implemented changes.&lt;br /&gt;
&lt;br /&gt;
I will also provide access to a genericized version of the interface code for others to build their own implementations of similar kiosk applications.&lt;br /&gt;
&lt;br /&gt;
[1] http://journal.code4lib.org/articles/5832&lt;br /&gt;
&lt;br /&gt;
== Wayfinding in a Cloud: Location Service for libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Petteri Kivimäki, The National Library of Finland, petteri.kivimaki@helsinki.fi&lt;br /&gt;
&lt;br /&gt;
Searching for books in large libraries can be a difficult task for a novice library user. This paper presents The Location Service, software as a service (SaaS) wayfinding application developed and managed by The National Library of Finland, which is targeted for all the libraries. The service provides additional information and map-based guidance to books and collections by showing their location on a map, and it can be integrated with any library management system, as the integration happens by adding a link to the service in the search interface. The service is being developed continuously based on the feedback received from the users.&lt;br /&gt;
&lt;br /&gt;
The service has two user interfaces: One for the customers and one for the library staff for managing the information related to the locations. The UI for the customers is fully customizable by the libraries, and the customization is done via template files by using the following techniques: HTML, CSS, and Javascript/jQuery. The service supports multiple languages, and the libraries have a full control of the languages, which they want to support in their environment.&lt;br /&gt;
&lt;br /&gt;
The service is written in Java and it uses Spring and Hibernate frameworks. The data is stored in PostgreSQL database, which is shared by all the libraries. They do not possess a direct access to the database, but the service offers an interface, which makes it possible to retrieve XML data over HTTP. Modification of the data via admin UI, however, is restricted, and access on the other libraries’ data is blocked.&lt;br /&gt;
&lt;br /&gt;
== Empowering Collection Owners with Automated Bulk Ingest Tools for DSpace ==&lt;br /&gt;
&lt;br /&gt;
* Terry Brady, Georgetown University, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Library has developed a number of applications to expedite the process of ingesting content into DSpace.&lt;br /&gt;
* Automatically inventory a collection of documents or images to be uploaded&lt;br /&gt;
* Generate a spreadsheet for metadata capture based on the inventory&lt;br /&gt;
* Generate item-level ingest folders, contents files and dublin core metadata for the items to be ingested&lt;br /&gt;
* Validate the contents of ingest folders prior to initiating the ingest to DSpace&lt;br /&gt;
* Present users with a simple, web-based form to initiate the batch ingest process&lt;br /&gt;
&lt;br /&gt;
The applications have eliminated a number of error-prone steps from the ingest workflow and have significantly reduced a number of tedious data editing steps.  These applications have empowered content experts to be in charge of their own collections. &lt;br /&gt;
&lt;br /&gt;
In this presentation, I will provide a demonstration of the tools that were built and discuss the development process that was followed.&lt;br /&gt;
&lt;br /&gt;
== Quality Assurance Reports for DSpace Collections ==&lt;br /&gt;
&lt;br /&gt;
* Terry Brady, Georgetown University, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Library has developed a collection of quality assurance reports to improve the consistency of the metadata in our DSpace collections.  The report infrastructure permits the creation of query snippets to test for possible consistency errors within the repository such as items missing thumbnails, items with multiple thumbnails, items missing a creation date, items containing improperly formatted dates, items without duplicated metadata fields, items recently added items across the repository, a community or a collection&lt;br /&gt;
&lt;br /&gt;
These reports have served to prioritize programmatic data cleanup tasks and manual data cleanup tasks.  The reports have served as a progress tracker for data cleanup work and will provide on-going monitoring of the metadata consistency of the repository.&lt;br /&gt;
&lt;br /&gt;
In this presentation, I will provide a demonstration of the tools that were built and discuss the development process that was followed.&lt;br /&gt;
&lt;br /&gt;
== A Hybrid Solution for Improving Single Sign-On to a Proxy Service with Squid and EZproxy through Shibboleth and ExLibris’ Aleph X-Server ==&lt;br /&gt;
&lt;br /&gt;
* Alexander Jerabek, UQAM - Université du Québec à Montréal, jerabek.alexander_j@uqam.ca&lt;br /&gt;
* Minh-Quang Nguyen, UQAM - Université du Québec à Montréal, nguyen.minh-quang@uqam.ca&lt;br /&gt;
&lt;br /&gt;
In this talk, we will describe how we developed and implemented a hybrid solution for improving single sign-on in conjunction with the library’s proxy service. This hybrid solution consists of integrating the disparate elements of EZproxy, the Squid workflow, Shibboleth, and the Aleph X-Server. We will report how this new integrated service improves the user experience. To our knowledge, this new service is unique and has not been implemented anywhere else. We will also present some statistics after approximately one year in production.&lt;br /&gt;
&lt;br /&gt;
See article: http://journal.code4lib.org/articles/7470&lt;br /&gt;
&lt;br /&gt;
== HTML5 Video Now! ==&lt;br /&gt;
&lt;br /&gt;
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Can you use HTML5 video now? Yes.&lt;br /&gt;
&lt;br /&gt;
I'll show you how to get started using HTML5 video, including gotchas, tips, and tricks. Beyond the basics we'll see the power of having video integrated into HTML and the browser. Finally, we'll look at examples that push the limits and show the exciting future of video on the Web.&lt;br /&gt;
&lt;br /&gt;
My experience comes from technical development of an oral history video clips project. I developed the technical aspects of the project, including video processing, server configuration, development of a public site, creation of an administrative interface, and video engagement analytics. Major portions of this work have been open sourced under an MIT license.&lt;br /&gt;
&lt;br /&gt;
== Hybrid Archival Collections Using Blacklight and Hydra ==&lt;br /&gt;
&lt;br /&gt;
* Adam Wead, Rock and Roll Hall of Fame and Museum, awead@rockhall.org&lt;br /&gt;
&lt;br /&gt;
At the Library and Archives of the Rock and Roll Hall of Fame, we use available tools such as Archivists' Toolkit to create EAD finding aids of our collections.  However, managing digital content created from these materials and the born-digital content that is also part of these collections represents a significant challenge.  In my presentation, I will discuss how we solve the problem of our hybrid collections by using Hydra as a digital asset manager and Blacklight as a unified presentation and discovery interface for all our materials.&lt;br /&gt;
&lt;br /&gt;
Our strategy centers around indexing ead xml into Solr as multiple documents: one for each collection, and one for every series, sub-series and item contained within a collection.  For discovery, we use this strategy to leverage item-level searching of archival collections alongside our traditional library content.  For digital collections, we use this same technique to represent a finding aid in Hydra as a set of linked objects using RDF.  New digital items are then linked to these parent objects at the collection and series level.  Once this is done, the items can be exported back out to the Blacklight solr index and the digital content appears along with the rest of the items in the collection.&lt;br /&gt;
&lt;br /&gt;
== Making the Web Accessible through Solid Design ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Cynthia|Cynthia Ng]] from Ryerson University Library &amp;amp; Archives&lt;br /&gt;
&lt;br /&gt;
In libraries, we are always trying our best to be accessible to everyone and we make every effort to do so physically, but what about our websites? Web designers are great at talking about the user experience and how to improve it, but what sometimes gets overlooked is how to make a site more accessible and meet accessibility guidelines. While guidelines are necessary to cover a minimum standard, web accessibility should come from good web design without ‘sacrificing’ features. While it's difficult to make a website fully accessible to everyone, there are easy, practical ways to make a site as accessible as possible.&lt;br /&gt;
&lt;br /&gt;
While the focus will be on websites and meeting the Web Accessibility Guidelines WCAG, the presentation will also touch on how to make custom web interfaces accessible.&lt;br /&gt;
&lt;br /&gt;
== Getting People to What They Need Fast! A Wayfinding Tool to Locate Books &amp;amp; Much More ==&lt;br /&gt;
 &lt;br /&gt;
* Steven Marsden, Ryerson University Library &amp;amp; Archives, steven dot marsden at ryerson dot ca&lt;br /&gt;
* [[User:Cynthia|Cynthia Ng]], Ryerson University Library &amp;amp; Archives&lt;br /&gt;
&lt;br /&gt;
Having a bewildered, lost user in the building or stacks is a common occurrence, but we can help our users find their way through enhanced maps and floor plans.  While not a new concept, these maps are integrated into the user’s flow of information without having to load a special app. The map not only highlights the location, but also provides all the related information with a link back to the detailed item view. During the first stage of the project, it has only be implemented for books (and other physical items), but the 'RULA Finder' is built to help users find just about anything and everything in the library including study rooms, computer labs, and staff. With a simple to use admin interface, it makes it easy for everyone, staff and users. &lt;br /&gt;
&lt;br /&gt;
The application is written in PHP with data stored in a MySQL database. The end-user interface involves jQuery, JSON, and the library's discovery layer (Summon) API.&lt;br /&gt;
&lt;br /&gt;
The presentation will not only cover the technical aspects, but also the implementation and usability findings.&lt;br /&gt;
&lt;br /&gt;
== De-sucking the Library User Experience ==&lt;br /&gt;
 &lt;br /&gt;
* Jeremy Prevost, Northwestern University, j-prevost {AT} northwestern [DOT] edu&lt;br /&gt;
&lt;br /&gt;
Have you ever thought that library vendors purposely create the worst possible user experience they can imagine because they just hate users? Have you ever thought that your own library website feels like it was created by committee rather than for users because, well, it was? I’ll talk about how we used vendor supplied APIs to our ILS and Discovery tool to create an experience for our users that sucks at least a little bit less.&lt;br /&gt;
&lt;br /&gt;
The talk will provide specific examples of how inefficient or confusing vendor supplied solutions are from a user perspective along with our specific streamlined solutions to the same problems. Code examples will be minimal as the focus will be on improving user experience rather than any one code solution of doing that. Examples may include the seemingly simple tasks of renewing a book or requesting an item from another campus library.&lt;br /&gt;
&lt;br /&gt;
== Solr Testing Is Easy with Rspec-Solr Gem ==&lt;br /&gt;
&lt;br /&gt;
* Naomi Dushay, Stanford University, ndushay AT stanford DOT edu&lt;br /&gt;
&lt;br /&gt;
How do you know if &lt;br /&gt;
&lt;br /&gt;
* your idea for &amp;quot;left anchoring&amp;quot; searches actually works?&lt;br /&gt;
* your field analysis for LC call numbers accommodates a suffix between the first and second cutter without breaking the rest of LC call number parsing?&lt;br /&gt;
* tweaking Solr configs to improve, say, Chinese searching, won't break Turkish and Cyrillic?&lt;br /&gt;
* changes to your solrconfig file accomplish what you wanted without breaking anything else?&lt;br /&gt;
&lt;br /&gt;
Avoid the whole app stack when writing Solr acceptance/relevancy/regression tests!  Forget cucumber and capybara.  This gem lets you easily (only 4 short files needed!) write tests like this, passing arbitrary parameters to Solr:&lt;br /&gt;
&lt;br /&gt;
  it &amp;quot;unstemmed author name Zare should precede stemmed variants&amp;quot; do&lt;br /&gt;
    resp = solr_response(author_search_args('Zare').merge({'fl'=&amp;gt;'id,author_person_display', 'facet'=&amp;gt;false}))&lt;br /&gt;
    resp.should include(&amp;quot;author_person_display&amp;quot; =&amp;gt; /\bZare\W/).in_each_of_first(3).documents&lt;br /&gt;
    resp.should_not include(&amp;quot;author_person_display&amp;quot; =&amp;gt; /Zaring/).in_each_of_first(20).documents&lt;br /&gt;
  end&lt;br /&gt;
      &lt;br /&gt;
  it &amp;quot;Cyrillic searching should work:  Восемьсoт семьдесят один день&amp;quot; do&lt;br /&gt;
    resp = solr_resp_doc_ids_only({'q'=&amp;gt;'Восемьсoт семьдесят один день'})&lt;br /&gt;
    resp.should include(&amp;quot;9091779&amp;quot;)&lt;br /&gt;
  end&lt;br /&gt;
   &lt;br /&gt;
  it &amp;quot;q of 'String quartets Parts' and variants should be plausible &amp;quot; do&lt;br /&gt;
    resp = solr_resp_doc_ids_only({'q'=&amp;gt;'String quartets Parts'})&lt;br /&gt;
    resp.should have_at_least(2000).documents&lt;br /&gt;
    resp.should have_the_same_number_of_results_as(solr_resp_doc_ids_only({'q'=&amp;gt;'(String quartets Parts)'}))&lt;br /&gt;
    resp.should have_more_results_than(solr_resp_doc_ids_only({'q'=&amp;gt;'&amp;quot;String quartets Parts&amp;quot;'}))&lt;br /&gt;
  end&lt;br /&gt;
   &lt;br /&gt;
  it &amp;quot;Traditional Chinese chars 三國誌 should get the same results as simplified chars 三国志&amp;quot; do&lt;br /&gt;
    resp = solr_response({'q'=&amp;gt;'三國誌', 'fl'=&amp;gt;'id', 'facet'=&amp;gt;false}) &lt;br /&gt;
    resp.should have_at_least(240).documents&lt;br /&gt;
    resp.should have_the_same_number_of_results_as(solr_resp_doc_ids_only({'q'=&amp;gt;'三国志'})) &lt;br /&gt;
  end&lt;br /&gt;
&lt;br /&gt;
See&lt;br /&gt;
   http://rubydoc.info/github/sul-dlss/rspec-solr/frames&lt;br /&gt;
   https://github.com/sul-dlss/rspec-solr&lt;br /&gt;
&lt;br /&gt;
and our production relevancy/acceptance/regression tests slowly migrating from cucumber to:&lt;br /&gt;
   https://github.com/sul-dlss/sw_index_tests&lt;br /&gt;
&lt;br /&gt;
== Northwestern's Digital Image Library ==&lt;br /&gt;
&lt;br /&gt;
*Mike Stroming, Northwestern University Library, m-stroming AT northwestern DOT edu&lt;br /&gt;
*Edgar Garcia, Northwestern University Library, edgar-garcia AT northwestern DOT edu&lt;br /&gt;
&lt;br /&gt;
At Northwestern University Library, we are about to release a beta version of our Digital Image Library (DIL).  DIL is an implementation of the Hydra technology that provides a Fedora repository solution for discovery of and access to over 100,000 images for staff, students, and scholars. Some important features are:&lt;br /&gt;
&lt;br /&gt;
*Build custom collection of images using drag-and-drop&lt;br /&gt;
*Re-order images within a collection using drag-and-drop&lt;br /&gt;
*Nest collections within other collections&lt;br /&gt;
*Create details/crops of images&lt;br /&gt;
*Zoom, rotate images&lt;br /&gt;
*Upload personal images&lt;br /&gt;
*Retrieve your own uploads and details from a collection&lt;br /&gt;
*Export a collection to a PowerPoint presentation&lt;br /&gt;
*Create a group of users and authorize access to your images&lt;br /&gt;
*Batch edit image metadata&lt;br /&gt;
&lt;br /&gt;
Our presentation will include a demo, explanation of the architecture, and a discussion of the benefits of being a part of the Hydra open-source community.&lt;br /&gt;
&lt;br /&gt;
== Two standards in a software (to say nothing of Normarc) ==&lt;br /&gt;
&lt;br /&gt;
*Zeno Tajoli, CINECA (Italy), z DOT tajoli AT cineca DOT it&lt;br /&gt;
&lt;br /&gt;
With this presentation I want to show how ILS Koha handles the support of three differnt MARC dialects:&lt;br /&gt;
MARC21, Unimarc and Normarc. The main points of the presentation:&lt;br /&gt;
&lt;br /&gt;
*Three MARC at MySQL level&lt;br /&gt;
*Three MARC at API level&lt;br /&gt;
*Three MARC at display&lt;br /&gt;
*Can I add a new format ?&lt;br /&gt;
&lt;br /&gt;
== Future Friendly Web Design for Libraries ==&lt;br /&gt;
&lt;br /&gt;
*[[User:michaelschofield|Michael Schofield]], Alvin Sherman Library, Research, and Information Technology Center, mschofied[dot]nova[dot]edu&lt;br /&gt;
&lt;br /&gt;
Libraries on the web are afterthoughts. Often their design is stymied on one hand by red tape imposed by the larger institution and on the other by an overload of too democratic input from colleagues. Slashed budgets / staff stretched too thin foul-up the R-word (that'd be &amp;quot;redesign&amp;quot;) - but things are getting pretty strange. Notions about the Web (and where it can be accessed) are changing. &lt;br /&gt;
&lt;br /&gt;
So libraries can only avoid refabbing their fixed-width desktop and jQuery Mobile m-dot websites for so long until desktop users evaporate and demand from patrons with web-ready refrigerators becomes deafening. Just when we have largely hopped on the bandwagon and gotten enthusiastic about being online, our users expect a library's site to look and perform great on everything. &lt;br /&gt;
&lt;br /&gt;
Our presence on the web should be built to weather ever-increasing device complexity. To meet users at their point of need, libraries must start thinking Future Friendly.&lt;br /&gt;
&lt;br /&gt;
This overview rehashes the approach and philosophy of library web design, re-orienting it for maximum accessibility and maximum efficiency of design. While just 20 minutes, we'll mull over techniques like mobile-first responsive web design, modular CSS, browser feature detection for progressive enhancement, and lots of nifty tricks.&lt;br /&gt;
&lt;br /&gt;
==BYU's discovery layer service aggregator==&lt;br /&gt;
&lt;br /&gt;
*Curtis	Thacker, Brigham Young University, curtis.thacker AT byu DOT edu&lt;br /&gt;
&lt;br /&gt;
It is clear that libraries will continue to experience rapid change based on the speed of technology. To acknowledge this new reality and to provide rapid response to shifting end user paradigms BYU has developed a custom service aggregator. At first our vendors looked at us a bit funny; however, in the last year they have been astonished with the fluid implementation of new services – here’s the short list:&lt;br /&gt;
&lt;br /&gt;
*filmfinder - a tool for browsing and searching films&lt;br /&gt;
*A custom book recommender service based on checkout data&lt;br /&gt;
*Integrated library services like personell, library hours, study room scheduler and database finder through a custom adwords system.&lt;br /&gt;
*A very geeky and powerful utility used for converting marc XML into primo compliant xml.&lt;br /&gt;
*Embedded floormaps&lt;br /&gt;
*A responsive web design&lt;br /&gt;
*Bing did-you-mean&lt;br /&gt;
*And many more.&lt;br /&gt;
&lt;br /&gt;
I will demo the system, review the archtecture and talk about future plans.&lt;br /&gt;
&lt;br /&gt;
==The Avalon Media System: A Next Generation Hydra Head For Audio and Video Delivery==&lt;br /&gt;
&lt;br /&gt;
* Michael Klein, Senior Software Developer, Northwestern University LIbrary, michael.klein AT northwestern DOT edu&lt;br /&gt;
* Nathan Rogers, Programmer/Analyst, Indiana University, rogersna AT indiana DOT edu&lt;br /&gt;
&lt;br /&gt;
Based on the success of the [http://www.dml.indiana.edu/ Variations] digital music platform, Indiana University and Northwestern University have developed a next generation educational tool for delivering multimedia resources to the classroom. The Avalon Media System (formerly Variations on Video) supports the ingest, media processing, management, and access-controlled delivery of library-managed video and audio collections. To do so, the system draws on several existing, mature, open source technologies:&lt;br /&gt;
&lt;br /&gt;
* The ingest, search, and discovery functionality of the Hydra framework&lt;br /&gt;
* The powerful multimedia workflow management features of Opencast Matterhorn&lt;br /&gt;
* The flexible Engage audio/video player&lt;br /&gt;
* The streaming capabilities of both Red5 Media Server (open source) and Adobe Flash Media Server (proprietary)&lt;br /&gt;
&lt;br /&gt;
Extensive customization options are built into the framework for tailoring the application to the needs of a specific institution.&lt;br /&gt;
&lt;br /&gt;
Our goal is to create an open platform that can be used by other institutions to serve the needs of the academic community. Release 1 is planned for a late February launch with future versions released every couple of months following. For more information visit http://avalonmediasystem.org/ and https://github.com/variations-on-video/hydrant.&lt;br /&gt;
&lt;br /&gt;
== The DH Curation Guide: Building a Community Resource == &lt;br /&gt;
&lt;br /&gt;
*Robin Davis, John Jay College of Criminal Justice, robdavis AT jjay.cuny.edu &lt;br /&gt;
*James Little, University of Illinois Urbana-Champaign, little9 AT illinois.edu  &lt;br /&gt;
&lt;br /&gt;
Data curation for the digital humanities is an emerging area of research and practice. The DH Curation Guide, launched in July 2012, is an educational resource that addresses aspects of humanities data curation in a series of expert-written articles. Each provides a succinct introduction to a topic with annotated lists of useful tools, projects, standards, and good examples of data curation done right. The DH Curation Guide is intended to be a go-to resource for data curation practitioners and learners in libraries, archives, museums, and academic institutions.  &lt;br /&gt;
&lt;br /&gt;
Because it's a growing field, we designed the DH Curation Guide to be a community-driven, living document. We developed a granular commenting system that encourages data curation community members to contribute remarks on articles, article sections, and article paragraphs. Moreover, we built in a way for readers to contribute and annotate resources for other data curation practitioners.  &lt;br /&gt;
&lt;br /&gt;
This talk will address how the DH Curation Guide is currently used and will include a sneak peek at the articles that are in store for the Guide’s future. We will talk about the difficulties and successes of launching a site that encourages community. We are all builders here, so we will also walk through developing the granular commenting/annotation system and the XSLT-powered publication workflow. &lt;br /&gt;
&lt;br /&gt;
== Solr Update == &lt;br /&gt;
&lt;br /&gt;
*Erik Hatcher, LucidWorks, erik.hatcher AT lucidworks.com &lt;br /&gt;
&lt;br /&gt;
Solr is continually improving.  Solr 4 was recently released, bringing dramatic changes in the underlying Lucene library and Solr-level features.  It's tough for us all to keep up with the various versions and capabilities.&lt;br /&gt;
&lt;br /&gt;
This talk will blaze through the highlights of new features and improvements in Solr 4 (and up).  Topics will include: SolrCloud, direct spell checking, surround query parser, and many other features.  We will focus on the features library coders really need to know about.&lt;br /&gt;
&lt;br /&gt;
== Reports for the People == &lt;br /&gt;
&lt;br /&gt;
*Kara Young, Keene State College, NH, kyoung1 at keene.edu&lt;br /&gt;
*Dana Clark, Keene State College, NH, dclark5 at keene.edu&lt;br /&gt;
&lt;br /&gt;
Libraries are increasingly being called upon to provide information on how our programs and services are moving our institutional strategic goals forward.  In support of College and departmental Information Literacy learning outcomes, Mason Library Systems at Keene State College developed an assessment database to record and report assessment activities by Library faculty.  Frustrated by the lack of freely available options for intuitively recording, accounting for, and outputting useful reports on instructional activities, Librarians requested a tool to make capturing and reporting activities (and their lives) easier.  Library Systems was able to respond to this need by working with librarians to identify what information is necessary to capture, where other assessment tools had fallen short, and ultimately by developing an application that supports current reporting imperatives while providing flexibility for future changes.&lt;br /&gt;
&lt;br /&gt;
The result of our efforts was an in-house browser interfaced Assessment Database to improve the process of data collection and analysis.  The application is written in PHP, data stored in a MySQL database, and presented via browser making extensive use of JQuery and JQuery plug-ins for data collection, manipulation, and presentation. &lt;br /&gt;
The presentation will outline the process undertaken to build a successful collaboration with Library faculty from conception to implementation, as well as the technical aspects of our trial-and-error approach. Plus: cool charts and graphs!&lt;br /&gt;
&lt;br /&gt;
==  Network Analyses of Library Catalog Data ==&lt;br /&gt;
 &lt;br /&gt;
* Kirk Hess, University of Illinois at Urbana-Champaign, kirkhess AT illinois.edu&lt;br /&gt;
* Harriett Green, University of Illinois at Urbana-Champaign, green19 AT illinois.edu &lt;br /&gt;
&lt;br /&gt;
Library collections are all too often like icebergs:  The amount exposed on the surface is only a fraction of the actual amount of content, and we’d like to recommend relevant items from deep within the catalog to users. With the assistance of an XSEDE Allocation grant (http://xsede.org), we’ve used R to reconstitute anonymous circulation data from the University of Illinois’s library catalog into separate user transactions. The transaction data is incorporated into subject analyses that use XSEDE supercomputing resources to generate predictive network analyses and visualizations of subject areas searched by library users using Gephi (https://gephi.org/). The test data set for developing the subject analyses consisted of approximately 38,000 items from the Literatures and Languages Library that contained 110,000 headings and 130,620 transactions. We’re currently working on developing a recommender system within VuFind to display the results of these analyses.&lt;br /&gt;
&lt;br /&gt;
== Pitfall! Working with Legacy Born Digital Materials in Special Collections ==&lt;br /&gt;
&lt;br /&gt;
* Donald Mennerich, The New York Public Library, don.mennerich AT gmail.com&lt;br /&gt;
* Mark A. Matienzo, Yale University Library, mark AT matienzo.org&lt;br /&gt;
&lt;br /&gt;
Archives and special collections are being faced with a growing abundance of  born digital material, as well as an abundance of many promising tools for managing them. However, one must consider the potential problems that can arise when approaching a collection containing legacy materials (from roughly the pre-internet era). Many of the tried and true, &amp;quot;best of breed&amp;quot; tools for digital preservation don't always work as they do for more recent materials, requiring a fair amount of ingenuity and use of &amp;quot;word of mouth tradecraft and knowledge exchanged through serendipitous contacts, backchannel conversations, and beer&amp;quot; (Kirschenbaum, &amp;quot;Breaking &amp;lt;code&amp;gt;badflag&amp;lt;/code&amp;gt;&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
Our presentation will focus on some of the strange problems encountered and creative solutions devised by two digital archivists in the course of preserving, processing, and providing access to collections at their institutions. We'll be placing particular particular emphasis of the pitfalls and crocodiles we've learned to swing over safely, while collecting treasure in the process. We'll address working with CP/M disks in collections of authors' papers, reconstructing a multipart hard drive backup spread across floppy disks, and more. &lt;br /&gt;
&lt;br /&gt;
== Project &amp;lt;s&amp;gt;foobar&amp;lt;/s&amp;gt; FUBAR ==&lt;br /&gt;
&lt;br /&gt;
* Becky Yoose, Grinnell College, yoosebec AT grinnell DOT edu&lt;br /&gt;
&lt;br /&gt;
Be it mandated from Those In A Higher Pay Grade Than You or self-inflicted, many of us deal with managing major library-related technology projects [1]. It’s common nowadays to manage multiple technology projects, and generally external and internal issues can be planned for to minimize project timeline shifts and quality of deliverables. Life, however, has other plans for you, and all your major library technology infrastructure projects pile on top of each other at the same time. How do you and your staff survive a train wreck of technology projects and produce deliverables to project stakeholders without having to go into the library IT version of the United States Federal Witness Protection Program?&lt;br /&gt;
&lt;br /&gt;
This session covers my experience with the collision of three major library technology projects - including a new institutional repository and an integrated library system migration - and how we dealt with external and internal factors, implemented damage control, and overall lessening the damage from the epic crash. You might laugh, you might cry, you will probably have flashbacks from previous projects, but you will come out of this session with a set of tools to use when you’re dealing with managing mission-critical projects.&lt;br /&gt;
&lt;br /&gt;
[1] Past code4lib talks have covered specific project management strategies, such as Agile, for application development. I will be focusing on and discussing general project management practices in relation to various library technology projects, many of which these strategies include in their own structures.&lt;br /&gt;
&lt;br /&gt;
== Implementing RFID in an Academic Library == &lt;br /&gt;
&lt;br /&gt;
* Scott Bacon, Coastal Carolina University, sbacon AT coastal DOT edu&lt;br /&gt;
&lt;br /&gt;
Coastal Carolina University’s Kimbel Library recently implemented RFID to increase security, provide better inventory control over library materials and enable do-it-yourself patron services such as self checkout. &lt;br /&gt;
&lt;br /&gt;
I’ll give a quick overview of RFID and the components involved and then will talk about how our library utilized the technology. It takes a lot of research, time, money and not too little resourcefulness to make your library RFID-ready. I’ll show how we developed our project timeline, how we assessed and evaluated vendors and how we navigated the bid process. I’ll also talk about hardware and software installation, configuration and troubleshooting and will discuss our book and media collection encoding process. &lt;br /&gt;
&lt;br /&gt;
We encountered myriad issues with our vendor, the hardware and the software. Would we do it all over again? Should your library consider RFID? Caveats abound...&lt;br /&gt;
&lt;br /&gt;
== Coding an Academic Library Intranet in Drupal: Now We're Getting Organizized... ==&lt;br /&gt;
&lt;br /&gt;
* Scott Bacon, Coastal Carolina University, sbacon AT coastal DOT edu&lt;br /&gt;
&lt;br /&gt;
The Kimbel Library Intranet is coded in Drupal 7, and was created to increase staff communication and store documentation. This presentation will contain an overview of our intranet project, including the modules we used, implementation issues, and possible directions in future development phases. I won’t forget to talk about the slew of tasty development issues we faced, including dealing with our university IT department, user buy-in, site navigation, user roles, project management, training and mobile modules (or the lack thereof). And some other fun (mostly) true anecdotes will surely be shared. &lt;br /&gt;
&lt;br /&gt;
The main functions of Phase I of this project were to increase communication across departments and committees, facilitate project management and revise the library's shared drive. Another important function of this first phase was to host mission-critical documentation such as strategic goals, policies and procedures. Phase II of this project will focus on porting employee tasks into the centralized intranet environment. This development phase, which aims to replicate and automate the bulk of staff workflows within a content management system, will be a huge undertaking. &lt;br /&gt;
&lt;br /&gt;
We chose Drupal as our intranet platform because of its extensibility, flexibility and community support. We are also moving our entire library web presence to Drupal in 2013 and will be soliciting any advice on which modules to use/avoid and which third-party services to wrangle into the Drupal environment. Should we use Drupal as the back-end to our entire Web presence? Why or why not?&lt;br /&gt;
&lt;br /&gt;
== Hands off! Best Practices and Top Ten Lists for Code Handoffs ==&lt;br /&gt;
 &lt;br /&gt;
* Naomi Dushay, Stanford University Library, ndushay@stanford.edu&lt;br /&gt;
* Bess Sadler, Stanford University Library, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Transition points in who is the primary developer on an actively developing code base can be a source of frustration for everyone involved. We've tried to minimize that pain point as much as possible through the use of agile methods like test driven development, continuous integration, and modular design. Has optimizing for developer happiness brought us happiness? What's worked, what hasn't, and what's worth adopting? How do you keep your project in a state where you can easily hand it off? &lt;br /&gt;
&lt;br /&gt;
== How to be an effective evangelist for your open source project ==&lt;br /&gt;
 &lt;br /&gt;
* Bess Sadler, Stanford University Library, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
The difference between an open source software project that gets new adopters and new contributing community members (which is to say, a project that goes on existing for any length of time) and a project that doesn't, often isn't a question of superior design or technology. It's more often a question of whether the advocates for the project can convince institutional leaders AND front line developers that a project is stable and trustworthy. What are successful strategies for attracting development partners? I'll try to answer that and talk about what we could do as a community to make collaboration easier.  &lt;br /&gt;
&lt;br /&gt;
== Thoughts from an open source vendor - What makes a &amp;quot;good&amp;quot; vendor in a meritocracy? ==&lt;br /&gt;
&lt;br /&gt;
* Matt Zumwalt, Data Curation Experts / MediaShelf / Hydra Project, matt@curationexperts.com&lt;br /&gt;
&lt;br /&gt;
What is the role of vendors in open source?  What should be the position of vendors in a meritocracy?  What are the avenues for encouraging great vendors who contribute to open source communities in valuable ways?  How you answer these questions has a huge impact on a community, and in order to formulate strong answers, you need to be well informed.  Let’s glimpse at the business practicalities of this situation, beginning with 1) an overview of the viable profit models for open-source software, 2) some of the realities of vendor involvement in open source, and 3) an account of the ins &amp;amp; outs of compensation &amp;amp; equity structures within for-profit corporations.&lt;br /&gt;
&lt;br /&gt;
The topics of power &amp;amp; influence, fairness, community participation, software quality, employment and personal profit are fair game, along with software licensing, support,  sponsorship, closed source software and the role of sales people.&lt;br /&gt;
&lt;br /&gt;
This presentation will draw on personal experience from the past seven years spent bootstrapping and running MediaShelf, a small but prolific for-profit consulting company that focuses entirely on open source digital repository software.  MediaShelf has played an active role in creating the Hydra Framework and continuously contributes to maintenance of Fedora and Blacklight. Those contributions have been funded through consulting contracts for authoring &amp;amp; implementing open source software on behalf of organizations around the world.&lt;br /&gt;
&lt;br /&gt;
==Occam’s Reader: A system that allows the sharing of eBooks via Interlibrary Loan==&lt;br /&gt;
&lt;br /&gt;
*Ryan Litsey, Texas Tech University, Ryan DOT Litsey AT ttu.edu&lt;br /&gt;
*Kenny Ketner, Texas Tech University, Kenny DOT Ketner AT ttu.edu&lt;br /&gt;
&lt;br /&gt;
Occam’s Reader is a software platform that allows the transfer and sharing of electronic books between libraries via existing interlibrary loan software. Occam’s Reader allows libraries to meet the growing need to be able to share our electronic resources. In the ever-increasing digital world, many of our collection development plans now include eBook platforms. The problem with eBooks, however, is that they are resources that are locked into the home library. With Occam’s Reader we can continue the centuries-old tradition of resource sharing and also keep up with the changing digital landscape. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Using Puppet for configuration management when no two servers look alike ==&lt;br /&gt;
* Eugene Vilensky, Senior Systems Administrator, Northwestern University Library, evilensky northwestern edu&lt;br /&gt;
&lt;br /&gt;
Configuration management is hot because it allows one to scale to thousands of machines, all of which look alike, and tightly manage changes across the nodes. Infrastructure as code, implement all changes programmatically, yadda yadda yadda.&lt;br /&gt;
&lt;br /&gt;
Unfortunately, servers which have gone unmanaged for a long time do not look very similar to each other.  Variables come in many forms, usually because of some or all of the following: Who installed the server, where it was installed, where the image was sourced from, when it was installed, where additional packages were sourced, and what kind of software was hosted on it.&lt;br /&gt;
&lt;br /&gt;
Bringing such machines into your configuration management platform is no harder and no easier than some or all of the following options options: 1) blow such machines away and start from scratch, migrate your data. 2) Find the lowest common baseline between the current state and the ideal state and start the work there. 3) implement new features/services on existing unmanaged machines but manage the new features/services.&lt;br /&gt;
&lt;br /&gt;
I will describe our experiences at the library for all three options using the Puppet open-source tool on Enterprise Linux 5 and 6.&lt;br /&gt;
&lt;br /&gt;
== REST &amp;lt;b&amp;gt;IS&amp;lt;/b&amp;gt; Your Mobile Strategy ==&lt;br /&gt;
&lt;br /&gt;
* Richard Wolf, University of Illinois at Chicago, richwolf@uic.edu&lt;br /&gt;
&lt;br /&gt;
Mobile is the new hotness ... and you can't be one of the cool kids unless you've got your own mobile app ... but the road to mobility is daunting.  I'll argue that it's actually easier than it seems ... and that the simplest way to mobility is to bring your data to the party, create a REST API around the data, tell developers about your API, and then let the magic happen.  To make my argument concrete, I'll show (lord help me!) how to go from an interesting REST API to a fun iOS tool for librarians and the general public in twenty minutes.&lt;br /&gt;
&lt;br /&gt;
== ARCHITECTING ScholarSphere: How We Built a Repository App That Doesn't Feel Like Yet Another Janky Old Repository App ==&lt;br /&gt;
&lt;br /&gt;
* Dan Coughlin, Penn State University, danny@psu.edu&lt;br /&gt;
* Mike Giarlo, Penn State University, michael@psu.edu&lt;br /&gt;
&lt;br /&gt;
ScholarSphere is a web application that allows the Penn State research community to deposit, share, and manage its scholarly works.  It is also, as some of our users and our peers have observed, a repository app that feels much more like Google Docs or GitHub than earlier-generation repository applications.  ScholarSphere is built upon the Hydra framework (Fedora Commons, Solr, Blacklight, Ruby on Rails), MySQL, Redis, Resque, FITS, ImageMagick, jQuery, Bootstrap, and FontAwesome.  We'll talk about techniques we used to:&lt;br /&gt;
&lt;br /&gt;
* eliminate Fedora-isms in the application&lt;br /&gt;
* model and expose RDF metadata in ways that users find unobtrusive&lt;br /&gt;
* manage permissions via a UI widget that doesn't stab you in the face&lt;br /&gt;
* harvest and connect controlled vocabularies (such as LCSH) to forms&lt;br /&gt;
* make URIs cool&lt;br /&gt;
* keep the app snappy without venturing into the architectural labyrinth of YAGNI&lt;br /&gt;
* build and queue background jobs&lt;br /&gt;
* expose social features and populate activity streams&lt;br /&gt;
* tie checksum verification, characterization, and version control to the UI&lt;br /&gt;
* let users upload and edit multiple files at once&lt;br /&gt;
&lt;br /&gt;
The application will be demonstrated; code will be shown; and we solemnly commit to showing ABSOLUTELY NO XML.&lt;br /&gt;
&lt;br /&gt;
==Coding with Mittens==&lt;br /&gt;
&lt;br /&gt;
*Jim LeFager, DePaul University Library jlefager@depaul.edu&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Working in an environment where developers have restricted access to servers and development areas, or where you are primarily working in multiple hosted systems with limited access, can be a challenge when you are attempting to incorporate any new functionality or improve an existing one.  Hosted web services present a benefit so that staff time is not dedicated to server maintenance and development, but customization can be difficult and at times impossible.  In many cases, incorporating any current API functionality requires additional work besides the original development work which can be frustrating and inefficient.  The result can be a Frankenstein monster of web services that is confusing to the user and difficult to navigate.  &lt;br /&gt;
&lt;br /&gt;
This talk will focus on some effective best practices, and maybe not so great but necessary practices that we have adopted to develop and improve our user’s experience using javascript/jQuery and CSS to manipulate our hosted environments.  This will include a review of available tools that allow collaborative development in the cloud, as well as examples of jQuery methods that have allowed us to take additional control of these hosted environments as well as track them using Google Analytics.  Included will be examples from Springshare Campus Guides, CONTENTdm and other hosted web spaces that have been ‘hacked’ to improve the UI.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Hacking the DPLA ==&lt;br /&gt;
* Nate Hill, Chattanooga Public Library,  nathanielhill AT gmail.com&lt;br /&gt;
* Sam Klein, Wikipedia, metasj AT gmail.com&lt;br /&gt;
&lt;br /&gt;
The Digital Public Library of America is a growing open-source platform to support digital libraries and archives of all kinds.  DPLA-alpha is available for testing, with data from six initial Hubs.  New APIs and data feeds are in development, with the next release scheduled for April.   &lt;br /&gt;
&lt;br /&gt;
Come learn what we are doing, how to contribute or hack the DPLA roadmap, and how you (or your favorite institution) can draw from and publish through it.  Larger institutions can join as a (content or service) hub, helping to aggregate and share metadata and services from across their {region, field, archive-type}.   We will discuss current challenges and possibilities (UI and API suggestions wanted!), apps being built on the platform, and related digitization efforts.&lt;br /&gt;
&lt;br /&gt;
DPLA has a transparent community and planning process; new participants are always welcome.  Half the time will be for suggestions and discussion.   Please bring proposals, problems, partnerships and possible paradoxes to discuss.&lt;br /&gt;
&lt;br /&gt;
== Introduction to SilverStripe 3.0 ==&lt;br /&gt;
 &lt;br /&gt;
* Ian Walls, University of Massachusetts Amherst, iwalls AT library DOT umass DOT edu&lt;br /&gt;
&lt;br /&gt;
SilverStripe is an open source Content Management System/development framework out of New Zealand, written in PHP, with a solid MVC structure.  This presentation will cover everything you need to know to get started with SilverStripe, including&lt;br /&gt;
* Features (and why you should consider SilverStripe)&lt;br /&gt;
* Requirements &amp;amp; Installation&lt;br /&gt;
* Model-View-Controller&lt;br /&gt;
* Key data types &amp;amp; configuration settings&lt;br /&gt;
* Modules&lt;br /&gt;
* Where to start with customization&lt;br /&gt;
* Community support and participation&lt;br /&gt;
&lt;br /&gt;
== Citation search in SOLR and second-order operators ==&lt;br /&gt;
 &lt;br /&gt;
* Roman Chyla, Astrophysics Data System, roman.chyla AT (cfa.harvad.edu|gmail.com)&lt;br /&gt;
&lt;br /&gt;
Citation search is basically about connections (Is the paper read by a friend of mine more important than others? Get me a paper read by somebody who cites many papers/is cited by many papers?), but the implementation of the citation search is surprisingly useful in many other areas.&lt;br /&gt;
&lt;br /&gt;
I will show 'guts' of the new citation search for astrophysics, it is generic and can be applied recursively to any Lucene query. Some people would call it a second-order operation because it works with the results of the previous (search) function. The talk will see technical details of the special query class, its collectors, how to add a new search operator and how to influence relevance scores. Then you can type with me: friends_of(friends_of(cited_for(keyword:&amp;quot;black holes&amp;quot;) AND keyword:&amp;quot;red dwarf&amp;quot;))&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Managing Segmented Images and Hierarchical Collections with Fedora-Commons and Solr ==&lt;br /&gt;
&lt;br /&gt;
* David Lacy, Villanova University, david DOT lacy AT villanova.edu&lt;br /&gt;
&lt;br /&gt;
Many of the resources within our digital library are split into parts -- newspapers, scrapbooks and journals being examples of collections of individual scanned pages.  In some cases, groups of pages within a collection, or segments within a particular page, may also represent chapters or articles.&lt;br /&gt;
&lt;br /&gt;
We recently devised a procedure to extract these &amp;quot;segmented resources&amp;quot; into their own objects within our repository, and index them individually in our Discovery Layer.&lt;br /&gt;
&lt;br /&gt;
In this talk I will explain how we dissected and organized these newly created resources with an extension to our Fedora Model, and how we make them discoverable through Solr configurations that facilitate browsable hierarchical relationships and field-collapsed results that group items within relevant resources.&lt;br /&gt;
&lt;br /&gt;
== Google Analytics, Event Tracking and Discovery Tools==&lt;br /&gt;
 &lt;br /&gt;
* Emily Lynema, North Carolina State University Libraries. ejlynema AT ncsu DOT edu&lt;br /&gt;
* Adam Constabaris, North Carolina State University Libraries, ajconsta AT ncsu DOT edu&lt;br /&gt;
&lt;br /&gt;
The NCSU Libraries is using Google Analytics increasingly across its website as a replacement for usage tracking via Urchin. More recently, we have also begun to use the event tracking features in Google Analytics. This has allowed us to gather usage statistics for activities that don’t initiate new requests to the server, such as clicks that hide and show already-loaded content (as in many tabbed interfaces).  Aggregating these events together with pageview tracking in Google Analytics presents a more unified picture of patron activity and can help improve design of tools like the library catalog.  While assuming a basic understanding of the use of Google Analytics pageview tracking, this presentation will start with an introduction to the event tracking capabilities that may be less widely known. &lt;br /&gt;
&lt;br /&gt;
We’ll share library catalog usage data pulled from Google Analytics, including information about  features that are common across the newest wave of catalog interfaces, such as tabbed content, Google Preview, and shelf browse. We will also cover the approach taken for the technical implementation of this data-intensive JavaScript event tracking.&lt;br /&gt;
&lt;br /&gt;
As a counterpart, we can demonstrate how we have begun to use Google Analytics event tracking in a proprietary vendor discovery tool (Serials Solutions Summon). While the same technical ideas govern this implementation, we can highlight the differences (read, challenges) inherent in utilizing this type of event tracking in vendor-owned application vs. a locally developed application.&lt;br /&gt;
&lt;br /&gt;
Along the way, hopefully you’ll learn a little about why you might (or might not) want to use Google Analytics event tracking yourself and see some interesting catalog usage stats.&lt;br /&gt;
&lt;br /&gt;
== Actions speak louder than words: Analyzing large-scale query logs to improve the research experience ==&lt;br /&gt;
&lt;br /&gt;
* Raman Chandrasekar, Serials Solutions, Raman DOT Chandrasekar AT serialssolutions DOT com&lt;br /&gt;
* Ted Diamond, Serials Solutions, Ted DOT Diamond AT serialssolutions DOT com&lt;br /&gt;
&lt;br /&gt;
Analyzing anonymized query and click through logs leads to a better understanding of user behaviors and intentions and provides great opportunities to respond to users with an improved search experience. A large-scale provider of SaaS services, Serials Solutions is uniquely positioned to learn from the dataset of queries aggregated from the Summon service generated by millions of users at hundreds of libraries around the world.&lt;br /&gt;
 &lt;br /&gt;
In this session, we will describe our Relevance Metrics Framework and provide examples of insights gained during its development and implementation. We will also cover recent product changes inspired by these insights. Chandra and Ted, from the Summon dev team, will share insights and outcomes from this ongoing process and highlight how analysis of large-scale query logs helps improve the academic research experience.&lt;br /&gt;
&lt;br /&gt;
== Supporting Gaming in the College Classroom == &lt;br /&gt;
&lt;br /&gt;
*Megan O'Neill, Albion College, moneill AT albion DOT edu&lt;br /&gt;
&lt;br /&gt;
Faculty are increasingly interested both in teaching with games and with gamifying their courses. Introducing digital games and game support for faculty through the library makes a lot of sense, but it comes with a thorny set of issues. This talk will discuss our library's initial steps toward creating a digital gamerspace and game support infrastructure in the library, including:&lt;br /&gt;
1) The scope and acquisitions decisions that make the most sense for us, and 2) Some difficulties we've discovered in trying to get our collection, physical- , digital- and head-space, and infrastructure up and going.&lt;br /&gt;
There will also be an extremely brief overview of WHY we decided to teach with games and to support gamification, what (if anything) to do about mobile gaming, and where games in education might be going.&lt;br /&gt;
&lt;br /&gt;
== Codecraft ==&lt;br /&gt;
 &lt;br /&gt;
* Devon Smith, OCLC Research, smithde@oclc.org&lt;br /&gt;
&lt;br /&gt;
We can think of and talk about software development as science, engineering, and craft. In this presentation, I'll talk about the craft aspect of software. From Wikipedia[1]: &amp;quot;In English, to describe something as a craft is to describe it as lying somewhere between an art (which relies on talent and technique) and a science (which relies on knowledge). In this sense, the English word craft is roughly equivalent to the ancient Greek term techne.&amp;quot; Of the questions who, what, where, why, when, and how, I will focus on why and how, with a minor in where.&lt;br /&gt;
&lt;br /&gt;
'''N.B.''': This will be a NON-TECHNICAL talk.&lt;br /&gt;
&lt;br /&gt;
[1] https://en.wikipedia.org/wiki/Craft#Classification&lt;br /&gt;
&lt;br /&gt;
== KnowBot: A Tool to Manage Reference and Beyond == &lt;br /&gt;
&lt;br /&gt;
* Sarah Park, Northwest Missouri State University&lt;br /&gt;
* Hong Gyu Han, Northwest Missouri State University&lt;br /&gt;
* Lori Mardis, Northwest Missouri State University&lt;br /&gt;
&lt;br /&gt;
Northwest Missouri State University has developed and used RefPole for collecting and analyzing reference statistics since 2005. RefPole was a tool to answer librarians’ needs to manage reference statistics and knowledge among librarians. It was an analysis tool for the library leaders to make decisions on library operations. RefPole was adequate for the internal use; however, it was developed for local access which keeps the collective reference knowledge from being shared beyond the desktop and from being accessed by students and faculty. &lt;br /&gt;
&lt;br /&gt;
In 2011, responding to growing internal and external need, the library has developed a web based knowledge base management system, KnowBot, in Ruby on Rail. KnowBot offers public searching, rating, cloud tagging, librarian, and reporting interfaces. With the additional public interfaces, it also extended reference services 24/7. Librarians can record responses to questions with graphics and multimedia. The reporting interface features not only the simple transactional data, but it also exhibits multi-dimensional analytic tool in real time.&lt;br /&gt;
&lt;br /&gt;
The presenters will demonstrate KnowBot; share the source code; and discuss the use of the knowledge base to answer the organizational and public need.&lt;br /&gt;
&lt;br /&gt;
== Creating a (mostly) integrated Patron Account with SirsiDynix Symphony and ILLiad ==&lt;br /&gt;
&lt;br /&gt;
* Emily Lynema, North Carolina State University Libraries, ejlynema AT ncsu DOT edu&lt;br /&gt;
* Jason Raitz, North Carolina State University Libraries, jcraitz AT ncsu DOT edu&lt;br /&gt;
&lt;br /&gt;
IIn 2012, the NCSU Libraries at long last replaced a vendor “my account” tool that had been running unsupported for years. With the opportunity to create something new, one of the initial goals was a user experience that more seamlessly combined ILS data from SirsiDynix Symphony with ILL data from ILLiad. As a Kuali OLE beta partner, the NCSU Libraries is looking at an ILS migration within the next few years, so another goal was to build the interface on top of a standard so it would not have to be re-written as part of the migration. And the icing on the cake was a transition from a local Perl-based authentication system to the newer campus-wide Shibboleth authentication.&lt;br /&gt;
&lt;br /&gt;
This presentation will start with our design goals for a new user interface, include a demonstration, and describe the simple techniques used to provide a more integrated view of Symphony and ILLiad patron data. The backbone of the actual application is built using Zend’s PHP Framework and integrates eXtensible Catalog’s NCIP Toolkit to reach out to Symphony for patron data. In addition, we can talk about our successes (and difficulties) using jQuery Mobile to create a mobile view using the same underlying code as the web version. As one of our first Shibboleth applications here in the Libraries, this experience also taught us first-hand about some of the challenges of this type of single sign-on.&lt;br /&gt;
&lt;br /&gt;
== SKOS Name Authority in a DSpace Institutional Repository ==&lt;br /&gt;
&lt;br /&gt;
* Tom Johnson, Oregon State University, thomas.johnson@oregonstate.edu&lt;br /&gt;
&lt;br /&gt;
Name ambiguity is widespread in institutional repositories. Searching by author, users are typically greeted by a variety of misspellings and permutations of initials, collision between contributors with similar names, and other problems inherent in uncontrolled (often user-submitted) data. While DSpace has the technical capacity to use controlled names, it relies on outside authority files (from LoC, for example) to do the heavy lifting. For institutional authors, this leaves a major coverage gap and creates namespace pollution on a vast scale (try searching [http://authorities.loc.gov authorities.loc.gov] for &amp;quot;Johnson, John&amp;quot;, sometime). &lt;br /&gt;
&lt;br /&gt;
OSU is solving this problem with an institutionally scoped, low maintenance SKOS/FOAF &amp;quot;name authority file&amp;quot;. People in the IR are assigned URIs, names are maintained as skos:prefLabel, altLabel, or hiddenLabel. We've developed a simple Python application allowing staff to update individual &amp;quot;records&amp;quot;, and code on the DSpace side to access the dataset over SPARQL. This presentation will walk you through where we are now, limitations we've run into, and possibilities for the future.&lt;br /&gt;
&lt;br /&gt;
== Meta-Harvesting: Harvesting the Harvesters ==&lt;br /&gt;
&lt;br /&gt;
* Steven Anderson, Boston Public Library, sanderson AT bpl DOT org&lt;br /&gt;
* Eben English, Boston Public Library, eenglish AT bpl DOT org&lt;br /&gt;
&lt;br /&gt;
The emerging Digital Public Library of America (http://dp.la/) has proposed to aggregate digital content for search and discovery from several regional &amp;quot;service hubs&amp;quot; that will provide metadata via an as-yet-unspecified harvest process. As these service hubs are already harvesters of digital content from myriad sources themselves, the potential for &amp;quot;telephone game&amp;quot;-esque data loss and/or transmutation is a significant danger.&lt;br /&gt;
&lt;br /&gt;
This talk will discuss the experience of Digital Commonwealth (http://www.digitalcommonwealth.org/), a statewide digital repository currently in the process of being revamped, refactored, and redesigned by the Boston Public Library using the Hydra Framework. The repository, which aggregates data from over 20 institutions (some of which are themselves aggregators), is also undergoing a massive metadata cleanup effort as records are prepared to be ingested into the DPLA as one of the regional service hubs. Topics will include automated and manual processes for data crosswalking and cleanup, advanced OAI-PMH chops, and the implications of the (at this time still-emerging) metadata standards and APIs being created by the DPLA.&lt;br /&gt;
&lt;br /&gt;
Every crosswalk, transformation, migration, harvest, or export/ingest of metadata requires informed decision making and precise attention to detail. This talk will provide insight into key decision points and potential quagmires, as well as a discussion of the challenges of dealing with heterogeneous data from a wide variety of institutions.&lt;br /&gt;
&lt;br /&gt;
== Pay No More Than £3 // DIY Digital Curation ==&lt;br /&gt;
 &lt;br /&gt;
* Chris Fitzpatrick, World Maritime University, cf AT wmu DOT se&lt;br /&gt;
&lt;br /&gt;
Are you a small library or archive? &amp;lt;br&amp;gt;&lt;br /&gt;
Do you feel you are being held back by limited technical resources?&amp;lt;br&amp;gt;&lt;br /&gt;
Tired of waiting around for the Google Books Library people to reply to your emails? &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Join the club. Open-source software, hackerspaces, dirt cheap storage, cloud computing, and social media make it possible for any institution to start curating digitally. Today.&lt;br /&gt;
This talk will cover some of the guerrilla tactics being employed to drag a small university's large collection into the internet age. &lt;br /&gt;
&lt;br /&gt;
Topics will include: &lt;br /&gt;
*Cheap and effective document scanning methods.&lt;br /&gt;
*Valuable resources found at your local hackerspace / makerspace / fablab.&lt;br /&gt;
*Metadata enrichment for the not-so-rich and NLP for the people.&lt;br /&gt;
*Utilizing social media to crowdsource your collection building.&lt;br /&gt;
*How to post-process, OCR, PDF, and ePub your documents using Free software.&lt;br /&gt;
*Ways to build out a digital repository with no servers, code, or large 2-year grants required. (ok, maybe some code).&lt;br /&gt;
&lt;br /&gt;
== IIIF: One Image Delivery API to Rule Them All ==&lt;br /&gt;
&lt;br /&gt;
* Willy Mene, Stanford University Libraries, wmene AT stanford DOT edu&lt;br /&gt;
* Stuart Snydman, Stanford University Libraries, snydman AT stanford DOT edu&lt;br /&gt;
&lt;br /&gt;
The International Image Interoperability Framework was conceived of by a group of research and national libraries determined to achieve the holy grail of seamless sharing and reuse of images in digital image repositories and applications.  By converging on common API’s for image delivery, metadata transmission and search, it is catalyzing the development of a new wave of interoperable image delivery software that will surpass the current crop of image viewers, page turners, and navigation systems, and in so doing give scholars an unprecedented level of consistent and rich access to image-based resources across participating repositories.&lt;br /&gt;
&lt;br /&gt;
The IIIF Image API (http://library.stanford.edu/iiif/image-api) specifies a web service that returns an image in response to a standard http or https request. The URL can specify the region, size, rotation, quality characteristics and format of the requested image. A URL can also be constructed to request basic technical information about the image to support client applications.  The API could be adopted by any image repository or service, and can be used to retrieve static images in response to a properly constructed URL.&lt;br /&gt;
&lt;br /&gt;
In this presentation we will review version 1 of the IIIF image api and validator, demonstrate applications by daring early adopters, and encourage widespread adoption.&lt;br /&gt;
&lt;br /&gt;
== Data-Driven Documents: Visualizing library data with D3.js ==&lt;br /&gt;
&lt;br /&gt;
* Bret Davidson, North Carolina State University Libraries, bret_davidson@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Several JavaScript libraries have emerged over the past few years for creating rich, interactive visualizations using web standards. Few are as powerful and flexible as D3.js[1]. D3 stands apart by merging web standards with a rich API and a unique approach to binding data to DOM elements, allowing you to apply data-driven transformations to a document. This emphasis on data over presentation has made D3 very popular; D3 is used by several prominent organizations including the New York Times[2], GOV.UK[3], and Trulia[4].&lt;br /&gt;
&lt;br /&gt;
Power usually comes at a cost, and D3 makes you pay with a steeper learning curve than many alternatives. In this talk, I will get you over the hump by introducing the core construct of D3, the Data-Join. I will also discuss when you might want to use D3.js, share some examples, and explore some advanced utilities like scales and shapes. I will close with a brief overview of how we are successfully using D3 at NCSU[5] and why investing time in learning D3 might make sense for your library.&lt;br /&gt;
&lt;br /&gt;
*[1]http://d3js.org/&lt;br /&gt;
*[2]http://www.nytimes.com/interactive/2012/08/24/us/drought-crops.html&lt;br /&gt;
*[3]https://www.gov.uk/performance/dashboard&lt;br /&gt;
*[4]http://trends.truliablog.com/vis/pricerange-boston/&lt;br /&gt;
*[5]http://www.lib.ncsu.edu/dli/projects/spaceassesstool&lt;br /&gt;
&lt;br /&gt;
== ''n'' Characters in Search of an Author ==&lt;br /&gt;
&lt;br /&gt;
* Jay Luker, IT Specialist, Smithsonian Astrophysics Data System, jluker@cfa.harvard.edu&lt;br /&gt;
&lt;br /&gt;
When it comes to author names the disconnect between our metadata and what a user might enter into a search box presents challenges when trying to maximize both precision and recall [0]. When indexing a paper written by &amp;quot;Wäterwheels, A&amp;quot; a goal should be to preserve as much as possible the original information. However, users searching by author name may frequently omit the diaeresis and search for simply, &amp;quot;Waterwheels&amp;quot;. The reverse of this scenario is also possible, i.e., your decrepit metadata contains only the ASCII, &amp;quot;Supybot, Zoia&amp;quot;, whereas the user enters, &amp;quot;Supybot, Zóia&amp;quot;. If recall is your highest priority the simple solution is to always downgrade to ASCII when indexing and querying. However this strategy sacrifices precision, as you will be unable to provide an &amp;quot;exact&amp;quot; search, necessary in cases where &amp;quot;Hacker, J&amp;quot; and &amp;quot;Häcker, J&amp;quot; really are two distinct authors.&lt;br /&gt;
&lt;br /&gt;
This talk will describe the strategy ADS[1] has devised for addressing common and edge-case problems faced when dealing with author name indexing and searching. I will cover the approach we devised to not only the transliteration issue described above, but also how we deal with author initials vs. full first and/or middle names, authors who have published under different forms of their name, authors who change their names (wha? people get married?!). Our implementation relies on Solr/Lucene[2], but my goal is an 80/20 mix of high- vs. low-level details to keep things both useful and stackgnostic [3].&lt;br /&gt;
&lt;br /&gt;
*[0] http://en.wikipedia.org/wiki/Precision_and_recall&lt;br /&gt;
*[1] http://www.adsabs.harvard.edu/&lt;br /&gt;
*[2] http://lucene.apache.org/solr/&lt;br /&gt;
*[3] http://en.wikipedia.org/wiki/Portmanteau&lt;br /&gt;
&lt;br /&gt;
== But, does it all still work : Testing Drupal with simpletest and casperjs ==&lt;br /&gt;
&lt;br /&gt;
* David Kinzer - Lead Developer, Jenkins Law Library, dkinzer@jenkinslaw.org&lt;br /&gt;
* Chad Nelson  - Developer, Jenkins Law Library, cnelson@jenkinslaw.org&lt;br /&gt;
&lt;br /&gt;
Most developers know that they should be writing tests along with their code, but not every developer knows how or where to get started. This talk will walk through the nuts and bolts of the testing a medium-sized Drupal site with many integrated moving parts. We’ll talk about unit testing of individual functions with [http://www.simpletest.org/en/overview.html SimpleTest] (and how that has changed how we write functions), functional testing of the user interface with [http://casperjs.org/ casperjs]. We will discuss automating deployment with [http://www.phing.info/ phing], [http://drupal.org/project/drush drush], [http://jenkins-ci.org/ jenkins-ci] &amp;amp; github, which, combined with our tests, removes the “hold-your-breath” feeling before updating our live site. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2013]]&lt;br /&gt;
&lt;br /&gt;
== Relations, Recommendations and PostgreSQL ==&lt;br /&gt;
&lt;br /&gt;
* William Denton, Web Librarian, York University, wdenton@yorku.ca&lt;br /&gt;
* Dan Scott, Systems Librarian, Laurentian University, dscott@laurentian.ca&lt;br /&gt;
&lt;br /&gt;
In 2012, a ragtag group of library hackers from various Ontario &lt;br /&gt;
universities, funded with only train tickets and fueled with Tim Hortons &lt;br /&gt;
coffee, assembled under the Scholars Portal banner to build a common &lt;br /&gt;
circulation data repository and recommendation engine: the Scholars &lt;br /&gt;
Portal Library Usage-based Recommendation Engine (SPLURGE). PostgreSQL, &lt;br /&gt;
the emerging darling of the old-school relational database world, is the &lt;br /&gt;
heart of SPLURGE, and the circulation data for Ontario's 400,000 &lt;br /&gt;
university students is its blood. Two of the contributors to this effort explore the PostgreSQL features &lt;br /&gt;
that SPLURGE uses to ease administration efforts, simplify application &lt;br /&gt;
development, and deliver high performance results. If you don't use &lt;br /&gt;
PostgreSQL for your data, you might want to try it after this &lt;br /&gt;
presentation; if you already do, you'll pick up some new tips and tricks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== A Cure for Romnesia: Site Story Web-Archiving ==&lt;br /&gt;
&lt;br /&gt;
* Harihar Shankar, Research Library, Los Alamos National Laboratory, harihar@lanl.gov&lt;br /&gt;
&lt;br /&gt;
The web changes constantly, erasing both inconvenient facts and&lt;br /&gt;
fictions.  At web-scale, preservation organizations cannot be expected&lt;br /&gt;
to keep up by using traditional crawling, and they already miss many&lt;br /&gt;
important versions.  The cure for this is to capture the interactions&lt;br /&gt;
between real browsers and the server, and push these into an archive&lt;br /&gt;
for safe keeping rather than trying to guess when pages change.&lt;br /&gt;
&lt;br /&gt;
Every time the Apache Web Server sends data to a browser, SiteStory’s&lt;br /&gt;
Apache Module also pushes this data to the SiteStory Web Archive. The&lt;br /&gt;
same version of a resource will not be archived more than once, no&lt;br /&gt;
matter how many times it has been requested.  The resulting archive is&lt;br /&gt;
effectively representative of a server's entire history, although&lt;br /&gt;
versions of resources that are never requested by a browser will also&lt;br /&gt;
never be archived.&lt;br /&gt;
&lt;br /&gt;
In this presentation I will give an overview of SiteStory, an&lt;br /&gt;
Open-Source project written in Java that runs as an application under&lt;br /&gt;
Tomcat 6 or greater. SiteStory’s Apache Module is written in C. I will&lt;br /&gt;
also demonstrate the TimeMap tool that visualizes versions of a&lt;br /&gt;
resource available in the SiteStory archive. The TimeMap tool is a&lt;br /&gt;
Firefox browser extension that plots versions of a resource on a&lt;br /&gt;
SIMILE timeline. Since the tools uses the Memento protocol, it can&lt;br /&gt;
also display versions of resources available in Memento compliant web&lt;br /&gt;
archives and content management systems.&lt;br /&gt;
&lt;br /&gt;
== Practical Relevance Ranking for 10 million books. ==&lt;br /&gt;
 &lt;br /&gt;
* Tom Burton-West, University of Michigan Library, tburtonw@umich.edu&lt;br /&gt;
&lt;br /&gt;
[http://www.hathitrust.org/ HathiTrust Full-text search] indexes the full-text and metadata for over 10 million books.  There are many challenges in tuning relevance ranking for a collection of this size.  This talk will discuss some of the underlying issues, some of our experiments to improve relevance ranking, and our ongoing efforts to develop a principled framework for testing changes to relevance ranking.&lt;br /&gt;
&lt;br /&gt;
Some of the topics covered will include:&lt;br /&gt;
&lt;br /&gt;
* Length normalization for indexing the full-text of book-length documents&lt;br /&gt;
* Indexing granularity for books&lt;br /&gt;
&lt;br /&gt;
*Testing new features in Solr 4.0:&lt;br /&gt;
**New ranking formulas that should work better with book-length documents: BM25 and DFR.&lt;br /&gt;
**Grouping/Field Collapsing.  Can we index 3 billion pages and then use Solr's field collapsing feature to rank books according to the most relevant page(s)?&lt;br /&gt;
**Finite State Automota/Block Trees for storing the in-memory index to the index.  Will this allow us to allow wildcards/truncation despite over 2 billion unique terms per index?&lt;br /&gt;
&lt;br /&gt;
*Relevance testing methodologies:Query log analysis, Click models, Interleaving, A/B testing, and Test collection based evaluation.&lt;br /&gt;
&lt;br /&gt;
*Testing of a new high-performance storage system to be installed in early 2013. We will report on any tests we are able to run prior to conference time.&lt;br /&gt;
&lt;br /&gt;
== Browser/Javascript Integration Testing with Ruby ==&lt;br /&gt;
&lt;br /&gt;
* Jessie Keck, Stanford University, jkeck at stanford dot edu&lt;br /&gt;
&lt;br /&gt;
It's near impossible to build a rich web application without javascript. We have a lot of great patterns to follow, such as progressive enhancement, to make sure our rich web applications are usable, accessible, and testable. However; when javascript is involved the possibility exists that bugs can be introduced that won't get caught by most unit and integration testing frameworks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This is where Watir (pronounced water) comes in.  Watir can be used with popular ruby testing frameworks like RSpec and Capybara.  This talk will show how to use the combination of these tools to write RSpec tests using Watir to spin up an application in a variety of browsers, navigate the application, and make assertions about the page using Capybara.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Tests using Watir are written in ruby but they don't necessarily need to test ruby application. You can test any application that you can point a browser at, so there are a wide variety of potential uses for tests written with Watir.&lt;br /&gt;
&lt;br /&gt;
== Immanentizing the Google ==&lt;br /&gt;
&lt;br /&gt;
* Will Sexton, Duke University Libraries, will.sexton@duke.edu&lt;br /&gt;
* Sean Aery, Duke University Libraries, sean.aery@duke.edu&lt;br /&gt;
&lt;br /&gt;
We're using a &amp;quot;Google-as-a-Service&amp;quot; approach to reduce the complexity and cost of maintaining a structured-data discovery platform for digitized collections and other library-generated content. Our work picks up from a paper in the code4lib Journal by NCSU's Jason Ronallo [1], introducing the idea of embedded schema.org HTML microdata for library digital collections. We've extended our schema.org/RDFa Lite implementation by using Google Site Search to develop a customized interface. In our talk, we'll demonstrate how to set up an instance of Site Search, how to customize the display of results, and how to use the platform's filtering, sorting and other useful functions. We'll also report on our analysis of usage data, and discuss our strategy for scaling the system to support global site search in an upcoming library-wide CMS migration project.&lt;br /&gt;
&lt;br /&gt;
[1] [http://journal.code4lib.org/articles/6400 &amp;quot;HTML5 Microdata and Schema.org&amp;quot;, code4lib #16]&lt;br /&gt;
&lt;br /&gt;
== Evolving Towards a Consortium MARCR Redis Datastore ==&lt;br /&gt;
&lt;br /&gt;
* Jeremy Nelson, Colorado College, jeremy.nelson@coloradocollege.edu&lt;br /&gt;
* Sheila Yeh, University of Denver, Sheila.Yeh@du.edu&lt;br /&gt;
&lt;br /&gt;
The current state of technology in library automation is not keeping pace with the explosive growth in information storage and retrieval system.  The lag costs institutions as well as users’ resource discovery.  To address this problem, we should look into how successfully enterprise such as Craigslist and StackOverflow manage and scale their enormous volume of data.  The key lies in the Redis, a NoSQL open source advanced key-value data structure server.   Therefore, Colorado College and the University of Denver, along with the Colorado Alliance of Research Libraries are exploring and co-developing a MARCR Redis Datastore.  It is a peer-to-peer bibliographic datastore, modeled using the Library of Congress Bibliographic Framework's new Linked Data based MARC 21 replacement, called MARCR (MARC Resources). The structure of MARCR leads itself to an advanced Consortium catalog where a Work is cataloged once and multiple institutions have complete control over their own Instances of the Work, de-duplicating cataloging efforts while supporting real-time resource sharing between the Instances. Control, access, and discovery of records in the proposed MARCR Redis Datastore are provided through lightweight HTML5 responsive apps built with Django, Bootstrap, and KnockoutJS that also integrate with both open-source and commercial discovery products.&lt;br /&gt;
&lt;br /&gt;
Redis offers many advantages for a shared MARCR bibliographic datastore, such as speed, scalability, and ease-of-deployment.  Especially it can support multiple cloud models that benefits institution of various size and capital. We will demonstrate a MVP (Minimal Viable Product) iteration of this MARCR Datastore using the transformed MARC 21 records from Colorado College and the University of Denver into Redis with coordination by Colorado Alliance of Research Libraries.&lt;br /&gt;
&lt;br /&gt;
== Take Your Content and Shove It ==&lt;br /&gt;
 &lt;br /&gt;
* Eric Frierson*, EBSCO Publishing, efrierson@ebscohost.com&lt;br /&gt;
&lt;br /&gt;
Public services librarians have experimented getting out of the library.  For example, the 'embedded librarian' model puts the librarian in class with students, offering help and advice throughout the semester at the point of need.  Digital services have also found their way into virtual classrooms by way of links from the course management system (e.g., Blackboard, Moodle) and the occasional embedded search box that serves as a portal into the library's search solution.&lt;br /&gt;
&lt;br /&gt;
With the release of discovery services and their associated APIs, we can do more.  Rather than linking back to the library, we can take our resources and push them into the learning experience, allowing them to escape the library website silo altogether.  Imagine a professor being able to search library resources and add items to their course website without ever leaving their CMS, or a student adding items to a folder that shows up in their campus dashboard.  What if we could tie the use of library resources to student success in the classroom by leveraging user data from CMS tools?  In this session, I will briefly describe how APIs might make these scenarios possible, but then facilitate a discussion on where else we could shove our resources.  I hope to initiate a few development projects along these lines.&lt;br /&gt;
&lt;br /&gt;
== On Top of Discovery (All Covered with Customizations) ==&lt;br /&gt;
 &lt;br /&gt;
* Scott Hanrath, University of Kansas Librarires, shanrath@ku.edu&lt;br /&gt;
&lt;br /&gt;
On Top of Discovery (All Covered with Customizations)&lt;br /&gt;
&lt;br /&gt;
How and why we've customized the front-end of our vendor library discovery system (Primo) to improve the user experience and integrate with local systems using dollops of JavaScript, a pinch of JSONP, and a smattering of both vendor and simple homegrown APIs.  I'll talk about techniques for adding more AJAX to an already AJAX-intensive interface that you don't fully control (and how a few underlying changes could make it easier) and reflect on our meatball-retention odds in the event that somebody sneezes and the underlying interface changes.&lt;br /&gt;
&lt;br /&gt;
Features to be discussed include improving the display of quasi-FRBRized records in search results through subtracting metadata here and adding metadata there, adding a 'did-you-mean' option in an attempt to steer users toward using Boolean operators in the way the system demands, adding fine-grained event tracking with Google Analytics, and porting existing add-ons like special collection requests, augmented stacks locations, and demand-driven acquisitions requests from our last-generation OPAC.&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2013]]&lt;/div&gt;</summary>
		<author><name>Rshanrath</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_Lightning_Talks_Signup&amp;diff=11427</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=11427"/>
				<updated>2012-02-15T02:31:02Z</updated>
		
		<summary type="html">&lt;p&gt;Rshanrath: &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 -- 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.  - 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>Rshanrath</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_Lightning_Talks_Signup&amp;diff=11103</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=11103"/>
				<updated>2012-02-07T18:00:31Z</updated>
		
		<summary type="html">&lt;p&gt;Rshanrath: &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 / 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&lt;br /&gt;
#&lt;br /&gt;
# akorphan - Heat maps... not just for input analysis&lt;br /&gt;
#&lt;br /&gt;
# &lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
# Cynthia Ng / Processing &amp;amp; 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 -- Zotero and SHERPA/RoMEO API mashup&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;
&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;
#&lt;br /&gt;
#&lt;br /&gt;
# ''Jeremy Nelson'' -- ''Aristotle - Django based Discovery Layer''&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;
[[Category:Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Rshanrath</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_twitter_list&amp;diff=10954</id>
		<title>2012 twitter list</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_twitter_list&amp;diff=10954"/>
				<updated>2012-02-06T17:35:20Z</updated>
		
		<summary type="html">&lt;p&gt;Rshanrath: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Put your twitter handle in here, if you're at Code4Lib 2012 Seattle.  I'll add you to the [https://twitter.com/#!/code4lib/attendees-2012 Attendees 2012 twitter list] for @code4lib when I get a chance. Thanks! -Sean&lt;br /&gt;
&lt;br /&gt;
# Sean Hannan (@MrDys)&lt;br /&gt;
# Cynthia Ng (@TheRealArty)&lt;br /&gt;
# Becky Yoose (@yo_bj)&lt;br /&gt;
# Jason Ronallo (@ronallo)&lt;br /&gt;
# Kåre Fiedler Christiansen (@kaarefc)&lt;br /&gt;
# Joe Montibello (@firstweet)&lt;br /&gt;
# Charlie Morris (@cdmo)&lt;br /&gt;
# Laura Smart (@infod1va)&lt;br /&gt;
# Keri Thompson (@DigiKeri_SIL)&lt;br /&gt;
# Misty De Meo (@mistydemeo)&lt;br /&gt;
# Robert H. McDonald (@mcdonald) - attending virtually&lt;br /&gt;
# Takanori Hayashi (@tzhaya)&lt;br /&gt;
# Jason Casden (@cazzerson)&lt;br /&gt;
# Corey Harper (@chrpr)&lt;br /&gt;
# Heather Pitts (@HLPitts)&lt;br /&gt;
# Alex Wade (@alexwade)&lt;br /&gt;
# Zoe Chao (@zoechao)&lt;br /&gt;
# Joel Richard (@cajunjoel)&lt;br /&gt;
# Mark Matienzo (@anarchivist)&lt;br /&gt;
# Tim Lepczyk (@singlesoliloquy)&lt;br /&gt;
# Scott Hanrath (@rshanrath)&lt;/div&gt;</summary>
		<author><name>Rshanrath</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_preconference_proposals&amp;diff=10333</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=10333"/>
				<updated>2012-01-20T14:52:52Z</updated>
		
		<summary type="html">&lt;p&gt;Rshanrath: /* Interest in Attending */&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;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
*David Uspal (david DOT uspal AT villanova DOT edu)&lt;br /&gt;
*Tammy Allgood Wolf&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;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
*Sam Kome&lt;br /&gt;
*Ray Schwartz&lt;br /&gt;
*Jim Robinson&lt;br /&gt;
*David Bucknum&lt;br /&gt;
*Jean Rainwater&lt;br /&gt;
*Laney McGlohon&lt;br /&gt;
*Joshua Gomez&lt;br /&gt;
*Wayne Schneider&lt;br /&gt;
*Andy Kohler&lt;br /&gt;
*Michael North&lt;br /&gt;
* Tom Keays (keaysht at lemoyne dot edu)&lt;br /&gt;
*Charlie Morris&lt;br /&gt;
*Michael Lindsey&lt;br /&gt;
* Kåre Fiedler Christiansen (morning only)&lt;br /&gt;
* Jørn Thøgersen&lt;br /&gt;
* Michael Poltorak Nielsen&lt;br /&gt;
* Dre&lt;br /&gt;
* Andrew Darby&lt;br /&gt;
* Timothy Clarke (tclarke@muhlenberg.edu)&lt;br /&gt;
* Keith Folsom&lt;br /&gt;
* Rebecca Jones&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;
==== Interest in Attending ====&lt;br /&gt;
*Becky Yoose&lt;br /&gt;
*Tom Johnson&lt;br /&gt;
*Ed Summers&lt;br /&gt;
* bernardo gomez ( bgomez at emory dot edu )&lt;br /&gt;
* William Gunn&lt;br /&gt;
* Jason Ronallo&lt;br /&gt;
* Keri Thompson&lt;br /&gt;
* David Lacy&lt;br /&gt;
* Corey A Harper&lt;br /&gt;
* Matt Phillips (mphillips@law.harvard.edu)&lt;br /&gt;
* Declan Fleming&lt;br /&gt;
* Shaun Ellis (shaune@princeton.edu)&lt;br /&gt;
* Wendy Robertson&lt;br /&gt;
* Joel Richard (richardjm AT si DOT edu)&lt;br /&gt;
* Devon Smith&lt;br /&gt;
* Ron Peterson (ronp@udel.edu0&lt;br /&gt;
* Scott Hanrath (shanrath AT ku DOT 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;
==== Interest in Attending ====&lt;br /&gt;
* &amp;quot;Gabriel Farrell&amp;quot; &amp;lt;gsf24@drexel.edu&amp;gt;&lt;br /&gt;
* &amp;quot;Erik Hetzner&amp;quot; &amp;lt;erik.hetzner AT ucop BORK edu&amp;gt;&lt;br /&gt;
* &amp;quot;Kevin S. Clarke&amp;quot; &amp;lt;ksclarke@gmail&amp;gt;&lt;br /&gt;
* &amp;quot;Michael B. Klein&amp;quot; &amp;lt;mbklein@gmail&amp;gt;&lt;br /&gt;
* Demian Katz (demian DOT katz AT villanova DOT edu)&lt;br /&gt;
* &amp;quot;Mark Mounts&amp;quot; &amp;lt;mark.mounts@dartmouth.edu&amp;gt;&lt;br /&gt;
* Anoop Atre ~ anoop.atre AT mnsu . edu&lt;br /&gt;
* David Isaak &amp;lt;david.isaak@kpchr.org&amp;gt;&lt;br /&gt;
* John Pillans &amp;lt;jpillan@indiana.edu&amp;gt;&lt;br /&gt;
* John Wynstra (john.wynstra@uni.edu)&lt;br /&gt;
* mark a. matienzo (mark at matienzo dot oh are gee)&lt;br /&gt;
* Sepehr Mavedati (sepehr DOT mavedati AT utoronto DOT ca)&lt;br /&gt;
* Anna Headley aheadle1 swarthmore edu&lt;br /&gt;
* Mads Villadsen&lt;br /&gt;
* Jonathan Rochkind&lt;br /&gt;
* Shahin Sahebi (shahin.ezzatsahebi at utoronto dot ca)&lt;br /&gt;
* Naomi Dushay (ndushay at stanford dot edu)&lt;br /&gt;
* Jeremy Nelson&lt;br /&gt;
* Kirk Hess &amp;lt;kirkhess@illinois.edu&amp;gt;&lt;br /&gt;
* Gary Thompson&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 favorite 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:  &amp;lt;del&amp;gt;Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com&amp;lt;/del&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Helper: Cary Gordon, Cherry Hill Company, @highermath / cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
* Patrick Berry (pberry@csuchico.edu)&lt;br /&gt;
* Chris Sharp (csharp@georgialibraries.org)&lt;br /&gt;
* Matt Critchlow (mcritchlow@ucsd.edu)&lt;br /&gt;
* Peter Murray (Peter.Murray@lyrasis.org)&lt;br /&gt;
* Margaret Heller (mheller@dom.edu)&lt;br /&gt;
* Kevin S. Clarke (ksclarke@gmail)&lt;br /&gt;
* Michael B. Klein (mbklein@gmail)&lt;br /&gt;
* Demian Katz (demian DOT katz AT villanova DOT edu)&lt;br /&gt;
* Benjamin Shum (bshum@biblio.org)&lt;br /&gt;
* Sibyl Schaefer (sschaefer@rockarch.org)&lt;br /&gt;
* Tammy Allgood Wolf (tammy.allgood@asu.edu)&lt;br /&gt;
* Chad Nelson (cnelson17 AT gsu DOT edu)&lt;br /&gt;
* Lisa Kurt (lkurt@unr.edu)&lt;br /&gt;
* Matt Phillips (mphillips@law.harvard.edu)&lt;br /&gt;
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)&lt;br /&gt;
* John Wynstra (john.wynstra@uni.edu)&lt;br /&gt;
* Declan Fleming&lt;br /&gt;
* Shaun Ellis (shaune@princeton.edu)&lt;br /&gt;
* Mads Villadsen&lt;br /&gt;
* Kåre Fiedler Christiansen&lt;br /&gt;
* Shahin Sahebi (shahin.ezzatsahebi@utoronto.ca)&lt;br /&gt;
* Devon Smith&lt;br /&gt;
* Jeremy Nelson&lt;br /&gt;
* Ron Peterson (ronp@udel.edu)&lt;br /&gt;
* Gary Thompson&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;
==== Interest in Attending ====&lt;br /&gt;
* bernardo gomez ( bgomez at emory dot edu )&lt;br /&gt;
* Mark Mounts &amp;lt;mark.mounts@dartmouth.edu&amp;gt;&lt;br /&gt;
* Sibyl Schaefer (sschaefer@rockarch.org)&lt;br /&gt;
* John Pillans (jpillan@indiana.edu)&lt;br /&gt;
* Mang Sun (mang.dot sun at rice dot edu)&lt;br /&gt;
* Emily Lynema (emily_lynema at ncsu dot edu)&lt;br /&gt;
* mark a. matienzo (mark at matienzo dot oh are gee)&lt;br /&gt;
* Daniel Lovins (daniel dot lovins at nyu dot edu)&lt;br /&gt;
* Jonathan Rochkind&lt;br /&gt;
* Keith Folsom&lt;br /&gt;
* Kirk Hess &amp;lt;kirkhess@illinois.edu&amp;gt;&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;
==== Interest in Attending ====&lt;br /&gt;
* Francis Kayiwa ( kayiwa@ YouEyeSee dot edu )&lt;br /&gt;
* Carmen Mitchell (carmenmitchell at gmail dot com)&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;
==== Interest in Attending ====&lt;br /&gt;
* Jen Weintraub (jweintraub@library.ucla.edu)&lt;br /&gt;
* Peter Green (pmgreen@princeton.edu)&lt;br /&gt;
* David Isaak (david.isaak@kpchr.org)&lt;br /&gt;
* Alex Rolfe (arolfe@georgefox.edu)&lt;br /&gt;
* mark a. matienzo (mark at matienzo dot oh are gee)&lt;br /&gt;
* Sarah Johnston (johnsts@stolaf.edu)&lt;br /&gt;
* Derek Merleaux (derek@merleaux d0t net)&lt;br /&gt;
* Adam Wead (awead {at} rockhall d.t 0 R G)&lt;br /&gt;
* Tania Fersenheim (tania dot fersenheim at gmail) (I'm only a maybe because I may have a conflict in this time slot)&lt;br /&gt;
&lt;br /&gt;
=== &amp;quot;Geo&amp;quot; ===&lt;br /&gt;
This session will explore, we hope collaboratively, the presentation of objects on maps.  There will be a section on workflow, a section on discovering objects via &amp;quot;geobrowse,&amp;quot; a section discovery of objects via &amp;quot;geosearch,&amp;quot; and an exploration of the discovery and presentation of geo-referenced images (e.g. historic maps). There will be open discussion on other approaches to map-based discovery.  Emphasis will be placed on simplicity of workflow and implementation.  Technologies include: Atom, Django, Solr, and OpenLayers.  &lt;br /&gt;
&lt;br /&gt;
Presenters:  Mike Graves, UNC Chapel Hill, gravm at email dot unc dot edu; Tim Shearer, UNC Chapel Hill, tshearer at email dot unc dot edu&lt;br /&gt;
(please feel free to contact Tim if you are interested in being a co-presenter)&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
* &amp;quot;Gabriel Farrell&amp;quot; &amp;lt;gsf24@drexel.edu&amp;gt;&lt;br /&gt;
* Anoop Atre ~ anoop.atre AT mnsu . edu&lt;br /&gt;
* Chad Nelson (cnelson17 AT gsu DOT edu)&lt;br /&gt;
* Jason Casden (jmcasden AT ncsu DOT edu&lt;br /&gt;
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)&lt;br /&gt;
* Sepehr Mavedati (sepehr DOT mavedati AT utoronto DOT ca)&lt;br /&gt;
* Anna Headley aheadle1 swarthmore edu&lt;br /&gt;
* Michael Poltorak Nielsen&lt;br /&gt;
* Wendy Robertson&lt;br /&gt;
* Joel Richard (richardjm AT si DOT edu)&lt;br /&gt;
* Jonathan Rochkind&lt;br /&gt;
* Naomi Dushay (ndushay at stanford dot edu)&lt;br /&gt;
* Scott Hanrath (shanrath AT ku DOT edu)&lt;br /&gt;
&lt;br /&gt;
== Half-day Evening ==&lt;br /&gt;
&lt;br /&gt;
=== Microsoft Campus Visit ===&lt;br /&gt;
Join us for a trip across Lake Washington to Microsoft Headquarters.  Bus will depart from the conference hotel at 4:15pm on Monday. We will visit the Microsoft Home, the Envisioning Lab, and/or the MS Library.  The we'll head over to Microsoft Research for drinks and appetizers, and you'll see some great demos of some cool new (and free!) technologies coming out of MSR.  Bus will get back to hotel by 9:00pm, plenty of time to hit a pub.  You'll learn about:&lt;br /&gt;
&lt;br /&gt;
1. Layerscape -[http://communities.worldwidetelescope.org/]&lt;br /&gt;
&lt;br /&gt;
2. ChronoZoom - [http://research.microsoft.com/chronozoom/]&lt;br /&gt;
&lt;br /&gt;
3. F# - [http://www.tryfsharp.org]&lt;br /&gt;
&lt;br /&gt;
4. Microsoft Academic Search - [http://academic.research.microsoft.com]&lt;br /&gt;
&lt;br /&gt;
5. Microsoft Audio Visual Indexing System - [http://research.microsoft.com/mavis] &lt;br /&gt;
&lt;br /&gt;
Space is limited, so reserve your seat today  Email Alex at the address below.    &lt;br /&gt;
&lt;br /&gt;
Coordinator: Alex Wade, Microsoft Research, awade at microsoft dot com &lt;br /&gt;
&lt;br /&gt;
Presenters: Behrooz Chitsaz; Rob Fatland; Christophe Poulain; Michael Zyskowski &lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending (Registration closed! We are now at capacity.)   ====&lt;br /&gt;
* Declan Fleming&lt;br /&gt;
* Matt Critchlow&lt;br /&gt;
* Tom Keays (keaysht at lemoyne dot edu)&lt;br /&gt;
* Jason Ronallo&lt;br /&gt;
* mark a. matienzo (mark at matienzo dot oh are gee)&lt;br /&gt;
* Mark Mounts &amp;lt;mark.mounts@dartmouth.edu&amp;gt;&lt;br /&gt;
* Kyle Banerjee &amp;lt;banerjek@uoregon.edu&amp;gt;&lt;br /&gt;
* Evviva Weinraub&lt;br /&gt;
* Emily Lynema &amp;lt;emily_lynema at ncsu dot edu&amp;gt;&lt;br /&gt;
* Jason Casden &amp;lt;jmcasden AT ncsu DOT edu&amp;gt;&lt;br /&gt;
* Daniel Lovins &amp;lt;daniel.lovins@nyu.edu&amp;gt;&lt;br /&gt;
* Cynthia Ng&lt;br /&gt;
* &amp;quot;Gabriel Farrell&amp;quot; &amp;lt;gsf24@drexel.edu&amp;gt;&lt;br /&gt;
* Shaun Ellis (shaune AT princeton DOT edu)&lt;br /&gt;
* Derek Merleaux (derek@merleaux d0t net)&lt;br /&gt;
* Anna Headley&lt;br /&gt;
* Mads Villadsen&lt;br /&gt;
* Kåre Fiedler Christiansen&lt;br /&gt;
* Jørn Thøgersen&lt;br /&gt;
* Michael Poltorak Nielsen&lt;br /&gt;
* Dileshni Jayasinghe&lt;br /&gt;
* Matt Phillips (mphillips@law.harvard.edu)&lt;br /&gt;
* Wendy Robertson&lt;br /&gt;
* Shahin Sahebi&lt;br /&gt;
* Matt Connolly &amp;lt;mjc12 AT cornell dot edu&amp;gt;&lt;br /&gt;
* Jeremy Nelson&lt;br /&gt;
* Naomi Dushay (ndushay at stanford dot edu)&lt;br /&gt;
* Dre&lt;br /&gt;
* Ken Varnum (varnum umich edu)&lt;br /&gt;
* Andrew Darby (agdarby at miami dot edu)&lt;br /&gt;
* REGISTRATION IS NOW CLOSED&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Rshanrath</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_preconference_proposals&amp;diff=10332</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=10332"/>
				<updated>2012-01-20T14:50:05Z</updated>
		
		<summary type="html">&lt;p&gt;Rshanrath: /* Interest in Attending */&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;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
*David Uspal (david DOT uspal AT villanova DOT edu)&lt;br /&gt;
*Tammy Allgood Wolf&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;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
*Sam Kome&lt;br /&gt;
*Ray Schwartz&lt;br /&gt;
*Jim Robinson&lt;br /&gt;
*David Bucknum&lt;br /&gt;
*Jean Rainwater&lt;br /&gt;
*Laney McGlohon&lt;br /&gt;
*Joshua Gomez&lt;br /&gt;
*Wayne Schneider&lt;br /&gt;
*Andy Kohler&lt;br /&gt;
*Michael North&lt;br /&gt;
* Tom Keays (keaysht at lemoyne dot edu)&lt;br /&gt;
*Charlie Morris&lt;br /&gt;
*Michael Lindsey&lt;br /&gt;
* Kåre Fiedler Christiansen (morning only)&lt;br /&gt;
* Jørn Thøgersen&lt;br /&gt;
* Michael Poltorak Nielsen&lt;br /&gt;
* Dre&lt;br /&gt;
* Andrew Darby&lt;br /&gt;
* Timothy Clarke (tclarke@muhlenberg.edu)&lt;br /&gt;
* Keith Folsom&lt;br /&gt;
* Rebecca Jones&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;
==== Interest in Attending ====&lt;br /&gt;
*Becky Yoose&lt;br /&gt;
*Tom Johnson&lt;br /&gt;
*Ed Summers&lt;br /&gt;
* bernardo gomez ( bgomez at emory dot edu )&lt;br /&gt;
* William Gunn&lt;br /&gt;
* Jason Ronallo&lt;br /&gt;
* Keri Thompson&lt;br /&gt;
* David Lacy&lt;br /&gt;
* Corey A Harper&lt;br /&gt;
* Matt Phillips (mphillips@law.harvard.edu)&lt;br /&gt;
* Declan Fleming&lt;br /&gt;
* Shaun Ellis (shaune@princeton.edu)&lt;br /&gt;
* Wendy Robertson&lt;br /&gt;
* Joel Richard (richardjm AT si DOT edu)&lt;br /&gt;
* Devon Smith&lt;br /&gt;
* Ron Peterson (ronp@udel.edu0&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;
==== Interest in Attending ====&lt;br /&gt;
* &amp;quot;Gabriel Farrell&amp;quot; &amp;lt;gsf24@drexel.edu&amp;gt;&lt;br /&gt;
* &amp;quot;Erik Hetzner&amp;quot; &amp;lt;erik.hetzner AT ucop BORK edu&amp;gt;&lt;br /&gt;
* &amp;quot;Kevin S. Clarke&amp;quot; &amp;lt;ksclarke@gmail&amp;gt;&lt;br /&gt;
* &amp;quot;Michael B. Klein&amp;quot; &amp;lt;mbklein@gmail&amp;gt;&lt;br /&gt;
* Demian Katz (demian DOT katz AT villanova DOT edu)&lt;br /&gt;
* &amp;quot;Mark Mounts&amp;quot; &amp;lt;mark.mounts@dartmouth.edu&amp;gt;&lt;br /&gt;
* Anoop Atre ~ anoop.atre AT mnsu . edu&lt;br /&gt;
* David Isaak &amp;lt;david.isaak@kpchr.org&amp;gt;&lt;br /&gt;
* John Pillans &amp;lt;jpillan@indiana.edu&amp;gt;&lt;br /&gt;
* John Wynstra (john.wynstra@uni.edu)&lt;br /&gt;
* mark a. matienzo (mark at matienzo dot oh are gee)&lt;br /&gt;
* Sepehr Mavedati (sepehr DOT mavedati AT utoronto DOT ca)&lt;br /&gt;
* Anna Headley aheadle1 swarthmore edu&lt;br /&gt;
* Mads Villadsen&lt;br /&gt;
* Jonathan Rochkind&lt;br /&gt;
* Shahin Sahebi (shahin.ezzatsahebi at utoronto dot ca)&lt;br /&gt;
* Naomi Dushay (ndushay at stanford dot edu)&lt;br /&gt;
* Jeremy Nelson&lt;br /&gt;
* Kirk Hess &amp;lt;kirkhess@illinois.edu&amp;gt;&lt;br /&gt;
* Gary Thompson&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 favorite 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:  &amp;lt;del&amp;gt;Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com&amp;lt;/del&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Helper: Cary Gordon, Cherry Hill Company, @highermath / cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
* Patrick Berry (pberry@csuchico.edu)&lt;br /&gt;
* Chris Sharp (csharp@georgialibraries.org)&lt;br /&gt;
* Matt Critchlow (mcritchlow@ucsd.edu)&lt;br /&gt;
* Peter Murray (Peter.Murray@lyrasis.org)&lt;br /&gt;
* Margaret Heller (mheller@dom.edu)&lt;br /&gt;
* Kevin S. Clarke (ksclarke@gmail)&lt;br /&gt;
* Michael B. Klein (mbklein@gmail)&lt;br /&gt;
* Demian Katz (demian DOT katz AT villanova DOT edu)&lt;br /&gt;
* Benjamin Shum (bshum@biblio.org)&lt;br /&gt;
* Sibyl Schaefer (sschaefer@rockarch.org)&lt;br /&gt;
* Tammy Allgood Wolf (tammy.allgood@asu.edu)&lt;br /&gt;
* Chad Nelson (cnelson17 AT gsu DOT edu)&lt;br /&gt;
* Lisa Kurt (lkurt@unr.edu)&lt;br /&gt;
* Matt Phillips (mphillips@law.harvard.edu)&lt;br /&gt;
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)&lt;br /&gt;
* John Wynstra (john.wynstra@uni.edu)&lt;br /&gt;
* Declan Fleming&lt;br /&gt;
* Shaun Ellis (shaune@princeton.edu)&lt;br /&gt;
* Mads Villadsen&lt;br /&gt;
* Kåre Fiedler Christiansen&lt;br /&gt;
* Shahin Sahebi (shahin.ezzatsahebi@utoronto.ca)&lt;br /&gt;
* Devon Smith&lt;br /&gt;
* Jeremy Nelson&lt;br /&gt;
* Ron Peterson (ronp@udel.edu)&lt;br /&gt;
* Gary Thompson&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;
==== Interest in Attending ====&lt;br /&gt;
* bernardo gomez ( bgomez at emory dot edu )&lt;br /&gt;
* Mark Mounts &amp;lt;mark.mounts@dartmouth.edu&amp;gt;&lt;br /&gt;
* Sibyl Schaefer (sschaefer@rockarch.org)&lt;br /&gt;
* John Pillans (jpillan@indiana.edu)&lt;br /&gt;
* Mang Sun (mang.dot sun at rice dot edu)&lt;br /&gt;
* Emily Lynema (emily_lynema at ncsu dot edu)&lt;br /&gt;
* mark a. matienzo (mark at matienzo dot oh are gee)&lt;br /&gt;
* Daniel Lovins (daniel dot lovins at nyu dot edu)&lt;br /&gt;
* Jonathan Rochkind&lt;br /&gt;
* Keith Folsom&lt;br /&gt;
* Kirk Hess &amp;lt;kirkhess@illinois.edu&amp;gt;&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;
==== Interest in Attending ====&lt;br /&gt;
* Francis Kayiwa ( kayiwa@ YouEyeSee dot edu )&lt;br /&gt;
* Carmen Mitchell (carmenmitchell at gmail dot com)&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;
==== Interest in Attending ====&lt;br /&gt;
* Jen Weintraub (jweintraub@library.ucla.edu)&lt;br /&gt;
* Peter Green (pmgreen@princeton.edu)&lt;br /&gt;
* David Isaak (david.isaak@kpchr.org)&lt;br /&gt;
* Alex Rolfe (arolfe@georgefox.edu)&lt;br /&gt;
* mark a. matienzo (mark at matienzo dot oh are gee)&lt;br /&gt;
* Sarah Johnston (johnsts@stolaf.edu)&lt;br /&gt;
* Derek Merleaux (derek@merleaux d0t net)&lt;br /&gt;
* Adam Wead (awead {at} rockhall d.t 0 R G)&lt;br /&gt;
* Tania Fersenheim (tania dot fersenheim at gmail) (I'm only a maybe because I may have a conflict in this time slot)&lt;br /&gt;
&lt;br /&gt;
=== &amp;quot;Geo&amp;quot; ===&lt;br /&gt;
This session will explore, we hope collaboratively, the presentation of objects on maps.  There will be a section on workflow, a section on discovering objects via &amp;quot;geobrowse,&amp;quot; a section discovery of objects via &amp;quot;geosearch,&amp;quot; and an exploration of the discovery and presentation of geo-referenced images (e.g. historic maps). There will be open discussion on other approaches to map-based discovery.  Emphasis will be placed on simplicity of workflow and implementation.  Technologies include: Atom, Django, Solr, and OpenLayers.  &lt;br /&gt;
&lt;br /&gt;
Presenters:  Mike Graves, UNC Chapel Hill, gravm at email dot unc dot edu; Tim Shearer, UNC Chapel Hill, tshearer at email dot unc dot edu&lt;br /&gt;
(please feel free to contact Tim if you are interested in being a co-presenter)&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
* &amp;quot;Gabriel Farrell&amp;quot; &amp;lt;gsf24@drexel.edu&amp;gt;&lt;br /&gt;
* Anoop Atre ~ anoop.atre AT mnsu . edu&lt;br /&gt;
* Chad Nelson (cnelson17 AT gsu DOT edu)&lt;br /&gt;
* Jason Casden (jmcasden AT ncsu DOT edu&lt;br /&gt;
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)&lt;br /&gt;
* Sepehr Mavedati (sepehr DOT mavedati AT utoronto DOT ca)&lt;br /&gt;
* Anna Headley aheadle1 swarthmore edu&lt;br /&gt;
* Michael Poltorak Nielsen&lt;br /&gt;
* Wendy Robertson&lt;br /&gt;
* Joel Richard (richardjm AT si DOT edu)&lt;br /&gt;
* Jonathan Rochkind&lt;br /&gt;
* Naomi Dushay (ndushay at stanford dot edu)&lt;br /&gt;
* Scott Hanrath (shanrath AT ku DOT edu)&lt;br /&gt;
&lt;br /&gt;
== Half-day Evening ==&lt;br /&gt;
&lt;br /&gt;
=== Microsoft Campus Visit ===&lt;br /&gt;
Join us for a trip across Lake Washington to Microsoft Headquarters.  Bus will depart from the conference hotel at 4:15pm on Monday. We will visit the Microsoft Home, the Envisioning Lab, and/or the MS Library.  The we'll head over to Microsoft Research for drinks and appetizers, and you'll see some great demos of some cool new (and free!) technologies coming out of MSR.  Bus will get back to hotel by 9:00pm, plenty of time to hit a pub.  You'll learn about:&lt;br /&gt;
&lt;br /&gt;
1. Layerscape -[http://communities.worldwidetelescope.org/]&lt;br /&gt;
&lt;br /&gt;
2. ChronoZoom - [http://research.microsoft.com/chronozoom/]&lt;br /&gt;
&lt;br /&gt;
3. F# - [http://www.tryfsharp.org]&lt;br /&gt;
&lt;br /&gt;
4. Microsoft Academic Search - [http://academic.research.microsoft.com]&lt;br /&gt;
&lt;br /&gt;
5. Microsoft Audio Visual Indexing System - [http://research.microsoft.com/mavis] &lt;br /&gt;
&lt;br /&gt;
Space is limited, so reserve your seat today  Email Alex at the address below.    &lt;br /&gt;
&lt;br /&gt;
Coordinator: Alex Wade, Microsoft Research, awade at microsoft dot com &lt;br /&gt;
&lt;br /&gt;
Presenters: Behrooz Chitsaz; Rob Fatland; Christophe Poulain; Michael Zyskowski &lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending (Registration closed! We are now at capacity.)   ====&lt;br /&gt;
* Declan Fleming&lt;br /&gt;
* Matt Critchlow&lt;br /&gt;
* Tom Keays (keaysht at lemoyne dot edu)&lt;br /&gt;
* Jason Ronallo&lt;br /&gt;
* mark a. matienzo (mark at matienzo dot oh are gee)&lt;br /&gt;
* Mark Mounts &amp;lt;mark.mounts@dartmouth.edu&amp;gt;&lt;br /&gt;
* Kyle Banerjee &amp;lt;banerjek@uoregon.edu&amp;gt;&lt;br /&gt;
* Evviva Weinraub&lt;br /&gt;
* Emily Lynema &amp;lt;emily_lynema at ncsu dot edu&amp;gt;&lt;br /&gt;
* Jason Casden &amp;lt;jmcasden AT ncsu DOT edu&amp;gt;&lt;br /&gt;
* Daniel Lovins &amp;lt;daniel.lovins@nyu.edu&amp;gt;&lt;br /&gt;
* Cynthia Ng&lt;br /&gt;
* &amp;quot;Gabriel Farrell&amp;quot; &amp;lt;gsf24@drexel.edu&amp;gt;&lt;br /&gt;
* Shaun Ellis (shaune AT princeton DOT edu)&lt;br /&gt;
* Derek Merleaux (derek@merleaux d0t net)&lt;br /&gt;
* Anna Headley&lt;br /&gt;
* Mads Villadsen&lt;br /&gt;
* Kåre Fiedler Christiansen&lt;br /&gt;
* Jørn Thøgersen&lt;br /&gt;
* Michael Poltorak Nielsen&lt;br /&gt;
* Dileshni Jayasinghe&lt;br /&gt;
* Matt Phillips (mphillips@law.harvard.edu)&lt;br /&gt;
* Wendy Robertson&lt;br /&gt;
* Shahin Sahebi&lt;br /&gt;
* Matt Connolly &amp;lt;mjc12 AT cornell dot edu&amp;gt;&lt;br /&gt;
* Jeremy Nelson&lt;br /&gt;
* Naomi Dushay (ndushay at stanford dot edu)&lt;br /&gt;
* Dre&lt;br /&gt;
* Ken Varnum (varnum umich edu)&lt;br /&gt;
* Andrew Darby (agdarby at miami dot edu)&lt;br /&gt;
* REGISTRATION IS NOW CLOSED&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Rshanrath</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_preconference_proposals&amp;diff=10331</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=10331"/>
				<updated>2012-01-20T14:49:25Z</updated>
		
		<summary type="html">&lt;p&gt;Rshanrath: /* Interest in Attending */&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;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
*David Uspal (david DOT uspal AT villanova DOT edu)&lt;br /&gt;
*Tammy Allgood Wolf&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;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
*Sam Kome&lt;br /&gt;
*Ray Schwartz&lt;br /&gt;
*Jim Robinson&lt;br /&gt;
*David Bucknum&lt;br /&gt;
*Jean Rainwater&lt;br /&gt;
*Laney McGlohon&lt;br /&gt;
*Joshua Gomez&lt;br /&gt;
*Wayne Schneider&lt;br /&gt;
*Andy Kohler&lt;br /&gt;
*Michael North&lt;br /&gt;
* Tom Keays (keaysht at lemoyne dot edu)&lt;br /&gt;
*Charlie Morris&lt;br /&gt;
*Michael Lindsey&lt;br /&gt;
* Kåre Fiedler Christiansen (morning only)&lt;br /&gt;
* Jørn Thøgersen&lt;br /&gt;
* Michael Poltorak Nielsen&lt;br /&gt;
* Dre&lt;br /&gt;
* Andrew Darby&lt;br /&gt;
* Timothy Clarke (tclarke@muhlenberg.edu)&lt;br /&gt;
* Keith Folsom&lt;br /&gt;
* Rebecca Jones&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;
==== Interest in Attending ====&lt;br /&gt;
*Becky Yoose&lt;br /&gt;
*Tom Johnson&lt;br /&gt;
*Ed Summers&lt;br /&gt;
* bernardo gomez ( bgomez at emory dot edu )&lt;br /&gt;
* William Gunn&lt;br /&gt;
* Jason Ronallo&lt;br /&gt;
* Keri Thompson&lt;br /&gt;
* David Lacy&lt;br /&gt;
* Corey A Harper&lt;br /&gt;
* Matt Phillips (mphillips@law.harvard.edu)&lt;br /&gt;
* Declan Fleming&lt;br /&gt;
* Shaun Ellis (shaune@princeton.edu)&lt;br /&gt;
* Wendy Robertson&lt;br /&gt;
* Joel Richard (richardjm AT si DOT edu)&lt;br /&gt;
* Devon Smith&lt;br /&gt;
* Ron Peterson (ronp@udel.edu0&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;
==== Interest in Attending ====&lt;br /&gt;
* &amp;quot;Gabriel Farrell&amp;quot; &amp;lt;gsf24@drexel.edu&amp;gt;&lt;br /&gt;
* &amp;quot;Erik Hetzner&amp;quot; &amp;lt;erik.hetzner AT ucop BORK edu&amp;gt;&lt;br /&gt;
* &amp;quot;Kevin S. Clarke&amp;quot; &amp;lt;ksclarke@gmail&amp;gt;&lt;br /&gt;
* &amp;quot;Michael B. Klein&amp;quot; &amp;lt;mbklein@gmail&amp;gt;&lt;br /&gt;
* Demian Katz (demian DOT katz AT villanova DOT edu)&lt;br /&gt;
* &amp;quot;Mark Mounts&amp;quot; &amp;lt;mark.mounts@dartmouth.edu&amp;gt;&lt;br /&gt;
* Anoop Atre ~ anoop.atre AT mnsu . edu&lt;br /&gt;
* David Isaak &amp;lt;david.isaak@kpchr.org&amp;gt;&lt;br /&gt;
* John Pillans &amp;lt;jpillan@indiana.edu&amp;gt;&lt;br /&gt;
* John Wynstra (john.wynstra@uni.edu)&lt;br /&gt;
* mark a. matienzo (mark at matienzo dot oh are gee)&lt;br /&gt;
* Sepehr Mavedati (sepehr DOT mavedati AT utoronto DOT ca)&lt;br /&gt;
* Anna Headley aheadle1 swarthmore edu&lt;br /&gt;
* Mads Villadsen&lt;br /&gt;
* Jonathan Rochkind&lt;br /&gt;
* Shahin Sahebi (shahin.ezzatsahebi at utoronto dot ca)&lt;br /&gt;
* Naomi Dushay (ndushay at stanford dot edu)&lt;br /&gt;
* Jeremy Nelson&lt;br /&gt;
* Kirk Hess &amp;lt;kirkhess@illinois.edu&amp;gt;&lt;br /&gt;
* Gary Thompson&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 favorite 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:  &amp;lt;del&amp;gt;Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com&amp;lt;/del&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Helper: Cary Gordon, Cherry Hill Company, @highermath / cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
* Patrick Berry (pberry@csuchico.edu)&lt;br /&gt;
* Chris Sharp (csharp@georgialibraries.org)&lt;br /&gt;
* Matt Critchlow (mcritchlow@ucsd.edu)&lt;br /&gt;
* Peter Murray (Peter.Murray@lyrasis.org)&lt;br /&gt;
* Margaret Heller (mheller@dom.edu)&lt;br /&gt;
* Kevin S. Clarke (ksclarke@gmail)&lt;br /&gt;
* Michael B. Klein (mbklein@gmail)&lt;br /&gt;
* Demian Katz (demian DOT katz AT villanova DOT edu)&lt;br /&gt;
* Benjamin Shum (bshum@biblio.org)&lt;br /&gt;
* Sibyl Schaefer (sschaefer@rockarch.org)&lt;br /&gt;
* Tammy Allgood Wolf (tammy.allgood@asu.edu)&lt;br /&gt;
* Chad Nelson (cnelson17 AT gsu DOT edu)&lt;br /&gt;
* Lisa Kurt (lkurt@unr.edu)&lt;br /&gt;
* Matt Phillips (mphillips@law.harvard.edu)&lt;br /&gt;
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)&lt;br /&gt;
* John Wynstra (john.wynstra@uni.edu)&lt;br /&gt;
* Declan Fleming&lt;br /&gt;
* Shaun Ellis (shaune@princeton.edu)&lt;br /&gt;
* Mads Villadsen&lt;br /&gt;
* Kåre Fiedler Christiansen&lt;br /&gt;
* Shahin Sahebi (shahin.ezzatsahebi@utoronto.ca)&lt;br /&gt;
* Devon Smith&lt;br /&gt;
* Jeremy Nelson&lt;br /&gt;
* Ron Peterson (ronp@udel.edu)&lt;br /&gt;
* Gary Thompson&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;
==== Interest in Attending ====&lt;br /&gt;
* bernardo gomez ( bgomez at emory dot edu )&lt;br /&gt;
* Mark Mounts &amp;lt;mark.mounts@dartmouth.edu&amp;gt;&lt;br /&gt;
* Sibyl Schaefer (sschaefer@rockarch.org)&lt;br /&gt;
* John Pillans (jpillan@indiana.edu)&lt;br /&gt;
* Mang Sun (mang.dot sun at rice dot edu)&lt;br /&gt;
* Emily Lynema (emily_lynema at ncsu dot edu)&lt;br /&gt;
* mark a. matienzo (mark at matienzo dot oh are gee)&lt;br /&gt;
* Daniel Lovins (daniel dot lovins at nyu dot edu)&lt;br /&gt;
* Jonathan Rochkind&lt;br /&gt;
* Keith Folsom&lt;br /&gt;
* Kirk Hess &amp;lt;kirkhess@illinois.edu&amp;gt;&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;
==== Interest in Attending ====&lt;br /&gt;
* Francis Kayiwa ( kayiwa@ YouEyeSee dot edu )&lt;br /&gt;
* Carmen Mitchell (carmenmitchell at gmail dot com)&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;
==== Interest in Attending ====&lt;br /&gt;
* Jen Weintraub (jweintraub@library.ucla.edu)&lt;br /&gt;
* Peter Green (pmgreen@princeton.edu)&lt;br /&gt;
* David Isaak (david.isaak@kpchr.org)&lt;br /&gt;
* Alex Rolfe (arolfe@georgefox.edu)&lt;br /&gt;
* mark a. matienzo (mark at matienzo dot oh are gee)&lt;br /&gt;
* Sarah Johnston (johnsts@stolaf.edu)&lt;br /&gt;
* Derek Merleaux (derek@merleaux d0t net)&lt;br /&gt;
* Adam Wead (awead {at} rockhall d.t 0 R G)&lt;br /&gt;
* Tania Fersenheim (tania dot fersenheim at gmail) (I'm only a maybe because I may have a conflict in this time slot)&lt;br /&gt;
&lt;br /&gt;
=== &amp;quot;Geo&amp;quot; ===&lt;br /&gt;
This session will explore, we hope collaboratively, the presentation of objects on maps.  There will be a section on workflow, a section on discovering objects via &amp;quot;geobrowse,&amp;quot; a section discovery of objects via &amp;quot;geosearch,&amp;quot; and an exploration of the discovery and presentation of geo-referenced images (e.g. historic maps). There will be open discussion on other approaches to map-based discovery.  Emphasis will be placed on simplicity of workflow and implementation.  Technologies include: Atom, Django, Solr, and OpenLayers.  &lt;br /&gt;
&lt;br /&gt;
Presenters:  Mike Graves, UNC Chapel Hill, gravm at email dot unc dot edu; Tim Shearer, UNC Chapel Hill, tshearer at email dot unc dot edu&lt;br /&gt;
(please feel free to contact Tim if you are interested in being a co-presenter)&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
* &amp;quot;Gabriel Farrell&amp;quot; &amp;lt;gsf24@drexel.edu&amp;gt;&lt;br /&gt;
* Anoop Atre ~ anoop.atre AT mnsu . edu&lt;br /&gt;
* Chad Nelson (cnelson17 AT gsu DOT edu)&lt;br /&gt;
* Jason Casden (jmcasden AT ncsu DOT edu&lt;br /&gt;
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)&lt;br /&gt;
* Sepehr Mavedati (sepehr DOT mavedati AT utoronto DOT ca)&lt;br /&gt;
* Anna Headley aheadle1 swarthmore edu&lt;br /&gt;
* Michael Poltorak Nielsen&lt;br /&gt;
* Wendy Robertson&lt;br /&gt;
* Joel Richard (richardjm AT si DOT edu)&lt;br /&gt;
* Jonathan Rochkind&lt;br /&gt;
* Naomi Dushay (ndushay at stanford dot edu)&lt;br /&gt;
* Scott Hanrath (shanrath AT ku.edu)&lt;br /&gt;
&lt;br /&gt;
== Half-day Evening ==&lt;br /&gt;
&lt;br /&gt;
=== Microsoft Campus Visit ===&lt;br /&gt;
Join us for a trip across Lake Washington to Microsoft Headquarters.  Bus will depart from the conference hotel at 4:15pm on Monday. We will visit the Microsoft Home, the Envisioning Lab, and/or the MS Library.  The we'll head over to Microsoft Research for drinks and appetizers, and you'll see some great demos of some cool new (and free!) technologies coming out of MSR.  Bus will get back to hotel by 9:00pm, plenty of time to hit a pub.  You'll learn about:&lt;br /&gt;
&lt;br /&gt;
1. Layerscape -[http://communities.worldwidetelescope.org/]&lt;br /&gt;
&lt;br /&gt;
2. ChronoZoom - [http://research.microsoft.com/chronozoom/]&lt;br /&gt;
&lt;br /&gt;
3. F# - [http://www.tryfsharp.org]&lt;br /&gt;
&lt;br /&gt;
4. Microsoft Academic Search - [http://academic.research.microsoft.com]&lt;br /&gt;
&lt;br /&gt;
5. Microsoft Audio Visual Indexing System - [http://research.microsoft.com/mavis] &lt;br /&gt;
&lt;br /&gt;
Space is limited, so reserve your seat today  Email Alex at the address below.    &lt;br /&gt;
&lt;br /&gt;
Coordinator: Alex Wade, Microsoft Research, awade at microsoft dot com &lt;br /&gt;
&lt;br /&gt;
Presenters: Behrooz Chitsaz; Rob Fatland; Christophe Poulain; Michael Zyskowski &lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending (Registration closed! We are now at capacity.)   ====&lt;br /&gt;
* Declan Fleming&lt;br /&gt;
* Matt Critchlow&lt;br /&gt;
* Tom Keays (keaysht at lemoyne dot edu)&lt;br /&gt;
* Jason Ronallo&lt;br /&gt;
* mark a. matienzo (mark at matienzo dot oh are gee)&lt;br /&gt;
* Mark Mounts &amp;lt;mark.mounts@dartmouth.edu&amp;gt;&lt;br /&gt;
* Kyle Banerjee &amp;lt;banerjek@uoregon.edu&amp;gt;&lt;br /&gt;
* Evviva Weinraub&lt;br /&gt;
* Emily Lynema &amp;lt;emily_lynema at ncsu dot edu&amp;gt;&lt;br /&gt;
* Jason Casden &amp;lt;jmcasden AT ncsu DOT edu&amp;gt;&lt;br /&gt;
* Daniel Lovins &amp;lt;daniel.lovins@nyu.edu&amp;gt;&lt;br /&gt;
* Cynthia Ng&lt;br /&gt;
* &amp;quot;Gabriel Farrell&amp;quot; &amp;lt;gsf24@drexel.edu&amp;gt;&lt;br /&gt;
* Shaun Ellis (shaune AT princeton DOT edu)&lt;br /&gt;
* Derek Merleaux (derek@merleaux d0t net)&lt;br /&gt;
* Anna Headley&lt;br /&gt;
* Mads Villadsen&lt;br /&gt;
* Kåre Fiedler Christiansen&lt;br /&gt;
* Jørn Thøgersen&lt;br /&gt;
* Michael Poltorak Nielsen&lt;br /&gt;
* Dileshni Jayasinghe&lt;br /&gt;
* Matt Phillips (mphillips@law.harvard.edu)&lt;br /&gt;
* Wendy Robertson&lt;br /&gt;
* Shahin Sahebi&lt;br /&gt;
* Matt Connolly &amp;lt;mjc12 AT cornell dot edu&amp;gt;&lt;br /&gt;
* Jeremy Nelson&lt;br /&gt;
* Naomi Dushay (ndushay at stanford dot edu)&lt;br /&gt;
* Dre&lt;br /&gt;
* Ken Varnum (varnum umich edu)&lt;br /&gt;
* Andrew Darby (agdarby at miami dot edu)&lt;br /&gt;
* REGISTRATION IS NOW CLOSED&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Rshanrath</name></author>	</entry>

	</feed>