Code4Lib - User contributions [en]

2015 Prepared Talk Proposals

2014-11-05T13:56:34Z

Jthomale:

Code4lib 2015 is a loosely-structured conference that provides people working at the intersection of libraries/archives/museums/cultural heritage and technology with a chance to share ideas, be inspired, and forge collaborations. For more information about the Code4lib community, please visit http://code4lib.org/about/.
The conference will be held at the Portland Hilton & Executive Tower in Portland, Oregon, from February 9-12, 2015.

'''Proposals for Prepared Talks:'''

We encourage everyone to propose a talk.

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

Proposals can be submitted through Friday, November 7, 2014 at 5pm PST (GMT−8). Voting will start on November 11, 2014 and continue through November 25, 2014. The URL to submit votes will be announced on the Code4Lib website and mailing list and will require an active code4lib.org account to participate. The final list of presentations will be announced in early- to mid-December.

'''Proposals for Prepared Talks:'''

Log in to the Code4lib wiki and edit this wiki page using the prescribed format. If you are not already registered, follow the instructions to do so.
Provide a title and brief (500 words or fewer) description of your proposed talk.
If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist voters in opening the conference to new presenters.

Please follow the formatting guidelines:

<pre>

== Talk Title: ==

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

Abstract of no more than 500 words.

</pre>

'''Talk Proposals'''
==Refinery — An open source locally deployable web platform for the analysis of large document collections==

* [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com

Refinery is an open source web platform for the analysis of large unstructured document collections. It extracts meaningful semantic themes within documents also known as "topics" which can be thought of as word clouds composed of terms that highly co-occur with one another. Once this semantic index is formed, one can extract relevant documents related to these topics and further refine their contents through a summarization process that allows users to search for phrases that are relevant to them within the corpus. The goal of Refinery is to make this whole process easier and to provide some of the latest scalable versions of these learning algorithms in an intuitive web-based interface. Refinery is also meant to be run locally, thus bypassing the need for securing document collections over the internet. The talk will go through some of the technologies involved and a demo of the app.

For more info check out http://www.docrefinery.org.

==Drupal 8 — Evolution & Revolution==

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

Drupal 8 is in beta and nearing release. Among its many features, it notably has become more developer friendly through its adoption of the Symfony PHP framework along with Symfony's outstanding set of libraries (like Guzzle) and tools (like Composer). And, in implementing the Twig theming system, it is can begin to escape PHPtemplate. These moves also make it easier to create headless systems that uses Angular.js and other systems for presentation, or even forgo presentation entirely.

From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.

==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==

* [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]], stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]

GameSalad is a popular tool for developing mobile and desktop games with little actual programming. In this presentation, Stan Bogdanov breaks down the development process he followed while building [https://github.com/stanrb/mobiLit mobiLit], a mobile app with the goal of being the first open-source gamified information literacy app to be used as part of a college-level information literacy curriculum. He will go through the basics of using GameSalad to create an app that can be easily customized by non-programmers and the instructional principles used to teach the material in a mobile medium. Stan will also go through two qualitative design studies he did on the app and discuss their results and the lessons learned from building mobiLit. The session will conclude with an overview of the next steps for the [https://github.com/stanrb/mobiLit mobiLit project].

==The Impossible Search: Pulling data form unknown sources==

* Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com

It's easy to search data you know the structure of, but what if you need to pull in data from sources that don't have a standard structure. The ability to search community events along with your standard catalog search results is an example, but often the only way to pull these events is through XML, JSON, (Insert structured format here), or even just raw html. But how do you get that structure? That simple question is what makes this impossible. The process to define and process this structure takes a lot of manual labor, especially if the data you are pulling is just HTML, and then every time you add data to the index you have to run all the data through a script to pull in data in a format Solr or an other index can use. This talk will focus on Solr, but the principles explained will apply to many other indexes.

==What! You're Not Using Docker?==

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

Boring part: Docker[1] is a container system that provides benefits similar to virtualization with only a fraction of the overhead. Scintillating part: Docker can host between four to six times the number of service instances than systems such as Xen or VMWare on a given piece of hardware. But thats not all! Docker also makes it simple(r) to create transportable instances, so you can spin up development servers on your laptop.

*[1]https://www.docker.com/

== Video Accessibility, WebVTT, and Timed Text Track Tricks ==

* Jason Ronallo, jronallo@gmail.com, NCSU Libraries

Video on the Web presents new challenges and opportunities. How do you make your video more accessible to those with various disabilities and needs? I'll show you how. This presentation will focus on how to write and deliver captions, subtitles, audio descriptions, and timed metadata tracks for Web video using the WebVTT W3C standard. Encoding timed text tracks in this way opens up opportunities for new functionality on your websites beyond accessibility. The presentation will show some examples of the potential for using timed text tracks in creative ways. I'll cover all the HTML and JavaScript you will need to know as well as some of the CSS and other bits you could probably do without but are too fun to pass up.

== Categorizing Records with Random Forests ==

* Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library
Academic libraries are increasingly responsible for providing ingest, search, discovery, and analysis for data sets. Emerging techniques from data science and machine learning can provide librarians and developers with an opportunity to generate new insights and services from these document collections. This presentation will provide a brief overview of common machine learning classification techniques, then dive into a more detailed example using a random forest to assign keywords to research data sets. The talk will emphasize the insight that can be gained from machine learning rather than the inner workings of the algorithms. The overall goal of this presentation is to provide librarians and developers with the context to recognize an opportunity to apply machine learning categorization techniques at their home campuses and organizations.

== Data Science in Libraries ==

* Devon Smith, smithde@oclc.org, OCLC

Data Science is increasing in buzz and hype. I'll go over what it is, what it isn't, and how it fits in libraries.

== PDF metadata extraction for academic literature ==

* Kevin Savage, kevin.savage at mendeley.com, Mendeley
* Joyce Stack, joyce.stack at mendeley.com, Mendeley

Mendeley recently added a, "document from file," endpoint to its API which attempts to extract metadata such as title and authors directly from PDF files. This talk will describe at a high level the machine learning methods we used including how we measured and tuned our model. We will then delve more deeply into our stack, the tools we used, some of the things that didn't work and why PDFs are the worst thing ever to compute over.

== Giving Users What They Want: Record Grouping in VuFind ==

* Mark Noble, mark@marmot.org, [//www.marmot.org Marmot Library Network]

In 2013, Marmot did extensive usability studies with patrons to determine what was difficult in the catalog. Many patrons had problems sifting through all of the various formats and editions of a title. In 2014 we developed a method for [//mercury.marmot.org/Union/Search?lookfor=divergent grouping records] so only a single work is shown in search results and all formats and editions are listed under that work. We will discuss our definition of a 'work' based on FRBR principles; combining meta data from MARC records with metadata from other sources like OverDrive; the technical details of Record Grouping; the design decisions made during implementation; and the reaction from users and staff.

== Topic Space: a mobile augmented reality recommendation app ==

* Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign

The Topic Space module (http://minrvaproject.org/modules_topicspace.php ) was developed with an IMLS Sparks! Grant to investigate augmented reality technologies for in-library recommendations. The funding allowed for sustained university community collaboration by the University Library, the Graduate School of Library and Information Science, as well as graduate student programmers sourced from the Department of Computer Science. Collaborators designed app functionality and identified relevant open source libraries that could power optical character recognition (OCR) functionality from within the mobile phone.

Topic space allows a user to take a picture of an item's call number in the book stacks. The module will show the user other books that are relevant but that are not shelved nearby. It can also show users books that are normally shelved here but that are currently checked out. Recommendations are based on Library of Congress subject headings and ILS circulation data which indicate recommendation candidates based on total check-outs.

Research questions included development of back end (server-side) pattern matching algorithms for recommendations, and a rapid formative evaluation of interface design that would provide optimal user experience for navigation of the book stacks as a context to recommendations.

Along with the Topic Space native app, grant collaborators prototyped web based recommendations which could serve as a new way of providing readers advisory and “more like this” recommendations from discovery interfaces accessed through desktop browsers. Outcomes of the grant include the availability of the [https://play.google.com/store/apps/details?id=edu.illinois.ugl.minrva Topic Spaces module within Minrva app on the Android Play store] and an experimental [http://backbonejs.org/ Backbone.js] based [http://minrva-dev.library.illinois.edu Topic Space web app].

== Leveling Up Your Git Workflow ==

* Megan Kudzia, moneill@albion.edu, Albion College Library
* Kate Sears, eks11@albion.edu, Albion College Library

Have you started experimenting with Git on your own, but now you need to include others in your projects? Learn from our mistakes! Transitioning from a one-person git workflow and repo structure, to a structure that includes multiple people (including student workers), is not for the faint of heart. We'll talk about why we decided to work this way, our path to developing a git culture amongst ourselves, conceptual and technical difficulties we've faced, what we learned, and where we are now. Also with pretty pictures (aka workflow drawings).

== Drone Loaning Program: Because Laptops are so last century ==

* Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries
* Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries

At Univ. Maryland we are in the very early stages of looking into allowing our student body get their hands on a drone. Yes that's right we will let students take out a drone for n amount of hours to work on projects of their choosing. The talk will talk about the logistics of getting a program of this sort from concept to "Is the drone available?". If people sign waivers we will also promise not to crash the drone into code4lib attendees.

== Got Git? Getting More Out of Your GitHub Repositories ==

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

This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories.

In additional to all of the great benefits of using Git for code management, the GitHub interface provides a powerful set of tools to showcase a project and to keep your users informed of developments to your project. These tools can assist with marketing and outreach - turning your code repository into a focus of conversation!

* [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]
* [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]
* [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]
* [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]
* Gists for code sharing
* Private Repositories and Organizational Groups
* Pull Request Conversation Tracking
* Customized Issue management

== Quick Wins for Every Department in the Library - File Analyzer! ==

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

The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.
* Analyzing Marc Records for the Cataloging department
* Transferring ILS invoices for the University Account System for the Acquisitions department
* Delivering patron fines to the Bursar’s office for the Access Service department
* Summarizing student worker timesheet data for the Finance department
* Validating COUNTER compliant reports for the Electronic Resources department
* Generating ingest packages for the Digital Services department
* Validating checksums for the Preservation department

Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!

==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==

* [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor

The transition from paper maps to digital ones changed much more than the maps themselves; it changed the very foundation of how we work and how we find each other. Now maps are transforming again. The Geospatial World is moving from GIS systems that are institutionally-focused, expensive, feature-burdened, and binds data into a complicated and demanding user-hostile interface. From this transition from digital to web-based digital geospatial tools has come growth and development in new forms of map-based investigative journalism, activism, scholarship, and business ventures. This talk will highlight the conditions and strategies that made these changes possible as a means to draw a path by which librarians through our own work may follow, dragons notwithstanding.

== Building Your Own Federated Search ==

* Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco

Advances in modern browsers have created some interesting possibilities for federated search. This presentation will cover common techniques and pitfalls in building a federated search. We will discuss what principles guided our decisions when implementing our own federated search. We will show tools we've built and our findings from building and using experimental prototypes.

Your higher education institution likely offers dozens of online resources for educators, students, researchers, and the public. And each of these online resources likely has its own search tool. But users can't be expected to search in dozens of different interfaces to find what they're looking for. A typical solution for this issue is federated search.

== Indexing Linked Data with LDPath ==

* Chris Beer, cabeer@stanford.edu, Stanford University Libraries

LDPath [1] is a simple query language for indexing linked open data, with support for caching, content negotiation, and integration with non-RDF endpoints. This talk will demonstrate the features and potential of the language and framework to index a resource with links into id.loc.gov, viaf.org, geonames.org, etc to build an application-ready document.

[1] http://marmotta.apache.org/ldpath/language.html

== Show Me the Money: Integrating an LMS with Payment Providers ==

* Josh Weisman, Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group

In order to provide an easy and convenient way for patrons to pay fines, we are exploring ways to integrate the library management system with online payment providers such as PayPal. With many LMS systems being designed and developed for the cloud, we should be able to provide the frictionless user experience our patrons have come to expect from online transactions. In this session we'll discuss strategies for integration and review a sample application which uses REST APIs from a library management system to integrate with PayPal.

== Shibboleth Federated Authentication for Library Applications: ==

* Scott Fisher, scott.fisher@ucop.edu, California Digital Library
* Ken Weiss, ken.weiss@ucop.edu, California Digital Library

Shibboleth is the most widely-used method to provide single-sign-on authentication to academic applications where users come from many different institutions. Shibboleth, the InCommon education and research trust framework, and the SAML protocol comprise a very powerful - but very complicated - solution to this very complicated problem. Scott and Ken have implemented Shibboleth for multiple library applications. They will share their understanding of the good, the bad, and the underlying spaghetti that makes it all work. Ken will discuss some of the technical aspects of the solution, touching on optimal and non-optimal use cases, administrative challenges, and authorization concerns. Scott will describe the implementation pattern for multi-institution single-sign-on that the California Digital Library has evolved, using the recently released Dash application (http://dash.cdlib.org) as an example.

==Scientific Data: A Needs Assessment Journey==

*[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History

While surveying digital research and collections data in the research science divisions at the American Museum of Natural History in NYC (as a part of my [http://ndsr.nycdigital.org/ National Digital Stewardship Residency] project), I have come across the big data hogs (genome sequencing and CT scanning) and the little pieces of data (images, publications), all equally important to not only scientific discovery, but as nodes in the history of science.

In this session, I will discuss the development of my needs assessment surveys for scientific datasets and the interview process with Museum curators and researchers as background, seguing into an explanation of the results. I will then combine my findings into preliminary selection criteria to choose tools for digital preservation and management unique to scientific datasets. This will brooke a discussion on emerging standards, tools, and technologies in big data, specific to research science.

I will conclude with preliminary findings on emerging technology that can be used to answer concerns surrounding the management and digital preservation of these data. I am hoping the Q&A session can be used to both answer questions about my project, and function as a way for you (the larger tech-savy library community) to discuss the tools I’ve touched on in this talk.

== Feminist Human Computer Interaction (HCI) in Library Software ==

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

Libraries are not neutral repositories of knowledge. Library classification systems and search technologies tend to reflect the inequalities, biases, ethnocentrism, and power imbalances of the societies in which they are built [1]. How might we better resist these tendencies in the library software we create? This talk will examine some qualities of feminist HCI (pluralism, self-disclosure, participation, ecology, advocacy, and embodiment) [2] through the lens of library software.

[1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.

[2] Bardzell, Shaowen. Feminist HCI: Taking Stock and Outlining an Agenda for Design. CHI 2010: HCI For All. http://dmrussell.net/CHI2010/docs/p1301.pdf

== Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==

* Audrey Altman, audrey at dp.la, Digital Public Library of America
* Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America
* Mark Breedlove, mark at dp.la, Digital Public Library of America

The Digital Public Library of America aggregates metadata for over 8 million objects from more than 24 direct partners, or Hubs, using its Metadata Application Profile (MAP), an RDF metadata application profile based on the Europeana Data Model. After working with the initial system for harvesting, mapping and enhancing our Hub’s metadata for a year, we realized that it was inadequate for working with data at this scale. There were architectural issues; it was opaque to non-developer and partner staff; there were inadequate tools for quality assurance and analysis; and the system was unaware that it was working with RDF data. As the network of Hubs expanded and we ingested more metadata, it became harder and harder to know when or why a harvest, a mapping task, or an enrichment went wrong because the tools for quality assurancewere largely inadequate.

The DPLA Content and Technology teams decided to develop a new system from the ground up to address those problems. Development of Heidrun, the internal version of the new system, started in October 2014. Heidrun’s goals are to make it easier for us to harvest and map metadata from various sources and in variety of schemas to the DPLA MAP, to better enrich that metadata using external data sources, and to actively involve our partners in the ingestion process through access to better QA tools. Heidrun and its componentry are built on Ruby on Rails, Blacklight, and ActiveTriples. Our presentation will give some background on our design principles and processes used during development, the architecture of the system, and its functionality. We plan to release a version of Heidrun and its components as a generalized metadata aggregation system for use by DPLA Hubs and others working to aggregate cultural heritage metadata.

== OS or GTFO: Program or Perish ==
*Tessa Fallon, tessa.fallon@gmail.com

Description TBD

== Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==
* Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries
Would your library like to have large digital signage that displays dynamic information such as library hours, weather, room availability, and more? Have you looked into purchasing large digital signage, only to be turned off by the high price tag and lack of customization available with commercial solutions? Our library has developed a cheap and effective alternative to these systems using HTML 5 authoring software, a large TV, and freely-available APIs from Google, Springshare, and others. At this session, you’ll learn about the system that we have in place for displaying dynamic and easily-updatable information on our library’s large digital display, and how you can easily create something similar for your library.

== REPOX: Metadata Blender ==

* John Mignault, jmignault@metro.org, Empire State Digital Network

With the growth in the number of hubs providing metadata to the Digital Public Library of America, many of them are using REPOX, a tool originally created for the Europeana project. We'll take a look at REPOX and its capabilities and how it can be useful for ingesting and transforming metadata.

== Beyond Open Source ==

* Jason Casden, jmcasden@ncsu.edu, NCSU Libraries
* Bret Davidson, bddavids@ncsu.edu, NCSU Libraries

The Code4Lib community has produced an increasingly impressive collection of open source software over the last decade, but much of this creative work remains out of reach for large portions of the library community. Do the relatively privileged institutions represented by a majority of Code4Lib participants have a professional responsibility to support the adoption of their innovations?

Drawing from old and new software packaging and distribution approaches (from freeware to Docker), we will propose extending the open source software values of collaboration and transparency to include the wide and affordable distribution of software. We believe this will not only simplify the process of sharing our applications within the Code4Lib community, but also make it possible for less well resourced institutions to actually use our software. We will identify areas of need, present our experiences with the users of our own open source projects, discuss our attempts to go beyond open source, and make an argument for the internal value of supporting and encouraging a vibrant library ecosystem.

[[Category:Code4Lib2015]]
[[Category:Talk Proposals]]

== Making It Work: Problem Solving Using Open Source at a Small Academic Library ==

* Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology
* Max King, mking9@iit.edu, Illinois Institute of Technology

The Illinois Institute of Technology campus was added to the National Register of Historic Places in 2005, and contains a building, Mies van der Rohe's S.R. Crown Hall, that was named a National Historic Landmark in 2001. Creating a digital resource that can adequately showcase the campus and its architecture is challenge enough in and of itself, but doing so as a two-person team of relative newcomers, at a university library without dedicated programmers on staff, ups the ante considerably.
The challenges of technical know-how, staff time, and funding are nothing new to anyone working on digital projects at a university library, and are amplified when doing so at a smaller institution. This talk covers the conception, development, and design of the campus map site that was built, concentrating on the problem-solving strategies developed to cope with limited technical and financial resources.
We'll talk about our approach to development with Open Source software, including Omeka, along with the Neatline and Simile Timeline plugins. We'll also discuss the juggling act of designing for mobile mapping functionality without sacrificing desktop design, weighing the costs of increased functionality versus our ability to time-effectively include that functionality, and the challenge of building a site that could be developed iteratively, with an eye towards future enhancement and sustainability. Finally, we’ll provide recommendations for other librarians at smaller institutions for their own efforts at digital development.

== Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==

* Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art

The Museum of Modern Art has amassed a large collection of audiovisual materials over its many decades of existence. In order to preserve these materials, much of the audiovisual collection has been digitized. This is a complex process involving numerous steps and devices, and the methods used for digitization can have an effect on the quality of the file that is preserved. Therefore, knowing exactly how something was digitized is critical for future stewards of these objects to be able to properly care for and preserve them. However, detailed technical information about the processes involved in the digitization of audiovisual materials is not defined explicitly in most metadata schemas used for audiovisual materials. In order to record process history using existing metadata standards, some level of creativity is required to allow existing standards to express this information.

This talk will detail different metadata standards, including PBCore, PREMIS, and reVTMD, that can be implemented as methods of recording this information. Specifically, the talk will examine efforts to integrate this metadata into the Museum of Modern Art’s new digital repository, the DRMC. This talk will provide background on the DRMC as well as MoMA’s specific institutional needs for process history metadata, then discuss different metadata implementations we have considered to document process history.

== Pig Kisses Elephant: Building Research Data Services for Web Archives ==

* Jefferson Bailey, jefferson@archive.org, Internet Archive
* Vinay Goel, vinay@archive.org, Internet Archive

More and more libraries and archives are creating web archiving programs. For both new and established programs, these archives can consist of hundreds of thousands, if not millions, of born-digital resources within a single collection; as such, they are ideally suited for large-scale computational study and analysis. Yet current access methods for web archives consist largely of browsing the archived web in the same manner as browsing the live web and the size of these collections and complexity of the WARC format can make aggregate analysis difficult. This talk will describe a project to create new ways for users and researchers to access and study web archives by offering extracted and post-processed datasets derived from web collections. Working with the 325+ institutions and their 2600+ collections within the Archive-It service, the Internet Archive is building methods to deliver a variety of datasets culled from collections of web content, including extracted metadata packaged in JSON, longitudinal link graph data, named entities, and other types of data. The talk will cover the technical details of building dataset production pipelines with Apache Pig, Hadoop, and tools like Stanford NER, the programmatic aspects of building data services for archives and researchers, and ongoing work to create new ways to access and study web archives.

== Awesome Pi, LOL! ==

* Matt Connolly, mconnolly@cornell.edu, Cornell University Library
* Jennifer Colt, jrc88@cornell.edu, Cornell University Library

Inspired by Harvard Library Lab’s “Awesome Box” project, Cornell’s Library Outside the Library (LOL) group is piloting a more automated approach to letting our users tell us which materials they find particularly stunning. Armed with a Raspberry Pi, a barcode scanner, and some bits of kit that flash and glow, we have ventured into the foreign world of hardware development. This talk will discuss what it’s like for software developers and designers to get their hands dirty, how patrons are reacting to the Awesomizer, and LOL’s not-afraid-to-fail philosophy of experimentation.

== You Gotta Keep 'em Separated: The Case for "Bento Box" Discovery Interfaces ==

* Jason Thomale, jason.thomale@unt.edu, University of North Texas Libraries

I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.

The thing is, practically all of us--in academic libraries at least--have a similar set up for discovery, with just a few variations, and so talking about it still seems useful. Stop me if this sounds familiar. You've got a single search box on the library homepage as a starting point for discovery. And it's probably a tabbed affair, with an option for searching the catalog for books, an option for searching a discovery service for articles, an option for searching databases, and maybe a few others. Maybe you have an option to search everything at once--probably the default, if you have it. And, if you're a crazy hepcat, maybe you ''only'' have your one search that searches everything, with no tabs.

Now, the question is, for your "everything" search, are you doing a combined list of results, or are you doing it bento-box style, with a short results list from each category displayed in its own compartment?

At UNT, we've been holding off on implementing an "everything" search, for various reasons. One reason is that the evidence for either style hasn't been very clear. There's this persistent paradox that we just can't reconcile: users tell us, through word and action, that they prefer searching Google, yet, libraries aren't Google, and there are valid design reasons why we shouldn't try to oversimplify our discovery interfaces to be like Google. And there's user data that supports both sides.

Holding off on making this decision has granted us 2 years of data on how people use our tabbed search interface that does ''not'' include an "everything" search. Recently I conducted a thorough analysis of this data--specifically the usage and query data for our catalog and discovery system (Summon). And I think it helps make the case for a bento box style discovery interface. To be clear, it isn't exactly the smoking gun that I was hoping for, but the picture it paints I think is telling. At the very least, it points away from a combined-results approach.

I'm proposing a talk discussing the data we've collected, the trends we've seen, and what I think it all means--plus other reasons that we're jumping on the "bento box" discovery bandwagon and why I think "bento box" is at this point the path that least sells our souls.

2013 Lightning Talks Signup

2013-02-12T16:27:18Z

Jthomale: /* Thursday, 10:15-11:00am [9 slots] */

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

Have something to add but didn't get a chance to do it in Chicago? Consider signing up to present at the [[Virtual Lightning Talks]] on April 3rd, 2013.

'''LIGHTNING TALK SIGNUPS OPEN AT 10 AM EST ON FEBRUARY 12'''

Those who already have presentation slots, please hold off and give those without slots lightning talk chances, to spread around the opportunity to talk to the conference.

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

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

# Cynthia Ng / RULA Bookfinder
# Julien Gibert - turning a solr response into a rdf file
# Bill Dueber -- Datamart report generator at UMich
# Jonathan Rochkind -- bento_search
# Ross Singer - How are you managing copyright?
# Masao Takaku - saveMLAK project for two years - http://savemlak.jp/
# Jon Stroop - Loris Image Server
# Eric Nord - Candybars for bugs
# Megan O'Neill Kudzia -- games for pedagogy in the library
# Geoffrey Boushey - GEDI reference app for Inter Library Loan
# john sarnowski - Audio archiving with full text search
# George Campbell - three.js: 3D Objects in the browser

=== Wenesday, 4:20-5:20pm [12 slots] ===

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

# Jeremy Morse -- mPach: Publishing directly into HathiTrust
# Steven Bassett -- RWD Retrofit
# Demian Katz - gamebooks.org, Geeby-Deeby, and the Dime Novel Bibliography Project.
# Rachel Frick -- LODLAM Summit 2013 and Challenge
# Kenny Ketner -- Occam's Reader
# Al Cornish - Orbis Cascade Alliance Shared ILS Project
# Makoto Okamoto -- Crowd Funding for Library in Japan
# Ryan Rotter -- HathiTrust ingest tools
# Rosalyn Metz -- What I learned while I was away
# Nettie Lagace -- recent cool fun NISO activities
# chuck koscher-- Fundref
# Andromeda Yelton -- I'll get bak to you on the title ;)

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

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

#
# James Stuart - Taming Email
# Jason Casden and Cory Lown - My #HuntLibrary
# Steven Anderson - Details TBA
# Will Hicks - Metadata entry beyond usability
#
#
#
#

[[Category:Code4Lib2013]]

2013 preconference proposals

2013-02-08T19:32:34Z

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

Please sign up to attend by January 15th. Doesn't mean you can't change your mind, but we will use the host committee will use these numbers to assign rooms.

Proposals '''now closed'''.

Spaces available: 4+ Rooms

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

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

Description.
</pre>

==Full Day==

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

This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

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

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

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

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

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

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

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

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

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

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

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

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:
* group discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/heroku-360link Py360 Link].

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

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

=== Intro to Blacklight CANCELED ===

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

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

RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language and the Rails framework. Participants will build a working Rails application.

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

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

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

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

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

Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called "Big Data" problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, MongoDB, and Neo4j.

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

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

* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

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

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

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

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

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

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

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome

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

=== DPLA Intro/Hacking ===
====Seminar Room A of Richard J. Daley Library, 1:30 pm to 5:30 pm on Monday, February 11====
* Presenter(s)/Leader(s): Nate Hill (Chattanooga Public Library, DPLA Audience and Participation Co-chair), SJ Klein (Wikimedia, OLPC, DPLA Technical Aspects Co-chair), Jeff Licht (DPLA Technical Development Project Manager)

The [http://dp.la Digital Public Library of America] (DPLA) is an open source metadata repository that provides read-only access to millions of records from across the United States via an open REST API. All API queries are returned as JSON-LD, a lightweight linked data format, and the metadata is freely reusable under a CC0 public domain license. A front-end portal is currently under development and will be launched in April 2013, though it will serve as but one way into the DPLA’s data. The DPLA encourages the development of applications and tools by developers of all skill levels and backgrounds. In this workshop, participants will actively code against the API to make apps, visualization tools, plug-ins, and other interesting tools that make use of DPLA data.

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

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

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

The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans ("The Pivot"), and failing more cheaply.

Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:

# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.
# Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:
#* Technical failure
#* Failure to effectively address a real user need
#* Overinvestment
#* Outreach/Promotion failure
#* Design/UX failure
#* Project team communication failure
#* Missed opportunities (risk-averse failure)
#* Successes gleaned from failures
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.
# A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.

I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.

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

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

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format. Sounds like this is an evening thing that might happen at a bar somewhere?

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

[[Category:Code4Lib2013]]

Main Page

2011-03-31T20:55:24Z

Jthomale: /* Current topics */

{|align=right
|__TOC__
|}

== About Code4Lib ==

* [[About Code4Lib]] - Background and history of the community
* [[A Guide for the Perplexed]] - Building skills for working with library technologies

== Code4Lib 2011 Conference ==
''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2011 Code4lib2011 category]''

* [http://code4lib.org/conference/2011 C4L2011 Home]
* [[C4L2011_registration | Registration Information!]]
* [[2011_committees_sign-up_page | 2011 Committees Sign-Up]] - '''Volunteer to help'''
* [[How To Plan A Code4LibCon]]
* [[C4L2011_social_activities|Social Activities]] - ideas & sign-up
* [[C4L2011_planning_wishlist|'''Put your ideas for 2011 here!''']]
* [http://www.facebook.com/event.php?eid=161853827200024 Facebook Event Page]
* [http://events.linkedin.com/Code4Lib-2011/pub/448897 LinkedIn Event Page]

=== Transportation ===
* [[C4L2011_rideshare|Airport Ride Share and Carpooling]]

=== Room Sharing ===
* [[C4L2011_roomshare | Hotel room share]]

== Local / Regional Groups ==

* [[NYC|Code4LibNYC]] - NYC and surrounding areas
* [[NEC4L|New England Code4lib]] - New England
* [http://se.code4lib.org Southeastern Code4lib] - North Carolina, Virginia, Tennessee, etc.
* [[NL|Code4Bib]] - Dutch Code4Bib
* [[MDC|Code4libMDC]] - Maryland, Washington D.C and surrounding areas
* [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest
* [[North|code4lib North]] - Ontario and surrounding areas ''(new for Jan 2010!)''
* [[Midwest|Code4Lib Midwest]] - Wherever that is...
* [http://groups.google.com/group/ikr-fejlesztok/ Code4lib.hu] - Group of Hungarian library developers
* [http://www.code4lib.jp/ Code4Lib Japan] - ''(new in 2010!)'', see also [http://twitter.com/yesonline/statuses/28561046501 tweet from Jerry Lee]
* [http://groups.google.com/group/code4glam Code4GLAM Australia] - coders, hackers, developers and technologists in the Australian GLAM (Galleries, Libraries, Archives & Museums) sector.

== Interest Groups ==

* [[ILS_Interop|ILS Interoperability]] - A group working to develop an infrastructure for interoperating between discovery layers and integrated library systems.
* [[Open_Source_Book_Widgets|Open Source Book Widgets]] - A list of open source book widgets
* [[Discovery|Open Source Discovery]] - Open Source application to enhance and support "discovery" in libraries
* [[Mobile_Apps|Mobile Applications]] - A group interested in mobile web and native application development for libraries
* [[Sources_Of_Metadata|Sources Of Metadata]] - list of api's and sources of interest to libraries

== Software Usage and Documentation ==

* [[Umlaut]] - OpenURL link resolving middleware
* [[:Category:Patterns|Patterns for Collaborative Code]] - Patterns to make your open source 'more open', more amenable to distributed development and use at multiple institutions without forking.
* [[ILS Documentation]]
* [[OSS Directory]]
* [[Working with MaRC]]
* [[Rogue]] - principles for standards creation

== Code4Lib Journal ==

* [[:Category:Code4Lib Journal|Code4Lib Journal]] - information and working documents

== Current topics ==

* [[OCLC Policy Change]]
* [[SirsiDynix: Integrated Library System Platforms on Open Source]]
* [[Parsing Library Data]]

== Other Code4Lib Sites ==

* [http://www.code4lib.org/ code4lib.org]
* [http://planet.code4lib.org planet.code4lib.org]

== Code4Lib 2012 Conference ==
''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2012 Code4lib2012 category]''

* [[C4L2012_Call_For_Host|'''2012 Call For Host''']]
* [http://sites.google.com/site/code4lib2012seattle/ Seattle proposal.]

== Earlier Conferences and events ==

== Code4libcon 2010 ==
''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2010 Code4lib2010 category]''
* [http://code4lib.org/conference/2010/schedule Finalized schedule]
* [[2010 Lightning Talks Signup]] - sign up to give a lightning talk
* [[2010 Breakout Sessions]] - suggest a breakout here
* '''[[2010 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff'''
* [[C4L2010_social_activities|Social Activities]] - ideas & sign-up
* [[Committees sign-up page]] - '''Volunteer to help'''
* [[C4L2011_planning_wishlist|'''Put your ideas for 2011 here!''']]

=== Transportation ===
* [[Asheville Airport to Hotel Van Manifest]]
* [[C4L2010rideshare|General shared travel/transportation planning]]
* [[C4L2010planning:RoommatesRidesEtc|Roommates, Rides, Etc]]

=== Deals ===
* [[C4L2010_manning_discount|Manning Publications Discount]] - discount code (40% off) for use by attendees through Feb. 28, 2010
* Thanks also to our other sponsors!

=== Asheville planning ===
* [[C4L2010planning|2010 Planning]]
* [[C4L2010planning:_wishlist | 2010 Planning Wishlist]] - planning page for issues, expectations, etc. for the 2010 conference

== Code4libcon 2009 ==
* [[BookRaffle]] - coordinate begging publishers for books to raffle off at the conference
* [http://inkdroid.org/c4l2009/attendees Get FOAFed] - add your FOAF profile to the network of c4l2009 attendees
* PreConferences:
** [[GIS_preconf_code4libcon2009]] - Open source GIS just like mom used to make
** [[LinkedData]] - A proposal for a linked-data code4lib2009 pre-conference
** [[LibX_Preconference]] - Proposal for a half-day pre-conference targeted at developers who wish to use the LibX 2.0 platform
** [http://code4lib.org/2009/oclc-precon OCLC Grid Services Preconference]
* [[RoommatesRidesEtc]] - Find roommates for Code4Lib 2009, share rides, etc.
* [[2009 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff

=== Other workshops ===
* [http://barcamp.org/SearchCampDC SearchCampDC] - barcamp style event in DC with usual suspects from code4lib
* [[code4lib/elag2010]] - 1-day code4lib preconference at elag2010

== Archived topics ==

* [[Logo Design Process]]

[[AdminToDo]] - ideas and tasks for maintaining the Code4Lib sites

Parsing Library Data

2011-03-31T20:50:28Z

Jthomale: New page: The legacy data that libraries must deal with is often challenging to parse algorithmically. MARC is just the first layer--once you peel that back, you find that you have an elaborate mish...

The legacy data that libraries must deal with is often challenging to parse algorithmically. MARC is just the first layer--once you peel that back, you find that you have an elaborate mish-mash of elements, each of which with its own idiosyncrasies. This page is meant to serve as a place for the Code4lib community to track and share information, problems, methodologies, code, pseudo-code, etc. about nuts-and-bolts parsing of legacy library data.

==Identifiers==

===Library of Congress Control Number===
MARC 21 Field(s): [http://www.loc.gov/marc/bibliographic/bd001.html 001] [http://www.loc.gov/marc/bibliographic/bd003.html 003] [http://www.loc.gov/marc/bibliographic/bd010.html 010]

===OCLC Control Number===
Marc 21 Field(s): [http://www.loc.gov/marc/bibliographic/bd001.html 001] [http://www.loc.gov/marc/bibliographic/bd003.html 003] [http://www.loc.gov/marc/bibliographic/bd035.html 035]

===ISBN===
MARC 21 Field(s): [http://www.loc.gov/marc/bibliographic/bd020.html 020]

* Problems with parsing in MARC
** [http://bibwild.wordpress.com/2011/03/31/why-marc-makes-computers-cry-exhibit-273-issnisbn-z/ Why MARC makes computers cry: Exhibit #273: ISSN/ISBN $z]

===ISSN===
MARC 21 Field(s): [http://www.loc.gov/marc/bibliographic/bd022.html 022]

* Problems with parsing in MARC
** [http://bibwild.wordpress.com/2011/03/31/why-marc-makes-computers-cry-exhibit-273-issnisbn-z/ Why MARC makes computers cry: Exhibit #273: ISSN/ISBN $z]

===Dewey Decimal Call Number===
MARC 21 Field(s): [http://www.loc.gov/marc/bibliographic/bd082.html 082]

===Library of Congress Call Number===
MARC 21 Field(s): [http://www.loc.gov/marc/bibliographic/bd050.html 050]

* Normalization
** [http://code.google.com/p/library-callnumber-lc/wiki/Home library-callnumber-lc Project Wiki Page]
** [http://rocky.uta.edu/doran/sortlc/ sortLC, code for sorting LCCs]

==Personal Names==

MARC 21 Field(s): (Name Headings) [http://www.loc.gov/marc/bibliographic/bd100.html 100] [http://www.loc.gov/marc/bibliographic/bd600.html 600] [http://www.loc.gov/marc/bibliographic/bd700.html 700] [http://www.loc.gov/marc/bibliographic/bd800.html 800]; Also [http://www.loc.gov/marc/bibliographic/bdx00.html X00 - Personal Names-General Information] (Uncontrolled Names) [http://www.loc.gov/marc/bibliographic/bd245.html 245$c] [http://www.loc.gov/marc/bibliographic/bd511.html 505$r] [http://www.loc.gov/marc/bibliographic/bd511.html 511] [http://www.loc.gov/marc/bibliographic/bd720.html 720]

* Parsing name parts
** [http://journal.code4lib.org/articles/2138 Automated Metadata Formatting for Cornell’s Print-on-Demand Books]
* Identifying the name of a person that played a particular role
** [http://journal.code4lib.org/articles/775 Identifying FRBR Work-Level Data in MARC Bibliographic Records for Manifestations of Moving Images]

==Corporate Names==
MARC 21 Field(s): [http://www.loc.gov/marc/bibliographic/bd110.html 110] [http://www.loc.gov/marc/bibliographic/bd610.html 610] [http://www.loc.gov/marc/bibliographic/bd710.html 710] [http://www.loc.gov/marc/bibliographic/bd810.html 810]; Also [http://www.loc.gov/marc/bibliographic/bdx10.html X10 - Corporate Names-General Information]

* Distinguishing corporate names from personal names
** [http://journal.code4lib.org/articles/2138 Automated Metadata Formatting for Cornell’s Print-on-Demand Books]

==Titles==

MARC 21 Field(s): (Transcribed Titles) [http://www.loc.gov/marc/bibliographic/bd245.html 245] [http://www.loc.gov/marc/bibliographic/bd505.html 505$t] (Alternate Titles) [http://www.loc.gov/marc/bibliographic/bd210.html 210] [http://www.loc.gov/marc/bibliographic/bd222.html 222] [http://www.loc.gov/marc/bibliographic/bd242.html 242] [http://www.loc.gov/marc/bibliographic/bd246.html 246] [http://www.loc.gov/marc/bibliographic/bd247.html 247] (Uniform Titles) [http://www.loc.gov/marc/bibliographic/bd130.html 130] [http://www.loc.gov/marc/bibliographic/bd240.html 240] [http://www.loc.gov/marc/bibliographic/bd243.html 243] [http://www.loc.gov/marc/bibliographic/bd630.html 630] [http://www.loc.gov/marc/bibliographic/bd730.html 730] [http://www.loc.gov/marc/bibliographic/bd830.html 830]; Also [http://www.loc.gov/marc/bibliographic/bdx30.html X30 - Uniform Titles-General Information]

* Normalization
** [http://journal.code4lib.org/articles/1758 Deciphering Journal Abbreviations with JAbbr]
** [http://journal.code4lib.org/articles/3832 Interpreting MARC: Where's the Bibliographic Data?]
* Matching techniques
** [http://journal.code4lib.org/articles/1758 Deciphering Journal Abbreviations with JAbbr]

==Subject Headings==
MARC 21 Field(s): [http://www.loc.gov/marc/bibliographic/bd600.html 600] [http://www.loc.gov/marc/bibliographic/bd610.html 610] [http://www.loc.gov/marc/bibliographic/bd611.html 611] [http://www.loc.gov/marc/bibliographic/bd630.html 630] [http://www.loc.gov/marc/bibliographic/bd648.html 648] [http://www.loc.gov/marc/bibliographic/bd650.html 650] [http://www.loc.gov/marc/bibliographic/bd651.html 651] [http://www.loc.gov/marc/bibliographic/bd653.html 653] [http://www.loc.gov/marc/bibliographic/bd654.html 654] [http://www.loc.gov/marc/bibliographic/bd655.html 655] [http://www.loc.gov/marc/bibliographic/bd656.html 656] [http://www.loc.gov/marc/bibliographic/bd657.html 657] [http://www.loc.gov/marc/bibliographic/bd658.html 658] [http://www.loc.gov/marc/bibliographic/bd662.html 662] [http://www.loc.gov/marc/bibliographic/bd69x.html 690-699]