Southeast 2019

2019-04-18T14:25:21Z

Kbeswick: add link to 2019 code4lib se program

Southeast 2019 Program

2019-04-18T14:24:55Z

Kbeswick: publish code4libse 2019 program

*'''Planning Committee:''' Kevin Beswick, Bret Davidson, Mike Kastellec, Mia Partlow, Hannah Rainey

== 15 minute talks ==

=== Dead Simple Catalog Indexer: Using Solr for better MARC searching ===
''''' Dennis Christman (Duke University) ''''' 
Are you ever frustrated searching MARC records in your ILS? Do you ever have complex searches or updates that are difficult or even impossible for your system to handle? The Dead Simple Catalog Indexer is an open source tool developed by NCSU Libraries that takes MARC records and puts them into Solr for you. Duke University Libraries (DUL) Technical Services has recently implemented this tool, opening up exciting new workflows for working with our data. Many of the complex searches we are now able to do would have previously required server level access, effectively creating a bottleneck where our projects had to work on another department’s timeline. Using this tool has helped to alleviate this bottleneck, allowing us to work through projects more quickly and freeing up the time of our colleagues. This session will briefly describe the tool and its implementation process, and then go over several projects where we utilized the tool. If you have ever needed to know every record had a certain combination of LDR position 06 and 337 values and haven’t been able to, this might be the tool for you.
 

=== Asserting for Success: Leveraging TravisCI, Bash, and Unit Tests to Ensure Metadata Transformations Do What We Expect ===
''''' Mark Baggett (University of Tennessee) ''''' 
Serving as a Digital Public Library of America (DPLA) service hub since 2015, the Digital Library of Tennessee uses Repox to aggregate our state’s cultural heritage materials and transforms each partner institution’s unique metadata mappings (DC, QDC, XOAI, MODS) to a shared format using XSLT. Over the years, testing metadata transforms before deployment to production has been time-consuming and frustrating for both the transform’s writer and its reviewer. It has also occasionally led to frantic moments before a scheduled ingest to repair a broken transform that went unnoticed during the review process. In this talk, I will go over our recent adoption of unit tests for this type of quality control, discuss what it's helped solve, and demonstrate how automated testing is not just for developers, but can help solve the work of librarians as well.
 

=== Metadata Cartography: MAPping metadata for a repository migration ===
''''' Anna Goslen, Rebekah Kati (University of North Carolina at Chapel Hill) ''''' 
The Carolina Digital Repository (CDR) at UNC-Chapel Hill will migrate from custom Fedora to Samvera Hyrax. As part of the content remediation process and preparation for storage and display in the new system, we need to migrate our MODS metadata to RDF. In this presentation, we will explain our repository and metadata use cases, describe the Metadata Application Profile creation process and offer advice and best practices for attendees who are contemplating their own Fedora to Hyrax content migration. We will discuss how legacy content, desired features, and system limitations each informed our decision making.
 

=== Building a Digital Public Library for Afghanistan ===
''''' Dunyau Maqsoudi-Moreno (Academy of Art University) ''''' 
Countries lacking internet connectivity, computer hardware, and equipment, while having limited capacities in terms of digital support, have limited access to information, which is crucial to increasing literacy ratings in developing countries. Hence, it is essential for a developing country like Afghanistan to undertake a digital initiative aimed at establishing a digital public library, which will not only curb its current illiteracy rations, but also offer greater potential for the country’s current and future youth. This is especially relevant for younger generation of females in Afghanistan, where due to societal norms, women in provinces and even in some city centers are prevented from going outside of their home to seek education. A digital library may be the medium that liberates Afghan women by bringing education to their homes without compromising their safety. This paper explores the potential benefits of establishing a digital public library for Afghanistan, and its findings will provide relevant information to information professionals with a passion for providing access to countries that do not have the luxury or support to do so. It includes four relevant case studies (two in-country and two from other developing countries), as well as a set of recommendations for the successful establishment of a digital library in Afghanistan.
 

=== Annotation of IIIF resources ===
''''' Niqui O'Neill (NC State University) ''''' 
This presentation will discuss and demo a new open source JavaScript library for presenting annotations of IIIF resources. The library allows for the use of annotations for display and storytelling purposes. This rich display of annotations demonstrates the reuse value of annotations and provides the opportunity for new forms of scholarly output. This presentation will give an introduction to annotations, demonstrate the low barrier of entry to using the library, challenges around creating and using annotations of IIIF resources from multiple data models, potential use cases, and future development opportunities. Additionally, this talk will also touch on issues of annotations as scholarly output and demonstrate a local annotation server to help mediate some of the obstacles in creating annotations.
 

=== Getting Serious About Open Access Advocacy: Ten Practical Repository UI and Metadata Revisions to Help Your Library Champion the Cause ===
''''' Maggie Dickson, Sean Aery (Duke University) ''''' 
As the 2010s draw to a close, open access to scholarly work has become an integral theme throughout many libraries’ strategic plans, and Duke University Libraries is no exception. Ushering in this new era of openness will require libraries to take concerted action to improve the way their institutions' open scholarly publications are represented once collected in the platforms they support for curation, discovery, and access. 

In a world where the open access copy of an article coexists with—and competes with—the published (often paywalled) version, how can libraries add value to the OA copy beyond merely making it accessible? How can we increase its impact? What can we do using our local metadata that can’t be done at scale by a publisher? And in the face of competing priorities, constrained resources, and a swiftly moving carousel of technology platforms, how can we make progress toward these ends without breaking the bank? 

Over the past year, Duke Libraries decided to embrace—rather than replace—an aging DSpace platform for its open access publications, updating the core software from version 1.7 to 6.2. With renewed focus on metadata architecture and targeted user interface enhancements, Duke’s new DSpace system puts a modern spin on the software, and dares to break outside of the box of what an OA repository traditionally does. 

We reconsidered how researchers can be presented alongside their research, displaying an author-provided photo and bio on item pages, and linking out to profiles in ORCID and VIVO using lightweight name string & ID pairing. We built copyable citations that vary by type, and took care to encourage citing the published version of the article where possible. We also illuminated usage, attention, and collection stats throughout the site. 

Metadata has been the true key to unlocking the potential of these materials. Through metadata auditing, remodeling, and remediation, we built a solid foundation for developing a platform worthy of the research it holds. These changes have in effect turned a traditionally utilitarian platform into one that can appeal on an emotional level, and have helped to highlight the distinctive character of the Duke research community. 

Come hear about Duke's approaches to addressing these challenges, and the tradeoffs and pitfalls encountered. No matter what platform your library's open access publications call home, you'll learn about ten ideas for practical metadata and interface changes you can make to help raise the profile of your institution's scholarly works.
 

=== Born-Digital Workflows at the Rose Library ===
''''' Brenna Edwards (Emory University) ''''' 
Creating workflows for preserving born-digital materials is a challenge, as technology and tools in the field are constantly being introduced or updated. At the Rose Manuscripts, Archives, and Rare Book Library at Emory University, the BitCurator environment has been adapted to create more efficient workflows for preserving born-digital media. While BitCurator has a wide menu of tools available, this talk will focus on a select few found to be the most useful when working with newly accessioned born-digital materials. These include FSLint,Bagger, BulkExtractor, Brunnhilde, and a toolset called CCA (Canadian Center for Architecture) Tools. Through experimentation and documentation, these tools have improved the workflow for both accessioning and processing born-digital media. This, in turn, makes the born-digital holdings at the Rose more accessible to our researchers.
 

=== An evolving Hyrax: two approaches to adapting open-source digital repository software for mediated data deposit ===
''''' Moira Downey, Jocelyn Triplett, Jennifer Darragh (Duke University) ''''' 
The Samvera open source software community's Hyrax framework provides a user interface for digital repositories that incorporates a robust and growing set of features centered around the archiving, publishing, and sharing of digital content. Hyrax natively enables upload of files through direct user deposit, proxy deposit, and mediated deposit. This range of options represents a variety of possible workflows. However, none of them explicitly facilitate a workflow that allows for a review of the files to ensure their quality prior to ingest into the system. Over the past year, Duke University Libraries have adapted the Hyrax codebase to develop two data repositories with distinct approaches to pre-publication quality control--one human-centered and one system-based. 

In 2017, Duke University Libraries introduced a data curation and publication program aimed at helping faculty and other campus scholars make their research data findable, accessible, interoperable and reusable (FAIR) [1]. The curation workflow established in support of this program is heavily reliant on staff intervention and involves a thorough review of a depositor's data to ensure that the dataset meets those FAIR standards. In the same spirit of openness that inspired the curation program, the libraries chose to build a local digital repository for researcher data using the Hyrax framework. The development team acknowledged that the software would require a number of customizations to allow the kind of human level audit that the program's curatorial procedures required. The end result--Duke's Research Data Repository [2]--is a system that allows researchers to submit files and accompanying metadata, while affording curatorial staff the opportunity to examine, rearrange, and potentially transform the files prior to ingest. 

Also at Duke, the team behind MorphoSource [3], a publicly accessible web digital repository for 3D scans of biological specimens, saw in Hyrax a solid foundation on which to redevelop and expand the scope of the site to include museum and cultural heritage objects. The current MorphoSource site has 62 thousand files from over 900 contributors, and is experiencing exponential growth. In order to accommodate this volume of deposits on the new platform while ensuring that the user-submitted data and metadata are interoperable and support preservation activities as well as discovery and access, the MorphoSource team has undertaken several customizations to the Hyrax interface to guide users and validate files and metadata throughout the deposit process. 

This presentation will look a closer look at how the two teams at Duke have bent the Hyrax codebase to build research data repositories using different workflows for pre-publication review and quality control. We will briefly trace the history of both archives, and explore the various ways in which each application implements the needs of its respective program. 

[1] https://www.go-fair.org/fair-principles/ 
[2] https://research.repository.duke.edu/ 
[3] https://www.morphosource.org
 

=== Embracing the Mess: An Approach to Utilizing All Potential Data Sources ===
''''' Luke Aeschleman (NC State University) ''''' 
NC State University Libraries’ Citation Index is a central hub for researcher citation data, sourcing metadata from Web of Science, ORCID, Crossref, and faculty Curriculum Vitaes. One of the major accomplishments of the application is its ability to “intertwine” citation metadata into an enhanced, cohesive record. As opposed to standard ETL workflows (in which all data sources would be standardized, deduplicated, and stored), the Citation Index benefits from incomplete or duplicate records, as each source represents a single part of the larger whole. Some sources are better for author affiliation data and some are better for external identifiers. Two sources might be equally “as good” at supplying metadata but both lack 100% coverage. To ensure the best possible final record, the Citation Index “embraces the mess.” This approach allows the application to be more resilient to dirty data and more flexible in adding new data sources (and even more mess!). 

This talk will use the Citation Index as a real-life example of how to approach multiple, open source data sources and the challenges of working in an environment that can be fraught with metadata inconsistencies. The talk will outline the benefits of “embracing the mess” as opposed to focusing on the creation of impeccably clean records.
 

=== Improving Library Workflows with Serverless Technologies ===
''''' Karen Coombs (OCLC) ''''' 
This session will provide an overview of the concepts of serverless and discuss how utilizing serverless technologies can improve library workflows, potentially reduce costs and facilitate innovation. The session will review several use cases related to for metadata maintenance, analytics and discovery; and examine using tools such as AWS Lambda, Step Functions, S3 and ElasticSearch.
 

=== Wrangling Images at the Digitization Rodeo ===
''''' Jeremy D. Moore (University of Tennessee) ''''' 
This presentation looks at digital image post-processing and quality control as data wrangling problems that can be solved by leveraging data science and developer tools, such as conda, Jupyter Notebooks, and GitHub. Based on my experience with millions of images in over a decade of managing digitization labs, I will share exploratory methods that fall somewhere between manually processing images in Adobe Photoshop and a fully-automated BASH script. Due to the unique issues inherent in physical item digitization performed by an ever-changing cast of student digital imaging technicians from a wide variety of backgrounds, this is less of a workflow and more a mentality lending itself to creative problem-solving in a manner that is flexible, scalable, and teachable to the non-developer. Attendees will be shown examples of past projects and hopefully learn new techniques for tackling old problems with Python.
 

=== Longleaf: a repository-independent command-line utility for applying digital preservation processes to files ===
''''' Benjamin Pennell, Jason Casden (University of North Carolina at Chapel Hill) ''''' 
As our digital collections infrastructure has grown over the past 20 years, we’ve found it difficult to apply digital preservation plans consistently across system-defined content boundaries. Our institution has developed longleaf, a new portable, command-line, repository-agnostic, rules-based tool for monitoring, replicating, and applying preservation processes to files. We chose to develop this tool in order to address several ongoing technological preservation challenges that we feel are also common at other institutions: 

* Preservation activities being applied to files based on system affiliation (i.e. repository platform or lack thereof) rather than the needs of the content.
* Difficulty maintaining an ideal schedule of fixity checks as the sizes of our collections grow.
* Physical and computational costs to servers and storage devices imposed by ongoing cryptographic checksum algorithms.
* Difficulty gradually introducing cloud storage services into our replication strategy for vulnerable files.

We argue that the complexity of digital preservation technologies and the manner in which they are coupled with repository management systems contribute significantly to these problems. In an attempt to address these issues, we have designed longleaf according to the principles of high “software availability” (Davidson & Casden, 2016) that prioritize ease of use by a broad set of users in a variety of environments. To that end, longleaf is an open source Unix-style utility that will run on any modern Linux operating system with only a ruby interpreter. It is designed as a flexible tool that can be applied to any content storage system with a file system: longleaf requires no repository, no external database, and no storage system other than the file system. It can be run completely from the command line or triggered by arbitrary external systems (e.g. initiated on file ingest). We will be applying longleaf to files managed entirely on shared drives, files managed by Hyrax and our in-house Fedora-based repositories, as well as digitization masters managed by CONTENTdm. 

Longleaf’s modular architecture and flexible configuration system will allow this tool to be used as a platform for evaluating and implementing varied preservation activities across subsets of larger collections. We are increasing coverage of ongoing and transactional fixity checks by implementing both typical computationally expensive cryptographic checksums alongside far more scaleable non-cryptographic checksums and filesystem checks based on different schedules, events, and collection affiliations. We will integrate storage endpoints with different access costs (e.g. Amazon S3 Glacier and magnetic tape data storage) by setting appropriate replication and verification (i.e. fixity checking) schedules and techniques based on characteristics of both the source and destination locations. This approach can allow the fairly straightforward implementation of actions based on levels of digital preservation need regardless of repository system constraints. 

In this session, we will present the longleaf system design and demonstrate the ways that we are using longleaf to consistently implement digital preservation plans as defined by our institution’s digital preservation specialists. 
 

Davidson, B., & Casden, J. (2016). Beyond open source. Code4Lib Journal, Issue 31. Retrieved from http://journal.code4lib.org/articles/11148
 

=== Drupal 7 to Drupal 8: Our Journey ===
''''' Erik Olson, Meredith Wynn (NC State University) ''''' 
Drupal 8 has some sorely needed improvements and many nice upgrades from Drupal 7. New tools like Symfony, Twig, and Composer alone make it worth the upgrade. Because of these new tools there are substantial changes in the way Drupal 8 is built and manages its data model. 

Upgrading a Drupal 7 site to Drupal 8 is, unfortunately, not as simple as running a script. Templates and custom modules will need to be rebuilt and all of your content will have to be migrated to a new database model. If this sounds daunting, well that’s because it is. 

The NC State University Libraries website had 25,000 nodes, 30 content types, 10 custom modules, 100+ custom views, and over 150 templates. I am very proud to say, without any evidence to back up this claim, it was the single largest website to attempt a Drupal 8 migration. The upgrade was very difficult, but we did it and we are glad we did. 

In our talk we will discuss the right and wrong ways to go about a migration, the best tools we found, and tips we wish we knew before we began our migration. 

Topics include:
* Benefits of Drupal’s “Migrate” module and what it lacks
* How to migrate views
* How to structure your yaml files for your custom content types
* Rewriting templates in Twig
 

=== Grant-funded open source software: lessons learned from the initial release ===
''''' Sharon Luong, Erica Titkemeyer (University of North Carolina at Chapel Hill) ''''' 
Jitterbug is a web application funded as part of an Andrew W. Mellon Foundation grant, supporting large-scale description, digitization, preservation, and access of archival audiovisual recordings across Wilson Special Collections Library at the University of North Carolina at Chapel Hill’s University Libraries. Launched in early 2017, Jitterbug has been successful in helping staff describe over 40,000 items and preserve and provide access to over 40% of the total archival recordings within the Southern Folklife Collection. 

Solving a number of challenges for audiovisual collections and institutions involved with AV preservation, including the need for customized fields based on formats and batch data importing for various points in the digitization workflow, it has been a hope that Jitterbug could find adoption among UNC’s peer institutions. However, many practical and technical hurdles remain in the way of Jitterbug use outside of Wilson Library. Specifically, this presentation will highlight the difficulties in promoting Jitterbug, from limitations experienced in grant-funded open source software development, to the discovery of local application dependencies that may keep it from being truly reusable by other institutions. 

Jitterbug’s Product Owner, Erica Titkemeyer, will share details on the initial development and use of the application. They will discuss, in hindsight, potential provisions to the grant proposal in order to allow for conceptualization of a simpler, more generalized version of Jitterbug to better meet the needs of a wider constituency. 

Jitterbug’s developer, Sharon Luong, will talk about technical measures to enable and improve the re-usability of initial open source software releases. These include simplifying application dependencies, decreasing setup effort, and increasing documentation. They will also discuss prioritizing these and other retroactive improvements against new requested features.
 

== 5 minute lightning talks ==

=== Raspberry PioT: Teaching the Internet of Things with the Raspberry Pi ===
''''' Colin Nickels (NC State University) ''''' 
The Internet of Things is a complicated topic; it's an umbrella term that encompasses many technologies; it's a messy collection of gadgets and gizmos; it's a buzzword that conveys little solid meaning. Making sense of this is hard. This complexity makes IoT a particularly difficult topic to teach in a hands-on Makerspace workshop. 

Over the years of struggling with this topic, we have adopted multiple different platforms, technologies and learning outcomes. Starting with Arduino and moving to Raspberry Pi, we have iterated on our workshop to make it more approachable and provide more time building an Internet of Things Thing. 

This talk highlights our efforts to tackle IoT as a workshop in our library. I will discuss the advantages of the Pi as well as lessons learned through years of struggling to teach this topic.
 

=== Using Python’s Pandas Data Analysis Library for Digital Collections Assessment ===
''''' Julia Gootzeit, Morgan McKeehan (University of North Carolina at Chapel Hill) ''''' 
Assessing the metadata and content of large-scale digital collections necessitates careful analysis of the very large data sets about collections that accrue within digital asset management systems over time. Collections data sets can be messy and complicated to work with, however, posing challenges for comprehensive assessment efforts. 

At our institution, we are currently conducting an assessment of metadata and content for our digital collections in preparation for migrating them out of CONTENTdm and into a new system. In this lightning talk, we will discuss how we used the open-source data analysis library pandas for the python programming language, to address some of the collections assessment challenges we have encountered. We have found pandas’ fine-grained and well-documented data analysis tools to be easy to work with and flexible for our needs in assessing large volumes of tabular metadata that well exceed the size limitations of commonly used spreadsheet software. 

In our talk, we will briefly outline the pandas modules we found useful for working with collections data, and will show how we used them to perform specific assessment tasks such as:
* merging data sets from various export sources according to specific parameters
* running calculations across combined data sets to create collections snapshots for attributes such as image quality of content files

We will also provide recommendations and links for the sources we have found most helpful for learning pandas.
 

=== Heroku to the Rescue! ===
''''' Meredith L. Hale (University of Tennessee) ''''' 
What are your options when you need to host an application and don’t have access to a server? In this lightning talk, I’ll provide snapshots of two cases studies that answer this question using Heroku with no resulting costs. Heroku is a cloud-based Platform as a Service (PaaS) that can be capitalized upon for a variety of projects. In one instance, Heroku is being used to minimize the technical knowledge staff need to use a Library of Congress reconciliation service and the time needed to install the requirements on individual computers. Hosting the app on Heroku makes it so that staff and students do not need to use the command line to run the reconciliation program in OpenRefine. In the second instance, Heroku is being used to host a Twitterbot that promotes the library’s digital collections through a daily image post with associated metadata on the Twitter application. Running a program periodically can be achieved in Heroku by using either apscheduler or the Heroku scheduler add-on. Once fired by Heroku, this program uses OAI-PMH to randomly select a digital collections item link and posts the associated image and title online using the affordances of OpenGraph tags and the Twitter API. Heroku proved to be a useful and approachable tool in these instances and provided me with my first experience using a PaaS. Through sharing my work with Heroku, I hope that attendees will use the platform to solve new problems of their own.
 

=== Integrating the Cantaloupe IIIF Server into Hyrax/Samvera ===
''''' Kevin S. Clarke (UCLA) ''''' 
Hyrax comes with RIIIF support, but it's easy to configure the Cantaloupe IIIF server to work with your Hyrax/Samvera installation. I propose to show how to accomplish this, and then to talk briefly about how we're planning to change the way that Hyrax and Cantaloupe interact. We envision using JP2 instead of TIFF images as the IIIF source image. We also want to further decouple Cantaloupe and Hyrax (which will involve storing manifests outside of Hyrax, as well as some other changes). I'll talk about the code we're writing to make this possible.
 

=== New Roots: Developing a Bilingual Omeka site ===
''''' Emily Brassell (University of North Carolina at Chapel Hill) ''''' 
In this lightning talk, I’ll give an overview of New Roots: Voices from Carolina del Norte!, a digital archive containing oral histories of Latin American migrants in North Carolina and the experiences of North Carolinians who have worked for the integration of new settlers into this southern state. 

Built on the Omeka platform and funded by the National Endowment for the Humanities, the project is a collaboration of the Latino Migration Project, the Southern Oral History Program, and University of North Carolina at Chapel Hill Libraries. There were two major considerations in developing the site: first, since Spanish speaking researchers and the Latino community in NC were important audiences, it was crucial to create a bilingual site. Secondly, to avoid the tedium and potential errors of duplicate data entry, we needed to sync data from our authoritative source (CONTENTdm) to Omeka. 

To create a bilingual site, we forked the Omeka Multilanguage plugin and customized it heavily. Our solution also depends on a custom theme, a metadata schema with English and Spanish translations of most fields, and English and Spanish translations of Omeka “SimplePages.” 

As for syncing data, we created an endpoint on our CONTENTdm server with XML data created according to the ResourceSync standard. We then created an Omeka plugin making heavy use of resync-php which translates the CONTENTdm data into fields usable by New Roots. 

The development process was enriched by working closely with a faculty member. In weekly meetings we refined requirements and discussed design decisions, and the project benefited greatly from her domain knowledge. 

In the talk, I’ll describe each of these aspects in more detail (focusing on the bilingual functionality) and will briefly highlight the site’s other features with a series of screenshots. Finally, I’ll discuss lessons learned and future aspirations for the site.
 

=== Replacing aging ipads with low cost DIY solutions ===
''''' Jason Fleming (University of North Carolina Wilmington) ''''' 
We have been using Raspberry Pis for rotating displays in the library for about 2 years now with success, so when it was time to replace our aging Ipad lookup stations we decided to explore the option of using a touch screen display coupled with a raspberry pi. We will describe the solution we came up with and the problems finding a case to fit, and how we ended up retrofitting the existing cases with new 3D printed parts.
 

=== Scaling Up R Instruction using RStudio Cloud + Zoom ===
''''' Alison Blaine (NC State University) ''''' 
In this lightning talk, I will discuss my experiences using cloud computing software, specifically RStudio Cloud, and webinar technology (Zoom) to scale up teaching R workshops at NC State to accomodate both in-person and online participants. This talk will focus on my 9-week R for Data Science workshop series that I'm currently teaching (Feb - April 2019), in which approximately 50 participants attend weekly hands-on coding sessions that are synchronous in-person at Hunt Library and online. The series is also being recorded and will be available as a self-directed non-credit course via the Moodle learning management software at NC State. My goal for the talk is to offer thoughts about how others might be able to successfully use these and similar technologies (such as Google Colab) to scale up data science instruction.
 

=== Building Bridges: The Triangle Digital Humanities Network as a Model for Navigating Inter-Institutional Collaboration ===
''''' Nathan Kelber, Claire Cahoon (University of North Carolina at Chapel Hill) ''''' 
Libraries across the country are striving to find the right people, knowledge, and resources to create and sustain successful digital projects, but often struggle to break out of silos and connect with outside sources. Large R1 institutions grapple with keeping connected while small institutions strive to get access to needed resources. We all benefit from collaborating across institutions, documenting our strengths, and building the capacities of our staffs. These are the broad goals of the Triangle Digital Humanities Network (TDHN), which aims to create a community of practice for digital humanities scholars, teachers, and practitioners from institutions of all kinds within the North Carolina research triangle. Our talk will discuss the benefits and challenges of developing such an organization, with a focus on inter-institutional collaboration. 

Tackling these issues requires a variety of tactics. At TDHN, we have focused on these support methods:
* Inter-institutional communication channels (email list, shared calendar)
* Census data of local people, projects, organizations, workshops, spaces, communities, and repositories
* A Triangle Digital Humanities Institute for training scholars, especially for incorporating new scholars and those at under-represented institutions

The challenge of any such community is to bring together people of diverse backgrounds, especially populations and institutions that are historically underrepresented in technology. We will address the challenges our team faces concerning decentralizing leadership and contribution as well as finding and including smaller institutions. Using TDHN as a case study, we will discuss the value of creating an interdisciplinary, inter-institutional, virtual community and how to take the first steps towards starting one in your area.
 

Back to [[Southeast 2019]]

Back to [[Southeast]]

2018-11-15T20:27:25Z

Kbeswick: /* Introduction */

Southeast

2018-11-15T19:45:51Z

Kbeswick: /* Summer 2019: Code4Lib Southeast @ NCSU */

== Mailing List ==
There is a separate Code4Lib-SE (Southeast) mailing list for the planning of Southeast region Code4Lib meetups. Feel free to post Code4Lib-SE topics to the main Code4Lib mailing list as well (for instance, announcing new meetups) but this Code4Lib-SE specific mailing list will make sure we don't drown the main mailing list with other sorts of Code4Lib-SE administriva.

https://groups.google.com/forum/#!forum/code4lib-se

== Upcoming Events ==
=== Summer 2019: Code4Lib Southeast @ North Carolina State University ===

Code4Lib Southeast 2019 will be hosted at the James B. Hunt Jr. Library at North Carolina State University in Raleigh, NC on Friday, May 31st, 2019.

For more details, visit the [[Southeast 2019|Code4Lib Southeast 2019 page]]

== Past Events ==

=== Summer 2018: Code4Lib Southeast, July 27, 2018 ===
Code4Lib [[Southeast 2018]] was hosted by the Atlanta University Center Robert W. Woodruff Library in Atlanta, Georgia on July 27, 2018.

Session slides, videos, tweets and more are available on the '''[[Southeast 2018 Schedule]]''' page.

=== Spring 2017: Code4Lib Southeast at Emory University Library, April 21, 2017 ===

Information about the event can be found at this link: '''[[Southeast_2017|Code4LibSE 2017 Emory Meeting]]'''

We currently have documentation from the Spring 2017 event about how the conference was planned. This document is available to anyone and is available [https://wiki.code4lib.org/images/1/19/HowToThrowA1DayConference.pdf here].

* (Summer - Fall 2015 will be in Greenville, SC) - Cancelled
* Winter-Spring 2015 will be at Tulane, New Orleans, Louisiana (primary contact: Phil Suda: phil.suda@gmail.com) - Cancelled

=== Spring 2015: Code4LibSE Datathon ===

'''May 1, 1-5 PM''' 
'''Room 128, Hodges Library, University of Tennessee Knoxville''' 
'''Registration page: http://goo.gl/forms/x9u11MCmJ1''' 

All are welcome to an afternoon datathon, put together as part of Code4LibSouthest. The event is free and open to all, although we do ask for you to register using this form so we can have a head count.

The first 2 hours will involve skillshares and workshops around data retrieval/munging tools, scripts, and workflows. Let us know if you have a skill that you would like to help others learn - some topics include OpenRefine/LODRefine, Google Docs + Scripting, writing XSLT, working with library data in python, open source ontology editors, working with open data APIs, understanding the RDF data model, etc. We will add confirmed topics for the skillshare part of the event agenda as they are confirmed on our Google Groups page - see https://groups.google.com/forum/#!topic/code4lib-se/. Please know that all data skills are welcome!

Skills to be Shared:
* Metadata munging with XQuery, including roundtripping MARC to/from other XML metadata formats using https://github.com/ksclarke/freelib-marc4j-exist -- Kevin Clarke
* Perl + MARC/RDF munging -- Galen Charlton
* WOS, sci2 + network visualizations -- Cody Behles
* Depending on time: DPLA API, LODRefine (Linked Open Data Refine) & Open Authorities Reconciliation -- Christina Harlow

We'll then take a coffee and food break as needed. Some coffee, tea and local treats from Magpie's Bakery will be provided.

The second 2 hours will consist of breakout sessions where groups of folks can work with datasets using the tools/skills picked up. We invite people to bring their own datasets that need any kind of work - encoding issues, normalizing headings, mapping to other formats, pulling in URIs. If you don't bring your own data, we'll use datasets from UTK and the DPLA that need work normalizing and mapping names/subjects of regional interest. Attendees are invited to sit and learn or work on their own data - whatever you feel most comfortable with doing.

Please register below, and let us know if you are 1. able to share skills or 2. will be bringing your own data. Neither of these are required for attendance.

Questions or issues? Email Christina at charlow2@utk.edu Travel information is being sent directly to those registered. Ask Christina if you didn't receive these.

Southeast

2018-11-15T19:45:14Z

Kbeswick: /* Summer 2019: Code4Lib Southeast @ NCSU */

== Mailing List ==
There is a separate Code4Lib-SE (Southeast) mailing list for the planning of Southeast region Code4Lib meetups. Feel free to post Code4Lib-SE topics to the main Code4Lib mailing list as well (for instance, announcing new meetups) but this Code4Lib-SE specific mailing list will make sure we don't drown the main mailing list with other sorts of Code4Lib-SE administriva.

https://groups.google.com/forum/#!forum/code4lib-se

== Upcoming Events ==
=== Summer 2019: Code4Lib Southeast @ NCSU ===

Code4Lib Southeast 2019 will be hosted at the James B. Hunt Jr. Library at North Carolina State University in Raleigh, NC on Friday, May 31st, 2019.

For more details, visit the [[Southeast 2019|Code4Lib Southeast 2019 page]]

== Past Events ==

=== Summer 2018: Code4Lib Southeast, July 27, 2018 ===
Code4Lib [[Southeast 2018]] was hosted by the Atlanta University Center Robert W. Woodruff Library in Atlanta, Georgia on July 27, 2018.

Session slides, videos, tweets and more are available on the '''[[Southeast 2018 Schedule]]''' page.

=== Spring 2017: Code4Lib Southeast at Emory University Library, April 21, 2017 ===

Information about the event can be found at this link: '''[[Southeast_2017|Code4LibSE 2017 Emory Meeting]]'''

We currently have documentation from the Spring 2017 event about how the conference was planned. This document is available to anyone and is available [https://wiki.code4lib.org/images/1/19/HowToThrowA1DayConference.pdf here].

* (Summer - Fall 2015 will be in Greenville, SC) - Cancelled
* Winter-Spring 2015 will be at Tulane, New Orleans, Louisiana (primary contact: Phil Suda: phil.suda@gmail.com) - Cancelled

=== Spring 2015: Code4LibSE Datathon ===

'''May 1, 1-5 PM''' 
'''Room 128, Hodges Library, University of Tennessee Knoxville''' 
'''Registration page: http://goo.gl/forms/x9u11MCmJ1''' 

All are welcome to an afternoon datathon, put together as part of Code4LibSouthest. The event is free and open to all, although we do ask for you to register using this form so we can have a head count.

The first 2 hours will involve skillshares and workshops around data retrieval/munging tools, scripts, and workflows. Let us know if you have a skill that you would like to help others learn - some topics include OpenRefine/LODRefine, Google Docs + Scripting, writing XSLT, working with library data in python, open source ontology editors, working with open data APIs, understanding the RDF data model, etc. We will add confirmed topics for the skillshare part of the event agenda as they are confirmed on our Google Groups page - see https://groups.google.com/forum/#!topic/code4lib-se/. Please know that all data skills are welcome!

Skills to be Shared:
* Metadata munging with XQuery, including roundtripping MARC to/from other XML metadata formats using https://github.com/ksclarke/freelib-marc4j-exist -- Kevin Clarke
* Perl + MARC/RDF munging -- Galen Charlton
* WOS, sci2 + network visualizations -- Cody Behles
* Depending on time: DPLA API, LODRefine (Linked Open Data Refine) & Open Authorities Reconciliation -- Christina Harlow

We'll then take a coffee and food break as needed. Some coffee, tea and local treats from Magpie's Bakery will be provided.

The second 2 hours will consist of breakout sessions where groups of folks can work with datasets using the tools/skills picked up. We invite people to bring their own datasets that need any kind of work - encoding issues, normalizing headings, mapping to other formats, pulling in URIs. If you don't bring your own data, we'll use datasets from UTK and the DPLA that need work normalizing and mapping names/subjects of regional interest. Attendees are invited to sit and learn or work on their own data - whatever you feel most comfortable with doing.

Please register below, and let us know if you are 1. able to share skills or 2. will be bringing your own data. Neither of these are required for attendance.

Questions or issues? Email Christina at charlow2@utk.edu Travel information is being sent directly to those registered. Ask Christina if you didn't receive these.

Southeast 2019

2018-11-15T19:39:40Z

Kbeswick:

Southeast 2019

2018-11-15T19:38:35Z

Kbeswick: Add Code4Lib Southeast 2019 page

2016 Lightning Talks

2016-03-14T17:22:04Z

Kbeswick: /* Wednesday 11:00 to 12:00 */

==Lightning Talks==
Lightning Talks presented at Code4Lib 2016 in Philadelphia, PA from March 8, 2016 - March 10, 2016.

==Tuesday 15:50 to 16:50==

[https://www.youtube.com/watch?v=CJf8Ja6sPAg Recording]

# [https://docs.google.com/presentation/d/1Xets1RZSM-7IsR31k3bsQn5wzSnQbtT0eGfe0y9-oLQ/edit#slide=id.p4 #Code4LibProgramSoWhite] - Whitni Watkins & Code4Lib 2016 Programming Committee
# Static Site Generator for Finding Aids - Hillel Arnold
# [http://subtxt.in/slides/av-access Accessible Digital Video Libraries for Humans and Machines] - Drew Gordon
# Visualizing Book Content - Greg Lindall
# So You're Going to Die :) - Angela Galvan
# You Can Participant In An OSS Project Even If You Don't Write Programs - Yuka Egusa
# XFR Collective - Lorena Ramírez-López
# [http://www.slideshare.net/bohyunkim/visualizing-library-data-59311803 Visualizing Library Data] - Boyhun Kim

==Wednesday 11:00 to 12:00==

[https://www.youtube.com/watch?v=SaMuY9SeyOc&feature=youtu.be&t=2h10m20s Recording]

# Let's Get Physical - Ian Walls
# Transferring Digital Records to the Archives - Greg Wiedeman
# Instagram API Changes - Todd Stoffer
# Why Cats Prefer Boxes Over Fancy Toys - Katherine Deibel
# [http://bit.ly/1YuCok4 "xmlaminar"] - Michael Gibney
# [http://z.umn.edu/c4ldoi Resolving Metadata from DOI] - Michael Berkowski
# [http://kbeswick.github.io/quick_search_code4lib2016/ QUICKSEARCH (Now Open Source)] - Kevin Beswick
# Using Sphinx for Documentation - Dan Gillean
# GW Programming Consultations - Justin Littman
# The RMap Project - Karen Hanson

==Thursday 10:15 to 11:00==

[https://youtu.be/pSlJr8L8dpA?t=50s Recording]

# [https://docs.google.com/presentation/d/1JbSDNvsOgTOMVPgQ7HgXSVrLj270DZlDTzFrawhubuA/edit#slide=id.g10c59995b4_0_76 Finding Aids/Digital Collections Integration] - Sean Aery
# Code4Lib Con (Staring down the barrel of a huge contract) - Chad Nelson
# GitHub as a Knowledge Base - Heidi Tebbe
# Leveraging the Public Cloud to Compliment Your ILS - Shlomo Knisbacher
# Stupid Simple JavaScript that Makes You a Hero and How to Win Friends in Libraries - Allison Jai O'Dell
# Single Sign On, Identity & System Integration - Steelsen Smith
# [https://github.com/alblaine/c4l16-lightningtalk/blob/master/slides.pdf Code+Art] - Alison Blaine
# opaquenamespace.org - Ryan Wick
# Your Metadata is What?!? - Robert Haschart
# FAUXBR, etc. in Pika - James Staub

[[Category:Code4Lib2016]]

2016 Conference Committees

2015-09-08T12:58:19Z

Kbeswick: /* Program Committee */

= Code4Lib 2016 Committees =

''Many hands make for light work.''

Hosting a conference is incredibly complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2016 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.

We will assign a local contact (LPC) to each committee.

== Location and Dates ==

* Location: Old City District of Philadelphia, PA
* Dates: March 7-10, 2016
** Pre-conferences -
** Main meeting -
** Post conference activities?

== Local Planning Committee ==
This committee is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.

* David Lacy (Villanova) - Primary Contact (v)
* Chad Nelson - Secondary Contact (v)
* Anna Headley (Chemical Heritage Foundation) - Documentarian (v)
* [[User:Sdellis|Shaun Ellis]] (Princeton) (v)
* Katherine Lynch (Temple) (v)
* Stephen Ng (Temple)
* Brett Bonfield (Collingswood Public)
* Lauren Gala (UPenn)
* David Uspal (Villanova) (v)
* Chris Clement (Drexel)

== Website Working Group ==
This group will focus on content strategy (in collaboration with the Documentation Committee) and feature implementations to improve the overall user experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).

[[Website Working Group Documents|Website Working Group Documents]]

* [[User:Cdmo|Charlie Morris]] (Penn State) - Primary Contact
* [[User:jtidal|Junior Tidal]] (New York City College of Technology) - Secondary Contact
* [[User:BillMcMillin|Bill McMillin]] (Pratt Institute) - Documentarian
* [[User:Sdellis|Shaun Ellis]] (Princeton) - LPC Contact (v)
* [[User:Phette23|Eric Phetteplace]] (Cal College of the Arts)
* [[User:Sarahshealy| Sarah Shealy]] (Greenville (SC) County Public Library)
* [[User:JennC| Jennifer Colt]] (Cornell University Library)
* [[User:LaurenAjamie| Lauren Ajamie]] (University of Notre Dame Library)
* [[User:MichaelSchofield| Michael Schofield]] ( @schoeyfield )
* [[User:LukeAeschleman| Luke Aeschleman]] (UNC - Chapel Hill | Health Sciences Library)
* [[User:Wickr|Ryan Wick]]
* [[User:cbeer|Chris Beer]]

== Sponsorship Committee ==
This group will focus on making sure all who want to support the conference have the opportunity to do so. Sponsorship Committee work involves working with the LPC to close budget gaps and talking to potential sponsors to find the level that is right for them.

The Sponsorship committee meets every Monday at 3pm EST (12pm PST) via [https://plus.google.com/hangouts/_/gwibrfqhzxe23uto4me3tktbnia Google hangout].

* [[User:Sdellis|Shaun Ellis]] (Princeton) (v)
* David Uspal (Villanova) - LPC Contact (v)
* Chad Nelson
* Morgan McKeehan
* Ray Schwartz
* Sharon Whitfield (Rowan University)
* Brett Bonfield (Collingswood Public) (v)
* Katherine Lynch (Temple University)

== Keynote Committee ==
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.

* Brett Bonfield (Collingswood Public)
* John Mignault (ESDN/METRO)
* Emily Morton-Owens
* [[User:Phette23|Eric Phetteplace]]
* Whitni Watkins (St. Lawrence University)
* Beatrice Pulliam (Providence Public)

== Pre-conference Committee ==
This committee plans the pre-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.
* Anna Headley - Chemical Heritage Foundation (Local Contact)
* [[User:ChristinaHarlow|Christina Harlow]]
* Eric Lease Morgan - Librarian-At-Large

== Program Committee ==
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.
* David Lacy - Villanova (Local Contact)
* Kevin Beswick - NCSU

== Scholarship Committee ==
This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.
* Chad Nelson (Local Contact)
* [[User:jtidal|Junior Tidal]] (New York City College of Technology)
* Linda Ballinger (Penn State)
* Mairelys Lemus-Rojas (University of Miami Libraries)
* Spencer Lamm (Drexel University)

== Childcare Committee ==
This group assess the need for childcare at the conference, organizes childcare options, determines cost, and liaises with parents and chilcare providers
* Chad Nelson (Local Contact)

== Additional Committees... Coming Soon! ==
* Book Give-Away
* Onsite Volunteer
* Social Activities
* Streaming Video
* T-Shirt
* Voting
* Whatever
* Wifi/Electrical
* IRC
* Reception?
* Accessibility

[[Category:Code4Lib2016]]

2014 During the Conference Volunteers

2014-03-10T17:59:54Z

Kbeswick: /* Session Timer Volunteers */

code4lib 2014 During the Conference Volunteers

== Hospitality Suite Committee ==

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

== Welcome Wagon Committee ==

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

* Becky Yoose (b.yoose at google)

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

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

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

Tuesday AM

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

Wednesday AM

Wednesday PM

Thursday AM

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

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

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

* Becky Yoose (yo_bj in IRC)

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

==Registration Desk Volunteers==

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

Tuesday 8-9 am

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

==MCs==

Tuesday AM

Tuesday PM

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

Wednesday AM

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

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

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

== Session Timer Volunteers ==

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

'''Schedule for Session Timers'''

Tuesday AM
* Francis Kayiwa
* Dan Kerchner

Tuesday PM
* Peter Murray
* Ranti Junus

Wednesday AM
* Maura Carbone

Wednesday PM
* Violeta Ilik

Thursday AM
* Bret Davidson

== Raffles ==

== Whatever Else Needs to be Done ==

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

[[Category: Code4Lib2014]]

2014 During the Conference Volunteers

2014-03-10T17:33:41Z

Kbeswick: /* Session Timer Volunteers */

code4lib 2014 During the Conference Volunteers

== Hospitality Suite Committee ==

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

== Welcome Wagon Committee ==

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

* Becky Yoose (b.yoose at google)

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

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

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

Tuesday AM

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

Wednesday AM

Wednesday PM

Thursday AM

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

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

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

* Becky Yoose (yo_bj in IRC)

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

==Registration Desk Volunteers==

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

Tuesday 8-9 am

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

==MCs==

Tuesday AM

Tuesday PM

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

Wednesday AM

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

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

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

== Session Timer Volunteers ==

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

'''Schedule for Session Timers'''

Tuesday AM
* Francis Kayiwa
* Dan Kerchner

Tuesday PM
* Peter Murray
* Ranti Junus

Wednesday AM
* Maura Carbone

Wednesday PM
* Violeta Ilik

Thursday AM
* Bret Davidson
* Ayse Durmaz

== Raffles ==

== Whatever Else Needs to be Done ==

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

[[Category: Code4Lib2014]]

2014 During the Conference Volunteers

2014-03-04T16:36:39Z

Kbeswick: create during the 2014 conference volunteer signup page

Main Page

2014-03-04T15:59:13Z

Kbeswick: /* Code4Lib 2014 Conference */

{|align=right
|__TOC__
|}

== About Code4Lib ==

* [[About Code4Lib]] - Background and history of the community
* [[A Guide for the Perplexed]] - Building skills for working with library technologies
* [[How to hack code4lib]] - For those newer to the community
* [https://docs.google.com/document/d/1m-9VtL7L_fUxl2hTF_YZSdFRfucaLtmHvLSzom6XPVM/edit?pli=1 Code4Lib Indoctrination] (This is a Google doc open to all including anonymous feedback.)
**"How do we make code4lib a more inclusive place for newcomers? Or, how do we quickly indoctrinate newbies to our values and ways of doing things?"
**Suggestions, ideas, and follow-up actions solicited.
* [[One recommended tool/resource for n00bs]] - For new coding librarians/library Coders
* [[Mentorship Program]]
* [[Zoia or the Code4Lib IRC bot]]

==Code4Lib 2015 Conference==
*[[2015 Hosting Proposals]]

==Code4Lib 2014 Conference==
See also the ''[[:Category:Code4Lib2014]] category''
*[http://code4lib.org/conference/2014 Summary Information]
*[[Code4Lib 2014 Conference Planning Volunteers]]
*[[2014 Proposals]]
*[[2014 Prepared Talk Proposals]]
*[[2014 preconference proposals]]
*[[2014 Invited Speakers Nominations]]
*[[Sponsor Logos for T-Shirt]]
*[[2014 t-shirt design proposals]]
**[[media:cmarkman-shirt.gif|winning design]]
*[[2014 Room and Ride Share]]
*[[2014 Social Activities]]
*[[2014 Video Recording & Streaming]]
*[[2014 Lessons Learned]]
*[[2014 During the Conference Volunteers]]

== Local / Regional Groups ==

* [[NYC|Code4LibNYC]] - NYC and surrounding areas
* [[NEC4L|New England Code4lib]] - New England
* [[NL|Code4Bib]] - Dutch Code4Bib
* [[MDC|Code4libMDC]] - Maryland, Washington D.C, Virginia, and surrounding areas
* [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest
* [[North|code4lib North]] - Ontario and surrounding areas ''(new for Jan 2010!)''
* [[Midwest|Code4Lib Midwest]] - Wherever that is...
* [http://groups.google.com/group/ikr-fejlesztok/ Code4lib.hu] - Group of Hungarian library developers
* [http://www.code4lib.jp/ Code4Lib Japan] - ''(new in 2010!)'', see also [http://twitter.com/yesonline/statuses/28561046501 tweet from Jerry Lee]
* [http://groups.google.com/group/code4glam Code4GLAM Australia] - coders, hackers, developers and technologists in the Australian GLAM (Galleries, Libraries, Archives & Museums) sector.
* [[GreatEastern|Code4Lib Great Eastern]] - Atlantic Provinces
* [[Code4lib_Mid-Atlantic|Code4Lib Mid-Atlantic]] - Philadelphia and the Greater Tri-State Area
* [[BC|Code4Lib BC]] - British Columbia ''(new in 2013)''
* [[Edmonton|Code4LibYEG]] - Edmonton, Alberta ''(also new in 2013)''

== Interest Groups ==

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

== Software Usage and Documentation ==

* [[Umlaut]] - OpenURL link resolving middleware
* [[:Category:Patterns|Patterns for Collaborative Code]] - Patterns to make your open source 'more open', more amenable to distributed development and use at multiple institutions without forking.
* [[ILS Documentation]]
* [[OSS Directory]]
* [[Working with MARC]]
* [[Rogue]] - principles for standards creation
* [[ProjectManagement]] - list of project management and issue tracking software that are frequently mentioned on the Code4Lib mailinglist

== Code4Lib Journal ==

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

== Current topics ==

* [[Code4Lib Website Update]]
* [[OCLC Policy Change]]
* [[SirsiDynix: Integrated Library System Platforms on Open Source]]
* [[Parsing Library Data]]
* [[Robots Are Our Friends]]

== Other Code4Lib Sites ==

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

== Earlier Conferences and events ==
[[Conference Financial History At A Glance]]

===Code4Lib 2013 Conference===
See also the ''[[:Category:Code4Lib2013]] category''
*[http://code4lib.org/conference/2013/schedule 2013 Schedule]
*[[2013 Lightning Talks Signup]]
*[https://docs.google.com/document/d/1TahfqabnchZLD1opq6ILs8XCYdXkgJDsj8-WyVLNzI4/edit Breakout Session Signups] | [[2013_breakout_sessions_reports|2013 Breakout Sessions Reports]]
*[[2013_committees_sign-up_page|Volunteer to help plan 2013 conference]]
*[[2013_During_the_Conference_Volunteers|During the conference volunteer signup]]
*[[2013 Invited Speakers Nominations]] -- nominations close Aug. 31, 2012.
*[[2013 preconference proposals|2013 preconference sessions]] - try to sign up by Jan 15th
*[[2013 talks proposals]] - due Friday, Nov 9
*[[2013 t-shirt design proposals]] - due Monday, Dec. 31
**[[media:Metadata.jpg|winning design]]

*[[2013_social_activities|Social Activities for 2013 Conference]]
*[[2013_travel|Travel Advice and Getting To and From the 2013 Conference]]
*[[2013_room_ride_share|2013 Conference Room and Ride Share]]
*[[2013_Guide_To_Wireless| Connecting to the UIC's Wifi]]
*[[2013 Twitter List| 2013 Twitter Attendee List]]

* Conference hashtag: #c4l13 -- [https://docs.google.com/spreadsheet/ccc?key=0AsyivMoYhk87dFljMUZURWZMYzNzT2lwcEduUUJ6d1E#gid=113 Archive of tweets] | [http://www.flickr.com/search/?q=c4l13 Flickr photos]

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

* [http://code4lib.org/conference/2012/ 2012 home]
* [[During_the_Conference_Volunteers|Volunteer to help at code4lib 2012]]
* [[2012_committees_sign-up_page|Volunteer to help plan 2012 conference]]
* [[2012_preconference_proposals|2012 Preconference Proposals]]--due Sunday, November 20
* [[2012_talks_proposals|2012 Talk Proposals]]--due Sunday, November 20
* [[2012_c4l2012_social_activities|Social Activities]] - ideas and sign-up
* [[c4l2012_rideshare|Rideshare-Roomshare]]
* [[c4l2012_t-shirtcontest|T-shirt contest]]
**[[media:C4l12-t-shirt.jpg|winning design]]
* [[ideas_for_2012|Put your ideas for 2012 here!]]
* [[C4L2012_Call_For_Host|2012 Call For Host]]
* [[How To Plan A Code4LibCon]]
* [http://linkd.in/unhJsR LinkedIn Event]
* [[2012_twitter_list|List your Twitter handle here]]
* [[2012_Lightning_Talks_Signup|Lightning Talks Signup]]
* [http://irc.code4lib.org/ IRC Channel Timeline & Log]
* [http://www.livestream.com/code4lib Conference Livestream] (non-attendees only, please!)

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

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

* [[C4L2011_rideshare|Airport Ride Share and Carpooling]]
* [[C4L2011_roomshare | Hotel room share]]
* [http://vote.code4lib.org/election/results/18 T-Shirt election]
** [[media:Option4.jpg|winning design]]

=== Code4Lib 2010 Conference ===

''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2010 Code4lib2010 category]''
* [http://code4lib.org/conference/2010/schedule Finalized schedule]
* [[2010 Lightning Talks Signup]] - sign up to give a lightning talk
* [[2010 Breakout Sessions]] - suggest a breakout here
* '''[[2010 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff'''
* [[C4L2010_social_activities|Social Activities]] - ideas & sign-up
* [[Committees sign-up page]] - '''Volunteer to help'''
* [[C4L2011_planning_wishlist|'''Put your ideas for 2011 here!''']]
* [[Asheville Airport to Hotel Van Manifest]]
* [[C4L2010rideshare|General shared travel/transportation planning]]
* [[C4L2010planning:RoommatesRidesEtc|Roommates, Rides, Etc]]
* [[C4L2010_manning_discount|Manning Publications Discount]] - discount code (40% off) for use by attendees through Feb. 28, 2010
* Thanks also to our other sponsors!
* [[C4L2010planning|2010 Planning]]
* [[C4L2010planning:_wishlist | 2010 Planning Wishlist]] - planning page for issues, expectations, etc. for the 2010 conference
* [http://vote.code4lib.org/election/results/14 T-Shirt election]
** [[media:Code4lib2010_P-Hochstenbach.png|winning design]]

=== Code4Lib 2009 Conference ===

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

=== Older Conference T-Shirt Designs ===
* [http://www.code4lib.org/node/235 2008 (Portland)] - [http://code4lib.org/files/code4lib08.gif winning design]
* [http://code4lib.org/node/146 2007 (Athens)] - [[2007 winning design]]
* [http://code4lib.org/tshirts 2006 (Corvalis)] - [[2006 winning design]]

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

== Archived topics ==

* [[Logo Design Process]]

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

2014 Prepared Talk Proposals

2013-11-08T21:17:30Z

Kbeswick: added kbeswick talk proposal

'''Proposals for Prepared Talks:'''

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

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

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

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

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

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

'''Talk Proposals'''

==Creating a new Greek-Dutch dictionary==
* Caspar Treijtel, University of Amsterdam, c.treijtel@uva.nl

At present, no complete dictionary of (ancient) Greek-Dutch is available online. A new dictionary is currently under construction at Leiden University, with software being developed at the University of Amsterdam. The team in Leiden has already begun preparation of the data, with at this moment about 6,000 approved lemmas. The ultimate goal is to produce both a print version and online open access version from the same source documents. The software needed for this has been made in a project that was funded by CLARIN-NL.

Migrator

For the production of lemmas we have implemented an advanced workflow. The (generally non-technical) users create lemmas using MS Word, which is both familiar and easy to use. We have developed a custom software module that carefully migrates the Word documents into deeply structured XML by analyzing the structure and semantics of the lemmas, and falling back on heuristics in ambiguous cases. While having initially envisioned the oXygen XML Author component as the main tool for creating new lemmas, we obtained excellent results with the migrator module, and decided therefore to continue using MS Word as the primary composition tool. The main advantage of this is that the editors are much more familiar with Word than with any other WYSIWYG editor. Lemmas that have been migrated to XML are stored in an XML database and can be further edited using oXygen XML Author.

Lemmatizer

Greek morphology is complicated. In order to use a dictionary effectively, a rather high level of initial language competence is necessary for the user to be able to relate the word form s/he finds in a text to the correct basic lemma form, where the definition of the word can be found. Using a Greek morphological database we have been able to facilitate the search for lemmas. A ‘lemmatizer’ module gives the possible parsings of the word forms and the lemmas they can be derived from. This enables the user to type in the word as found in the text and be redirected to the correct lemma.

Visualization

For the online dictionary we have implemented a visualization module that allows the user to view multiple lemmas at once. The implementation of this module has been done using the Javascript framework MooTools. The result is a viewer that performs really well and is run by maintainable Javascript code.

The online dictionary is still being worked on, have a look at http://www.woordenboekgrieks.nl/ for the beta version. A newer test version with additional features can be found here: http://angel.ic.uva.nl:8600/.

Credits

* construction of the dictionary: Prof. Ineke Sluiter, Classics department of Leiden University; Prof. Albert Rijksbaron, University of Amsterdam
* publisher of the dictionary: Amsterdam University Press
* design/typesetting dictionary: TaT Zetwerk (http://www.tatzetwerk.nl/)
* software development: Digital Production Center, University Library, University of Amsterdam
* project funding: CLARIN-NL (http://www.clarin.nl/)
* morphological database for use by the lemmatizer: courtesy of Prof. Helma Dik, University of Chicago (based on data of the Perseus Project)

----

== Using Drupal to drive alternative presentation systems ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== WebSockets for Real-Time and Interactive Interfaces ==

* [http://ronallo.com Jason Ronallo], NCSU Libraries, jason_ronallo@ncsu.edu

Previous Code4Lib presentations:
* [http://code4lib.org/conference/2012/ronallo HTML5 Microdata and Schema.org] 2012
* [http://code4lib.org/conference/2013/ronallo HTML5 Video Now!] 2013

Watching the Google Analytics Real-Time dashboard for the first time was mesmerizing. As soon as someone visited a site, I could see what page they were on. For a digital collections site with a lot of images, it was fun to see what visitors were looking at. But getting from Google Analytics to the image or other content of what was currently being viewed was cumbersome. The real-time experience was something I wanted share with others. I'll show you how I used a WebSocket service to create a real-time interface to digital collections.

In the Hunt Library at NCSU we have some large video walls. I wanted to make HTML-based exhibits that featured viewer interactions. I'll show you how I converted Listen to Wikipedia [1] into an bring-your-own-device interactive exhibit. With WebSockets any HTML page can be remote controlled by any internet connected device.

I will attempt to include real-time audience participation.

[1] http://listen.hatnote.com/

== Rapid Development of Automated Tasks with the File Analyzer ==

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

The Georgetown University Libraries have customized the File Analyzer and Metadata Harvester application (https://github.com/Georgetown-University-Libraries/File-Analyzer) to solve a number of library automation challenges:
* validating digitized and reformatted files
* validating vendor statistics for counter compliance
* preparing collections of digital files for archiving and ingest
* manipulating ILS import and export files

The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census. After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform. Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.

The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules. As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.

Learn about the functionality that is available for download, how you can use this tool to automate workflows from digital collections to ILS ingests to electronic resources statistics and also discuss the opportunities to collaborate on enhancements to this application!

== GeoHydra: How to Build a Geospatial Digital Library with Fedora ==

* [http://stanford.edu/~drh Darren Hardy], Stanford University, drh@stanford.edu

Geographically-rich data are exploding and putting fear in those trying to
tackle integrating them into existing digital library infrastructures.
Building a spatial data infrastructure that integrates with your digital
library infrastructure need not be a daunting task. We have successfully
deployed a geospatial digital library infrastructure using Fedora and
open-source geospatial software [1]. We'll discuss the primary design
decisions and technologies that led to a production deployment within a few
months. Briefly, our architecture revolves around discovery, delivery, and
metadata pipelines using open-source OpenGeoPortal [2], Solr [3], GeoServer
[4], PostGIS [5], and GeoNetwork [6] technologies, plus the proprietary ESRI
ArcMap [7] -- the GIS industry's workhorse. Finally, we'll discuss the key
skillsets needed to build and maintain a spatial data infrastructure.

[1] http://foss4g.org
[2] http://opengeoportal.org
[3] http://lucene.apache.org/solr
[4] http://geoserver.org
[5] http://postgis.net
[6] http://geonetwork-opensource.org
[7] http://esri.com

==Under the Hood of Hadoop Processing at OCLC Research ==

[http://roytennant.com/ Roy Tennant]

* Previous Code4Lib presentations: 2006: "The Case for Code4Lib 501c(3)"

[http://hadoop.apache.org/ Apache Hadoop] is widely used by Yahoo!, Google, and many others to process massive amounts of data quickly. OCLC Research uses a 40-node compute cluster with Hadoop and HBase to process the 300 million MARC records of WorldCat in various ways. This presentation will explain how Hadoop MapReduce works and illustrate it with specific examples and code. The role of the jobtracker in both monitoring and reporting on processes will be explained. String searching WorldCat will also be demonstrated live.

== Quick and Easy Data Visualization with Google Visualization API and Google Chart Libraries ==

[http://bohyunkim.net/blog Bohyun Kim], Florida International University, bohyun.kim@fiu.edu
* 'No' previous Code4Lib presentations

Do most of the data that your library collects stay in spreadsheets or are published as a static table with a series of boring numbers? Do your library stakeholders spend more time collecting the data than using it as a decision-making tool because the data is presented in a way that makes it hard for them [http://developers.google.com/chart/interactive/docs/gallery to quickly grasp its significance? ]

This talk will provide an overview of [http://developers.google.com/chart/interactive/docs/reference Google Visualization API] [2] and [http://developers.google.com/chart/ Google Chart Libraries] [3] to get you started on the way to quickly query and visualize your library data from remote data sources (e.g. a Google Spreadsheet or your own database) with (or without) cool-looking user-controls, animation effects, and even a dashboard.

== Leap Motion + Rare Books: A hands-free way to view and interact with rare books in 3D ==

[http://http://www.youtube.com/user/jpdenzer Juan Denzer], Binghamton University, jdenzer@binghamton.edu
* 'No' previous Code4Lib presentations

As rare books become more delicate over time, making them available to the public becomes harder. We at Binghamton University Library have developed an application that makes it easier to view rare books without ever having to touch them. We have combined the Leap Motion hands-free device and 3D rendered models to create a new virtual experience for the viewer.

The application allows the user to rotate and zoom in on a 3D representation of a rare book. The user is also able to ‘open’ the virtual book and flip through it using a natural user interface. Such as swiping the hand left or right to turn the page.

The application is built on the .Net framework and is written in C#. 3D models are created using simple 3D software such as sketchup or Blender. Scans of the book cover and spine are created using simple flatbed scanners. The inside pages are scanned using overhead scanners.

This talk with discuss the technologies used in developing the application and virtually any library could implement the application with virtually no coding at all. This presentation will have a demonstration of the software and also a chance for audience members to experience the Rare Book Leap Motion App themselves.

== Course Reserves Unleashed! ==

* Bobbi Fox, Library Technology Services, Harvard University, bobbi_fox@harvard.edu
* Gloria Korsman, Andover-Harvard Theological Library
** No previous Code4Lib presentations

Hey kids! Remember when SOAP was used for something other than washing? Our sophisticated (and highly functional) Course Reserves Request system does!

However, while the system is great for submitting and processing course reserve requests, the student-facing presentation through Havard’s home-grown -- and soon to be replaced -- LMS leaves a lot to be desired.

Follow along as we leverage Solr 4 as a No-SQL database, along with more progressive RESTful API techniques, to release Reserves data into the wild without interfering with reserves request processing -- and, in the process, open up the opportunity for other schools to feed their data in as well.

== We Are All Disabled! Universal Web Design Making Web Services Accessible for Everyone ==

Cynthia Ng, Accessibility Librarian, CILS at Langara College
* No previous Code4Lib presentations (not counting lightning talks)

We’re building and improving tools and services all the time, but do you only develop for the “average” user or add things for “disabled” users? We all use “assistive” technology accessing information in a multitude of ways with different platforms, devices, etc. Let’s focus on providing web services that are accessible to everyone without it being onerous or ugly. The aim is to get you thinking about what you can do to make web-based services and content more accessible for all from the beginning or with small amounts of effort whether you're a developer or not.

The goal of the presentation is to provide both developers and content creators with information on simple, practical ways to make web content and web services more accessible. However, rather than thinking about putting in extra effort or making adjustment for those with disabilities, I want to help people think about how to make their websites more accessible for all users through universal web design.

== Personalize your Google Analytics Data with Custom Events and Variables ==

[http://joshwilson.net Josh Wilson], Systems Integration Librarian, State Library of North Carolina - joshwilsonnc@gmail.com

At the State Library of North Carolina, we had more specific questions about the use of our digital collections than standard GA could provide. A few implementations of custom events and custom variables later, we have our answers.

I'll demonstrate how these analytics add-ons work, and why implementation can sometimes be more complicated than just adding a few lines of JavaScript to your ga.js. I'll discuss some specific examples in use at the SLNC:

* Capturing the content of specific metadata fields in CONTENTdm as Custom Events
* Recording Drupal taxonomy terms as Custom Variables

In both instances, this data deepened our understanding of how our sites and collections were being used, and in turn, we were able to report usage more accurately to content contributors and other stakeholders.

More on: [https://developers.google.com/analytics/devguides/collection/gajs/eventTrackerGuide GA Custom Events] | [https://developers.google.com/analytics/devguides/collection/gajs/gaTrackingCustomVariables GA Custom Variables]

== Behold Fedora 4: The Incredible Shrinking Repository! ==

Esmé Cowles, UC San Diego Library. Previous talk: [http://code4lib.org/conference/2013/cowles-critchlow-westbrook All Teh Metadatas Re-Revisited] (2013)

* One repository contains untold numbers of digital objects and powers many Hydra and Islandora apps
* It speaks RDF, but contains no triplestore! (triplestores sold separately, SPARQL Update may be involved, some restrictions apply)
* Flexible enough to tie itself in knots implementing storage and access control policies
* Witness feats of strength and scalability, with dramatically increased performance and clustering
* Plumb the depths of bottomless hierarchies, and marvel at the metadata woven into the very fabric of the repository
* Ponder the paradox of ingesting large files by not ingesting them
* Be amazed as Fedora 4 swallows other systems whole (including Fedora 3 repositories)
* Watch novice developers setup Fedora 4 from scratch, with just a handful of incantations to Git and Maven

The Fedora Commons Repository is the foundation of many digital collections, e-research, digital library, archives, digital preservation, institutional repository and open access publishing systems. This talk will focus on how Fedora 4 improves core repository functionality, adds new features, maintains backwards compatibility, and addresses the shortcomings of Fedora 3.

== Organic Free-Range API Development - Making Web Services That You Will Actually Want to Consume ==

Steve Meyer and Karen Coombs, OCLC

Building web services can have great benefits by providing reusability of data and functionality. Underpinning your applications with a web service will allow you to write code once and support multiple environments: your library's web app, mobile applications, the embedded widget in your campus portal. However, building a web service is its own kind of artful programming. Doing it well requires attention to many of the same techniques and requirements as building web applications, though with different outcomes.

So what are the usability principles for web services? How do you build a web service that you (and others) will actually want to use? In this talk, we’ll share some of the lessons learned - the good, the bad, and the ugly - through OCLC's work on the WorldCat Metadata API. This web service is a sophisticated API that provides external clients with read and write access to WorldCat data. It provides a model to help aspiring API creators navigate the potential complications of crafting a web service. We'll cover:

* Loose coupling of data assets and resource-oriented data modeling at the core
* Coding to standards vs. exposure of an internal data model
* Authentication and security for web services: API Keys, Digital Signing, OAuth Flows
* Building web services that behave as a suite so it looks like the left hand knows what the right hand is doing

So at the end of the day, your team will know your API is a very good egg after all.

If accepted, the presenters intend to produce and share a Quick Guide for building a web service that will reflect content presented in the talk.

== Lucene's Latest (for Libraries) ==

erik.hatcher@lucidworks.com

Lucene powers the search capabilities of practically all library discovery platforms, by way of Solr, etc. The Lucene project evolves rapidly, and it's a full-time job to keep up with the ever improving features and scalability. This talk will distill and showcase the most relevant(!) advancements to date.

== The Why and How of Very Large Displays in Libraries. ==

* Cory Lown, NCSU Libraries, cwlown@ncsu.edu

Previous Code4Lib Presentations:
* [http://code4lib.org/conference/2012/lown How People Search the Library from a Single Search Box] 2012
* [http://code4lib.org/conference/2010/orphanides_lown_lynema Enhancing Discoverability with Virtual Shelf Browse] 2010

Built into the walls of NC State's new Hunt Library are several [http://www.christiedigital.com/en-us/digital-signage/products/microtiles/pages/microtiles-digital-signage-video-wall.aspx Christie MicroTile Display Wall Systems]. What does a library do with a display that's seven feet tall and over twenty feet wide? I'll talk about why libraries might want large displays like this, what we're doing with them right now, and what we might do with them in the future. I'll talk about how these displays factor into planning for new and existing web projects. And I'll get into the fun details of how you build web applications that scale from the very small browser window on a phone all the way up to a browser window with about 14 million pixels (about 10 million more than a dual 24" monitor desktop setup).

== Discovering your Discovery System in Real Time. ==

* Godmar Back, Virginia Tech, gback@vt.edu
* Annette Bailey, Virginia Tech, afbailey@vt.edu

Practically all libraries today provide web-based discovery systems to their users;
users discover items and peruse or check them out by clicking on links. Unlike
the traditional transaction of checking out a book at the circulation desk, this
interaction is largely invisible. We have built a system that records user's
interaction with Summon in real-time, processes the resulting data with minimal delay,
and visualizes it in various ways using Google Charts and using various d3.js modules,
such as word clouds, tree maps, and others.

These visualizations can be embedded in web sites, but are also suitable for
projection via large-scale displays or projectors right into the 'Learning Spaces'
many libraries are converted into. The goal of this talk is to share the technology
and advocate the building of a cloud-based infrastructure that would make this
technology available to any library that uses a discovery system, rather than just
those who have the technological prowess for developing such systems and
visualizations in-house.

Previous presentations at Code4Lib:
* Talk: Code4Lib 2009 [http://code4lib.org/files/LibX2.0-Code4Lib-2009AsPresented.ppt LibX 2.0]
* Preconference: [http://wiki.code4lib.org/index.php/LibX_Preconference LibX 2.0, 2009]
* Preconference: Code4Lib 2010, On Widgets and Web Services

== Your Library, Anywhere: A Modern, Responsive Library Catalogue at University of Toronto Libraries ==

* Bilal Khalid, Gordon Belray, Lisa Gayhart (lisa.gayhart@utoronto.ca)

* No previous Code4Lib presentations

With the recent surge in the mobile device market and an ever expanding patron base with increasingly divergent levels of technical ability, the University of Toronto Libraries embarked on the development of a new catalogue discovery layer to fit the needs of its diverse users.

[http://search.library.utoronto.ca The result]: a mobile-friendly, flexible and intuitive web application that brings the full power of a faceted library catalogue to users without compromising quality or performance, employing Responsive Web Design principles. This talk will discuss: application development; service improvements; interface design; and user outreach, testing, and project communications. Feedback and questions from the audience are very welcome. If time runs short, we will be available for questions and conversation after the presentation.

Note: A version of this content has been provisionally accepted as an article for Code4Lib Journal, January 2014 publication.)

== All Tiled Up ==

* Mike Graves, MIT Libraries (mgraves@mit.edu)

You've got maps. You even scanned and georeferenced them. Now what? Running a full GIS stack can be expensive, and overkill in some cases. The good news is that you have a lot more options now than you did just a few years ago. I'd like to present some lighter weight solutions to making georeferenced images available on the Web.

This talk will provide an introduction to MBTiles. I'll go over what they are, how you create them, how you use them and why you would use them.

== The Great War: Image Interoperability to Facebook ==

* Rob Sanderson, Los Alamos National Laboratory (azaroth42@gmail.com)
** (Code4Lib 2006: [http://www.code4lib.org/2006/sanderson | Library Text Mining])
* Rob Warren, Carleton University
** No previous presentations

Using a pipeline constructed from Linked Open Data and other interoperability specifications, it is possible to merge and re-use image and textual data from distributed library collections to build new, useful tools and applications. Starting with the OAI-PMH interface to ContentDM, we will take you on a tour through the International Image Interoperability Framework and Shared Canvas, to a cross-institutional viewer, and image analysis for the purposes of building a historical Facebook from finding and tagging people in photographs. The World War One collections are drawn from multiple institutions and merged by the machine learning code.

The presentation will focus on the (open source) toolchain and the benefits of the use of standards throughout: OAI-PMH to get the metadata, IIIF for interaction with the images, the Shared Canvas ontology for describing collections of digitized objects, Open Annotation for tagging things in the images and specialized ontologies that are specific to the contents. The tools include standard RDF / OWL technologies, JSON-LD, imagemagick and OpenCV for image analysis.

== Visualizing Solr Search Results with D3.js for User-Friendly Navigation of Large Results Sets ==

*Julia Bauder, Grinnell College Libraries (bauderj-at-grinnell-dot-edu)
*No previous presentations at national Code4Lib conferences

As the corpus of articles, books, and other resources searched by discovery systems continues to get bigger, searchers are more and more frequently confronted with unmanageably large numbers of results. How can we help users make sense of 10,000 hits and find the ones they actually want? Facets help, but making sense of a gigantic sidebar of facets is not an easy task for users, either.
During this talk, I will explain how we will soon be using Solr 4’s pivot queries and hierarchical visualizations (e.g., treemaps) from D3.js to let patrons view and manipulate search results. We will be doing this with our VuFind 2.0 catalog, but this technique will work with any system running Solr 4. I will also talk about early student reaction to our tests of these visualization features.

== PeerLibrary – open source cloud based collaborative library ==

* [http://mitar.tnode.com/ Mitar Milutinovic], UC Berkeley, mitar.code4lib at tnode.com
* Not presented or attended code4lib before

[https://github.com/peerlibrary/peerlibrary PeerLibrary is a new open source project] and a cloud service providing collaborative reading, sharing and storing. Users can upload publications they want to read (currently in PDF format), read them in the browser in real-time with others, highlight, annotate and organize their own or collaborative library. PeerLibrary provides a search engine to search over all uploaded open access publications. Additionally, it aims to collaboratively aggregate the open layer of knowledge on top of this publications through public annotations and references user will add to publications. In this way publications would not just be available to read, but accessible to the general public as well. Currently, it is aiming at scientific community and scientific publications.

See [http://blog.peerlibrary.org/post/63458789185/screencast-previewing-the-peerlibrary-project screencast here]. [http://peerlibrary.org/ Subscribe to newsletter] to be a beta tester when we open.

It is still in development and beta launch is planned at the end of November.

== Who was where when, or finding biographical articles on Wikipedia by place and time ==

* [http://morton-owens.info Emily Morton-Owens], The Seattle Public Library (presenting on work from NYU)
* No previous c4l presentations

It's easy to answer the question "What important people were in Paris in 1939?" But what about Virginia in the 1750s or Scandinavia in the 14th century? I created a tool that allows you to search for biographies in a generally applicable way, using a map interface. I would like to present updates to my thesis project, which combines a crawler written in Java that extracts information from Wikipedia articles, with a MongoDB data store and a frontend in Python.

The input to the project is freetext of entire articles in Wikipedia; this is important to allow us to pick up Benjamin Franklin not just in the single most obvious place of Philadelphia but also in London, Paris, Boston, etc. I can talk about my experiments disambiguating place names (approaches pioneered on newspaper articles were actually unhelpful on this type of text) and setting up a processing queue that does not become mired in the biographies of every human who ever played soccer. I also want to mitigate some of the implementation choices I made due to my academic deadline and improve the accuracy/usability.

What I hope to show is that I was able to develop a novel and useful reference tool automatically, using fairly simple heuristics that are a far cry from hand-cataloging familiar to many librarians.

You can try out [http://linserv1.cims.nyu.edu:48866/ the original version] (this server is inconveniently set to be updated/rebooted on 11/8--may be temporarily unavailable)

== Good!, DRY, and Dynamic: Content Strategy for Libraries (Especially the Big Ones) ==

*Michael Schofield, Nova Southeastern University Libraries, mschofield@nova.edu
*No previous code4lib presentations.

The responsibilities of the #libweb are exploding [it’s a good thing] and it is no longer uncommon for libraries to manage or even home-grow multiple applications and sites. Often it is at this point where the web people begin to suffer the absence of a content strategy when, say, business hours need to be updated sitewide a half-dozen times.

We were already feeling this crunch when we decided to further complicate the Nova Southeastern University Libraries by splitting the main library website into two. The Alvin Sherman Library, Research, and Information Technology Center is a unique joint-use facility that serves not only the academic community but the public of Broward County - and marketing a hyperblend of content through one portal just wasn't cutting it. With a web team of two, we knew that managing all this rehashed, disparate content was totally unsustainable.

I want to share in this talk how I went about making our library content DRY (“don’t repeat yourself”): input content in one place--blurbs, policies, featured events, featured databases, book reviews, business hours, and so on.--and syndicate it everywhere - even, sometimes, dynamically target that content for specific audiences or context. It is a presentation that is a little about workflow, a little more about browser and context detection, a tangent about content-modeling the CMS, and a lot about APIs, syndication, and performance.

== No code, no root, no problem? Adventures in SaaS and library discovery ==

*[mailto:erwhite@vcu.edu Erin White, VCU]
*No previous C4L presentations

In 2012 VCU was an eager early adopter of Ex Libris' cloud service Alma as an ILS, ERM, link resolver, and single-stop, de-silo'd public-facing discovery tool. This has been a disruptive change that has shifted our systems staff's day-to-day work, relationships with others in the library, and relationships with vendors.

I'll share some of our experiences and takeaways from implementing and maintaining a cloud service:
* Seeking disruption and finding it
* Changing expectations of service and the reality of unplanned downtime
* Communication and problem resolution with non-IT library staff
* Working with a vendor that uses agile development methodology
* Benefits and pitfalls of creating customizations and code workarounds
* Changes in library IT/coders' roles with SaaS

...as well as thoughts on the philosophy of library discovery vs real-life experiences in moving to a single-search model.

== Building for others (and ourselves): the Avalon Media System ==
* [mailto:michael.klein@northwestern.edu Michael B Klein], Senior Software Developer, Northwestern University
** [http://code4lib.org/conference/2010/metz_klein Public Datasets in the Cloud] (code4lib 2010)
** [http://code4lib.org/conference/2013/klein-rogers The Avalon Media System: A Next Generation Hydra Head For Audio and Video Delivery] (code4lib 2013)
* [mailto:j-rudder@northwestern.edu Julie Rudder], Digital Initiatives Project Manager, Northwestern University
** no previous code4lib presentations

[http://www.avalonmediasystem.org/ Avalon Media System] is a collaborative effort between development teams at Northwestern and Indiana Universities. Our goal is to produce an open source media management platform that works well for us, but is also widely adopted and contributed to by other institutions. We believe that building a strong user and contributor community is vital to the success and longevity of the project, and have developed the system with this goal in mind. We will share lessons learned, pains and successes we’ve had releasing two versions of the application since last year.

Our presentation will cover our experiences:
* providing flexible, admin-friendly distribution and installation options
* building with abstraction, customization and local integrations in mind
* prioritizing features (user stories)
* attracting code contributions from other institutions
* gathering community feedback
* creating a product rather than a bag of parts

== How to check your data to provide a great data product? Data quality as a key product feature at Europeana ==

*[mailto:Peter.Kiraly@kb.nl Péter Király] portal backend developer, Europeana
*No previous C4L presentations

[http://Europeana.eu/ Europeana.eu] - Europe's digital library, archive and museum - aggregates more than 30 million metadata records from more than 2200 institutions. The records come from libraries, archives, museums and every other kind of cultural institution, from very different systems and metadata schemas, and are typically transformed several times until they are ingested into the Europeana data repository. Europeana builds a consolidated database from these records, creating reliable and consistent services for end-users (a search portal, search widget, mobile apps, thematic sites etc.) and an API, which supports our strategic goeal of data for reuse in education, creative industries, and the cultural sector. A reliable "data product" is thus at the core of our own software products, as well as those of our API partners.

Much effort is needed to smooth out local differences in the metadata curation practice of our data providers. We need a solid framework to measure the consistency of our data and provide feedback to decision-makers inside and outside the organisation. We can also use this metrics framework to ask content providers to improve their own metadata. Of course, a data-quality-driven approach requires that we also improve the data transformation steps of the Europeana ingestion process itself. Data quality issues heavily define what new features we are able to create in our user interfaces and API, and might actually affect the design and implementation of our underlying data structure, the Europeana Data Model.

In the presentation I briefly describe the Europeana metadata ingestion process, show the data quality metrics, the measuring techniques (using the Europeana API, Solr and MongoDB queries), some typical problems (both trivial and difficult ones), and finally the feedback mechanism we propose to deploy.

Keywords: Europeana, data quality, EDM, API, Apache Solr, MongoDB, #opendata, #openglam

== Teach your Fedora to Fly: scaling out a digital repository ==

*[mailto:acoburn@amherst.edu Aaron Coburn], Software Developer, Amherst College
*No previous C4L presentations

Fedora is a great repository system for managing large collections of digital objects, but what happens when a popular food magazine begins directing a large number of readers to a manuscript showing Emily Dickinson’s own recipe for doughnuts? While Fedora excels in its support of XML-based metadata, it doesn’t always perform well under a high volume of traffic. Nor is it especially tolerant of network or hardware failures.

This presentation will show how we are making heavy use of a fedora repository while at the same time insulating it almost entirely from any web traffic. Starting with a distributed web front-end built with Node.js, and caching most of the user-accessible content from Fedora in an elastic, fault-tolerant Riak (NoSQL) cluster, we have eliminated nearly all single points of failure in the system. It also means that our production system is spread across twelve separate servers, where asynchrony and Map-Reduce are king. And aside from being blazing fast, it is also entirely Hydra-compliant.

Furthermore, we will attempt to answer the question: if fedora crashes and the visitors to your site don’t notice, did it really fail?

== Using Open Source Software and Freeware to Preserve and Deliver Digital Videos ==
* [mailto:wfang@kinoy.rutgers.edu Wei Fang], Head of Digital Services, Rutgers University Law Library
* Jiebei Luo, Digital Projects Initiative Intern, Rutgers University
*No previous C4L presentations

The Rutgers University Law Library is the official digital repository of the New Jersey Supreme Court oral arguments since 2002. This large video collection contains approximately 3,000 videos with a total of 400 GB or 6,000 viewing hours. With the expansion of this collection, the existing database and the static website could not efficiently support the library’s daily operations and meet its patrons’ search needs.
By utilizing open source software and freeware such as Ubuntu, FFmpeg, Solr and Drupal, the library is able to develop a complete solution to re-encoding videos, embedding subtitles, incorporating Solr search engine and content management system to support full-text subtitle search, automatically updating video metadata records in the library catalog system and eventually providing a plug-in free HTML 5-based Web interface for patrons to view the videos online.
The aspects below will be presented in detail at the conference:
* Video codecs comparison
* Server-end batch video encoding/re-encoding
* HTML 5 video tag and embedding subtitles
* Incorporating search engine Solr and content management tool Drupal with the database to retrieve videos by full-text search especially in subtitle files
* Incorporating video metadata with the library catalog system

== Shared Vision, Shared Resources: the Curate Institutional Repository ==
* Dan Brubaker Horst, University of Notre Dame
** [http://code4lib.org/conference/2011/JohnsonHorst A Community-Based Approach to Developing a Digital Exhibit at Notre Dame Using the Hydra Framework]
* Julie Rudder, Northwestern University
** no previous presentations

Curate is being collaboratively developed by several institutions in the Hydra community who share the need and vision for a Fedora-backed Institutional Repository. The first release of Curate was a collaboration between Notre Dame and Northwestern University, along with Digital Curation Experts (DCE) - a vendor hired jointly by our two institutions. Powered by the Hydra engine Sufia, the team worked quickly to release the first version of Curate in October 2013 which provides a basic self-deposit system that has support for various content types, collection building, DOI minting, and user profile creation. From the very beginning we have built Curate to be easy to theme and extend in order to ease the process of installation and use by other institutions.

In December 2013, additional partners will join the project including: Indiana University, the University of Cincinnati and the University of Virginia. Each institution contributes resources to the project in order to further our common goal to create a product that fits our needs and has a sustainable future.Together we will tackle additional content types (like complex data, software, media), administrative collections and more.

Our presentation will include:
* a brief demonstration of Curate and technical overview
* why and how we work together
* why build Curate
* the future of the project

== Solr, Cloud and Blacklight ==
* David Jiao, Library Information Systems, Indiana University at Bloomington, djiao@indiana.edu
** No previous code4lib presentations

SolrCloud refers to the distributed capabilities in Solr4. It is designed to offer a highly available, fault tolerant environment by organizing data into multiple pieces that can be hosted on multiple machines with replicas, and providing a centralized cluster configuration and management.

At Indiana University, we are upgrading our Solr backend for our recently released Blacklight-based OPAC system from Solr 1.4 to Solr4, and we also put up efforts to build a private cloud of Solr4 servers. In this talk, I will persent certain features of SolrCloud, including distributed requests, fault tolerance, near real time indexing/searching, and configuration management with Zookeeper, and our experiences of utilizing these features to provide better performance and architecture for our OPAC system, which serves over 7 million bibliographic records to over 100 thousand students and faculty members. I will also discuss some practical lessons learned from our SolrCloud setup/upgrade and the integration of the new SolrCloud to our customized Blacklight system.

== Leveraging XSD's for Reflective, Live Dataset Support in Institutional Repositories ==
* [mailto:msulliva@ufl.edu Mark Sullivan], Library Information Technology, University of Florida
** No previous code4lib presentations

The University of Florida Libraries are currently adding support for active datasets into our METS-based institutional repository software. This ongoing project enables the library to be a partner in current, or long-running, data-driven projects around the university by providing tangible short-term and long-term benefits to the projects. The system assists project teams by storing and providing access to their data, while supporting online filtering and sorting of the data, custom queries, and adding and editing of the data by authorized users. We are also exploring simple data visualizations to allow users to perform basic graphical and geographic queries. Several different schemas were explored including DDI and EML, but ultimately the streamlined approach of using XSD's with some custom attributes was chosen, with all other data residing in the METS file portions. Currently the system is being developed using XSD's describing XML datasets, but this model should easily scale to support SQL datasets or large datasets supported by Hadoop or iRODS.

This work is being integrated in the open source [http://sobek.ufl.edu SobekCM Digital Content Management System] which is built on a pair-tree structure of METS resources with [http://ufdc.ufl.edu/design/webcontent/sobekcm/SobekCM_Resource_Object.pdf rich metadata support] including DC, MODS, MARC, VRACore, DarwinCore, IEE-LOM, GML/KML, schema.org microdata, and many other standard schemas. The system has emphasized online, distributed creation and maintenance of resources including geo-placement and geographic searching of resources, building structure maps (table of contents) visually online, and a broad suite of curator tools.

This work is presented as a model which could be implemented in other systems as well. We will demonstrate current support and discuss our upcoming roadmap to provide complete support.

== Dead-simple Video Content Management: Let Your Filesystem Do The Work ==

* Andreas Orphanides, NCSU Libraries (akorphan (at) ncsu.edu)
** (never led or soloed a C4L presentation)

Content management is hard. To keep all the moving parts in order, and to maintain a layer of separation between the system and content creators (who are frequently not technical experts), we typically turn to content management systems like Drupal. But even Drupal and its kin require significant overhead and present a not inconsiderable learning curve for nontechnical users.

In some contexts it's possible -- and desirable -- to manage content in a more streamlined, lightweight way, with a minimum of fuss and technical infrastructure. In this presentation I'll share a simple MVC-like architecture for managing video content for playback on the web, which uses a combination of Apache's mod_rewrite module and your server's filesystem structure to provide an automated approach to video content management that's easy to implement and provides a low barrier to content updates: friendly to content creators and technology implementors alike. Even better, the basic method is HTML5-friendly, and can be integrated into your favorite content management system if you've got permissions for creating templates.

In the presentation I'll go into detail about the system structure and logic required to implement this approach. I'll detail the benefits and limitations of the system, as well as the challenges I encountered in developing its implementation. Audience members should come away with sufficient background to implement a similar system on their own servers. Implementation documentation and genericized code will also be shared, as available.

== Managing Discovery ==

* Andrew Pasterfield, Senior Programmer/Systems Analyst, University of Calgary Library, ampaster@ucalgary.ca
**No previous code4lib presentations 
In fall 2012 the University of Calgary Library launched a new home page that incorporated a Summon powered
Single Search Box with customized “bento box” results display. Search at the U of C now combines a range of
metadata sources for discovery and customized mapping of a database recommender and LibGuide into a unified
display. Further customizations include a non Google Analytics/non proxy method to log clicks. 

This presentation will discuss the technical details of bringing the various systems together into one display interface to increase discovery at the U of C Library.

http://library.ucalgary.ca

== Sorting it out: a piece of the User Centered Design Process ==

* Cindy Beggs, [http://www.akendi.com/aboutus/management/ Akendi], cindy@akendi.com

This talk is about how to apply a user centered design methodology to the process of creating an information architecture. Participants learn the fundamentals of UCD and how card sorting and reverse card sorting enable us to isolate the content we present on screen from the layouts and visuals of those screens. We talk about ways to identify who will be using the information architecture you are creating and why we need to know how it will be used.

What will attendees takes away from your talk?
The criticality of involving “real” end users in the process of creating an information architecture. The basics of following a user-centered-design process in the creation of best in class, content-rich, digital products.

Cindy Beggs has been working in the “information industry” for over 25 years. A librarian by profession, she has spent decades helping users figure out how to find their way through large bodies of content. Her insights into how people seek information, her empathy for those who find it a challenge and her practical experience helping organizations figure out how to best structure their content contribute to her success as an information architect with both clients and trainees. (http://www.akendi.com/aboutus/management/)

==Implementation of ArchivesSpace in University of Richmond==

*Birong Ho, bho@richmond.edu

University of Richmond implemented its archive collection management ArchivsSpace in the fall, 2013. As a charter member and the Head of Special Collection as the Board member, implementation of such an Open Source Software became a priority.

Several aspects of implementation will be addressed in the talk. Among them, they are Collections and Repository, storage layer including data format, System resources requirements, Technical architecture, Customization, scaling and integrated with other systems in the library.

The customization, scale, and integration with other systems such as Archeon and Exist on campus became a concern will be focused and elaborated in the talk.

==Easy Wins for Modern Web Technologies in Libraries==

*[mailto:trey.terrell@oregonstate.edu Trey Terrell], Analyst Programmer, Oregon State University
** No previous Code4Lib presentations

Oregon State University is currently implementing an updated version of its room reservation system. In its development we've come across and implemented a variety of "easy wins" to make it more responsive, easier to maintain, less expensive to run, and just cooler to experience. While our particular system was in Ruby on Rails, this talk will address general methods and example utilities which can be used no matter your stack.

I'll be talking about things like cache management, reverse proxies, publish/subscribe servers, WebSockets, responsive design, asynchronous processing, and keeping complicated stacks up and running with minimal effort.

==Implementing Islandora at a Small Institution==

*Megan Kudzia, Albion College Library
*Eddie Bachle, Albion College IT
**No previous Code4Lib presentations

Albion College (and particularly the Library/Archives and Special Collections) has a variety of needs which could be met by an open-source Institutional Repository system. Several months and lots of conversations later, we’re continuing to troubleshoot our way through Islandora. We’d like to talk about what has worked for us, where our frustrations have been, whether it’s even possible to install and develop a system like this at a small institution, and where the process has stalled.

As of right now, we do have a semi-working installation. We’re not sure when it will be ready for our end users, but we'll talk about our development process and evaluate our progress.
''Contributions also by Nicole Smeltekop, Albion College Archives & Special Collections''

== PhantomJS+Selenium: Easy Automated Testing of AJAX-y UIs ==

* Martin Haye, California Digital Library, martin.haye@ucop.edu
** Previous Code4Lib Presentation: [http://code4lib.org/conference/2012/collett Beyond code: Versioning data with Git and Mercurial] at Code4Lib 2012 (Martin co-presenting with Stephanie Collett)
* Mark Redar, California Digital Library, mark.redar@ucop.edu

Web user interfaces are demanding ever-more dynamism and polish, combining HTML5, AJAX, lots of CSS and jQuery (or ilk) to create autocomplete drop-downs, intelligent buttons, stylish alert dialogs, etc. How can you make automated tests for these highly complex and interactive UIs?

Part of the answer is PhantomJS. It’s a modern WebKit browser that’s “headless” (meaning it has no display) that can be driven from command-line Selenium unit tests. PhantomJS is dead simple to install, and its blazing speed and server-friendliness make continuous integration testing easy. You can write UI unit tests in {language-of-your-choice} and run them not just in PhantomJS but in Firefox and Chrome, plus a zillion browser/OS combinations at places like SauceLabs, TestingBot and BrowserStack.

In this double-team live code talk, we’ll explain all that while we demonstrate the following in real time:

* Start with nothing.
* Install Selenium bindings for Ruby and Python.
* In each language write a small test of an AJAX-y UI.
* Run the tests in Firefox, and fix bugs (in the test or UI) as needed.
* Install PhantomJS.
* Show the same tests running headless as part of a server-friendly test suite.
* (Wifi permitting) Show the same tests running on a couple different browser/OS combinations on the server cloud at SauceLabs – talking through a tunnel to the local firewalled application.

==New Technologies, Collaboration, & Entrepreneurship in Libraries: Harnessing Their Power to Help Your Library==

* Stephanie Walker – swalker@brooklyn.cuny.edu
* Howard Spivak – howards@brooklyn.cuny.edu
* Alex - Alex@brooklyn.cuny.edu

Academic libraries are caught in budget squeezes and often struggle to find ways to communicate value to senior administration and others. At Brooklyn College Library, we have taken an unusual, possibly unique, approach to these issues. Our technology staff have long worked directly with librarians to develop products that meet library, faculty, and student needs, and we have shared many of our products with colleagues, including an award-winning website, e-resource, and content management system we call 4MyLibrary, which we shared for free with 8 CUNY colleges, and also an easy-to-use book scanner, which has proven overwhelming popular with students, faculty, other librarians, and numerous campus offices. Recently, motivated by budget cuts, we decided that what worked for us might interest other libraries, and working with our Office of Technology Commercialization, we started selling 2 products: our book scanners (at half the price of commercial alternatives), and a hosting service, whereby we could host and support 4MyLibrary for libraries with minimal technology staff. Both succeeded, and yielded major benefits: a steady revenue stream and the admiration and serious goodwill of our senior administration and others. However, this presentation is neither a basic how-to, nor an advertisement. With this presentation, we hope to spur a conversation for broader collaboration, especially regarding new technologies, among libraries. We all have some level of technical expertise, most of us are struggling with rising prices and tight budgets, and many of us are unhappy with various technology products we use, from scanners to our ILS. We believe – and can demonstrate – that with collaboration, we can solve many of our problems, and provide better services to boot.

== Identifiers, Data, and Norse Gods ==

* Ryan Scherle, [http://datadryad.org Dryad Digital Repository], ryan@datadryad.org
** previous Code4Lib talk [http://ryan.scherle.org/papers/2010-2-code4lib-HIVE.ppt HIVE: A New Tool for Working With Vocabularies], at Code4Lib 2011.

ORCID and DataCite provide stable identifiers for researchers and and data, respectively. Each system does a fine job of providing value to its users. But wouldn't it be great if they could link their systems to create something much more powerful? Perhaps even as powerful as a god?

Enter [http://odin-project.eu/ ODIN], The ORCID and DataCite Interoperability Network. ODIN is a two-year project to unleash the power of persistent identifiers for researchers and the research they create. This talk will present recent work from the ODIN project, including several tools that can unleash the godlike power of identifiers at your institution. Current tools include:
* Metadata generator tool: allows repository staff to create DataCite metadata with embedded ORCIDs.
* Claiming tool: assists researchers in claiming their work within the ORCID system.
* ORCID-feed: includes a list of ORCID works on any web page.
* ODIN's HAMR: assists in populating a DSpace repository with ORCIDs. Based on work from a Code4Lib hackathon!

== Armed Bandits in the Digital Library ==

* Roman Chyla, [http://labs.adsabs.harvard.edu/adsabs/ Astrophysics Data System], rchyla@cfa.harvard.edu
** Previous Code4Lib: [http://code4lib.org/conference/2013/chyla Citation search in SOLR and second-order operators]

Many of us are using the excellent Lucene library (or SOLR appliance) to provide search functionality. These systems contain number of features to adjust relevancy ranking of hits, but we may not know how to use them. In this presentation, I'll present the available options - eg. what is the default ranking 'Vector space model, what are the alternatives (eg. BM25) and what are the other options we have to tweak and adjust the ranking of the hits (eg. boost factors, functions). But even if we know how to deploy these adjustments and tweaks, we are still left in dark. We do not know whether the change we've just rolled out had a significant (statistically significant) effect or maybe it was just a waste of time and resources? A/B testing is one option, but there may be a much better one - so called "Multi-Armed Bandits Approach". And in this talk I'd like to show how we are experimenting with this strategy to adjust [http://labs.adsabs.harvard.edu/adsabs/ ADS search engine].

== Building Worker Queues with AWS and Resque ==

* Eric Rochester [http://scholarslab.org Scholars' Lab], erochest@virginia.edu
* Scott Turnbull [http://aptrust.org/ Academic Preservation Trust], scott.turnbull@aptrust.org

A common task in larger systems is to be able to process large input files automatically. Often users can drop those files into a shared directory on AWS or on NFS or another shared drive. Those files need to be processed and potentially integrated into a system. This task has come up recently in the University of Virginia libraries in allowing users to add GIS data to the system and in setting up a system for the Academic Preservation Trust (http://aptrust.org/) that ingests files and resources into the preservation system.

This system is built by loosely coupling a number of different technologies. This allows us to easily interoperate and communicate between different system and programming environments. Because the interfaces are well defined, it’s also fairly simple to switch out technologies as the requirements of the system change.

The process is fairly simple:

First, a Ruby daemon monitors an AWS S3 bucket that others can upload new files into. This daemon creates a Resque status task, adds a marker for the task in a database, and continues monitoring.

Second, Resque mediates incoming job requests and routes them to the appropriate workers which may be in Java, Go, or Ruby. The diversity of technologies that Resque can manage allows great latitude to leverage the appropriate tool for a specific job. While processing, it updates the status for that job and coordinates processing with other jobs.

Finally, a page that is integrated into a larger Rails app provides a novice-user-friendly view of the status of the workers and allows basic tasks such as restarting the job.

This architecture allows us to swap in the technology that best fits each part of the process, and it makes it easier to maintain the system. We use this to integrate and coordinate between tasks handled in Java, Ruby, and Go, and it provides an effective way to interoperate with these programming languages and the respective strengths that they bring to this system.

==Piwik: Open source web analytics==
* Kirk Hess, University of Illinois at Urbana-Champaign (kirkhess@illinois.edu)
** (Code4Lib 2012: [http://code4lib.org/conference/2012/hess| Discovering Digital Library User Behavior with Google Analytics])

While Google Analytics is synonymous with Web Analytics, fortunately today we have many other good options, and one option is Piwik, [http://piwik.org| piwik.org] a simple to install, open-source PHP/MySQL application with a tracking script that will sit alongside Google Analytics tracking the usual clicks, events and variables. In this presentation, I'd like to cover the usual analytics topics and also cover what makes Piwik powerful, such as importing and visualizing web logs from any system to incorporate both past and future data, easily tracking downloads, and the ability to write your own reports or dashboard. The visitor log data is stored securely on your own server so you have control over who looks at the data and how much or how little to keep. With an active and helpful developer community, Piwik has the potential for analytics which makes sense for libraries, not e-commerce.

== Next Generation Catalogue - RDF as a Basis for New Services ==
* Anne-Lena Westrum – digitalutvikling@gmail.com
* Benjamin Rokseth
* Asgeir Rekkavik
* Petter Goksøyr Åsen

Oslo Public Library has converted the entire MARC-catalogue to RDF via the self-made conversion tool MARC2RDF.

[http://digital.deichman.no/data.deichman.no/| data.deichman.no], the enriched RDF version of the library catalogue including its authority files, forms the basis for two different mashups; The Active shelf and the Book recommendation database. The RDF catalogue is linked with various content and the dataset is updated daily to account for additions, deletions and changes made in the MARC catalogue.

[http://vimeo.com/68687814| The Active shelf] is a physical touchscreen device that makes use of open source software, RFID technology, RDF data and external web service APIs to provide information about any library book a patron is curious to know more about.

The Book recommendations database stores book recommendations written by library staff from all over Norway and links them to the RDF-representation of the MARC-catalogue.

==Economics of Scale: Thinking about Metadata Quality and Completeness for Fun and Profit==
* William Hicks, University of North Texas (William.hicks@unt.edu)

The UNT Libraries Digital Collections constitute three internet gateways, The Portal to Texas History, UNT Digital Library, and the Gateway to Oklahoma History, making available to the public a wide range of materials, from photographs and newspapers, to dissertations and recordings of music ensemble performances. The collections disseminate over 500,000 unique items, that were used over 9 millions times last year and with growth trends in both areas shows no signs of slowing.

As the size and scope of our collections has grown, so to has a pressing need to think clearly about the quality of our metadata, the completeness of our records, and the most efficient way of doing metadata entry. Not surprisingly there have been a few things written on the subject and so over the last few months we’ve started writing new code and getting the infrastructure of our metadata editing system to a place where we can begin to test these ideas on our ever expanding dataset. What kinds of questions are we looking to answer, and what types of tools are we building? That’s what this talk will be all about, but here are a few ideas to ponder:

* What kinds of tools have we built, or can we employ to standardize data entry and aid the user in their input needs?
* How close does a metadata record come to a “completeness” standard? What does that even look like? What are the implications when we look at such a standard at scale?
* If we can identify what we think a “quality” metadata record “is”, historically speaking, how close do we get to that ideal?
* Does an item’s history matter? Can we quantify it and locate value in change through time?
* What are the economic costs of metadata entry? If we have enough quantifiable measures about the types of objects in our systems, and we can profile our data entry personnel, what can this say about optimizing staff time and return on investment?
* What sort of priorities are we setting for ourselves when we treat all items as equal, when clearly some types of materials get vastly more use by the public.
* Finally what kinds of analysis tools might we develop to gauge our overall metadata “health,” to steer projects, or to ultimately improve our systems for our end user’s needs?

Most of our questions are still quite open ended, and honestly we are just getting started down this road. But as digital collections grow, and library budgets realign or shrink, it becomes increasingly important to back up our assertions and opinions with numbers, and find more efficient ways to work with the resources we have.

==More Like This: Approaches to Recommending Related Items using Subject Headings==
* Kevin Beswick, NCSU Libraries (kdbeswic@ncsu.edu)
** No previous code4lib presentations

With a significant portion of the collection at our new Hunt Library being housed in an automated storage and retrieval system, several of us at NCSU Libraries have begun looking at ways to replace and improve upon the classic shelf browsing experience in order to make it easier for patrons to browse related materials. Our goal is to mimic popular services like Amazon and Netflix, which utilize recommendation engines to make it easy for users to find items similar to a particular item of interest. While there have been previous efforts in libraries to recreate this experience using circulation or call number data, we are currently investigating algorithms that focus on use of subject headings. Use of subject headings as an alternative can be particularly helpful in the case of electronic materials that do not always have call numbers or circulation data. In this talk, I will share:

* Details of the proposed algorithms
* How these algorithms were quickly and easily implemented using Solr.
* Our evaluation process and its outcomes in terms of the effectiveness of the algorithms.
* How this has (or could) impact presentation of recommended items in our discovery layer.

[[:Category:Code4Lib2014]]