https://wiki.code4lib.org/api.php?action=feedcontributions&user=Egh&feedformat=atomCode4Lib - User contributions [en]2024-03-29T13:31:31ZUser contributionsMediaWiki 1.26.2https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&diff=420102015 Prepared Talk Proposals2014-11-07T22:23:14Z<p>Egh: add rich citations talk</p>
<hr />
<div>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/. <br />
The conference will be held at the Portland Hilton & Executive Tower in Portland, Oregon, from February 9-12, 2015.<br />
<br />
'''Proposals for Prepared Talks:'''<br />
<br />
We encourage everyone to propose a talk.<br />
<br />
Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:<br />
* Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software<br />
* Tools and technologies – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)<br />
* Technical issues - Big issues in library technology that should be addressed or better understood<br />
* 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.<br />
<br />
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.<br />
<br />
'''Proposals for Prepared Talks:'''<br />
<br />
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.<br />
Provide a title and brief (500 words or fewer) description of your proposed talk.<br />
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.<br />
<br />
Please follow the formatting guidelines:<br />
<br />
<pre><br />
<br />
== Talk Title: ==<br />
<br />
* Speaker's name, email address, and (optional) affiliation<br />
* Second speaker's name, email address, and affiliation, if second speaker<br />
<br />
Abstract of no more than 500 words.<br />
<br />
</pre><br />
<br />
'''Talk Proposals'''<br />
== Zines + Gamification = Awesomest Metadata Literacy Outreach Event Ever! ==<br />
<br />
* [http://www.JenniferHecker.info Jennifer Hecker], jenniferraehecker@gmail.com, [http://www.lib.utexas.edu/subject/zines University of Texas Libraries] & [http://www.AustinFanzineProject.org Austin Fanzine Project]<br />
* [http://anomalily.net/ Lillian Karabaic], librarian@iprc.org, [http://www.iprc.org/ Independent Publishing Resource Center] (Portland)<br />
<br />
In academic libraries, and elsewhere, the popularity of zine (a magazine produced for love, not profit) collections is on the rise. At the same time, metadata literacy is becoming an increasingly important skill, helping people navigate and understand digital environments and interactions. We have found a way to teach metadata literacy to the general public that isn’t super-boring – in fact, we’ve made it downright fun!<br />
<br />
First, volunteer zine librarian Lillian Karabaic of Portland’s Independent Publishing Resource Center facilitated the creation of a gamified cataloging interface for the IPRC’s annual Raiders of the Lost Archives backlog-busting 24-hour volunteer cataloging event.<br />
<br />
Then, archivist Jennifer Hecker facilitated the adaptation of the IPRC’s game for use in a similar, but also very different context – promoting UT Libraries newly-acquired zine collections. The main goal of the academic-library-based event was increasing excitement around the collections, but with the side goal of building metadata literacy, and introducing an understanding of library cataloging issues.<br />
<br />
The Texas modification also conforms to the xZINECOREx metadata schema developed by the national [http://zinelibraries.info/ Zine Librarians Interest Group], and triggered interesting conversations with the Libraries’s cataloging department about evolving metadata standards and how to incorporate the products of crowd-sourcing projects into existing workflows.<br />
<br />
Both games will be demoed.<br />
<br />
We have never presented at Code4lib.<br />
<br />
== Do the Semantic FRBRoo ==<br />
* Rosie Le Faive, rlefaive@upei.ca, University of Prince Edward Island<br />
<br />
[http://www.islandora.ca Islandora] is great for creating repositories of any data type, but how can you model meaningful relationships between digital objects and use them to tell a story?<br />
<br />
At UPEI, I’m assembling an ethnography of Prince Edward Island’s traditional fiddle music that includes musical clips, video clips, oral histories, musical notation, images, and ethnographic commentaries. In order to present an exhibition-style site, I’m tying these digital objects together via the people, places, events, tunes and topics that they share or describe. <br />
<br />
To describe the relationships, I’m extending Islandora to use [http://www.cidoc-crm.org/frbr_inro.html FRBRoo], a vocabulary that combines the FRBR model with CIDOC-CRM, the the object-oriented museum documentation ontology. These modules being developed will allow other researchers to create a structured, navigable digital repository of diverse object types, that uses Islandora as an exhibition platform. <br />
<br />
== Our $50,000 Problem: Why Library School? ==<br />
* Jennie Rose Halperin, jhalperin@mozilla.com, Mozilla Corporation<br />
<br />
57 library schools in the United States are churning out approximately 100 graduates per year, many with debt upwards of $50,000. According to ONet, [http://www.inthelibrarywiththeleadpipe.org/2011/is-the-united-states-training-too-many-librarians-or-too-few-part-1/ 84% of library jobs in the US require an MLS.] The library profession is [http://dpeaflcio.org/programs-publications/issue-fact-sheets/library-workers-facts-figures/) 92% white and 82% female and entry-level librarians can expect to make $32,500 per year.]<br />
<br />
Contrasted with developers, who are almost [http://www.ncwit.org/blog/did-you-know-demographics-technical-women 90% male] and can expect to make [http://www.forbes.com/sites/jennagoudreau/2011/06/01/best-entry-level-jobs/ $70,000 in an entry-level position,] these numbers are dismal.<br />
<br />
According to a recent survey, the top skill that outgoing library students want to know is “programming” and yet many MLS programs still consider Microsoft Word an essential technology skill.<br />
<br />
What is going on here? Why do we accept this fate, where mostly female debt-burdened professionals continue to be thrown onto the work force without the education their expensive degrees promised?<br />
<br />
As a community we need to come together to stop this cycle. We need to provide better support and mentorship to diversify and keep the profession relevant and help librarianship move into the future it deserves.<br />
<br />
This talk will walk through the challenges of navigating a hostile employment environment as well as present models for better development and future state imagining.<br />
<br />
== No cataloging software? Need more than Dublin Core? No problem!: Experiences with CollectiveAccess ==<br />
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University<br />
* Rachel Wittmann, rwittma@clemson.edu, Clemson University<br />
<br />
Clemson University Libraries has implemented the open-source software CollectiveAccess for customized digital collection needs. CollectiveAccess is an open-source project with the goal of providing a flexible way to manage and publish museum and archival collections. There are several applications associated with the projects; most used are: Providence (for cataloging and entering metadata) and Pawtucket (for displaying objects in a collection for the public). It has many profiles readily available for installing with existing library standards, such as Dublin Core, and there is a robust syntax for creating your own profiles to fit custom tailored metadata schemas. Plus, the user interface allows you to modify the metadata profile quickly and easily.<br />
<br />
In this talk, we will discuss:<br />
* Our experiences with installing Providence and creating an installation profile that satisfies the needs of many of the Clemson Libraries digital archiving processes. <br />
* The stumbling blocks experienced in that process and how they were resolved.<br />
* The available plugins sourcing widely used authorities, such as Library of Congress thesauri and GeoNames.org, and how they have been used by our projects. <br />
* A brief overview of the export and import functions and also current workflow practices within Providence.<br />
* Future plans & the role of CollectiveAccess at Clemson University Libraries<br />
<br />
== Getting ContentDM and Wordpress to Play Together ==<br />
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University<br />
<br />
Clemson University Libraries has a very strong program for digitizing and archiving photographs, and the Digital Imaging team processes many hundreds of photographs every month. These images are managed using different methods, including ContentDM, a digital collection manager.<br />
<br />
ContentDM provides various methods for searching and displaying photographs, along with their metadata. However, recent initiatives have resulted in the need to leverage those collections into exhibits displayed on other library-related websites, such as our Special Collections unit. The Clemson Libraries has invested heavily in Wordpress as our content management system of choice, and it seemed most efficient not to have to export and import images into our Wordpress sites in order to provide exhibited images.<br />
<br />
Fortunately, ContentDM has provided an API to many of their functions, allowing the extraction of metadata and even rescaled images through URLs. This project has been developing a plugin for Wordpress that integrates with ContentDM through shortcodes that Wordpress editors can easily include in their content. These shortcodes allow editors to choose how many images, which images from which collections, thumbnail sizes, etc. to display in different gallery styles. Plans are for it to allow integration with different plugins such as Fancybox and Masonry.<br />
<br />
In this presentation, I will demonstrate the current state of the plugin and discuss future plans. <br />
<br />
==Refinery — An open source locally deployable web platform for the analysis of large document collections==<br />
<br />
* [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com<br />
<br />
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.<br />
<br />
For more info check out http://www.docrefinery.org.<br />
<br />
==Drupal 8 — Evolution & Revolution==<br />
<br />
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com<br />
<br />
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.<br />
<br />
From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.<br />
<br />
==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==<br />
<br />
* [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]], stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]<br />
<br />
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].<br />
<br />
==The Impossible Search: Pulling data from multiple unknown sources==<br />
<br />
* Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com <br />
<br />
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.<br />
<br />
==What! You're Not Using Docker?==<br />
<br />
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com<br />
<br />
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.<br />
<br />
*[1]https://www.docker.com/<br />
<br />
== Video Accessibility, WebVTT, and Timed Text Track Tricks ==<br />
<br />
* Jason Ronallo, jronallo@gmail.com, NCSU Libraries<br />
<br />
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.<br />
<br />
== Categorizing Records with Random Forests ==<br />
<br />
* Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library<br />
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. <br />
<br />
== Data Science in Libraries ==<br />
<br />
* Devon Smith, smithde@oclc.org, OCLC<br />
<br />
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.<br />
<br />
== PDF metadata extraction for academic literature == <br />
<br />
* Kevin Savage, kevin.savage at mendeley.com, Mendeley<br />
* Joyce Stack, joyce.stack at mendeley.com, Mendeley<br />
<br />
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.<br />
<br />
== Giving Users What They Want: Record Grouping in VuFind ==<br />
<br />
* Mark Noble, mark@marmot.org, [//www.marmot.org Marmot Library Network]<br />
<br />
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.<br />
<br />
== Topic Space: a mobile augmented reality recommendation app ==<br />
<br />
* Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign<br />
<br />
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.<br />
<br />
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. <br />
<br />
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.<br />
<br />
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].<br />
<br />
== Leveling Up Your Git Workflow ==<br />
<br />
* Megan Kudzia, moneill@albion.edu, Albion College Library<br />
* Kate Sears, eks11@albion.edu, Albion College Library<br />
<br />
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).<br />
<br />
== Drone Loaning Program: Because Laptops are so last century ==<br />
<br />
* Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries<br />
* Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries<br />
<br />
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.<br />
<br />
== Got Git? Getting More Out of Your GitHub Repositories ==<br />
<br />
* Terry Brady, twb27@georgetown.edu, Georgetown University Library<br />
<br />
This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories. <br />
<br />
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!<br />
<br />
* [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]<br />
* [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]<br />
* [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]<br />
* [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]<br />
* Gists for code sharing<br />
* Private Repositories and Organizational Groups<br />
* Pull Request Conversation Tracking<br />
* Customized Issue management<br />
<br />
== Quick Wins for Every Department in the Library - File Analyzer! ==<br />
<br />
* Terry Brady, twb27@georgetown.edu, Georgetown University Library<br />
<br />
The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.<br />
* Analyzing Marc Records for the Cataloging department<br />
* Transferring ILS invoices for the University Account System for the Acquisitions department <br />
* Delivering patron fines to the Bursar’s office for the Access Service department<br />
* Summarizing student worker timesheet data for the Finance department<br />
* Validating COUNTER compliant reports for the Electronic Resources department<br />
* Generating ingest packages for the Digital Services department<br />
* Validating checksums for the Preservation department<br />
<br />
Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!<br />
<br />
==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==<br />
<br />
* [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor<br />
<br />
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. <br />
<br />
== Building Your Own Federated Search ==<br />
<br />
* Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco<br />
<br />
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.<br />
<br />
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. <br />
<br />
== Indexing Linked Data with LDPath ==<br />
<br />
* Chris Beer, cabeer@stanford.edu, Stanford University Libraries<br />
<br />
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.<br />
<br />
[1] http://marmotta.apache.org/ldpath/language.html<br />
<br />
== Show Me the Money: Integrating an LMS with Payment Providers ==<br />
<br />
* Josh Weisman, Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group<br />
<br />
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.<br />
<br />
== Shibboleth Federated Authentication for Library Applications: ==<br />
<br />
* Scott Fisher, scott.fisher@ucop.edu, California Digital Library<br />
* Ken Weiss, ken.weiss@ucop.edu, California Digital Library<br />
<br />
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.<br />
<br />
==Scientific Data: A Needs Assessment Journey==<br />
<br />
*[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History<br />
<br />
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. <br />
<br />
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. <br />
<br />
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. <br />
<br />
== Feminist Human Computer Interaction (HCI) in Library Software ==<br />
<br />
* Bess Sadler, bess@stanford.edu, Stanford University Libraries<br />
<br />
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. <br />
<br />
[1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.<br />
<br />
[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<br />
<br />
== Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==<br />
<br />
* Audrey Altman, audrey at dp.la, Digital Public Library of America<br />
* Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America<br />
* Mark Breedlove, mb at dp.la, Digital Public Library of America<br />
<br />
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 assurance were largely inadequate. <br />
<br />
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.<br />
<br />
== OS or GTFO: Program or Perish ==<br />
*Tessa Fallon, tessa.fallon@gmail.com<br />
<br />
Description TBD<br />
<br />
== Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==<br />
* Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries<br />
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.<br />
<br />
== REPOX: Metadata Blender ==<br />
<br />
* John Mignault, jmignault@metro.org, Empire State Digital Network<br />
<br />
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, to aggregate disparate metadata feeds and transform them into formats suitable for ingest into DPLA. The Empire State Digital Network, the forthcoming DPLA service hub for NY state, is using it to prepare for our first ingest into DPLA in early 2015. We'll take a look at REPOX and its capabilities and how it can be useful for ingesting and transforming metadata, and also discuss some things we've learned in massaging widely varied metadata feeds.<br />
<br />
== Beyond Open Source ==<br />
<br />
* Jason Casden, jmcasden@ncsu.edu, NCSU Libraries<br />
* Bret Davidson, bddavids@ncsu.edu, NCSU Libraries<br />
<br />
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?<br />
<br />
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.<br />
<br />
[[Category:Code4Lib2015]] <br />
[[Category:Talk Proposals]]<br />
<br />
== Making It Work: Problem Solving Using Open Source at a Small Academic Library ==<br />
<br />
* Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology<br />
* Max King, mking9@iit.edu, Illinois Institute of Technology<br />
<br />
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.<br />
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.<br />
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.<br />
<br />
== Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==<br />
<br />
* Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Pig Kisses Elephant: Building Research Data Services for Web Archives ==<br />
<br />
* Jefferson Bailey, jefferson@archive.org, Internet Archive<br />
* Vinay Goel, vinay@archive.org, Internet Archive<br />
<br />
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.<br />
<br />
== Awesome Pi, LOL! ==<br />
<br />
* Matt Connolly, mconnolly@cornell.edu, Cornell University Library<br />
* Jennifer Colt, jrc88@cornell.edu, Cornell University Library<br />
<br />
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.<br />
<br />
== You Gotta Keep 'em Separated: The Case for "Bento Box" Discovery Interfaces ==<br />
<br />
* Jason Thomale, jason.thomale@unt.edu, University of North Texas Libraries<br />
<br />
I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.<br />
<br />
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.<br />
<br />
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?<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift ==<br />
<br />
* Ashley Blewer!, ashley.blewer@gmail.com<br />
<br />
Checksum technology is used all over the place, from git commits to authenticating Linux packages. It is most commonly used in the digital preservation field to monitor materials in storage for changes that will occur over time or used in the transmission of files during duplication. But do you even checksum, bro? I want this talk to move checksums from a position of mysterious macho jargon to something everyone can understand and want to use. I think a lot of people have heard of checksum but don’t know where to begin when it comes to actually using it at their institution. And cryptography is hella intimidating! This talk will cover what checksums are, how they can be integrated into a library or archival workflow, protecting collections requiring additional levels of security, algorithms used to verify file fixity and how they are different, and other aspects of cryptographic technology. Oh, and please note that all points in this talk will be emphasized or lightly performed through Taylor Swift lyrics. Seriously, this talk will consist of at least 50% Taylor Swift. Can you, like, even?<br />
<br />
== Level Up Your Coding with Code Club (yes, you can talk about it) ==<br />
<br />
* Coral Sheldon-Hess, coral@sheldon-hess.org<br />
<br />
Reading code is a necessary part of becoming a better developer. It gives you more experience and more insight into How Things Are (or Aren't) Done; it builds your intuition about how to solve problems with code; and it increases your confidence that you, too, can tackle whatever technological problems you're facing.<br />
<br />
But you don't have to read code alone! (Which is good. It's really not fun to read code alone.) <br />
<br />
In late 2014, a group of librarians formed two Code Clubs, inspired by [http://bloggytoons.com/code-club/ this talk by Saron] (of Bloggytoons fame). I'd like to tell you about how we've structured our Code Clubs, what has gone well, what we've learned, and what you need to do to form your own Code Club. I'll share a list of the codebases we've looked at, too, to help you get your own Code Club off the ground! <br />
<br />
== The Growth of a Programmer ==<br />
<br />
* [[User:jgo | Joshua Gomez]], Getty Research Institute, jgomez@getty.edu<br />
<br />
Just like other creative endeavors, software developers can experience periods of great productivity or find themselves in a rut. After contemplating the alternating periods in my own career I've noticed several factors that have effected my own professional growth and happiness, including: mentorship, structure, community, teamwork, environment, formal education, etc. Not all of the factors need to be present at all times; but some mixture of them is critical for continued growth. In this talk, I will articulate these factors, discuss how they can effect a developer's career, and how they can be sought out when missing. This talk is aimed at both new developers looking to strike their own path as well as the veterans that lead or mentor them.<br />
<br />
== Developing a Fedora 4.0 Content Model for Disk Images ==<br />
<br />
* Matthew Farrell, matthew.j.farrell@duke.edu, Duke University Libraries<br />
* Alexandra Chassanoff, achass@email.unc.edu, BitCurator Access Project Manager<br />
<br />
As the acquisition of born-digital materials grows, institutions are seeking methods to facilitate easy ingest into their repositories and provide access to disk images and files derived or extracted from disk images. In this session, we describe our development of a Fedora 4.0 Content model for disk images, including acceptable image file formats and the rationale behind those choices. We will also discuss efforts to integrate the disk image content model into the BitCurator Access environment. Unlike generalized, format-agnostic content models which might treat the disk image as a generic bitstream, a content model designed for disk images enables expression of relationships among associated content in the collection such as files extracted from images and other born-digital and digitized material associated with the same creator. It also enables capture of file-system attributes such as file paths, timestamps, whether files are allocated/deleted, etc. Further, a disk image content model suggests further steps repositories can take in order to transform and re-use associated metadata generated during the creation and forensic analysis of the disk image.<br />
<br />
== Data acquisition and publishing tools in R ==<br />
<br />
* Scott Chamberlain, scott@ropensci.org, rOpenSci/UC Berkeley - first-time presenter<br />
<br />
R is an open source programming environment that is widely used among researchers in many fields. R is powerful because it's free, increasingly robust, and facilitates reproducible research, an increasingly sought after goal in academia. Although tools for data manipulation/visualization/analysis are well developed in R, data acquisition and publishing tools are not. rOpenSci is a collaborative effort to create the tools necessary to complete the reproducible research workflow. This presentation discusses the need for these tools, including examples, including interacting with the repositories Mendeley, Dryad, DataONE, and Figshare. In addition, we are building tools for searching scholarly metadata and acuiring full text of open access articles in a standarized way across metadata providers (e.g., Crossref, DataCite, DPLA) and publishers (e.g., PLOS, PeerJ, BMC, Pubmed). Last, we are building out tools for data reading and writing in Ecologial Metadata Language (EML).<br />
<br />
== SPLUNK: Log File Analysis ==<br />
<br />
* Jim LeFager, jlefager@depaul.edu, DePaul University Library<br />
DePaul University Library recently took over monitoring and maintaining of the library EZproxy servers this past year and using Splunk, a machine data analysis tool, we are able to gather information and statistics on our electronic resource usage in addition to monitoring the servers. Splunk is a tool that can collect, analyze, and visualize log files and other machine data in real time and this has allowed for gathering realtime usage statistics for our electronic resources allowing us to filter by multiple facets including IP Range, Group Membership (student, faculty), so that we can see who is accessing our resources and from where. Splunk allows our library to query our data and create rich custom dashboards as well as create alerts that can be triggered when certain conditions are met, such as error codes, which can send an email alert to a group of users. We will be leveraging Splunk to monitor all library web applications going forward. This talk will review setting up Splunk and best practices in using the available features and customizations available including creating queries, alerts, and custom dashboards. <br />
<br />
== Your code does not exist in a vacuum ==<br />
* Becky Yoose, yoosebec at grinnell dot edu, Grinnell College (Done a lightning talk, MC duties, but have not presented a prepared talk)<br />
<br />
“If you have something to say, then say it in code…” - Sebastian Hammer, code4lib 2009<br />
<br />
In its 10 year run, code4lib has covered the spectrum of libtech development, from search to repositories to interfaces. However, during this time there has been little discussion about this one little fact about development - code does not exist in a vacuum. <br />
<br />
Like the comment above, code has something to say. A person’s or organization’s culture and beliefs influences code in all steps of the development cycle. What development method you use, tools, programming languages, licenses - everything is interconnected with and influenced by the philosophies, economics, social structures, and cultural beliefs of the developer and their organization/community.<br />
<br />
This talk will discuss these interconnections and influences when one develops code for libraries, focusing on several development practices (such as “Fail Fast, Fail Often” and Agile) and licensing choices (such as open source) that libtech has either tried to model or incorporate into mainstream libtech practices. It’ll only scratch the surface of the many influences present in libtech development, but it will give folks a starting point to further investigate these connections at their own organizations and as a community as a whole.<br />
<br />
tl;dr - this will be a messy theoretical talk about technology and libraries. No shiny code slides, no live demos. You might come out of this talk feeling uncomfortable. Your code does not exist in a vacuum. Then again, you don’t exist in a vacuum either.<br />
<br />
== The Metadata Hopper: Mapping and Merging Metadata Standards for Simple, User-Friendly Access ==<br />
<br />
* Tracy Seneca, tjseneca@uic.edu, University of Illinois at Chicago<br />
* Esther Verreau: verreau1@uic.edu, University of Illinois at Chicago<br />
<br />
The Chicago Collections Consortium: 15 institutions and growing! 8 distinct EAD standards! At least 3 permutations of MARC, and we lost count of the varieties of custom CONTENTdm image collections. Not to mention the 14,730 unique subject terms, nearly all of which lead our poor end-users to exactly one organization's content. <br />
<br />
All large content aggregation projects have faced this challenge, and there are a few emerging tools to help us wrangle disparate metadata into new contexts. The Metadata Hopper is one such tool. The Metadata Hopper enables archivists to map their local metadata standards to standardized deposit records, and tags those materials using a shared vocabulary, integrating them into a user-friendly portal without disrupting local practices. In last year's Code4Lib lightning talk we described the challenges that the Chicago Collections Consortium faces in creating shared, in-depth access to archival and digital collections about Chicago history and culture across CCC member organizations. This year, thanks to the Andrew W. Mellon Foundation, we have a working Django application to demonstrate. In this talk we'll discuss the design that enables multiple layers of flexibility, from the ability to accept a variety of metadata standards to designing for an open source audience.<br />
<br />
http://chicagocollectionsconsortium.org<br />
<br />
== Programmers are not projects: lessons learned from managing humans ==<br />
<br />
* Erin White, erwhite@vcu.edu, Virginia Commonwealth University - first-time presenter<br />
<br />
Managing projects is one thing, but managing people is another. Whether we’re hired as managers or grow “organically” into management roles, sometimes technical people end up leading technical teams (gasp!). I’ll talk about lessons I’ve learned about hiring, retaining, and working long-term and day-to-day with highly tech-competent humans. I’ll also talk about navigating the politics of libraryland, juggling different types of projects, and working with constrained budgets to make good things and keep talented people engaged.<br />
<br />
== Practical Strategies for Picking Low-Hanging Fruits to Improve Your Library's Web Usability and UX ==<br />
<br />
* Bohyun Kim, bkim@hshsl.umaryland.edu, University of Maryland, Baltimore<br />
<br />
Have you ever tried to fix an obvious (to you at least!) problem in Web usability or UX (user experience) only to face strong resistance from the library staff? Are you a strong advocate for making library resources, systems, services, and space as usable as possible, but do you often find yourself struggling to get the point across and/or obtain the crucial buy-in from colleagues and administrators? <br />
<br />
There is no shortage of Web usability and UX guidelines. But applying them to a library and implementing desired changes often involve a long and slow process. To tackle this issue, this talk will focus on how to utilize the 'expert review' process (aka 'heuristic evaluation') as a preliminary or even preparatory step before embarking on more time-and-labor-intensive usability testing and user research. Several examples from simple fixes to more nuanced usability and UX issues in libraries will be discussed to your heart's content. The goal of this talk is to provide practical strategies for picking as many low-hanging fruits as possible to make a real (albeit small) difference to your library's Web usability and UX effectively and efficiently.<br />
<br />
== A Semantic Makeover for CMS Data ==<br />
<br />
* Bill Levay, wjlevay@gmail.com, Linked Jazz Project<br />
<br />
How can we take semi-structured but messy metadata from a repository like CONTENTdm and transform it into rich linked data? Working with metadata from Tulane’s Hogan Jazz Archive Photography Collection, the Linked Jazz Project used Open Refine and Python scripts to tease out proper names, match them with name authority URIs, and specify FOAF relationships between musicians who appear together in photographs. Additional RDF triples were created for any dates associated with the photos, and for those images with place information we employed GeoNames URIs. Historical images and data that were siloed can now interact with other datasets, like Linked Jazz’s rich set of names and personal relationships, and can be visualized [link to come] or otherwise presented on the web in any number of ways. I have not previously presented at a Code4Lib conference.<br />
<br />
== Taking User Experience (UX) to new heights ==<br />
<br />
* Kayne Richens, kayne.richens@deakin.edu.au, Deakin University<br />
<br />
User Experience, or "UX", is for more than just websites. At Deakin University Library we're exploring ways to improve the user experience inside our campus library spaces, by putting new technologies front and centre in the overall experience for our students. How are we doing this? We’re collaborating with the University's IT department and exploring the following Library-changing opportunities:<br />
<br />
- Augmented Reality for Way-finding: We’re tackling that infamous thing that all Libraries can't get right – way-finding. We're enhancing library tour information and way-finding experiences by introducing augmented reality solutions.<br />
<br />
- Heat mapping the library with wi-fi: We’re using our existing wi-fi infrastructure to present "heat maps" of library space utilisation, allowing our users to easily locate the space that best suits their needs, whether it be busy spaces to collaborate, or quiet spaces to study. And by overlaying computer usage and group study room bookings, users can quickly locate the space they need.<br />
<br />
- Video chat library service: We’re piloting video-conferencing facilities in our group study rooms and spaces, connecting users and librarians and other professionals.<br />
<br />
This talk will look at how these different technologies will be brought together to provide improved user experiences, as well some of the evidence and reasons that helped us to identify our needs, so you can too.<br />
<br />
==How to Hack it as a Working Parent: or, Should Your Face be Bathed in the Blue Glow of a Phone at 2 AM?==<br />
<br />
*Margaret Heller, Loyola University Chicago, mheller1@luc.edu<br />
*Christina Salazar, California State University Channel Islands, christina.salazar@csuci.edu<br />
*May Yan, Ryerson University, may.yan@ryerson.ca<br />
<br />
Modern technology has made it easier than ever for parents employed in technical environments to keep up with work at all hours and in all locations. This makes it possible to work a flexible schedule, but also may lead to problems with work/life balance and furthering unreasonable expectations about working hours. Add to that shifting gender roles and limited paid parental leave in the United States and you have potential for burnout and a certainty for anxiety. It raises the additioal question of whether the “always connected” mindset puts up a barrier to some populations who otherwise might be better represented in open source and library technology communities. <br />
<br />
This presentation will address tools that are useful for working parents in technical library positions, and share some lessons learned about using these tools while maintaining a reasonable work/life balance. We will consider a question that Karen Coyle raised back in 1996: <br />
“What if the thousands of hours of graveyard shift amateur hacking wasn't really the best way to get the job done? That would be unthinkable.” <br />
<br />
For those who are able to take an extended parental leave, we will present strategies for minimizing the impact to your career and your employer. For those (particularly in the United States) who are only able to take a short leave will require different strategies. Despite different levels of preparation, all are useful exercises in succession planning and making a stronger workplace and future ability to work a flexible schedule through reviewing workloads, cross-training personnel, hiring contract replacements, and creative divisions of labor. Such preparation makes work better for everyone, kids or no kids or caretakers of any kind.<br />
<br />
==Making your digital objects embeddable around the web==<br />
<br />
* Jessie Keck, jkeck@stanford.edu, Stanford University Libraries<br />
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries<br />
<br />
With more and more content from our digital repositories making their way into our discovery environments we quickly realize that we’re repeatedly re-inventing the wheel when it comes to creating “Viewers” for these digital objects. With various different types of viewers necessary (books, images, audio, video, geospatial data, etc) the burden of getting these viewers into various environments (topic guides, blogs, catalogs, etc) becomes exponential.<br />
<br />
In this talk we’ll discuss how Stanford University Libraries implemented an oEmbed service to create an extensible viewer framework for all of its digital content. Using this service we’ve been able to easily integrate viewers into various discovery applications as well as make it easy for end users who discover our objects to easily embed customized versions into their own websites and blogs.<br />
<br />
==So you want to make your geospatial data discoverable==<br />
<br />
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries<br />
<br />
Finding data for research or coursework can be one of the most time intensive tasks for a scholar or student. We introduce GeoBlacklight, an open source, multi-institutional software project focused on solving these common challenges at institutions across the world. GeoBlacklight prioritizes user experience, integrates with many GIS tools, and streamlines the use and organization of geospatial data. This talk will provide an introduction to the software, demonstrate current functionality, and provide a road map for future work.<br />
<br />
== Clueless-Driven Development: How I learned to migrate to Fedora 4 ==<br />
<br />
* Adam Wead, awead@psu.edu, Penn State University<br />
<br />
Recently I was tasked with migrating the content from our Fedora3 repository to the new Fedora4 repository architecture.<br />
Despite a wealth of community support, I had no idea how to approach, or even begin to solve this problem. I knew I<br />
wanted to follow best practices and use test-driven development to build my solution, but had no idea where to start.<br />
Despite this initial setback, I was able to start writing tests with only a vague understanding of the problem. As my<br />
tests exposed where my understanding of the problem was flawed, my code evolved, and within a week I had arrived at a<br />
working solution that exhibited all the hallmarks of good testing and software design.<br />
<br />
This talk recounts the process I went through from starting with practically nothing, to arriving at a working solution.<br />
You can follow the rules of test-driven development, but you can write tests in an expressive way to describe the<br />
problem instead of just describing what the code should do. It was also essential to begin testing from an integration<br />
viewpoint as opposed to a unit one, because at the outset the units were unknown and were later realized through further<br />
development. For the presentation, I will be demonstrating using RSpec and Ruby. All the code examples will be related<br />
to the Hydra software stack; however, I hope to show that the processes at work will be applicable in any context.<br />
<br />
<br />
== Designing and Leading a Kick A** Tech Team ==<br />
<br />
* Sibyl Schaefer, sschaefer@rockarch.org, Rockefeller Archive Center<br />
<br />
New managers are often promoted without receiving management training, yet management is not something you just figure out. The experience of being expected to know how to manage, yet not being trained to do so often results in new managers feeling isolated and unsure how to move from making to managing. In this talk I’ll focus on my own managerial experience of designing and leading an archival tech team in a small independent archives. Topics covered will include hiring, delegating, creating a team culture, and leading people whose specialized knowledge exceeds your own. The talk take-aways should be applicable to managers and employees at large and small institutions alike.<br />
<br />
<br />
==American (Archives) Horror Story: LTO Failure and Data Loss ==<br />
<br />
* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH<br />
* Casey Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH<br />
<br />
Here’s a story to send shivers down archival spines: when transferring video files off LTO for the American Archive project, WGBH got an initial failure rate of 57%. After repeat tries, the rates improved; still, an unnervingly large percentage of files were never able to be transferred successfully. Even more unnerving, going public with our horror story got a big response from other archives using LTO -- it seems like many institutions are having similarly scary results. What are the real risks with LTO tape? Are there steps that archives should be taking to better circumvent those risks? This presentation will share information about LTO storage failures across archives world and discuss the process of investigating the problem at WGBH by testing different methods of data retrieval from LTO (direct and networked downloads, individual file retrieval and bulk data dump, use of LTO 4 and LTO 6 decks) and using checksum comparisons and file analysis and characterization tools such as ffprobe, mediainfo and exiftool to analyze failed files. We'll also present whatever results we’ve managed to turn up by the time of Code4Lib!<br />
<br />
== PBCore in Action: Three Words, Not Two! ==<br />
<br />
* Casey E. Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH<br />
* Andrew (Drew) Myers, andrew_myers@wgbh.org, Supervising Developer, WGBH<br />
<br />
In 2001, public media representatives developed the PBCore XML schema to establish a common language for managing metadata about their analog and digital audio and video. Since then, PBCore has been adopted by a number of organizations and archivists in the moving image archival community. The schema has also undergone a few revisions, but on more than one occasion it was left orphaned and with little to no support.<br />
<br />
Times have changed. You may have heard the news that PBCore is back in action as part of the American Archive of Public Broadcasting initiative and via the Association of Moving Image Archivists (AMIA) PBCore Advisory Subcommittee. A group of archivists, public media stakeholders, and engaged users have come together to provide necessary, sustaining support for the standard and to see to its further development. <br />
<br />
At this session, we'll discuss the scope and uses of PBCore in digital preservation and access, report on the progress and goals of the PBCore Advisory Subcommittee, and share how the group (by the time of the conference) will have transformed the XML schema into an RDF ontology, bringing PBCore into the second decade of the 21st century. #PBHardcore<br />
<br />
==Collaborating to Avert the Digital Graveyard==<br />
<br />
* Harish Nayak, hnayak@library.rochester.edu, University of Rochester Libraries <br />
* Sean Morris, smorris@library.rochester.edu, University of Rochester Libraries <br />
<br />
In 1995, the Robbins Library at the University of Rochester created a digital collection of Arthurian texts, images, and bibliographies. Together with medieval scholars, we recently completed the redesign and development of an interface for this collection. Using FRBR concepts, we re-conceptualized organization and editing workflow from the ground up in a mobile-first Drupal-based project. <br />
<br />
In this talk we will describe the project as well as how we utilized the techniques of work practice study and user centered design to maintain engagement with reluctant stakeholders, nontechnical scholars, and VERY meticulous graduate students. Neither of us have previously presented at a Code4Lib conference.<br />
<br />
==Docker? VMs? EC2? Yes! With Packer.io==<br />
<br />
* Kevin S. Clarke, ksclarke@gmail.com, Digital Library Programmer, UCLA<br />
<br />
There are a lot of exciting ways to deploy a software stack nowadays. Many of our library systems are fully virtualized. Docker is a compelling alternative, and there are also cloud options like Amazon's EC2. This talk will introduce Packer.io, a tool for creating identical machine images for multiple platforms (e.g., Docker, VMWare, VirtualBox, EC2, GCE, OpenStack, et al.) all from a single source configuration. It works well with Ansible, Chef, Puppet, Salt, and plain old Bash scripts. And, it's designed to be scriptable so that builds can be automated. This presentation will show how easy it is to use Packer.io to bring up a set of related services like Fedora 4, Grinder (for stress testing), and Graphite (for charting metrics). As an added value, all the buzzwords in this proposal will be defined and explained!<br />
<br />
== Technology on your Wrist: Cross-platform Smartwatch Development for Libraries ==<br />
<br />
* [[User:sanderson|Steven Carl Anderson]], sanderson@bpl.org, [http://www.bpl.org Boston Public Library] (no previously accepted prepared talks but have done lightning talks in the past)<br />
<br />
I'll be the first to admit: smartwatches are unlikely to completely revolutionize how a library provides online services. But I believe they still represent an opportunity to further enhance existing library services and resources in a unique way.<br />
<br />
At the Boston Public Library (BPL), we're in the initial phases of designing a modest smartwatch app to provide notifications for circulation availability and checked-out-material due-date alerts by the end of current year. We're starting small, but we plan to evolve the concept over time as we see what (if any) traction such an application gets with potential users. For example, we plan to explore the possibility of adding "nearest branch to my current location" functionality to this app.<br />
<br />
Despite the "development phase" of this application as of this writing, this talk is not being given by a novice. As a technology enthusiast, I've released [http://www.phdgaming.com/smartwatch_projects/ five smartwatch applications] and have had two of those be finalists in a [http://www.phdgaming.com/samsung_challenge/ Samsung sponsored development challenge]. This experience not only will allow for the BPL to avoid many beginner mistakes in its smartwatch app development but also gives a much more complete understanding of the smartwatch development ecosystem.<br />
<br />
This talk will explore the following questions:<br />
<br />
* What kinds of online library services could potentially be transformed or translated into the smartwatch/wearable domain? What kinds of services are better left alone? These questions are currently being explored and I'll talk about our plans and experiences. Included will be any statistical information from our application launch along with statistics from my personal development.<br />
<br />
* How to support all the different operating systems these devices run without painful modifications to your codebase. (There's Tizen that is used by Samsung's Gear 2 and Gear S, Android Wear that is used by most other non-Apple manufacturers, then there is Apple's upcoming smartwatch itself, etc.)<br />
<br />
* How to support different screen resolutions on such a small device. From round to rectangular to perfectly square, smartwatches come in all different shapes these days.<br />
<br />
* What are the app stores like on these platforms? As I support multiple applications through different distribution networks, a guide to navigating how to distribute one's app is included and I'll reveal how these systems work “behind the curtain.”<br />
<br />
* What are common issues and pitfalls to avoid when doing development? Tips on broken APIs and how to cope or optimizing your code will be included.<br />
<br />
==Seeing the Forest From the Trees: The Art of Creating Workflows for Digital Projects ==<br />
<br />
* Jen LaBarbera, j.labarbera@neu.edu, NDSR Resident, Northeastern University<br />
* Joey Heinen, joseph_heinen@harvard.edu, NDSR Resident, Harvard University<br />
* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH<br />
* Tricia Patterson, triciap@mit.edu, NDSR Resident, MIT<br />
<br />
We have to "turn projects into programs" in order to create a solid and sustainable digital preservation initiative...but what the heck does that even mean? What does that look like?<br />
<br />
In this talk, members of the inaugural Boston cohort of the National Digital Stewardship Residency will discuss one piece of our digital preservation test kitchen: our stabs at creating digital workflows that will (hopefully) help our institutions turn digital preservation projects into programs. Specifically, we will talk about how difficult it is to create a general and overarching workflow for digital preservation tasks (e.g. ingest into repositories, format migrations, etc.) that incorporates various technical tools while also taking into account the myriad and unending list of possible exceptions or special scenarios. Turning these complicated, specific processes into a simplified and generalized workflow is an art. We haven't necessarily perfected that art yet, but in this talk, we'll share what has worked for us -- and what hasn't. We’ll also touch on the importance of documentation, and achieving that delicate balance of adequately thorough documentation that doesn’t pose the risk of information avalanche. These processes often create more questions than answers, but we'll share the answers that we (and our mentors) have found along the way!<br />
<br />
== Annotations as Linked Data with Fedora4 and Triannon (a Real Use Case for RDF!) ==<br />
<br />
* Rob Sanderson, azaroth@stanford.edu, Stanford University Libraries<br />
* Naomi Dushay, ndushay@stanford.edu, Stanford University Libraries<br />
<br />
Annotations on content resources allow users to contribute knowledge within the digital repository space. W3C Open Annotation provides a comprehensive model for web annotation on all types of content, using Linked Data as a fundamental framework. Annotation clients generate instances of this model, typically using a JSON serialization, but need to store that data somewhere using a standard interaction pattern so that best of breed clients, servers, and data can be mixed and matched.<br />
<br />
Stanford is using Fedora4 for managing Open Annotations, via a middleware component called Triannon. Triannon receives the JSON data from the annotation client, and uses the Linked Data Platform API implementation in Fedora4 to create, retrieve, update and delete the constituent resources. Triannon could be easily modified to use other LDP implementations, or could be modified to work with linked data other than annotations.<br />
<br />
== Hydras in the Wild: A survey of current projects ==<br />
<br />
* Mark Bussey, mark@curationexperts.com, Data Curation Experts<br />
<br />
You've seen the tutorials, but [https://github.com/projecthydra/hydra/wiki/Dive-into-Hydra Dive Into Hydra] seems to leave something wanting. What can you really do using the Hydra Framework? This talks looks at a number of current Hydra projects and highlights the design and functional features unique to each. Compare and contrast UX, design and functional capabilites from a range of hydra-based repositories including:<br />
* Avalon for media discovery and distribution (Indiana and Northwestern Univiersities) <br />
* HydraDam for media archive management(WGBH)<br />
* HyHull for general Institutional Repository needs (University of Hull)<br />
* T-DIL for slide library functions (Tufts University)<br />
* Sufia & Scholarsphere as a bundled self-deposit IR solution (Pennsylvania State University)<br />
* Curate & Worthwhile as general purpose repository platforms (Multiple Insititutions)<br />
This will be a whirlwind tour aimed at providing ideas and inspiration for your own repository development project.<br />
<br />
== Hydra Makeovers! ==<br />
<br />
* Alicia Cozine, alicia@curationexperts.com, Data Curation Experts<br />
* Patrick Feeley, pgf8@case.edu, Case Western Reserve University<br />
<br />
Compare two Hydra-based applications with the systems they replaced. Marvel at the Before and After snapshots of functionality, speed, and look & feel. <br />
* '''Digital Case 2.0''' is an institutional repository, complete with administrative tools, derivatives transcoding, flexible XML metadata storage, embargo and lease capability, faceted searching, and content viewers for texts/TEI, images, audio recordings, and videos. Digital Case 2.0 is based on worthwhile, an open-source IR starter gem. <br />
* '''The Tufts Digital Image Library''' is a specialized tool for art and art history resources, offering image collections with user access controls, image ordering, collection nesting, drag-and-drop organization, slideshows, and export capability. <br />
Both new systems are built on hydra, the open-source Ruby-on-Rails repository solution that incorporates Fedora for storage, Solr for indexing, and Blacklight for search optimization. Their beauty is not just skin-deep!<br />
<br />
<br />
<br />
== Helping Google (and scholars, researchers, educators, & the public) find archival audio ==<br />
<br />
* Anne Wootton, anne@popuparchive.org, Pop Up Archive (www.popuparchive.org)<br />
<br />
Culturally significant digital audio collections are hard to discover on the web. There are major barriers keeping this valuable media from scholars, researchers, and the general public:<br />
<br />
Audio is opaque: you can’t picture sound, or skim the words in a recording. <br />
Audio is hard to share: there’s no text to interact with. <br />
Audio is not text: but since text is the medium of the web, there’s no path for audiences to find content-rich audio.<br />
Audio metadata is inconsistent and incomplete.<br />
<br />
At Pop Up Archive, we're helping solve this problem making the spoken word searchable. We began as a UC-Berkeley School of Information Master's thesis to provide better access to recorded sound for audio producers, journalists, and historians. Today, Pop Up Archive processes thousands of hours of sound from all over the web to create automatic, timestamped transcripts and keywords, working with media companies and institutions like NPR, KQED, HuffPost Live, Princeton, and Stanford. We're building collections of sound from journalists, media organizations, and oral history archives from around the world. Pop Up Archive is supported by the John S. and James L. Knight Foundation, the National Endowment for the Humanities, and 500 Startups.<br />
<br />
== Digital Content Integrated with ILS Data for User Discovery: Lessons Learned ==<br />
<br />
* Naomi Dushay, ndushay@stanford.edu, Stanford University Libraries<br />
* Laney McGlohon, laneymcg@stanford.edu, Stanford University Libraries (first-time presenter)<br />
<br />
So you want to expose your digital content in your discovery interface, integrated with the data from your ILS? How do you make the best information user searchable? How do you present complete, up to date search results with a minimum of duplicate entries?<br />
<br />
At Stanford, we have these cases and more:<br />
* digital content with no metadata in ILS<br />
* digital content for metadata in ILS<br />
* digital content with its own metadata derived from ILS metadata.<br />
<br />
We will describe our efforts to accommodate multiple updatable metadata sources for materials in the ILS and our Digital Object Repository while presenting users with reduced duplication in SearchWorks. Included will be some failures, some successes, and an honest assessment of where we are now.<br />
<br />
== Show All the Things: Kanban for Libraries == <br />
<br />
* Mike Hagedon, mhagedon@email.arizona.edu, University of Arizona Libraries (first-time presenter)<br />
<br />
The web developers at the University of Arizona Libraries had a problem: we were working on a major website rebuild project with no clear way to prioritize it against our other work. We knew we wanted to follow Agile principles and initially chose Scrum to organize and communicate about our work. But we found that certain core pieces of Scrum did not work for our team. Then we discovered Kanban, an Agile meta-process for organizing work (team or individual) that treats the work more as a flow than as a series of fixed time boxes. I’ll be talking about our journey toward finding a process that works for our team and how we’ve applied the principles of Kanban to better get our work done. Specifically, I'll discuss principles like how to visualize all your work, how to limit how much you’re doing (to get more done!), and how to optimize the flow of your work.<br />
<br />
== DIY Catalog ==<br />
<br />
* Wayne Schneider, wschneider at [//www.hclib.org hclib.org], [//www.hclib.org Hennepin County Library]<br />
* Amy Drayer, adrayer at [//www.hclib.org hclib.org], [//www.hclib.org Hennepin County Library]<br />
<br />
With so many discovery layers being made available that didn’t quite fit user needs but still came with substantial costs, Hennepin County Library determined it would develop one that could handle its customizations. So they built their own ILS API, Web services, and an interface that provides all the features (and existing custom features) of the old catalog, with new features planned, all within a responsive layout. Get a look at the system architecture, how the front end communicates through the layers back to the databases, and how to manage the infrastructure.<br />
<br />
== OverDrive: Full Integration ==<br />
<br />
* Amy Drayer, adrayer at [//www.hclib.org hclib.org], [//www.hclib.org Hennepin County Library]<br />
* Wayne Schneider, wschneider at [//www.hclib.org hclib.org], [//www.hclib.org Hennepin County Library]<br />
<br />
How do you increase usage of your ebooks? Seamless integration in the catalog certainly helps. Users can search for digital titles, limit to just those that are available, place a request, borrow, and manage all their digital titles from the library website alongside all the other physical titles the library has. Get a quick demo and learn how this was all made possible.<br />
<br />
The [//www.hclib.org Hennepin County Library] is ranked one of [//www.thedigitalshift.com/2014/10/ebooks/overdrive-api-usage-indicates-growth-ebook-checkouts-via-opac/ the top users of OverDrive and OverDrive’s API] and is looking to more fully integrate 3M Cloud, OneClickDigital, and other digital resources.<br />
<br />
== Dynamic Indexing: a Tragic Solr Story ==<br />
<br />
* Wayne Schneider, wschneider at [//www.hclib.org hclib.org], [//www.hclib.org Hennepin County Library]<br />
<br />
Loading data from an ILS into Solr isn’t so hard, unless it needs to be dynamic, fast, and hold more data than what can be found in 1.5 million MARC records. Some additional information we’ve incorporated are from Syndetics, ILS circulation, and OverDrive. We’ll share the nitty gritty details and what we learned about dynamic Solr indexing, including how to get good performance, how to deal with indexing failures, how to schedule it all to keep the data up-to-date, and some things you can do with that data such as popularity ratings.<br />
<br />
== Fedora 4, Survey of Core Capabilities and External Modules: == <br />
* Andrew Woods, awoods@duraspace.org, DuraSpace<br />
<br />
Now that the production release of Fedora 4.0 is out, the time is right to take a step back and review the core capabilities offered by Fedora:<br />
* Basic CRUD<br />
* Versioning<br />
*- Transactions<br />
* etc<br />
<br />
...and take a closer look at the supported external modules:<br />
* Authorization<br />
* Solr integration<br />
* Triplestore integration<br />
* Camel integration<br />
* etc<br />
<br />
In addition to clarifying specific implementation details, this is an opportunity to surface community requirements which may have not been addressed in the initial release.<br />
<br />
== Bleeding edge beacons: redesign of a library tour with new technology ==<br />
<br />
* Neal Henshaw, Virginia Tech <br />
* Somiah Lattimore, Straight Up Creative<br />
* Keith Gilbertson, keith.gilbertson@vt.edu, Virginia Tech<br />
<br />
This group has not yet presented at Code4Lib<br />
<br />
A technology liaison, a designer, and a developer are working together to update a mobile audio tour of an academic library.<br />
<br />
The walking tour was originally conceived of and created by the technology liaison to provide an orientation experience for incoming students. In its current version, patrons visit several stations in the library and activate an audio description of each station by scanning a QR barcode with a mobile device.<br />
<br />
We are building a prototype to test with focus groups so that we can launch a new version of the tour in early 2015. The tour has been reimagined with a professional and communicative user interface that presents students with learning goals for each location in the library. The new version of the tour is a mobile application with integrated support for micro-location technology provided through Bluetooth low energy beacon devices, known informally as iBeacons, installed throughout the building. As a touring student walks through the library, her location is noted by the app so that an appropriate video segment is automatically played according to the current location.<br />
<br />
We will discuss perspectives on the design of the project, including<br />
<br />
* Designing with technology to achieve learning goals<br />
* Designing graphical elements, interaction, and user experience<br />
* Designing to maintain compatibility with older technologies<br />
<br />
We’ll explain our efforts to make the application usable by those with hearing impairments and mobility impairments, reactions from our first users, and challenges in working with the relatively new beacon technology.<br />
<br />
== Distributed Remediation: Small tools for big problems: ==<br />
<br />
* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs<br />
<br />
Remediation of legacy data can be automated only so much. Certain essential cleanup tasks, such as aligning a name with the correct authorized version, is very difficult for a computer yet trivial for a person. While it is these types remediations that will allow an institution to take advantage and participate in the web of Linked Open Data, a wholly manual approach is unrealistic. However, by augmenting automated remediation with a light human touch we can quickly and efficiently reach our goals. This talk will look at tools and methods being developed at NYPL Labs to empower library staff and the public to help clean up our legacy metadata through collaborative remediation.<br />
<br />
==VuFind + WorldCat: Open Source Discovery Meets Big Library Data==<br />
<br />
* Karen A. Coombs, coombsk@oclc.org, OCLC<br />
* Demian Katz, demian.katz@villanova.edu, Villanova University<br />
<br />
Good collaboration is crucial to any integration. Our project, to integrate the open source discovery tool, VuFind, with results from the new WorldCat Discovery API, is no different. We want to exploit the flexibility of VuFind and add the depth and breadth of WorldCat and central index content. Plus, the project has the potential to eliminate the hurdle of exporting and indexing MARC records for 32 VuFind libraries.<br />
<br />
While we are really excited about the UI enhancements, we are also curious to see how we can share our domain expertise between our two organizations to get the project done quickly. How will different perspectives shape our existing code bases? How will we adjust to working on the same code base simultaneously? And how can we best incorporate what we learn along the way?<br />
<br />
There is also new territory to explore using the API: integrating bibliographic and article data into a single results set. And the overarching question: will we be able to take advantage of Linked Data in the WorldCat Discovery API to create some “glue” between records in existing VuFind indexes and third-party data providers?<br />
<br />
This presentation will discuss our adventures in the OCLC WorldShare Platform/VuFind collaboration: the opportunities, challenges and results. You’ll learn what worked, what didn’t and how you can improve your own discovery interface integration project—no matter what provider or APIs you use.<br />
<br />
== Book Reader Bingo: Which Page-Turner Should I Use? ==<br />
<br />
* Eben English, eenglish [at] bpl.org, Boston Public Library<br />
<br />
Another day, another library reinventing the book-viewer wheel. When will the madness end? This talk will explore the current landscape of book-viewer/page-turner applications for digital library systems with an eye towards helping you make the right decision for your project. We'll look at some the major players on the market (such as Internet Archive BookReader, Wellcome Player, Mirador, and WDL-Viewer to name a few) and compare them based on a number of criteria: feature sets, mobile/tablet friendliness, ease of integration, code health, test coverage, "market share" (number of implementers), and other important factors. We'll look at the results of ACTUAL USABILITY TESTS to see what features users REALLY want in a book-viewer, and how each app measures up. <br />
<br />
We'll also discuss important recent trends (such as the IIIF Presentation API, ReadersFirst, and NYPL's Library Simplified initiative) that have the potential to shape the book-viewer development landscape in the immediate future. Which page-turner applications are best poised to adopt/integrate/leverage these emerging standards? Which will become obsolete? This talk has the answers you need.<br />
<br />
== Rich Citations ==<br />
<br />
* Adam Becker, abecker@plos.org, Public Library of Science<br />
* Erik Hetzner, ehetzner@plos.org, Public Library of Science<br />
<br />
Citations should connect you to the research you need. They should<br />
link directly to the relevant papers and data. They should tell you<br />
everything you need to know about how and where two pieces of research<br />
are connected. They should be easy to use and they should never get in<br />
the way of the reading experience. In short, citations should not<br />
clumsily point to a mere chunk of plain undifferentiated text sitting<br />
in a static list at the end of the paper. But with almost no<br />
exceptions, citations in scientific papers do just that.<br />
<br />
PLOS Labs has been working on a project to capture extra information<br />
about citations. To this end, we have designed a metadata structure<br />
describing the context of a paper's citations, called rich citations.<br />
This structured information includes complete bibliographic<br />
information for the cited items, location and context of the in-text<br />
citation, co-citations, reference license and status (updated,<br />
retracted, etc.), and more.<br />
<br />
We have processed the complete PLOS corpus to extract this rich<br />
citation metadata, and made this data available in an API located at<br />
http://api.richcitations.org/.<br />
<br />
We have also developed a JavaScript overlay to enhance a paper's view<br />
using rich citations (http://alpha.richcitations.org). This overlay<br />
uses the underlying rich citation metadata to allow the user to view<br />
information about an in-text citation, quickly navigate between<br />
citations, and sort and filter the paper's reference list.<br />
<br />
In this talk, we will describe the rich citation metadata that we are<br />
capturing. We will demonstrate how this metadata can enhance a<br />
reader's experience of an article and how it can be used by<br />
researchers to better understand how citations are used in the<br />
scientific community. We will also discuss our ongoing plans to extend<br />
this project to the wider literature beyond PLOS, and how interested<br />
members of the community can help.</div>Eghhttps://wiki.code4lib.org/index.php?title=2013_preconference_proposals&diff=311222013 preconference proposals2013-01-10T05:47:23Z<p>Egh: /* Solr 4 In Depth */</p>
<hr />
<div>Proposals '''now closed'''.<br />
<br />
Spaces available: 4+ Rooms<br />
<br />
Please follow the formatting guidelines:<br />
<pre><br />
=== Talk Title ===<br />
<br />
* Presenter/Leader, affiliation (optional), and email address (mandatory!)<br />
* Second Presenter/Leader, affiliation, email address, if applicable<br />
<br />
Description.<br />
</pre><br />
<br />
==Full Day==<br />
<br />
===Drupal4lib Sub-con Barcamp===<br />
<br />
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or <br />
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu<br />
<br />
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.<br />
<br />
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.<br />
<br />
Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.<br />
<br />
====I plan on attending:====<br />
<br />
=====All Day=====<br />
*Margaret Heller<br />
*Mahria Lebow, mahria at uw edu<br />
*Paula Gray-Overtoom, pgrayove at gmail.com<br />
<br />
=====Morning=====<br />
* [[User:Kevenj|Keven Jeffery]]<br />
* Sean Chen<br />
<br />
=====Afternoon=====<br />
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)<br />
* Christina Salazar (afternoon only)<br />
* Sarah Dooley (afternoon)<br />
* Josh Wilson, joshwilsonnc at gmail (likely afternoon only)<br />
* Ken Varnum, varnum at umich e-d-u<br />
* Cody Hennesy, chennesy at library berkeley edu<br />
<br />
==Half Day Morning==<br />
=== Open space session ===<br />
<br />
* Dan Chudnov, dchud at gwu edu<br />
<br />
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.<br />
<br />
If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.<br />
<br />
'''I plan on attending:'''<br />
* Devon Smith<br />
* Esmé Cowles, escowles@ucsd.edu<br />
* Jason Casden<br />
* Ryan Eby<br />
* mark matienzo<br />
* Donald Mennerich<br />
* Patrick Berry, pberry@csuchico.edu<br />
<br />
=== Delivery services ===<br />
* Ted Lawless, Brown University Library, tlawless at brown edu. <br />
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.<br />
<br />
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. <br />
<br />
Possible topics/activities include:<br />
* group discussion of what some libraries have done in this area<br />
* comparisons of different approaches to addressing delivery <br />
* overview of tools available <br />
* sharing of strategies and experiences<br />
* 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]. <br />
<br />
Resources and background information:<br />
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway] <br />
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]<br />
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]<br />
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]<br />
<br />
'''I plan on attending:'''<br />
* Ken Varnum, varnum at umich e-d-u<br />
* Ayla Stein<br />
* Curtis Thacker<br />
* Rosalyn Metz rosalynmetz at gmail com<br />
* James Van Mil - james.vanmil at gmail com<br />
* Andrew Nagy<br />
* Ranti Junus<br />
* Aaron Collier - acollier at csufresno edu<br />
<br />
=== Intro to Blacklight CANCELLED ===<br />
<br />
PLEASE NOTE: This pre-conference has been cancelled in favor of joining forces with the RailsBridge workshop. The afternoon Blacklight session will still be offered.<br />
<br />
=== RailsBridge Intro to Ruby on Rails ===<br />
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu<br />
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br />
* Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu<br />
* Ross Singer, Talis, rossfsinger@gmail.com<br />
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org<br />
* Bess Sadler, Stanford University, bess@stanford.edu<br />
* Anyone else want to come and help folks? Contact Jason.<br />
<br />
RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language, the Rails framework, and version control with git. Participants will build a working Rails application. <br />
<br />
There will be some pre-preconference preparation needed so that we can effectively use our time. Details to come.<br />
<br />
* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby<br />
<br />
Please add your name below and fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dEpxd0tzU1ZscnU5QUUtd0JGUk9qQkE6MA#gid=0 experience survey].<br />
<br />
'''I plan on attending:'''<br />
# First and last name and email address<br />
# John MacGillivray<br />
# Jon Stroop - jstroop at princeton<br />
# Christina Salazar - christina{dot}salazar{at}csuci{dot}edu<br />
# Karen Coombs - coombsk{at}oclc{dot}org<br />
# Becky Yoose - b dot yoose at google overlord<br />
# Jeremy Morse - jgmorse at umich<br />
# Julia Bauder - julia{dot}bauder{at}gmail{dot}com <br />
# Chung Kang<br />
# Karen Miller - k-miller3{at}northwestern{dot}edu<br />
# Betsy Coles - bcoles{at}caltech{dot}edu<br />
# Jay Luker - jay{dot}luker{at}gmail{dot}com<br />
# Santi Thompson<br />
# Sarah Dooley - sarah{at}nclive{dot}org<br />
# Brandon Dudley<br />
# Ken Irwin<br />
# Dennis Ogg - ogg{at}ucar{dot}edu<br />
# Ian Walls - iwalls{at}library{dot}umass{dot}edu<br />
# Steven Villereal – villereal{at}gmail{dot}com<br />
# Hillel Arnold - hillel{dot}arnold{at}gmail{dot}com<br />
# Josh Wilson - joshwilsonnc at gmail<br />
# Cynthia Ng - cynthia [dot] s [dot] ng [at] gmail<br />
# Ian Chan<br />
# Heidi Frank - hf36{at}nyu{dot}edu<br />
# Mark Mounts<br />
# Bill McMillin - wmcmilli{at}pratt {dot}edu<br />
# David Lacy - david dot lacy at villanova dot edu<br />
# Courtney Greene - crgreene at indiana dot edu<br />
# Laney McGlohon - lmcglohon@getty.edu<br />
# Nancy Enneking - nenneking@getty.edu<br />
# Jason Raitz - jcraitz at ncsu dot edu<br />
# Nick Cappadona<br />
# Steven Marsden - steven.marsden@ryerson.ca<br />
# Linda Ballinger - ballingerl at newberry dot org<br />
# Brendan Quinn - brendan-quinn at northwestern dot edu<br />
# Michael Levy - mlevy {at}ushmm {dot}org<br />
# Michael North (m-north at northwestern dot edu)<br />
# Shawn Averkamp - shawnaverkamp{at}gmail{dot}com<br />
# Tim Thompson - t.thompson5{at}miami{dot}edu<br />
# Allan Berry - allan{dot}berry{at}gmail{dot}com<br />
# Andrew Darby - agdarby at miami dot edu<br />
# Cody Hennesy - chennesy at library dot berkeley dot edu<br />
# Devin Higgins - higgi135 at msu dot edu<br />
# Emily Zervas - emily{dot}zervas{at}gmail{dot}com<br />
# Rob Dumas - rdumas {at} chipublib {dot} org<br />
<br />
===Intro to NoSQL Databases===<br />
* Joshua Gomez, George Washington University, jngomez at gwu edu<br />
<br />
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, CouchDB, and Neo4j.<br />
<br />
'''I plan on attending:'''<br />
* Esha Datta<br />
* Trevor Thornton<br />
* Michael Doran<br />
* Ray Schwartz - schwartzr2@wpunj.edu<br />
* Kevin Clarke<br />
* Andreas Orphanides<br />
* Tommy Ingulfsen - tommying{at}caltech{dot}edu<br />
* Harrison Dekker<br />
* Eric James eric dot james at yale dot edu<br />
* Sean Crowe - sean.crowe@uc.edu<br />
* Scott Hanrath<br />
* Erin Fahy - erin.fahy at mtholyoke edu<br />
* Karen Coyle - kcoyle at kcoyle.net<br />
* Charles Draper<br />
* David Uspal<br />
* Shawn Kiewel - smkiewel at uga dot edu<br />
* Stephanie Collett - stephanie dot collett at ucop dot edu<br />
* Declan Fleming - declan at declan dot net<br />
* David Gonzalez - d.gonzalez26 at umiami dot edu<br />
* Jeff Peterson - gpeterso at umn dot edu<br />
* May Chan - msuicat at gmail dot com<br />
* Kathryn Stine - kathryn dot stine at ucop dot edu<br />
<br />
==Half Day Afternoon==<br />
=== Data Visualization Hackfest ===<br />
* Chris Beer, cabeer at stanford.edu<br />
* Dan Chudnov, dchud at gwu edu<br />
<br />
* 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: <br />
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.<br />
- we'll separate into groups and hack on stuff.<br />
- at the end of the day, we'll present our progress.<br />
<br />
Not a code hacker? No worries; all skill sets and backgrounds are valuable! <br />
<br />
'''I plan on attending:'''<br />
* Devon Smith<br />
* Esha Datta<br />
* Ray Schwartz - schwartzr2@wpunj.edu<br />
* Karen Coombs - coombsk{at}oclc{dot}org<br />
* Julia Bauder - julia{dot}bauder{at}gmail{dot}com<br />
* Jason Stirnaman (jstirnaman at kumc.edu)<br />
* Joshua Gomez<br />
* Ayla Stein<br />
* Harrison Dekker<br />
* Ian Walls - iwalls{at}library{dot}umass{dot}edu<br />
* Scott Hanrath<br />
* [[User:Kevenj|Keven Jeffery]]<br />
* James Van Mil - james.vanmil at gmail com<br />
* Sean Crowe - sean.crowe@uc.edu<br />
* Karen coyle - kcoyle at kcoyle.net<br />
* David Lacy - david dot lacy at villanova dot edu<br />
* mark matienzo<br />
* David Uspal<br />
* Emily Lynema - ejlynema at ncsu dot edu<br />
* Sean Chen<br />
* Donald Mennerich<br />
* Allan Berry - allan{dot}berry{at}gmail{dot}com<br />
* Declan Fleming - declan at declan dot net<br />
* Chick Markley -- chick at qrhino dot com<br />
* Rosalyn Metz -- rosalynmetz at gmail com<br />
* Devin Higgins - higgi135 at msu dot edu<br />
* Emily Zervas emily{dot}zervas{at}gmail{dot}com<br />
* May Chan -- msuicat at gmail dot com<br />
* Kathryn Stine - kathryn dot stine at ucop dot edu<br />
<br />
=== Intro to Hydra ===<br />
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)<br />
* Justin Coyne, Data Curation Experts (justin.coyne at curationexperts.com)<br />
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br />
<br />
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. <br />
<br />
'''I plan on attending:'''<br />
* Jeremy Prevost<br />
* Dennis Ogg - ogg{at}ucar{dot}edu<br />
* Terry Brady<br />
* Betsy Coles - bcoles{at}caltech{dot}edu<br />
* Brendan Quinn - brendan-quinn at northwestern dot edu<br />
* Shawn Kiewel - smkiewel at uga dot edu<br />
* Steven Villereal – villereal{at}gmail{dot}com<br />
* Ryan Eby<br />
* Dean Farrell<br />
* Ian Chan<br />
* Mark Mounts<br />
* Carl Jones<br />
* Laney McGlohon - lmcglohon@getty.edu<br />
* Nancy Enneking - nenneking@getty.edu<br />
* Allan Berry - allan{dot}berry{at}gmail{dot}com<br />
* Andrew Darby - agdarby at miami dot edu<br />
<br />
=== Intro to Blacklight ===<br />
* Bess Sadler, Stanford University Library (bess at stanford.edu)<br />
* Jason Ronallo, NC State (jronallo at gmail.com)<br />
* Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)<br />
<br />
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. <br />
<br />
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<br />
<br />
'''I plan on attending:'''<br />
* John MacGillivray<br />
* Jon Stroop<br />
* Jeremy Morse - jgmorse at umich<br />
* Karen Miller - k-miller3{at}northwestern{dot}edu<br />
* Tommy Ingulfsen - tommying{at}caltech{dot}edu<br />
* Chung Kang<br />
* Santi Thompson<br />
* Brandon Dudley<br />
* Ken Irwin<br />
* Hillel Arnold<br />
* Heidi Frank - hf36{at}nyu{dot}com<br />
* Chris Sharp - csharp{at}georgialibraries{dot}org<br />
* Bill McMillin - wmcmilli{at} pratt{dot} edu<br />
* Jason Raitz - jcraitz at ncsu dot edu<br />
* Linda Ballinger - ballingerl at newberry dot org<br />
* Tim Thompson - t.thompson5{at}miami{dot}edu<br />
* David Gonzalez - d.gonzalez26 at umiami dot edu<br />
* Courtney Greene - crgreene at indiana dot edu<br />
<br />
=== DPLA Intro/Hacking ===<br />
<br />
* Presenter(s)/Leader(s): TBD<br />
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)<br />
<br />
This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
=== Fail4lib ===<br />
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)<br />
* Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)<br />
<br />
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.<br />
<br />
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:<br />
<br />
# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.<br />
# 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:<br />
#* Technical failure<br />
#* Failure to effectively address a real user need<br />
#* Overinvestment<br />
#* Outreach/Promotion failure<br />
#* Design/UX failure<br />
#* Project team communication failure<br />
#* Missed opportunities (risk-averse failure)<br />
#* Successes gleaned from failures<br />
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.<br />
# 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.<br />
<br />
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.<br />
<br />
'''I plan on attending:'''<br />
* Becky Yoose<br />
* Lisa Rabey<br />
* Cynthia Ng (maybe) - cynthia [dot] s [dot] ng [at] gmail<br />
* Patrick Berry, pberry@csuchico.edu<br />
<br />
=== Solr 4 In Depth ===<br />
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)<br />
<br />
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?<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Erin Fahy - erin.fahy at mtholyoke edu<br />
* Esmé Cowles, escowles@ucsd.edu<br />
* Jon Stroop<br />
* Adam Constabars<br />
* Kevin Clarke<br />
* Jacob Andresen<br />
* Ted Lawless (tlawless at brown dot edu)<br />
* Jay Luker<br />
* Tom Burton-West<br />
* Curtis Thacker<br />
* Eric James eric dot james at yale dot edu<br />
* Bess Sadler (bess at stanford dot edu)<br />
* Michael North<br />
* Charles Draper<br />
* Nick Cappadona<br />
* Stephanie Collett - stephanie dot collett at ucop dot edu<br />
* Kalee Sprague - kalee dot sprague at yale dot edu<br />
* Jeff Peterson - gpeterso at umn dot edu<br />
* Erik Hetzner<br />
[[Category:Code4Lib2013]]</div>Eghhttps://wiki.code4lib.org/index.php?title=2012_Lightning_Talks_Signup&diff=111922012 Lightning Talks Signup2012-02-07T19:52:51Z<p>Egh: /* Thursday, 10:15-11:00am [9 slots] */</p>
<hr />
<div>'''Sign up for Lightning Talks!!'''<br />
<br />
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.<br />
<br />
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:<br />
<br />
''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.''<br />
<br />
''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.''<br />
<br />
''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.''<br />
<br />
You might also like Mark Fowler's's [http://www.perl.com/pub/2004/07/30/lightningtalk.html Advice for Giving a Lightning Talk].<br />
<br />
'''LIGHTNING TALK SIGNUPS OPEN AT 10 AM PST ON FEBRUARY 7'''<br />
<br />
=== Tuesday, 4:10-5:10pm [12 slots] ===<br />
<br />
Enter ''Name'' -- ''Title of Talk''<br />
<br />
# Al Cornish / XTF in 300 seconds<br />
# 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<br />
# Andrew Nagy / Vendors Suck<br />
# akorphan - Heat maps... not just for input analysis<br />
# Gabriel Farrell / ElasticSearch<br />
# nettie lagace - identifying and solving interoperability problems through cooperation<br />
# Eric Larson -- Finding images in book page images<br />
# adam wead / Blacklight at the Rock Hall<br />
# Kelley McGrath -- FRBR, facets, moving images<br />
# Bohyun Kim -- [http://www.slideshare.net/bohyunkim Web Usability in terms of words]<br />
# Simon Spero. - Restriction Classes, Bitches<br />
# Cynthia Ng / [http://processing.org/ Processing] & [http://processingjs.org/ ProcessingJS]<br />
<br />
=== Wednesday, 4:00-5:00pm [12 slots] ===<br />
<br />
Enter ''Name'' -- ''Title of Talk''<br />
<br />
# Scott Hanrath -- Zotero and SHERPA/RoMEO API mashup<br />
# [[User:DataGazetteer|Peter Murray]] -- Introducing FOSS4LIB.org<br />
# @anarchivist -- something something something<br />
# Mike Durbin -- Edge Cases - Digitizing and delivering undescribed items in EAD<br />
# David Walker -- Basic Learning Tool Interoperability (LTI) Protocol<br />
# Ryuuji Yoshimoto -- Introducing CALIL.JP ,scraping/mushup all of OPACs in JAPAN!<br />
# Kåre Fiedler Christiansen (@kaarefc) -- Chucking all the software components in a library together to present recorded radio and tv<br />
# Joel Richard -- introducing Macaw metadata collection tool <br />
#Rachel Frick - LOD-LAM Incubator Project<br />
# Mao Tsunekawa - Project Shizuku : Making Friends in libraries<br />
# Keith Folsom - Archivists' Toolkit Database Server on an Amazon EC2 Instance<br />
#Rebecca jones<br />
<br />
=== Thursday, 10:15-11:00am [9 slots] ===<br />
<br />
Enter ''Name'' -- ''Title of Talk''<br />
<br />
# David Uspal -- Rapid Deployment Projects<br />
# Robert Haschart -- Adding publicly-accessible Hathi Trust items to your Solr-based discovery system.<br />
# Jeremy Nelson -- Aristotle a Django based Discovery Layer<br />
# Dennis Schafroth - Turbo MARC in YAZ Library<br />
# Yuka Egusa, Masao Takaku -- Recovery of Minamisanriku Library from tsunami disaster<br />
# Corey Harper -- Records to Graphs to Records: Value of DC Abstract Model<br />
# Erik Hetzner -- Strategy for c4l voting<br />
#<br />
#<br />
<br />
<br />
[[Category:Code4Lib2012]]</div>Eghhttps://wiki.code4lib.org/index.php?title=2012_Craft_Brew_Drinkup&diff=110122012 Craft Brew Drinkup2012-02-06T21:00:50Z<p>Egh: </p>
<hr />
<div>'''Wednesday, February 8, after 9 PM, in hospitality suite'''<br />
<br />
The Craft Brew Drinkup at Code4lib 2012 is all about sharing and enjoying good beer with fellow conference attendees. The idea is to bring bottles of your favorite beers.<br />
<br />
While you're not obligated to bring ''local beers'' from whereever you're from, participants are definitely encouraged to bring beer that you think is special and might be somewhat hard for others outside your area to find. Homebrew is especially welcome. Sign up below with your name, where you're from, and list a few brews or bottles you're thinking about (but not necessarily committing to) bringing along. You can also request that people bring specific beer if you so desire, but don't necessarily expect that your wishes will be granted.<br />
<br />
''If you do not check bags or otherwise cannot arrange to bring beer from where you call home, you may be interested in buying beer from a local beer store. See the "Buying Beer in Seattle" section below for suggestions.''<br />
<br />
__TOC__<br />
<br />
=== Sign up ===<br />
<br />
{| border="1" cellpadding="5" class="sortable" <br />
! Name<br />
! Location<br />
! Brews or Breweries I might bring<br />
! Requests<br />
|-<br />
| anarchivist<br />
| New Haven CT/Brooklyn NY<br />
| '''Purchased''': Element Brewing Dark Element, Element Brewing Extra Special Oak, Olde Burnside Ten Penny Ale Reserve, Cisco Captain Swain's Extra Stout<br />
'''Special bottles''': Who knows? Something special.<br />
| Imperial porters/stouts; really funky-/Brett-tasting beers or wild ales; highly-hopped stuff; interesting session beers<br />
|-<br />
| kayiwa<br />
| Chicago IL<br />
| Bourbon County Stout; New Glarus Barleywine, 3 Floyds Behemoth Barleywine<br />
| Barleywines; Aged Stouts; Anything from Deschutes<br />
(psst, Francis: I've got some homebrewed barleywine aging in the basement; i won't be in Seattle but I'll bring some to C4L-Midwest -[[User:Kenirwin|Kenirwin]] 13:26, 29 January 2012 (PST))<br />
|-<br />
| danwho<br />
| San Diego, CA<br />
| Alpine Brewery Exponential Hoppiness; Iron Fist; maybe Lost Abbey; Bud Light<br />
| hoppy imperials, sours, funky farmhouses. Also, I'd vote Wednesday or Tuesday evening since a lot of folks are doing the Microsoft tour and/or newcomer dinners Monday<br />
|-<br />
| declan<br />
| San Diego, CA<br />
| hmm, looking over the cellar... Parabola, Black Tuesday, Cherry Adam, Angel Share, Captain stout, Silva.... we'll see!<br />
| dark, black stuff. like my heart. Or sours. Or Belgies. Founders, Bells, New Glaris, Goose Island.<br />
|-<br />
| awead<br />
| Cleveland, OH<br />
| Founders Porter, some new IPA I found...<br />
| Stuff that doesn't suck.<br />
|-<br />
|bibliotechy<br />
|Atlanta, Ga<br />
|Some Terrapin beers... Hopsecutioner, Sweetwater Brewery Exodus Porter if it is still around<br />
|Boreale noire, rousse or cuivre from Montreal! <br />
|-<br />
|sdellis<br />
|Lambertville, NJ<br />
|Riverhorse... (possibly Hop Hazard, but I'll see what's fresh). Maybe Lionshead (pilsner) from Doylestown, PA (legend has it you can drink as much as you want and never get a hangover).<br />
|Bitters, pub style, IPAs, brown ales<br />
|-<br />
|jastirn<br />
|Kansas City, KS<br />
|Whatever I can get from Wilderness Brewing (KC), Free State (Lawrence, KS), Schlafly Imperial Stout (St. Louis), and Blvd Smokestack (KC) (for Danwho)<br />
| More blueberry stout, stouts, lagers, spicy<br />
|-<br />
|HLPitts<br />
|Salem, OR<br />
|Hopworks barleywine, Rogue Chocolate Stout and Dead Guy, Seven Brides porter, Wandering Aengus cider, and a small variety (less small than it was yesterday...) from Deschutes (including Obsidian for anarchivist)<br />
|stouts/porters, sours, red ales<br />
|-<br />
|bohyunkim<br />
|Miami, FL<br />
|Scotch ale and Pale ale from Oskar Blues brewery / White Rascal from Avery from in Colorado, Boulder<br />
|cider, Rogue Dead Guy, malty, fruity, blonde/gloden ale <br />
|-<br />
|carmendarlene<br />
|San Diego, CA<br />
|something from SoCal...Maybe more Alpine. Going shopping at the Best Damn Beer Store later this week.<br />
|New Glaris, Goose Island, Three Floyds, Cantillon...stuff that I can't get in San Diego. <br />
|-<br />
|flyingzumwalt & jcoyne<br />
|Minneapolis, MN<br />
|Surly Coffee Bender & Surly Cynic, Bell's Two Hearted, Lift Bridge Farm Girl, Crispin Cider<br />
|Revivalist beers (ie. [http://www.yardsbrewing.com/ales_poor-richards-tavern-spruce.asp Yard's Revolutionary Beers] ), New Glarus, Yuengling<br />
|-<br />
|singlesoliloquy<br />
|St. Louis, MO<br />
|[http://www.schlafly.com/beers/styles/quadrupel/ Schlafly Quadrupel] & [http://www.schlafly.com/beers/styles/biere-de-garde/ Schlafly Biere de Garde]<br />
|Good pilsners.<br />
|-<br />
|pberry<br />
|Chico, CA<br />
|Hope to buy Chico stuff in SEA, Bigfoot was just released.<br />
|Ales<br />
|-<br />
|calvinmah<br />
|Vancouver, Canada<br />
|driving to SEA so I'll bring a crate<br />
|Beer<br />
|-<br />
|tara robertson<br />
|Vancouver, Canada<br />
|two limited release beers from [http://gib.ca/beer/ Granville Island Brewing]: Fresh Hop ESP, Imperial IPA<br />
|<br />
|-<br />
|younga, ward, jeff<br />
|Seattle, WA<br />
|Random assortment of growlers: Georgetown Brewery, Big Time, Schooner Exact, Epic Ales.<br />
|<br />
|-<br />
|lrobare<br />
|Eugene, OR<br />
|Ninkasi, probably Total Domination and something else<br />
|<br />
|-<br />
|scollett<br />
|Seattle, WA<br />
|Live in Berkeley, CA, but will buy local or raid the beer stash of my Seattle relatives.<br />
|<br />
|-<br />
|lisapisa77<br />
|Reno, NV<br />
|Ichthyosaur "Icky" IPA from Great Basin and probably something else<br />
|Alagash or Victory or brown ales<br />
|-<br />
|-<br />
|chrpr<br />
|New York, NY<br />
|Brooklyn Sorachi Ace, Southhampton Saison, Probably some other stuff<br />
|Sours, Farmhouse, Misc. high abv goodness...<br />
|-<br />
|carboy<br />
|Arlington, TX<br />
|Yeti, Mephistopheles<br />
|Imperial stout, IPA, barleywine<br />
|-<br />
|mbaggett<br />
|Knoxville, TN<br />
|I won't be checking a bag, but I'll be raiding all the Seattle beer spots this weekend. I hope to surprise everyone with a bottle of Pliny the Elder or at least the new Oak Aged Espresso Yeti.<br />
|Double IPAs, West Coast IPAs, Saisons and Sours<br />
|-<br />
|dlovins<br />
|New York, NY<br />
| Not sure. Something local<br />
|<del>Maybe a hefeweizen of some sort</del> something good in any case<br />
|-<br />
|saverkamp<br />
|Iowa City, IA<br />
|Something from Good People (AL), Back Forty (AL), maybe also Millstream (IA) or Peacetree (IA)<br />
|<br />
|-<br />
|dileshni<br />
|Toronto, ON<br />
|Muskoka cream ale & Beau's Brewery LugTread Lagered Ale<br />
|Cookies.<br />
|-<br />
|chick<br />
|Berkeley<br />
|Best I can find between now and then<br />
|Chocolate Bacon Candy<br />
|-<br />
|jeg<br />
|Charlottetown, PEI<br />
|Gahan IPA, Brown, Might pickup something else on the way<br />
|Hops. Enough hops to peel paint off walls.<br />
|-<br />
|jkeck<br />
|SF Bay Area<br />
|Won't be checking baggage so will I will pick up something local.<br />
|All kinds of IPAs. Hoppy beers. Bacon.<br />
|-<br />
|mackeral<br />
|SF Bay Area<br />
|High Water "Blind Spot" Dark Specialty Ale (Belmont, CA), Auburn Alehouse Imperial IPA (Auburn, CA), Monk's Cafe Flemish Sour Ale (Belgium)<br />
|sours baby<br />
|-<br />
|-<br />
|jdwyn<br />
|Iowa<br />
|MillStream John's White Ale--Iowa brewer (think Belium white like: Hoegaarden, Blue Moon)<br />
|A beer tasting education.<br />
|-<br />
|-<br />
|skerijayne aka DigiKeri_SIL<br />
|MD<br />
|Clipper City Siren Noire, Brewer's Art something, Victory maybe Golden Monkey?<br />
|New Glarus, Belgians, anything over 8%<br />
|-<br />
|ddrexler<br />
|La Grande, OR<br />
|Eastern Oregon stuff: a few fancy brews from Deschutes and Terminal Gravity IPA<br />
|surprise me<br />
|-<br />
|gugek<br />
|Durham, NC<br />
|[http://twitter.com/#!/chefjoseandres/statuses/160920845353619457 Fullsteam First Frost Persimmon]<br />
|Something creative<br />
|-<br />
|wickr<br />
|Hillsboro, OR<br />
|Deschutes Hop Henge, Rogue Hazelnut Brown Nectar, Ambacht (Hillsboro, OR) Pie Cherry Dark<br />
|<br />
|-<br />
|acollier<br />
|Fresno, CA<br />
|Pliny, Sierra Nevada Big Foot (2012)<br />
|Any Sours or Imperial IPAs<br />
|-<br />
|Erik Hetzner<br />
|Oakland, CA<br />
|1 growler Russian River Damnation (Belgian Strong Golden)<br />
|<br />
|}<br />
<br />
=== Suggestions ===<br />
<br />
'''Add using the following format: (person who you are making the request of): (your request) - (your name)'''<br />
<br />
* Unnamed persons from the Keystone State: Sly Fox, any special Weyerbacher - anarchivist<br />
* anyone: Boulevard smokestack series - danwho<br />
* whosoever brought blueberry stout last year, more of that please - jastirn<br />
* Oregonians/PNW folks: Deschutes Hop Henge (cuz it's seasonal) and Obsidian (cuz I like it) - anarchivist<br />
* younga/Seattlites: Georgetown Donkey Deux; Georgetown Braggott - anarchivist<br />
* if by chance anyone is coming from Salt Lake City: I would love Big Bad Baptist from Epic. Or the Wit if it's available again (I think it's the wrong season though). - HLPitts<br />
<br />
=== Buying Beer in Seattle ===<br />
<br />
from an email to the code4lib list: <br />
<br />
: I can think of three good bottleshops (all w/ taps in case you want a growler) that are located on bus lines from downtown:<br />
:<br />
: * [http://bottleworksbeerstore.blogspot.com/ Bottleworks]: Probably the shop I frequent the most. Take the 16 to Wallingford.<br />
: * [http://www.lastdropbeershop.com/ Last Drop]: Take the 71,72, or 73 north from downtown and get off at 80th.<br />
: * [http://www.seattlebeerauthority.com/ Beer Authority]: probably the quickest trip from downtown on the 522. get off at the 125th St stop in Lake City and walk north a couple of blocks.<br />
: * [http://www.fullthrottlebottles.com/ Full Throttle Bottles]: Buses 131, 106, 23 --about 30 minute ride. <br />
: * Also, QFC (large grocery store chain) usually has a great selection.<br />
: * Lots of other pub/beer places noted on [http://g.co/maps/4m5pk the map]<br />
<br />
=== Disclaimers === <br />
<br />
* This is an unofficial event organized by attendees of Code4lib 2012.<br />
* All guests at the Drinkup must be 21 years of age or over with a [http://www.cherylslastcall.com/pdfs/Acceptable-ID-Forms.pdf valid form of ID].<br />
* Any participation in the Drinkup is at your own risk.<br />
* All guests are expected to drink responsibly and behave appropriately.<br />
<br />
<br />
=== Packing and Shipping Beer ===<br />
<br />
If you're flying to Code4lib, you will have to consider how to bring your beer. Some attendees in past years have packed beer in their checked luggage, and others have purchased a beer shipper that was checked separately as luggage. In any event, '''you will not be able to bring beer in carryon luggage.'''<br />
<br />
The following are links to resources that provide info on packing your beer for transit.<br />
<br />
* [http://barlowbrewing.com/2010/11/11/how-to-pack-and-ship-beer/ How to pack and ship beer]<br />
* [http://baltimoresnacker.blogspot.com/2009/06/how-to-pack-beer-and-wine-into-your.html How to pack beer and wine into your luggage]<br />
* [http://beeradvocate.com/forum/read/3880083 Flying With Beer (Beer Advocate forums)]<br />
* [http://beeradvocate.com/forum/read/4364472 Shipping beer while on business travel (Beer Advocate forums)]<br />
* [http://www.mrboxonline.com/bottle-styrofoam-beer-shipper-p-7579.html A sample styrofoam beer shipper/box combo]<br />
<br />
<br />
[[Category:Code4Lib2012]]</div>Eghhttps://wiki.code4lib.org/index.php?title=2012_c4l2012_social_activities&diff=109162012 c4l2012 social activities2012-02-06T16:28:50Z<p>Egh: </p>
<hr />
<div>==Ideas==<br />
* Woodinville distillery tour<br />
* Seattle distillery tour<br />
* Favorite local breweries<br />
* Favorite local tea houses<br />
* Favorite local used bookstores<br />
* Visit hackerspace<br />
** +1<br />
<br />
==Planned events==<br />
<br />
===Pre-Newcomer + Veterans dinner /drink-up Monday===<br />
Early in town for pre-conference? <br />
First time at code4lib? <br />
Don't know anyone at code4lib?<br />
Join fellow c4l newbies + 2nd + 3rd timers + veterans. <br />
You will gain a bunch of new/veteran code4libbers in one night!<br />
Sign up below (NO CAP). You can show up only for dinner or drinks or both! <br />
<br />
But put your name so that we have a rough idea about the number of ppl who will show up =)<br />
<br />
'''Plans'''<br />
* When: Monday evening (2/6) <br />
* For Dinner: Meet at 6PM (ish)at the hotel lobby<br />
* For Drinks: show up at Hideout between 8 -10 PM for local art, fancy cocktails, or Belgian beer<br />
* For Hospitality suite intro chat/hangout: show up at 10 PM - midnight? at hospitality suite<br />
<br />
Dinner: [http://www.yelp.com/biz/kastoori-grill-seattle Kastoori Grill -Indian & Himalayan/Nepalese/Tibetan (vegetarian-friendly)]<br />
0.8 miles 15 min. walk<br />
* Bohyun Kim - n/v (2nd-timer) (leader)<br />
* Jason Clark - leader<br />
* Margaret Heller<br />
* Sarah Johnston - n<br />
* Andrea Schurr - n/v (2nd-timer)<br />
* Jason Ronallo<br />
* Karen Coombs - v<br />
* Eric James<br />
* Misty De Meo - n<br />
* Keri Thompson - n<br />
* Andreas Orphanides - v<br />
* Tom Burton-West -v<br />
* Keith Folsom - n<br />
* Sam Meister - n<br />
<br />
Drinks: [http://www.yelp.com/biz/the-hideout-seattle Hideout Lounge] for local art, fancy cocktails, and Belgian beer<br />
0.3 miles 8 min. walk<br />
* Bohyun Kim - n/v (2nd-timer) (leader)<br />
* Jason Clark - leader<br />
* Lisa Kurt - n<br />
* Margaret Heller<br />
* Andrea Schurr - n/v (2nd-timer)<br />
* Anoop Atre (Would love to if back from MS visit)<br />
* Heather Pitts (maybe) - n<br />
* Evviva Weinraub - Hope to join up if back from MS visit)<br />
* Megan Banasek -n<br />
* Misty De Meo (maybe) - n<br />
* Keri Thompson (definitely)<br />
* David Drexler (likely) - n<br />
* Andreas Orphanides - v<br />
* Rebecca Jones - n<br />
* Chick Markley - v<br />
* Ray Henry - n<br />
<br />
Hospitality suite intro chat/ hangout: just show up at the hospitality suite - no sign up required.<br />
<br />
===Morning Run Tuesday===<br />
I (Ray Schwartz) am organizing a morning run for anyone that would like to join me. It will be around 5 to 6 miles. I usually run a 10 minute per mile pace. And I would like to start around 7am. Select which days Tuesday or Wednesday or both mornings. Choose the date you wish via this Doodle link http://www.doodle.com/3tbigutqvkda5ib8<br />
<br />
Link to the course map is at http://www.runningmap.com/?id=351428.<br />
<br />
So far 4 have signed up for both Tuesday and Wednesday. Let's meet in the Lobby at 7am on Tuesday, and we will decide how to do Wednesday.<br />
<br />
===Newcomer dinner Tuesday===<br />
First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating <strike>discussions about</strike> demonstrations of the many uses of <strike>bacon</strike> <strike>dongles</strike> XML.<br />
<br />
Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!<br />
<br />
'''Plans'''<br />
* When: Tuesday evening (2/7) '''Note that this year's dinner is on Tuesday'''<br />
* Time: 6 PM (ish) or whenever you can get your group together<br />
* Mastermind (if you have any questions): [mailto:yoosebec@grinnell.edu Becky Yoose]<br />
<br />
''Guidelines:''<br />
*Max of '''6''' per group<br />
**Please, no waitlisting :(<br />
*ID yourselves so we can get a good mix of new people and veterans in each group<br />
**New folks - n<br />
**c4l vets - v<br />
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group :)''')<br />
**Leader duties<br />
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library coders <br />
***Herd folks from hotel to restaurant (know where you're going!)<br />
<br />
<br />
'''Restaurants'''<br />
<br />
'''Restaurants within .25 miles of the hotel'''<br />
<br />
[http://www.sazeracrestaurant.com/index.php Sazerac] (AWESOME happy hour menu that runs until 8)<br />
* Martin Haye - n<br />
* William Gunn - n<br />
* Rebecca Jones - n<br />
* Chick Markley - v<br />
* Al Cornish - v<br />
* Keri Thompson - n<br />
*'''capped at 6''' ''(So, who's the fearless leader of this group? ~yo_bj)''<br />
<br />
[http://oasiankitchen.com/ O'Asian Kitchen and Lounge] (Asian) <br />
<br />
'''Restaurants between .25 miles and .5 miles of the hotel'''<br />
<br />
[http://www.pikebrewing.com/index_html.shtml Pike Brewing] (local brewery, pub food)<br />
* Ken Varnum - n<br />
* Chad Nelson - n<br />
* Ed Summers - v<br />
* Tommy Ingulfsen - n<br />
* Adam Wead - v or .5n<br />
* Dan Coughlin - n<br />
*'''capped at 6''' ''(So, who's the fearless leader of this group? ~yo_bj)''<br />
<br />
[http://www.rockbottom.com/ The Rock Bottom Restaurant & Brewery] (American)<br />
<br />
[http://www.wildginger.net/ Wild Ginger] (Asian, a bit overpriced)<br />
* Tamar Sadeh - n<br />
* Kevin Clarke - v<br />
<br />
[http://www.thepurplecafe.com/index.html Purple Cafe] (American, Wine Bar) ''reservation made under Calvin Mah for 6:30pm for the 6 of us. I'll be meeting in the hotel lobby at 6pm with some sort of sign. See you then!''<br />
* Calvin Mah - (leader) - v<br />
* David Isaak - n<br />
* Aaron Collier - n<br />
* Sean Hannan - v<br />
* Joshua Gomez - v<br />
* Charlie Morris - n<br />
* '''capped at 6'''<br />
<br />
[http://www.cafepaloma.com/ Cafe Paloma] (Mediterranean)<br />
* Jean Rainwater (leader) - v<br />
* Kelley McGrath - n<br />
* Lori Robare - n<br />
* Emily Lynema - v<br />
* Sarah Johnston - n<br />
* Sam Meister - n<br />
* '''capped at 6'''<br />
<br />
[http://www.thecollinspub.com/ Collins Pub] (Pub Food, great beer selection)<br />
* Francis Kayiwa - (leader) "(get hold of me at first dot last name at goog as the date gets closer with your mobile)" v<br />
* Michael Lindsey - v<br />
* Dan Suchy - v<br />
* David Drexler - n<br />
* Laura Smart - n<br />
* Heather Pitts - n<br />
*'''capped at 6'''<br />
<br />
[http://www.mcmenamins.com/311-six-arms-home Six Arms - McMenamins] (Pub Food & they brew their own beer) ''Meet in the Lobby at 6pm. I've also emailed you. --Joel''<br />
* Joel Richard (richardjm AT si.edu) (leader) - v<br />
* Margaret Heller - v<br />
* Sibyl Schaefer (sschaefer AT rockarch . org) - v<br />
* Tim Lepczyk (timlepczyk AT gmail.com) - n<br />
* Ray Schwartz (schwartzr2@wpunj.edu) - v<br />
* Andrea Schurr (andrea-schurr AT utc DOT edu) - v(2nd-timer)<br />
* '''capped at 6'''<br />
<br />
[http://www.611supreme.com/ 611 Supreme] (Crepes and Full Bar) ''Reservation for 6 at 6:30. Meet in the conference hotel lobby at 6pm. Look for the short woman in a trench coat and wide brim hat ~Becky''<br />
<br />
*Becky Yoose (leader) - v <br />
*Cynthia Ng - n<br />
*Zoe Chao - v<br />
*Stephanie Collett - n (2nd-timer)<br />
*Bethany Nowviskie - n<br />
* Ben Shum - n<br />
*'''capped at 6'''<br />
<br />
[http://www.panafricamarket.com/wp/ Pan Africa Restaurant & Bar] (Pan African) <br />
CLOSED TUESDAYS!!!!!!!!!!!!!!!!!!<br />
Sorry for the confusion. I have moved everyone to Long Provincial, so that you'll have a place held in case you want it. If Long Provincial doesn't suit you, please remove your name in case someone else wants the spot. Again, I'm sorry. --Jason<br />
<br />
[http://longprovincial.com/ Long Provincial] Vietnamese (.7 miles from hotel; 15 minute walk)<br />
<br />
Reservation for 6 for 6:30 (and I have a confirmation number!). Meet in the hotel lobby at 6 to allow for a strolling pace to walk over there.<br />
<br />
Has a jellyfish tank.<br />
<br />
*Jason Ronallo (leader?) - v?<br />
*Nettie Lagace - n<br />
*Bohyun Kim - n/v (2nd-timer)<br />
*Wendy Robertson - n<br />
*Jennifer Bowen - n/v (3rd timer)<br />
*James Stuart - n<br />
*'''capped at six'''<br />
<br />
'''Restaurants between .5 and 1 mile from hotel'''<br />
<br />
[http://momijiseattle.com/ Momiji] New Japanese restaurant in Seattle - [http://www.concierge.com/tools/blogs/unpacked/2011/10/momiji-seattle.html Reviewed in Concierge.com]<br />
<br />
* Andrew Nagy (leader) - v<br />
* Cory Lown - v<br />
* Tod Robbins - n<br />
<br />
<br />
[http://tomdouglas.com/index.php?page=palace-kitchen-dinner Palace Kitchen] (another Tom Douglas restaurant, w/ a focus on meat). ''I have made a reservation for 6 at 8pm. Let's meet in the conference lobby at 6:30pm and make our way slowly over; we will find things to do in the interim. Look for Mike Giarlo, a man who may be holding a sign that says "HI I'M MIKE GIARLO" or otherwise shouting his name or looking confused.''<br />
<br />
* Mike Giarlo (leader) - v<br />
* Carmen Mitchell - n<br />
* Daniel Lovins - v<br />
* Cary Gordon - v <br />
* Declan Fleming - v<br />
* Amy Unger - n<br />
* (CAPPED AT SIX!)<br />
<br />
[http://sitkaandspruce.com/ Sitka and Spruce] (Eclectic, super-local and super-seasonal.) ''We have a reservation for 6 at 8:15pm. We'll meet in the conference lobby at 6:30 pm and head over - the owners also run [http://www.ferdinandthebar.com/home/ Bar Ferd'nand], a wine shop/bar in the same building, and we can kill time there before we eat. Look for Mark Matienzo or Hillel Arnold.''<br />
<br />
* Mark Matienzo (leader) - v<br />
* Hillel Arnold - sophomore<br />
* Devon Smith - v<br />
* bernardo gomez - n<br />
* Derek Merleaux - sophmore<br />
* Jennifer Weintraub - n<br />
* (CAPPED AT SIX!)<br />
<br />
[http://www.yelp.com/biz/japonessa-seattle Japonessa Restaurant] (Japanese + full bar)<br />
* Kate Zwaard - n<br />
* Joe Atzberger - v<br />
* Scott Fisher - n (2nd-timer)<br />
* Anoop Atre - n<br />
<br />
[http://tomdouglas.com/index.php?page=serious-pie Serious Pie] (Tom Douglas restaurant, inventive pizzas, good local beer list). <br />
<br />
* Christopher Spalding (leader) - v<br />
* Robin Schaaf - n<br />
* Jason Stirnaman - v<br />
* Christina Morris - n<br />
* Lisa Kurt - n<br />
* Ray Henry - n<br />
*'''capped at six'''<br />
<br />
[http://www.allmenus.com/wa/seattle/204592-ballet-restaurant/menu/ Ballet] (Vietnamese)<br />
<br />
[http://www.kokebrestaurant.com/ Kokeb Ethiopian Restaurant] (Ethiopian) ''Let's say meet at the lobby at 6pm like everyone else. Woohoo!''<br />
<br />
''We have reservations for 6 at 6:45.''<br />
<br />
* Andreas Orphanides (leader) - v<br />
* Mark Mounts - v<br />
* Joe Montibello - n<br />
* Justin Littman - n<br />
* Ron Peterson<br />
* Bobbi Fox - sophmore<br />
* (CAPPED AT SIX!)<br />
Crashing the [http://www.seattlerb.org/ Seattle Ruby] meetup, which meets on Capital Hill at 7:00 on Tuesdays. Eat at [http://www.yelp.com/biz/poppy-seattle Poppy] before. Leaving from the hotel lobby at 6:00. ''If you dig Ruby, come to this. Seattle ruby produced Nokogiri, Vlad, Rubygems.org ....''<br />
* Matt Zumwalt (leader) - v<br />
* *Justin Coyne - n<br />
* Misty De Meo - n<br />
<br />
<br />
[http://tomdouglas.com/index.php?page=dahlia-lounge Dahlia Lounge] (Pacific Northwest cuisine, $$$)<br />
<br />
[http://www.mattsinthemarket.com/ Matt's in the Market] (Northwest Cuisine, $$$)<br />
<br />
[http://www.placepigalle-seattle.com/ Place Pigalle] (French)<br />
<br />
[http://www.chezshea.com/ Chez Shea] (French)<br />
<br />
[http://www.elysianbrewing.com/elysian.html Elysian Breweries and Pubs] (Pub Food)<br />
<br />
[http://www.mezaseattle.com/index.html Meza] (Latin Fare)<br />
Have reservations for 6.45. It's about a mile from hotel. 10min bus, 30 min walk. Meet in lobby @ 6 and we'll work out bus/walk/cab. -corey<br />
* Tara Robertson - n<br />
* Shawn Averkamp - sophomore<br />
* Corey Harper - v (leader)<br />
* Shaun Ellis - sophomore<br />
* Jon Stroop - fifth year senior<br />
* Birkin James Diana - v (hi Jon!; hey newcomers, I'm taking the 6th slot, but, if you're stuck for a signup, plz do feel free to bump/overwrite me - seriously!)<br />
* '''capped at 6'''''(So, who's the fearless leader of this group? ~yo_bj)''<br />
<br />
[http://inthebowlbistro.com/index.php In the Bowl] (Veg*n, Asian)<br />
<br />
[http://www.plumbistro.com/ Plumb Bistro] (Veg*n)<br />
<br />
[http://highlineseattle.com/ Highline] (Veg*n, bar)<br />
<br />
'''Restaurants more than 1 miles from the hotel'''<br />
<br />
[http://bravehorsetavern.com/ Brave Horse Tavern] (another Tom Douglas, good regional beer list, yummy food. Near South Lake Union. Would require a ride on the South Lake Union Trolley (SLUT), but it's easy to get to/use from downtown. <br />
<br />
[http://www.temperodobrasil.net/ Tempero do Brasil] I was excited to see Ipanema Grill 6 blocks from the hotel, unfortunately it seems to be closed for good. So this restaurant which is a 10 minute ($15) cab ride away and which also serves Brazilian cuisine (including the ever-tasty feijoada) will have to do.<br />
* Robert Haschart - leader - v third year<br />
* Molly Pickral - n<br />
* Erik Hetzner - 2nd c4l<br />
<br />
[http://flyingfishrestaurant.com/ Flying Fish] (Seafood)<br />
<br />
[http://www.allmenus.com/wa/seattle/3437-cafe-flora/menu/dinner/ Cafe Flora] (FANTASTIC Veg*n restaurant. Use Metro bus #11 to get there)<br />
<br />
[http://www.teapotvegetarianhouse.com/index.htm Teapot Vegetarian House] (Veg*n, Asian)<br />
<br />
[http://spaceneedle.com/restaurant/ Space Needle] (American, Pricy; but what the heck, listed it anyway for those who want the experience)<br />
<br />
==="Get Lamp" viewing Tuesday (9 PM) ===<br />
<br />
"Tuesday, February 7, 9 PM or shortly after -Courtyard Ballroom"<br />
<br />
Adam Wead and Michael Klein are organizing a viewing of [http://www.getlamp.com/ Get Lamp: The Text Adventure Documentary]<br />
<br />
It's not about Linux, Apache, MySQL or PHP, but if you don't have a one, you might get eaten by a grue.<br />
<br />
If there is additional interest, there may be another viewing this week.<br />
<br />
<br />
===Morning Run Wednesday===<br />
I (Ray Schwartz) am organizing a morning run for anyone that would like to join me. It will be around 5 to 6 miles. I usually run a 10 minute per mile pace. And I would like to start around 7am. Select which days Tuesday or Wednesday or both mornings. Choose the date you wish via this Doodle link http://www.doodle.com/3tbigutqvkda5ib8<br />
<br />
Link to the course map is at http://www.runningmap.com/?id=351428.<br />
<br />
So far 4 have signed up for both Tuesday and Wednesday. Let's meet in the Lobby at 7am on Tuesday, and we will decide how to do Wednesday.<br />
<br />
<br />
<br />
===Veg*n Dinner Wednesday===<br />
<br />
We'll pick a place with lots of veg*n options to go eat Wednesday for dinner. Vegetarians and non-vegetarians welcome.<br />
<br />
*[http://lovinghut.us/seattle/index.html Loving Hut] Modest price. 1 mile from hotel. Will do bill splitting if we let them know up front. <br />
<br />
Talked with Loving Hut and made a reservation for 15 for 6:30. Meet in the hotel lobby at 6.<br />
<br />
*Jason Ronallo (jronallo AT gmail.com)<br />
*Sean Hannan<br />
*Ed Summers<br />
*James Stuart<br />
*Bohyun Kim<br />
*Bethany Nowviskie<br />
*Margaret Heller<br />
*Laura Smart<br />
*Sibyl Schaefer<br />
*Cynthia Ng<br />
*Andrea Shurr<br />
*Eric James<br />
*Birkin James Diana<br />
*Sheree F<br />
*Misty De Meo<br />
*Reservation is for 15.<br />
<br />
===Meat-Up Dinner Wednesday===<br />
<br />
[http://www.bokaseattle.com/ BOKA Kitchen + Bar], 1010 1st Ave (between Spring St & Madison St) - about 1/3 mile/5 min from hotel. We head over from the Amazon Technology Open House and get there by 8PM.<br />
Very much a eat-local place. Beecher cheddar - yum. Nice, mellow room. We should be back in plenty of time to hit the Drink-Up.<br />
<br />
* Cary Gordon<br />
* Anoop Atre<br />
<br />
Note that they have some excellent non-meat options for any meat groupies that want to hang with us.<br />
<br />
(if you do not find a suitable burger joint, there are also some top-notch steakhouses in Seattle. Both the Metropolitan Grill and El Gaucho are delightful if folks are OK with $50 steaks. Just FYI, not trying to hijack your meat-up, Cary!. -mjgiarlo)<br />
<br />
===Evergreen/Koha and friends dinner Wednesday===<br />
Put your name and any food limitations, or suggestions of places to go. We'll figure where we're going later. For now, let's assume we're meeting in the hotel lobby at 6pm.<br />
<br />
* Tara Robertson<br />
* Chris Sharp<br />
* Tod Robbins - n<br />
* Ben Shum<br />
<br />
===[[2012 Craft Brew Drinkup|Craft Brew Drinkup]], Wednesday (9 PM)===<br />
<br />
'''Wednesday, February 8, 9 PM-ish -Hospitality Suite'''<br />
<br />
Like good beer? Bring some in your luggage! Some of us are planning to bring some of our favorite local, special, or homebrewed beers to share. Interested? Sign up on the [[2012 Craft Brew Drinkup]] page!<br />
<br />
===Dim Sum Lunch Thursday===<br />
<br />
For those of you staying in town after the last session on Thursday, [http://oasiankitchen.com/ O'Asian Kitchen] has dim sum service during the weekdays. Meet up around 12:35, meeting location tba. Bring cash for easier bill splitting.<br />
<br />
*Becky Yoose<br />
* Declan Fleming - love me some Dim Sum!<br />
* Adam Wead<br />
* Heather Pitts<br />
* Sibyl Schaefer<br />
* Anoop Atre<br />
* Dan Suchy<br />
* Carmen Mitchell<br />
* Tara Robertson<br />
* Ray Schwartz<br />
* Cynthia Ng<br />
* Corey Harper<br />
* Joshua Gomez<br />
* Cary Gordon<br />
* Mike Giarlo<br />
* Joe Atzberger<br />
* Dileshni Jayasinghe<br />
* Ryan Wick<br />
<br />
==Social Map - places of interest==<br />
[http://g.co/maps/4m5pk Code4lib 2012 - Seattle - social events, hangouts, and places to see]<br />
<br />
==Seattle Events Feb 5-9==<br />
===Saturday, February 4, 2012===<br />
In case you are showing up really early.<br />
* Belgianfest: http://www.washingtonbeer.com/belgianfest/<br />
===Sunday, February 5, 2012===<br />
* Clinton Fearon & The Boogie Brown Band/Live Wyya/Adrian Xavier/Selecta Raiford/DJ Courtland, Neumos: http://neumos.com/neumos.php<br />
* Michael The Blind/The Els, Skylark: http://www.skylarkcafe.com/<br />
* Addaura/Alda/Hallow, Comet<br />
* "I Am My Own Wife" 7:30pm at Seattle Repertory Theatre (Seattle Center) http://www.seattlerep.org/Plays/1112/IM/<br />
* Science Fiction + Fantasy short film festival, Encore screening. http://www.empmuseum.org/programs/index.asp?categoryID=216<br />
<br />
===Monday, February 6, 2012===<br />
* Silent Movie Mondays: Last Command 1928, http://stgpresents.org/artists/?artist=1829#, Show at 7:00pm, The Paramount Theatre $10<br />
This all-classic film series, First Oscars, is accompanied by live music from the historic Mighty Wurlitzer organ, one of the last three remaining organs of its kind to reside in its original environment, played by critically acclaimed organist Jim Riggs.<br />
<br />
===Tuesday, February 7, 2012===<br />
* Lionize/Maylene & The Sons Of Disaster, El Corazon: http://elcorazonseattle.com/<br />
* The Pulltab Playboys/Rachel Lyn Harrington & The Knock Outs/The James Low Western Front, Sunset: http://sunsettavern.com/<br />
* Twin Sister, Vera: http://theveraproject.org/shows/<br />
* The Features, Chop Suey: http://www.chopsuey.com/<br />
* Wilco/White Denim, Paramount Theatre: http://stgpresents.org/<br />
* "I Am My Own Wife" 7:30pm at Seattle Repertory Theatre (Seattle Center) http://www.seattlerep.org/Plays/1112/IM/<br />
* Intro to Arduino Workshop, 7pm at Metrix Create Space http://metrixcreatespace.com/<br />
<br />
===Wednesday, February 8, 2012===<br />
* The Golden Blondes/The Jet Age/Mr. Drinx & The Pot Heads, Sunset: http://sunsettavern.com/<br />
* Pipsisewah/The Chasers/The Magic Mirrors, Tractor: http://www.tractortavern.com/ <br />
* Dengue Fever vs Secret Chiefs 3, Moe Bar http://bit.ly/yJtfXv (how could you pass the opportunity to see someone play this thing :http://bit.ly/wB5AgZ<br />
* Amazon Tech in Seattle is having an open house next Wednesday at 5:30 PM with Werner Vogels and David Friedberg of the Climate Corporation. https://aws.amazon.com/amazon-open-house-february-2012/ ([http://g.co/maps/adpnt map])<br />
<br />
===Thursday, February 9, 2012===<br />
* SAM Opening - Gauguin and Polynesia: An Elusive Paradise: http://www.seattleartmuseum.org/gauguin<br />
* The Jayhawks, Neptune Theater: http://stgpresents.org/<br />
* Digital Leather, Comet <br />
* Savani World Quintet/Super Sones, Columbia City Theater: http://www.columbiacitytheater.com/<br />
* Blvd Park {album release}/Nettle Honey/Creeping Time, Tractor: http://www.tractortavern.com/<br />
* Eleanor Friedberger, Crocodile: http://thecrocodile.com/index.html<br />
<br />
===Ongoing Events===<br />
* Seattle Art Museum: Tours are every Saturday & Sunday at noon, and the First Thursday of every month at 10:30, 11:30 am, 12:30 & 1:30 pm.<br />
* EMP: Exhibits on display include: Battlestar Galactica, Nirvana, Avatar, and Can’t Look Away: The Lure of Horror Film<br />
* Teatro ZinZanni: ¡Caliente! http://dreams.zinzanni.org/<br />
* Pacific NW Ballet: performing Don Quixote at McCaw Hall http://www.pnb.org/<br />
* Oklahoma!, Sunday matinee and nightly: 5th Avenue Theatre, 1308 Fifth Avenue http://www.5thavenue.org/show/oklahoma<br />
<br />
==Local events/places==<br />
* Metrix Create Space<br />
* Ada's Technical Books<br />
* Northwest Outdoor Center<br />
* Center for Wooden Boats<br />
* Empty Sea Studios acoustic music<br />
<br />
<br />
==Local Beer Places==<br />
* Map of [http://beermapping.com/maps/citymaps.php?m=seattle#lat=47.66723703450515&lng=-122.28263854980469&z=5 beer venues] maintained at Beermapping.com.<br />
* List of [http://www.washingtonbeer.com/breweries/seattle-king-co/ local breweries] ([http://maps.google.com/maps/ms?hl=en&ie=UTF8&msa=0&msid=201783184139227541123.0004813e64758434cb054&source=embed&ll=47.558921,-122.106171&spn=0.442982,1.234589&z=10&source=embed map]) maintained by the Washington Beer Commission<br />
* Map of [http://www.ratebeer.com/Places/RegionMap.asp?rid=7600 beer venues] maintained by Ratebeer.com.<br />
<br />
==See also==<br />
[http://orbiscascade.org/index/c4l-things-to-do-in-seattle Things to do in Seattle, from the hosts]<br />
<br />
<br />
[[Category:Code4Lib2012]]</div>Eghhttps://wiki.code4lib.org/index.php?title=2012_preconference_proposals&diff=101752012 preconference proposals2012-01-12T05:05:14Z<p>Egh: /* Interest in Attending */</p>
<hr />
<div>=Proposals for 2012 Code4LibCon Preconferences=<br />
Proposals closed Sunday, November 20, 2011, so we can finalize the list and add them to registration! (The deadline for preconference proposals has passed.)<br />
<br />
Spaces available: main meeting room (max 275) + 5 breakout rooms (max 30-50). <br />
<br />
'''Please include a "Contact/Responsible Individual" name and email address so we know who is willing to put on the proposed precon.<br />
'''<br />
==Full Day==<br />
<br />
<br />
=== Hacking Content ===<br />
<br />
What is the future of getting library information and resources into users’ hands at the right time and with appropriate context and relevancy. Learning management systems, library guides, Web-scale discovery systems-plenty of tools to choose from and still we see lots of opportunities for improvement. Let’s pick them apart and brainstorm ideas for projects that could address weaknesses in one or all of these systems. If you’re interested in these issues, challenges and conundrums join us for a day of thinking, dreaming and scheming. All skill sets and backgrounds needed. <br />
<br />
Speakers/Facilitators will be:<br />
- Thom Cox - Manager of Library Information Technology Services - Tufts University<br />
- Ken Varnum – Web Systems Manager - University of Michigan Libraries<br />
- Evviva Weinraub – Director, Emerging Technologies and Services - Oregon State University Libraries <br />
<br />
Contact: Margaret Mellinger - margaret dot mellinger at oregonstate dot edu<br />
<br />
==== Interest in Attending ====<br />
<br />
=== Developing applications using REST web services ===<br />
<br />
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.<br />
<br />
Come ready to learn and code!<br />
<br />
Presenter: Karen Coombs - coombsk at oclc dot org<br />
<br />
==== Interest in Attending ====<br />
<br />
*Sam Kome<br />
*Ray Schwartz<br />
*Jim Robinson<br />
*David Bucknum<br />
<br />
==Half Day Morning==<br />
<br />
<br />
=== Linkfest ===<br />
<br />
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!<br />
<br />
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!<br />
<br />
Organizer type person: Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu<br />
<br />
==== Interest in Attending ====<br />
*Becky Yoose<br />
*Tom Johnson<br />
*Ed Summers<br />
* bernardo gomez ( bgomez at emory dot edu )<br />
* William Gunn<br />
* Jason Ronallo<br />
<br />
=== What's New in Solr ===<br />
<br />
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. <br />
<br />
Presenter: Erik Hatcher - erik . hatcher @ lucidimagination dot com<br />
<br />
==== Interest in Attending ====<br />
* "Gabriel Farrell" <gsf24@drexel.edu><br />
* "Erik Hetzner" <erik.hetzner AT ucop BORK edu><br />
<br />
==Half Day Afternoon==<br />
<br />
<br />
=== Git -r done === <br />
<br />
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.<br />
<br />
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.<br />
<br />
Coordinator: Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com<br />
<br />
Helper: Cary Gordon, Cherry Hill Company, @highermath / cgordon@chillco.com<br />
<br />
==== Interest in Attending ====<br />
<br />
* Patrick Berry (pberry@csuchico.edu)<br />
* Chris Sharp (csharp@georgialibraries.org)<br />
* Matt Critchlow (mcritchlow@ucsd.edu)<br />
* Peter Murray (Peter.Murray@lyrasis.org)<br />
*Margaret Heller (mheller@dom.edu)<br />
<br />
=== Blacklight ===<br />
<br />
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.<br />
<br />
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).<br />
<br />
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.<br />
<br />
Presenters: Jessie Keck, Stanford University - jkeck at stanford dot edu | Molly Pickral, University of Virginia - mpc3c at virginia dot edu<br />
<br />
==== Interest in Attending ====<br />
* bernardo gomez ( bgomez at emory dot edu )<br />
<br />
=== DACS and EAD Overview ===<br />
<br />
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.<br />
<br />
Presenter: Doris Munson, Eastern Washington University, dmunson at ewu dot edu<br />
(please feel free to contact me if you are interested in being a co-presenter)<br />
<br />
==== Interest in Attending ====<br />
<br />
=== [[Digging into metadata: context, code, and collaboration]] ===<br />
<br />
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. <br />
<br />
Person Herder: Becky Yoose, Grinnell College, yoosebec at grinnell dot edu<br />
<br />
Collaborators/Facilitators: Corey Harper, New York University - corey dot harper at nyu dot edu | Shana L. McDanold, University of Pennsylvania - <br />
mcdanold at pobox dot upenn dot edu | Laura Smart, Caltech - laura at library dot caltech dot edu<br />
<br />
==== Interest in Attending ====<br />
<br />
=== "Geo" ===<br />
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. <br />
<br />
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<br />
(please feel free to contact Tim if you are interested in being a co-presenter)<br />
<br />
==== Interest in Attending ====<br />
* "Gabriel Farrell" <gsf24@drexel.edu><br />
<br />
[[Category: Code4Lib2012]]</div>Eghhttps://wiki.code4lib.org/index.php?title=2012_talks_proposals&diff=98032012 talks proposals2011-11-18T22:48:47Z<p>Egh: </p>
<hr />
<div>Deadline for talk submission is ''Sunday, November 20''.<br />
<br />
Prepared talks are 20 minutes (including setup and questions), and focus on one or more of the following areas:<br />
* tools (some cool new software, software library or integration platform)<br />
* specs (how to get the most out of some protocols, or proposals for new ones)<br />
* challenges (one or more big problems we should collectively address)<br />
<br />
The community will vote on proposals using the criteria of:<br />
* usefulness<br />
* newness<br />
* geekiness<br />
* diversity of topics<br />
<br />
Please follow the formatting guidelines:<br />
<br />
<pre><br />
<br />
== Talk Title: ==<br />
<br />
* Speaker's name, affiliation, and email address<br />
* Second speaker's name, affiliation, email address, if second speaker<br />
<br />
Abstract of no more than 500 words.<br />
</pre><br />
<br />
== VuFind 2.0: Why and How? ==<br />
<br />
* Demian Katz, Villanova University, demian.katz@villanova.edu<br />
<br />
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.<br />
<br />
== Open Source Software Registry ==<br />
<br />
* [[User:DataGazetteer|Peter Murray]], LYRASIS, Peter.Murray@lyrasis.org<br />
<br />
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]. <br />
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. <br />
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.<br />
<br />
The first half of this session will demonstrate the registry functions and describe how projects and providers can get involved. <br />
The second half of the session will be a brainstorming suggestion of how to expand the functionality and usefulness of the registry.<br />
<br />
== Property Graphs And TinkerPop Applications in Digital Libraries ==<br />
<br />
* Brian Tingle, California Digital Library, brian.tingle.cdlib.org@gmail.com<br />
<br />
[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. <br />
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.<br />
<br />
<br />
== Security in Mind ==<br />
<br />
* Erin Germ, United States Naval Academy, Nimitz Library, germ@usna.edu<br />
<br />
I would like to talk about security of library software.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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”.<br />
<br />
''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.''<br />
<br />
== Search Engines and Libraries ==<br />
<br />
* Greg Lindahl, blekko CTO, greg@blekko.com<br />
<br />
[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.<br />
<br />
''We have exhibited at a couple of library conferences, and have received a lot of interest. blekko is a free service.''<br />
<br />
== Beyond code. Versioning data with Git and Mercurial. ==<br />
<br />
* Stephanie Collett, California Digital Library, stephanie.collett@ucop.edu<br />
* Martin Haye, California Digital Library, martin.haye@ucop.edu<br />
<br />
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.<br />
<br />
==Design for Developers==<br />
<br />
*Lisa Kurt, University of Nevada, Reno, lkurt@unr.edu<br />
<br />
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.<br />
<br />
==Building research applications with Mendeley==<br />
<br />
William Gunn, Mendeley william.gunn@mendeley.com (@mrgunn)<br />
<br />
This is partly a tool talk and partly a big idea one.<br />
<br />
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.<br />
<br />
<br />
<br />
==Your UI can make or break the application (to the user, anyway)==<br />
<br />
* Robin Schaaf, University of Notre Dame, schaaf.4@nd.edu<br />
<br />
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.<br />
<br />
==Why Nobody Knows How Big The Library Really Is - Perspective of a Library Outside Turned Insider==<br />
<br />
* Patrick Berry, California State University, Chico, pberry@csuchico.edu<br />
<br />
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.<br />
<br />
==Building a URL Management Module using the Concrete5 Package Architecture==<br />
<br />
* David Uspal, Villanova University, david.uspal@villanova.edu<br />
<br />
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.<br />
<br />
==Building an NCIP connector to OpenSRF to facilitate resource sharing==<br />
<br />
* Jon Scott, Lyrasis, jon_scott@wsu.edu and Kyle Banerjee, Orbis Cascade Alliance, banerjek@uoregon.edu <br />
<br />
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.<br />
<br />
<br />
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. <br />
<br />
<br />
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.<br />
<br />
==Practical Agile: What's Working for Stanford, Blacklight, and Hydra==<br />
<br />
* Naomi Dushay, Stanford University Libraries, ndushay@stanford.edu<br />
<br />
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.<br />
<br />
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.<br />
<br />
==Quick and <strike>Dirty</strike> Clean Usability: Rapid Prototyping with Bootstrap==<br />
<br />
* Shaun Ellis, Princeton University Libraries, shaune@princeton.edu <br />
<br />
''"The code itself is unimportant; a project is only as useful as people actually find it." - Linus Torvalds'' [http://bit.ly/p4uuyy]<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
==Search Engine Relevancy Tuning - A Static Rank Framework for Solr/Lucene==<br />
<br />
* Mike Schultz, Amazon.com (formerly Summon Search Architect) mike.schultz@gmail.com<br />
<br />
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.<br />
<br />
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:<br />
<br />
* Query-time only calculation - nothing is baked into the index - with parameters adjustable at query time.<br />
* 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.<br />
* An intuitive approach for mixing dynamic and static rank that is more effective than simple adding or multiplying.<br />
* A way of equating disparate static metadata types that leads to understandable results ordering.<br />
<br />
==Submitting Digitized Book-like things to the Internet Archive==<br />
<br />
* Joel Richard, Smithsonian Institution Libraries, richardjm@si.edu<br />
<br />
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. <br />
<br />
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. <br />
<br />
Finally, we'll wrap up with a brief summary of how to use things that are on the Internet Archive in your own websites.<br />
<br />
== So... you think you want to Host a Code4Lib National Conference, do you? ==<br />
<br />
* Elizabeth Duell, Orbis Cascade Alliance, eduell@uoregon.edu<br />
<br />
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!<br />
<br />
Be a step ahead of the game by learning from the people behind the curtain. Ask questions and be given templates/ cheat sheets! <br />
<br />
== HTML5 Microdata and Schema.org ==<br />
<br />
* Jason Ronallo, North Carolina State University Libraries, jason_ronallo@ncsu.edu<br />
<br />
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. <br />
* What is microdata? <br />
* Where does microdata fit with regards to other approaches like RDFa and microformats? <br />
* Where do libraries stand in the worldview of Schema.org and what can they do about it? <br />
* How can implementing microdata and schema.org optimize your sites for search engines?<br />
* What tools are available?<br />
<br />
== Stack View: A Library Browsing Tool ==<br />
<br />
* Annie Cain, Harvard Library Innovation Lab, acain@law.harvard.edu<br />
<br />
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].<br />
<br />
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.<br />
<br />
== “Linked-Data-Ready” Software for Libraries ==<br />
<br />
* Jennifer Bowen, University of Rochester River Campus Libraries, jbowen@library.rochester.edu<br />
<br />
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. <br />
<br />
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.<br />
<br />
== How people search the library from a single search box ==<br />
<br />
* Cory Lown, North Carolina State University Libraries, cory_lown@ncsu.edu<br />
<br />
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.<br />
<br />
== An Incremental Approach to Archival Description and Access ==<br />
<br />
* Chela Scott Weber, New York University Libraries, chelascott@gmail.com<br />
* Mark A. Matienzo, Yale University Library, mark@matienzo.org<br />
<br />
''This is placeholder text; description coming shortly''<br />
<br />
== Making the Easy Things Easy: A Generic ILS API ==<br />
<br />
* Wayne Schneider, Hennepin County Library, wschneider@hclib.org<br />
<br />
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.<br />
<br />
This talk will present work we have done on a web services approach to an API for traditional library transactional data, including example applications.<br />
<br />
== Your Catalog in Linked Data==<br />
<br />
* Tom Johnson, Oregon State University Libraries, thomas.johnson@oregonstate.edu<br />
<br />
Linked Library Data activity over the last year has seen bibliographic data sets and vocabularies proliferating from traditional library<br />
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.<br />
<br />
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.<br />
<br />
== Getting the Library into the Learning Management System using Basic LTI == <br />
<br />
* David Walker, California State University, dwalker@calstate.edu<br />
<br />
The integration of library resources into learning management systems (LMS) has long been something of a holy grail for academic libraries. The ability to deliver targeted library systems and services to students and faculty directly within their online course would greatly simplify access to library resources. Yet, the technical barriers to achieving that goal have to date been formidable. <br />
<br />
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.<br />
<br />
== Turn your Library Proxy Server into a Honeypot ==<br />
<br />
* Calvin Mah, Simon Fraser University, calvinm@sfu.ca (@calvinmah)<br />
<br />
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.<br />
<br />
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.<br />
<br />
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. <br />
<br />
== Relevance Ranking in the Scholarly Domain ==<br />
<br />
* Tamar Sadeh, PhD, Ex Libris Group, tamar.sadeh@exlibrisgroup.com<br />
<br />
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. <br />
<br />
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. <br />
<br />
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. <br />
<br />
== Mobile Library Catalog using Z39.50 ==<br />
<br />
* James Paul Muir, The Ohio State University, muir.29@osu.edu<br />
<br />
A talk about putting a new spin on an age-old technology, creating a universal interface, which exposes any Z39.50 capable library catalog as a simple, useful and universal REST API for use in native mobile apps and mobile web.<br />
<br />
The talk includes the exploration and demonstration of the Ohio State University’s native app “OSU Mobile” for iOS and Android and shows how the library catalog search was integrated.<br />
<br />
The backbone of the project is a REST API, which was created in a weekend using a PHP framework that translates OPAC XML results from the Z39.50 interface into mobile-friendly JSON formatting.<br />
<br />
Raw Z39.50 search results contain all MARC information as well as local holdings. <br />
Configurable search fields and the ability to select which fields to include in the JSON output make this solution a perfect fit for any Z39.50-capable library catalog.<br />
<br />
Looking forward, possibilities for expansion include the use of Off Campus Sign-In for online resources so mobile patrons can directly access online resources from a smartphone (included in the Android version of OSU Mobile) as well as integration with library patron account.<br />
<br />
Enjoy this alternative to writing a custom OPAC adapter or using a 3rd party service for exposing library records and use the proven and universal Z39.50 interface directly against your library catalog. <br />
<br />
<br />
== DMPTool: Guidance and Resources for your data management plan ==<br />
<br />
* Marisa Strong, California Digital Libary, marisa.strong@ucop.edu<br />
<br />
A number of U.S. funding agencies such as the National Science Foundation require researchers to supply detailed, cost-effective plans for managing research data, called Data Management Plans. To help researchers with this requirement, several organizations such as the California Digital Library, University of Illinois, University of Virginia, Smithsonian Institution, the DataONE consortium and the (UK) Digital Curation Centre) came together to develop the DMPTool. The goal of the DMPTool is to provide researchers with guidance, links to resources and help with writing data management plans.<br />
<br />
This tool presents the requirements specific to the funding agency they are applying for along with detailed help with each section. Users can create a plan, preview it, export it in various formats, and make it freely accessible for others to read. Users who are members of participating institutions will benefit from specific help for each section, suggested answers, and resources for management of their data, all specific to their institution. Institutions can also announce events, workshops, and data management information via the DMPTool blog available from within the tool.<br />
<br />
This open-source software tool is integrated with federated login using Shibboleth which allows users to login via their home institutions. It is a Ruby/Rails application hosted on a SLES VM. We had a geographically distributed development team sharing code on Bitbucket. <br />
<br />
This talk will demo the features of the application as well as highlight the development practices and infrastructure used in building the application.<br />
<br />
== Lies, Damned Lies, and Lines of Code Per Day ==<br />
<br />
* James Stuart, Columbia University, james.stuart@columbia.edu<br />
<br />
We've all heard about that one study that showed that Pair Programming was 20% efficient than working alone. Or maybe you saw on a blog that study that showed that programmers who write fewer lines of code per day are more efficient...or was it less efficient? And of course, we all know that programmers who work in (Ruby|Python|Java|C|Erlang) have been shown to be more efficient.<br />
<br />
A quick examination of some of the research surrounding programming efficiency and methodology, with a focus on personal productivity, and how to incorporate the more believable research into your own team's workflow.<br />
<br />
<br />
==An Anatomy of a Book Viewer==<br />
<br />
*Mohammed Abuouda, Bibliotheca Alexandrina, mohammed.abuouda@bibalex.org<br />
<br />
Bibliotheca Alexandria (BA) hosts 210,000 digital books in different languages available at http://dar.bibalex.org. It includes the largest collection of digitized Arabic books. Using open source tools, BA has developed a modular book viewer that can be deployed in any environment to provide the users with a great personalized reading experience. BA’s book viewer provides several services that make this possible: morphological search in different languages, localization, server load balancing, scalability and image processing. Personalization features includes different types of annotation such as sticky notes, highlighting and underlining. It also provides the ability to embed the viewer in any webpage and change its skin.<br />
<br />
In this talk we will describe the book viewer architecture, its modular design and how to incorporate it in your current environment.<br />
<br />
<br />
== Carrier: Digital Signage System ==<br />
<br />
* [[User:jmspargu|Justin Spargur]], The University of Arizona, spargurj@u.library.arizona.edu<br />
<br />
Carrier is a web-based digital signage application written using JavaScript, PHP, MySQL that can be used on any device with an internet connection and a web browser. Used across the University of Arizona Libraries campuses, Carrier can display any web-based content, allowing users to promote new library collections and services via images, web pages, or videos. Users can easily manage the order in which slides are delivered, manage the length that slides are displayed for, set dates for when slides should be shown, and even specify specific locations where slides should be presented. <br />
<br />
In addition to marketing purposes, Carrier can be used to send both low and high priority alerts to patrons. Alerts can be sent through the administrative interface, via RSS feeds, and even through a Twitter feed, allowing for easy integration with existing campus emergency notification systems.<br />
<br />
I will describe the technical underpinnings of Carrier, challenges that we’ve faced since its implementation, enhancements planned for the next release of the software, and discuss our plans for releasing this software for others to use '''for free'''.<br />
<br />
<br />
== We Built It. They Came. Now What? ==<br />
<br />
* [[User:evviva|Evviva Weinraub]], Oregon State University, evviva.weinraub@oregonstate.edu<br />
<br />
You have a great idea for something new or useful. You build it, put it out there on GitHub, do a couple of presentations, maybe a press release and BAM, suddenly you’ve created a successful Open Source tool that others are using. Great!<br />
<br />
Fast-forward 3 years. <br />
<br />
You still believe in the product, but you can no longer be solely responsible for taking care of it. Just putting it out there has made it a tool others use, but how do you find a community of folks who believe in the product as much as you do and are willing to commit the time and energy into building, sustaining and moving this project forward. Or just figuring out if you should bother trying?<br />
<br />
In 2006, OSU Libraries built an Interactive Course Assignment system called Library a la Carte – think LibGuides only Open Source. We now find ourselves in just this predicament. <br />
<br />
What can we do as a community to move beyond our build-first-ask-questions-later mentality and embed sustainability into our new and existing ideas and products without moving toward commercialization? I fully expect we’ll end up with more questions than answers, but let’s spend some talking about our predicament and yours and think about how we can come out the other side. <br />
<br />
<br />
== Contextually Rich Collections Without the Risk: Digital Forensics and Automated Data Triage for Digital Collections ==<br />
<br />
* [[User:kamwoods|Kam Woods]], University of North Carolina at Chapel Hill, kamwoods@email.unc.edu<br />
* Cal Lee, University of North Carolina at Chapel Hill, callee -- at -- ils -- unc -- edu<br />
* Matthew Kirschenbaum, University of Maryland, mkirschenbaum@gmail.com<br />
<br />
Digital libraries and archives are increasingly faced with a significant backlog of unprocessed data along with an accelerating stream of incoming material. These data often arrive from donor organizations, institutions, and individuals on hard drives, optical and magnetic disks, flash memory devices, and even complete hardware (traditional desktop computers and mobile systems). <br />
<br />
Information on these devices may be sensitive, obscured by operating system arcana, or require specialized tools and procedures to parse. Furthermore, the sheer volume of materials being handled means that even simple tasks such as providing useful content reports can be impractical (or impossible) in current workflows.<br />
<br />
Many of the tasks currently associated with data triage and analysis can be simplified and performed with improved coverage and accuracy through the use of open source digital forensics tools. In this talk we will discuss recent developments in providing digital librarians and archivists with simple, open source tools to accomplish these tasks. We will discuss tools and methods be tested, developed and packaged as part of the [http://bitcurator.net BitCurator] project. These tools can be used to reduce or eliminate laborious, error-prone tasks in existing workflows and put valuable time back into the hands of digital librarians and archivists -- time better used to identify and tackle complex tasks that *cannot* be solved by software.<br />
<br />
== Finding Movies with FRBR and Facets ==<br />
<br />
* Kelley McGrath, University of Oregon, kelleym@uoregon.edu<br />
<br />
How might the Functional Requirements for Bibliographic Records (FRBR) model and faceted navigation improve access to film and video in libraries? I will describe the design and implementation of a FRBR-inspired prototype discovery interface ([http://blazing-sunset-24.heroku.com/ http://blazing-sunset-24.heroku.com/]) using Solr and Blacklight . This approach demonstrates how FRBR can enable a work-centric view that is focused on the original movie or program while supporting users in selecting an appropriate version.<br />
<br />
The prototype features two sets of facets, which independently address two important information needs: (1) "What kind of movie or program do you want to watch?" (e.g., a 1970s TV sitcom, something directed by Kurosawa, or an early German horror film); (2) "How do you want to watch it? Where do you want to get it from?" (e.g., on Blu-ray, with Spanish subtitles, available at the local public library). This structure enables patrons to narrow, broaden and pivot across facet values instead of limiting them to the tree-structured hierarchy common with existing FRBR applications. <br />
<br />
This type of interface requires controlled data values mapped to FRBR group 1 entities, which in many cases are not available in existing MARC bibliographic records. I will discuss ongoing work using the XC Metadata Services Toolkit ([http://www.extensiblecatalog.org/ http://www.extensiblecatalog.org/]) to extract and normalize data from existing MARC records for videos in order to populate a FRBRized, faceted discovery interface.<br />
<br />
==Escaping the Black Box — Building a Platform to Foster Collaborative Innovation==<br />
<br />
* Karen Coombs, OCLC, coombsk@oclc.org<br />
* Kathryn Harnish, OCLC harnishk@oclc.org<br />
<br />
Exposed Web services offer an unprecedented opportunity for collaborative innovation — that’s one of the hallmarks of Web-based services like Amazon, Google, and Facebook. These environments are popular not only for their native feature sets, but also for the array of community-developed apps that can run in them. The creativity of the development communities that work in these systems brings new value to all types of users.<br />
<br />
What if the library community could realize this same level of collaborative innovation around its systems? What kinds of support would be necessary to transform library systems from “black boxes” to more open, accessible environments in which value is created and multiplied by the user community?<br />
<br />
In this session, we’ll discuss the challenges and opportunities OCLC faced in creating just that kind of environment. The recently-released OCLC “cooperative platform” provides improved access to a wide variety of OCLC’s data and services, allowing library developers and other interested partners to collaborate, innovate, and share new solutions with fellow libraries. We’ll describe the open standards and technologies we’ve put in play in as we:<br />
* exposed robust Web services that provide access to both data and business logic; <br />
* created an architecture for integrating community-built applications in OCLC (and other) products; and <br />
* developed an infrastructure to support community development, collaboration, and app sharing<br />
<br />
Learn how OCLC is helping to open the “black box” -- and give libraries the freedom to become true partners in the evolution of their library systems.<br />
<br />
== Code inheritance; or, The Ghosts of Perls Past ==<br />
<br />
* Jon Gorman, University of Illinois, jtgorman@illinois.ed<br />
<br />
<br />
Any organization has a history not found in its archives or museums. Mysteries exist that origins are lost to the collective institutional knowledge. Despite what has been forgotten by humans, our servers and computers still keep running. Instructions crafted long ago execute like digital ghosts following orders of masters who have long since left.<br />
<br />
The University of Illinois has a fair amount of Perl code created by several different developers. This code includes software that handles our data feeds coming both in and out of campus, reports against our Voyager system, some web applications, and more.<br />
<br />
I'll touch a little on the historical legacy and why Perl is used. From there I'll share some tips, best practices, and some of the mistakes I've made in trying to maintain this code. Most of the advice will transition to any language, but code and libraries discussed will be Perl. The presentation will also touch on some internal debate on whether or not to port parts of our Perl codebase.<br />
<br />
<br />
== Recorded Radio/TV broadcasts streamed for library users ==<br />
<br />
* Kåre Fiedler Christiansen, The State and University Library Denmark, kfc@statsbiblioteket.dk<br />
* Mads Villadsen, The State and University Library Denmark, mv@statsbiblioteket.dk<br />
<br />
"Provide online access to the Radio/TV collection," my boss said. About 500,000<br />
hours of Danish broacast radio and TV. Easy, right? Well, half a year later <br />
we'd done it, but it turned out to involve practically every it employee in the <br />
library and quite a few non-technical people as well.<br />
<br />
Combining our Fedora-based DOMS repository system with our Lucene-based Summa<br />
search system with our WAYF-based single-signon system with an upgrade of our<br />
SAN system for enough speed to deliver the content with an ffmpeg-based <br />
transcoding workflow system with a Wowza-based streaming server, and sprinkling<br />
it all with a nice user-friendly web frontend turned out to be quite a challenge,<br />
but also one of the most engaging experiences for a long time.<br />
<br />
Of course we were immidiately shut down, since the legal details weren't quite<br />
as clear as we thought they were, but take an exclusive preview at <br />
http://developer.statsbiblioteket.dk/kultur/ - username/password: code4lib.<br />
<br />
== NoSQL Bibliographic Records: Implementing a Native FRBR Datastore with Redis ==<br />
* Jeremy Nelson, Colorado College, jeremy.nelson@coloradocollege.edu<br />
<br />
In October, the Library of Congress issued a news release, "A Bibliographic Framework for the Digital Age" outlining a list of requirements for a New Bibliographic Framework Environment. Responding to this challenge, this talk will demonstrate a Redis (http://redis.io) FRBR datastore proof-of-concept that, with a lightweight python-based interface, can meet these requirements. <br />
<br />
Because FRBR is an Entity-Relationship model; it is easily implemented as key-value within the primitive data structures provided by Redis. Redis' flexibility makes it easy to associate arbitrary metadata and vocabularies, like MARC, METS, VRA or MODS, with FRBR entities and inter-operate with legacy and emerging standards and practices like RDA Vocabularies and LinkedData.<br />
<br />
<br />
== Upgrading from Catalog to Discovery Environment: A Consortial Approach ==<br />
<br />
* Spencer Lamm, Swarthmore College, slamm1@swarthmore.edu<br />
* Chelsea Lobdell, Swarthmore College, clobdel1@swarthmore.edu<br />
<br />
<br />
Almost two years ago the Tri-College Consortium of Haverford, Swarthmore, and Bryn Mawr Colleges embarked upon a journey to provide enhanced end-user experience and discoverability with our library applications. Our solution was to implement an integration of ExLibris's Primo Central into Villanova's VuFind for a dual-channel searching experience. We present a case study of the collaborative and technical aspects of our process.<br />
<br />
At a high level we will describe our approach to project management and decision making. We used a multi-tiered structure of working groups with an iterative design-feedback implementation cycle. We will relay lessons learned from our experience: successes, failures, and unexpected hurdles.<br />
<br />
At a lower, technical level we will discuss the vufind search module architecture; the workflow of creating a new search channel; a Primo API parser; and the data structures of the Primo API response and the Primo SearchObject. Time permitting, we will also outline how we modified VuFind's Innovative driver to work with our ILS.<br />
<br />
<br />
== Improving geospatial data access for researchers and students ==<br />
<br />
* Dileshni Jayasinghe, Scholars Portal, University of Toronto, d.jayasinghe@utoronto.ca<br />
* Sepehr Mavedati, Scholars Portal, University of Toronto, sepehr.mavedati@utoronto.ca<br />
<br />
Scholars GeoPortal (http://geo.scholarsportal.info) was created as a platform for online delivery of geospatial data resources to the Ontario Council of University Libraries community. Prior to the start of this project, each institution was storing data locally, and had its own practice for distributing datasets to users. This ranged from home grown online data delivery systems to burning data on to DVDs for each individual request. Most institutions had limited resources and expertise to create and maintain a sophisticated delivery system on their own. Led by OCUL Map, GIS librarians, staff at Scholars Portal in partnership with the Government of Ontario, the GeoPortal project began in 2009.<br />
<br />
Our talk will focus on the design and architecture of Scholars Portal's solution to support maps and geospatial data, and how we distribute these data collections to our users. <br />
<br />
The system consists of 4 main components: metadata management system, map server, spatial database, and the web application.<br />
<br />
*Metadata Management: customized metadata editor with data hosted in MarkLogic, providing text and spatial queries<br />
*Map Server: ArcGIS Server<br />
*Spatial database: MS SQL Server with spatial extension<br />
*Web application: Javascript web application using Dojo and Esri’s Javascript API<br />
<br />
For other code4libbers who are interested in a similar system, we will also discuss the open source alternatives for each component (GeoNetwork, MapServer, etc.), and challenges and limitations we faced trying to use some of these tools. We'd also like to pick your brains on how we can make this application better. What can we do differently?<br />
<br />
== LibX 2.0 ==<br />
<br />
* Godmar Back, Virginia Tech, godmar@gmail.com<br />
<br />
We would like to provide the Code4Lib community with an update on what we've accomplished with LibX (which we last presented in 2009) - where we've gone, what our users are thinking, and how both its technology and its adapter community can be included in the code4lib world.<br />
<br />
== Introducing the DuraSpace Incubator ==<br />
<br />
* Jonathan Markow, DuraSpace, jjmarkow@duraspace.org<br />
<br />
DuraSpace is planning to launch a new incubation program for the benefit of open source projects that wish to become part of our organization, in the interest of helping them to become sustainable, community-driven projects and supporting them afterwards with umbrella services that help them to thrive. From time to time DuraSpace becomes aware of open source software projects in the preservation, archiving, or repository space that are in search of a community “home”. The motivation might be that the project is simply trying to attract more developers, that it would like to develop a more robust community of users and service providers, that its current organizational sponsorship is in question, or that it would like to take advantage of an existing and compatible organization's best practices and administrative infrastructure rather than create a new one of its own. DuraSpace is now prepared to leverage its resources, experience, and reputation in the community to help these projects become, or continue to be, successful. Projects emerging from incubation will become officially recognized as DuraSpace projects. This briefing presents highlights of the DuraSpace Incubator and invites questions and feedback from participants.<br />
<br />
<br />
== In-browser data storage and me ==<br />
<br />
* Jason Casden, North Carolina State University Libraries, jason_casden@ncsu.edu<br />
<br />
When it comes to storing data in web browsers on a semi-persistent basis, there are several partially-adopted, semi-deprecated, product-specific, or even universally accepted options. These include models such as key-value stores, relational databases, and object stores. I will present some of these options and discuss possible applications of these technologies in library services. In addition to quoting heavily from Mark Pilgrim's excellent chapter on this topic, I will weave in my own experience utilizing in-browser data storage in an iPad-based data collection tool to successfully improve performance and data stability while reducing network dependence. See also: HTML5.<br />
<br />
<br />
<br />
== Coding for the past, archiving for the future … and the Salman Rushdie Papers ==<br />
<br />
* Peter Hornsby, Emory University Libraries, phornsb@emory.edu<br />
<br />
Cultural heritage production is moving to the digital medium and libraries use of repository solutions such as Fedora Commons and DSpace are a solid response to this change. But how do we go from, for instance a selection of 90's computing technology to a collection of digital objects ready for ingest into your institution's local repository? Once you have ingested your digital objects how are you going to provide access to these resources? The arrival of the Salman Rushdie Papers, which contain 10 years of Sir Salman Rushdie's digital life, gave Emory University Libraries the opportunity to explore these questions. I would like to to talk about the approach the Emory University Libraries adopted, what we learned and the coding challenges that remain.<br />
<br />
== Indexing big data with Tika, Solr & map-reduce ==<br />
<br />
* Scott Fisher, California Digital Library, scott.fisher AT ucop BORK edu<br />
* Erik Hetzner, California Digital Library, erik.hetzner AT ucop BORK edu<br />
<br />
The Web Archiving Service at the California Digital Library has<br />
crawled a large amount of data, in every format found on the web: 30<br />
TB, comprising about 600 million fetched URLs. In this talk we will<br />
discuss how we parsed this data using Tika and map-reduce, and how we<br />
indexed this data with Solr, tweaked the relevance ranking, and were<br />
able to provide our users with a better search experience.<br />
<br />
[[Category: Code4Lib2012]]</div>Eghhttps://wiki.code4lib.org/index.php?title=2012_talks_proposals&diff=98022012 talks proposals2011-11-18T22:48:30Z<p>Egh: add my talk</p>
<hr />
<div>Deadline for talk submission is ''Sunday, November 20''.<br />
<br />
Prepared talks are 20 minutes (including setup and questions), and focus on one or more of the following areas:<br />
* tools (some cool new software, software library or integration platform)<br />
* specs (how to get the most out of some protocols, or proposals for new ones)<br />
* challenges (one or more big problems we should collectively address)<br />
<br />
The community will vote on proposals using the criteria of:<br />
* usefulness<br />
* newness<br />
* geekiness<br />
* diversity of topics<br />
<br />
Please follow the formatting guidelines:<br />
<br />
<pre><br />
<br />
== Talk Title: ==<br />
<br />
* Speaker's name, affiliation, and email address<br />
* Second speaker's name, affiliation, email address, if second speaker<br />
<br />
Abstract of no more than 500 words.<br />
</pre><br />
<br />
== VuFind 2.0: Why and How? ==<br />
<br />
* Demian Katz, Villanova University, demian.katz@villanova.edu<br />
<br />
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.<br />
<br />
== Open Source Software Registry ==<br />
<br />
* [[User:DataGazetteer|Peter Murray]], LYRASIS, Peter.Murray@lyrasis.org<br />
<br />
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]. <br />
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. <br />
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.<br />
<br />
The first half of this session will demonstrate the registry functions and describe how projects and providers can get involved. <br />
The second half of the session will be a brainstorming suggestion of how to expand the functionality and usefulness of the registry.<br />
<br />
== Property Graphs And TinkerPop Applications in Digital Libraries ==<br />
<br />
* Brian Tingle, California Digital Library, brian.tingle.cdlib.org@gmail.com<br />
<br />
[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. <br />
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.<br />
<br />
<br />
== Security in Mind ==<br />
<br />
* Erin Germ, United States Naval Academy, Nimitz Library, germ@usna.edu<br />
<br />
I would like to talk about security of library software.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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”.<br />
<br />
''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.''<br />
<br />
== Search Engines and Libraries ==<br />
<br />
* Greg Lindahl, blekko CTO, greg@blekko.com<br />
<br />
[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.<br />
<br />
''We have exhibited at a couple of library conferences, and have received a lot of interest. blekko is a free service.''<br />
<br />
== Beyond code. Versioning data with Git and Mercurial. ==<br />
<br />
* Stephanie Collett, California Digital Library, stephanie.collett@ucop.edu<br />
* Martin Haye, California Digital Library, martin.haye@ucop.edu<br />
<br />
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.<br />
<br />
==Design for Developers==<br />
<br />
*Lisa Kurt, University of Nevada, Reno, lkurt@unr.edu<br />
<br />
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.<br />
<br />
==Building research applications with Mendeley==<br />
<br />
William Gunn, Mendeley william.gunn@mendeley.com (@mrgunn)<br />
<br />
This is partly a tool talk and partly a big idea one.<br />
<br />
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.<br />
<br />
<br />
<br />
==Your UI can make or break the application (to the user, anyway)==<br />
<br />
* Robin Schaaf, University of Notre Dame, schaaf.4@nd.edu<br />
<br />
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.<br />
<br />
==Why Nobody Knows How Big The Library Really Is - Perspective of a Library Outside Turned Insider==<br />
<br />
* Patrick Berry, California State University, Chico, pberry@csuchico.edu<br />
<br />
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.<br />
<br />
==Building a URL Management Module using the Concrete5 Package Architecture==<br />
<br />
* David Uspal, Villanova University, david.uspal@villanova.edu<br />
<br />
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.<br />
<br />
==Building an NCIP connector to OpenSRF to facilitate resource sharing==<br />
<br />
* Jon Scott, Lyrasis, jon_scott@wsu.edu and Kyle Banerjee, Orbis Cascade Alliance, banerjek@uoregon.edu <br />
<br />
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.<br />
<br />
<br />
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. <br />
<br />
<br />
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.<br />
<br />
==Practical Agile: What's Working for Stanford, Blacklight, and Hydra==<br />
<br />
* Naomi Dushay, Stanford University Libraries, ndushay@stanford.edu<br />
<br />
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.<br />
<br />
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.<br />
<br />
==Quick and <strike>Dirty</strike> Clean Usability: Rapid Prototyping with Bootstrap==<br />
<br />
* Shaun Ellis, Princeton University Libraries, shaune@princeton.edu <br />
<br />
''"The code itself is unimportant; a project is only as useful as people actually find it." - Linus Torvalds'' [http://bit.ly/p4uuyy]<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
==Search Engine Relevancy Tuning - A Static Rank Framework for Solr/Lucene==<br />
<br />
* Mike Schultz, Amazon.com (formerly Summon Search Architect) mike.schultz@gmail.com<br />
<br />
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.<br />
<br />
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:<br />
<br />
* Query-time only calculation - nothing is baked into the index - with parameters adjustable at query time.<br />
* 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.<br />
* An intuitive approach for mixing dynamic and static rank that is more effective than simple adding or multiplying.<br />
* A way of equating disparate static metadata types that leads to understandable results ordering.<br />
<br />
==Submitting Digitized Book-like things to the Internet Archive==<br />
<br />
* Joel Richard, Smithsonian Institution Libraries, richardjm@si.edu<br />
<br />
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. <br />
<br />
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. <br />
<br />
Finally, we'll wrap up with a brief summary of how to use things that are on the Internet Archive in your own websites.<br />
<br />
== So... you think you want to Host a Code4Lib National Conference, do you? ==<br />
<br />
* Elizabeth Duell, Orbis Cascade Alliance, eduell@uoregon.edu<br />
<br />
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!<br />
<br />
Be a step ahead of the game by learning from the people behind the curtain. Ask questions and be given templates/ cheat sheets! <br />
<br />
== HTML5 Microdata and Schema.org ==<br />
<br />
* Jason Ronallo, North Carolina State University Libraries, jason_ronallo@ncsu.edu<br />
<br />
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. <br />
* What is microdata? <br />
* Where does microdata fit with regards to other approaches like RDFa and microformats? <br />
* Where do libraries stand in the worldview of Schema.org and what can they do about it? <br />
* How can implementing microdata and schema.org optimize your sites for search engines?<br />
* What tools are available?<br />
<br />
== Stack View: A Library Browsing Tool ==<br />
<br />
* Annie Cain, Harvard Library Innovation Lab, acain@law.harvard.edu<br />
<br />
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].<br />
<br />
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.<br />
<br />
== “Linked-Data-Ready” Software for Libraries ==<br />
<br />
* Jennifer Bowen, University of Rochester River Campus Libraries, jbowen@library.rochester.edu<br />
<br />
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. <br />
<br />
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.<br />
<br />
== How people search the library from a single search box ==<br />
<br />
* Cory Lown, North Carolina State University Libraries, cory_lown@ncsu.edu<br />
<br />
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.<br />
<br />
== An Incremental Approach to Archival Description and Access ==<br />
<br />
* Chela Scott Weber, New York University Libraries, chelascott@gmail.com<br />
* Mark A. Matienzo, Yale University Library, mark@matienzo.org<br />
<br />
''This is placeholder text; description coming shortly''<br />
<br />
== Making the Easy Things Easy: A Generic ILS API ==<br />
<br />
* Wayne Schneider, Hennepin County Library, wschneider@hclib.org<br />
<br />
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.<br />
<br />
This talk will present work we have done on a web services approach to an API for traditional library transactional data, including example applications.<br />
<br />
== Your Catalog in Linked Data==<br />
<br />
* Tom Johnson, Oregon State University Libraries, thomas.johnson@oregonstate.edu<br />
<br />
Linked Library Data activity over the last year has seen bibliographic data sets and vocabularies proliferating from traditional library<br />
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.<br />
<br />
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.<br />
<br />
== Getting the Library into the Learning Management System using Basic LTI == <br />
<br />
* David Walker, California State University, dwalker@calstate.edu<br />
<br />
The integration of library resources into learning management systems (LMS) has long been something of a holy grail for academic libraries. The ability to deliver targeted library systems and services to students and faculty directly within their online course would greatly simplify access to library resources. Yet, the technical barriers to achieving that goal have to date been formidable. <br />
<br />
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.<br />
<br />
== Turn your Library Proxy Server into a Honeypot ==<br />
<br />
* Calvin Mah, Simon Fraser University, calvinm@sfu.ca (@calvinmah)<br />
<br />
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.<br />
<br />
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.<br />
<br />
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. <br />
<br />
== Relevance Ranking in the Scholarly Domain ==<br />
<br />
* Tamar Sadeh, PhD, Ex Libris Group, tamar.sadeh@exlibrisgroup.com<br />
<br />
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. <br />
<br />
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. <br />
<br />
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. <br />
<br />
== Mobile Library Catalog using Z39.50 ==<br />
<br />
* James Paul Muir, The Ohio State University, muir.29@osu.edu<br />
<br />
A talk about putting a new spin on an age-old technology, creating a universal interface, which exposes any Z39.50 capable library catalog as a simple, useful and universal REST API for use in native mobile apps and mobile web.<br />
<br />
The talk includes the exploration and demonstration of the Ohio State University’s native app “OSU Mobile” for iOS and Android and shows how the library catalog search was integrated.<br />
<br />
The backbone of the project is a REST API, which was created in a weekend using a PHP framework that translates OPAC XML results from the Z39.50 interface into mobile-friendly JSON formatting.<br />
<br />
Raw Z39.50 search results contain all MARC information as well as local holdings. <br />
Configurable search fields and the ability to select which fields to include in the JSON output make this solution a perfect fit for any Z39.50-capable library catalog.<br />
<br />
Looking forward, possibilities for expansion include the use of Off Campus Sign-In for online resources so mobile patrons can directly access online resources from a smartphone (included in the Android version of OSU Mobile) as well as integration with library patron account.<br />
<br />
Enjoy this alternative to writing a custom OPAC adapter or using a 3rd party service for exposing library records and use the proven and universal Z39.50 interface directly against your library catalog. <br />
<br />
<br />
== DMPTool: Guidance and Resources for your data management plan ==<br />
<br />
* Marisa Strong, California Digital Libary, marisa.strong@ucop.edu<br />
<br />
A number of U.S. funding agencies such as the National Science Foundation require researchers to supply detailed, cost-effective plans for managing research data, called Data Management Plans. To help researchers with this requirement, several organizations such as the California Digital Library, University of Illinois, University of Virginia, Smithsonian Institution, the DataONE consortium and the (UK) Digital Curation Centre) came together to develop the DMPTool. The goal of the DMPTool is to provide researchers with guidance, links to resources and help with writing data management plans.<br />
<br />
This tool presents the requirements specific to the funding agency they are applying for along with detailed help with each section. Users can create a plan, preview it, export it in various formats, and make it freely accessible for others to read. Users who are members of participating institutions will benefit from specific help for each section, suggested answers, and resources for management of their data, all specific to their institution. Institutions can also announce events, workshops, and data management information via the DMPTool blog available from within the tool.<br />
<br />
This open-source software tool is integrated with federated login using Shibboleth which allows users to login via their home institutions. It is a Ruby/Rails application hosted on a SLES VM. We had a geographically distributed development team sharing code on Bitbucket. <br />
<br />
This talk will demo the features of the application as well as highlight the development practices and infrastructure used in building the application.<br />
<br />
== Lies, Damned Lies, and Lines of Code Per Day ==<br />
<br />
* James Stuart, Columbia University, james.stuart@columbia.edu<br />
<br />
We've all heard about that one study that showed that Pair Programming was 20% efficient than working alone. Or maybe you saw on a blog that study that showed that programmers who write fewer lines of code per day are more efficient...or was it less efficient? And of course, we all know that programmers who work in (Ruby|Python|Java|C|Erlang) have been shown to be more efficient.<br />
<br />
A quick examination of some of the research surrounding programming efficiency and methodology, with a focus on personal productivity, and how to incorporate the more believable research into your own team's workflow.<br />
<br />
<br />
==An Anatomy of a Book Viewer==<br />
<br />
*Mohammed Abuouda, Bibliotheca Alexandrina, mohammed.abuouda@bibalex.org<br />
<br />
Bibliotheca Alexandria (BA) hosts 210,000 digital books in different languages available at http://dar.bibalex.org. It includes the largest collection of digitized Arabic books. Using open source tools, BA has developed a modular book viewer that can be deployed in any environment to provide the users with a great personalized reading experience. BA’s book viewer provides several services that make this possible: morphological search in different languages, localization, server load balancing, scalability and image processing. Personalization features includes different types of annotation such as sticky notes, highlighting and underlining. It also provides the ability to embed the viewer in any webpage and change its skin.<br />
<br />
In this talk we will describe the book viewer architecture, its modular design and how to incorporate it in your current environment.<br />
<br />
<br />
== Carrier: Digital Signage System ==<br />
<br />
* [[User:jmspargu|Justin Spargur]], The University of Arizona, spargurj@u.library.arizona.edu<br />
<br />
Carrier is a web-based digital signage application written using JavaScript, PHP, MySQL that can be used on any device with an internet connection and a web browser. Used across the University of Arizona Libraries campuses, Carrier can display any web-based content, allowing users to promote new library collections and services via images, web pages, or videos. Users can easily manage the order in which slides are delivered, manage the length that slides are displayed for, set dates for when slides should be shown, and even specify specific locations where slides should be presented. <br />
<br />
In addition to marketing purposes, Carrier can be used to send both low and high priority alerts to patrons. Alerts can be sent through the administrative interface, via RSS feeds, and even through a Twitter feed, allowing for easy integration with existing campus emergency notification systems.<br />
<br />
I will describe the technical underpinnings of Carrier, challenges that we’ve faced since its implementation, enhancements planned for the next release of the software, and discuss our plans for releasing this software for others to use '''for free'''.<br />
<br />
<br />
== We Built It. They Came. Now What? ==<br />
<br />
* [[User:evviva|Evviva Weinraub]], Oregon State University, evviva.weinraub@oregonstate.edu<br />
<br />
You have a great idea for something new or useful. You build it, put it out there on GitHub, do a couple of presentations, maybe a press release and BAM, suddenly you’ve created a successful Open Source tool that others are using. Great!<br />
<br />
Fast-forward 3 years. <br />
<br />
You still believe in the product, but you can no longer be solely responsible for taking care of it. Just putting it out there has made it a tool others use, but how do you find a community of folks who believe in the product as much as you do and are willing to commit the time and energy into building, sustaining and moving this project forward. Or just figuring out if you should bother trying?<br />
<br />
In 2006, OSU Libraries built an Interactive Course Assignment system called Library a la Carte – think LibGuides only Open Source. We now find ourselves in just this predicament. <br />
<br />
What can we do as a community to move beyond our build-first-ask-questions-later mentality and embed sustainability into our new and existing ideas and products without moving toward commercialization? I fully expect we’ll end up with more questions than answers, but let’s spend some talking about our predicament and yours and think about how we can come out the other side. <br />
<br />
<br />
== Contextually Rich Collections Without the Risk: Digital Forensics and Automated Data Triage for Digital Collections ==<br />
<br />
* [[User:kamwoods|Kam Woods]], University of North Carolina at Chapel Hill, kamwoods@email.unc.edu<br />
* Cal Lee, University of North Carolina at Chapel Hill, callee -- at -- ils -- unc -- edu<br />
* Matthew Kirschenbaum, University of Maryland, mkirschenbaum@gmail.com<br />
<br />
Digital libraries and archives are increasingly faced with a significant backlog of unprocessed data along with an accelerating stream of incoming material. These data often arrive from donor organizations, institutions, and individuals on hard drives, optical and magnetic disks, flash memory devices, and even complete hardware (traditional desktop computers and mobile systems). <br />
<br />
Information on these devices may be sensitive, obscured by operating system arcana, or require specialized tools and procedures to parse. Furthermore, the sheer volume of materials being handled means that even simple tasks such as providing useful content reports can be impractical (or impossible) in current workflows.<br />
<br />
Many of the tasks currently associated with data triage and analysis can be simplified and performed with improved coverage and accuracy through the use of open source digital forensics tools. In this talk we will discuss recent developments in providing digital librarians and archivists with simple, open source tools to accomplish these tasks. We will discuss tools and methods be tested, developed and packaged as part of the [http://bitcurator.net BitCurator] project. These tools can be used to reduce or eliminate laborious, error-prone tasks in existing workflows and put valuable time back into the hands of digital librarians and archivists -- time better used to identify and tackle complex tasks that *cannot* be solved by software.<br />
<br />
== Finding Movies with FRBR and Facets ==<br />
<br />
* Kelley McGrath, University of Oregon, kelleym@uoregon.edu<br />
<br />
How might the Functional Requirements for Bibliographic Records (FRBR) model and faceted navigation improve access to film and video in libraries? I will describe the design and implementation of a FRBR-inspired prototype discovery interface ([http://blazing-sunset-24.heroku.com/ http://blazing-sunset-24.heroku.com/]) using Solr and Blacklight . This approach demonstrates how FRBR can enable a work-centric view that is focused on the original movie or program while supporting users in selecting an appropriate version.<br />
<br />
The prototype features two sets of facets, which independently address two important information needs: (1) "What kind of movie or program do you want to watch?" (e.g., a 1970s TV sitcom, something directed by Kurosawa, or an early German horror film); (2) "How do you want to watch it? Where do you want to get it from?" (e.g., on Blu-ray, with Spanish subtitles, available at the local public library). This structure enables patrons to narrow, broaden and pivot across facet values instead of limiting them to the tree-structured hierarchy common with existing FRBR applications. <br />
<br />
This type of interface requires controlled data values mapped to FRBR group 1 entities, which in many cases are not available in existing MARC bibliographic records. I will discuss ongoing work using the XC Metadata Services Toolkit ([http://www.extensiblecatalog.org/ http://www.extensiblecatalog.org/]) to extract and normalize data from existing MARC records for videos in order to populate a FRBRized, faceted discovery interface.<br />
<br />
==Escaping the Black Box — Building a Platform to Foster Collaborative Innovation==<br />
<br />
* Karen Coombs, OCLC, coombsk@oclc.org<br />
* Kathryn Harnish, OCLC harnishk@oclc.org<br />
<br />
Exposed Web services offer an unprecedented opportunity for collaborative innovation — that’s one of the hallmarks of Web-based services like Amazon, Google, and Facebook. These environments are popular not only for their native feature sets, but also for the array of community-developed apps that can run in them. The creativity of the development communities that work in these systems brings new value to all types of users.<br />
<br />
What if the library community could realize this same level of collaborative innovation around its systems? What kinds of support would be necessary to transform library systems from “black boxes” to more open, accessible environments in which value is created and multiplied by the user community?<br />
<br />
In this session, we’ll discuss the challenges and opportunities OCLC faced in creating just that kind of environment. The recently-released OCLC “cooperative platform” provides improved access to a wide variety of OCLC’s data and services, allowing library developers and other interested partners to collaborate, innovate, and share new solutions with fellow libraries. We’ll describe the open standards and technologies we’ve put in play in as we:<br />
* exposed robust Web services that provide access to both data and business logic; <br />
* created an architecture for integrating community-built applications in OCLC (and other) products; and <br />
* developed an infrastructure to support community development, collaboration, and app sharing<br />
<br />
Learn how OCLC is helping to open the “black box” -- and give libraries the freedom to become true partners in the evolution of their library systems.<br />
<br />
== Code inheritance; or, The Ghosts of Perls Past ==<br />
<br />
* Jon Gorman, University of Illinois, jtgorman@illinois.ed<br />
<br />
<br />
Any organization has a history not found in its archives or museums. Mysteries exist that origins are lost to the collective institutional knowledge. Despite what has been forgotten by humans, our servers and computers still keep running. Instructions crafted long ago execute like digital ghosts following orders of masters who have long since left.<br />
<br />
The University of Illinois has a fair amount of Perl code created by several different developers. This code includes software that handles our data feeds coming both in and out of campus, reports against our Voyager system, some web applications, and more.<br />
<br />
I'll touch a little on the historical legacy and why Perl is used. From there I'll share some tips, best practices, and some of the mistakes I've made in trying to maintain this code. Most of the advice will transition to any language, but code and libraries discussed will be Perl. The presentation will also touch on some internal debate on whether or not to port parts of our Perl codebase.<br />
<br />
<br />
== Recorded Radio/TV broadcasts streamed for library users ==<br />
<br />
* Kåre Fiedler Christiansen, The State and University Library Denmark, kfc@statsbiblioteket.dk<br />
* Mads Villadsen, The State and University Library Denmark, mv@statsbiblioteket.dk<br />
<br />
"Provide online access to the Radio/TV collection," my boss said. About 500,000<br />
hours of Danish broacast radio and TV. Easy, right? Well, half a year later <br />
we'd done it, but it turned out to involve practically every it employee in the <br />
library and quite a few non-technical people as well.<br />
<br />
Combining our Fedora-based DOMS repository system with our Lucene-based Summa<br />
search system with our WAYF-based single-signon system with an upgrade of our<br />
SAN system for enough speed to deliver the content with an ffmpeg-based <br />
transcoding workflow system with a Wowza-based streaming server, and sprinkling<br />
it all with a nice user-friendly web frontend turned out to be quite a challenge,<br />
but also one of the most engaging experiences for a long time.<br />
<br />
Of course we were immidiately shut down, since the legal details weren't quite<br />
as clear as we thought they were, but take an exclusive preview at <br />
http://developer.statsbiblioteket.dk/kultur/ - username/password: code4lib.<br />
<br />
== NoSQL Bibliographic Records: Implementing a Native FRBR Datastore with Redis ==<br />
* Jeremy Nelson, Colorado College, jeremy.nelson@coloradocollege.edu<br />
<br />
In October, the Library of Congress issued a news release, "A Bibliographic Framework for the Digital Age" outlining a list of requirements for a New Bibliographic Framework Environment. Responding to this challenge, this talk will demonstrate a Redis (http://redis.io) FRBR datastore proof-of-concept that, with a lightweight python-based interface, can meet these requirements. <br />
<br />
Because FRBR is an Entity-Relationship model; it is easily implemented as key-value within the primitive data structures provided by Redis. Redis' flexibility makes it easy to associate arbitrary metadata and vocabularies, like MARC, METS, VRA or MODS, with FRBR entities and inter-operate with legacy and emerging standards and practices like RDA Vocabularies and LinkedData.<br />
<br />
<br />
== Upgrading from Catalog to Discovery Environment: A Consortial Approach ==<br />
<br />
* Spencer Lamm, Swarthmore College, slamm1@swarthmore.edu<br />
* Chelsea Lobdell, Swarthmore College, clobdel1@swarthmore.edu<br />
<br />
<br />
Almost two years ago the Tri-College Consortium of Haverford, Swarthmore, and Bryn Mawr Colleges embarked upon a journey to provide enhanced end-user experience and discoverability with our library applications. Our solution was to implement an integration of ExLibris's Primo Central into Villanova's VuFind for a dual-channel searching experience. We present a case study of the collaborative and technical aspects of our process.<br />
<br />
At a high level we will describe our approach to project management and decision making. We used a multi-tiered structure of working groups with an iterative design-feedback implementation cycle. We will relay lessons learned from our experience: successes, failures, and unexpected hurdles.<br />
<br />
At a lower, technical level we will discuss the vufind search module architecture; the workflow of creating a new search channel; a Primo API parser; and the data structures of the Primo API response and the Primo SearchObject. Time permitting, we will also outline how we modified VuFind's Innovative driver to work with our ILS.<br />
<br />
<br />
== Improving geospatial data access for researchers and students ==<br />
<br />
* Dileshni Jayasinghe, Scholars Portal, University of Toronto, d.jayasinghe@utoronto.ca<br />
* Sepehr Mavedati, Scholars Portal, University of Toronto, sepehr.mavedati@utoronto.ca<br />
<br />
Scholars GeoPortal (http://geo.scholarsportal.info) was created as a platform for online delivery of geospatial data resources to the Ontario Council of University Libraries community. Prior to the start of this project, each institution was storing data locally, and had its own practice for distributing datasets to users. This ranged from home grown online data delivery systems to burning data on to DVDs for each individual request. Most institutions had limited resources and expertise to create and maintain a sophisticated delivery system on their own. Led by OCUL Map, GIS librarians, staff at Scholars Portal in partnership with the Government of Ontario, the GeoPortal project began in 2009.<br />
<br />
Our talk will focus on the design and architecture of Scholars Portal's solution to support maps and geospatial data, and how we distribute these data collections to our users. <br />
<br />
The system consists of 4 main components: metadata management system, map server, spatial database, and the web application.<br />
<br />
*Metadata Management: customized metadata editor with data hosted in MarkLogic, providing text and spatial queries<br />
*Map Server: ArcGIS Server<br />
*Spatial database: MS SQL Server with spatial extension<br />
*Web application: Javascript web application using Dojo and Esri’s Javascript API<br />
<br />
For other code4libbers who are interested in a similar system, we will also discuss the open source alternatives for each component (GeoNetwork, MapServer, etc.), and challenges and limitations we faced trying to use some of these tools. We'd also like to pick your brains on how we can make this application better. What can we do differently?<br />
<br />
== LibX 2.0 ==<br />
<br />
* Godmar Back, Virginia Tech, godmar@gmail.com<br />
<br />
We would like to provide the Code4Lib community with an update on what we've accomplished with LibX (which we last presented in 2009) - where we've gone, what our users are thinking, and how both its technology and its adapter community can be included in the code4lib world.<br />
<br />
== Introducing the DuraSpace Incubator ==<br />
<br />
* Jonathan Markow, DuraSpace, jjmarkow@duraspace.org<br />
<br />
DuraSpace is planning to launch a new incubation program for the benefit of open source projects that wish to become part of our organization, in the interest of helping them to become sustainable, community-driven projects and supporting them afterwards with umbrella services that help them to thrive. From time to time DuraSpace becomes aware of open source software projects in the preservation, archiving, or repository space that are in search of a community “home”. The motivation might be that the project is simply trying to attract more developers, that it would like to develop a more robust community of users and service providers, that its current organizational sponsorship is in question, or that it would like to take advantage of an existing and compatible organization's best practices and administrative infrastructure rather than create a new one of its own. DuraSpace is now prepared to leverage its resources, experience, and reputation in the community to help these projects become, or continue to be, successful. Projects emerging from incubation will become officially recognized as DuraSpace projects. This briefing presents highlights of the DuraSpace Incubator and invites questions and feedback from participants.<br />
<br />
<br />
== In-browser data storage and me ==<br />
<br />
* Jason Casden, North Carolina State University Libraries, jason_casden@ncsu.edu<br />
<br />
When it comes to storing data in web browsers on a semi-persistent basis, there are several partially-adopted, semi-deprecated, product-specific, or even universally accepted options. These include models such as key-value stores, relational databases, and object stores. I will present some of these options and discuss possible applications of these technologies in library services. In addition to quoting heavily from Mark Pilgrim's excellent chapter on this topic, I will weave in my own experience utilizing in-browser data storage in an iPad-based data collection tool to successfully improve performance and data stability while reducing network dependence. See also: HTML5.<br />
<br />
<br />
<br />
== Coding for the past, archiving for the future … and the Salman Rushdie Papers ==<br />
<br />
* Peter Hornsby, Emory University Libraries, phornsb@emory.edu<br />
<br />
Cultural heritage production is moving to the digital medium and libraries use of repository solutions such as Fedora Commons and DSpace are a solid response to this change. But how do we go from, for instance a selection of 90's computing technology to a collection of digital objects ready for ingest into your institution's local repository? Once you have ingested your digital objects how are you going to provide access to these resources? The arrival of the Salman Rushdie Papers, which contain 10 years of Sir Salman Rushdie's digital life, gave Emory University Libraries the opportunity to explore these questions. I would like to to talk about the approach the Emory University Libraries adopted, what we learned and the coding challenges that remain.<br />
<br />
== Indexing big data with Tika, Solr & map-reduce ==<br />
<br />
The Web Archiving Service at the California Digital Library has<br />
crawled a large amount of data, in every format found on the web: 30<br />
TB, comprising about 600 million fetched URLs. In this talk we will<br />
discuss how we parsed this data using Tika and map-reduce, and how we<br />
indexed this data with Solr, tweaked the relevance ranking, and were<br />
able to provide our users with a better search experience.<br />
<br />
* Scott Fisher, California Digital Library, scott.fisher AT ucop BORK edu<br />
* Erik Hetzner, California Digital Library, erik.hetzner AT ucop BORK edu<br />
<br />
[[Category: Code4Lib2012]]</div>Egh