Code4Lib - User contributions [en]

2015 Preconference Proposals

2014-12-08T18:28:16Z

Bretdavidson: /* Fail4Lib 2015 */

== Preconference Schedule (draft) ==

Session titles in Italics means they have not been confirmed yet by presenters/workshop leaders.

This is a draft, and there may be some room switching when registration opens. Rooms will be confirmed the week before Code4Lib.

{| class="wikitable sortable"
|-
! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1:30 PM - 4:30 PM)
|-
| '''Parlor A (30''') || Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable (Needs: projector, internet connection, and power strips) || Intro to Git & possibly beyond (Needs: projector/screen)
|-
| '''Parlor B (30)''' || Code Retreat (Needs whiteboard, dry-erase markers, projector) || Code Retreat (Needs whiteboard, dry-erase markers, projector)
|-
| '''Parlor C (30)''' || code4lib/Write The Docs barcamp (Needs: projector/screen, flipboard/whiteboard, power sources for laptops) || code4lib/Write The Docs barcamp
|-
| '''Grand Ballroom''' I (320) || CANCELLED: [UXtravaganza] || Presentations workshop (Needs: projector/screen)
|-
| '''Grand Ballroom''' II (200) || Visualizing Library Data (Needs: projector) || DPLA API Workshop (Bringing their own projector)
|-
| '''Galleria I (35)''' || Coding Custom Solutions for Every Department in the Library with File Analyzer (Needs PC laptop projection, monitor, internet access/wifi, attendees bring laptops) || Fail4Lib 2015 (Needs: projector/screen; Requested: Conference table seating, limit 20 attendants)
|-
| '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (Needs: internet/wifi, overhead projection) || CollectionSpace: Getting it up and running at your museum (Needs: Projector)
|-
| '''Galleria III (35)''' || Replace yourself with a painfully complex bash script...or try Ansible (Confirmed with Chad; No given setup needs yet) || Intro to Docker
|-
| '''Studio (35)''' || Linked Data Workshop (Bringing their own projector) || Dive into Hydra (Needs: projector/screen; Requests: classroom style seating)
|-
| '''Directors (35)''' || Code4Arc (Needs: projector) || Code4Arc (Needs: projector)
|-
| '''Council (45)''' || Delivering and Preserving GIS Data (Projector, Video connector for MacBook Pro, wifi, power outlets) || A hands-on introduction to GeoBlacklight (Needs: projector, outlets; Requests: list of attendees)
|}

== Instructions ==
Thank you for considering proposing a pre-conference! Here are a few details:

* We will be taking pre-conference proposals until '''November 7, 2014'''
* If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu
* Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]
* If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)
* If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu
* '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions
* Please use the template for proposals provided in the pre-formatted block below

== Pre-conferences ==

===MORNING:===

=== Delivering and Preserving GIS Data ===

'''Half Day [Morning]'''

* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu

We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# [[User:Ssimpkin|Sarah Simpkin]]
# Vicky Steeves
# Andrew Battista
# Peggy Griesinger
#
#
#
#
#
#

=== A hands-on introduction to GeoBlacklight ===

'''Half Day [Afternoon]'''

* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu

GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop "Delivering and Preserving GIS Data".

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# [[User:Ssimpkin|Sarah Simpkin]]
# Vicky Steeves
# Andrew Battista
# Peggy Griesinger
#
#
#
#
#
#

===RailsBridge: Intro to programming in Ruby on Rails===

'''"Half-Day" [morning]'''

* Contact Carolyn Cole, Penn State University, carolyn@psu.edu
* Laney McGlohon, Stanford University, laneymcg@stanford.edu
* Additional instructors welcome

Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.

RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Maura Carbone
#Vicky Steeves
# Peggy Griesinger
# Mike Price
# Jean Rainwater
# Coral Sheldon-Hess
# Margaret Heller
# Bohyun Kim
# Mark Jarrell
#

=== Replace yourself with a painfully complex bash script...or try Ansible ===

'''Half Day [Morning]'''

* Chad Nelson, chad dot nelson @ lyrasis dot org
* Blake Carver, Blake dot carver @lyrasis dot org

Abstract:

[http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
# Ray Schwartz
# Coral Sheldon-Hess
# Kevin S. Clarke
# Joshua Gomez
# Charlie Morris
# Andy Mardesich
# Anna Headley
# Chelsea Lobdell
# Shaun Ellis
# Mark Mounts
# Chris Sharp

=== Intro to Docker ===

'''Half Day [Whenever]'''

* John Fink, McMaster University, john dot fink at gmail dot com
* Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com

Abstract:

[http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.

''Interested in Attending''

# Jim Hahn
# Joshua Gomez
# Bobbi Fox
# Ray Schwartz
# Megan Kudzia
# Coral Sheldon-Hess (pleeeeaaase put this in a different slot from Ansible!)
# Cary Gordon (uses Docker in production on AWS)
# Eric Phetteplace
# Esther Verreau
# Charlie Morris
# Anna Headley (voting for afternoon, compliments ansible)
# Shaun Ellis
# Mark Mounts
# Matt Critchlow
# Ray Henry

=== Code Retreat ===

'''Full Day'''

* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu
* Additional facilitators welcome; Especially if you have CodeRetreat experience.

Abstract:

"Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.
By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.
Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time." [http://coderetreat.org/about About Code Retreat]

''Interested in Attending''

# Mike Giarlo
# Charlie Morris
# Devon Smith
# Barbara Hui
# Carol Bean
# Matt Connolly
# James Van Mil
#
#
#

=== Presentations workshop ===

'''"Half Day [Afternoon]"''' (but could be expanded based on interest)

* Chris Beer, Stanford University, cabeer@stanford.edu
* Additional facilitators welcome.

This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#Vicky Steeves
#
#
#
#
#
#
#
#
#

=== Dive into Hydra ===

'''"Half Day [Afternoon]"'''

* Justin Coyne, Data Curation Experts, justin@curationexperts.com
* Bess Sadler, Stanford University, bess@stanford.edu

Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend "RailsBridge" prior to this workshop.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Maura Carbone
# Peggy Griesinger
# Mike Price
# Jean Rainwater
# Sara Amato
#
#
#
#
#

=== code4lib/Write The Docs barcamp ===

'''"Full Day"''', with options for jumping in for half a day

* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu
* Write the Docs contacts: TBA

Abstract

Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization.

Remember, like metadata, documentation is a love note to the future.

More information about Write the Docs at http://conf.writethedocs.org/

There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

'''Full day'''
# Emily Lynema
#
#
#
#
#
#
#
#
#

'''Morning'''
# Ranti Junus
# Mita Williams
# Whitni Watkins
#
#
#
#
#
#
#

'''Afternoon'''
# Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon.
# Kevin S. Clarke
# Chris Sharp
#
#
#
#
#
#
#

=== Linked Data Workshop ===

'''"Half Day [morning]"'''

* Karen Estlund, University of Oregon, kestlund@uoregon.edu
* Tom Johnson, DPLA, tom@dp.la

Abstract:

Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Logan Cox
# Ray Schwartz
# Chris Hallberg
# Derek Merleaux
# Steven Anderson
# Eben English
# Mark Mounts
# Heather Pitts
# Andrew Woods
# Carol Bean

=== Code4Arc ===

'''"Full Day"''' (with options for half day participation)

* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com
* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org
* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com

Abstract:

What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how?

Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.

The schedule may include the following:

* Panel type conversations about the State of Art in Archives
* Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed
* Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)

Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with.

When signing up, please indicate if you are an end-user or a developer.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Laney McGlohon - developer
# Shaun Ellis
#
#
#
#
#
#
#
#

=== Fail4Lib 2015 ===

'''Half Day [TBD, probably afternoon]'''

* Andreas Orphanides, akorphan (at) ncsu.edu
* Jason Casden, jmcasden (at) ncsu.edu

Abstract:

Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.

This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)

The schedule may include the following:

* Case studies. Avoid our own mistakes by bearing witness to the failures of others.
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.
* Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.

''Interested in attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Ray Schwartz
# Charlie Morris
# Emily Lynema
# Bret Davidson
#
#
#
#
#
#

=== Coding Custom Solutions for Every Department in the Library with File Analyzer ===

'''"Half Day [Morning]"'''

* Terry Brady, Georgetown University Library, twb27@georgetown.edu

Abstract

The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.

* Analyzing Marc Records for the Cataloging department
* Transferring ILS invoices for the University Account System for the Acquisitions department
* Delivering patron fines to the Bursar’s office for the Access Service department
* Summarizing student worker timesheet data for the Finance department
* Validating counter compliant reports for the Electronic Resources department
* Preparing ingest packages for the Digital Services department
* Validating checksums for the Preservation department

This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.

The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Megan Kudzia
#
#
#
#
#
#
#
#
#

=== Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===

'''Half Day [Whenever]'''

* Karen A. Coombs, OCLC, coombsk@oclc.org

Abstract
Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.

We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Peggy Griesinger
# Ray Schwartz
# Josh Wilson
#
#
#
#
#
#
#

=== CANCELLED: ''UXtravaganza'' ===
'''"Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]"'''

* William Hicks, University of North Texas, William.hicks@unt.edu
* Volunteers?

Abstract

I’m envisioning a 1/2 of full day for front-end developers, content strategy people, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state of current research, and play with each other’s sites. A half day seems doable, but if there’s significant enough interest we could push for a full? Here are a few of the things I think might be interesting to see happen:

* '''Analytics Share-fest:''' A few volunteers demonstrate data about their websites, catalogs, archival/digital collections. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etc. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeing.

* '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation. Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc.

* '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an [http://labup.org Open Device Lab]. We have about a dozen devices now of varying sizes, OS, OS Versions, + Google Glass. I’ll bring the devices, you can bring yours, and assuming we can get the wifi up and running we can test our sites/services with our big sausage fingers rather than pretending to do so through emulators and the one or two devices we each usually have on hand. If anyone is game they can do a tutorial on Browser-based Inspector Tools, Browser-Cams, or other testing services.

* '''The Eye’s Have It.''' The UNT Libraries is also in the process of acquiring an eye tracker and software for usability and other gaze-based research studies. We’ll take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before the conference. Assuming we can get our act together learning the device and can get past the technical hurdles of setting it up at the pre-conference, we could try to do some live demos on each other’s sites; i.e. You nominate a site/service, someone in the audience volunteers to wear the device, and we all watch them struggle do the tasks you request on a projector. Rinse. Lather. Repeat. It would hardly be scientific, but it sure would be fun. As a backup, if we have some sites nominated beforehand, I can run a few students at my library through some tasks here and we can show off the results to the crowd.

For those of you wanting to attend and help out, I’d really like to see some discussion on typography, writing for the web, “dealing with business/administrative requirements from on-high", maybe do some prototyping exercises, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running a usability test, that would be rad. But we need you to step up and steer part of the time for most of this to work, so if you are interested in some aspect, and especially if you want to volunteer to lead a bit of the time, contact me.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your
name (but not email address, etc.) here

# Ray Schwartz
# Andy Mardesich
# Chelsea Lobdell
# Eben English (1/2 day)
# Shaun Ellis (as attendee or volunteer)
# Whitni Watkins (as attendee or volunteer)
#
#
#
#

=== Intro to Git & possibly beyond ===

'''Half Day [Whenever]'''

* Erin Fahy, Stanford University, efahy@stanford.edu
* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu

We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:

* What is a Distributed Version Control System?
* What's the difference between Git and Github.com?
* How to initialize new Git projects locally and on a remote server/Github
* Cloning/Forking existing projects and keeping up to date
* The wonderful world of Git branches
* Interactive rebasing
* Contributing code to existing projects & what pull requests are
* How to handle merge conflicts
* Overview of workflows and branch best practices
* (time allowing) Advanced git: pre/post hooks, submodules, anything else?

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Jeannie Graham
# Derek Merleaux
# Laurie Reeves
#
#
#
#
#
#
#

=== Visualizing Library Data ===

'''"Half Day [Morning||Afternoon]"'''

* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs

Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Ashley Blewer!
# Bobbi Fox
# Ray Schwartz
# Ranti Junus
# Eric Phetteplace
# Joshua Gomez
# Charlie Morris
# Andy Mardesich
# Tao Zhao
# Chris Hallberg
# Derek Merleaux
# Bohyun Kim
# Mark Jarrell
# Eben English
# Shaun Ellis
# Sarah Simpkin
# Mark Mounts
# Kathryn Stine
# Steve Meyer
# Matt Critchlow
# Andrew Pasterfield
# Ray Henry
# Bret Davidson

=== CollectionSpace: Getting it up and running at your museum ===

'''Half Day [Afternoon]'''

* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org
* TBD

This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org

Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.

''Interested in Attending''
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Terry Brady
#
#
#
#
#
#
#
#
#

=== DPLA API Workshop: ===

'''Half Day [Afternoon]'''

* Audrey Altman, DPLA
* Mark Breedlove, DPLA
* Mark Matienzo, DPLA
* Tom Johnson, DPLA

The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Ranti Junus
# Jean Rainwater
# Mita Williams
# Margaret Heller
# Bohyun Kim
# Steven Anderson
# Shaun Ellis
# Sarah Simpkin
# Mark Jarrell
# Heather Pitts
# Kathryn Stine
# Andrew Woods

[[Category:Code4Lib2015]]

2015 Preconference Proposals

2014-12-08T18:27:26Z

Bretdavidson: /* Visualizing Library Data */

== Preconference Schedule (draft) ==

Session titles in Italics means they have not been confirmed yet by presenters/workshop leaders.

This is a draft, and there may be some room switching when registration opens. Rooms will be confirmed the week before Code4Lib.

{| class="wikitable sortable"
|-
! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1:30 PM - 4:30 PM)
|-
| '''Parlor A (30''') || Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable (Needs: projector, internet connection, and power strips) || Intro to Git & possibly beyond (Needs: projector/screen)
|-
| '''Parlor B (30)''' || Code Retreat (Needs whiteboard, dry-erase markers, projector) || Code Retreat (Needs whiteboard, dry-erase markers, projector)
|-
| '''Parlor C (30)''' || code4lib/Write The Docs barcamp (Needs: projector/screen, flipboard/whiteboard, power sources for laptops) || code4lib/Write The Docs barcamp
|-
| '''Grand Ballroom''' I (320) || CANCELLED: [UXtravaganza] || Presentations workshop (Needs: projector/screen)
|-
| '''Grand Ballroom''' II (200) || Visualizing Library Data (Needs: projector) || DPLA API Workshop (Bringing their own projector)
|-
| '''Galleria I (35)''' || Coding Custom Solutions for Every Department in the Library with File Analyzer (Needs PC laptop projection, monitor, internet access/wifi, attendees bring laptops) || Fail4Lib 2015 (Needs: projector/screen; Requested: Conference table seating, limit 20 attendants)
|-
| '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (Needs: internet/wifi, overhead projection) || CollectionSpace: Getting it up and running at your museum (Needs: Projector)
|-
| '''Galleria III (35)''' || Replace yourself with a painfully complex bash script...or try Ansible (Confirmed with Chad; No given setup needs yet) || Intro to Docker
|-
| '''Studio (35)''' || Linked Data Workshop (Bringing their own projector) || Dive into Hydra (Needs: projector/screen; Requests: classroom style seating)
|-
| '''Directors (35)''' || Code4Arc (Needs: projector) || Code4Arc (Needs: projector)
|-
| '''Council (45)''' || Delivering and Preserving GIS Data (Projector, Video connector for MacBook Pro, wifi, power outlets) || A hands-on introduction to GeoBlacklight (Needs: projector, outlets; Requests: list of attendees)
|}

== Instructions ==
Thank you for considering proposing a pre-conference! Here are a few details:

* We will be taking pre-conference proposals until '''November 7, 2014'''
* If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu
* Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]
* If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)
* If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu
* '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions
* Please use the template for proposals provided in the pre-formatted block below

== Pre-conferences ==

===MORNING:===

=== Delivering and Preserving GIS Data ===

'''Half Day [Morning]'''

* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu

We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# [[User:Ssimpkin|Sarah Simpkin]]
# Vicky Steeves
# Andrew Battista
# Peggy Griesinger
#
#
#
#
#
#

=== A hands-on introduction to GeoBlacklight ===

'''Half Day [Afternoon]'''

* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu

GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop "Delivering and Preserving GIS Data".

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# [[User:Ssimpkin|Sarah Simpkin]]
# Vicky Steeves
# Andrew Battista
# Peggy Griesinger
#
#
#
#
#
#

===RailsBridge: Intro to programming in Ruby on Rails===

'''"Half-Day" [morning]'''

* Contact Carolyn Cole, Penn State University, carolyn@psu.edu
* Laney McGlohon, Stanford University, laneymcg@stanford.edu
* Additional instructors welcome

Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.

RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Maura Carbone
#Vicky Steeves
# Peggy Griesinger
# Mike Price
# Jean Rainwater
# Coral Sheldon-Hess
# Margaret Heller
# Bohyun Kim
# Mark Jarrell
#

=== Replace yourself with a painfully complex bash script...or try Ansible ===

'''Half Day [Morning]'''

* Chad Nelson, chad dot nelson @ lyrasis dot org
* Blake Carver, Blake dot carver @lyrasis dot org

Abstract:

[http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
# Ray Schwartz
# Coral Sheldon-Hess
# Kevin S. Clarke
# Joshua Gomez
# Charlie Morris
# Andy Mardesich
# Anna Headley
# Chelsea Lobdell
# Shaun Ellis
# Mark Mounts
# Chris Sharp

=== Intro to Docker ===

'''Half Day [Whenever]'''

* John Fink, McMaster University, john dot fink at gmail dot com
* Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com

Abstract:

[http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.

''Interested in Attending''

# Jim Hahn
# Joshua Gomez
# Bobbi Fox
# Ray Schwartz
# Megan Kudzia
# Coral Sheldon-Hess (pleeeeaaase put this in a different slot from Ansible!)
# Cary Gordon (uses Docker in production on AWS)
# Eric Phetteplace
# Esther Verreau
# Charlie Morris
# Anna Headley (voting for afternoon, compliments ansible)
# Shaun Ellis
# Mark Mounts
# Matt Critchlow
# Ray Henry

=== Code Retreat ===

'''Full Day'''

* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu
* Additional facilitators welcome; Especially if you have CodeRetreat experience.

Abstract:

"Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.
By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.
Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time." [http://coderetreat.org/about About Code Retreat]

''Interested in Attending''

# Mike Giarlo
# Charlie Morris
# Devon Smith
# Barbara Hui
# Carol Bean
# Matt Connolly
# James Van Mil
#
#
#

=== Presentations workshop ===

'''"Half Day [Afternoon]"''' (but could be expanded based on interest)

* Chris Beer, Stanford University, cabeer@stanford.edu
* Additional facilitators welcome.

This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#Vicky Steeves
#
#
#
#
#
#
#
#
#

=== Dive into Hydra ===

'''"Half Day [Afternoon]"'''

* Justin Coyne, Data Curation Experts, justin@curationexperts.com
* Bess Sadler, Stanford University, bess@stanford.edu

Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend "RailsBridge" prior to this workshop.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Maura Carbone
# Peggy Griesinger
# Mike Price
# Jean Rainwater
# Sara Amato
#
#
#
#
#

=== code4lib/Write The Docs barcamp ===

'''"Full Day"''', with options for jumping in for half a day

* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu
* Write the Docs contacts: TBA

Abstract

Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization.

Remember, like metadata, documentation is a love note to the future.

More information about Write the Docs at http://conf.writethedocs.org/

There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

'''Full day'''
# Emily Lynema
#
#
#
#
#
#
#
#
#

'''Morning'''
# Ranti Junus
# Mita Williams
# Whitni Watkins
#
#
#
#
#
#
#

'''Afternoon'''
# Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon.
# Kevin S. Clarke
# Chris Sharp
#
#
#
#
#
#
#

=== Linked Data Workshop ===

'''"Half Day [morning]"'''

* Karen Estlund, University of Oregon, kestlund@uoregon.edu
* Tom Johnson, DPLA, tom@dp.la

Abstract:

Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Logan Cox
# Ray Schwartz
# Chris Hallberg
# Derek Merleaux
# Steven Anderson
# Eben English
# Mark Mounts
# Heather Pitts
# Andrew Woods
# Carol Bean

=== Code4Arc ===

'''"Full Day"''' (with options for half day participation)

* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com
* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org
* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com

Abstract:

What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how?

Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.

The schedule may include the following:

* Panel type conversations about the State of Art in Archives
* Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed
* Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)

Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with.

When signing up, please indicate if you are an end-user or a developer.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Laney McGlohon - developer
# Shaun Ellis
#
#
#
#
#
#
#
#

=== Fail4Lib 2015 ===

'''Half Day [TBD, probably afternoon]'''

* Andreas Orphanides, akorphan (at) ncsu.edu
* Jason Casden, jmcasden (at) ncsu.edu

Abstract:

Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.

This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)

The schedule may include the following:

* Case studies. Avoid our own mistakes by bearing witness to the failures of others.
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.
* Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.

''Interested in attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Ray Schwartz
# Charlie Morris
# Emily Lynema
#
#
#
#
#
#
#

=== Coding Custom Solutions for Every Department in the Library with File Analyzer ===

'''"Half Day [Morning]"'''

* Terry Brady, Georgetown University Library, twb27@georgetown.edu

Abstract

The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.

* Analyzing Marc Records for the Cataloging department
* Transferring ILS invoices for the University Account System for the Acquisitions department
* Delivering patron fines to the Bursar’s office for the Access Service department
* Summarizing student worker timesheet data for the Finance department
* Validating counter compliant reports for the Electronic Resources department
* Preparing ingest packages for the Digital Services department
* Validating checksums for the Preservation department

This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.

The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Megan Kudzia
#
#
#
#
#
#
#
#
#

=== Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===

'''Half Day [Whenever]'''

* Karen A. Coombs, OCLC, coombsk@oclc.org

Abstract
Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.

We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Peggy Griesinger
# Ray Schwartz
# Josh Wilson
#
#
#
#
#
#
#

=== CANCELLED: ''UXtravaganza'' ===
'''"Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]"'''

* William Hicks, University of North Texas, William.hicks@unt.edu
* Volunteers?

Abstract

I’m envisioning a 1/2 of full day for front-end developers, content strategy people, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state of current research, and play with each other’s sites. A half day seems doable, but if there’s significant enough interest we could push for a full? Here are a few of the things I think might be interesting to see happen:

* '''Analytics Share-fest:''' A few volunteers demonstrate data about their websites, catalogs, archival/digital collections. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etc. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeing.

* '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation. Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc.

* '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an [http://labup.org Open Device Lab]. We have about a dozen devices now of varying sizes, OS, OS Versions, + Google Glass. I’ll bring the devices, you can bring yours, and assuming we can get the wifi up and running we can test our sites/services with our big sausage fingers rather than pretending to do so through emulators and the one or two devices we each usually have on hand. If anyone is game they can do a tutorial on Browser-based Inspector Tools, Browser-Cams, or other testing services.

* '''The Eye’s Have It.''' The UNT Libraries is also in the process of acquiring an eye tracker and software for usability and other gaze-based research studies. We’ll take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before the conference. Assuming we can get our act together learning the device and can get past the technical hurdles of setting it up at the pre-conference, we could try to do some live demos on each other’s sites; i.e. You nominate a site/service, someone in the audience volunteers to wear the device, and we all watch them struggle do the tasks you request on a projector. Rinse. Lather. Repeat. It would hardly be scientific, but it sure would be fun. As a backup, if we have some sites nominated beforehand, I can run a few students at my library through some tasks here and we can show off the results to the crowd.

For those of you wanting to attend and help out, I’d really like to see some discussion on typography, writing for the web, “dealing with business/administrative requirements from on-high", maybe do some prototyping exercises, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running a usability test, that would be rad. But we need you to step up and steer part of the time for most of this to work, so if you are interested in some aspect, and especially if you want to volunteer to lead a bit of the time, contact me.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your
name (but not email address, etc.) here

# Ray Schwartz
# Andy Mardesich
# Chelsea Lobdell
# Eben English (1/2 day)
# Shaun Ellis (as attendee or volunteer)
# Whitni Watkins (as attendee or volunteer)
#
#
#
#

=== Intro to Git & possibly beyond ===

'''Half Day [Whenever]'''

* Erin Fahy, Stanford University, efahy@stanford.edu
* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu

We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:

* What is a Distributed Version Control System?
* What's the difference between Git and Github.com?
* How to initialize new Git projects locally and on a remote server/Github
* Cloning/Forking existing projects and keeping up to date
* The wonderful world of Git branches
* Interactive rebasing
* Contributing code to existing projects & what pull requests are
* How to handle merge conflicts
* Overview of workflows and branch best practices
* (time allowing) Advanced git: pre/post hooks, submodules, anything else?

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Jeannie Graham
# Derek Merleaux
# Laurie Reeves
#
#
#
#
#
#
#

=== Visualizing Library Data ===

'''"Half Day [Morning||Afternoon]"'''

* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs

Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Ashley Blewer!
# Bobbi Fox
# Ray Schwartz
# Ranti Junus
# Eric Phetteplace
# Joshua Gomez
# Charlie Morris
# Andy Mardesich
# Tao Zhao
# Chris Hallberg
# Derek Merleaux
# Bohyun Kim
# Mark Jarrell
# Eben English
# Shaun Ellis
# Sarah Simpkin
# Mark Mounts
# Kathryn Stine
# Steve Meyer
# Matt Critchlow
# Andrew Pasterfield
# Ray Henry
# Bret Davidson

=== CollectionSpace: Getting it up and running at your museum ===

'''Half Day [Afternoon]'''

* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org
* TBD

This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org

Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.

''Interested in Attending''
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Terry Brady
#
#
#
#
#
#
#
#
#

=== DPLA API Workshop: ===

'''Half Day [Afternoon]'''

* Audrey Altman, DPLA
* Mark Breedlove, DPLA
* Mark Matienzo, DPLA
* Tom Johnson, DPLA

The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Ranti Junus
# Jean Rainwater
# Mita Williams
# Margaret Heller
# Bohyun Kim
# Steven Anderson
# Shaun Ellis
# Sarah Simpkin
# Mark Jarrell
# Heather Pitts
# Kathryn Stine
# Andrew Woods

[[Category:Code4Lib2015]]

2014 During the Conference Volunteers

2014-03-10T12:58:54Z

Bretdavidson: /* Session Timer Volunteers */

code4lib 2014 During the Conference Volunteers

== Hospitality Suite Committee ==

This committee makes arrangements for any hospitality suite amenities (technology, snacks, games, icebreakers...) we may want.

== Welcome Wagon Committee ==

Offers conference newcomers an opportunity to self-identify; offers oldtimers an opportunity to meet newcomers. May also want to constitute a year-round variation for #code4lib.

* Becky Yoose (b.yoose at google)

== Social Networking ==
Responsible for non-IRC social networking presence.

1-2 person(s) to take questions for sessions (assuming there's time during the session) via Twitter/IRC. Mark if you can only do one or both.

Consider directing people with questions to presenter on twitter/IRC (if applicable) if there is no time for questions.

Tuesday AM

Tuesday PM
* Coral Sheldon-Hess (@web_kunoichi on Twitter, coral on IRC)

Wednesday AM

Wednesday PM

Thursday AM

== IRC Evangelists ==
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.

One of the easiest ways to participate is to [http://webchat.freenode.net/ Go here] with your web browser. Choose a nickname (anything works so long as it is unique; if you want to be anonymous pick appropriately). Enter "code4lib" as the "Channel".

If you've managed to get into the channel without help, type "@helpers" (without the quotes) to see a list of #code4lib helpers.

== IRC Access ==
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people

==Registration Desk Volunteers==

CONCENTRA will be working at the registration desk. We are looking for possibly one person to be a code4lib presence at the desk on Tuesday morning.

Tuesday 8-9 am

Adam Constabaris (first dot last with the cases on the down-low at gmail)

==MCs==

Tuesday AM

Tuesday PM

* Dre, destroyer of cookies, doesn't look as good in a hat as Becky.

Wednesday AM

*Becky, destroyer of last names, singer of badly adapted show tunes

Wednesday PM
*Rosalyn, destroyer of fun, not as entertaining as Becky

Thursday AM
* Cynthia, destroyer of jokes, babbler of the universe

== Session Timer Volunteers ==

People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop with a stopwatch program). It's good to have two people in each slot to back each other up in case of machinery failure.

'''Schedule for Session Timers'''

Tuesday AM
* Francis Kayiwa
* Dan Kerchner

Tuesday PM
* Peter Murray
* Ranti Junus

Wednesday AM
* Maura Carbone

Wednesday PM
* Violeta Ilik

Thursday AM
* Bret Davidson

== Raffles ==

== Whatever Else Needs to be Done ==

* Roy Tennant, royt in channel, text to 707-287-5580

[[Category: Code4Lib2014]]

2014 preconference proposals

2013-11-12T15:50:33Z

Bretdavidson: /* Fail4Lib 2014 */

==Code4Lib 2014 Pre-Conference Proposals==

Proposals will be accepted through December 6th, 2013.

Please fill out your proposal in the following format. If you are interested in attending a proposed pre-conference add your name to the list for that proposal.

Pitch Format:

----

===NAME===
'''"Full-Day|Half-Day" [PREFERRED TIME]'''

Description

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

----

===Drupal4lib Sub-con Barcamp===
=====Full Day=====

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com

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.

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).

[[resources to help you learn drupal]]

====Interested in Attending:====

=====All Day=====
Renna Tuten

=====Morning=====

=====Afternoon=====

===Open Refine Hackfest===
'''"Half-Day"'''
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com

[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

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.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

----

===Responsive Design Hackfest===
'''"Half-Day [Afternoon]"'''
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com
* Contact David Ward, University of Illinois, dh-ward@illinois.edu

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].

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.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

=== Intro to Blacklight ===
'''"Half-Day [Morning]"'''
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu
* TA: Bess Sadler, Stanford University, bess@stanford.edu

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.

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.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#Megan Kudzia
#Bret Davidson

===Blacklight Hackfest===
'''"Half-Day [Afternoon]"'''
* Contact Chris Beer, Stanford University, cabeer@stanford.edu

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.

For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

===RailsBridge: Intro to programming in Ruby on Rails===
'''"Half-Day" [morning]'''
* Contact Justin Coyne, Data Curation Experts, justin@curationexperts.com

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.

RailsBridge is a great workshop that opens the doors to projects like Blacklight and Hydra.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

===Managing Projects: Or I'm in charge, now what?===
'''Full-Day'''

Contact:
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu

This will be a full day session on project management. We'll cover
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets
* '''Executing the Project''' -- status meeting, status reports, issue management
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good)

'''Interested in Attending'''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

===Fail4Lib 2014===
'''Half Day [TBD, probably afternoon]'''

Contacts:
* Andreas Orphanides, akorphan (at) ncsu.edu
* Jason Casden, jmcasden (at) ncsu.edu

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.

The schedule may include the following:

* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?
* 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?
* 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?

''Interested in attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#Bret Davidson

[[:Category:Code4Lib2014]]

2014 preconference proposals

2013-11-12T15:49:55Z

Bretdavidson: /* Intro to Blacklight */

2014 Prepared Talk Proposals

2013-10-29T19:40:49Z

Bretdavidson:

==2014 Prepared Talk Proposals==

'''Proposals for Prepared Talks:'''

Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:

* ''Projects'' you've worked on which incorporate innovative implementation of existing technologies and/or development of new software
* ''Tools and technologies'' – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)
* ''Technical issues'' - Big issues in library technology that should be addressed or better understood
* ''Relevant non-technical issues'' – Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc.

'''To Propose a Talk'''
* Log in to the wiki in order to submit a proposal. If you are not already registered, follow the instructions to do so.
* Provide a title and brief (500 words or fewer) description of your proposed talk.
* If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist us in opening the conference to new presenters.

As in past years, the Code4Lib community will vote on proposals that they would like to see included in the program. This year, however, only the top 10 proposals will be guaranteed a slot at the conference. Additional presentations will be selected by the Program Committee in an effort to ensure diversity in program content. Community votes will, of course, still weigh heavily in these decisions.

Presenters whose proposals are selected for inclusion in the program will be guaranteed an opportunity to register for the conference. The standard conference registration fee will still apply.

''Proposals can be submitted through '''Friday, November 8, 2013, at 5pm PST'''''. Voting will commence on November 18, 2013 and continue through December 6, 2013. The final line-up of presentations will be announced in early January, 2014.

'''Talk Proposals'''

----

== Using Drupal to drive alternative presentation systems ==

* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com

Recently, we have been building systems that use angular.js, Rails, or other systems for presentation, while leveraging Drupal's sophisticated content management capabilities on the back end.

So far, these have been one-way systems, but as we move to Drupal 8 we are beginning to explore ways to further decouple the presentation and CMS functions.

== A Book, a Web Browser and a Tablet: How Bibliotheca Alexandrina's Book Viewer Framework Makes It Possible ==

* [[User:Mohammed.abuouda|Mohammed Abu ouda]], Bibliotheca Alexandrina (The new Library of Alexandria)

A lot of institutions around the world are engaged in multiple digitization projects aiming at preserving the human knowledge present in books and availing them through multiple channels to people around the whole globe. These efforts will sure help close the digital gap particularly with the arrival of affordable e-readers, mobile phones and network coverage. However, the digital reading experience has not yet arrived to its maximum potential. Many readers miss features they like in their good old books and wish to find them in their digital counterpart. In an attempt to create a unique digital reading experience, Bibliotheca Alexandria (BA) created a flexible book viewing framework that is currently used to access its current collection of more than 300,000 digital books in five different languages which includes the largest collection of digitized Arabic books.

Using open source tools, BA used the framework to develop a modular book viewer that can be deployed in different environments and is currently at the heart of various BA projects. The Book viewer provides several features creating a more natural reading experience. As with physical books, the reader can now personalize the books he reads by adding annotations like highlights, underlines and sticky notes to capture his thoughts and ideas in addition to being able to share the book with friends on social networks. The reader can perform a search across the content of the book receiving highlighted search results within the pages of the book. More features can be further added to the book viewer through its plugin architecture.

== Structured data NOW: seeding schema.org in library systems ==

* [http://coffeecode.net Dan Scott], Laurentian University
** Previous code4lib presentations: [https://archive.org/details/code4lib.conf.2008.pres.CouchDBsacrilege CouchDB is sacrilege... mmm, delicious sacrilege] at Code4Lib 2008

The semantic web, linked data, and structured data are all fantastic ideas with a barrier imposed by implementation constraints. If their system does not allow customizations, or the institution lacks skilled human resources, it does not matter how enthused a given library might be about publishing structured data... it will not happen. However, if the software in use simply publishes structured data by default, then the web will be populated for free. Really! No extra resources necessary.

This presentation highlights Dan's work with systems such as Evergreen, Koha, and VuFind to enable the publication of schema.org structured data out-of-the-box. Along the way, we reflect the current state of the W3C Schema.org Bibliographic Extension community group efforts to shape the evolution of the schema.org vocabulary. Finally, hold on tight as we contemplate next steps and the possibilities of a world where structured data is the norm on the web.

== Towards Pasta Code Nirvana: Using JavaScript MVC to Fill Your Programming Ravioli ==

* Bret Davidson, North Carolina State University Libraries, bret_davidson@ncsu.edu
** Previous Code4Lib Presentations: [http://wiki.code4lib.org/index.php/2013_talks_proposals#Data-Driven_Documents:_Visualizing_library_data_with_D3.js Visualizing library data with D3.js] at Code4Lib 2013

JavaScript MVC frameworks are ushering in a golden age of robust and responsive web applications that take advantage of evergreen browsers, performant JS engines, and the unprecedented reach provided by billions of personal computing devices. The web browser has emerged as the world’s most popular application runtime and the complexity[1] and scope of JavaScript applications has exploded accordingly. Server-side web frameworks like Rails and Django have helped developers adhere to best practices like modularity, dependency injection, and unit testing for years, practices that are now being applied to JavaScript development through projects like Backbone[2], Ember[3], and Angular[4].

This talk will discuss the issues JavaScript MVC frameworks are trying to solve, common features like data binding, implications for the future of web development[5], and the appropriateness of JavaScript MVC for library applications.

*[1]http://en.wikipedia.org/wiki/Spaghetti_code
*[2]http://backbonejs.org
*[3]http://emberjs.com
*[4]http://angularjs.org
*[5]http://tomdale.net/2013/09/progressive-enhancement-is-dead/

[[:Category:Code4Lib2014]]

Code4Lib 2014 Conference Planning Volunteers

2013-07-09T20:30:50Z

Bretdavidson: /* Keynote Speakers Committee */

= Code4Lib 2014 Committees =

If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.

We hope to include at least one local person on each committee.

== Book Give-Away Committee ==

This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.

* Kevin S. Clarke (O'Reilly) and general wrangling
* Michael B. Klein (Pragmatic) and winner-picker app

== Keynote Speakers Committee ==

This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.

* Jason Casden (NCSU)
* Tom Johnson (Johnson.tom@gmail.com)
* Bret Davidson (NCSU)

== Onsite Volunteer Committee ==

This committee solicits volunteers to do whatever tasks are needed in person at the conference.

* Kevin S. Clarke
* Kevin Beswick (NCSU)
* Yan Wang (NCCU)

== Pre-conference Committee ==

This committee plans the pre-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

* Adam Constabaris (NCSU)
* Tim Shearer (UNC)

== Program Committee ==

This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting both pre-conferences and regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.

* Tom Johnson (Johnson.tom@gmail.com)
* Kevin Beswick (NCSU)
* Ranti Junus (MSU)

== Scholarships Committee ==

This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.

* Jason Ronallo (NCSU)
* Cory Lown (NCSU)

== Social Activities Committee ==

The committee plans, proposes, and organizes the evening activities.

* Jason Raitz
* Rosalyn Metz
* Dre
* Becky Yoose

== Sponsorships Committee ==

This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.

* Tim McGeary (lead worrier)
* Roy Tennant (OCLC)
* Shaun Ellis (shaune@princeton.edu)
* Robert H. McDonald (Indiana)
* Sean Chen (Duke)
* Thomas Dowling (Wake Forest)
* Will Sexton (Duke)
* Jeff Campbell (UNC-CH)
* Brett Bonfield (Collingswood Public)

== Streaming Video Committee ==

This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.

- Francis Kayiwa

== T-Shirt Committee ==

This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference.

*Charlie Morris (NCSU)

== Voting Activities Committee ==

This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.

*Adam Constabaris (NCSU)

== Whatever Committee ==

This committee does whatever the organizers can't talk anyone else into doing.

* Francis Kayiwa
* Kevin S. Clarke
* Dre
* Ranti Junus

== Wifi / Electrical / IRC Committee==

This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.

* [[User:highermath|Cary Gordon]], cgordon@chillco.com

This is a newly proposed committee.

= Documentation =
To help with documention, no need to sign up, just start editing.
* [[How To Plan A Code4LibCon]]

== Documentation Interest Group ==
Promote ongoing documentation efforts.

[[Category: Code4Lib2014]]

2013 preconference proposals

2013-02-08T01:11:46Z

Bretdavidson: /* 1-360 Richard J. Daley Library, 1:30 pm to 5:30 pm on Monday, February 11 */

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.

Proposals '''now closed'''.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===
====UIC Forum, 9:00 am to 5:00 pm on Monday, February 11====
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

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.

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.

This event is open to the library community. There is a nominal fee ($10) for non-Code4LibCon attendees.

Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.

====I plan on attending:====

=====All Day=====
*Margaret Heller
*Mahria Lebow, mahria at uw edu
*Paula Gray-Overtoom, pgrayove at gmail.com
*Dhanushka Samarakoon, dhanu80 at g mail com
*Leo Robert Klein <del>(when he figures out what date this is)</del> - 2/11 (9a-5p). P.S. Oh Great One! Who do we hand the 10 bucks to?
*Sarah Shealy, sarah.shealy at gmail.com

=====Morning=====
* [[User:Kevenj|Keven Jeffery]]
* Sean Chen

=====Afternoon=====
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)
* Christina Salazar (afternoon only)
* Sarah Dooley (afternoon)
* Josh Wilson, joshwilsonnc at gmail (likely afternoon only)
* Ken Varnum, varnum at umich e-d-u
* Cody Hennesy, chennesy at library berkeley edu
* Colin Koteles, koteles at cod dot edu

==Half Day Morning==
=== Open space session ===
====303 Library of the Health Sciences, 9:00 am to 12:00 pm on Monday, February 11====
* Dan Chudnov, dchud at gwu edu

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.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

'''I plan on attending:'''
* Devon Smith
* Esmé Cowles, escowles@ucsd.edu
* Jason Casden
* Ryan Eby
* mark matienzo
* Donald Mennerich
* Patrick Berry, pberry@csuchico.edu
* Kåre Fiedler Christiansen, kfc@statsbiblioteket.dk
* Michael Poltorak Nielsen mn at statsbiblioteket dot dk
* Joe Atzberger, ohiocore@gmail.com
* Shawn Carraway carraways at midlandstech dot edu
* Emily F. Shaw emily-f-shaw at uiowa dot edu

=== Delivery services ===
====1-1010 Richard J. Daley Library, 9:00 am to 12:00 pm on Monday, February 11====
* Ted Lawless, Brown University Library, tlawless at brown edu.
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.

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.

Possible topics/activities include:
* group discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* 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].

Resources and background information:
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

'''I plan on attending:'''
* Ken Varnum, varnum at umich e-d-u
* Curtis Thacker
* Rosalyn Metz rosalynmetz at gmail com
* James Van Mil - james.vanmil at gmail com
* Andrew Nagy
* Ranti Junus
* Aaron Collier - acollier at csufresno edu
* Demian Katz - demian dot katz at villanova dot edu
* Jacob Andresen - jacob at reindex dot dk
* Erin White - erwhite at vcu edu
* Zeno Tajoli tajoli at cilea it
* William Hicks - William{dot}hicks{at}unt{dot}edu
* Beatrice Pulliam bpulliam at providence edu
* David Bietila dbietila at uchicago edu
* James Staub - james dot staub at nashville dot gov

=== Intro to Blacklight CANCELED ===

PLEASE NOTE: This pre-conference has been canceled in favor of joining forces with the RailsBridge workshop. The afternoon Blacklight session will still be offered.

=== RailsBridge Intro to Ruby on Rails ===
====UIC Forum, 9:00 am to 12:00 pm on Monday, February 11====
* Jason Ronallo, North Carolina State University Libraries, jronallo@gmail.com
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)
* Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu
* Ross Singer, Talis, rossfsinger@gmail.com
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org
* Bess Sadler, Stanford University, bess@stanford.edu
* James Stuart
* Jason Stirnaman (helper), University of Kansas Medical Center, jstirnaman@kumc.edu
* Anyone else want to come and help folks? Contact Jason.
* Richard Aroksaar, National Park Service, richard_aroksaar@nps.gov

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.

* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby

There is some pre-preconference preparation needed so that we can effectively use our time.

'''IMPORTANT''': From this point on if you sign up you '''must''' do the following in order to be prepared for the preconference workshop:
# Add your name below
# fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dEpxd0tzU1ZscnU5QUUtd0JGUk9qQkE6MA#gid=0 experience survey]
# read [https://docs.google.com/document/d/1lQEvljB6MWOdxqcibYsQDVMT2hCevk7Y5cm3143_eaU/edit the emails you have missed]

'''I plan on attending:'''
# First and last name and email address
# John MacGillivray
# Christina Salazar - christina{dot}salazar{at}csuci{dot}edu
# Karen Coombs - coombsk{at}oclc{dot}org
# Becky Yoose - b dot yoose at google overlord
# Jeremy Morse - jgmorse at umich
# Julia Bauder - julia{dot}bauder{at}gmail{dot}com
# Chung Kang
# Karen Miller - k-miller3{at}northwestern{dot}edu
# Betsy Coles - bcoles{at}caltech{dot}edu
# Jay Luker - jay{dot}luker{at}gmail{dot}com
# Santi Thompson
# Sarah Dooley - sarah{at}nclive{dot}org
# Brandon Dudley
# Ken Irwin
# Dennis Ogg - ogg{at}ucar{dot}edu
# Ian Walls - iwalls{at}library{dot}umass{dot}edu
# Steven Villereal – villereal{at}gmail{dot}com
# Hillel Arnold - hillel{dot}arnold{at}gmail{dot}com
# Josh Wilson - joshwilsonnc at gmail
# Cynthia Ng - cynthia [dot] s [dot] ng [at] gmail
# Ian Chan
# Heidi Frank - hf36{at}nyu{dot}edu
# Mark Mounts - mark{dot}mounts{at}dartmouth{dot}edu
# Bill McMillin - wmcmilli{at}pratt {dot}edu
# David Lacy - david dot lacy at villanova dot edu
# Courtney Greene - crgreene at indiana dot edu
# Laney McGlohon - lmcglohon@getty.edu
# Nancy Enneking - nenneking@getty.edu
# Jason Raitz - jcraitz at ncsu dot edu
# Nick Cappadona
# Steven Marsden - steven.marsden@ryerson.ca
# Linda Ballinger - ballingerl at newberry dot org
# Brendan Quinn - brendan-quinn at northwestern dot edu
# Michael Levy - mlevy {at}ushmm {dot}org
# Michael North (m-north at northwestern dot edu)
# Shawn Averkamp - shawnaverkamp{at}gmail{dot}com
# Allan Berry - allan{dot}berry{at}gmail{dot}com
# Cody Hennesy - chennesy at library dot berkeley dot edu
# Devin Higgins - higgi135 at msu dot edu
# Emily Zervas - emily{dot}zervas{at}gmail{dot}com
# Rob Dumas - rdumas {at} chipublib {dot} org
# Evan Boyd - eboyd /at/ ctschicago /period/ edu
# Lauren Ajamie - lauren dot ajamie at nd dot edu
# David Anderson - david dot anderson3 at nih dot gov
# David Bucknum - dabu at loc dot gov
# Dave Menninger - dave.menninger at gmail dot com
# Chris Day - cday2 at saic dot edu
# Corey Harper - corey dot harper at nyu dot edu
# Dileshni Jayasinghe - d dot jayasinghe at utoronto dot ca
# Harish Nayak - hnayak at library dot rochester dot edu
# David Cliff dgcliff@iu.edu
# Cody Hanson codyhanson@umn.edu
# Sean Purcell seanpurc{at}uga{dot}edu
# Laurie Lee Moses lmoses{at}colum{dot}edu
# Sibyl Schaefer sibylschaefer at gmail dot com
# Alisak Sanavongsay asanavongsay{at}ucmerced.edu
# Wayne Schneider wschneider at hclib dot org
# Carolyn Caizzi - carolyn{dot}caizzi {at}northwestern{dot}edu
# Julie Rudder - j-rudder at northwestern dot edu
# Matthew Butler - matthew-butler at uiowa dot edu
# Andromeda Yelton - andromeda.yelton at gmail
# Adam Strohm - adamstrohm at gmail dot com
# Kelly Thompson - thompson {dot} kelly {dot} j {at} gmail {dot} com
# Jane Sandberg - sandbrg2 {at} illinois {dot} edu
# Colin Koteles - koteles at cod dot edu
# George Campbell - campbelg{at}oclc{dot}org
# Sarah Thorngate - scthorngate{at}northpark{dot}edu
# Will Clarke - wfu.edu at clarkewd
# Terry Brady - twb27 at georgetown dot edu
# Patrick Feeley - pgf8 {at} case {dot} edu
# Bennett Magnino - bennett {dot} magnino {at} gmail {dot} com
# Christine McClure camcclure {at} gmail {dot} com
'''IMPORTANT''': From this point on if you sign up you '''must''' do the following in order to be prepared for the preconference workshop:
# Add your name above
# fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dEpxd0tzU1ZscnU5QUUtd0JGUk9qQkE6MA#gid=0 experience survey]
# read [https://docs.google.com/document/d/1lQEvljB6MWOdxqcibYsQDVMT2hCevk7Y5cm3143_eaU/edit the emails you have missed]

===Intro to NoSQL Databases===
====1-470 Richard J. Daley Library, 9:00 am to 12:00 pm on Monday, February 11====
* Joshua Gomez, George Washington University, jngomez at gwu edu

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 "Big Data" 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.

'''I plan on attending:'''
* Esha Datta
* Trevor Thornton
* Michael Doran
* Ray Schwartz - schwartzr2@wpunj.edu
* Kevin Clarke
* Andreas Orphanides
* Tommy Ingulfsen - tommying{at}caltech{dot}edu
* Harrison Dekker
* Eric James eric dot james at yale dot edu
* Sean Crowe - sean.crowe@uc.edu
* Scott Hanrath - shanrath@ku.edu
* Erin Fahy - erin.fahy at mtholyoke edu
* Karen Coyle - kcoyle at kcoyle.net
* Charles Draper
* David Uspal
* Shawn Kiewel - smkiewel at uga dot edu
* Stephanie Collett - stephanie dot collett at ucop dot edu
* Declan Fleming - declan at declan dot net
* David Gonzalez - d.gonzalez26 at umiami dot edu
* Jeff Peterson - gpeterso at umn dot edu
* May Chan - msuicat at gmail dot com
* Kathryn Stine - kathryn dot stine at ucop dot edu
* Tim Thompson - t.thompson5{at}miami{dot}edu
* Eben English - eenglish [at] bpl dot org
* Marisa Strong - marisa dot strong at ucop dot edu
* Michael Lindsey - mackeral at gmail dot com
* Mike Hagedon - hagedonm at u dot library dot arizona dot edu
* Scott Fisher - first/last name with dot in between at ucop dot edu
* James Griffin - griffinj at lafayette dot edu
* Jesse Brown - jfbrown78 at gmail dot com
* [[User:gdave|Dave Green]] david dot L dot green at dartmouth dot edu
* Michael Poltorak Nielsen mn at statsbiblioteket dot dk
* Mads Villadsen, mv@statsbiblioteket.dk
* Jørn Thøgersen, jt@statsbiblioteket.dk
* Julien Gibert, gibert at abes dot fr
* Lisa Gonzalez, lgonzalez@ctu.edu
* Charles Ledvina, charles@indexdata.com
* Jim LeFager, jlefager@depaul.edu
* Debbie Maron, dmaron@purdue.edu
* Carolina Garcia - cg116 nyu
* Tracy Seneca- tjseneca@uic.edu
* William Denton - wtd@pobox.com
* Andrew Darby - agdarby at miami dot edu
* Gary Maixner maixner2 at uiuc dot edu
* Jeremy Prevost
* Esther Verreau everreau skokielibrary info
* Matthew Short, mshort@niu.edu
* Kate Flynn, kef@uic.edu
* Jon Stroop - jstroop at princeton
* Mark Redar
* Robert Haschart - rh9ec at virginia dot edu
* Xiaoming Wang - xw5d at virginia dot edu
* Graham Hukill - graham dot hukill at wayne edu
* Susan Price
* Virginia Schilling - virginia dot schilling at ucr dot edu
* Bret Davidson

==Half Day Afternoon==
=== Data Visualization Hackfest ===
====1-470 Richard J. Daley Library, 1:30 pm to 5:30 pm on Monday, February 11====
* Chris Beer, cabeer at stanford.edu
* Dan Chudnov, dchud at gwu edu

* 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 "Where Librarians Go To Hack"] 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:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

'''I plan on attending:'''
# Devon Smith
# Esha Datta
# Ray Schwartz - schwartzr2@wpunj.edu
# Karen Coombs - coombsk{at}oclc{dot}org
# Julia Bauder - julia{dot}bauder{at}gmail{dot}com
# Jason Stirnaman (jstirnaman at kumc.edu)
# Joshua Gomez
# Ayla Stein (astein at uh.edu)
# Harrison Dekker
# Ian Walls - iwalls{at}library{dot}umass{dot}edu
# Scott Hanrath - shanrath@ku.edu
# Annie Pho
# [[User:Kevenj|Keven Jeffery]]
# James Van Mil - james.vanmil at gmail com
# Sean Crowe - sean.crowe@uc.edu
# Karen coyle - kcoyle at kcoyle.net
# David Lacy - david dot lacy at villanova dot edu
# mark matienzo
# David Uspal
# Emily Lynema - ejlynema at ncsu dot edu
# Sean Chen
# Donald Mennerich
# Allan Berry - allan{dot}berry{at}gmail{dot}com
# Declan Fleming - declan at declan dot net
# Chick Markley -- chick at qrhino dot com
# Devin Higgins - higgi135 at msu dot edu
# Emily Zervas emily{dot}zervas{at}gmail{dot}com
# May Chan -- msuicat at gmail dot com
# Kathryn Stine - kathryn dot stine at ucop dot edu
# James Griffin - griffinj at lafayette dot edu
# Dave Menninger dave.menninger at gmail dot com
# [[User:gdave|Dave Green]] david dot L dot green at dartmouth dot edu
# Rikke Willer - riwi at dtic dot dtu dot dk
# Michael Poltorak NIelsen mn at statsbiblioteket dot dk
# Mads Villadsen, mv@statsbiblioteket.dk
# Jørn Thøgersen, jt@statsbiblioteket.dk
# Joe Atzberger, ohiocore@gmail.com
# Julien Gibert, gibert at abes dot fr
# Christie Peterson - cpeterson at jhu dot edu
# Jim LeFager - jlefager@depaul.edu
# Harish Nayak - hnayak at library dot rochester dot edu
# William Denton - wtd@pobox.com
# Shawn Carraway carraways at midlandstech dot edu
# Naomi Dushay - ndushay at stanford dot edu
# William Hicks - William{dot}hicks{at}unt{dot}edu
# Beatrice Pulliam bpulliam at providence edu
# Matthew Short, mshort@niu.edu
# George Campbell, campbelg{at}oclc{dot}org
# James Staub - james dot staub at nashville dot gov
# Will Clarke - wfu dot edu at clarkewd

=== Intro to Hydra ===
====303 Library of the Health Sciences, 1:30 pm to 5:30 pm on Monday, February 11====
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)
* Justin Coyne, Data Curation Experts (justin.coyne at curationexperts.com)
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)

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.

'''I plan on attending:'''
* Jeremy Prevost
* Dennis Ogg - ogg{at}ucar{dot}edu
* Terry Brady
* Betsy Coles - bcoles{at}caltech{dot}edu
* Brendan Quinn - brendan-quinn at northwestern dot edu
* Shawn Kiewel - smkiewel at uga dot edu
* Steven Villereal – villereal{at}gmail{dot}com
* Ryan Eby
* Dean Farrell
* Ian Chan
* Mark Mounts - mark{dot}mounts{at}dartmouth{dot}edu
* Carl Jones
* Laney McGlohon - lmcglohon@getty.edu
* Nancy Enneking - nenneking@getty.edu
* Allan Berry - allan{dot}berry{at}gmail{dot}com
* Andrew Darby - agdarby at miami dot edu
* Kåre Fiedler Christiansen - kfc@statsbiblioteket.dk
* Corey Harper - corey dot harper at nyu dot edu
* Gary Maixner - maixner2 at uiuc dot edu
* Sibyl Schaefer - sibylschaefer at gmail dot com
* Emily F. Shaw - emily-f-shaw{at}uiowa{dot}edu
* Alicia Morris - alicia.morris@tufts.edu
* Tim Thompson - t.thompson5{at}miami{dot}edu
* Kate Flynn, kef@uic.edu
* Shawn Averkamp, shawn-averkamp{at}uiowa{dot}edu

=== Intro to Blacklight ===
====1-1010 Richard J. Daley Library, 1:30 pm to 5:30 pm on Monday, February 11====
* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Jason Ronallo, NC State (jronallo at gmail.com)
* Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)

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&A around local issues people might encounter.

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

'''I plan on attending:'''
* John MacGillivray
* Jon Stroop
* Jeremy Morse - jgmorse at umich
* Karen Miller - k-miller3{at}northwestern{dot}edu
* Tommy Ingulfsen - tommying{at}caltech{dot}edu
* Chung Kang
* Santi Thompson
* Brandon Dudley
* Ken Irwin
* Hillel Arnold
* Heidi Frank - hf36{at}nyu{dot}com
* Chris Sharp - csharp{at}georgialibraries{dot}org
* Bill McMillin - wmcmilli{at} pratt{dot} edu
* Jason Raitz - jcraitz at ncsu dot edu
* Linda Ballinger - ballingerl at newberry dot org
* Tim Thompson - t.thompson5{at}miami{dot}edu
* David Gonzalez - d.gonzalez26 at umiami dot edu
* Courtney Greene - crgreene at indiana dot edu
* Evan Boyd - eboyd /at/ ctschicago /period/ edu
* Lauren Ajamie - lauren dot ajamie at nd dot edu
* David Anderson - david dot anderson3 at nih dot gov
* Michael Lindsey - mackeral at gmail dot com
* David Bucknum - dabu at loc dot gov
* Chris Day - cday2 at saic dot edu
* Carolina Garcia - cg116 nyu
* David Cliff dgcliff@iu.edu
* Cody Hanson codyhanson@umn.edu
* Sean Purcell seanpurc{at}uga{dot}edu
* Laurie Lee Moses lmoses{at}colum{dot}edu
* Alisak Sanavongsay asanavongsay{at}ucmerced.edu
* Wayne Schneider wschneider at hclib dot org
* Carolyn Caizzi carolyn{dot}caizzi{at}northwestern{dot}edu
* Julie Rudder - j-rudder at northwestern dot edu
* Andromeda Yelton - andromeda.yelton at gmail
* Adam Strohm - adamstrohm at gmail dot com
* Luke Gaudreau - luke underscore gaudreau at harvard dot edu
* Cole Hudson - cole dot hudson at wayne dot edu

=== DPLA Intro/Hacking ===
====Seminar Room A of Richard J. Daley Library, 1:30 pm to 5:30 pm on Monday, February 11====
* 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)

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.

'''I plan on attending:'''
* First and last name, Affiliation
* Justin Clark, Berkman Center for Internet and Society
* Anita Patel, Berkman Center for Internet and Society
* Peter Murray, LYRASIS
* Christine McClure, Illinois Institute of Technology
* Richard Aroksaar, National Park Service

'''I plan on making:'''
* App name (your name): app description

=== Fail4lib ===
====1-360 Richard J. Daley Library, 1:30 pm to 5:30 pm on Monday, February 11====
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)
* Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)

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 ("The Pivot"), and failing more cheaply.

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:

# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.
# 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:
#* Technical failure
#* Failure to effectively address a real user need
#* Overinvestment
#* Outreach/Promotion failure
#* Design/UX failure
#* Project team communication failure
#* Missed opportunities (risk-averse failure)
#* Successes gleaned from failures
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.
# 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.

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.

'''I plan on attending:'''
* Becky Yoose
* Lisa Rabey
* Cynthia Ng (maybe) - cynthia [dot] s [dot] ng [at] gmail
* Patrick Berry, pberry@csuchico.edu
* Erin White, erwhite at vcu edu
* Ranti Junus, ranti.junus at gmail
* Rosalyn Metz -- rosalynmetz at gmail com
* Bret Davidson

=== Solr 4 In Depth ===
====UIC Forum, 1:30 pm to 5:30 pm on Monday, February 11====
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)

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?

'''I plan on attending:'''
* First and last name
* Erin Fahy - erin.fahy at mtholyoke edu
* Esmé Cowles, escowles@ucsd.edu
* Jon Stroop
* Adam Constabars
* Kevin Clarke
* Jacob Andresen (jacob at reindex dot dk)
* Ted Lawless (tlawless at brown dot edu)
* Tom Burton-West
* Curtis Thacker
* Eric James eric dot james at yale dot edu
* Bess Sadler (bess at stanford dot edu)
* Michael North
* Charles Draper
* Nick Cappadona
* Stephanie Collett - stephanie dot collett at ucop dot edu
* Kalee Sprague - kalee dot sprague at yale dot edu
* Jeff Peterson - gpeterso at umn dot edu
* Erik Hetzner
* Demian Katz - demian dot katz at villanova dot edu
* Eben English - eenglish at bpl dot org
* Raman Chandrasekar
* Jason Ronallo - jnronall@ncsu.edu
* Eric Larson - elarson@library.wisc.edu
* Mike Hagedon - hagedonm at u dot library dot arizona dot edu
* Jesse Brown - jfbrown78 at gmail dot com
* Steven Marsden - steven.marsden@ryerson.ca
* Zeno Tajoli - tajoli at cilea it
* Charles Ledvina - charles att indexdata dott com
* Tracy Seneca - tjseneca@uic.edu
* Tod Olson - tod at uchicago dot edu
* Esther Verreau - everreau skokielibrary info
* Jane Sandberg - sandbrg2 at illinois dot edu
* Mark Redar
* Robert Haschart - rh9ec at virginia dot edu
* Xiaoming Wang - xw5d at virginia dot edu
* Graham Hukill - graham dot hukill at wayne edu
* Susan Price

[[Category:Code4Lib2013]]

2013 preconference proposals

2013-02-08T01:10:48Z

Bretdavidson: /* 1-470 Richard J. Daley Library, 9:00 am to 12:00 pm on Monday, February 11 */

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.

Proposals '''now closed'''.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===
====UIC Forum, 9:00 am to 5:00 pm on Monday, February 11====
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

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.

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.

This event is open to the library community. There is a nominal fee ($10) for non-Code4LibCon attendees.

Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.

====I plan on attending:====

=====All Day=====
*Margaret Heller
*Mahria Lebow, mahria at uw edu
*Paula Gray-Overtoom, pgrayove at gmail.com
*Dhanushka Samarakoon, dhanu80 at g mail com
*Leo Robert Klein <del>(when he figures out what date this is)</del> - 2/11 (9a-5p). P.S. Oh Great One! Who do we hand the 10 bucks to?
*Sarah Shealy, sarah.shealy at gmail.com

=====Morning=====
* [[User:Kevenj|Keven Jeffery]]
* Sean Chen

=====Afternoon=====
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)
* Christina Salazar (afternoon only)
* Sarah Dooley (afternoon)
* Josh Wilson, joshwilsonnc at gmail (likely afternoon only)
* Ken Varnum, varnum at umich e-d-u
* Cody Hennesy, chennesy at library berkeley edu
* Colin Koteles, koteles at cod dot edu

==Half Day Morning==
=== Open space session ===
====303 Library of the Health Sciences, 9:00 am to 12:00 pm on Monday, February 11====
* Dan Chudnov, dchud at gwu edu

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.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

'''I plan on attending:'''
* Devon Smith
* Esmé Cowles, escowles@ucsd.edu
* Jason Casden
* Ryan Eby
* mark matienzo
* Donald Mennerich
* Patrick Berry, pberry@csuchico.edu
* Kåre Fiedler Christiansen, kfc@statsbiblioteket.dk
* Michael Poltorak Nielsen mn at statsbiblioteket dot dk
* Joe Atzberger, ohiocore@gmail.com
* Shawn Carraway carraways at midlandstech dot edu
* Emily F. Shaw emily-f-shaw at uiowa dot edu

=== Delivery services ===
====1-1010 Richard J. Daley Library, 9:00 am to 12:00 pm on Monday, February 11====
* Ted Lawless, Brown University Library, tlawless at brown edu.
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.

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.

Possible topics/activities include:
* group discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* 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].

Resources and background information:
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

'''I plan on attending:'''
* Ken Varnum, varnum at umich e-d-u
* Curtis Thacker
* Rosalyn Metz rosalynmetz at gmail com
* James Van Mil - james.vanmil at gmail com
* Andrew Nagy
* Ranti Junus
* Aaron Collier - acollier at csufresno edu
* Demian Katz - demian dot katz at villanova dot edu
* Jacob Andresen - jacob at reindex dot dk
* Erin White - erwhite at vcu edu
* Zeno Tajoli tajoli at cilea it
* William Hicks - William{dot}hicks{at}unt{dot}edu
* Beatrice Pulliam bpulliam at providence edu
* David Bietila dbietila at uchicago edu
* James Staub - james dot staub at nashville dot gov

=== Intro to Blacklight CANCELED ===

PLEASE NOTE: This pre-conference has been canceled in favor of joining forces with the RailsBridge workshop. The afternoon Blacklight session will still be offered.

=== RailsBridge Intro to Ruby on Rails ===
====UIC Forum, 9:00 am to 12:00 pm on Monday, February 11====
* Jason Ronallo, North Carolina State University Libraries, jronallo@gmail.com
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)
* Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu
* Ross Singer, Talis, rossfsinger@gmail.com
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org
* Bess Sadler, Stanford University, bess@stanford.edu
* James Stuart
* Jason Stirnaman (helper), University of Kansas Medical Center, jstirnaman@kumc.edu
* Anyone else want to come and help folks? Contact Jason.
* Richard Aroksaar, National Park Service, richard_aroksaar@nps.gov

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.

* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby

There is some pre-preconference preparation needed so that we can effectively use our time.

'''IMPORTANT''': From this point on if you sign up you '''must''' do the following in order to be prepared for the preconference workshop:
# Add your name below
# fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dEpxd0tzU1ZscnU5QUUtd0JGUk9qQkE6MA#gid=0 experience survey]
# read [https://docs.google.com/document/d/1lQEvljB6MWOdxqcibYsQDVMT2hCevk7Y5cm3143_eaU/edit the emails you have missed]

'''I plan on attending:'''
# First and last name and email address
# John MacGillivray
# Christina Salazar - christina{dot}salazar{at}csuci{dot}edu
# Karen Coombs - coombsk{at}oclc{dot}org
# Becky Yoose - b dot yoose at google overlord
# Jeremy Morse - jgmorse at umich
# Julia Bauder - julia{dot}bauder{at}gmail{dot}com
# Chung Kang
# Karen Miller - k-miller3{at}northwestern{dot}edu
# Betsy Coles - bcoles{at}caltech{dot}edu
# Jay Luker - jay{dot}luker{at}gmail{dot}com
# Santi Thompson
# Sarah Dooley - sarah{at}nclive{dot}org
# Brandon Dudley
# Ken Irwin
# Dennis Ogg - ogg{at}ucar{dot}edu
# Ian Walls - iwalls{at}library{dot}umass{dot}edu
# Steven Villereal – villereal{at}gmail{dot}com
# Hillel Arnold - hillel{dot}arnold{at}gmail{dot}com
# Josh Wilson - joshwilsonnc at gmail
# Cynthia Ng - cynthia [dot] s [dot] ng [at] gmail
# Ian Chan
# Heidi Frank - hf36{at}nyu{dot}edu
# Mark Mounts - mark{dot}mounts{at}dartmouth{dot}edu
# Bill McMillin - wmcmilli{at}pratt {dot}edu
# David Lacy - david dot lacy at villanova dot edu
# Courtney Greene - crgreene at indiana dot edu
# Laney McGlohon - lmcglohon@getty.edu
# Nancy Enneking - nenneking@getty.edu
# Jason Raitz - jcraitz at ncsu dot edu
# Nick Cappadona
# Steven Marsden - steven.marsden@ryerson.ca
# Linda Ballinger - ballingerl at newberry dot org
# Brendan Quinn - brendan-quinn at northwestern dot edu
# Michael Levy - mlevy {at}ushmm {dot}org
# Michael North (m-north at northwestern dot edu)
# Shawn Averkamp - shawnaverkamp{at}gmail{dot}com
# Allan Berry - allan{dot}berry{at}gmail{dot}com
# Cody Hennesy - chennesy at library dot berkeley dot edu
# Devin Higgins - higgi135 at msu dot edu
# Emily Zervas - emily{dot}zervas{at}gmail{dot}com
# Rob Dumas - rdumas {at} chipublib {dot} org
# Evan Boyd - eboyd /at/ ctschicago /period/ edu
# Lauren Ajamie - lauren dot ajamie at nd dot edu
# David Anderson - david dot anderson3 at nih dot gov
# David Bucknum - dabu at loc dot gov
# Dave Menninger - dave.menninger at gmail dot com
# Chris Day - cday2 at saic dot edu
# Corey Harper - corey dot harper at nyu dot edu
# Dileshni Jayasinghe - d dot jayasinghe at utoronto dot ca
# Harish Nayak - hnayak at library dot rochester dot edu
# David Cliff dgcliff@iu.edu
# Cody Hanson codyhanson@umn.edu
# Sean Purcell seanpurc{at}uga{dot}edu
# Laurie Lee Moses lmoses{at}colum{dot}edu
# Sibyl Schaefer sibylschaefer at gmail dot com
# Alisak Sanavongsay asanavongsay{at}ucmerced.edu
# Wayne Schneider wschneider at hclib dot org
# Carolyn Caizzi - carolyn{dot}caizzi {at}northwestern{dot}edu
# Julie Rudder - j-rudder at northwestern dot edu
# Matthew Butler - matthew-butler at uiowa dot edu
# Andromeda Yelton - andromeda.yelton at gmail
# Adam Strohm - adamstrohm at gmail dot com
# Kelly Thompson - thompson {dot} kelly {dot} j {at} gmail {dot} com
# Jane Sandberg - sandbrg2 {at} illinois {dot} edu
# Colin Koteles - koteles at cod dot edu
# George Campbell - campbelg{at}oclc{dot}org
# Sarah Thorngate - scthorngate{at}northpark{dot}edu
# Will Clarke - wfu.edu at clarkewd
# Terry Brady - twb27 at georgetown dot edu
# Patrick Feeley - pgf8 {at} case {dot} edu
# Bennett Magnino - bennett {dot} magnino {at} gmail {dot} com
# Christine McClure camcclure {at} gmail {dot} com
'''IMPORTANT''': From this point on if you sign up you '''must''' do the following in order to be prepared for the preconference workshop:
# Add your name above
# fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dEpxd0tzU1ZscnU5QUUtd0JGUk9qQkE6MA#gid=0 experience survey]
# read [https://docs.google.com/document/d/1lQEvljB6MWOdxqcibYsQDVMT2hCevk7Y5cm3143_eaU/edit the emails you have missed]

===Intro to NoSQL Databases===
====1-470 Richard J. Daley Library, 9:00 am to 12:00 pm on Monday, February 11====
* Joshua Gomez, George Washington University, jngomez at gwu edu

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 "Big Data" 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.

'''I plan on attending:'''
* Esha Datta
* Trevor Thornton
* Michael Doran
* Ray Schwartz - schwartzr2@wpunj.edu
* Kevin Clarke
* Andreas Orphanides
* Tommy Ingulfsen - tommying{at}caltech{dot}edu
* Harrison Dekker
* Eric James eric dot james at yale dot edu
* Sean Crowe - sean.crowe@uc.edu
* Scott Hanrath - shanrath@ku.edu
* Erin Fahy - erin.fahy at mtholyoke edu
* Karen Coyle - kcoyle at kcoyle.net
* Charles Draper
* David Uspal
* Shawn Kiewel - smkiewel at uga dot edu
* Stephanie Collett - stephanie dot collett at ucop dot edu
* Declan Fleming - declan at declan dot net
* David Gonzalez - d.gonzalez26 at umiami dot edu
* Jeff Peterson - gpeterso at umn dot edu
* May Chan - msuicat at gmail dot com
* Kathryn Stine - kathryn dot stine at ucop dot edu
* Tim Thompson - t.thompson5{at}miami{dot}edu
* Eben English - eenglish [at] bpl dot org
* Marisa Strong - marisa dot strong at ucop dot edu
* Michael Lindsey - mackeral at gmail dot com
* Mike Hagedon - hagedonm at u dot library dot arizona dot edu
* Scott Fisher - first/last name with dot in between at ucop dot edu
* James Griffin - griffinj at lafayette dot edu
* Jesse Brown - jfbrown78 at gmail dot com
* [[User:gdave|Dave Green]] david dot L dot green at dartmouth dot edu
* Michael Poltorak Nielsen mn at statsbiblioteket dot dk
* Mads Villadsen, mv@statsbiblioteket.dk
* Jørn Thøgersen, jt@statsbiblioteket.dk
* Julien Gibert, gibert at abes dot fr
* Lisa Gonzalez, lgonzalez@ctu.edu
* Charles Ledvina, charles@indexdata.com
* Jim LeFager, jlefager@depaul.edu
* Debbie Maron, dmaron@purdue.edu
* Carolina Garcia - cg116 nyu
* Tracy Seneca- tjseneca@uic.edu
* William Denton - wtd@pobox.com
* Andrew Darby - agdarby at miami dot edu
* Gary Maixner maixner2 at uiuc dot edu
* Jeremy Prevost
* Esther Verreau everreau skokielibrary info
* Matthew Short, mshort@niu.edu
* Kate Flynn, kef@uic.edu
* Jon Stroop - jstroop at princeton
* Mark Redar
* Robert Haschart - rh9ec at virginia dot edu
* Xiaoming Wang - xw5d at virginia dot edu
* Graham Hukill - graham dot hukill at wayne edu
* Susan Price
* Virginia Schilling - virginia dot schilling at ucr dot edu
* Bret Davidson

==Half Day Afternoon==
=== Data Visualization Hackfest ===
====1-470 Richard J. Daley Library, 1:30 pm to 5:30 pm on Monday, February 11====
* Chris Beer, cabeer at stanford.edu
* Dan Chudnov, dchud at gwu edu

* 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 "Where Librarians Go To Hack"] 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:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

'''I plan on attending:'''
# Devon Smith
# Esha Datta
# Ray Schwartz - schwartzr2@wpunj.edu
# Karen Coombs - coombsk{at}oclc{dot}org
# Julia Bauder - julia{dot}bauder{at}gmail{dot}com
# Jason Stirnaman (jstirnaman at kumc.edu)
# Joshua Gomez
# Ayla Stein (astein at uh.edu)
# Harrison Dekker
# Ian Walls - iwalls{at}library{dot}umass{dot}edu
# Scott Hanrath - shanrath@ku.edu
# Annie Pho
# [[User:Kevenj|Keven Jeffery]]
# James Van Mil - james.vanmil at gmail com
# Sean Crowe - sean.crowe@uc.edu
# Karen coyle - kcoyle at kcoyle.net
# David Lacy - david dot lacy at villanova dot edu
# mark matienzo
# David Uspal
# Emily Lynema - ejlynema at ncsu dot edu
# Sean Chen
# Donald Mennerich
# Allan Berry - allan{dot}berry{at}gmail{dot}com
# Declan Fleming - declan at declan dot net
# Chick Markley -- chick at qrhino dot com
# Devin Higgins - higgi135 at msu dot edu
# Emily Zervas emily{dot}zervas{at}gmail{dot}com
# May Chan -- msuicat at gmail dot com
# Kathryn Stine - kathryn dot stine at ucop dot edu
# James Griffin - griffinj at lafayette dot edu
# Dave Menninger dave.menninger at gmail dot com
# [[User:gdave|Dave Green]] david dot L dot green at dartmouth dot edu
# Rikke Willer - riwi at dtic dot dtu dot dk
# Michael Poltorak NIelsen mn at statsbiblioteket dot dk
# Mads Villadsen, mv@statsbiblioteket.dk
# Jørn Thøgersen, jt@statsbiblioteket.dk
# Joe Atzberger, ohiocore@gmail.com
# Julien Gibert, gibert at abes dot fr
# Christie Peterson - cpeterson at jhu dot edu
# Jim LeFager - jlefager@depaul.edu
# Harish Nayak - hnayak at library dot rochester dot edu
# William Denton - wtd@pobox.com
# Shawn Carraway carraways at midlandstech dot edu
# Naomi Dushay - ndushay at stanford dot edu
# William Hicks - William{dot}hicks{at}unt{dot}edu
# Beatrice Pulliam bpulliam at providence edu
# Matthew Short, mshort@niu.edu
# George Campbell, campbelg{at}oclc{dot}org
# James Staub - james dot staub at nashville dot gov
# Will Clarke - wfu dot edu at clarkewd

=== Intro to Hydra ===
====303 Library of the Health Sciences, 1:30 pm to 5:30 pm on Monday, February 11====
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)
* Justin Coyne, Data Curation Experts (justin.coyne at curationexperts.com)
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)

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.

'''I plan on attending:'''
* Jeremy Prevost
* Dennis Ogg - ogg{at}ucar{dot}edu
* Terry Brady
* Betsy Coles - bcoles{at}caltech{dot}edu
* Brendan Quinn - brendan-quinn at northwestern dot edu
* Shawn Kiewel - smkiewel at uga dot edu
* Steven Villereal – villereal{at}gmail{dot}com
* Ryan Eby
* Dean Farrell
* Ian Chan
* Mark Mounts - mark{dot}mounts{at}dartmouth{dot}edu
* Carl Jones
* Laney McGlohon - lmcglohon@getty.edu
* Nancy Enneking - nenneking@getty.edu
* Allan Berry - allan{dot}berry{at}gmail{dot}com
* Andrew Darby - agdarby at miami dot edu
* Kåre Fiedler Christiansen - kfc@statsbiblioteket.dk
* Corey Harper - corey dot harper at nyu dot edu
* Gary Maixner - maixner2 at uiuc dot edu
* Sibyl Schaefer - sibylschaefer at gmail dot com
* Emily F. Shaw - emily-f-shaw{at}uiowa{dot}edu
* Alicia Morris - alicia.morris@tufts.edu
* Tim Thompson - t.thompson5{at}miami{dot}edu
* Kate Flynn, kef@uic.edu
* Shawn Averkamp, shawn-averkamp{at}uiowa{dot}edu

=== Intro to Blacklight ===
====1-1010 Richard J. Daley Library, 1:30 pm to 5:30 pm on Monday, February 11====
* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Jason Ronallo, NC State (jronallo at gmail.com)
* Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)

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&A around local issues people might encounter.

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

'''I plan on attending:'''
* John MacGillivray
* Jon Stroop
* Jeremy Morse - jgmorse at umich
* Karen Miller - k-miller3{at}northwestern{dot}edu
* Tommy Ingulfsen - tommying{at}caltech{dot}edu
* Chung Kang
* Santi Thompson
* Brandon Dudley
* Ken Irwin
* Hillel Arnold
* Heidi Frank - hf36{at}nyu{dot}com
* Chris Sharp - csharp{at}georgialibraries{dot}org
* Bill McMillin - wmcmilli{at} pratt{dot} edu
* Jason Raitz - jcraitz at ncsu dot edu
* Linda Ballinger - ballingerl at newberry dot org
* Tim Thompson - t.thompson5{at}miami{dot}edu
* David Gonzalez - d.gonzalez26 at umiami dot edu
* Courtney Greene - crgreene at indiana dot edu
* Evan Boyd - eboyd /at/ ctschicago /period/ edu
* Lauren Ajamie - lauren dot ajamie at nd dot edu
* David Anderson - david dot anderson3 at nih dot gov
* Michael Lindsey - mackeral at gmail dot com
* David Bucknum - dabu at loc dot gov
* Chris Day - cday2 at saic dot edu
* Carolina Garcia - cg116 nyu
* David Cliff dgcliff@iu.edu
* Cody Hanson codyhanson@umn.edu
* Sean Purcell seanpurc{at}uga{dot}edu
* Laurie Lee Moses lmoses{at}colum{dot}edu
* Alisak Sanavongsay asanavongsay{at}ucmerced.edu
* Wayne Schneider wschneider at hclib dot org
* Carolyn Caizzi carolyn{dot}caizzi{at}northwestern{dot}edu
* Julie Rudder - j-rudder at northwestern dot edu
* Andromeda Yelton - andromeda.yelton at gmail
* Adam Strohm - adamstrohm at gmail dot com
* Luke Gaudreau - luke underscore gaudreau at harvard dot edu
* Cole Hudson - cole dot hudson at wayne dot edu

=== DPLA Intro/Hacking ===
====Seminar Room A of Richard J. Daley Library, 1:30 pm to 5:30 pm on Monday, February 11====
* 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)

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.

'''I plan on attending:'''
* First and last name, Affiliation
* Justin Clark, Berkman Center for Internet and Society
* Anita Patel, Berkman Center for Internet and Society
* Peter Murray, LYRASIS
* Christine McClure, Illinois Institute of Technology
* Richard Aroksaar, National Park Service

'''I plan on making:'''
* App name (your name): app description

=== Fail4lib ===
====1-360 Richard J. Daley Library, 1:30 pm to 5:30 pm on Monday, February 11====
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)
* Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)

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 ("The Pivot"), and failing more cheaply.

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:

# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.
# 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:
#* Technical failure
#* Failure to effectively address a real user need
#* Overinvestment
#* Outreach/Promotion failure
#* Design/UX failure
#* Project team communication failure
#* Missed opportunities (risk-averse failure)
#* Successes gleaned from failures
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.
# 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.

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.

'''I plan on attending:'''
* Becky Yoose
* Lisa Rabey
* Cynthia Ng (maybe) - cynthia [dot] s [dot] ng [at] gmail
* Patrick Berry, pberry@csuchico.edu
* Erin White, erwhite at vcu edu
* Ranti Junus, ranti.junus at gmail
* Rosalyn Metz -- rosalynmetz at gmail com

=== Solr 4 In Depth ===
====UIC Forum, 1:30 pm to 5:30 pm on Monday, February 11====
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)

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?

'''I plan on attending:'''
* First and last name
* Erin Fahy - erin.fahy at mtholyoke edu
* Esmé Cowles, escowles@ucsd.edu
* Jon Stroop
* Adam Constabars
* Kevin Clarke
* Jacob Andresen (jacob at reindex dot dk)
* Ted Lawless (tlawless at brown dot edu)
* Tom Burton-West
* Curtis Thacker
* Eric James eric dot james at yale dot edu
* Bess Sadler (bess at stanford dot edu)
* Michael North
* Charles Draper
* Nick Cappadona
* Stephanie Collett - stephanie dot collett at ucop dot edu
* Kalee Sprague - kalee dot sprague at yale dot edu
* Jeff Peterson - gpeterso at umn dot edu
* Erik Hetzner
* Demian Katz - demian dot katz at villanova dot edu
* Eben English - eenglish at bpl dot org
* Raman Chandrasekar
* Jason Ronallo - jnronall@ncsu.edu
* Eric Larson - elarson@library.wisc.edu
* Mike Hagedon - hagedonm at u dot library dot arizona dot edu
* Jesse Brown - jfbrown78 at gmail dot com
* Steven Marsden - steven.marsden@ryerson.ca
* Zeno Tajoli - tajoli at cilea it
* Charles Ledvina - charles att indexdata dott com
* Tracy Seneca - tjseneca@uic.edu
* Tod Olson - tod at uchicago dot edu
* Esther Verreau - everreau skokielibrary info
* Jane Sandberg - sandbrg2 at illinois dot edu
* Mark Redar
* Robert Haschart - rh9ec at virginia dot edu
* Xiaoming Wang - xw5d at virginia dot edu
* Graham Hukill - graham dot hukill at wayne edu
* Susan Price

[[Category:Code4Lib2013]]

2013 talks proposals

2012-11-07T13:35:16Z

Bretdavidson:

'''Deadline has been extended by request due to the hurricane/storm.'''

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.

Prepared talks are 20 minutes (including setup and questions), and focus on one or more of the following areas:
* tools (some cool new software, software library or integration platform)
* specs (how to get the most out of some protocols, or proposals for new ones)
* challenges (one or more big problems we should collectively address)

The community will vote on proposals using the criteria of:
* usefulness
* newness
* geekiness
* uniqueness
* awesomeness

Please follow the formatting guidelines:

<pre>
== Talk Title ==

* Speaker's name, affiliation, and email address
* Second speaker's name, affiliation, email address, if applicable

Abstract of no more than 500 words.
</pre>

== All Teh Metadatas Re-Revisited ==

* Esme Cowles, UC San Diego Library, escowles AT ucsd DOT edu
* Matt Critchlow, UC San Diego Library, mcritchlow AT ucsd DOT edu
* Bradley Westbrook, UC San Diego Library, bdwestbrook AT ucsd DOT edu

Last year Declan Fleming presented ALL TEH METADATAS and reviewed our UC
San Diego Library Digital Asset Management system and RDF data model. You
may be shocked to hear that all that metadata wasn't quite enough to
handle increasingly complex digital library and research data in an
elegant way. Our ad-hoc, 8-year-old data model has also been added to in
inconsistent ways and our librarians and developers have not always been
perfectly in sync in understanding how the data model has evolved over
time.

In this presentation we'll review our process of locking a team of
librarians and developers in a room to figure out a new data model, from
domain definition through building and testing an OWL ontology. We¹ll also
cover the challenges we ran into, including the review of existing
controlled vocabularies and ontologies, or lack thereof, and the decisions
made to cover the gaps. Finally, we'll discuss how we engaged the digital
library community for feedback and what we have to do next. We all know
that Things Fall Apart, this is our attempt at Doing Better This Time.

== Modernizing VuFind with Zend Framework 2 ==

* Demian Katz, Villanova University, demian DOT katz AT villanova DOT edu

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.

== Did You Really Say That Out Loud? Tools and Techniques for Safe Public WiFi Computing ==

* [[User:DataGazetteer|Peter Murray]], LYRASIS, Peter.Murray@lyrasis.org

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.
Remember [https://en.wikipedia.org/wiki/Firesheep Firesheep]?
It was an extension to Firefox that demonstrated how easy it was to snag session cookies and impersonate someone else.
So what are you sending out over the airwaves, and what techniques are available to prevent eavesdropping?
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.

== Drupal 8 Preview — Symfony and Twig ==

* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com

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.

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.

Symfony and Twig have a common creator, Fabien Potencier, who's overall goal is to rid the world of the excesses of PHP 4.

== Neat! But How Do We Do It? - The Real-world Problem of Digitizing Complex Corporate Digital Objects ==

* Matthew Mariner, University of Colorado Denver, Auraria Library, matthew.mariner@ucdenver.edu

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, "Let's digitize these together and make them one big awesome project to support public urban history"? 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 "grand ideas crushed by technological limitations" and "projects on the right track" to follow.

== ResCarta Tools building a standard format for audio archiving, discovery and display ==

* [[User:sarney|John Sarnowski]], The ResCarta Foundation, john.sarnowski@rescarta.org

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.

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.

ResCarta-Web presents your audio to IE, Chome, Firefox, Safari, and Opera browsers with full playback and word search capability. Display format is OGG!!

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)

== Format Designation in MARC Records: A Trip Down the Rabbit-Hole ==

* Michael Doran, University of Texas at Arlington, doran@uta.edu

This presentation will use a seemingly simple data point, the "format" 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.

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.

== Touch Kiosk 2: Piezoelectric Boogaloo ==

* Andreas Orphanides, North Carolina State University Libraries, akorphan@ncsu.edu

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.

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.

I will also provide access to a genericized version of the interface code for others to build their own implementations of similar kiosk applications.

[1] http://journal.code4lib.org/articles/5832

== Wayfinding in a Cloud: Location Service for libraries ==

* Petteri Kivimäki, The National Library of Finland, petteri.kivimaki@helsinki.fi

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.

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.

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.

== Empowering Collection Owners with Automated Bulk Ingest Tools for DSpace ==

* Terry Brady, Georgetown University, twb27@georgetown.edu

The Georgetown University Library has developed a number of applications to expedite the process of ingesting content into DSpace.
* Automatically inventory a collection of documents or images to be uploaded
* Generate a spreadsheet for metadata capture based on the inventory
* Generate item-level ingest folders, contents files and dublin core metadata for the items to be ingested
* Validate the contents of ingest folders prior to initiating the ingest to DSpace
* Present users with a simple, web-based form to initiate the batch ingest process

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.

In this presentation, I will provide a demonstration of the tools that were built and discuss the development process that was followed.

== Quality Assurance Reports for DSpace Collections ==

* Terry Brady, Georgetown University, twb27@georgetown.edu

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

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.

In this presentation, I will provide a demonstration of the tools that were built and discuss the development process that was followed.

== A Hybrid Solution for Improving Single Sign-On to a Proxy Service with Squid and EZproxy through Shibboleth and ExLibris’ Aleph X-Server ==

* Alexander Jerabek, UQAM - Université du Québec à Montréal, jerabek.alexander_j@uqam.ca
* Minh-Quang Nguyen, UQAM - Université du Québec à Montréal, nguyen.minh-quang@uqam.ca

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.

See article: http://journal.code4lib.org/articles/7470

== HTML5 Video Now! ==

* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu

Can you use HTML5 video now? Yes.

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.

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.

== Hybrid Archival Collections Using Blacklight and Hydra ==

* Adam Wead, Rock and Roll Hall of Fame and Museum, awead@rockhall.org

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.

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.

== Making the Web Accessible through Solid Design ==

* [[User:Cynthia|Cynthia Ng]] from Ryerson University Library & Archives

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.

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.

== Getting People to What They Need Fast! A Wayfinding Tool to Locate Books & Much More ==

* Steven Marsden, Ryerson University Library & Archives, steven dot marsden at ryerson dot ca
* [[User:Cynthia|Cynthia Ng]], Ryerson University Library & Archives

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.

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.

The presentation will not only cover the technical aspects, but also the implementation and usability findings.

== De-sucking the Library User Experience ==

* Jeremy Prevost, Northwestern University, j-prevost {AT} northwestern [DOT] edu

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.

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.

== Solr Testing Is Easy with Rspec-Solr Gem ==

* Naomi Dushay, Stanford University, ndushay AT stanford DOT edu

How do you know if

* your idea for "left anchoring" searches actually works?
* 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?
* tweaking Solr configs to improve, say, Chinese searching, won't break Turkish and Cyrillic?
* changes to your solrconfig file accomplish what you wanted without breaking anything else?

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:

it "unstemmed author name Zare should precede stemmed variants" do
resp = solr_response(author_search_args('Zare').merge({'fl'=>'id,author_person_display', 'facet'=>false}))
resp.should include("author_person_display" => /\bZare\W/).in_each_of_first(3).documents
resp.should_not include("author_person_display" => /Zaring/).in_each_of_first(20).documents
end

it "Cyrillic searching should work: Восемьсoт семьдесят один день" do
 resp = solr_resp_doc_ids_only({'q'=>'Восемьсoт семьдесят один день'})
 resp.should include("9091779")
end

it "q of 'String quartets Parts' and variants should be plausible " do
 resp = solr_resp_doc_ids_only({'q'=>'String quartets Parts'})
 resp.should have_at_least(2000).documents
 resp.should have_the_same_number_of_results_as(solr_resp_doc_ids_only({'q'=>'(String quartets Parts)'}))
 resp.should have_more_results_than(solr_resp_doc_ids_only({'q'=>'"String quartets Parts"'}))
end

it "Traditional Chinese chars 三國誌 should get the same results as simplified chars 三国志" do
resp = solr_response({'q'=>'三國誌', 'fl'=>'id', 'facet'=>false})
resp.should have_at_least(240).documents
resp.should have_the_same_number_of_results_as(solr_resp_doc_ids_only({'q'=>'三国志'}))
end

See
http://rubydoc.info/github/sul-dlss/rspec-solr/frames
https://github.com/sul-dlss/rspec-solr

and our production relevancy/acceptance/regression tests slowly migrating from cucumber to:
https://github.com/sul-dlss/sw_index_tests

== Northwestern's Digital Image Library ==

*Mike Stroming, Northwestern University Library, m-stroming AT northwestern DOT edu
*Edgar Garcia, Northwestern University Library, edgar-garcia AT northwestern DOT edu

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:

*Build custom collection of images using drag-and-drop
*Re-order images within a collection using drag-and-drop
*Nest collections within other collections
*Create details/crops of images
*Zoom, rotate images
*Upload personal images
*Retrieve your own uploads and details from a collection
*Export a collection to a PowerPoint presentation
*Create a group of users and authorize access to your images
*Batch edit image metadata

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.

== Two standards in a software (to say nothing of Normarc) ==

*Zeno Tajoli, CINECA (Italy), z DOT tajoli AT cineca DOT it

With this presentation I want to show how ILS Koha handles the support of three differnt MARC dialects:
MARC21, Unimarc and Normarc. The main points of the presentation:

*Three MARC at MySQL level
*Three MARC at API level
*Three MARC at display
*Can I add a new format ?

== Future Friendly Web Design for Libraries ==

*[[User:michaelschofield|Michael Schofield]], Alvin Sherman Library, Research, and Information Technology Center, mschofied[dot]nova[dot]edu

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 "redesign") - but things are getting pretty strange. Notions about the Web (and where it can be accessed) are changing.

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.

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.

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.

==BYU's discovery layer service aggregator==

*Curtis Thacker, Brigham Young University, curtis.thacker AT byu DOT edu

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:

*filmfinder - a tool for browsing and searching films
*A custom book recommender service based on checkout data
*Integrated library services like personell, library hours, study room scheduler and database finder through a custom adwords system.
*A very geeky and powerful utility used for converting marc XML into primo compliant xml.
*Embedded floormaps
*A responsive web design
*Bing did-you-mean
*And many more.

I will demo the system, review the archtecture and talk about future plans.

==The Avalon Media System: A Next Generation Hydra Head For Audio and Video Delivery==

* Michael Klein, Senior Software Developer, Northwestern University LIbrary, michael.klein AT northwestern DOT edu
* Nathan Rogers, Programmer/Analyst, Indiana University, rogersna AT indiana DOT edu

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:

* The ingest, search, and discovery functionality of the Hydra framework
* The powerful multimedia workflow management features of Opencast Matterhorn
* The flexible Engage audio/video player
* The streaming capabilities of both Red5 Media Server (open source) and Adobe Flash Media Server (proprietary)

Extensive customization options are built into the framework for tailoring the application to the needs of a specific institution.

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.

== The DH Curation Guide: Building a Community Resource ==

*Robin Davis, John Jay College of Criminal Justice, robdavis AT jjay.cuny.edu
*James Little, University of Illinois Urbana-Champaign, little9 AT illinois.edu

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.

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.

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.

== Solr Update ==

*Erik Hatcher, LucidWorks, erik.hatcher AT lucidworks.com

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.

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.

== Reports for the People ==

*Kara Young, Keene State College, NH, kyoung1 at keene.edu
*Dana Clark, Keene State College, NH, dclark5 at keene.edu

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.

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.
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!

== Network Analyses of Library Catalog Data ==

* Kirk Hess, University of Illinois at Urbana-Champaign, kirkhess AT illinois.edu
* Harriett Green, University of Illinois at Urbana-Champaign, green19 AT illinois.edu

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.

== Pitfall! Working with Legacy Born Digital Materials in Special Collections ==

* Donald Mennerich, The New York Public Library, don.mennerich AT gmail.com
* Mark A. Matienzo, Yale University Library, mark AT matienzo.org

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, "best of breed" tools for digital preservation don't always work as they do for more recent materials, requiring a fair amount of ingenuity and use of "word of mouth tradecraft and knowledge exchanged through serendipitous contacts, backchannel conversations, and beer" (Kirschenbaum, "Breaking <code>badflag</code>").

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.

== Project <s>foobar</s> FUBAR ==

* Becky Yoose, Grinnell College, yoosebec AT grinnell DOT edu

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?

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.

[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.

== Implementing RFID in an Academic Library ==

* Scott Bacon, Coastal Carolina University, sbacon AT coastal DOT edu

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.

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.

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...

== Coding an Academic Library Intranet in Drupal: Now We're Getting Organizized... ==

* Scott Bacon, Coastal Carolina University, sbacon AT coastal DOT edu

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.

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.

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?

== Hands off! Best Practices and Top Ten Lists for Code Handoffs ==

* Naomi Dushay, Stanford University Library, ndushay@stanford.edu
* Bess Sadler, Stanford University Library, bess@stanford.edu

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?

== How to be an effective evangelist for your open source project ==

* Bess Sadler, Stanford University Library, bess@stanford.edu

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.

== What does it mean to be a "good" vendor in an open source meritocracy? ==

* Matt Zumwalt, Data Curation Experts / MediaShelf / Hydra Project, matt@curationexperts.com

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 & outs of compensation & equity structures within for-profit corporations.

The topics of power & influence, fairness, community participation, software quality, employment and personal profit are fair game, along with software licensing, sponsorship, closed source software and the role of sales people.

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. Those contributions have been funded through consulting contracts for authoring & implementing open source software on behalf of organizations around the world.

==Occam’s Reader: A system that allows the sharing of eBooks via Interlibrary Loan==

*Ryan Litsey, Texas Tech University, Ryan DOT Litsey AT ttu.edu
*Kenny Ketner, Texas Tech University, Kenny DOT Ketner AT ttu.edu

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.

== Using Puppet for configuration management when no two servers look alike ==
* Eugene Vilensky, Senior Systems Administrator, Northwestern University Library, evilensky northwestern edu

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.

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.

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.

I will describe our experiences at the library for all three options using the Puppet open-source tool on Enterprise Linux 5 and 6.

== REST IS Your Mobile Strategy ==

* Richard Wolf, University of Illinois at Chicago, richwolf@uic.edu

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.

== ScholarSphere: How We Built a Repository App That Doesn't Feel Like Yet Another Janky Old Repository App ==

* Dan Coughlin, Penn State University, danny@psu.edu
* Mike Giarlo, Penn State University, michael@psu.edu

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:

* eliminate Fedora-isms in the application
* model and expose RDF metadata in ways that users find unobtrusive
* manage permissions via a UI widget that doesn't stab you in the face
* harvest and connect controlled vocabularies (such as LCSH) to forms
* make URIs cool
* keep the app snappy without venturing into the architectural labyrinth of YAGNI
* build and queue background jobs
* expose social features and populate activity streams
* tie checksum verification, characterization, and version control to the UI
* let users upload and edit multiple files at once

The application will be demonstrated; code will be shown; and we solemnly commit to showing ABSOLUTELY NO XML.

==Coding with Mittens==

*Jim LeFager, DePaul University Library jlefager@depaul.edu

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.

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.

== Hacking the DPLA ==
* Nate Hill, Chattanooga Public Library, nathanielhill AT gmail.com
* Sam Klein, Wikipedia, metasj AT gmail.com

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.

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.

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.

== Introduction to SilverStripe 3.0 ==

* Ian Walls, University of Massachusetts Amherst, iwalls AT library DOT umass DOT edu

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
* Features (and why you should consider SilverStripe)
* Requirements & Installation
* Model-View-Controller
* Key data types & configuration settings
* Modules
* Where to start with customization
* Community support and participation

== Citation search in SOLR and second-order operators ==

* Roman Chyla, Astrophysics Data System, roman.chyla AT (cfa.harvad.edu|gmail.com)

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.

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:"black holes") AND keyword:"red dwarf"))

== Managing Segmented Images and Hierarchical Collections with Fedora-Commons and Solr ==

* David Lacy, Villanova University, david DOT lacy AT villanova.edu

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.

We recently devised a procedure to extract these "segmented resources" into their own objects within our repository, and index them individually in our Discovery Layer.

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.

== Google Analytics, Event Tracking and Discovery Tools==

* Emily Lynema, North Carolina State University Libraries. ejlynema AT ncsu DOT edu
* Adam Constabaris, North Carolina State University Libraries, ajconsta AT ncsu DOT edu

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.

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.

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.

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.

== Actions speak louder than words: Analyzing large-scale query logs to improve the research experience ==

* Raman Chandrasekar, Serials Solutions, Raman DOT Chandrasekar AT serialssolutions DOT com
* Ted Diamond, Serials Solutions, Ted DOT Diamond AT serialssolutions DOT com

Analyzing anonymized query and click through logs leads to a better understanding of user behaviors and intents 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 globe.

In this session, we will describe our Relevance Metrics Framework and provide examples of insights gained and surprises encountered 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.

== Supporting Gaming in the College Classroom ==

*Megan O'Neill, Albion College, moneill AT albion DOT edu

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:
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.
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.

== Codecraft ==

* Devon Smith, OCLC Research, smithde@oclc.org

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]: "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." Of the questions who, what, where, why, when, and how, I will focus on why and how, with a minor in where.

'''N.B.''': This will be a NON-TECHNICAL talk.

[1] https://en.wikipedia.org/wiki/Craft#Classification

== KnowBot: A Tool to Manage Reference and Beyond ==

* Sarah Park, Northwest Missouri State University
* Hong Gyu Han, Northwest Missouri State University
* Lori Mardis, Northwest Missouri State University

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.

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.

The presenters will demonstrate KnowBot; share the source code; and discuss the use of the knowledge base to answer the organizational and public need.

== Creating a (mostly) integrated Patron Account with SirsiDynix Symphony and ILLiad ==

* Emily Lynema, North Carolina State University Libraries, ejlynema AT ncsu DOT edu
* Jason Raitz, North Carolina State University Libraries, jcraitz AT ncsu DOT edu

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.

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.

== SKOS Name Authority in a DSpace Institutional Repository ==

* Tom Johnson, Oregon State University, thomas.johnson@oregonstate.edu

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 "Johnson, John", sometime).

OSU is solving this problem with an institutionally scoped, low maintenance SKOS/FOAF "name authority file". 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 "records", 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.

== Meta-Harvesting: Harvesting the Harvesters ==

* Steven Anderson, Boston Public Library, sanderson AT bpl DOT org
* Eben English, Boston Public Library, eenglish AT bpl DOT org

The emerging Digital Public Library of America (http://dp.la/) has proposed to aggregate digital content for search and discovery from several regional "service hubs" 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 "telephone game"-esque data loss and/or transmutation is a significant danger.

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.

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.

== Pay No More Than £3 // DIY Digital Curation ==

* Chris Fitzpatrick, World Maritime University, cf AT wmu DOT se

Are you a small library or archive? 
Do you feel you are being held back by limited technical resources? 
Tired of waiting around for the Google Books Library people to reply to your emails? 

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.
This talk will cover some of the guerrilla tactics being employed to drag a small university's large collection into the internet age.

Topics will include:
*Cheap and effective document scanning methods.
*Valuable resources found at your local hackerspace / makerspace / fablab.
*Metadata enrichment for the not-so-rich and NLP for the people.
*Utilizing social media to crowdsource your collection building.
*How to post-process, OCR, PDF, and ePub your documents using Free software.
*Ways to build out a digital repository with no servers, code, or large 2-year grants required. (ok, maybe some code).

== IIIF: One Image Delivery API to Rule Them All ==

* Willy Mene, Stanford University Libraries, wmene AT stanford DOT edu
* Stuart Snydman, Stanford University Libraries, snydman AT stanford DOT edu

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.

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.

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.

== Data-Driven Documents: Visualizing library data with D3.js ==

* Bret Davidson, North Carolina State University Libraries, bret_davidson@ncsu.edu

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].

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.

*[1]http://d3js.org/
*[2]http://www.nytimes.com/interactive/2012/08/24/us/drought-crops.html
*[3]https://www.gov.uk/performance/dashboard
*[4]http://trends.truliablog.com/vis/pricerange-boston/
*[5]http://www.lib.ncsu.edu/dli/projects/spaceassesstool

[[Category:Code4Lib2013]]