Code4Lib - User contributions [en]

Code4Lib 2014 Conference Planning Volunteers

2013-06-12T01:17:12Z

Tjohnson: /* 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)

== Onsite Volunteer Committee ==

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

* Kevin S. Clarke
* Kevin Beswick (NCSU)

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

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

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

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

Code4Lib 2014 Conference Planning Volunteers

2013-06-12T01:15:49Z

Tjohnson: /* Program Committee */ im happy to run the program comittee.

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

== Onsite Volunteer Committee ==

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

* Kevin S. Clarke
* Kevin Beswick (NCSU)

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

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

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

== 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 talks proposals

2012-11-05T23:36:14Z

Tjohnson: SKOS Name Authority

'''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 <b>IS</b> 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

In 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 at 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 includes light-weight use of Zend studio for PHP and integration of the 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.

[[Category:Code4Lib2013]]

2012 Lightning Talks Signup

2012-02-07T20:06:17Z

Tjohnson: /* If only, we had more time */

'''Sign up for Lightning Talks!!'''

Lightning talks are scheduled on all three days of the conference. A lightning talk is a fast-paced 5 minute talk on a topic of your choosing. Sign-ups for lightning talks will open at 10 am on Tuesday, February 7, immediately following the first keynote.

Mark Jason Dominus has a nice page [http://perl.plover.com/lt/lightning-talks.html about lightning talks], which includes this summary of why you might want to do one:

''Maybe you've never given a talk before, and you'd like to start small. For a Lightning Talk, you don't need to make slides, and if you do decide to make slides, you only need to make three.''

''Maybe you're nervous and you're afraid you'll mess up. It's a lot easier to plan and deliver a five minute talk than it is to deliver a long talk. And if you do mess up, at least the painful part will be over quickly.''

''Maybe you don't have much to say. Maybe you just want to ask a question, or invite people to help you with your project, or boast about something you did, or tell a short cautionary story. These things are all interesting and worth talking about, but there might not be enough to say about them to fill up thirty minutes.''

You might also like Mark Fowler's's [http://www.perl.com/pub/2004/07/30/lightningtalk.html Advice for Giving a Lightning Talk].

'''LIGHTNING TALK SIGNUPS OPEN AT 10 AM PST ON FEBRUARY 7'''

=== Tuesday, 4:10-5:10pm [12 slots] ===

Enter ''Name'' -- ''Title of Talk''

# Al Cornish / XTF in 300 seconds
# Makoto OKamoto / [http://savemlak.jp/wiki/saveMLAK/en?lang=en&uselang=en saveMLAK] - Aid activities for the Great East Japan Earthquake through collaboration via Wiki
# Andrew Nagy / Vendors Suck
# akorphan - Heat maps... not just for input analysis
# Gabriel Farrell / ElasticSearch
# nettie lagace - identifying and solving interoperability problems through cooperation
# Eric Larson -- Finding images in book page images
# adam wead / Blacklight at the Rock Hall
# Kelley McGrath -- FRBR, facets, moving images
# Bohyun Kim -- [http://www.slideshare.net/bohyunkim Web Usability in terms of words]
# Simon Spero. - Restriction Classes, Bitches
# Cynthia Ng / [http://processing.org/ Processing] & [http://processingjs.org/ ProcessingJS]

=== Wednesday, 4:00-5:00pm [12 slots] ===

Enter ''Name'' -- ''Title of Talk''

# Scott Hanrath -- Zotero and SHERPA/RoMEO API mashup
# [[User:DataGazetteer|Peter Murray]] -- Introducing FOSS4LIB.org
# Mark Matienzo -- I've Got Good News
# Mike Durbin -- Edge Cases - Digitizing and delivering undescribed items in EAD
# David Walker -- Basic Learning Tool Interoperability (LTI) Protocol
# Ryuuji Yoshimoto -- Introducing CALIL.JP ,scraping/mushup all of OPACs in JAPAN!
# Kåre Fiedler Christiansen (@kaarefc) -- Chucking all the software components in a library together to present recorded radio and tv
# Joel Richard -- introducing Macaw metadata collection tool
# Rachel Frick - LOD-LAM Incubator Project
# Mao Tsunekawa - Project Shizuku : Making Friends in libraries
# Keith Folsom - Archivists' Toolkit Database Server on an Amazon EC2 Instance
# Rebecca jones

=== Thursday, 10:15-11:00am [9 slots] ===

Enter ''Name'' -- ''Title of Talk''

# David Uspal -- Rapid Deployment Projects
# Robert Haschart -- Adding publicly-accessible Hathi Trust items to your Solr-based discovery system.
# Jeremy Nelson -- Aristotle a Django based Discovery Layer
# Dennis Schafroth - Turbo MARC in YAZ Library
# Yuka Egusa, Masao Takaku -- Recovery of Minamisanriku Library from tsunami disaster
# Corey Harper -- Records to Graphs to Records: Value of DC Abstract Model
# Erik Hetzner -- Strategy for c4l voting
# Ed Summers -- jobs.code4lib.org
# Christopher Spalding -- Search in a Blender

===If only we had more time===
#
#

[[Category:Code4Lib2012]]

2012 preconference proposals

2012-02-06T23:51:03Z

Tjohnson: /* Resources */

=Proposals for 2012 Code4LibCon Preconferences=
Proposals closed Sunday, November 20, 2011, so we can finalize the list and add them to registration! (The deadline for preconference proposals has passed.)

Spaces available: main meeting room (max 275) + 5 breakout rooms (max 30-50).

'''Please include a "Contact/Responsible Individual" name and email address so we know who is willing to put on the proposed precon.
'''
==Full Day==

=== Developing applications using REST web services ===

Been hearing about web services but don’t know where to start to build something? Have you built applications that use read services but are stumped by OAuth, Content Negotiation and HTTP Headers? Come dig in and learn how to build applications that interact with both read and write REST services. We’ll cover the basic principles and practices of REST services and discuss the Atom Publishing Protocol as a REST service and its extensibility. The group will examine and test the CouchDB HTTP API by building a simple list creation tool. You’ll learn how OCLC’s platform web services leverage Atom to expose the data and business processes from OCLC’s library systems. By the end of the session, you’ll know the basic principles of REST services, be able to perform Create, Read, Update and Delete operations via REST and be able to authenticate to REST services via API keys and OAuth.

Come ready to learn and code!

Presenter: Karen Coombs - coombsk at oclc dot org

Room: East Room

==== Interest in Attending ====

*Sam Kome
*Ray Schwartz (schwartzr2@wpunj.edu)
*Jim Robinson
*David Bucknum
*Jean Rainwater
*Joshua Gomez
*Andy Kohler
*Michael North
* Tom Keays (keaysht at lemoyne dot edu)
*Charlie Morris
*Michael Lindsey
* Kåre Fiedler Christiansen (morning only)
* Jørn Thøgersen
* Michael Poltorak Nielsen
* Dre
* Timothy Clarke (tclarke@muhlenberg.edu)
* Keith Folsom
* Rebecca Jones
* Michael Doran (doran@uta.edu)
* Ray Henry (ray dot henry at pcc dot edu)
* Bohyun Kim
* Matt Connolly
* Cynthia Ng
* Justin Littman
* Sibyl Schaefer
* Ron Peterson (ronp@udel.edu)
* Tim Lepczyk
* Joe Montibello
* Mao Tsunekawa (tsunekaw at slis.tsukuba.ac.jp)
* Ryuuji Yoshimoto (ryuuji at notaland.com)
* Masae Fujita (mfujita at code4lib.jp)

==Half Day Morning==

=== [[2012 Linkfest Preconference|Linkfest]] ===

We've had talks and sessions galore about Linked Data at code4lib in past years. Let's focus on linking. Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web. At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there. May a kajillion links bloom!

If you need an "intro to linked data" we can prep a good list of readings/talks to review before you come. But please come ready to link!

Organizer type person: Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu

Room: Municipal Room

==== Interest in Attending ====
* Becky Yoose
* Tom Johnson
* Ed Summers
* bernardo gomez ( bgomez at emory dot edu )
* William Gunn
* Jason Ronallo
* Keri Thompson
* David Lacy
* Corey A Harper
* Matt Phillips (mphillips@law.harvard.edu)
* Declan Fleming
* Shaun Ellis (shaune@princeton.edu)
* Wendy Robertson
* Joel Richard (richardjm AT si DOT edu)
* Devon Smith
* Scott Hanrath (shanrath AT ku DOT edu)
* Jason Stirnaman (jstirnaman AT kumc DOT edu)
* Sean Chen
* Laura Smart
* Tommy Ingulfsen
* Mark Mounts (mark.mounts@dartmouth.edu)
* Kate Zwaard
* Cindy Harper
* Jon Stroop
* Tim Shearer (tshearer at email dot unc dot edu)

=== What's New in Solr ===

UPDATE: Erik won't be making it to Seattle, but will tune in and call in as desired to that time slot. Discuss Solr!!! I'll be lurking and helping out however I can.

This session will bring folks up to speed on the latest developments in Lucene and Solr. There's always a lot of new capabilities as well as tips and tricks on using Solr in clever and powerful ways.

Presenter: Erik Hatcher - erik . hatcher @ lucidimagination dot com (remotely calling in and/or via IRC)

Room: Federal Room

==== Interest in Attending ====
* "Gabriel Farrell" <gsf24@drexel.edu>
* "Erik Hetzner" <erik.hetzner AT ucop BORK edu>
* "Michael B. Klein" <mbklein@gmail>
* Demian Katz (demian DOT katz AT villanova DOT edu)
* Anoop Atre ~ anoop.atre AT mnsu . edu
* David Isaak <david.isaak@kpchr.org>
* John Pillans <jpillan@indiana.edu>
* John Wynstra (john.wynstra@uni.edu)
* mark a. matienzo (mark at matienzo dot oh are gee)
* Sepehr Mavedati (sepehr DOT mavedati AT utoronto DOT ca)
* Mads Villadsen
* Jonathan Rochkind
* Shahin Sahebi (shahin.ezzatsahebi at utoronto dot ca)
* Naomi Dushay (ndushay at stanford dot edu)
* Jeremy Nelson
* Kirk Hess <kirkhess@illinois.edu>
* Gary Thompson
* Larry Baerveldt <lrbaerveldt@gmail.com>
* Dennis Schafroth <dennis @ indexdata.com>
* Bobbi Fox <bobbi_fox at harvard dot edu>
* Ed Fugikawa <ed at coalliance dot org>
* Eric James <eric dot james at yale dot edu>
* Robert Haschart <rh9ec at virginia dot edu>
* Ted Lawless

=== Knocking Down Silos: Tools and Approaches for Simplifying Discovery ===

What strategies have you used to merge silos to give users a more streamlined search experience? How are libraries using tools like Drupal, Islandora, Dublin Core, Solr and Blacklight to make article, catalog and/or repository content discoverable via a single interface? If you’re interested in these issues, challenges and conundrums join us for a morning of thinking, dreaming and scheming.

Speakers/Facilitators will be:
- Thom Cox - Manager of Library Information Technology Services - Tufts University
- Ken Varnum – Web Systems Manager - University of Michigan Libraries
- Stephen Westman – Analyst Programmer, Emerging Technologies and Services - Oregon State University Libraries

Contact: Margaret Mellinger - margaret dot mellinger at oregonstate dot edu

Room: Salon A

==== Interest in Attending ====

* David Uspal (david DOT uspal AT villanova DOT edu)
* Tammy Allgood Wolf
* Wayne Schneider
* Laney McGlohon
* "Kevin S. Clarke" <ksclarke@gmail>
*Kevin Reiss (kr2 AT princeton DOT edu)
* Dan Brubaker Horst (dan.brubaker.horst AT nd.edu)

==Half Day Afternoon==

=== Git -r done ===

A session to cover all things Git, everyone's favorite distributed version control system. This session should cover a little bit of the history of Git, how it works, and how it's different than other version controls systems like SVN. Practical application should also be covered, including how to clone existing repos and contribute code back to them, how to host your own repository, and best practices for setting up a distributed network.

Looking for attendees with real-life Git experience to share it, so we can all broaden our understanding of possible use-cases and nifty advanced features.

Coordinator: <del>Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com</del>

Coordinator Stand-In: Michael B. Klein, Stanford University Libraries, @mbklein or mbklein at stanford.edu

Helper: Cary Gordon, Cherry Hill Company, @highermath / cgordon@chillco.com

Room: Superior Room
==== Interest in Attending ====

* Patrick Berry (pberry@csuchico.edu)
* Chris Sharp (csharp@georgialibraries.org)
* Matt Critchlow (mcritchlow@ucsd.edu)
* Peter Murray (Peter.Murray@lyrasis.org)
* Margaret Heller (mheller@dom.edu)
* Kevin S. Clarke (ksclarke@gmail)
* Michael B. Klein (mbklein@gmail)
* Demian Katz (demian DOT katz AT villanova DOT edu)
* Benjamin Shum (bshum@biblio.org)
* Sibyl Schaefer (sschaefer at rockarch dot org)
* Tammy Allgood Wolf (tammy.allgood@asu.edu)
* Chad Nelson (cnelson17 AT gsu DOT edu)
* Lisa Kurt (lkurt@unr.edu)
* Matt Phillips (mphillips@law.harvard.edu)
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)
* John Wynstra (john.wynstra@uni.edu)
* Declan Fleming
* Shaun Ellis (shaune@princeton.edu)
* Mads Villadsen
* Kåre Fiedler Christiansen
* Shahin Sahebi (shahin.ezzatsahebi@utoronto.ca)
* Devon Smith
* Jeremy Nelson
* Stephanie Collett
* Gary Thompson
* Brian McBride (brian.mcbride at utah.edu)
* Jacob Reed (jacob.reed at utah.edu)
* Bohyun Kim (bohyun.kim at fiu.edu)
* Larry Baerveldt <lrbaerveldt@gmail.com>
* Wayne Schneider
* Matt Connolly
* ernesto valencia
* Ed Fugikawa <ed at coalliance dot org>
* Andrea Schurr (Andrea-Schurr at utc dot edu)
* David Uspal (david DOT uspal AT villanova DOT edu)
* Kate Zwaard
* Kevin Reiss (kr2 AT princeton DOT edu)
* Jon Stroop

==== Resources ====

* Introduction to Git by Scott Chacon (video): http://www.youtube.com/watch?v=ZDR433b0HJY
* Git Immersion (great tutorial): http://gitimmersion.com/index.html
* Git Magic (from basics to advanced topics): http://www-cs-students.stanford.edu/~blynn/gitmagic/index.html
* Git Community Book: http://book.git-scm.com/
* Git Ready (tutorials, recipes, and topics): http://gitready.com/
* Git Rebase Workflow, explained: http://mettadore.com/analysis/a-simple-git-rebase-workflow-explained/
* Interactive Git Cheat Sheet: http://ndpsoftware.com/git-cheatsheet.html
* Linus Torvalds on Git (Google Tech Talk): http://www.youtube.com/watch?v=4XpnKHJAok8

=== Blacklight ===

This session will be walk-through of the architecture of Blacklight and what we have been improving since the rails 3 upgrade. In addition to the architecture of the software, we will also briefly discuss the architecture of the Blacklight community and what has made it successful so far.

For part of the session we will install Blacklight live and get it up and running. This install demo will include a How-To on basic customizations in Blacklight using a test-driven approach (one of the cornerstones of the Blacklight community).

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.

Installation screencast: https://www.youtube.com/watch?v=VLuHuoB8Z6w

Presenters: Jessie Keck, Stanford University - jkeck at stanford dot edu | Molly Pickral, University of Virginia - mpc3c at virginia dot edu

Room: Municipal Room

==== Interest in Attending ====
* bernardo gomez ( bgomez at emory dot edu )
* Mark Mounts <mark.mounts@dartmouth.edu>
* Sibyl Schaefer (sschaefer@rockarch.org)
* John Pillans (jpillan@indiana.edu)
* Mang Sun (mang.dot sun at rice dot edu)
* Emily Lynema (emily_lynema at ncsu dot edu)
* mark a. matienzo (mark at matienzo dot oh are gee)
* Daniel Lovins (daniel dot lovins at nyu dot edu)
* Jonathan Rochkind
* Keith Folsom
* Kirk Hess <kirkhess@illinois.edu>
* Jason Stirnaman (jstirnaman AT kumc DOT edu)
* David Drexler <ddrexler@eou.edu>
* Mike Giarlo (michael at psu.edu)
* Scott Fisher
* Ryuuji Yoshimoto (ryuuji at notaland.com)
* Joe Montibello (joseph.montibello@dartmouth.edu)
* Mao Tsunekawa (tsunekaw at slis.tsukuba.ac.jp)
* Mark Baggett (mbagget1 at utk.edu)

=== DACS and EAD Overview ===

This session will look at what DACS (Describing Archives: a Content Standard) is and describe the ten required elements. Then there will be an overview of what EAD is, how it works, and the required elements. The final part will be a practice session on taking a paper finding aid and coding it using DACS and EAD.

Presenter: Doris Munson, Eastern Washington University, dmunson at ewu dot edu
(please feel free to contact me if you are interested in being a co-presenter)

Room: Hospitality Suite

==== Interest in Attending ====
* Francis Kayiwa ( kayiwa@ YouEyeSee dot edu )
* Carmen Mitchell (carmenmitchell at gmail dot com)
* Cindy Harper (charper at colgate dot edu)

==== Links ====
*[http://www2.archivists.org/standards SAA Standards Portal]
*[http://loc.gov/ead/ LoC EAD website]
*[http://socialarchive.iath.virginia.edu/ Social Networks and Archival Context (SNAC) project] ([http://socialarchive.iath.virginia.edu/prototype.html Prototype])
*[http://eac.staatsbibliothek-berlin.de/ EAC-CPF Website]

=== [[Digging into metadata: context, code, and collaboration]] ===

Working with library/archival metadata is difficult. This preconference will tackle pressing questions and will show some of the intricacies of metadata (including AACR2/MARC) with exercises to demonstrate why inconsistencies exist in the data. What steps can the cataloging & metadata community take to help improve the quality of this data? What tools & techniques could help? Rules have evolved over time leaving dirty legacy data. Systems have impacted--and will continue to impact--data structure & design. How can this data be aggregated and refined for use in a new emerging data environments? What assumptions can safely be made and when do you need to inquire about local practice? We will end with a hack-fest where you can ask questions of experienced catalogers and get help with your metadata related problems. Bring your laptops and data.

Person Herder: Becky Yoose, Grinnell College, yoosebec at grinnell dot edu

Collaborators/Facilitators: Corey Harper, New York University - corey dot harper at nyu dot edu | Shana L. McDanold, University of Pennsylvania -
mcdanold at pobox dot upenn dot edu | Laura Smart, Caltech - laura at library dot caltech dot edu

Room: Salon A

==== Interest in Attending ====
* Peter Green (pmgreen@princeton.edu)
* David Isaak (david.isaak@kpchr.org)
* Alex Rolfe (arolfe@georgefox.edu)
* mark a. matienzo (mark at matienzo dot oh are gee)
* Sarah Johnston (johnsts@stolaf.edu)
* Derek Merleaux (derek@merleaux d0t net)
* Adam Wead (awead {at} rockhall d.t 0 R G)
* Tania Fersenheim (tania dot fersenheim at gmail) (I'm only a maybe because I may have a conflict in this time slot)
* Robin Dean (robin at coalliance dot org)
* Takanori Hayashi (tzhaya at affrc dot go dot jp)
* Paul Deschner (deschner at law dot harvard dot edu)

=== "Geo" ===
This session will explore, we hope collaboratively, the presentation of objects on maps. There will be a section on workflow, a section on discovering objects via "geobrowse," a section discovery of objects via "geosearch," and an exploration of the discovery and presentation of geo-referenced images (e.g. historic maps). There will be open discussion on other approaches to map-based discovery. Emphasis will be placed on simplicity of workflow and implementation. Technologies include: Atom, Django, Solr, and OpenLayers.

Presenters: Mike Graves, UNC Chapel Hill, gravm at email dot unc dot edu; Tim Shearer, UNC Chapel Hill, tshearer at email dot unc dot edu
(please feel free to contact Tim if you are interested in being a co-presenter)

Room: Federal Room

==== Interest in Attending ====
* "Gabriel Farrell" <gsf24@drexel.edu>
* Anoop Atre ~ anoop.atre AT mnsu . edu
* Chad Nelson (cnelson17 AT gsu DOT edu)
* Jason Casden (jmcasden AT ncsu DOT edu
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)
* Sepehr Mavedati (sepehr DOT mavedati AT utoronto DOT ca)
* Michael Poltorak Nielsen
* Wendy Robertson
* Joel Richard (richardjm AT si DOT edu)
* Jonathan Rochkind
* Naomi Dushay (ndushay at stanford dot edu)
* Scott Hanrath (shanrath AT ku DOT edu)
* Aaron Collier (acollier AT csufresno DOT edu)
* David Lacy (david DOT lacy AT villanova DOT edu)
* Jen Weintraub (jweintraub AT library dot ucla dot edu)
* Sean Chen
* Bobbi Fox (bobbi_fox AT harvard dot edu)
* Eric James (eric dot james at yale dot edu)
* Ted Lawless
* Dan Brubaker Horst (dan.brubaker.horst AT nd.edu)
* Masae Fujita (mfujita at code4lib.jp)

== Half-day Evening ==

=== Microsoft Campus Visit ===
Join us for a trip across Lake Washington to Microsoft Headquarters. Bus will depart from the conference hotel at 4:15pm on Monday. We will visit the Microsoft Home, the Envisioning Lab, and/or the MS Library. The we'll head over to Microsoft Research for drinks and appetizers, and you'll see some great demos of some cool new (and free!) technologies coming out of MSR. Bus will get back to hotel by 9:00pm, plenty of time to hit a pub. You'll learn about:

1. Layerscape -[http://communities.worldwidetelescope.org/]

2. ChronoZoom - [http://research.microsoft.com/chronozoom/]

3. F# - [http://www.tryfsharp.org]

4. Microsoft Academic Search - [http://academic.research.microsoft.com]

5. Microsoft Audio Visual Indexing System - [http://research.microsoft.com/mavis]

Space is limited, so reserve your seat today Email Alex at the address below.

Coordinator: Alex Wade, Microsoft Research, awade at microsoft dot com

Presenters: Behrooz Chitsaz; Rob Fatland; Christophe Poulain; Michael Zyskowski

==== Interest in Attending (Registration closed! We are now at capacity.) ====
* Declan Fleming
* Matt Critchlow
* Tom Keays (keaysht at lemoyne dot edu)
* mark a. matienzo (mark at matienzo dot oh are gee)
* Mark Mounts <mark.mounts@dartmouth.edu>
* Kyle Banerjee <banerjek@uoregon.edu>
* Evviva Weinraub
* Emily Lynema <emily_lynema at ncsu dot edu>
* Jason Casden <jmcasden AT ncsu DOT edu>
* Daniel Lovins <daniel.lovins@nyu.edu>
* Cynthia Ng
* "Gabriel Farrell" <gsf24@drexel.edu>
* Shaun Ellis (shaune AT princeton DOT edu)
* Derek Merleaux (derek@merleaux d0t net)
* Mads Villadsen
* Kåre Fiedler Christiansen
* Jørn Thøgersen
* Michael Poltorak Nielsen
* Dileshni Jayasinghe
* Matt Phillips (mphillips@law.harvard.edu)
* Wendy Robertson
* Shahin Sahebi
* Matt Connolly <mjc12 AT cornell dot edu>
* Jeremy Nelson
* Naomi Dushay (ndushay at stanford dot edu)
* Dre
* Ken Varnum (varnum umich edu)
* David Uspal (david DOT uspal AT villanova DOT edu)
* REGISTRATION IS NOW CLOSED

[[Category: Code4Lib2012]]

2012 preconference proposals

2012-01-12T00:38:05Z

Tjohnson: /* Interest in Attending */

2012 talks proposals

2011-11-16T20:12:31Z

Tjohnson: /* Your Catalog in Linked Data */

Deadline for talk submission is ''Sunday, November 20''.

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
* diversity of topics

Please follow the formatting guidelines:

<pre>

== Talk Title: ==

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

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

== VuFind 2.0: Why and How? ==

* Demian Katz, Villanova University, demian.katz@villanova.edu

A major new version of the VuFind discovery software is currently in development. While VuFind 1.x remains extremely popular, some of its components are beginning to show their age. VuFind 2.0 aims to retain all the strengths of the previous version of the software while making the architecture cleaner, more modern and more standards-based. This presentation will examine the motivation behind the update, preview some of the new features to look forward to, and discuss the challenges of creating a developer-friendly open source package in PHP.

== Open Source Software Registry ==

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

LYRASIS is creating and shepherding a [[Registry_E-R_Diagram|registry of library open source software]] as part of its [http://www.lyrasis.org/News/Press-Releases/2011/LYRASIS-Receives-Grant-to-Support-Open-Source.aspx grant from the Mellon Foundation to support the adoption of open source software by libraries].
The goal of the grant is to help libraries of all types determine if open source software is right for them, and what combination of software, hosting, training, and consulting works for their situation.
The registry is intended to become a community exchange point and stimulant for growth of the library open source ecosystem by connecting libraries with projects, service providers, and events.

The first half of this session will demonstrate the registry functions and describe how projects and providers can get involved.
The second half of the session will be a brainstorming suggestion of how to expand the functionality and usefulness of the registry.

== Property Graphs And TinkerPop Applications in Digital Libraries ==

* Brian Tingle, California Digital Library, brian.tingle.cdlib.org@gmail.com

[http://www.tinkerpop.com/ TinkerPop] is an open source software development group focusing on technologies in the [http://en.wikipedia.org/wiki/Graph_database graph database] space.
This talk will provide a general introduction to the TinkerPop Graph Stack and the [https://github.com/tinkerpop/gremlin/wiki/Defining-a-Property-Graph property graph model] is uses. The introduction will include code examples and explanations of the property graph models used by the [http://socialarchive.iath.virginia.edu/ Social Networks in Archival Context] project and show how the historical social graph is exposed as a JSON/REST API implemented by a TinkerPop [https://github.com/tinkerpop/rexster rexster] [https://github.com/tinkerpop/rexster-kibbles Kibble] that contains the application's graph theory logic. Other graph database applications possible with TinkerPop such as RDF support, and citation analysis will also be discussed.

== Security in Mind ==

* Erin Germ, United States Naval Academy, Nimitz Library, germ@usna.edu

I would like to talk about security of library software.

Over the Summer, I discovered a critical vulnerability in a vendor’s software that (verified) allowed me to assume any user’s identity for that site, (verified) switch to any user, and to (unverified, meaning I didn’t not perform this as I didn’t want to “hack” another library’s site) assume the role of any user for any other library who used this particular vendor's software.

Within a 3 hour period, I discovered a 2 vulnerabilities: 1) minor one allowing me to access any backups from any library site, and 2) a critical vulnerability. From start to finish, the examination, discovery in the vulnerability, and execution of a working exploit was done in less than 2 hours. The vulnerability was a result of poor cookie implementation. The exploit itself revolved around modifying the cookie, and then altering the browser’s permissions by assuming the role of another user.

I do not intend on stating which vendor it was, but I will show how I was able to perform this. If needed, I can do further research and “investigation” into other vendor's software to see what I can “find”.

''If selected, I will contact the vendor to inform them that I will present about this at C4L2012. I do not intend on releasing the name of the vendor.''

== Search Engines and Libraries ==

* Greg Lindahl, blekko CTO, greg@blekko.com

[https://blekko.com blekko] is a new web-scale search engine which enables end-users to create vertical search engines, through a feature called [http://help.blekko.com/index.php/category/slashtags/ slashtags]. Slashtags can contain as few as 1 or as many as tens of thousands of websites relevant to a narrow or broad topic. We have an extensive set of slashtags curated by a combination of volunteers and an in-house librarian team, or end-users can create and share their own. This talk will cover examples of slashtag creation relevant to libraries, and show how to embed this search into a library website, either using javascript or via our API.

''We have exhibited at a couple of library conferences, and have received a lot of interest. blekko is a free service.''

== Beyond code. Versioning data with Git and Mercurial. ==

* Stephanie Collett, California Digital Library, stephanie.collett@ucop.edu
* Martin Haye, California Digital Library, martin.haye@ucop.edu

Within a relatively short time since their introduction, [http://en.wikipedia.org/wiki/Distributed_Version_Control_System distributed version control systems] (DVCS) like [http://git-scm.com/ Git] and [http://mercurial.selenic.com/ Mercurial] have enjoyed widespread adoption for versioning code. It didn’t take long for the library development community to start discussing the potential for using DVCS within our applications and repositories to version data. After all, many of the features that have made some of these systems popular in the open source community to version code (e.g. lightweight, file-based, compressed, reliable) also make them compelling options for versioning data. And why write an entire versioning system from scratch if a DVCS solution can be a drop-in solution? At the [http://www.cdlib.org/ California Digital Library] (CDL) we’ve started using Git and Mercurial in some of our applications to version data. This has proven effective in some situations and unworkable in others. This presentation will be a practical case study of CDL’s experiences with using DVCS to version data. We will explain how we’re incorporating Git and Mercurial in our applications, describe our successes and failures and consider the issues involved in repurposing these systems for data versioning.

==Design for Developers==

*Lisa Kurt, University of Nevada, Reno, lkurt@unr.edu

Users expect good design. This talk will delve into what makes really great design, what to look for, and how to do it. Learn the principles of great design to take your applications, user interfaces, and projects to a higher level. With years of experience in graphic design and illustration, Lisa will discuss design principles, trends, process, tools, and development. Design examples will be from her own projects as well as a variety from industry. You’ll walk away with design knowledge that you can apply immediately to a variety of applications and a number of top notch go-to resources to get you up and running.

==Building research applications with Mendeley==

William Gunn, Mendeley william.gunn@mendeley.com (@mrgunn)

This is partly a tool talk and partly a big idea one.

Mendeley has built the world's largest open database of research and we've now begun to collect some interesting social metadata around the document metadata. I would like to share with the Code4Lib attendees information about using this resource to do things within your application that have previously been impossible for the library community, or in some cases impossible without expensive database subscriptions. One thing that's now possible is to augment catalog search by surfacing information about content usage, allowing people to not only find things matching a query, but popular things or things read by their colleagues. In addition to augmenting search, you can also use this information to augment discovery. Imagine an online exhibit of artifacts from a newly discovered dig not just linking to papers which discuss the artifact, but linking to really good interesting papers about the place and the people who made the artifacts. So the big idea is, "How will looking at the literature from a broader perspective than simple citation analysis change how research is done and communicated? How can we build tools that make this process easier and faster?" I can show some examples of applications that have been built using the Mendeley and PLoS APIs to begin to address this question, and I can also present results from Mendeley's developer challenge which shows what kinds of applications researchers are looking for, what kind of applications peope are building, and illustrates some interesting places where the two don't overlap.

==Your UI can make or break the application (to the user, anyway)==

* Robin Schaaf, University of Notre Dame, schaaf.4@nd.edu

UI development is hard and too often ends up as an after-thought to computer programmers - if you were a CS major in college I'll bet you didn't have many, if any, design courses. I'll talk about how to involve the users upfront with design and some common pitfalls of this approach. I'll also make a case for why you should do the screen design before a single line of code is written. And I'll throw in some ideas for increasing usability and attractiveness of your web applications. I'd like to make a case study of the UI development of our open source ERMS.

==Why Nobody Knows How Big The Library Really Is - Perspective of a Library Outside Turned Insider==

* Patrick Berry, California State University, Chico, pberry@csuchico.edu

In this talk I would like to bring the perspective of an "outsider" (although an avowed IT insider) to let you know that people don't understand the full scope of the library. As we "rethink education", it is incumbent upon us to help educate our institutions as to the scope of the library. I will present some of the tactics I'm employing to help people outside, and in some cases inside, the library to understand our size and the value we bring to the institution.

==Building a URL Management Module using the Concrete5 Package Architecture==

* David Uspal, Villanova University, david.uspal@villanova.edu

Keeping track of URLs utilized across a large website such as a university library, and keeping that content up to date for subject and course guides, can be a pain, and as an open source shop, we’d like to have open source solution for this issue. For this talk, I intend to detail our solution to this issue by walking step-by-step through the building process for our URL Management module -- including why a new solution was necessary; a quick rundown of our CMS ([http://www.concrete5.org Concrete5], a CMS that isn’t Drupal); utilizing the Concrete5 APIs to isolate our solution from core code (to avoid complications caused by core updates); how our solution was integrated into the CMS architecture for easy installation; and our future plans on the project.

==Building an NCIP connector to OpenSRF to facilitate resource sharing==

* Jon Scott, Lyrasis, jon_scott@wsu.edu and Kyle Banerjee, Orbis Cascade Alliance, banerjek@uoregon.edu

How do you reverse engineer any protocol to provide a new service? Humans (and worse yet, committees) often design verbose protocols built around use cases that don't line up current reality. To compound difficulties, the contents of protocol containers are not sufficiently defined/predictable and the only assistance available is sketchy documentation and kind individuals on the internet willing to share what they learned via trial by fire.

NCIP (Niso Circulation Interchange Protocol) is an open standard that defines a set of messages to support exchange of circulation data between disparate circulation, interlibrary loan, and related applications -- widespread adoption of NCIP would eliminate huge amounts of duplicate processing in separate systems.

This presentation discusses how we learned enough about NCIP and OpenSRF from scratch to build an NCIP responder for Evergreen to facilitate resource sharing in a large consortium that relies on over 20 different ILSes.

==Practical Agile: What's Working for Stanford, Blacklight, and Hydra==

* Naomi Dushay, Stanford University Libraries, ndushay@stanford.edu

Agile development techniques can be difficult to adopt in the context of library software development. Maybe your shop has only one or two developers, or you always have too many simultaneous projects. Maybe your new projects can’t be started until 27 librarians reach consensus on the specifications.

This talk will present successful Agile- and Silicon-Valley-inspired practices we’ve adopted at Stanford and/or in the Blacklight and Hydra projects. We’ve targeted developer happiness as well as improved productivity with our recent changes. User stories, dead week, sight lines … it’ll be a grab bag of goodies to bring back to your institution, including some ideas on how to adopt these practices without overt management buy in.

==Quick and <strike>Dirty</strike> Clean Usability: Rapid Prototyping with Bootstrap==

* Shaun Ellis, Princeton University Libraries, shaune@princeton.edu

''"The code itself is unimportant; a project is only as useful as people actually find it." - Linus Torvalds'' [http://bit.ly/p4uuyy]

Usability has been a buzzword for some time now, but what is the process for making the the transition toward a better user experience, and hence, better designed library sites? I will discuss the one facet of the process my team is using to redesign the Finding Aids site for Princeton University Libraries (still in development). The approach involves the use of rapid prototyping, with Bootstrap [http://twitter.github.com/bootstrap/], to make sure we are on track with what users and stakeholders expect up front, and throughout the development process.

Because Bootstrap allows for early and iterative user feedback, it is more effective than the historic Photoshop mockups/wireframe technique. The Photoshop approach allows stakeholders to test the look, but not the feel -- and often leaves developers scratching their heads. Being a CSS/HTML/Javascript grid-based framework, Bootstrap makes it easy for anyone with a bit of HTML/CSS chops to quickly build slick, interactive prototypes right in the browser -- tangible solutions which can be shared, evaluated, revised, and followed by all stakeholders (see Minimum Viable Products [http://en.wikipedia.org/wiki/Minimum_viable_product]). Efficiency is multiplied because the customized prototypes can flow directly into production use, as is the goal with iterative development approaches, such as the Agile methodology.

While Bootstrap is not the only framework that offers grid-based layout, development is expedited and usability is enhanced by Bootstraps use of of "prefabbed" conventional UI patterns, clean typography, and lean Javascript for interactivity. Furthermore, out-of-the box Bootstrap comes in a fairly neutral palette, so focus remains on usability, and does not devolve into premature discussions of color or branding choices. Finally, using Less can be a powerful tool in conjunction with Bootstrap, but is not necessary. I will discuss the pros and cons, and offer examples for how to getting up and running with or without Less.

==Search Engine Relevancy Tuning - A Static Rank Framework for Solr/Lucene==

* Mike Schultz, Amazon.com (formerly Summon Search Architect) mike.schultz@gmail.com

Solr/Lucene provides a lot of flexibility for adjusting relevancy scoring and improving search results. Roughly speaking there are two areas of concern: Firstly, a 'dynamic rank' calculation that is a function of the user query and document text fields. And secondly, a 'static rank' which is independent of the query and generally is a function of non-text document metadata. In this talk I will outline an easily understood, hand-tunable static rank system with a minimal number of parameters.

The obvious major feature of a search engine is to return results relevant to a user query. Perhaps less obvious is the huge role query independent document features play in achieving that. Google's PageRank is an example of a static ranking of web pages based on links and other secret sauce. In the Summon service, our 800 million documents have features like publication date, document type, citation count and Boolean features like the-article-is-peer-reviewed. These fields aren't textual and remain 'static' from query to query, but need to influence a document's relevancy score. In our search results, with all query related features being equal, we'd rather have more recent documents above older ones, Journals above Newspapers, and articles that are peer reviewed above those that are not. The static rank system I will describe achieves this and has the following features:

* Query-time only calculation - nothing is baked into the index - with parameters adjustable at query time.
* The system is based on a signal metaphor where components are 'wired' together. System components allow multiplexing, amplifying, summing, tunable band-pass filtering, string-to-value-mapping all with a bare minimum of parameters.
* An intuitive approach for mixing dynamic and static rank that is more effective than simple adding or multiplying.
* A way of equating disparate static metadata types that leads to understandable results ordering.

==Submitting Digitized Book-like things to the Internet Archive==

* Joel Richard, Smithsonian Institution Libraries, richardjm@si.edu

The Smithsonian Libraries has submitted thousands of out-of-copyright items to the Internet Archive over the years. Specifically in relation to the Biodiversity Heritage Library, we have developed an in-house boutique scanning and upload process that became a learning experience in automated uploading to the Archive. As part of the software development, we created a whitepaper that details the combined learning experiences of the Smithsonian Libraries and the Missouri Botanical Garden. We will discuss some of the the contents of this whitepaper in the context of our scanning process and the manner in which we upload items to the Archive.

Our talk will include a discussion of the types of files and their formats used by the Archive, processes that the Archive performs on uploaded items, ways of interacting and affecting those processes, potential pitfalls and solutions that you may encounter when uploading, and tools that the Archive provides to help monitor and manage your uploaded documents.

Finally, we'll wrap up with a brief summary of how to use things that are on the Internet Archive in your own websites.

== So... you think you want to Host a Code4Lib National Conference, do you? ==

* Elizabeth Duell, Orbis Cascade Alliance, eduell@uoregon.edu

Are you interested in hosting your own Code4Lib Conference? Do you know what it would take? What does BEO stands for? What does F&B Minimum mean? Who would you talk to for support/mentoring? There are so many things to think about: internet support, venue size, rooming blocks, contracts, dietary restrictions and coffee (can't forget the coffee!) just to name a few. Putting together a conference of any size can look daunting, so let's take the scary out of it and replace it with a can do attitude!

Be a step ahead of the game by learning from the people behind the curtain. Ask questions and be given templates/ cheat sheets!

== HTML5 Microdata and Schema.org ==

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

When the big search engines announced support for HTML5 microdata and the schema.org vocabularies, the balance of power for semantic markup in HTML shifted.
* What is microdata?
* Where does microdata fit with regards to other approaches like RDFa and microformats?
* Where do libraries stand in the worldview of Schema.org and what can they do about it?
* How can implementing microdata and schema.org optimize your sites for search engines?
* What tools are available?

== Stack View: A Library Browsing Tool ==

* Annie Cain, Harvard Library Innovation Lab, acain@law.harvard.edu
* Jeff Goldenson, Harvard Library Innovation Lab, jgoldenson@law.harvard.edu

In an effort to recreate and build upon the traditional method of browsing a physical library, we used catalog data, including dimensions and page count, to create a [http://librarylab.law.harvard.edu/projects/stackview/ virtual shelf].

This CSS and JavaScript backed visualization allows items to sit on any number of different shelves, really taking advantage of its digital nature. See how we built Stack View on top of our data and learn how you can create shelves of your own using our open source code.

== “Linked-Data-Ready” Software for Libraries ==

* Jennifer Bowen, University of Rochester River Campus Libraries, jbowen@library.rochester.edu

Linked data is poised to replace MARC as the basis for the new library bibliographic framework. For libraries to benefit from linked data, they must learn about it, experiment with it, demonstrate its usefulness, and take a leadership role in its deployment.

The eXtensible Catalog Organization (XCO) offers open-source software for libraries that is “linked-data-ready.” XC software prepares MARC and Dublin Core metadata for exposure to the semantic web, incorporating FRBR Group 1 entities and registered vocabularies for RDA elements and roles. This presentation will include a software demonstration, proposed software architecture for creation and management of linked data, a vision for how libraries can migrate from MARC to linked data, and an update on XCO progress toward linked data goals.

== How people search the library from a single search box ==

* Cory Lown, North Carolina State University Libraries, cory_lown@ncsu.edu

Searching the library is complex. There's the catalog, article databases, journal title and database title look-ups, the library website, finding aids, knowledge bases, etc. How would users search if they could get to all of these resources from a single search box? I'll share what we've learned about single search at NCSU Libraries by tracking use of QuickSearch (http://www.lib.ncsu.edu/search/index.php?q=aerospace+engineering), our home-grown unified search application. As part of this talk I will suggest low-cost ways to collect real world use data that can be applied to improve search. I will try to convince you that data collection must be carefully planned and designed to be an effective tool to help you understand what your users are telling you through their behavior. I will talk about how the fragmented library resource environment challenges us to provide useful and understandable search environments. Finally, I will share findings from analyzing millions of user transactions about how people search the library from a production single search box at a large university library.

== An Incremental Approach to Archival Description and Access ==

* Chela Scott Weber, New York University Libraries, chelascott@gmail.com
* Mark A. Matienzo, Yale University Library, mark@matienzo.org

''This is placeholder text; description coming shortly''

== Making the Easy Things Easy: A Generic ILS API ==

* Wayne Schneider, Hennepin County Library, wschneider@hclib.org

Some stuff we try to do is complicated, because, let's face it, library data is hard. Some stuff, on the other hand, should be easy. Given an item identifier, I should be able to look at item availability. Given a title identifier, I should be able to place a request. And no, I shouldn't have to parse through the NCIP specification or write a SIP client to do it.

This talk will present work we have done on a web services approach to an API for traditional library transactional data, including example applications.

== Your Catalog in Linked Data==

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

Linked Library Data activity over the last year has seen bibliographic data sets and vocabularies proliferating from traditional library
sources. We've reached a point where regular libraries don't have to go it alone to be on the Semantic Web. There is a quickly growing pool of things we can actually ''link to'', and everyone's existing data can be immediately enriched by participating.

This is a quick and dirty road to getting your catalog onto the Linked Data web. The talk will take you from start to finish, using Free Software tools to establish a namespace, put up a SPARQL endpoint, make a simple data model, convert MARC records to RDF, and link the results to major existing data sets (skipping conveniently over pesky processing time). A small amount of "why linked data?" content will be covered, but the primary goal is to leave you able to reproduce the process and start linking your catalog into the web of data. Appropriate documentation will be on the web.

== Getting the Library into the Learning Management System using Basic LTI ==

* David Walker, California State University, dwalker@calstate.edu

The integration of library resources into learning management systems (LMS) has long been something of a holy grail for academic libraries. The ability to deliver targeted library systems and services to students and faculty within the context of a specific course could greatly simplify access to library resources. Yet, the technical barriers to achieving that goal have to date been formidable.

The recently released Learning Tool Interoperability (LTI) protocol, developed by IMS, now greatly simplifies this process by allowing libraries (and others) to develop and maintain “tools” that function like a native plugin or building block within the LMS, but ultimately live outside of it. In this presentation, David will provide an overview of Basic LTI, a simplified subset (or profile) of the wider LTI protocol, showing how libraries can use this to easily integrate their external systems into any major LMS. He’ll showcase the work Cal State has done to do just that.

== Turn your Library Proxy Server into a Honeypot ==

* Calvin Mah, Simon Fraser University, calvinm@sfu.ca (@calvinmah)

Ezproxy has provided libraries with a useful tool for providing patrons with offsite online access to licensed electronic resources. This has not gone unnoticed for the unscrupulous users of the Internet who are either unwilling or unable to obtain legitimate access to these materials for themselves. Instead, they buy or share hacked university computing accounts for unauthorized access. When undetected, abuse of compromised university accounts can lead to abuse of vendor resources which lead to the blocking of the entire campus block of IP addresses from accessing that resource.

Simon Fraser University Library has been pro actively detecting and thwarting unauthorized attempts through log analysis. Since SFU has begun analysing our ezproxy logs, the number of new SFU login credentials which are posted and shared in publicly accessible forums has been reduced to zero. Since our log monitoring began in 2008, the annual average number of SFU login credentials that are compromised or hacked is 140. Instead of being a single point of weakness in campus IT security, the library’s proxy server is a honeypot exposing weak passwords, keystroke logging trojans installed on patron PCs and campus network password sniffers.

This talk will discuss techniques such as geomapping login attempts, strategies such as seeding phishing attempts and tools such as statistical log analysis used in detecting compromised login credentials.

== Relevance Ranking in the Scholarly Domain ==

* Tamar Sadeh, PhD, Ex Libris Group, tamar.sadeh@exlibrisgroup.com

The greatest challenge for discovery systems is how to provide users with the most relevant search results, given the immense landscape of available content. In a manner that is similar to human interaction between two parties, in which each person adjusts to the other in tone, language, and subject matter, discovery systems would ideally be sophisticated and flexible enough to adjust their algorithms to individual users and each user’s information needs.

When evaluating the relevance of an item to a specific user in a specific context, relevance-ranking algorithms need to take into account, in addition to the degree to which the item matches the query, information that is not embodied in the item itself. Such information, which includes the item’s scholarly value, the type of search that the user is conducting (e.g., an exploratory search or a known-item search), and other factors, enables a discovery system to fulfill user expectations that have been shaped by experience with Web search engines.

The session will focus on the challenges of developing and evaluating relevance-ranking algorithms for the scholarly domain. Examples will be drawn mainly from the relevance-ranking technology deployed by the Ex Libris Primo discovery solution.

[[Category: Code4Lib2012]]

2012 talks proposals

2011-11-16T19:07:26Z

Tjohnson: /* Your Catalog in Linked Data */

Deadline for talk submission is ''Sunday, November 20''.

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
* diversity of topics

Please follow the formatting guidelines:

<pre>

== Talk Title: ==

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

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

== VuFind 2.0: Why and How? ==

* Demian Katz, Villanova University, demian.katz@villanova.edu

A major new version of the VuFind discovery software is currently in development. While VuFind 1.x remains extremely popular, some of its components are beginning to show their age. VuFind 2.0 aims to retain all the strengths of the previous version of the software while making the architecture cleaner, more modern and more standards-based. This presentation will examine the motivation behind the update, preview some of the new features to look forward to, and discuss the challenges of creating a developer-friendly open source package in PHP.

== Open Source Software Registry ==

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

LYRASIS is creating and shepherding a [[Registry_E-R_Diagram|registry of library open source software]] as part of its [http://www.lyrasis.org/News/Press-Releases/2011/LYRASIS-Receives-Grant-to-Support-Open-Source.aspx grant from the Mellon Foundation to support the adoption of open source software by libraries].
The goal of the grant is to help libraries of all types determine if open source software is right for them, and what combination of software, hosting, training, and consulting works for their situation.
The registry is intended to become a community exchange point and stimulant for growth of the library open source ecosystem by connecting libraries with projects, service providers, and events.

The first half of this session will demonstrate the registry functions and describe how projects and providers can get involved.
The second half of the session will be a brainstorming suggestion of how to expand the functionality and usefulness of the registry.

== Property Graphs And TinkerPop Applications in Digital Libraries ==

* Brian Tingle, California Digital Library, brian.tingle.cdlib.org@gmail.com

[http://www.tinkerpop.com/ TinkerPop] is an open source software development group focusing on technologies in the [http://en.wikipedia.org/wiki/Graph_database graph database] space.
This talk will provide a general introduction to the TinkerPop Graph Stack and the [https://github.com/tinkerpop/gremlin/wiki/Defining-a-Property-Graph property graph model] is uses. The introduction will include code examples and explanations of the property graph models used by the [http://socialarchive.iath.virginia.edu/ Social Networks in Archival Context] project and show how the historical social graph is exposed as a JSON/REST API implemented by a TinkerPop [https://github.com/tinkerpop/rexster rexster] [https://github.com/tinkerpop/rexster-kibbles Kibble] that contains the application's graph theory logic. Other graph database applications possible with TinkerPop such as RDF support, and citation analysis will also be discussed.

== Security in Mind ==

* Erin Germ, United States Naval Academy, Nimitz Library, germ@usna.edu

I would like to talk about security of library software.

Over the Summer, I discovered a critical vulnerability in a vendor’s software that (verified) allowed me to assume any user’s identity for that site, (verified) switch to any user, and to (unverified, meaning I didn’t not perform this as I didn’t want to “hack” another library’s site) assume the role of any user for any other library who used this particular vendor's software.

Within a 3 hour period, I discovered a 2 vulnerabilities: 1) minor one allowing me to access any backups from any library site, and 2) a critical vulnerability. From start to finish, the examination, discovery in the vulnerability, and execution of a working exploit was done in less than 2 hours. The vulnerability was a result of poor cookie implementation. The exploit itself revolved around modifying the cookie, and then altering the browser’s permissions by assuming the role of another user.

I do not intend on stating which vendor it was, but I will show how I was able to perform this. If needed, I can do further research and “investigation” into other vendor's software to see what I can “find”.

''If selected, I will contact the vendor to inform them that I will present about this at C4L2012. I do not intend on releasing the name of the vendor.''

== Search Engines and Libraries ==

* Greg Lindahl, blekko CTO, greg@blekko.com

[https://blekko.com blekko] is a new web-scale search engine which enables end-users to create vertical search engines, through a feature called [http://help.blekko.com/index.php/category/slashtags/ slashtags]. Slashtags can contain as few as 1 or as many as tens of thousands of websites relevant to a narrow or broad topic. We have an extensive set of slashtags curated by a combination of volunteers and an in-house librarian team, or end-users can create and share their own. This talk will cover examples of slashtag creation relevant to libraries, and show how to embed this search into a library website, either using javascript or via our API.

''We have exhibited at a couple of library conferences, and have received a lot of interest. blekko is a free service.''

== Beyond code. Versioning data with Git and Mercurial. ==

* Stephanie Collett, California Digital Library, stephanie.collett@ucop.edu
* Martin Haye, California Digital Library, martin.haye@ucop.edu

Within a relatively short time since their introduction, [http://en.wikipedia.org/wiki/Distributed_Version_Control_System distributed version control systems] (DVCS) like [http://git-scm.com/ Git] and [http://mercurial.selenic.com/ Mercurial] have enjoyed widespread adoption for versioning code. It didn’t take long for the library development community to start discussing the potential for using DVCS within our applications and repositories to version data. After all, many of the features that have made some of these systems popular in the open source community to version code (e.g. lightweight, file-based, compressed, reliable) also make them compelling options for versioning data. And why write an entire versioning system from scratch if a DVCS solution can be a drop-in solution? At the [http://www.cdlib.org/ California Digital Library] (CDL) we’ve started using Git and Mercurial in some of our applications to version data. This has proven effective in some situations and unworkable in others. This presentation will be a practical case study of CDL’s experiences with using DVCS to version data. We will explain how we’re incorporating Git and Mercurial in our applications, describe our successes and failures and consider the issues involved in repurposing these systems for data versioning.

==Design for Developers==

*Lisa Kurt, University of Nevada, Reno, lkurt@unr.edu

Users expect good design. This talk will delve into what makes really great design, what to look for, and how to do it. Learn the principles of great design to take your applications, user interfaces, and projects to a higher level. With years of experience in graphic design and illustration, Lisa will discuss design principles, trends, process, tools, and development. Design examples will be from her own projects as well as a variety from industry. You’ll walk away with design knowledge that you can apply immediately to a variety of applications and a number of top notch go-to resources to get you up and running.

==Building research applications with Mendeley==

William Gunn, Mendeley william.gunn@mendeley.com (@mrgunn)

This is partly a tool talk and partly a big idea one.

Mendeley has built the world's largest open database of research and we've now begun to collect some interesting social metadata around the document metadata. I would like to share with the Code4Lib attendees information about using this resource to do things within your application that have previously been impossible for the library community, or in some cases impossible without expensive database subscriptions. One thing that's now possible is to augment catalog search by surfacing information about content usage, allowing people to not only find things matching a query, but popular things or things read by their colleagues. In addition to augmenting search, you can also use this information to augment discovery. Imagine an online exhibit of artifacts from a newly discovered dig not just linking to papers which discuss the artifact, but linking to really good interesting papers about the place and the people who made the artifacts. So the big idea is, "How will looking at the literature from a broader perspective than simple citation analysis change how research is done and communicated? How can we build tools that make this process easier and faster?" I can show some examples of applications that have been built using the Mendeley and PLoS APIs to begin to address this question, and I can also present results from Mendeley's developer challenge which shows what kinds of applications researchers are looking for, what kind of applications peope are building, and illustrates some interesting places where the two don't overlap.

==Your UI can make or break the application (to the user, anyway)==

* Robin Schaaf, University of Notre Dame, schaaf.4@nd.edu

UI development is hard and too often ends up as an after-thought to computer programmers - if you were a CS major in college I'll bet you didn't have many, if any, design courses. I'll talk about how to involve the users upfront with design and some common pitfalls of this approach. I'll also make a case for why you should do the screen design before a single line of code is written. And I'll throw in some ideas for increasing usability and attractiveness of your web applications. I'd like to make a case study of the UI development of our open source ERMS.

==Why Nobody Knows How Big The Library Really Is - Perspective of a Library Outside Turned Insider==

* Patrick Berry, California State University, Chico, pberry@csuchico.edu

In this talk I would like to bring the perspective of an "outsider" (although an avowed IT insider) to let you know that people don't understand the full scope of the library. As we "rethink education", it is incumbent upon us to help educate our institutions as to the scope of the library. I will present some of the tactics I'm employing to help people outside, and in some cases inside, the library to understand our size and the value we bring to the institution.

==Building a URL Management Module using the Concrete5 Package Architecture==

* David Uspal, Villanova University, david.uspal@villanova.edu

Keeping track of URLs utilized across a large website such as a university library, and keeping that content up to date for subject and course guides, can be a pain, and as an open source shop, we’d like to have open source solution for this issue. For this talk, I intend to detail our solution to this issue by walking step-by-step through the building process for our URL Management module -- including why a new solution was necessary; a quick rundown of our CMS ([http://www.concrete5.org Concrete5], a CMS that isn’t Drupal); utilizing the Concrete5 APIs to isolate our solution from core code (to avoid complications caused by core updates); how our solution was integrated into the CMS architecture for easy installation; and our future plans on the project.

==Building an NCIP connector to OpenSRF to facilitate resource sharing==

* Jon Scott, Lyrasis, jon_scott@wsu.edu and Kyle Banerjee, Orbis Cascade Alliance, banerjek@uoregon.edu

How do you reverse engineer any protocol to provide a new service? Humans (and worse yet, committees) often design verbose protocols built around use cases that don't line up current reality. To compound difficulties, the contents of protocol containers are not sufficiently defined/predictable and the only assistance available is sketchy documentation and kind individuals on the internet willing to share what they learned via trial by fire.

NCIP (Niso Circulation Interchange Protocol) is an open standard that defines a set of messages to support exchange of circulation data between disparate circulation, interlibrary loan, and related applications -- widespread adoption of NCIP would eliminate huge amounts of duplicate processing in separate systems.

This presentation discusses how we learned enough about NCIP and OpenSRF from scratch to build an NCIP responder for Evergreen to facilitate resource sharing in a large consortium that relies on over 20 different ILSes.

==Practical Agile: What's Working for Stanford, Blacklight, and Hydra==

* Naomi Dushay, Stanford University Libraries, ndushay@stanford.edu

Agile development techniques can be difficult to adopt in the context of library software development. Maybe your shop has only one or two developers, or you always have too many simultaneous projects. Maybe your new projects can’t be started until 27 librarians reach consensus on the specifications.

This talk will present successful Agile- and Silicon-Valley-inspired practices we’ve adopted at Stanford and/or in the Blacklight and Hydra projects. We’ve targeted developer happiness as well as improved productivity with our recent changes. User stories, dead week, sight lines … it’ll be a grab bag of goodies to bring back to your institution, including some ideas on how to adopt these practices without overt management buy in.

==Quick and <strike>Dirty</strike> Clean Usability: Rapid Prototyping with Bootstrap==

* Shaun Ellis, Princeton University Libraries, shaune@princeton.edu

''"The code itself is unimportant; a project is only as useful as people actually find it." - Linus Torvalds'' [http://bit.ly/p4uuyy]

Usability has been a buzzword for some time now, but what is the process for making the the transition toward a better user experience, and hence, better designed library sites? I will discuss the one facet of the process my team is using to redesign the Finding Aids site for Princeton University Libraries (still in development). The approach involves the use of rapid prototyping, with Bootstrap [http://twitter.github.com/bootstrap/], to make sure we are on track with what users and stakeholders expect up front, and throughout the development process.

Because Bootstrap allows for early and iterative user feedback, it is more effective than the historic Photoshop mockups/wireframe technique. The Photoshop approach allows stakeholders to test the look, but not the feel -- and often leaves developers scratching their heads. Being a CSS/HTML/Javascript grid-based framework, Bootstrap makes it easy for anyone with a bit of HTML/CSS chops to quickly build slick, interactive prototypes right in the browser -- tangible solutions which can be shared, evaluated, revised, and followed by all stakeholders (see Minimum Viable Products [http://en.wikipedia.org/wiki/Minimum_viable_product]). Efficiency is multiplied because the customized prototypes can flow directly into production use, as is the goal with iterative development approaches, such as the Agile methodology.

While Bootstrap is not the only framework that offers grid-based layout, development is expedited and usability is enhanced by Bootstraps use of of "prefabbed" conventional UI patterns, clean typography, and lean Javascript for interactivity. Furthermore, out-of-the box Bootstrap comes in a fairly neutral palette, so focus remains on usability, and does not devolve into premature discussions of color or branding choices. Finally, using Less can be a powerful tool in conjunction with Bootstrap, but is not necessary. I will discuss the pros and cons, and offer examples for how to getting up and running with or without Less.

==Search Engine Relevancy Tuning - A Static Rank Framework for Solr/Lucene==

* Mike Schultz, Amazon.com (formerly Summon Search Architect) mike.schultz@gmail.com

Solr/Lucene provides a lot of flexibility for adjusting relevancy scoring and improving search results. Roughly speaking there are two areas of concern: Firstly, a 'dynamic rank' calculation that is a function of the user query and document text fields. And secondly, a 'static rank' which is independent of the query and generally is a function of non-text document metadata. In this talk I will outline an easily understood, hand-tunable static rank system with a minimal number of parameters.

The obvious major feature of a search engine is to return results relevant to a user query. Perhaps less obvious is the huge role query independent document features play in achieving that. Google's PageRank is an example of a static ranking of web pages based on links and other secret sauce. In the Summon service, our 800 million documents have features like publication date, document type, citation count and Boolean features like the-article-is-peer-reviewed. These fields aren't textual and remain 'static' from query to query, but need to influence a document's relevancy score. In our search results, with all query related features being equal, we'd rather have more recent documents above older ones, Journals above Newspapers, and articles that are peer reviewed above those that are not. The static rank system I will describe achieves this and has the following features:

* Query-time only calculation - nothing is baked into the index - with parameters adjustable at query time.
* The system is based on a signal metaphor where components are 'wired' together. System components allow multiplexing, amplifying, summing, tunable band-pass filtering, string-to-value-mapping all with a bare minimum of parameters.
* An intuitive approach for mixing dynamic and static rank that is more effective than simple adding or multiplying.
* A way of equating disparate static metadata types that leads to understandable results ordering.

==Submitting Digitized Book-like things to the Internet Archive==

* Joel Richard, Smithsonian Institution Libraries, richardjm@si.edu

The Smithsonian Libraries has submitted thousands of out-of-copyright items to the Internet Archive over the years. Specifically in relation to the Biodiversity Heritage Library, we have developed an in-house boutique scanning and upload process that became a learning experience in automated uploading to the Archive. As part of the software development, we created a whitepaper that details the combined learning experiences of the Smithsonian Libraries and the Missouri Botanical Garden. We will discuss some of the the contents of this whitepaper in the context of our scanning process and the manner in which we upload items to the Archive.

Our talk will include a discussion of the types of files and their formats used by the Archive, processes that the Archive performs on uploaded items, ways of interacting and affecting those processes, potential pitfalls and solutions that you may encounter when uploading, and tools that the Archive provides to help monitor and manage your uploaded documents.

Finally, we'll wrap up with a brief summary of how to use things that are on the Internet Archive in your own websites.

== So... you think you want to Host a Code4Lib National Conference, do you? ==

* Elizabeth Duell, Orbis Cascade Alliance, eduell@uoregon.edu

Are you interested in hosting your own Code4Lib Conference? Do you know what it would take? What does BEO stands for? What does F&B Minimum mean? Who would you talk to for support/mentoring? There are so many things to think about: internet support, venue size, rooming blocks, contracts, dietary restrictions and coffee (can't forget the coffee!) just to name a few. Putting together a conference of any size can look daunting, so let's take the scary out of it and replace it with a can do attitude!

Be a step ahead of the game by learning from the people behind the curtain. Ask questions and be given templates/ cheat sheets!

== HTML5 Microdata and Schema.org ==

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

When the big search engines announced support for HTML5 microdata and the schema.org vocabularies, the balance of power for semantic markup in HTML shifted.
* What is microdata?
* Where does microdata fit with regards to other approaches like RDFa and microformats?
* Where do libraries stand in the worldview of Schema.org and what can they do about it?
* How can implementing microdata and schema.org optimize your sites for search engines?
* What tools are available?

== Stack View: A Library Browsing Tool ==

* Annie Cain, Harvard Library Innovation Lab, acain@law.harvard.edu
* Jeff Goldenson, Harvard Library Innovation Lab, jgoldenson@law.harvard.edu

In an effort to recreate and build upon the traditional method of browsing a physical library, we used catalog data, including dimensions and page count, to create a [http://librarylab.law.harvard.edu/projects/stackview/ virtual shelf].

This CSS and JavaScript backed visualization allows items to sit on any number of different shelves, really taking advantage of its digital nature. See how we built Stack View on top of our data and learn how you can create shelves of your own using our open source code.

== “Linked-Data-Ready” Software for Libraries ==

* Jennifer Bowen, University of Rochester River Campus Libraries, jbowen@library.rochester.edu

Linked data is poised to replace MARC as the basis for the new library bibliographic framework. For libraries to benefit from linked data, they must learn about it, experiment with it, demonstrate its usefulness, and take a leadership role in its deployment.

The eXtensible Catalog Organization (XCO) offers open-source software for libraries that is “linked-data-ready.” XC software prepares MARC and Dublin Core metadata for exposure to the semantic web, incorporating FRBR Group 1 entities and registered vocabularies for RDA elements and roles. This presentation will include a software demonstration, proposed software architecture for creation and management of linked data, a vision for how libraries can migrate from MARC to linked data, and an update on XCO progress toward linked data goals.

== How people search the library from a single search box ==

* Cory Lown, North Carolina State University Libraries, cory_lown@ncsu.edu

Searching the library is complex. There's the catalog, article databases, journal title and database title look-ups, the library website, finding aids, knowledge bases, etc. How would users search if they could get to all of these resources from a single search box? I'll share what we've learned about single search at NCSU Libraries by tracking use of QuickSearch (http://www.lib.ncsu.edu/search/index.php?q=aerospace+engineering), our home-grown unified search application. As part of this talk I will suggest low-cost ways to collect real world use data that can be applied to improve search. I will try to convince you that data collection must be carefully planned and designed to be an effective tool to help you understand what your users are telling you through their behavior. I will talk about how the fragmented library resource environment challenges us to provide useful and understandable search environments. Finally, I will share findings from analyzing millions of user transactions about how people search the library from a production single search box at a large university library.

== An Incremental Approach to Archival Description and Access ==

* Chela Scott Weber, New York University Libraries, chelascott@gmail.com
* Mark A. Matienzo, Yale University Library, mark@matienzo.org

''This is placeholder text; description coming shortly''

== Making the Easy Things Easy: A Generic ILS API ==

* Wayne Schneider, Hennepin County Library, wschneider@hclib.org

Some stuff we try to do is complicated, because, let's face it, library data is hard. Some stuff, on the other hand, should be easy. Given an item identifier, I should be able to look at item availability. Given a title identifier, I should be able to place a request. And no, I shouldn't have to parse through the NCIP specification or write a SIP client to do it.

This talk will present work we have done on a web services approach to an API for traditional library transactional data, including example applications.

== Your Catalog in Linked Data==

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

Linked Library Data activity over the last year has seen bibliographic data sets and vocabularies proliferating from traditional library
sources. We've reached a point where regular libraries don't have to go it alone to be on the Semantic Web. There is a quickly growing pool of things we can actually ''link to'', and everyone's existing data can be immediately enriched by participating.

This is quick and dirty road to getting your catalog onto the Linked Data web. The talk will take you from start to finish, using Free Software tools to establish a namespace, put up a SPARQL endpoint, make a simple data model, convert MARC records to RDF, and link the results to major existing data sets (skipping conveniently over pesky processing time). A small amount of "why linked data?" content will be covered, but the primary goal is to leave you able to reproduce the process and start linking your catalog into the web of data. Appropriate documentation will be on the web.

== Integrating Library Systems and Services into Learning Management Systems using Basic LTI ==

* David Walker, California State University, dwalker@calstate.edu

The integration of library resources into learning management systems (LMS) has long been something of a holy grail for academic libraries. The ability to deliver targeted library systems and services to students and faculty within the context of a specific course could greatly simplify access to library resources. Yet, the technical barriers to achieving that goal have to date been formidable.

The recently released Learning Tool Interoperability (LTI) protocol, developed by IMS, now greatly simplifies this process by allowing libraries (and others) to develop and maintain “tools” that function like a native plugin or building block within the LMS, but ultimately live outside of it. In this presentation, David will provide an overview of Basic LTI, a simplified subset (or profile) of the wider LTI protocol, showing how libraries can use this to easily integrate their external systems into any major LMS. He’ll showcase the work Cal State has done to do just that.

[[Category: Code4Lib2012]]

2012 talks proposals

2011-11-16T19:06:57Z

Tjohnson: /* Your Catalog in Linked Data */

Deadline for talk submission is ''Sunday, November 20''.

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
* diversity of topics

Please follow the formatting guidelines:

<pre>

== Talk Title: ==

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

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

== VuFind 2.0: Why and How? ==

* Demian Katz, Villanova University, demian.katz@villanova.edu

A major new version of the VuFind discovery software is currently in development. While VuFind 1.x remains extremely popular, some of its components are beginning to show their age. VuFind 2.0 aims to retain all the strengths of the previous version of the software while making the architecture cleaner, more modern and more standards-based. This presentation will examine the motivation behind the update, preview some of the new features to look forward to, and discuss the challenges of creating a developer-friendly open source package in PHP.

== Open Source Software Registry ==

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

LYRASIS is creating and shepherding a [[Registry_E-R_Diagram|registry of library open source software]] as part of its [http://www.lyrasis.org/News/Press-Releases/2011/LYRASIS-Receives-Grant-to-Support-Open-Source.aspx grant from the Mellon Foundation to support the adoption of open source software by libraries].
The goal of the grant is to help libraries of all types determine if open source software is right for them, and what combination of software, hosting, training, and consulting works for their situation.
The registry is intended to become a community exchange point and stimulant for growth of the library open source ecosystem by connecting libraries with projects, service providers, and events.

The first half of this session will demonstrate the registry functions and describe how projects and providers can get involved.
The second half of the session will be a brainstorming suggestion of how to expand the functionality and usefulness of the registry.

== Property Graphs And TinkerPop Applications in Digital Libraries ==

* Brian Tingle, California Digital Library, brian.tingle.cdlib.org@gmail.com

[http://www.tinkerpop.com/ TinkerPop] is an open source software development group focusing on technologies in the [http://en.wikipedia.org/wiki/Graph_database graph database] space.
This talk will provide a general introduction to the TinkerPop Graph Stack and the [https://github.com/tinkerpop/gremlin/wiki/Defining-a-Property-Graph property graph model] is uses. The introduction will include code examples and explanations of the property graph models used by the [http://socialarchive.iath.virginia.edu/ Social Networks in Archival Context] project and show how the historical social graph is exposed as a JSON/REST API implemented by a TinkerPop [https://github.com/tinkerpop/rexster rexster] [https://github.com/tinkerpop/rexster-kibbles Kibble] that contains the application's graph theory logic. Other graph database applications possible with TinkerPop such as RDF support, and citation analysis will also be discussed.

== Security in Mind ==

* Erin Germ, United States Naval Academy, Nimitz Library, germ@usna.edu

I would like to talk about security of library software.

Over the Summer, I discovered a critical vulnerability in a vendor’s software that (verified) allowed me to assume any user’s identity for that site, (verified) switch to any user, and to (unverified, meaning I didn’t not perform this as I didn’t want to “hack” another library’s site) assume the role of any user for any other library who used this particular vendor's software.

Within a 3 hour period, I discovered a 2 vulnerabilities: 1) minor one allowing me to access any backups from any library site, and 2) a critical vulnerability. From start to finish, the examination, discovery in the vulnerability, and execution of a working exploit was done in less than 2 hours. The vulnerability was a result of poor cookie implementation. The exploit itself revolved around modifying the cookie, and then altering the browser’s permissions by assuming the role of another user.

I do not intend on stating which vendor it was, but I will show how I was able to perform this. If needed, I can do further research and “investigation” into other vendor's software to see what I can “find”.

''If selected, I will contact the vendor to inform them that I will present about this at C4L2012. I do not intend on releasing the name of the vendor.''

== Search Engines and Libraries ==

* Greg Lindahl, blekko CTO, greg@blekko.com

[https://blekko.com blekko] is a new web-scale search engine which enables end-users to create vertical search engines, through a feature called [http://help.blekko.com/index.php/category/slashtags/ slashtags]. Slashtags can contain as few as 1 or as many as tens of thousands of websites relevant to a narrow or broad topic. We have an extensive set of slashtags curated by a combination of volunteers and an in-house librarian team, or end-users can create and share their own. This talk will cover examples of slashtag creation relevant to libraries, and show how to embed this search into a library website, either using javascript or via our API.

''We have exhibited at a couple of library conferences, and have received a lot of interest. blekko is a free service.''

== Beyond code. Versioning data with Git and Mercurial. ==

* Stephanie Collett, California Digital Library, stephanie.collett@ucop.edu
* Martin Haye, California Digital Library, martin.haye@ucop.edu

Within a relatively short time since their introduction, [http://en.wikipedia.org/wiki/Distributed_Version_Control_System distributed version control systems] (DVCS) like [http://git-scm.com/ Git] and [http://mercurial.selenic.com/ Mercurial] have enjoyed widespread adoption for versioning code. It didn’t take long for the library development community to start discussing the potential for using DVCS within our applications and repositories to version data. After all, many of the features that have made some of these systems popular in the open source community to version code (e.g. lightweight, file-based, compressed, reliable) also make them compelling options for versioning data. And why write an entire versioning system from scratch if a DVCS solution can be a drop-in solution? At the [http://www.cdlib.org/ California Digital Library] (CDL) we’ve started using Git and Mercurial in some of our applications to version data. This has proven effective in some situations and unworkable in others. This presentation will be a practical case study of CDL’s experiences with using DVCS to version data. We will explain how we’re incorporating Git and Mercurial in our applications, describe our successes and failures and consider the issues involved in repurposing these systems for data versioning.

==Design for Developers==

*Lisa Kurt, University of Nevada, Reno, lkurt@unr.edu

Users expect good design. This talk will delve into what makes really great design, what to look for, and how to do it. Learn the principles of great design to take your applications, user interfaces, and projects to a higher level. With years of experience in graphic design and illustration, Lisa will discuss design principles, trends, process, tools, and development. Design examples will be from her own projects as well as a variety from industry. You’ll walk away with design knowledge that you can apply immediately to a variety of applications and a number of top notch go-to resources to get you up and running.

==Building research applications with Mendeley==

William Gunn, Mendeley william.gunn@mendeley.com (@mrgunn)

This is partly a tool talk and partly a big idea one.

Mendeley has built the world's largest open database of research and we've now begun to collect some interesting social metadata around the document metadata. I would like to share with the Code4Lib attendees information about using this resource to do things within your application that have previously been impossible for the library community, or in some cases impossible without expensive database subscriptions. One thing that's now possible is to augment catalog search by surfacing information about content usage, allowing people to not only find things matching a query, but popular things or things read by their colleagues. In addition to augmenting search, you can also use this information to augment discovery. Imagine an online exhibit of artifacts from a newly discovered dig not just linking to papers which discuss the artifact, but linking to really good interesting papers about the place and the people who made the artifacts. So the big idea is, "How will looking at the literature from a broader perspective than simple citation analysis change how research is done and communicated? How can we build tools that make this process easier and faster?" I can show some examples of applications that have been built using the Mendeley and PLoS APIs to begin to address this question, and I can also present results from Mendeley's developer challenge which shows what kinds of applications researchers are looking for, what kind of applications peope are building, and illustrates some interesting places where the two don't overlap.

==Your UI can make or break the application (to the user, anyway)==

* Robin Schaaf, University of Notre Dame, schaaf.4@nd.edu

UI development is hard and too often ends up as an after-thought to computer programmers - if you were a CS major in college I'll bet you didn't have many, if any, design courses. I'll talk about how to involve the users upfront with design and some common pitfalls of this approach. I'll also make a case for why you should do the screen design before a single line of code is written. And I'll throw in some ideas for increasing usability and attractiveness of your web applications. I'd like to make a case study of the UI development of our open source ERMS.

==Why Nobody Knows How Big The Library Really Is - Perspective of a Library Outside Turned Insider==

* Patrick Berry, California State University, Chico, pberry@csuchico.edu

In this talk I would like to bring the perspective of an "outsider" (although an avowed IT insider) to let you know that people don't understand the full scope of the library. As we "rethink education", it is incumbent upon us to help educate our institutions as to the scope of the library. I will present some of the tactics I'm employing to help people outside, and in some cases inside, the library to understand our size and the value we bring to the institution.

==Building a URL Management Module using the Concrete5 Package Architecture==

* David Uspal, Villanova University, david.uspal@villanova.edu

Keeping track of URLs utilized across a large website such as a university library, and keeping that content up to date for subject and course guides, can be a pain, and as an open source shop, we’d like to have open source solution for this issue. For this talk, I intend to detail our solution to this issue by walking step-by-step through the building process for our URL Management module -- including why a new solution was necessary; a quick rundown of our CMS ([http://www.concrete5.org Concrete5], a CMS that isn’t Drupal); utilizing the Concrete5 APIs to isolate our solution from core code (to avoid complications caused by core updates); how our solution was integrated into the CMS architecture for easy installation; and our future plans on the project.

==Building an NCIP connector to OpenSRF to facilitate resource sharing==

* Jon Scott, Lyrasis, jon_scott@wsu.edu and Kyle Banerjee, Orbis Cascade Alliance, banerjek@uoregon.edu

How do you reverse engineer any protocol to provide a new service? Humans (and worse yet, committees) often design verbose protocols built around use cases that don't line up current reality. To compound difficulties, the contents of protocol containers are not sufficiently defined/predictable and the only assistance available is sketchy documentation and kind individuals on the internet willing to share what they learned via trial by fire.

NCIP (Niso Circulation Interchange Protocol) is an open standard that defines a set of messages to support exchange of circulation data between disparate circulation, interlibrary loan, and related applications -- widespread adoption of NCIP would eliminate huge amounts of duplicate processing in separate systems.

This presentation discusses how we learned enough about NCIP and OpenSRF from scratch to build an NCIP responder for Evergreen to facilitate resource sharing in a large consortium that relies on over 20 different ILSes.

==Practical Agile: What's Working for Stanford, Blacklight, and Hydra==

* Naomi Dushay, Stanford University Libraries, ndushay@stanford.edu

Agile development techniques can be difficult to adopt in the context of library software development. Maybe your shop has only one or two developers, or you always have too many simultaneous projects. Maybe your new projects can’t be started until 27 librarians reach consensus on the specifications.

This talk will present successful Agile- and Silicon-Valley-inspired practices we’ve adopted at Stanford and/or in the Blacklight and Hydra projects. We’ve targeted developer happiness as well as improved productivity with our recent changes. User stories, dead week, sight lines … it’ll be a grab bag of goodies to bring back to your institution, including some ideas on how to adopt these practices without overt management buy in.

==Quick and <strike>Dirty</strike> Clean Usability: Rapid Prototyping with Bootstrap==

* Shaun Ellis, Princeton University Libraries, shaune@princeton.edu

''"The code itself is unimportant; a project is only as useful as people actually find it." - Linus Torvalds'' [http://bit.ly/p4uuyy]

Usability has been a buzzword for some time now, but what is the process for making the the transition toward a better user experience, and hence, better designed library sites? I will discuss the one facet of the process my team is using to redesign the Finding Aids site for Princeton University Libraries (still in development). The approach involves the use of rapid prototyping, with Bootstrap [http://twitter.github.com/bootstrap/], to make sure we are on track with what users and stakeholders expect up front, and throughout the development process.

Because Bootstrap allows for early and iterative user feedback, it is more effective than the historic Photoshop mockups/wireframe technique. The Photoshop approach allows stakeholders to test the look, but not the feel -- and often leaves developers scratching their heads. Being a CSS/HTML/Javascript grid-based framework, Bootstrap makes it easy for anyone with a bit of HTML/CSS chops to quickly build slick, interactive prototypes right in the browser -- tangible solutions which can be shared, evaluated, revised, and followed by all stakeholders (see Minimum Viable Products [http://en.wikipedia.org/wiki/Minimum_viable_product]). Efficiency is multiplied because the customized prototypes can flow directly into production use, as is the goal with iterative development approaches, such as the Agile methodology.

While Bootstrap is not the only framework that offers grid-based layout, development is expedited and usability is enhanced by Bootstraps use of of "prefabbed" conventional UI patterns, clean typography, and lean Javascript for interactivity. Furthermore, out-of-the box Bootstrap comes in a fairly neutral palette, so focus remains on usability, and does not devolve into premature discussions of color or branding choices. Finally, using Less can be a powerful tool in conjunction with Bootstrap, but is not necessary. I will discuss the pros and cons, and offer examples for how to getting up and running with or without Less.

==Search Engine Relevancy Tuning - A Static Rank Framework for Solr/Lucene==

* Mike Schultz, Amazon.com (formerly Summon Search Architect) mike.schultz@gmail.com

Solr/Lucene provides a lot of flexibility for adjusting relevancy scoring and improving search results. Roughly speaking there are two areas of concern: Firstly, a 'dynamic rank' calculation that is a function of the user query and document text fields. And secondly, a 'static rank' which is independent of the query and generally is a function of non-text document metadata. In this talk I will outline an easily understood, hand-tunable static rank system with a minimal number of parameters.

The obvious major feature of a search engine is to return results relevant to a user query. Perhaps less obvious is the huge role query independent document features play in achieving that. Google's PageRank is an example of a static ranking of web pages based on links and other secret sauce. In the Summon service, our 800 million documents have features like publication date, document type, citation count and Boolean features like the-article-is-peer-reviewed. These fields aren't textual and remain 'static' from query to query, but need to influence a document's relevancy score. In our search results, with all query related features being equal, we'd rather have more recent documents above older ones, Journals above Newspapers, and articles that are peer reviewed above those that are not. The static rank system I will describe achieves this and has the following features:

* Query-time only calculation - nothing is baked into the index - with parameters adjustable at query time.
* The system is based on a signal metaphor where components are 'wired' together. System components allow multiplexing, amplifying, summing, tunable band-pass filtering, string-to-value-mapping all with a bare minimum of parameters.
* An intuitive approach for mixing dynamic and static rank that is more effective than simple adding or multiplying.
* A way of equating disparate static metadata types that leads to understandable results ordering.

==Submitting Digitized Book-like things to the Internet Archive==

* Joel Richard, Smithsonian Institution Libraries, richardjm@si.edu

The Smithsonian Libraries has submitted thousands of out-of-copyright items to the Internet Archive over the years. Specifically in relation to the Biodiversity Heritage Library, we have developed an in-house boutique scanning and upload process that became a learning experience in automated uploading to the Archive. As part of the software development, we created a whitepaper that details the combined learning experiences of the Smithsonian Libraries and the Missouri Botanical Garden. We will discuss some of the the contents of this whitepaper in the context of our scanning process and the manner in which we upload items to the Archive.

Our talk will include a discussion of the types of files and their formats used by the Archive, processes that the Archive performs on uploaded items, ways of interacting and affecting those processes, potential pitfalls and solutions that you may encounter when uploading, and tools that the Archive provides to help monitor and manage your uploaded documents.

Finally, we'll wrap up with a brief summary of how to use things that are on the Internet Archive in your own websites.

== So... you think you want to Host a Code4Lib National Conference, do you? ==

* Elizabeth Duell, Orbis Cascade Alliance, eduell@uoregon.edu

Are you interested in hosting your own Code4Lib Conference? Do you know what it would take? What does BEO stands for? What does F&B Minimum mean? Who would you talk to for support/mentoring? There are so many things to think about: internet support, venue size, rooming blocks, contracts, dietary restrictions and coffee (can't forget the coffee!) just to name a few. Putting together a conference of any size can look daunting, so let's take the scary out of it and replace it with a can do attitude!

Be a step ahead of the game by learning from the people behind the curtain. Ask questions and be given templates/ cheat sheets!

== HTML5 Microdata and Schema.org ==

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

When the big search engines announced support for HTML5 microdata and the schema.org vocabularies, the balance of power for semantic markup in HTML shifted.
* What is microdata?
* Where does microdata fit with regards to other approaches like RDFa and microformats?
* Where do libraries stand in the worldview of Schema.org and what can they do about it?
* How can implementing microdata and schema.org optimize your sites for search engines?
* What tools are available?

== Stack View: A Library Browsing Tool ==

* Annie Cain, Harvard Library Innovation Lab, acain@law.harvard.edu
* Jeff Goldenson, Harvard Library Innovation Lab, jgoldenson@law.harvard.edu

In an effort to recreate and build upon the traditional method of browsing a physical library, we used catalog data, including dimensions and page count, to create a [http://librarylab.law.harvard.edu/projects/stackview/ virtual shelf].

This CSS and JavaScript backed visualization allows items to sit on any number of different shelves, really taking advantage of its digital nature. See how we built Stack View on top of our data and learn how you can create shelves of your own using our open source code.

== “Linked-Data-Ready” Software for Libraries ==

* Jennifer Bowen, University of Rochester River Campus Libraries, jbowen@library.rochester.edu

Linked data is poised to replace MARC as the basis for the new library bibliographic framework. For libraries to benefit from linked data, they must learn about it, experiment with it, demonstrate its usefulness, and take a leadership role in its deployment.

The eXtensible Catalog Organization (XCO) offers open-source software for libraries that is “linked-data-ready.” XC software prepares MARC and Dublin Core metadata for exposure to the semantic web, incorporating FRBR Group 1 entities and registered vocabularies for RDA elements and roles. This presentation will include a software demonstration, proposed software architecture for creation and management of linked data, a vision for how libraries can migrate from MARC to linked data, and an update on XCO progress toward linked data goals.

== How people search the library from a single search box ==

* Cory Lown, North Carolina State University Libraries, cory_lown@ncsu.edu

Searching the library is complex. There's the catalog, article databases, journal title and database title look-ups, the library website, finding aids, knowledge bases, etc. How would users search if they could get to all of these resources from a single search box? I'll share what we've learned about single search at NCSU Libraries by tracking use of QuickSearch (http://www.lib.ncsu.edu/search/index.php?q=aerospace+engineering), our home-grown unified search application. As part of this talk I will suggest low-cost ways to collect real world use data that can be applied to improve search. I will try to convince you that data collection must be carefully planned and designed to be an effective tool to help you understand what your users are telling you through their behavior. I will talk about how the fragmented library resource environment challenges us to provide useful and understandable search environments. Finally, I will share findings from analyzing millions of user transactions about how people search the library from a production single search box at a large university library.

== An Incremental Approach to Archival Description and Access ==

* Chela Scott Weber, New York University Libraries, chelascott@gmail.com
* Mark A. Matienzo, Yale University Library, mark@matienzo.org

''This is placeholder text; description coming shortly''

== Making the Easy Things Easy: A Generic ILS API ==

* Wayne Schneider, Hennepin County Library, wschneider@hclib.org

Some stuff we try to do is complicated, because, let's face it, library data is hard. Some stuff, on the other hand, should be easy. Given an item identifier, I should be able to look at item availability. Given a title identifier, I should be able to place a request. And no, I shouldn't have to parse through the NCIP specification or write a SIP client to do it.

This talk will present work we have done on a web services approach to an API for traditional library transactional data, including example applications.

== Your Catalog in Linked Data==

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

Linked Library Data activity over the last year has seen bibliographic data sets and vocabularies proliferating from traditional library
sources. We've reached a point where regular libraries don't have to go it alone to be on the Semantic Web. There is a quickly growing pool of things we can actually ''link to'', and everyone's existing data can be immediately enriched by participating.

This is quick and dirty road to getting your catalog onto the Linked Data web. The talk take you from start to finish, using Free Software
tools to establish a namespace, put up a SPARQL endpoint, make a simple data model, convert MARC records to RDF, and link the results to major existing data sets (skipping conveniently over pesky processing time). A small amount of "why linked data?" content will be covered, but the primary goal is to leave you able to reproduce the process and start linking your catalog into the web of data. Appropriate documentation will be on the web.

== Integrating Library Systems and Services into Learning Management Systems using Basic LTI ==

* David Walker, California State University, dwalker@calstate.edu

The integration of library resources into learning management systems (LMS) has long been something of a holy grail for academic libraries. The ability to deliver targeted library systems and services to students and faculty within the context of a specific course could greatly simplify access to library resources. Yet, the technical barriers to achieving that goal have to date been formidable.

The recently released Learning Tool Interoperability (LTI) protocol, developed by IMS, now greatly simplifies this process by allowing libraries (and others) to develop and maintain “tools” that function like a native plugin or building block within the LMS, but ultimately live outside of it. In this presentation, David will provide an overview of Basic LTI, a simplified subset (or profile) of the wider LTI protocol, showing how libraries can use this to easily integrate their external systems into any major LMS. He’ll showcase the work Cal State has done to do just that.

[[Category: Code4Lib2012]]

2012 talks proposals

2011-11-16T19:05:22Z

Tjohnson: /* Your Catalog in Linked Data */

Deadline for talk submission is ''Sunday, November 20''.

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
* diversity of topics

Please follow the formatting guidelines:

<pre>

== Talk Title: ==

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

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

== VuFind 2.0: Why and How? ==

* Demian Katz, Villanova University, demian.katz@villanova.edu

A major new version of the VuFind discovery software is currently in development. While VuFind 1.x remains extremely popular, some of its components are beginning to show their age. VuFind 2.0 aims to retain all the strengths of the previous version of the software while making the architecture cleaner, more modern and more standards-based. This presentation will examine the motivation behind the update, preview some of the new features to look forward to, and discuss the challenges of creating a developer-friendly open source package in PHP.

== Open Source Software Registry ==

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

LYRASIS is creating and shepherding a [[Registry_E-R_Diagram|registry of library open source software]] as part of its [http://www.lyrasis.org/News/Press-Releases/2011/LYRASIS-Receives-Grant-to-Support-Open-Source.aspx grant from the Mellon Foundation to support the adoption of open source software by libraries].
The goal of the grant is to help libraries of all types determine if open source software is right for them, and what combination of software, hosting, training, and consulting works for their situation.
The registry is intended to become a community exchange point and stimulant for growth of the library open source ecosystem by connecting libraries with projects, service providers, and events.

The first half of this session will demonstrate the registry functions and describe how projects and providers can get involved.
The second half of the session will be a brainstorming suggestion of how to expand the functionality and usefulness of the registry.

== Property Graphs And TinkerPop Applications in Digital Libraries ==

* Brian Tingle, California Digital Library, brian.tingle.cdlib.org@gmail.com

[http://www.tinkerpop.com/ TinkerPop] is an open source software development group focusing on technologies in the [http://en.wikipedia.org/wiki/Graph_database graph database] space.
This talk will provide a general introduction to the TinkerPop Graph Stack and the [https://github.com/tinkerpop/gremlin/wiki/Defining-a-Property-Graph property graph model] is uses. The introduction will include code examples and explanations of the property graph models used by the [http://socialarchive.iath.virginia.edu/ Social Networks in Archival Context] project and show how the historical social graph is exposed as a JSON/REST API implemented by a TinkerPop [https://github.com/tinkerpop/rexster rexster] [https://github.com/tinkerpop/rexster-kibbles Kibble] that contains the application's graph theory logic. Other graph database applications possible with TinkerPop such as RDF support, and citation analysis will also be discussed.

== Security in Mind ==

* Erin Germ, United States Naval Academy, Nimitz Library, germ@usna.edu

I would like to talk about security of library software.

Over the Summer, I discovered a critical vulnerability in a vendor’s software that (verified) allowed me to assume any user’s identity for that site, (verified) switch to any user, and to (unverified, meaning I didn’t not perform this as I didn’t want to “hack” another library’s site) assume the role of any user for any other library who used this particular vendor's software.

Within a 3 hour period, I discovered a 2 vulnerabilities: 1) minor one allowing me to access any backups from any library site, and 2) a critical vulnerability. From start to finish, the examination, discovery in the vulnerability, and execution of a working exploit was done in less than 2 hours. The vulnerability was a result of poor cookie implementation. The exploit itself revolved around modifying the cookie, and then altering the browser’s permissions by assuming the role of another user.

I do not intend on stating which vendor it was, but I will show how I was able to perform this. If needed, I can do further research and “investigation” into other vendor's software to see what I can “find”.

''If selected, I will contact the vendor to inform them that I will present about this at C4L2012. I do not intend on releasing the name of the vendor.''

== Search Engines and Libraries ==

* Greg Lindahl, blekko CTO, greg@blekko.com

[https://blekko.com blekko] is a new web-scale search engine which enables end-users to create vertical search engines, through a feature called [http://help.blekko.com/index.php/category/slashtags/ slashtags]. Slashtags can contain as few as 1 or as many as tens of thousands of websites relevant to a narrow or broad topic. We have an extensive set of slashtags curated by a combination of volunteers and an in-house librarian team, or end-users can create and share their own. This talk will cover examples of slashtag creation relevant to libraries, and show how to embed this search into a library website, either using javascript or via our API.

''We have exhibited at a couple of library conferences, and have received a lot of interest. blekko is a free service.''

== Beyond code. Versioning data with Git and Mercurial. ==

* Stephanie Collett, California Digital Library, stephanie.collett@ucop.edu
* Martin Haye, California Digital Library, martin.haye@ucop.edu

Within a relatively short time since their introduction, [http://en.wikipedia.org/wiki/Distributed_Version_Control_System distributed version control systems] (DVCS) like [http://git-scm.com/ Git] and [http://mercurial.selenic.com/ Mercurial] have enjoyed widespread adoption for versioning code. It didn’t take long for the library development community to start discussing the potential for using DVCS within our applications and repositories to version data. After all, many of the features that have made some of these systems popular in the open source community to version code (e.g. lightweight, file-based, compressed, reliable) also make them compelling options for versioning data. And why write an entire versioning system from scratch if a DVCS solution can be a drop-in solution? At the [http://www.cdlib.org/ California Digital Library] (CDL) we’ve started using Git and Mercurial in some of our applications to version data. This has proven effective in some situations and unworkable in others. This presentation will be a practical case study of CDL’s experiences with using DVCS to version data. We will explain how we’re incorporating Git and Mercurial in our applications, describe our successes and failures and consider the issues involved in repurposing these systems for data versioning.

==Design for Developers==

*Lisa Kurt, University of Nevada, Reno, lkurt@unr.edu

Users expect good design. This talk will delve into what makes really great design, what to look for, and how to do it. Learn the principles of great design to take your applications, user interfaces, and projects to a higher level. With years of experience in graphic design and illustration, Lisa will discuss design principles, trends, process, tools, and development. Design examples will be from her own projects as well as a variety from industry. You’ll walk away with design knowledge that you can apply immediately to a variety of applications and a number of top notch go-to resources to get you up and running.

==Building research applications with Mendeley==

William Gunn, Mendeley william.gunn@mendeley.com (@mrgunn)

This is partly a tool talk and partly a big idea one.

Mendeley has built the world's largest open database of research and we've now begun to collect some interesting social metadata around the document metadata. I would like to share with the Code4Lib attendees information about using this resource to do things within your application that have previously been impossible for the library community, or in some cases impossible without expensive database subscriptions. One thing that's now possible is to augment catalog search by surfacing information about content usage, allowing people to not only find things matching a query, but popular things or things read by their colleagues. In addition to augmenting search, you can also use this information to augment discovery. Imagine an online exhibit of artifacts from a newly discovered dig not just linking to papers which discuss the artifact, but linking to really good interesting papers about the place and the people who made the artifacts. So the big idea is, "How will looking at the literature from a broader perspective than simple citation analysis change how research is done and communicated? How can we build tools that make this process easier and faster?" I can show some examples of applications that have been built using the Mendeley and PLoS APIs to begin to address this question, and I can also present results from Mendeley's developer challenge which shows what kinds of applications researchers are looking for, what kind of applications peope are building, and illustrates some interesting places where the two don't overlap.

==Your UI can make or break the application (to the user, anyway)==

* Robin Schaaf, University of Notre Dame, schaaf.4@nd.edu

UI development is hard and too often ends up as an after-thought to computer programmers - if you were a CS major in college I'll bet you didn't have many, if any, design courses. I'll talk about how to involve the users upfront with design and some common pitfalls of this approach. I'll also make a case for why you should do the screen design before a single line of code is written. And I'll throw in some ideas for increasing usability and attractiveness of your web applications. I'd like to make a case study of the UI development of our open source ERMS.

==Why Nobody Knows How Big The Library Really Is - Perspective of a Library Outside Turned Insider==

* Patrick Berry, California State University, Chico, pberry@csuchico.edu

In this talk I would like to bring the perspective of an "outsider" (although an avowed IT insider) to let you know that people don't understand the full scope of the library. As we "rethink education", it is incumbent upon us to help educate our institutions as to the scope of the library. I will present some of the tactics I'm employing to help people outside, and in some cases inside, the library to understand our size and the value we bring to the institution.

==Building a URL Management Module using the Concrete5 Package Architecture==

* David Uspal, Villanova University, david.uspal@villanova.edu

Keeping track of URLs utilized across a large website such as a university library, and keeping that content up to date for subject and course guides, can be a pain, and as an open source shop, we’d like to have open source solution for this issue. For this talk, I intend to detail our solution to this issue by walking step-by-step through the building process for our URL Management module -- including why a new solution was necessary; a quick rundown of our CMS ([http://www.concrete5.org Concrete5], a CMS that isn’t Drupal); utilizing the Concrete5 APIs to isolate our solution from core code (to avoid complications caused by core updates); how our solution was integrated into the CMS architecture for easy installation; and our future plans on the project.

==Building an NCIP connector to OpenSRF to facilitate resource sharing==

* Jon Scott, Lyrasis, jon_scott@wsu.edu and Kyle Banerjee, Orbis Cascade Alliance, banerjek@uoregon.edu

How do you reverse engineer any protocol to provide a new service? Humans (and worse yet, committees) often design verbose protocols built around use cases that don't line up current reality. To compound difficulties, the contents of protocol containers are not sufficiently defined/predictable and the only assistance available is sketchy documentation and kind individuals on the internet willing to share what they learned via trial by fire.

NCIP (Niso Circulation Interchange Protocol) is an open standard that defines a set of messages to support exchange of circulation data between disparate circulation, interlibrary loan, and related applications -- widespread adoption of NCIP would eliminate huge amounts of duplicate processing in separate systems.

This presentation discusses how we learned enough about NCIP and OpenSRF from scratch to build an NCIP responder for Evergreen to facilitate resource sharing in a large consortium that relies on over 20 different ILSes.

==Practical Agile: What's Working for Stanford, Blacklight, and Hydra==

* Naomi Dushay, Stanford University Libraries, ndushay@stanford.edu

Agile development techniques can be difficult to adopt in the context of library software development. Maybe your shop has only one or two developers, or you always have too many simultaneous projects. Maybe your new projects can’t be started until 27 librarians reach consensus on the specifications.

This talk will present successful Agile- and Silicon-Valley-inspired practices we’ve adopted at Stanford and/or in the Blacklight and Hydra projects. We’ve targeted developer happiness as well as improved productivity with our recent changes. User stories, dead week, sight lines … it’ll be a grab bag of goodies to bring back to your institution, including some ideas on how to adopt these practices without overt management buy in.

==Quick and <strike>Dirty</strike> Clean Usability: Rapid Prototyping with Bootstrap==

* Shaun Ellis, Princeton University Libraries, shaune@princeton.edu

''"The code itself is unimportant; a project is only as useful as people actually find it." - Linus Torvalds'' [http://bit.ly/p4uuyy]

Usability has been a buzzword for some time now, but what is the process for making the the transition toward a better user experience, and hence, better designed library sites? I will discuss the one facet of the process my team is using to redesign the Finding Aids site for Princeton University Libraries (still in development). The approach involves the use of rapid prototyping, with Bootstrap [http://twitter.github.com/bootstrap/], to make sure we are on track with what users and stakeholders expect up front, and throughout the development process.

Because Bootstrap allows for early and iterative user feedback, it is more effective than the historic Photoshop mockups/wireframe technique. The Photoshop approach allows stakeholders to test the look, but not the feel -- and often leaves developers scratching their heads. Being a CSS/HTML/Javascript grid-based framework, Bootstrap makes it easy for anyone with a bit of HTML/CSS chops to quickly build slick, interactive prototypes right in the browser -- tangible solutions which can be shared, evaluated, revised, and followed by all stakeholders (see Minimum Viable Products [http://en.wikipedia.org/wiki/Minimum_viable_product]). Efficiency is multiplied because the customized prototypes can flow directly into production use, as is the goal with iterative development approaches, such as the Agile methodology.

While Bootstrap is not the only framework that offers grid-based layout, development is expedited and usability is enhanced by Bootstraps use of of "prefabbed" conventional UI patterns, clean typography, and lean Javascript for interactivity. Furthermore, out-of-the box Bootstrap comes in a fairly neutral palette, so focus remains on usability, and does not devolve into premature discussions of color or branding choices. Finally, using Less can be a powerful tool in conjunction with Bootstrap, but is not necessary. I will discuss the pros and cons, and offer examples for how to getting up and running with or without Less.

==Search Engine Relevancy Tuning - A Static Rank Framework for Solr/Lucene==

* Mike Schultz, Amazon.com (formerly Summon Search Architect) mike.schultz@gmail.com

Solr/Lucene provides a lot of flexibility for adjusting relevancy scoring and improving search results. Roughly speaking there are two areas of concern: Firstly, a 'dynamic rank' calculation that is a function of the user query and document text fields. And secondly, a 'static rank' which is independent of the query and generally is a function of non-text document metadata. In this talk I will outline an easily understood, hand-tunable static rank system with a minimal number of parameters.

The obvious major feature of a search engine is to return results relevant to a user query. Perhaps less obvious is the huge role query independent document features play in achieving that. Google's PageRank is an example of a static ranking of web pages based on links and other secret sauce. In the Summon service, our 800 million documents have features like publication date, document type, citation count and Boolean features like the-article-is-peer-reviewed. These fields aren't textual and remain 'static' from query to query, but need to influence a document's relevancy score. In our search results, with all query related features being equal, we'd rather have more recent documents above older ones, Journals above Newspapers, and articles that are peer reviewed above those that are not. The static rank system I will describe achieves this and has the following features:

* Query-time only calculation - nothing is baked into the index - with parameters adjustable at query time.
* The system is based on a signal metaphor where components are 'wired' together. System components allow multiplexing, amplifying, summing, tunable band-pass filtering, string-to-value-mapping all with a bare minimum of parameters.
* An intuitive approach for mixing dynamic and static rank that is more effective than simple adding or multiplying.
* A way of equating disparate static metadata types that leads to understandable results ordering.

==Submitting Digitized Book-like things to the Internet Archive==

* Joel Richard, Smithsonian Institution Libraries, richardjm@si.edu

The Smithsonian Libraries has submitted thousands of out-of-copyright items to the Internet Archive over the years. Specifically in relation to the Biodiversity Heritage Library, we have developed an in-house boutique scanning and upload process that became a learning experience in automated uploading to the Archive. As part of the software development, we created a whitepaper that details the combined learning experiences of the Smithsonian Libraries and the Missouri Botanical Garden. We will discuss some of the the contents of this whitepaper in the context of our scanning process and the manner in which we upload items to the Archive.

Our talk will include a discussion of the types of files and their formats used by the Archive, processes that the Archive performs on uploaded items, ways of interacting and affecting those processes, potential pitfalls and solutions that you may encounter when uploading, and tools that the Archive provides to help monitor and manage your uploaded documents.

Finally, we'll wrap up with a brief summary of how to use things that are on the Internet Archive in your own websites.

== So... you think you want to Host a Code4Lib National Conference, do you? ==

* Elizabeth Duell, Orbis Cascade Alliance, eduell@uoregon.edu

Are you interested in hosting your own Code4Lib Conference? Do you know what it would take? What does BEO stands for? What does F&B Minimum mean? Who would you talk to for support/mentoring? There are so many things to think about: internet support, venue size, rooming blocks, contracts, dietary restrictions and coffee (can't forget the coffee!) just to name a few. Putting together a conference of any size can look daunting, so let's take the scary out of it and replace it with a can do attitude!

Be a step ahead of the game by learning from the people behind the curtain. Ask questions and be given templates/ cheat sheets!

== HTML5 Microdata and Schema.org ==

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

When the big search engines announced support for HTML5 microdata and the schema.org vocabularies, the balance of power for semantic markup in HTML shifted.
* What is microdata?
* Where does microdata fit with regards to other approaches like RDFa and microformats?
* Where do libraries stand in the worldview of Schema.org and what can they do about it?
* How can implementing microdata and schema.org optimize your sites for search engines?
* What tools are available?

== Stack View: A Library Browsing Tool ==

* Annie Cain, Harvard Library Innovation Lab, acain@law.harvard.edu
* Jeff Goldenson, Harvard Library Innovation Lab, jgoldenson@law.harvard.edu

In an effort to recreate and build upon the traditional method of browsing a physical library, we used catalog data, including dimensions and page count, to create a [http://librarylab.law.harvard.edu/projects/stackview/ virtual shelf].

This CSS and JavaScript backed visualization allows items to sit on any number of different shelves, really taking advantage of its digital nature. See how we built Stack View on top of our data and learn how you can create shelves of your own using our open source code.

== “Linked-Data-Ready” Software for Libraries ==

* Jennifer Bowen, University of Rochester River Campus Libraries, jbowen@library.rochester.edu

Linked data is poised to replace MARC as the basis for the new library bibliographic framework. For libraries to benefit from linked data, they must learn about it, experiment with it, demonstrate its usefulness, and take a leadership role in its deployment.

The eXtensible Catalog Organization (XCO) offers open-source software for libraries that is “linked-data-ready.” XC software prepares MARC and Dublin Core metadata for exposure to the semantic web, incorporating FRBR Group 1 entities and registered vocabularies for RDA elements and roles. This presentation will include a software demonstration, proposed software architecture for creation and management of linked data, a vision for how libraries can migrate from MARC to linked data, and an update on XCO progress toward linked data goals.

== How people search the library from a single search box ==

* Cory Lown, North Carolina State University Libraries, cory_lown@ncsu.edu

Searching the library is complex. There's the catalog, article databases, journal title and database title look-ups, the library website, finding aids, knowledge bases, etc. How would users search if they could get to all of these resources from a single search box? I'll share what we've learned about single search at NCSU Libraries by tracking use of QuickSearch (http://www.lib.ncsu.edu/search/index.php?q=aerospace+engineering), our home-grown unified search application. As part of this talk I will suggest low-cost ways to collect real world use data that can be applied to improve search. I will try to convince you that data collection must be carefully planned and designed to be an effective tool to help you understand what your users are telling you through their behavior. I will talk about how the fragmented library resource environment challenges us to provide useful and understandable search environments. Finally, I will share findings from analyzing millions of user transactions about how people search the library from a production single search box at a large university library.

== An Incremental Approach to Archival Description and Access ==

* Chela Scott Weber, New York University Libraries, chelascott@gmail.com
* Mark A. Matienzo, Yale University Library, mark@matienzo.org

''This is placeholder text; description coming shortly''

== Making the Easy Things Easy: A Generic ILS API ==

* Wayne Schneider, Hennepin County Library, wschneider@hclib.org

Some stuff we try to do is complicated, because, let's face it, library data is hard. Some stuff, on the other hand, should be easy. Given an item identifier, I should be able to look at item availability. Given a title identifier, I should be able to place a request. And no, I shouldn't have to parse through the NCIP specification or write a SIP client to do it.

This talk will present work we have done on a web services approach to an API for traditional library transactional data, including example applications.

== Your Catalog in Linked Data==

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

Linked Library Data activity over the last year has seen bibliographic data sets and vocabularies proliferating from traditional library
sources. We've reached a point where regular libraries don't have to go it alone to be on the Semantic Web. There is a quickly growing pool of things we can actually ''link to'', and everyone's existing data can be immediately enriched by participating.

This is quick and dirty road to getting your catalog onto the Linked Data web. The talk take you from start to finish, using Free Software
tools to establish a namespace, put up a SPARQL endpoint, make a simple data model, convert MARC records to RDF, and link the results to major existing data sets (skipping conveniently over pesky processing time).

A small amount of "why linked data?" content will be covered, but the primary goal is to leave you able to reproduce the process and
start linking your catalog into the web of data. Appropriate documentation will be on the web.

[[Category: Code4Lib2012]]

2012 talks proposals

2011-11-16T19:04:35Z

Tjohnson: /* Your Catalog in Linked Data */

Deadline for talk submission is ''Sunday, November 20''.

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
* diversity of topics

Please follow the formatting guidelines:

<pre>

== Talk Title: ==

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

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

== VuFind 2.0: Why and How? ==

* Demian Katz, Villanova University, demian.katz@villanova.edu

A major new version of the VuFind discovery software is currently in development. While VuFind 1.x remains extremely popular, some of its components are beginning to show their age. VuFind 2.0 aims to retain all the strengths of the previous version of the software while making the architecture cleaner, more modern and more standards-based. This presentation will examine the motivation behind the update, preview some of the new features to look forward to, and discuss the challenges of creating a developer-friendly open source package in PHP.

== Open Source Software Registry ==

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

LYRASIS is creating and shepherding a [[Registry_E-R_Diagram|registry of library open source software]] as part of its [http://www.lyrasis.org/News/Press-Releases/2011/LYRASIS-Receives-Grant-to-Support-Open-Source.aspx grant from the Mellon Foundation to support the adoption of open source software by libraries].
The goal of the grant is to help libraries of all types determine if open source software is right for them, and what combination of software, hosting, training, and consulting works for their situation.
The registry is intended to become a community exchange point and stimulant for growth of the library open source ecosystem by connecting libraries with projects, service providers, and events.

The first half of this session will demonstrate the registry functions and describe how projects and providers can get involved.
The second half of the session will be a brainstorming suggestion of how to expand the functionality and usefulness of the registry.

== Property Graphs And TinkerPop Applications in Digital Libraries ==

* Brian Tingle, California Digital Library, brian.tingle.cdlib.org@gmail.com

[http://www.tinkerpop.com/ TinkerPop] is an open source software development group focusing on technologies in the [http://en.wikipedia.org/wiki/Graph_database graph database] space.
This talk will provide a general introduction to the TinkerPop Graph Stack and the [https://github.com/tinkerpop/gremlin/wiki/Defining-a-Property-Graph property graph model] is uses. The introduction will include code examples and explanations of the property graph models used by the [http://socialarchive.iath.virginia.edu/ Social Networks in Archival Context] project and show how the historical social graph is exposed as a JSON/REST API implemented by a TinkerPop [https://github.com/tinkerpop/rexster rexster] [https://github.com/tinkerpop/rexster-kibbles Kibble] that contains the application's graph theory logic. Other graph database applications possible with TinkerPop such as RDF support, and citation analysis will also be discussed.

== Security in Mind ==

* Erin Germ, United States Naval Academy, Nimitz Library, germ@usna.edu

I would like to talk about security of library software.

Over the Summer, I discovered a critical vulnerability in a vendor’s software that (verified) allowed me to assume any user’s identity for that site, (verified) switch to any user, and to (unverified, meaning I didn’t not perform this as I didn’t want to “hack” another library’s site) assume the role of any user for any other library who used this particular vendor's software.

Within a 3 hour period, I discovered a 2 vulnerabilities: 1) minor one allowing me to access any backups from any library site, and 2) a critical vulnerability. From start to finish, the examination, discovery in the vulnerability, and execution of a working exploit was done in less than 2 hours. The vulnerability was a result of poor cookie implementation. The exploit itself revolved around modifying the cookie, and then altering the browser’s permissions by assuming the role of another user.

I do not intend on stating which vendor it was, but I will show how I was able to perform this. If needed, I can do further research and “investigation” into other vendor's software to see what I can “find”.

''If selected, I will contact the vendor to inform them that I will present about this at C4L2012. I do not intend on releasing the name of the vendor.''

== Search Engines and Libraries ==

* Greg Lindahl, blekko CTO, greg@blekko.com

[https://blekko.com blekko] is a new web-scale search engine which enables end-users to create vertical search engines, through a feature called [http://help.blekko.com/index.php/category/slashtags/ slashtags]. Slashtags can contain as few as 1 or as many as tens of thousands of websites relevant to a narrow or broad topic. We have an extensive set of slashtags curated by a combination of volunteers and an in-house librarian team, or end-users can create and share their own. This talk will cover examples of slashtag creation relevant to libraries, and show how to embed this search into a library website, either using javascript or via our API.

''We have exhibited at a couple of library conferences, and have received a lot of interest. blekko is a free service.''

== Beyond code. Versioning data with Git and Mercurial. ==

* Stephanie Collett, California Digital Library, stephanie.collett@ucop.edu
* Martin Haye, California Digital Library, martin.haye@ucop.edu

Within a relatively short time since their introduction, [http://en.wikipedia.org/wiki/Distributed_Version_Control_System distributed version control systems] (DVCS) like [http://git-scm.com/ Git] and [http://mercurial.selenic.com/ Mercurial] have enjoyed widespread adoption for versioning code. It didn’t take long for the library development community to start discussing the potential for using DVCS within our applications and repositories to version data. After all, many of the features that have made some of these systems popular in the open source community to version code (e.g. lightweight, file-based, compressed, reliable) also make them compelling options for versioning data. And why write an entire versioning system from scratch if a DVCS solution can be a drop-in solution? At the [http://www.cdlib.org/ California Digital Library] (CDL) we’ve started using Git and Mercurial in some of our applications to version data. This has proven effective in some situations and unworkable in others. This presentation will be a practical case study of CDL’s experiences with using DVCS to version data. We will explain how we’re incorporating Git and Mercurial in our applications, describe our successes and failures and consider the issues involved in repurposing these systems for data versioning.

==Design for Developers==

*Lisa Kurt, University of Nevada, Reno, lkurt@unr.edu

Users expect good design. This talk will delve into what makes really great design, what to look for, and how to do it. Learn the principles of great design to take your applications, user interfaces, and projects to a higher level. With years of experience in graphic design and illustration, Lisa will discuss design principles, trends, process, tools, and development. Design examples will be from her own projects as well as a variety from industry. You’ll walk away with design knowledge that you can apply immediately to a variety of applications and a number of top notch go-to resources to get you up and running.

==Building research applications with Mendeley==

William Gunn, Mendeley william.gunn@mendeley.com (@mrgunn)

This is partly a tool talk and partly a big idea one.

Mendeley has built the world's largest open database of research and we've now begun to collect some interesting social metadata around the document metadata. I would like to share with the Code4Lib attendees information about using this resource to do things within your application that have previously been impossible for the library community, or in some cases impossible without expensive database subscriptions. One thing that's now possible is to augment catalog search by surfacing information about content usage, allowing people to not only find things matching a query, but popular things or things read by their colleagues. In addition to augmenting search, you can also use this information to augment discovery. Imagine an online exhibit of artifacts from a newly discovered dig not just linking to papers which discuss the artifact, but linking to really good interesting papers about the place and the people who made the artifacts. So the big idea is, "How will looking at the literature from a broader perspective than simple citation analysis change how research is done and communicated? How can we build tools that make this process easier and faster?" I can show some examples of applications that have been built using the Mendeley and PLoS APIs to begin to address this question, and I can also present results from Mendeley's developer challenge which shows what kinds of applications researchers are looking for, what kind of applications peope are building, and illustrates some interesting places where the two don't overlap.

==Your UI can make or break the application (to the user, anyway)==

* Robin Schaaf, University of Notre Dame, schaaf.4@nd.edu

UI development is hard and too often ends up as an after-thought to computer programmers - if you were a CS major in college I'll bet you didn't have many, if any, design courses. I'll talk about how to involve the users upfront with design and some common pitfalls of this approach. I'll also make a case for why you should do the screen design before a single line of code is written. And I'll throw in some ideas for increasing usability and attractiveness of your web applications. I'd like to make a case study of the UI development of our open source ERMS.

==Why Nobody Knows How Big The Library Really Is - Perspective of a Library Outside Turned Insider==

* Patrick Berry, California State University, Chico, pberry@csuchico.edu

In this talk I would like to bring the perspective of an "outsider" (although an avowed IT insider) to let you know that people don't understand the full scope of the library. As we "rethink education", it is incumbent upon us to help educate our institutions as to the scope of the library. I will present some of the tactics I'm employing to help people outside, and in some cases inside, the library to understand our size and the value we bring to the institution.

==Building a URL Management Module using the Concrete5 Package Architecture==

* David Uspal, Villanova University, david.uspal@villanova.edu

Keeping track of URLs utilized across a large website such as a university library, and keeping that content up to date for subject and course guides, can be a pain, and as an open source shop, we’d like to have open source solution for this issue. For this talk, I intend to detail our solution to this issue by walking step-by-step through the building process for our URL Management module -- including why a new solution was necessary; a quick rundown of our CMS ([http://www.concrete5.org Concrete5], a CMS that isn’t Drupal); utilizing the Concrete5 APIs to isolate our solution from core code (to avoid complications caused by core updates); how our solution was integrated into the CMS architecture for easy installation; and our future plans on the project.

==Building an NCIP connector to OpenSRF to facilitate resource sharing==

* Jon Scott, Lyrasis, jon_scott@wsu.edu and Kyle Banerjee, Orbis Cascade Alliance, banerjek@uoregon.edu

How do you reverse engineer any protocol to provide a new service? Humans (and worse yet, committees) often design verbose protocols built around use cases that don't line up current reality. To compound difficulties, the contents of protocol containers are not sufficiently defined/predictable and the only assistance available is sketchy documentation and kind individuals on the internet willing to share what they learned via trial by fire.

NCIP (Niso Circulation Interchange Protocol) is an open standard that defines a set of messages to support exchange of circulation data between disparate circulation, interlibrary loan, and related applications -- widespread adoption of NCIP would eliminate huge amounts of duplicate processing in separate systems.

This presentation discusses how we learned enough about NCIP and OpenSRF from scratch to build an NCIP responder for Evergreen to facilitate resource sharing in a large consortium that relies on over 20 different ILSes.

==Practical Agile: What's Working for Stanford, Blacklight, and Hydra==

* Naomi Dushay, Stanford University Libraries, ndushay@stanford.edu

Agile development techniques can be difficult to adopt in the context of library software development. Maybe your shop has only one or two developers, or you always have too many simultaneous projects. Maybe your new projects can’t be started until 27 librarians reach consensus on the specifications.

This talk will present successful Agile- and Silicon-Valley-inspired practices we’ve adopted at Stanford and/or in the Blacklight and Hydra projects. We’ve targeted developer happiness as well as improved productivity with our recent changes. User stories, dead week, sight lines … it’ll be a grab bag of goodies to bring back to your institution, including some ideas on how to adopt these practices without overt management buy in.

==Quick and <strike>Dirty</strike> Clean Usability: Rapid Prototyping with Bootstrap==

* Shaun Ellis, Princeton University Libraries, shaune@princeton.edu

''"The code itself is unimportant; a project is only as useful as people actually find it." - Linus Torvalds'' [http://bit.ly/p4uuyy]

Usability has been a buzzword for some time now, but what is the process for making the the transition toward a better user experience, and hence, better designed library sites? I will discuss the one facet of the process my team is using to redesign the Finding Aids site for Princeton University Libraries (still in development). The approach involves the use of rapid prototyping, with Bootstrap [http://twitter.github.com/bootstrap/], to make sure we are on track with what users and stakeholders expect up front, and throughout the development process.

Because Bootstrap allows for early and iterative user feedback, it is more effective than the historic Photoshop mockups/wireframe technique. The Photoshop approach allows stakeholders to test the look, but not the feel -- and often leaves developers scratching their heads. Being a CSS/HTML/Javascript grid-based framework, Bootstrap makes it easy for anyone with a bit of HTML/CSS chops to quickly build slick, interactive prototypes right in the browser -- tangible solutions which can be shared, evaluated, revised, and followed by all stakeholders (see Minimum Viable Products [http://en.wikipedia.org/wiki/Minimum_viable_product]). Efficiency is multiplied because the customized prototypes can flow directly into production use, as is the goal with iterative development approaches, such as the Agile methodology.

While Bootstrap is not the only framework that offers grid-based layout, development is expedited and usability is enhanced by Bootstraps use of of "prefabbed" conventional UI patterns, clean typography, and lean Javascript for interactivity. Furthermore, out-of-the box Bootstrap comes in a fairly neutral palette, so focus remains on usability, and does not devolve into premature discussions of color or branding choices. Finally, using Less can be a powerful tool in conjunction with Bootstrap, but is not necessary. I will discuss the pros and cons, and offer examples for how to getting up and running with or without Less.

==Search Engine Relevancy Tuning - A Static Rank Framework for Solr/Lucene==

* Mike Schultz, Amazon.com (formerly Summon Search Architect) mike.schultz@gmail.com

Solr/Lucene provides a lot of flexibility for adjusting relevancy scoring and improving search results. Roughly speaking there are two areas of concern: Firstly, a 'dynamic rank' calculation that is a function of the user query and document text fields. And secondly, a 'static rank' which is independent of the query and generally is a function of non-text document metadata. In this talk I will outline an easily understood, hand-tunable static rank system with a minimal number of parameters.

The obvious major feature of a search engine is to return results relevant to a user query. Perhaps less obvious is the huge role query independent document features play in achieving that. Google's PageRank is an example of a static ranking of web pages based on links and other secret sauce. In the Summon service, our 800 million documents have features like publication date, document type, citation count and Boolean features like the-article-is-peer-reviewed. These fields aren't textual and remain 'static' from query to query, but need to influence a document's relevancy score. In our search results, with all query related features being equal, we'd rather have more recent documents above older ones, Journals above Newspapers, and articles that are peer reviewed above those that are not. The static rank system I will describe achieves this and has the following features:

* Query-time only calculation - nothing is baked into the index - with parameters adjustable at query time.
* The system is based on a signal metaphor where components are 'wired' together. System components allow multiplexing, amplifying, summing, tunable band-pass filtering, string-to-value-mapping all with a bare minimum of parameters.
* An intuitive approach for mixing dynamic and static rank that is more effective than simple adding or multiplying.
* A way of equating disparate static metadata types that leads to understandable results ordering.

==Submitting Digitized Book-like things to the Internet Archive==

* Joel Richard, Smithsonian Institution Libraries, richardjm@si.edu

The Smithsonian Libraries has submitted thousands of out-of-copyright items to the Internet Archive over the years. Specifically in relation to the Biodiversity Heritage Library, we have developed an in-house boutique scanning and upload process that became a learning experience in automated uploading to the Archive. As part of the software development, we created a whitepaper that details the combined learning experiences of the Smithsonian Libraries and the Missouri Botanical Garden. We will discuss some of the the contents of this whitepaper in the context of our scanning process and the manner in which we upload items to the Archive.

Our talk will include a discussion of the types of files and their formats used by the Archive, processes that the Archive performs on uploaded items, ways of interacting and affecting those processes, potential pitfalls and solutions that you may encounter when uploading, and tools that the Archive provides to help monitor and manage your uploaded documents.

Finally, we'll wrap up with a brief summary of how to use things that are on the Internet Archive in your own websites.

== So... you think you want to Host a Code4Lib National Conference, do you? ==

* Elizabeth Duell, Orbis Cascade Alliance, eduell@uoregon.edu

Are you interested in hosting your own Code4Lib Conference? Do you know what it would take? What does BEO stands for? What does F&B Minimum mean? Who would you talk to for support/mentoring? There are so many things to think about: internet support, venue size, rooming blocks, contracts, dietary restrictions and coffee (can't forget the coffee!) just to name a few. Putting together a conference of any size can look daunting, so let's take the scary out of it and replace it with a can do attitude!

Be a step ahead of the game by learning from the people behind the curtain. Ask questions and be given templates/ cheat sheets!

== HTML5 Microdata and Schema.org ==

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

When the big search engines announced support for HTML5 microdata and the schema.org vocabularies, the balance of power for semantic markup in HTML shifted.
* What is microdata?
* Where does microdata fit with regards to other approaches like RDFa and microformats?
* Where do libraries stand in the worldview of Schema.org and what can they do about it?
* How can implementing microdata and schema.org optimize your sites for search engines?
* What tools are available?

== Stack View: A Library Browsing Tool ==

* Annie Cain, Harvard Library Innovation Lab, acain@law.harvard.edu
* Jeff Goldenson, Harvard Library Innovation Lab, jgoldenson@law.harvard.edu

In an effort to recreate and build upon the traditional method of browsing a physical library, we used catalog data, including dimensions and page count, to create a [http://librarylab.law.harvard.edu/projects/stackview/ virtual shelf].

This CSS and JavaScript backed visualization allows items to sit on any number of different shelves, really taking advantage of its digital nature. See how we built Stack View on top of our data and learn how you can create shelves of your own using our open source code.

== “Linked-Data-Ready” Software for Libraries ==

* Jennifer Bowen, University of Rochester River Campus Libraries, jbowen@library.rochester.edu

Linked data is poised to replace MARC as the basis for the new library bibliographic framework. For libraries to benefit from linked data, they must learn about it, experiment with it, demonstrate its usefulness, and take a leadership role in its deployment.

The eXtensible Catalog Organization (XCO) offers open-source software for libraries that is “linked-data-ready.” XC software prepares MARC and Dublin Core metadata for exposure to the semantic web, incorporating FRBR Group 1 entities and registered vocabularies for RDA elements and roles. This presentation will include a software demonstration, proposed software architecture for creation and management of linked data, a vision for how libraries can migrate from MARC to linked data, and an update on XCO progress toward linked data goals.

== How people search the library from a single search box ==

* Cory Lown, North Carolina State University Libraries, cory_lown@ncsu.edu

Searching the library is complex. There's the catalog, article databases, journal title and database title look-ups, the library website, finding aids, knowledge bases, etc. How would users search if they could get to all of these resources from a single search box? I'll share what we've learned about single search at NCSU Libraries by tracking use of QuickSearch (http://www.lib.ncsu.edu/search/index.php?q=aerospace+engineering), our home-grown unified search application. As part of this talk I will suggest low-cost ways to collect real world use data that can be applied to improve search. I will try to convince you that data collection must be carefully planned and designed to be an effective tool to help you understand what your users are telling you through their behavior. I will talk about how the fragmented library resource environment challenges us to provide useful and understandable search environments. Finally, I will share findings from analyzing millions of user transactions about how people search the library from a production single search box at a large university library.

== An Incremental Approach to Archival Description and Access ==

* Chela Scott Weber, New York University Libraries, chelascott@gmail.com
* Mark A. Matienzo, Yale University Library, mark@matienzo.org

''This is placeholder text; description coming shortly''

== Making the Easy Things Easy: A Generic ILS API ==

* Wayne Schneider, Hennepin County Library, wschneider@hclib.org

Some stuff we try to do is complicated, because, let's face it, library data is hard. Some stuff, on the other hand, should be easy. Given an item identifier, I should be able to look at item availability. Given a title identifier, I should be able to place a request. And no, I shouldn't have to parse through the NCIP specification or write a SIP client to do it.

This talk will present work we have done on a web services approach to an API for traditional library transactional data, including example applications.

== Your Catalog in Linked Data==

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

Linked Library Data activity over the last year has seen bibliographic data sets and vocabularies proliferating from traditional library
sources. We've reached a point where regular libraries don't have to go it alone to be on the Semantic Web--there's a quickly growing pool
of things we can actually ''link to''--and everyone's existing data can be immediately enriched by participating.

This is quick and dirty road to getting your catalog onto the Linked Data web. The talk take you from start to finish, using Free Software
tools to establish a namespace, put up a SPARQL endpoint, make a simple data model, convert MARC records to RDF, and link the results to major existing data sets (skipping conveniently over pesky processing time).

A small amount of "why linked data?" content will be covered, but the primary goal is to leave you able to reproduce the process and
start linking your catalog into the web of data. Appropriate documentation will be on the web.

[[Category: Code4Lib2012]]

2012 talks proposals

2011-11-16T19:02:33Z

Tjohnson: /* Your Catalog in Linked Data */

Deadline for talk submission is ''Sunday, November 20''.

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
* diversity of topics

Please follow the formatting guidelines:

<pre>

== Talk Title: ==

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

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

== VuFind 2.0: Why and How? ==

* Demian Katz, Villanova University, demian.katz@villanova.edu

A major new version of the VuFind discovery software is currently in development. While VuFind 1.x remains extremely popular, some of its components are beginning to show their age. VuFind 2.0 aims to retain all the strengths of the previous version of the software while making the architecture cleaner, more modern and more standards-based. This presentation will examine the motivation behind the update, preview some of the new features to look forward to, and discuss the challenges of creating a developer-friendly open source package in PHP.

== Open Source Software Registry ==

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

LYRASIS is creating and shepherding a [[Registry_E-R_Diagram|registry of library open source software]] as part of its [http://www.lyrasis.org/News/Press-Releases/2011/LYRASIS-Receives-Grant-to-Support-Open-Source.aspx grant from the Mellon Foundation to support the adoption of open source software by libraries].
The goal of the grant is to help libraries of all types determine if open source software is right for them, and what combination of software, hosting, training, and consulting works for their situation.
The registry is intended to become a community exchange point and stimulant for growth of the library open source ecosystem by connecting libraries with projects, service providers, and events.

The first half of this session will demonstrate the registry functions and describe how projects and providers can get involved.
The second half of the session will be a brainstorming suggestion of how to expand the functionality and usefulness of the registry.

== Property Graphs And TinkerPop Applications in Digital Libraries ==

* Brian Tingle, California Digital Library, brian.tingle.cdlib.org@gmail.com

[http://www.tinkerpop.com/ TinkerPop] is an open source software development group focusing on technologies in the [http://en.wikipedia.org/wiki/Graph_database graph database] space.
This talk will provide a general introduction to the TinkerPop Graph Stack and the [https://github.com/tinkerpop/gremlin/wiki/Defining-a-Property-Graph property graph model] is uses. The introduction will include code examples and explanations of the property graph models used by the [http://socialarchive.iath.virginia.edu/ Social Networks in Archival Context] project and show how the historical social graph is exposed as a JSON/REST API implemented by a TinkerPop [https://github.com/tinkerpop/rexster rexster] [https://github.com/tinkerpop/rexster-kibbles Kibble] that contains the application's graph theory logic. Other graph database applications possible with TinkerPop such as RDF support, and citation analysis will also be discussed.

== Security in Mind ==

* Erin Germ, United States Naval Academy, Nimitz Library, germ@usna.edu

I would like to talk about security of library software.

Over the Summer, I discovered a critical vulnerability in a vendor’s software that (verified) allowed me to assume any user’s identity for that site, (verified) switch to any user, and to (unverified, meaning I didn’t not perform this as I didn’t want to “hack” another library’s site) assume the role of any user for any other library who used this particular vendor's software.

Within a 3 hour period, I discovered a 2 vulnerabilities: 1) minor one allowing me to access any backups from any library site, and 2) a critical vulnerability. From start to finish, the examination, discovery in the vulnerability, and execution of a working exploit was done in less than 2 hours. The vulnerability was a result of poor cookie implementation. The exploit itself revolved around modifying the cookie, and then altering the browser’s permissions by assuming the role of another user.

I do not intend on stating which vendor it was, but I will show how I was able to perform this. If needed, I can do further research and “investigation” into other vendor's software to see what I can “find”.

''If selected, I will contact the vendor to inform them that I will present about this at C4L2012. I do not intend on releasing the name of the vendor.''

== Search Engines and Libraries ==

* Greg Lindahl, blekko CTO, greg@blekko.com

[https://blekko.com blekko] is a new web-scale search engine which enables end-users to create vertical search engines, through a feature called [http://help.blekko.com/index.php/category/slashtags/ slashtags]. Slashtags can contain as few as 1 or as many as tens of thousands of websites relevant to a narrow or broad topic. We have an extensive set of slashtags curated by a combination of volunteers and an in-house librarian team, or end-users can create and share their own. This talk will cover examples of slashtag creation relevant to libraries, and show how to embed this search into a library website, either using javascript or via our API.

''We have exhibited at a couple of library conferences, and have received a lot of interest. blekko is a free service.''

== Beyond code. Versioning data with Git and Mercurial. ==

* Stephanie Collett, California Digital Library, stephanie.collett@ucop.edu
* Martin Haye, California Digital Library, martin.haye@ucop.edu

Within a relatively short time since their introduction, [http://en.wikipedia.org/wiki/Distributed_Version_Control_System distributed version control systems] (DVCS) like [http://git-scm.com/ Git] and [http://mercurial.selenic.com/ Mercurial] have enjoyed widespread adoption for versioning code. It didn’t take long for the library development community to start discussing the potential for using DVCS within our applications and repositories to version data. After all, many of the features that have made some of these systems popular in the open source community to version code (e.g. lightweight, file-based, compressed, reliable) also make them compelling options for versioning data. And why write an entire versioning system from scratch if a DVCS solution can be a drop-in solution? At the [http://www.cdlib.org/ California Digital Library] (CDL) we’ve started using Git and Mercurial in some of our applications to version data. This has proven effective in some situations and unworkable in others. This presentation will be a practical case study of CDL’s experiences with using DVCS to version data. We will explain how we’re incorporating Git and Mercurial in our applications, describe our successes and failures and consider the issues involved in repurposing these systems for data versioning.

==Design for Developers==

*Lisa Kurt, University of Nevada, Reno, lkurt@unr.edu

Users expect good design. This talk will delve into what makes really great design, what to look for, and how to do it. Learn the principles of great design to take your applications, user interfaces, and projects to a higher level. With years of experience in graphic design and illustration, Lisa will discuss design principles, trends, process, tools, and development. Design examples will be from her own projects as well as a variety from industry. You’ll walk away with design knowledge that you can apply immediately to a variety of applications and a number of top notch go-to resources to get you up and running.

==Building research applications with Mendeley==

William Gunn, Mendeley william.gunn@mendeley.com (@mrgunn)

This is partly a tool talk and partly a big idea one.

Mendeley has built the world's largest open database of research and we've now begun to collect some interesting social metadata around the document metadata. I would like to share with the Code4Lib attendees information about using this resource to do things within your application that have previously been impossible for the library community, or in some cases impossible without expensive database subscriptions. One thing that's now possible is to augment catalog search by surfacing information about content usage, allowing people to not only find things matching a query, but popular things or things read by their colleagues. In addition to augmenting search, you can also use this information to augment discovery. Imagine an online exhibit of artifacts from a newly discovered dig not just linking to papers which discuss the artifact, but linking to really good interesting papers about the place and the people who made the artifacts. So the big idea is, "How will looking at the literature from a broader perspective than simple citation analysis change how research is done and communicated? How can we build tools that make this process easier and faster?" I can show some examples of applications that have been built using the Mendeley and PLoS APIs to begin to address this question, and I can also present results from Mendeley's developer challenge which shows what kinds of applications researchers are looking for, what kind of applications peope are building, and illustrates some interesting places where the two don't overlap.

==Your UI can make or break the application (to the user, anyway)==

* Robin Schaaf, University of Notre Dame, schaaf.4@nd.edu

UI development is hard and too often ends up as an after-thought to computer programmers - if you were a CS major in college I'll bet you didn't have many, if any, design courses. I'll talk about how to involve the users upfront with design and some common pitfalls of this approach. I'll also make a case for why you should do the screen design before a single line of code is written. And I'll throw in some ideas for increasing usability and attractiveness of your web applications. I'd like to make a case study of the UI development of our open source ERMS.

==Why Nobody Knows How Big The Library Really Is - Perspective of a Library Outside Turned Insider==

* Patrick Berry, California State University, Chico, pberry@csuchico.edu

In this talk I would like to bring the perspective of an "outsider" (although an avowed IT insider) to let you know that people don't understand the full scope of the library. As we "rethink education", it is incumbent upon us to help educate our institutions as to the scope of the library. I will present some of the tactics I'm employing to help people outside, and in some cases inside, the library to understand our size and the value we bring to the institution.

==Building a URL Management Module using the Concrete5 Package Architecture==

* David Uspal, Villanova University, david.uspal@villanova.edu

Keeping track of URLs utilized across a large website such as a university library, and keeping that content up to date for subject and course guides, can be a pain, and as an open source shop, we’d like to have open source solution for this issue. For this talk, I intend to detail our solution to this issue by walking step-by-step through the building process for our URL Management module -- including why a new solution was necessary; a quick rundown of our CMS ([http://www.concrete5.org Concrete5], a CMS that isn’t Drupal); utilizing the Concrete5 APIs to isolate our solution from core code (to avoid complications caused by core updates); how our solution was integrated into the CMS architecture for easy installation; and our future plans on the project.

==Building an NCIP connector to OpenSRF to facilitate resource sharing==

* Jon Scott, Lyrasis, jon_scott@wsu.edu and Kyle Banerjee, Orbis Cascade Alliance, banerjek@uoregon.edu

How do you reverse engineer any protocol to provide a new service? Humans (and worse yet, committees) often design verbose protocols built around use cases that don't line up current reality. To compound difficulties, the contents of protocol containers are not sufficiently defined/predictable and the only assistance available is sketchy documentation and kind individuals on the internet willing to share what they learned via trial by fire.

NCIP (Niso Circulation Interchange Protocol) is an open standard that defines a set of messages to support exchange of circulation data between disparate circulation, interlibrary loan, and related applications -- widespread adoption of NCIP would eliminate huge amounts of duplicate processing in separate systems.

This presentation discusses how we learned enough about NCIP and OpenSRF from scratch to build an NCIP responder for Evergreen to facilitate resource sharing in a large consortium that relies on over 20 different ILSes.

==Practical Agile: What's Working for Stanford, Blacklight, and Hydra==

* Naomi Dushay, Stanford University Libraries, ndushay@stanford.edu

Agile development techniques can be difficult to adopt in the context of library software development. Maybe your shop has only one or two developers, or you always have too many simultaneous projects. Maybe your new projects can’t be started until 27 librarians reach consensus on the specifications.

This talk will present successful Agile- and Silicon-Valley-inspired practices we’ve adopted at Stanford and/or in the Blacklight and Hydra projects. We’ve targeted developer happiness as well as improved productivity with our recent changes. User stories, dead week, sight lines … it’ll be a grab bag of goodies to bring back to your institution, including some ideas on how to adopt these practices without overt management buy in.

==Quick and <strike>Dirty</strike> Clean Usability: Rapid Prototyping with Bootstrap==

* Shaun Ellis, Princeton University Libraries, shaune@princeton.edu

''"The code itself is unimportant; a project is only as useful as people actually find it." - Linus Torvalds'' [http://bit.ly/p4uuyy]

Usability has been a buzzword for some time now, but what is the process for making the the transition toward a better user experience, and hence, better designed library sites? I will discuss the one facet of the process my team is using to redesign the Finding Aids site for Princeton University Libraries (still in development). The approach involves the use of rapid prototyping, with Bootstrap [http://twitter.github.com/bootstrap/], to make sure we are on track with what users and stakeholders expect up front, and throughout the development process.

Because Bootstrap allows for early and iterative user feedback, it is more effective than the historic Photoshop mockups/wireframe technique. The Photoshop approach allows stakeholders to test the look, but not the feel -- and often leaves developers scratching their heads. Being a CSS/HTML/Javascript grid-based framework, Bootstrap makes it easy for anyone with a bit of HTML/CSS chops to quickly build slick, interactive prototypes right in the browser -- tangible solutions which can be shared, evaluated, revised, and followed by all stakeholders (see Minimum Viable Products [http://en.wikipedia.org/wiki/Minimum_viable_product]). Efficiency is multiplied because the customized prototypes can flow directly into production use, as is the goal with iterative development approaches, such as the Agile methodology.

While Bootstrap is not the only framework that offers grid-based layout, development is expedited and usability is enhanced by Bootstraps use of of "prefabbed" conventional UI patterns, clean typography, and lean Javascript for interactivity. Furthermore, out-of-the box Bootstrap comes in a fairly neutral palette, so focus remains on usability, and does not devolve into premature discussions of color or branding choices. Finally, using Less can be a powerful tool in conjunction with Bootstrap, but is not necessary. I will discuss the pros and cons, and offer examples for how to getting up and running with or without Less.

==Search Engine Relevancy Tuning - A Static Rank Framework for Solr/Lucene==

* Mike Schultz, Amazon.com (formerly Summon Search Architect) mike.schultz@gmail.com

Solr/Lucene provides a lot of flexibility for adjusting relevancy scoring and improving search results. Roughly speaking there are two areas of concern: Firstly, a 'dynamic rank' calculation that is a function of the user query and document text fields. And secondly, a 'static rank' which is independent of the query and generally is a function of non-text document metadata. In this talk I will outline an easily understood, hand-tunable static rank system with a minimal number of parameters.

The obvious major feature of a search engine is to return results relevant to a user query. Perhaps less obvious is the huge role query independent document features play in achieving that. Google's PageRank is an example of a static ranking of web pages based on links and other secret sauce. In the Summon service, our 800 million documents have features like publication date, document type, citation count and Boolean features like the-article-is-peer-reviewed. These fields aren't textual and remain 'static' from query to query, but need to influence a document's relevancy score. In our search results, with all query related features being equal, we'd rather have more recent documents above older ones, Journals above Newspapers, and articles that are peer reviewed above those that are not. The static rank system I will describe achieves this and has the following features:

* Query-time only calculation - nothing is baked into the index - with parameters adjustable at query time.
* The system is based on a signal metaphor where components are 'wired' together. System components allow multiplexing, amplifying, summing, tunable band-pass filtering, string-to-value-mapping all with a bare minimum of parameters.
* An intuitive approach for mixing dynamic and static rank that is more effective than simple adding or multiplying.
* A way of equating disparate static metadata types that leads to understandable results ordering.

==Submitting Digitized Book-like things to the Internet Archive==

* Joel Richard, Smithsonian Institution Libraries, richardjm@si.edu

The Smithsonian Libraries has submitted thousands of out-of-copyright items to the Internet Archive over the years. Specifically in relation to the Biodiversity Heritage Library, we have developed an in-house boutique scanning and upload process that became a learning experience in automated uploading to the Archive. As part of the software development, we created a whitepaper that details the combined learning experiences of the Smithsonian Libraries and the Missouri Botanical Garden. We will discuss some of the the contents of this whitepaper in the context of our scanning process and the manner in which we upload items to the Archive.

Our talk will include a discussion of the types of files and their formats used by the Archive, processes that the Archive performs on uploaded items, ways of interacting and affecting those processes, potential pitfalls and solutions that you may encounter when uploading, and tools that the Archive provides to help monitor and manage your uploaded documents.

Finally, we'll wrap up with a brief summary of how to use things that are on the Internet Archive in your own websites.

== So... you think you want to Host a Code4Lib National Conference, do you? ==

* Elizabeth Duell, Orbis Cascade Alliance, eduell@uoregon.edu

Are you interested in hosting your own Code4Lib Conference? Do you know what it would take? What does BEO stands for? What does F&B Minimum mean? Who would you talk to for support/mentoring? There are so many things to think about: internet support, venue size, rooming blocks, contracts, dietary restrictions and coffee (can't forget the coffee!) just to name a few. Putting together a conference of any size can look daunting, so let's take the scary out of it and replace it with a can do attitude!

Be a step ahead of the game by learning from the people behind the curtain. Ask questions and be given templates/ cheat sheets!

== HTML5 Microdata and Schema.org ==

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

When the big search engines announced support for HTML5 microdata and the schema.org vocabularies, the balance of power for semantic markup in HTML shifted.
* What is microdata?
* Where does microdata fit with regards to other approaches like RDFa and microformats?
* Where do libraries stand in the worldview of Schema.org and what can they do about it?
* How can implementing microdata and schema.org optimize your sites for search engines?
* What tools are available?

== Stack View: A Library Browsing Tool ==

* Annie Cain, Harvard Library Innovation Lab, acain@law.harvard.edu
* Jeff Goldenson, Harvard Library Innovation Lab, jgoldenson@law.harvard.edu

In an effort to recreate and build upon the traditional method of browsing a physical library, we used catalog data, including dimensions and page count, to create a [http://librarylab.law.harvard.edu/projects/stackview/ virtual shelf].

This CSS and JavaScript backed visualization allows items to sit on any number of different shelves, really taking advantage of its digital nature. See how we built Stack View on top of our data and learn how you can create shelves of your own using our open source code.

== “Linked-Data-Ready” Software for Libraries ==

* Jennifer Bowen, University of Rochester River Campus Libraries, jbowen@library.rochester.edu

Linked data is poised to replace MARC as the basis for the new library bibliographic framework. For libraries to benefit from linked data, they must learn about it, experiment with it, demonstrate its usefulness, and take a leadership role in its deployment.

The eXtensible Catalog Organization (XCO) offers open-source software for libraries that is “linked-data-ready.” XC software prepares MARC and Dublin Core metadata for exposure to the semantic web, incorporating FRBR Group 1 entities and registered vocabularies for RDA elements and roles. This presentation will include a software demonstration, proposed software architecture for creation and management of linked data, a vision for how libraries can migrate from MARC to linked data, and an update on XCO progress toward linked data goals.

== How people search the library from a single search box ==

* Cory Lown, North Carolina State University Libraries, cory_lown@ncsu.edu

Searching the library is complex. There's the catalog, article databases, journal title and database title look-ups, the library website, finding aids, knowledge bases, etc. How would users search if they could get to all of these resources from a single search box? I'll share what we've learned about single search at NCSU Libraries by tracking use of QuickSearch (http://www.lib.ncsu.edu/search/index.php?q=aerospace+engineering), our home-grown unified search application. As part of this talk I will suggest low-cost ways to collect real world use data that can be applied to improve search. I will try to convince you that data collection must be carefully planned and designed to be an effective tool to help you understand what your users are telling you through their behavior. I will talk about how the fragmented library resource environment challenges us to provide useful and understandable search environments. Finally, I will share findings from analyzing millions of user transactions about how people search the library from a production single search box at a large university library.

== An Incremental Approach to Archival Description and Access ==

* Chela Scott Weber, New York University Libraries, chelascott@gmail.com
* Mark A. Matienzo, Yale University Library, mark@matienzo.org

''This is placeholder text; description coming shortly''

== Making the Easy Things Easy: A Generic ILS API ==

* Wayne Schneider, Hennepin County Library, wschneider@hclib.org

Some stuff we try to do is complicated, because, let's face it, library data is hard. Some stuff, on the other hand, should be easy. Given an item identifier, I should be able to look at item availability. Given a title identifier, I should be able to place a request. And no, I shouldn't have to parse through the NCIP specification or write a SIP client to do it.

This talk will present work we have done on a web services approach to an API for traditional library transactional data, including example applications.

== Your Catalog in Linked Data==

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

Linked Library Data activity over the last year has seen bibliographic data sets and vocabularies proliferating from traditional library
sources. We've reached a point where regular libraries don't have to go it alone to be on the Semantic Web--there's a quickly growing pool
of things we can actually ''link to''. Regular libraries can see their existing data enriched by participating.

This is quick and dirty road to getting your catalog onto the Linked Data web. The talk take you from start to finish, using Free Software
tools to establish a namespace, put up a SPARQL endpoint, make a simple data model, convert MARC records to RDF, and link the results to major existing data sets (skipping conveniently over pesky processing time).

A small amount of "why linked data?" content will be covered, but the primary goal is to leave you able to reproduce the process and
start linking your catalog into the web of data. Appropriate documentation will be on the web.

[[Category: Code4Lib2012]]

2012 talks proposals

2011-11-16T18:59:58Z

Tjohnson: /* Taking your Catalog from MARC to Linked Data in 20 Minutes */

Deadline for talk submission is ''Sunday, November 20''.

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
* diversity of topics

Please follow the formatting guidelines:

<pre>

== Talk Title: ==

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

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

== VuFind 2.0: Why and How? ==

* Demian Katz, Villanova University, demian.katz@villanova.edu

A major new version of the VuFind discovery software is currently in development. While VuFind 1.x remains extremely popular, some of its components are beginning to show their age. VuFind 2.0 aims to retain all the strengths of the previous version of the software while making the architecture cleaner, more modern and more standards-based. This presentation will examine the motivation behind the update, preview some of the new features to look forward to, and discuss the challenges of creating a developer-friendly open source package in PHP.

== Open Source Software Registry ==

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

LYRASIS is creating and shepherding a [[Registry_E-R_Diagram|registry of library open source software]] as part of its [http://www.lyrasis.org/News/Press-Releases/2011/LYRASIS-Receives-Grant-to-Support-Open-Source.aspx grant from the Mellon Foundation to support the adoption of open source software by libraries].
The goal of the grant is to help libraries of all types determine if open source software is right for them, and what combination of software, hosting, training, and consulting works for their situation.
The registry is intended to become a community exchange point and stimulant for growth of the library open source ecosystem by connecting libraries with projects, service providers, and events.

The first half of this session will demonstrate the registry functions and describe how projects and providers can get involved.
The second half of the session will be a brainstorming suggestion of how to expand the functionality and usefulness of the registry.

== Property Graphs And TinkerPop Applications in Digital Libraries ==

* Brian Tingle, California Digital Library, brian.tingle.cdlib.org@gmail.com

[http://www.tinkerpop.com/ TinkerPop] is an open source software development group focusing on technologies in the [http://en.wikipedia.org/wiki/Graph_database graph database] space.
This talk will provide a general introduction to the TinkerPop Graph Stack and the [https://github.com/tinkerpop/gremlin/wiki/Defining-a-Property-Graph property graph model] is uses. The introduction will include code examples and explanations of the property graph models used by the [http://socialarchive.iath.virginia.edu/ Social Networks in Archival Context] project and show how the historical social graph is exposed as a JSON/REST API implemented by a TinkerPop [https://github.com/tinkerpop/rexster rexster] [https://github.com/tinkerpop/rexster-kibbles Kibble] that contains the application's graph theory logic. Other graph database applications possible with TinkerPop such as RDF support, and citation analysis will also be discussed.

== Security in Mind ==

* Erin Germ, United States Naval Academy, Nimitz Library, germ@usna.edu

I would like to talk about security of library software.

Over the Summer, I discovered a critical vulnerability in a vendor’s software that (verified) allowed me to assume any user’s identity for that site, (verified) switch to any user, and to (unverified, meaning I didn’t not perform this as I didn’t want to “hack” another library’s site) assume the role of any user for any other library who used this particular vendor's software.

Within a 3 hour period, I discovered a 2 vulnerabilities: 1) minor one allowing me to access any backups from any library site, and 2) a critical vulnerability. From start to finish, the examination, discovery in the vulnerability, and execution of a working exploit was done in less than 2 hours. The vulnerability was a result of poor cookie implementation. The exploit itself revolved around modifying the cookie, and then altering the browser’s permissions by assuming the role of another user.

I do not intend on stating which vendor it was, but I will show how I was able to perform this. If needed, I can do further research and “investigation” into other vendor's software to see what I can “find”.

''If selected, I will contact the vendor to inform them that I will present about this at C4L2012. I do not intend on releasing the name of the vendor.''

== Search Engines and Libraries ==

* Greg Lindahl, blekko CTO, greg@blekko.com

[https://blekko.com blekko] is a new web-scale search engine which enables end-users to create vertical search engines, through a feature called [http://help.blekko.com/index.php/category/slashtags/ slashtags]. Slashtags can contain as few as 1 or as many as tens of thousands of websites relevant to a narrow or broad topic. We have an extensive set of slashtags curated by a combination of volunteers and an in-house librarian team, or end-users can create and share their own. This talk will cover examples of slashtag creation relevant to libraries, and show how to embed this search into a library website, either using javascript or via our API.

''We have exhibited at a couple of library conferences, and have received a lot of interest. blekko is a free service.''

== Beyond code. Versioning data with Git and Mercurial. ==

* Stephanie Collett, California Digital Library, stephanie.collett@ucop.edu
* Martin Haye, California Digital Library, martin.haye@ucop.edu

Within a relatively short time since their introduction, [http://en.wikipedia.org/wiki/Distributed_Version_Control_System distributed version control systems] (DVCS) like [http://git-scm.com/ Git] and [http://mercurial.selenic.com/ Mercurial] have enjoyed widespread adoption for versioning code. It didn’t take long for the library development community to start discussing the potential for using DVCS within our applications and repositories to version data. After all, many of the features that have made some of these systems popular in the open source community to version code (e.g. lightweight, file-based, compressed, reliable) also make them compelling options for versioning data. And why write an entire versioning system from scratch if a DVCS solution can be a drop-in solution? At the [http://www.cdlib.org/ California Digital Library] (CDL) we’ve started using Git and Mercurial in some of our applications to version data. This has proven effective in some situations and unworkable in others. This presentation will be a practical case study of CDL’s experiences with using DVCS to version data. We will explain how we’re incorporating Git and Mercurial in our applications, describe our successes and failures and consider the issues involved in repurposing these systems for data versioning.

==Design for Developers==

*Lisa Kurt, University of Nevada, Reno, lkurt@unr.edu

Users expect good design. This talk will delve into what makes really great design, what to look for, and how to do it. Learn the principles of great design to take your applications, user interfaces, and projects to a higher level. With years of experience in graphic design and illustration, Lisa will discuss design principles, trends, process, tools, and development. Design examples will be from her own projects as well as a variety from industry. You’ll walk away with design knowledge that you can apply immediately to a variety of applications and a number of top notch go-to resources to get you up and running.

==Building research applications with Mendeley==

William Gunn, Mendeley william.gunn@mendeley.com (@mrgunn)

This is partly a tool talk and partly a big idea one.

Mendeley has built the world's largest open database of research and we've now begun to collect some interesting social metadata around the document metadata. I would like to share with the Code4Lib attendees information about using this resource to do things within your application that have previously been impossible for the library community, or in some cases impossible without expensive database subscriptions. One thing that's now possible is to augment catalog search by surfacing information about content usage, allowing people to not only find things matching a query, but popular things or things read by their colleagues. In addition to augmenting search, you can also use this information to augment discovery. Imagine an online exhibit of artifacts from a newly discovered dig not just linking to papers which discuss the artifact, but linking to really good interesting papers about the place and the people who made the artifacts. So the big idea is, "How will looking at the literature from a broader perspective than simple citation analysis change how research is done and communicated? How can we build tools that make this process easier and faster?" I can show some examples of applications that have been built using the Mendeley and PLoS APIs to begin to address this question, and I can also present results from Mendeley's developer challenge which shows what kinds of applications researchers are looking for, what kind of applications peope are building, and illustrates some interesting places where the two don't overlap.

==Your UI can make or break the application (to the user, anyway)==

* Robin Schaaf, University of Notre Dame, schaaf.4@nd.edu

UI development is hard and too often ends up as an after-thought to computer programmers - if you were a CS major in college I'll bet you didn't have many, if any, design courses. I'll talk about how to involve the users upfront with design and some common pitfalls of this approach. I'll also make a case for why you should do the screen design before a single line of code is written. And I'll throw in some ideas for increasing usability and attractiveness of your web applications. I'd like to make a case study of the UI development of our open source ERMS.

==Why Nobody Knows How Big The Library Really Is - Perspective of a Library Outside Turned Insider==

* Patrick Berry, California State University, Chico, pberry@csuchico.edu

In this talk I would like to bring the perspective of an "outsider" (although an avowed IT insider) to let you know that people don't understand the full scope of the library. As we "rethink education", it is incumbent upon us to help educate our institutions as to the scope of the library. I will present some of the tactics I'm employing to help people outside, and in some cases inside, the library to understand our size and the value we bring to the institution.

==Building a URL Management Module using the Concrete5 Package Architecture==

* David Uspal, Villanova University, david.uspal@villanova.edu

Keeping track of URLs utilized across a large website such as a university library, and keeping that content up to date for subject and course guides, can be a pain, and as an open source shop, we’d like to have open source solution for this issue. For this talk, I intend to detail our solution to this issue by walking step-by-step through the building process for our URL Management module -- including why a new solution was necessary; a quick rundown of our CMS ([http://www.concrete5.org Concrete5], a CMS that isn’t Drupal); utilizing the Concrete5 APIs to isolate our solution from core code (to avoid complications caused by core updates); how our solution was integrated into the CMS architecture for easy installation; and our future plans on the project.

==Building an NCIP connector to OpenSRF to facilitate resource sharing==

* Jon Scott, Lyrasis, jon_scott@wsu.edu and Kyle Banerjee, Orbis Cascade Alliance, banerjek@uoregon.edu

How do you reverse engineer any protocol to provide a new service? Humans (and worse yet, committees) often design verbose protocols built around use cases that don't line up current reality. To compound difficulties, the contents of protocol containers are not sufficiently defined/predictable and the only assistance available is sketchy documentation and kind individuals on the internet willing to share what they learned via trial by fire.

NCIP (Niso Circulation Interchange Protocol) is an open standard that defines a set of messages to support exchange of circulation data between disparate circulation, interlibrary loan, and related applications -- widespread adoption of NCIP would eliminate huge amounts of duplicate processing in separate systems.

This presentation discusses how we learned enough about NCIP and OpenSRF from scratch to build an NCIP responder for Evergreen to facilitate resource sharing in a large consortium that relies on over 20 different ILSes.

==Practical Agile: What's Working for Stanford, Blacklight, and Hydra==

* Naomi Dushay, Stanford University Libraries, ndushay@stanford.edu

Agile development techniques can be difficult to adopt in the context of library software development. Maybe your shop has only one or two developers, or you always have too many simultaneous projects. Maybe your new projects can’t be started until 27 librarians reach consensus on the specifications.

This talk will present successful Agile- and Silicon-Valley-inspired practices we’ve adopted at Stanford and/or in the Blacklight and Hydra projects. We’ve targeted developer happiness as well as improved productivity with our recent changes. User stories, dead week, sight lines … it’ll be a grab bag of goodies to bring back to your institution, including some ideas on how to adopt these practices without overt management buy in.

==Quick and <strike>Dirty</strike> Clean Usability: Rapid Prototyping with Bootstrap==

* Shaun Ellis, Princeton University Libraries, shaune@princeton.edu

''"The code itself is unimportant; a project is only as useful as people actually find it." - Linus Torvalds'' [http://bit.ly/p4uuyy]

Usability has been a buzzword for some time now, but what is the process for making the the transition toward a better user experience, and hence, better designed library sites? I will discuss the one facet of the process my team is using to redesign the Finding Aids site for Princeton University Libraries (still in development). The approach involves the use of rapid prototyping, with Bootstrap [http://twitter.github.com/bootstrap/], to make sure we are on track with what users and stakeholders expect up front, and throughout the development process.

Because Bootstrap allows for early and iterative user feedback, it is more effective than the historic Photoshop mockups/wireframe technique. The Photoshop approach allows stakeholders to test the look, but not the feel -- and often leaves developers scratching their heads. Being a CSS/HTML/Javascript grid-based framework, Bootstrap makes it easy for anyone with a bit of HTML/CSS chops to quickly build slick, interactive prototypes right in the browser -- tangible solutions which can be shared, evaluated, revised, and followed by all stakeholders (see Minimum Viable Products [http://en.wikipedia.org/wiki/Minimum_viable_product]). Efficiency is multiplied because the customized prototypes can flow directly into production use, as is the goal with iterative development approaches, such as the Agile methodology.

While Bootstrap is not the only framework that offers grid-based layout, development is expedited and usability is enhanced by Bootstraps use of of "prefabbed" conventional UI patterns, clean typography, and lean Javascript for interactivity. Furthermore, out-of-the box Bootstrap comes in a fairly neutral palette, so focus remains on usability, and does not devolve into premature discussions of color or branding choices. Finally, using Less can be a powerful tool in conjunction with Bootstrap, but is not necessary. I will discuss the pros and cons, and offer examples for how to getting up and running with or without Less.

==Search Engine Relevancy Tuning - A Static Rank Framework for Solr/Lucene==

* Mike Schultz, Amazon.com (formerly Summon Search Architect) mike.schultz@gmail.com

Solr/Lucene provides a lot of flexibility for adjusting relevancy scoring and improving search results. Roughly speaking there are two areas of concern: Firstly, a 'dynamic rank' calculation that is a function of the user query and document text fields. And secondly, a 'static rank' which is independent of the query and generally is a function of non-text document metadata. In this talk I will outline an easily understood, hand-tunable static rank system with a minimal number of parameters.

The obvious major feature of a search engine is to return results relevant to a user query. Perhaps less obvious is the huge role query independent document features play in achieving that. Google's PageRank is an example of a static ranking of web pages based on links and other secret sauce. In the Summon service, our 800 million documents have features like publication date, document type, citation count and Boolean features like the-article-is-peer-reviewed. These fields aren't textual and remain 'static' from query to query, but need to influence a document's relevancy score. In our search results, with all query related features being equal, we'd rather have more recent documents above older ones, Journals above Newspapers, and articles that are peer reviewed above those that are not. The static rank system I will describe achieves this and has the following features:

* Query-time only calculation - nothing is baked into the index - with parameters adjustable at query time.
* The system is based on a signal metaphor where components are 'wired' together. System components allow multiplexing, amplifying, summing, tunable band-pass filtering, string-to-value-mapping all with a bare minimum of parameters.
* An intuitive approach for mixing dynamic and static rank that is more effective than simple adding or multiplying.
* A way of equating disparate static metadata types that leads to understandable results ordering.

==Submitting Digitized Book-like things to the Internet Archive==

* Joel Richard, Smithsonian Institution Libraries, richardjm@si.edu

The Smithsonian Libraries has submitted thousands of out-of-copyright items to the Internet Archive over the years. Specifically in relation to the Biodiversity Heritage Library, we have developed an in-house boutique scanning and upload process that became a learning experience in automated uploading to the Archive. As part of the software development, we created a whitepaper that details the combined learning experiences of the Smithsonian Libraries and the Missouri Botanical Garden. We will discuss some of the the contents of this whitepaper in the context of our scanning process and the manner in which we upload items to the Archive.

Our talk will include a discussion of the types of files and their formats used by the Archive, processes that the Archive performs on uploaded items, ways of interacting and affecting those processes, potential pitfalls and solutions that you may encounter when uploading, and tools that the Archive provides to help monitor and manage your uploaded documents.

Finally, we'll wrap up with a brief summary of how to use things that are on the Internet Archive in your own websites.

== So... you think you want to Host a Code4Lib National Conference, do you? ==

* Elizabeth Duell, Orbis Cascade Alliance, eduell@uoregon.edu

Are you interested in hosting your own Code4Lib Conference? Do you know what it would take? What does BEO stands for? What does F&B Minimum mean? Who would you talk to for support/mentoring? There are so many things to think about: internet support, venue size, rooming blocks, contracts, dietary restrictions and coffee (can't forget the coffee!) just to name a few. Putting together a conference of any size can look daunting, so let's take the scary out of it and replace it with a can do attitude!

Be a step ahead of the game by learning from the people behind the curtain. Ask questions and be given templates/ cheat sheets!

== HTML5 Microdata and Schema.org ==

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

When the big search engines announced support for HTML5 microdata and the schema.org vocabularies, the balance of power for semantic markup in HTML shifted.
* What is microdata?
* Where does microdata fit with regards to other approaches like RDFa and microformats?
* Where do libraries stand in the worldview of Schema.org and what can they do about it?
* How can implementing microdata and schema.org optimize your sites for search engines?
* What tools are available?

== Stack View: A Library Browsing Tool ==

* Annie Cain, Harvard Library Innovation Lab, acain@law.harvard.edu
* Jeff Goldenson, Harvard Library Innovation Lab, jgoldenson@law.harvard.edu

In an effort to recreate and build upon the traditional method of browsing a physical library, we used catalog data, including dimensions and page count, to create a [http://librarylab.law.harvard.edu/projects/stackview/ virtual shelf].

This CSS and JavaScript backed visualization allows items to sit on any number of different shelves, really taking advantage of its digital nature. See how we built Stack View on top of our data and learn how you can create shelves of your own using our open source code.

== “Linked-Data-Ready” Software for Libraries ==

* Jennifer Bowen, University of Rochester River Campus Libraries, jbowen@library.rochester.edu

Linked data is poised to replace MARC as the basis for the new library bibliographic framework. For libraries to benefit from linked data, they must learn about it, experiment with it, demonstrate its usefulness, and take a leadership role in its deployment.

The eXtensible Catalog Organization (XCO) offers open-source software for libraries that is “linked-data-ready.” XC software prepares MARC and Dublin Core metadata for exposure to the semantic web, incorporating FRBR Group 1 entities and registered vocabularies for RDA elements and roles. This presentation will include a software demonstration, proposed software architecture for creation and management of linked data, a vision for how libraries can migrate from MARC to linked data, and an update on XCO progress toward linked data goals.

== How people search the library from a single search box ==

* Cory Lown, North Carolina State University Libraries, cory_lown@ncsu.edu

Searching the library is complex. There's the catalog, article databases, journal title and database title look-ups, the library website, finding aids, knowledge bases, etc. How would users search if they could get to all of these resources from a single search box? I'll share what we've learned about single search at NCSU Libraries by tracking use of QuickSearch (http://www.lib.ncsu.edu/search/index.php?q=aerospace+engineering), our home-grown unified search application. As part of this talk I will suggest low-cost ways to collect real world use data that can be applied to improve search. I will try to convince you that data collection must be carefully planned and designed to be an effective tool to help you understand what your users are telling you through their behavior. I will talk about how the fragmented library resource environment challenges us to provide useful and understandable search environments. Finally, I will share findings from analyzing millions of user transactions about how people search the library from a production single search box at a large university library.

== An Incremental Approach to Archival Description and Access ==

* Chela Scott Weber, New York University Libraries, chelascott@gmail.com
* Mark A. Matienzo, Yale University Library, mark@matienzo.org

''This is placeholder text; description coming shortly''

== Making the Easy Things Easy: A Generic ILS API ==

* Wayne Schneider, Hennepin County Library, wschneider@hclib.org

Some stuff we try to do is complicated, because, let's face it, library data is hard. Some stuff, on the other hand, should be easy. Given an item identifier, I should be able to look at item availability. Given a title identifier, I should be able to place a request. And no, I shouldn't have to parse through the NCIP specification or write a SIP client to do it.

This talk will present work we have done on a web services approach to an API for traditional library transactional data, including example applications.

== Your Catalog in Linked Data==

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

Linked Library Data activity over the last year has seen bibliographic
data sets and vocabularies proliferating from traditional library
sources. We've reached a point where regular libraries don't have to
go it alone to be on the Semantic Web--there's a quickly growing pool
of things we can actually *link to*. Everyday libraries can see their
existing data enriched by participating.

This is quick and dirty road to getting your catalog onto the Linked
Data web. The talk take you from start to finish, using Free Software
tools to establish a namespace, put up a SPARQL endpoint, make a data
model, converting MARC records to RDF, and link them up to major
existing data sets (skipping conveniently over pesky processing time).

A small amount of "why linked data?" content will be covered, but
the primary goal is to leave you able to reproduce the process and
start linking your catalog into the web of data. Appropriate
documentation will be on the web.

[[Category: Code4Lib2012]]

2012 talks proposals

2011-11-16T18:59:27Z

Tjohnson: t. johnson proposal

Deadline for talk submission is ''Sunday, November 20''.

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
* diversity of topics

Please follow the formatting guidelines:

<pre>

== Talk Title: ==

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

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

== VuFind 2.0: Why and How? ==

* Demian Katz, Villanova University, demian.katz@villanova.edu

A major new version of the VuFind discovery software is currently in development. While VuFind 1.x remains extremely popular, some of its components are beginning to show their age. VuFind 2.0 aims to retain all the strengths of the previous version of the software while making the architecture cleaner, more modern and more standards-based. This presentation will examine the motivation behind the update, preview some of the new features to look forward to, and discuss the challenges of creating a developer-friendly open source package in PHP.

== Open Source Software Registry ==

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

LYRASIS is creating and shepherding a [[Registry_E-R_Diagram|registry of library open source software]] as part of its [http://www.lyrasis.org/News/Press-Releases/2011/LYRASIS-Receives-Grant-to-Support-Open-Source.aspx grant from the Mellon Foundation to support the adoption of open source software by libraries].
The goal of the grant is to help libraries of all types determine if open source software is right for them, and what combination of software, hosting, training, and consulting works for their situation.
The registry is intended to become a community exchange point and stimulant for growth of the library open source ecosystem by connecting libraries with projects, service providers, and events.

The first half of this session will demonstrate the registry functions and describe how projects and providers can get involved.
The second half of the session will be a brainstorming suggestion of how to expand the functionality and usefulness of the registry.

== Property Graphs And TinkerPop Applications in Digital Libraries ==

* Brian Tingle, California Digital Library, brian.tingle.cdlib.org@gmail.com

[http://www.tinkerpop.com/ TinkerPop] is an open source software development group focusing on technologies in the [http://en.wikipedia.org/wiki/Graph_database graph database] space.
This talk will provide a general introduction to the TinkerPop Graph Stack and the [https://github.com/tinkerpop/gremlin/wiki/Defining-a-Property-Graph property graph model] is uses. The introduction will include code examples and explanations of the property graph models used by the [http://socialarchive.iath.virginia.edu/ Social Networks in Archival Context] project and show how the historical social graph is exposed as a JSON/REST API implemented by a TinkerPop [https://github.com/tinkerpop/rexster rexster] [https://github.com/tinkerpop/rexster-kibbles Kibble] that contains the application's graph theory logic. Other graph database applications possible with TinkerPop such as RDF support, and citation analysis will also be discussed.

== Security in Mind ==

* Erin Germ, United States Naval Academy, Nimitz Library, germ@usna.edu

I would like to talk about security of library software.

Over the Summer, I discovered a critical vulnerability in a vendor’s software that (verified) allowed me to assume any user’s identity for that site, (verified) switch to any user, and to (unverified, meaning I didn’t not perform this as I didn’t want to “hack” another library’s site) assume the role of any user for any other library who used this particular vendor's software.

Within a 3 hour period, I discovered a 2 vulnerabilities: 1) minor one allowing me to access any backups from any library site, and 2) a critical vulnerability. From start to finish, the examination, discovery in the vulnerability, and execution of a working exploit was done in less than 2 hours. The vulnerability was a result of poor cookie implementation. The exploit itself revolved around modifying the cookie, and then altering the browser’s permissions by assuming the role of another user.

I do not intend on stating which vendor it was, but I will show how I was able to perform this. If needed, I can do further research and “investigation” into other vendor's software to see what I can “find”.

''If selected, I will contact the vendor to inform them that I will present about this at C4L2012. I do not intend on releasing the name of the vendor.''

== Search Engines and Libraries ==

* Greg Lindahl, blekko CTO, greg@blekko.com

[https://blekko.com blekko] is a new web-scale search engine which enables end-users to create vertical search engines, through a feature called [http://help.blekko.com/index.php/category/slashtags/ slashtags]. Slashtags can contain as few as 1 or as many as tens of thousands of websites relevant to a narrow or broad topic. We have an extensive set of slashtags curated by a combination of volunteers and an in-house librarian team, or end-users can create and share their own. This talk will cover examples of slashtag creation relevant to libraries, and show how to embed this search into a library website, either using javascript or via our API.

''We have exhibited at a couple of library conferences, and have received a lot of interest. blekko is a free service.''

== Beyond code. Versioning data with Git and Mercurial. ==

* Stephanie Collett, California Digital Library, stephanie.collett@ucop.edu
* Martin Haye, California Digital Library, martin.haye@ucop.edu

Within a relatively short time since their introduction, [http://en.wikipedia.org/wiki/Distributed_Version_Control_System distributed version control systems] (DVCS) like [http://git-scm.com/ Git] and [http://mercurial.selenic.com/ Mercurial] have enjoyed widespread adoption for versioning code. It didn’t take long for the library development community to start discussing the potential for using DVCS within our applications and repositories to version data. After all, many of the features that have made some of these systems popular in the open source community to version code (e.g. lightweight, file-based, compressed, reliable) also make them compelling options for versioning data. And why write an entire versioning system from scratch if a DVCS solution can be a drop-in solution? At the [http://www.cdlib.org/ California Digital Library] (CDL) we’ve started using Git and Mercurial in some of our applications to version data. This has proven effective in some situations and unworkable in others. This presentation will be a practical case study of CDL’s experiences with using DVCS to version data. We will explain how we’re incorporating Git and Mercurial in our applications, describe our successes and failures and consider the issues involved in repurposing these systems for data versioning.

==Design for Developers==

*Lisa Kurt, University of Nevada, Reno, lkurt@unr.edu

Users expect good design. This talk will delve into what makes really great design, what to look for, and how to do it. Learn the principles of great design to take your applications, user interfaces, and projects to a higher level. With years of experience in graphic design and illustration, Lisa will discuss design principles, trends, process, tools, and development. Design examples will be from her own projects as well as a variety from industry. You’ll walk away with design knowledge that you can apply immediately to a variety of applications and a number of top notch go-to resources to get you up and running.

==Building research applications with Mendeley==

William Gunn, Mendeley william.gunn@mendeley.com (@mrgunn)

This is partly a tool talk and partly a big idea one.

Mendeley has built the world's largest open database of research and we've now begun to collect some interesting social metadata around the document metadata. I would like to share with the Code4Lib attendees information about using this resource to do things within your application that have previously been impossible for the library community, or in some cases impossible without expensive database subscriptions. One thing that's now possible is to augment catalog search by surfacing information about content usage, allowing people to not only find things matching a query, but popular things or things read by their colleagues. In addition to augmenting search, you can also use this information to augment discovery. Imagine an online exhibit of artifacts from a newly discovered dig not just linking to papers which discuss the artifact, but linking to really good interesting papers about the place and the people who made the artifacts. So the big idea is, "How will looking at the literature from a broader perspective than simple citation analysis change how research is done and communicated? How can we build tools that make this process easier and faster?" I can show some examples of applications that have been built using the Mendeley and PLoS APIs to begin to address this question, and I can also present results from Mendeley's developer challenge which shows what kinds of applications researchers are looking for, what kind of applications peope are building, and illustrates some interesting places where the two don't overlap.

==Your UI can make or break the application (to the user, anyway)==

* Robin Schaaf, University of Notre Dame, schaaf.4@nd.edu

UI development is hard and too often ends up as an after-thought to computer programmers - if you were a CS major in college I'll bet you didn't have many, if any, design courses. I'll talk about how to involve the users upfront with design and some common pitfalls of this approach. I'll also make a case for why you should do the screen design before a single line of code is written. And I'll throw in some ideas for increasing usability and attractiveness of your web applications. I'd like to make a case study of the UI development of our open source ERMS.

==Why Nobody Knows How Big The Library Really Is - Perspective of a Library Outside Turned Insider==

* Patrick Berry, California State University, Chico, pberry@csuchico.edu

In this talk I would like to bring the perspective of an "outsider" (although an avowed IT insider) to let you know that people don't understand the full scope of the library. As we "rethink education", it is incumbent upon us to help educate our institutions as to the scope of the library. I will present some of the tactics I'm employing to help people outside, and in some cases inside, the library to understand our size and the value we bring to the institution.

==Building a URL Management Module using the Concrete5 Package Architecture==

* David Uspal, Villanova University, david.uspal@villanova.edu

Keeping track of URLs utilized across a large website such as a university library, and keeping that content up to date for subject and course guides, can be a pain, and as an open source shop, we’d like to have open source solution for this issue. For this talk, I intend to detail our solution to this issue by walking step-by-step through the building process for our URL Management module -- including why a new solution was necessary; a quick rundown of our CMS ([http://www.concrete5.org Concrete5], a CMS that isn’t Drupal); utilizing the Concrete5 APIs to isolate our solution from core code (to avoid complications caused by core updates); how our solution was integrated into the CMS architecture for easy installation; and our future plans on the project.

==Building an NCIP connector to OpenSRF to facilitate resource sharing==

* Jon Scott, Lyrasis, jon_scott@wsu.edu and Kyle Banerjee, Orbis Cascade Alliance, banerjek@uoregon.edu

How do you reverse engineer any protocol to provide a new service? Humans (and worse yet, committees) often design verbose protocols built around use cases that don't line up current reality. To compound difficulties, the contents of protocol containers are not sufficiently defined/predictable and the only assistance available is sketchy documentation and kind individuals on the internet willing to share what they learned via trial by fire.

NCIP (Niso Circulation Interchange Protocol) is an open standard that defines a set of messages to support exchange of circulation data between disparate circulation, interlibrary loan, and related applications -- widespread adoption of NCIP would eliminate huge amounts of duplicate processing in separate systems.

This presentation discusses how we learned enough about NCIP and OpenSRF from scratch to build an NCIP responder for Evergreen to facilitate resource sharing in a large consortium that relies on over 20 different ILSes.

==Practical Agile: What's Working for Stanford, Blacklight, and Hydra==

* Naomi Dushay, Stanford University Libraries, ndushay@stanford.edu

Agile development techniques can be difficult to adopt in the context of library software development. Maybe your shop has only one or two developers, or you always have too many simultaneous projects. Maybe your new projects can’t be started until 27 librarians reach consensus on the specifications.

This talk will present successful Agile- and Silicon-Valley-inspired practices we’ve adopted at Stanford and/or in the Blacklight and Hydra projects. We’ve targeted developer happiness as well as improved productivity with our recent changes. User stories, dead week, sight lines … it’ll be a grab bag of goodies to bring back to your institution, including some ideas on how to adopt these practices without overt management buy in.

==Quick and <strike>Dirty</strike> Clean Usability: Rapid Prototyping with Bootstrap==

* Shaun Ellis, Princeton University Libraries, shaune@princeton.edu

''"The code itself is unimportant; a project is only as useful as people actually find it." - Linus Torvalds'' [http://bit.ly/p4uuyy]

Usability has been a buzzword for some time now, but what is the process for making the the transition toward a better user experience, and hence, better designed library sites? I will discuss the one facet of the process my team is using to redesign the Finding Aids site for Princeton University Libraries (still in development). The approach involves the use of rapid prototyping, with Bootstrap [http://twitter.github.com/bootstrap/], to make sure we are on track with what users and stakeholders expect up front, and throughout the development process.

Because Bootstrap allows for early and iterative user feedback, it is more effective than the historic Photoshop mockups/wireframe technique. The Photoshop approach allows stakeholders to test the look, but not the feel -- and often leaves developers scratching their heads. Being a CSS/HTML/Javascript grid-based framework, Bootstrap makes it easy for anyone with a bit of HTML/CSS chops to quickly build slick, interactive prototypes right in the browser -- tangible solutions which can be shared, evaluated, revised, and followed by all stakeholders (see Minimum Viable Products [http://en.wikipedia.org/wiki/Minimum_viable_product]). Efficiency is multiplied because the customized prototypes can flow directly into production use, as is the goal with iterative development approaches, such as the Agile methodology.

While Bootstrap is not the only framework that offers grid-based layout, development is expedited and usability is enhanced by Bootstraps use of of "prefabbed" conventional UI patterns, clean typography, and lean Javascript for interactivity. Furthermore, out-of-the box Bootstrap comes in a fairly neutral palette, so focus remains on usability, and does not devolve into premature discussions of color or branding choices. Finally, using Less can be a powerful tool in conjunction with Bootstrap, but is not necessary. I will discuss the pros and cons, and offer examples for how to getting up and running with or without Less.

==Search Engine Relevancy Tuning - A Static Rank Framework for Solr/Lucene==

* Mike Schultz, Amazon.com (formerly Summon Search Architect) mike.schultz@gmail.com

Solr/Lucene provides a lot of flexibility for adjusting relevancy scoring and improving search results. Roughly speaking there are two areas of concern: Firstly, a 'dynamic rank' calculation that is a function of the user query and document text fields. And secondly, a 'static rank' which is independent of the query and generally is a function of non-text document metadata. In this talk I will outline an easily understood, hand-tunable static rank system with a minimal number of parameters.

The obvious major feature of a search engine is to return results relevant to a user query. Perhaps less obvious is the huge role query independent document features play in achieving that. Google's PageRank is an example of a static ranking of web pages based on links and other secret sauce. In the Summon service, our 800 million documents have features like publication date, document type, citation count and Boolean features like the-article-is-peer-reviewed. These fields aren't textual and remain 'static' from query to query, but need to influence a document's relevancy score. In our search results, with all query related features being equal, we'd rather have more recent documents above older ones, Journals above Newspapers, and articles that are peer reviewed above those that are not. The static rank system I will describe achieves this and has the following features:

* Query-time only calculation - nothing is baked into the index - with parameters adjustable at query time.
* The system is based on a signal metaphor where components are 'wired' together. System components allow multiplexing, amplifying, summing, tunable band-pass filtering, string-to-value-mapping all with a bare minimum of parameters.
* An intuitive approach for mixing dynamic and static rank that is more effective than simple adding or multiplying.
* A way of equating disparate static metadata types that leads to understandable results ordering.

==Submitting Digitized Book-like things to the Internet Archive==

* Joel Richard, Smithsonian Institution Libraries, richardjm@si.edu

The Smithsonian Libraries has submitted thousands of out-of-copyright items to the Internet Archive over the years. Specifically in relation to the Biodiversity Heritage Library, we have developed an in-house boutique scanning and upload process that became a learning experience in automated uploading to the Archive. As part of the software development, we created a whitepaper that details the combined learning experiences of the Smithsonian Libraries and the Missouri Botanical Garden. We will discuss some of the the contents of this whitepaper in the context of our scanning process and the manner in which we upload items to the Archive.

Our talk will include a discussion of the types of files and their formats used by the Archive, processes that the Archive performs on uploaded items, ways of interacting and affecting those processes, potential pitfalls and solutions that you may encounter when uploading, and tools that the Archive provides to help monitor and manage your uploaded documents.

Finally, we'll wrap up with a brief summary of how to use things that are on the Internet Archive in your own websites.

== So... you think you want to Host a Code4Lib National Conference, do you? ==

* Elizabeth Duell, Orbis Cascade Alliance, eduell@uoregon.edu

Are you interested in hosting your own Code4Lib Conference? Do you know what it would take? What does BEO stands for? What does F&B Minimum mean? Who would you talk to for support/mentoring? There are so many things to think about: internet support, venue size, rooming blocks, contracts, dietary restrictions and coffee (can't forget the coffee!) just to name a few. Putting together a conference of any size can look daunting, so let's take the scary out of it and replace it with a can do attitude!

Be a step ahead of the game by learning from the people behind the curtain. Ask questions and be given templates/ cheat sheets!

== HTML5 Microdata and Schema.org ==

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

When the big search engines announced support for HTML5 microdata and the schema.org vocabularies, the balance of power for semantic markup in HTML shifted.
* What is microdata?
* Where does microdata fit with regards to other approaches like RDFa and microformats?
* Where do libraries stand in the worldview of Schema.org and what can they do about it?
* How can implementing microdata and schema.org optimize your sites for search engines?
* What tools are available?

== Stack View: A Library Browsing Tool ==

* Annie Cain, Harvard Library Innovation Lab, acain@law.harvard.edu
* Jeff Goldenson, Harvard Library Innovation Lab, jgoldenson@law.harvard.edu

In an effort to recreate and build upon the traditional method of browsing a physical library, we used catalog data, including dimensions and page count, to create a [http://librarylab.law.harvard.edu/projects/stackview/ virtual shelf].

This CSS and JavaScript backed visualization allows items to sit on any number of different shelves, really taking advantage of its digital nature. See how we built Stack View on top of our data and learn how you can create shelves of your own using our open source code.

== “Linked-Data-Ready” Software for Libraries ==

* Jennifer Bowen, University of Rochester River Campus Libraries, jbowen@library.rochester.edu

Linked data is poised to replace MARC as the basis for the new library bibliographic framework. For libraries to benefit from linked data, they must learn about it, experiment with it, demonstrate its usefulness, and take a leadership role in its deployment.

The eXtensible Catalog Organization (XCO) offers open-source software for libraries that is “linked-data-ready.” XC software prepares MARC and Dublin Core metadata for exposure to the semantic web, incorporating FRBR Group 1 entities and registered vocabularies for RDA elements and roles. This presentation will include a software demonstration, proposed software architecture for creation and management of linked data, a vision for how libraries can migrate from MARC to linked data, and an update on XCO progress toward linked data goals.

== How people search the library from a single search box ==

* Cory Lown, North Carolina State University Libraries, cory_lown@ncsu.edu

Searching the library is complex. There's the catalog, article databases, journal title and database title look-ups, the library website, finding aids, knowledge bases, etc. How would users search if they could get to all of these resources from a single search box? I'll share what we've learned about single search at NCSU Libraries by tracking use of QuickSearch (http://www.lib.ncsu.edu/search/index.php?q=aerospace+engineering), our home-grown unified search application. As part of this talk I will suggest low-cost ways to collect real world use data that can be applied to improve search. I will try to convince you that data collection must be carefully planned and designed to be an effective tool to help you understand what your users are telling you through their behavior. I will talk about how the fragmented library resource environment challenges us to provide useful and understandable search environments. Finally, I will share findings from analyzing millions of user transactions about how people search the library from a production single search box at a large university library.

== An Incremental Approach to Archival Description and Access ==

* Chela Scott Weber, New York University Libraries, chelascott@gmail.com
* Mark A. Matienzo, Yale University Library, mark@matienzo.org

''This is placeholder text; description coming shortly''

== Making the Easy Things Easy: A Generic ILS API ==

* Wayne Schneider, Hennepin County Library, wschneider@hclib.org

Some stuff we try to do is complicated, because, let's face it, library data is hard. Some stuff, on the other hand, should be easy. Given an item identifier, I should be able to look at item availability. Given a title identifier, I should be able to place a request. And no, I shouldn't have to parse through the NCIP specification or write a SIP client to do it.

This talk will present work we have done on a web services approach to an API for traditional library transactional data, including example applications.

== Taking your Catalog from MARC to Linked Data in 20 Minutes ==

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

Linked Library Data activity over the last year has seen bibliographic
data sets and vocabularies proliferating from traditional library
sources. We've reached a point where regular libraries don't have to
go it alone to be on the Semantic Web--there's a quickly growing pool
of things we can actually *link to*. Everyday libraries can see their
existing data enriched by participating.

This is quick and dirty road to getting your catalog onto the Linked
Data web. The talk take you from start to finish, using Free Software
tools to establish a namespace, put up a SPARQL endpoint, make a data
model, converting MARC records to RDF, and link them up to major
existing data sets (skipping conveniently over pesky processing time).

A small amount of "why linked data?" content will be covered, but
the primary goal is to leave you able to reproduce the process and
start linking your catalog into the web of data. Appropriate
documentation will be on the web.

[[Category: Code4Lib2012]]

2012 committees sign-up page

2011-06-14T16:45:12Z

Tjohnson: /* Program Committee */

= Code4Lib 2012 Committees =

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

== Book Give-Away Committee ==

* Kevin S. Clarke (ksclarke@gmail.com) -- McHenry Library, UC Santa Cruz

== Sponsorships Committee ==

This committee organizes the sponsorship activities. Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.

* Kyle Banerjee (banerjek@uoregon.edu) -- Orbis Cascade Alliance
* Anjanette Young -- University of Washington
* Mike Giarlo -- Penn State

== Keynote Speakers Committee ==

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

* Ann Lally (alally at uw dot edu) University of Washington
* Dre (akorphan at ncsu dot edu) North Carolina State University

== Program Committee ==

This committee plans the structure of the program, arranges the voting on presentations, etc. These folks will also announce speakers, etc.

* Jeremy Frumkin (frumkinj at u dot library dot arizona dot edu) - University of Arizona
* Ranti Junus (ranti.junus at gmail) - Michigan State University
* John Fink (john.fink at gmail) - McMaster University
* Tom Johnson (thomas dot johnson at oregonstate dot edu) - Oregon State University

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

* Jeremy Frumkin (frumkinj at u dot library dot arizona dot edu) - University of Arizona

== T-Shirt Committee ==

This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes.

* Ann Lally (alally at uw dot edu) University of Washington

== Social Activities Committee ==

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

* Jennifer Ward (jlward1 at uw dot edu) -- University of Washington

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

* Mike Giarlo -- Penn State

== Hospitality Suite Committee ==

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

* Mike Giarlo -- Penn State
* Tom Johnson -- Oregon State University

== 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 gmail dot com) -- Miami University/Grinnell College
* Bohyun Kim(kimb at fiu dot edu) -- Florida International University

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

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

== IRC Access ==
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful.

==Registration Desk Volunteers==
The Registration Desk has a group from IU to register C4L attendees, but we need an additional 1-2 volunteers to hang out for 2-hour shifts and be there to help out. Also on Monday and Tuesday, an additional volunteer with IU Wireless access knowledge would be helpful on the Registration Desk to answer tech questions.

== Microphone Runners==

Run wireless handheld microphones to audience members asking questions.

== Session Timer Volunteers ==

People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop with a stopwatch program).

* Ann Gleason (amwhit24 at uw dot edu) - University of Washington

'''Schedule for Session Timers'''

== Raffles ==
(calling awardees)
(backup)
(program)

= 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: Code4Lib2012]]

2012 committees sign-up page

2011-06-14T16:39:48Z

Tjohnson: /* Hospitality Suite Committee */

= Code4Lib 2012 Committees =

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

== Book Give-Away Committee ==

* Kevin S. Clarke (ksclarke@gmail.com) -- McHenry Library, UC Santa Cruz

== Sponsorships Committee ==

This committee organizes the sponsorship activities. Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.

* Kyle Banerjee (banerjek@uoregon.edu) -- Orbis Cascade Alliance
* Anjanette Young -- University of Washington
* Mike Giarlo -- Penn State

== Keynote Speakers Committee ==

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

* Ann Lally (alally at uw dot edu) University of Washington
* Dre (akorphan at ncsu dot edu) North Carolina State University

== Program Committee ==

This committee plans the structure of the program, arranges the voting on presentations, etc. These folks will also announce speakers, etc.

* Jeremy Frumkin (frumkinj at u dot library dot arizona dot edu) - University of Arizona
* Ranti Junus (ranti.junus at gmail) - Michigan State University
* John Fink (john.fink at gmail) - McMaster University
* Tom Johnson (thomas.johnnson at oregonstate dot edu) - Oregon State University

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

* Jeremy Frumkin (frumkinj at u dot library dot arizona dot edu) - University of Arizona

== T-Shirt Committee ==

This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes.

* Ann Lally (alally at uw dot edu) University of Washington

== Social Activities Committee ==

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

* Jennifer Ward (jlward1 at uw dot edu) -- University of Washington

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

* Mike Giarlo -- Penn State

== Hospitality Suite Committee ==

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

* Mike Giarlo -- Penn State
* Tom Johnson -- Oregon State University

== 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 gmail dot com) -- Miami University/Grinnell College
* Bohyun Kim(kimb at fiu dot edu) -- Florida International University

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

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

== IRC Access ==
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful.

==Registration Desk Volunteers==
The Registration Desk has a group from IU to register C4L attendees, but we need an additional 1-2 volunteers to hang out for 2-hour shifts and be there to help out. Also on Monday and Tuesday, an additional volunteer with IU Wireless access knowledge would be helpful on the Registration Desk to answer tech questions.

== Microphone Runners==

Run wireless handheld microphones to audience members asking questions.

== Session Timer Volunteers ==

People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop with a stopwatch program).

* Ann Gleason (amwhit24 at uw dot edu) - University of Washington

'''Schedule for Session Timers'''

== Raffles ==
(calling awardees)
(backup)
(program)

= 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: Code4Lib2012]]

2012 committees sign-up page

2011-06-14T16:39:21Z

Tjohnson: /* Program Committee */

= Code4Lib 2012 Committees =

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

== Book Give-Away Committee ==

* Kevin S. Clarke (ksclarke@gmail.com) -- McHenry Library, UC Santa Cruz

== Sponsorships Committee ==

This committee organizes the sponsorship activities. Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.

* Kyle Banerjee (banerjek@uoregon.edu) -- Orbis Cascade Alliance
* Anjanette Young -- University of Washington
* Mike Giarlo -- Penn State

== Keynote Speakers Committee ==

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

* Ann Lally (alally at uw dot edu) University of Washington
* Dre (akorphan at ncsu dot edu) North Carolina State University

== Program Committee ==

This committee plans the structure of the program, arranges the voting on presentations, etc. These folks will also announce speakers, etc.

* Jeremy Frumkin (frumkinj at u dot library dot arizona dot edu) - University of Arizona
* Ranti Junus (ranti.junus at gmail) - Michigan State University
* John Fink (john.fink at gmail) - McMaster University
* Tom Johnson (thomas.johnnson at oregonstate dot edu) - Oregon State University

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

* Jeremy Frumkin (frumkinj at u dot library dot arizona dot edu) - University of Arizona

== T-Shirt Committee ==

This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes.

* Ann Lally (alally at uw dot edu) University of Washington

== Social Activities Committee ==

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

* Jennifer Ward (jlward1 at uw dot edu) -- University of Washington

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

* Mike Giarlo -- Penn State

== Hospitality Suite Committee ==

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

* Mike Giarlo -- Penn State

== 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 gmail dot com) -- Miami University/Grinnell College
* Bohyun Kim(kimb at fiu dot edu) -- Florida International University

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

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

== IRC Access ==
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful.

==Registration Desk Volunteers==
The Registration Desk has a group from IU to register C4L attendees, but we need an additional 1-2 volunteers to hang out for 2-hour shifts and be there to help out. Also on Monday and Tuesday, an additional volunteer with IU Wireless access knowledge would be helpful on the Registration Desk to answer tech questions.

== Microphone Runners==

Run wireless handheld microphones to audience members asking questions.

== Session Timer Volunteers ==

People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop with a stopwatch program).

* Ann Gleason (amwhit24 at uw dot edu) - University of Washington

'''Schedule for Session Timers'''

== Raffles ==
(calling awardees)
(backup)
(program)

= 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: Code4Lib2012]]