https://wiki.code4lib.org/api.php?action=feedcontributions&user=Kevinreiss&feedformat=atomCode4Lib - User contributions [en]2024-03-29T10:22:41ZUser contributionsMediaWiki 1.26.2https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&diff=420182015 Prepared Talk Proposals2014-11-07T23:04:50Z<p>Kevinreiss: /* BYOB: Build Your Own Bootstrap */</p>
<hr />
<div>Code4lib 2015 is a loosely-structured conference that provides people working at the intersection of libraries/archives/museums/cultural heritage and technology with a chance to share ideas, be inspired, and forge collaborations. For more information about the Code4lib community, please visit http://code4lib.org/about/. <br />
The conference will be held at the Portland Hilton & Executive Tower in Portland, Oregon, from February 9-12, 2015.<br />
<br />
'''Proposals for Prepared Talks:'''<br />
<br />
We encourage everyone to propose a talk.<br />
<br />
Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:<br />
* Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software<br />
* Tools and technologies – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)<br />
* Technical issues - Big issues in library technology that should be addressed or better understood<br />
* Relevant non-technical issues – Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc.<br />
<br />
Proposals can be submitted through Friday, November 7, 2014 at 5pm PST (GMT−8). Voting will start on November 11, 2014 and continue through November 25, 2014. The URL to submit votes will be announced on the Code4Lib website and mailing list and will require an active code4lib.org account to participate. The final list of presentations will be announced in early- to mid-December.<br />
<br />
'''Proposals for Prepared Talks:'''<br />
<br />
Log in to the Code4lib wiki and edit this wiki page using the prescribed format. If you are not already registered, follow the instructions to do so.<br />
Provide a title and brief (500 words or fewer) description of your proposed talk.<br />
If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist voters in opening the conference to new presenters.<br />
<br />
Please follow the formatting guidelines:<br />
<br />
<pre><br />
<br />
== Talk Title: ==<br />
<br />
* Speaker's name, email address, and (optional) affiliation<br />
* Second speaker's name, email address, and affiliation, if second speaker<br />
<br />
Abstract of no more than 500 words.<br />
<br />
</pre><br />
<br />
'''Talk Proposals'''<br />
== Zines + Gamification = Awesomest Metadata Literacy Outreach Event Ever! ==<br />
<br />
* [http://www.JenniferHecker.info Jennifer Hecker], jenniferraehecker@gmail.com, [http://www.lib.utexas.edu/subject/zines University of Texas Libraries] & [http://www.AustinFanzineProject.org Austin Fanzine Project]<br />
* [http://anomalily.net/ Lillian Karabaic], librarian@iprc.org, [http://www.iprc.org/ Independent Publishing Resource Center] (Portland)<br />
<br />
In academic libraries, and elsewhere, the popularity of zine (a magazine produced for love, not profit) collections is on the rise. At the same time, metadata literacy is becoming an increasingly important skill, helping people navigate and understand digital environments and interactions. We have found a way to teach metadata literacy to the general public that isn’t super-boring – in fact, we’ve made it downright fun!<br />
<br />
First, volunteer zine librarian Lillian Karabaic of Portland’s Independent Publishing Resource Center facilitated the creation of a gamified cataloging interface for the IPRC’s annual Raiders of the Lost Archives backlog-busting 24-hour volunteer cataloging event.<br />
<br />
Then, archivist Jennifer Hecker facilitated the adaptation of the IPRC’s game for use in a similar, but also very different context – promoting UT Libraries newly-acquired zine collections. The main goal of the academic-library-based event was increasing excitement around the collections, but with the side goal of building metadata literacy, and introducing an understanding of library cataloging issues.<br />
<br />
The Texas modification also conforms to the xZINECOREx metadata schema developed by the national [http://zinelibraries.info/ Zine Librarians Interest Group], and triggered interesting conversations with the Libraries’s cataloging department about evolving metadata standards and how to incorporate the products of crowd-sourcing projects into existing workflows.<br />
<br />
Both games will be demoed.<br />
<br />
We have never presented at Code4lib.<br />
<br />
== Do the Semantic FRBRoo ==<br />
* Rosie Le Faive, rlefaive@upei.ca, University of Prince Edward Island<br />
<br />
[http://www.islandora.ca Islandora] is great for creating repositories of any data type, but how can you model meaningful relationships between digital objects and use them to tell a story?<br />
<br />
At UPEI, I’m assembling an ethnography of Prince Edward Island’s traditional fiddle music that includes musical clips, video clips, oral histories, musical notation, images, and ethnographic commentaries. In order to present an exhibition-style site, I’m tying these digital objects together via the people, places, events, tunes and topics that they share or describe. <br />
<br />
To describe the relationships, I’m extending Islandora to use [http://www.cidoc-crm.org/frbr_inro.html FRBRoo], a vocabulary that combines the FRBR model with CIDOC-CRM, the the object-oriented museum documentation ontology. These modules being developed will allow other researchers to create a structured, navigable digital repository of diverse object types, that uses Islandora as an exhibition platform. <br />
<br />
== Our $50,000 Problem: Why Library School? ==<br />
* Jennie Rose Halperin, jhalperin@mozilla.com, Mozilla Corporation<br />
<br />
57 library schools in the United States are churning out approximately 100 graduates per year, many with debt upwards of $50,000. According to ONet, [http://www.inthelibrarywiththeleadpipe.org/2011/is-the-united-states-training-too-many-librarians-or-too-few-part-1/ 84% of library jobs in the US require an MLS.] The library profession is [http://dpeaflcio.org/programs-publications/issue-fact-sheets/library-workers-facts-figures/) 92% white and 82% female and entry-level librarians can expect to make $32,500 per year.]<br />
<br />
Contrasted with developers, who are almost [http://www.ncwit.org/blog/did-you-know-demographics-technical-women 90% male] and can expect to make [http://www.forbes.com/sites/jennagoudreau/2011/06/01/best-entry-level-jobs/ $70,000 in an entry-level position,] these numbers are dismal.<br />
<br />
According to a recent survey, the top skill that outgoing library students want to know is “programming” and yet many MLS programs still consider Microsoft Word an essential technology skill.<br />
<br />
What is going on here? Why do we accept this fate, where mostly female debt-burdened professionals continue to be thrown onto the work force without the education their expensive degrees promised?<br />
<br />
As a community we need to come together to stop this cycle. We need to provide better support and mentorship to diversify and keep the profession relevant and help librarianship move into the future it deserves.<br />
<br />
This talk will walk through the challenges of navigating a hostile employment environment as well as present models for better development and future state imagining.<br />
<br />
== No cataloging software? Need more than Dublin Core? No problem!: Experiences with CollectiveAccess ==<br />
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University<br />
* Rachel Wittmann, rwittma@clemson.edu, Clemson University<br />
<br />
Clemson University Libraries has implemented the open-source software CollectiveAccess for customized digital collection needs. CollectiveAccess is an open-source project with the goal of providing a flexible way to manage and publish museum and archival collections. There are several applications associated with the projects; most used are: Providence (for cataloging and entering metadata) and Pawtucket (for displaying objects in a collection for the public). It has many profiles readily available for installing with existing library standards, such as Dublin Core, and there is a robust syntax for creating your own profiles to fit custom tailored metadata schemas. Plus, the user interface allows you to modify the metadata profile quickly and easily.<br />
<br />
In this talk, we will discuss:<br />
* Our experiences with installing Providence and creating an installation profile that satisfies the needs of many of the Clemson Libraries digital archiving processes. <br />
* The stumbling blocks experienced in that process and how they were resolved.<br />
* The available plugins sourcing widely used authorities, such as Library of Congress thesauri and GeoNames.org, and how they have been used by our projects. <br />
* A brief overview of the export and import functions and also current workflow practices within Providence.<br />
* Future plans & the role of CollectiveAccess at Clemson University Libraries<br />
<br />
== Getting ContentDM and Wordpress to Play Together ==<br />
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University<br />
<br />
Clemson University Libraries has a very strong program for digitizing and archiving photographs, and the Digital Imaging team processes many hundreds of photographs every month. These images are managed using different methods, including ContentDM, a digital collection manager.<br />
<br />
ContentDM provides various methods for searching and displaying photographs, along with their metadata. However, recent initiatives have resulted in the need to leverage those collections into exhibits displayed on other library-related websites, such as our Special Collections unit. The Clemson Libraries has invested heavily in Wordpress as our content management system of choice, and it seemed most efficient not to have to export and import images into our Wordpress sites in order to provide exhibited images.<br />
<br />
Fortunately, ContentDM has provided an API to many of their functions, allowing the extraction of metadata and even rescaled images through URLs. This project has been developing a plugin for Wordpress that integrates with ContentDM through shortcodes that Wordpress editors can easily include in their content. These shortcodes allow editors to choose how many images, which images from which collections, thumbnail sizes, etc. to display in different gallery styles. Plans are for it to allow integration with different plugins such as Fancybox and Masonry.<br />
<br />
In this presentation, I will demonstrate the current state of the plugin and discuss future plans. <br />
<br />
==Refinery — An open source locally deployable web platform for the analysis of large document collections==<br />
<br />
* [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com<br />
<br />
Refinery is an open source web platform for the analysis of large unstructured document collections. It extracts meaningful semantic themes within documents also known as "topics" which can be thought of as word clouds composed of terms that highly co-occur with one another. Once this semantic index is formed, one can extract relevant documents related to these topics and further refine their contents through a summarization process that allows users to search for phrases that are relevant to them within the corpus. The goal of Refinery is to make this whole process easier and to provide some of the latest scalable versions of these learning algorithms in an intuitive web-based interface. Refinery is also meant to be run locally, thus bypassing the need for securing document collections over the internet. The talk will go through some of the technologies involved and a demo of the app.<br />
<br />
For more info check out http://www.docrefinery.org.<br />
<br />
==Drupal 8 — Evolution & Revolution==<br />
<br />
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com<br />
<br />
Drupal 8 is in beta and nearing release. Among its many features, it notably has become more developer friendly through its adoption of the Symfony PHP framework along with Symfony's outstanding set of libraries (like Guzzle) and tools (like Composer). And, in implementing the Twig theming system, it is can begin to escape PHPtemplate. These moves also make it easier to create headless systems that uses Angular.js and other systems for presentation, or even forgo presentation entirely.<br />
<br />
From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.<br />
<br />
==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==<br />
<br />
* [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]], stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]<br />
<br />
GameSalad is a popular tool for developing mobile and desktop games with little actual programming. In this presentation, Stan Bogdanov breaks down the development process he followed while building [https://github.com/stanrb/mobiLit mobiLit], a mobile app with the goal of being the first open-source gamified information literacy app to be used as part of a college-level information literacy curriculum. He will go through the basics of using GameSalad to create an app that can be easily customized by non-programmers and the instructional principles used to teach the material in a mobile medium. Stan will also go through two qualitative design studies he did on the app and discuss their results and the lessons learned from building mobiLit. The session will conclude with an overview of the next steps for the [https://github.com/stanrb/mobiLit mobiLit project].<br />
<br />
==The Impossible Search: Pulling data from multiple unknown sources==<br />
<br />
* Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com <br />
<br />
It's easy to search data you know the structure of, but what if you need to pull in data from sources that don't have a standard structure. The ability to search community events along with your standard catalog search results is an example, but often the only way to pull these events is through XML, JSON, (Insert structured format here), or even just raw html. But how do you get that structure? That simple question is what makes this impossible. The process to define and process this structure takes a lot of manual labor, especially if the data you are pulling is just HTML, and then every time you add data to the index you have to run all the data through a script to pull in data in a format Solr or an other index can use. This talk will focus on Solr, but the principles explained will apply to many other indexes.<br />
<br />
==What! You're Not Using Docker?==<br />
<br />
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com<br />
<br />
Boring part: Docker[1] is a container system that provides benefits similar to virtualization with only a fraction of the overhead. Scintillating part: Docker can host between four to six times the number of service instances than systems such as Xen or VMWare on a given piece of hardware. But thats not all! Docker also makes it simple(r) to create transportable instances, so you can spin up development servers on your laptop.<br />
<br />
*[1]https://www.docker.com/<br />
<br />
== Video Accessibility, WebVTT, and Timed Text Track Tricks ==<br />
<br />
* Jason Ronallo, jronallo@gmail.com, NCSU Libraries<br />
<br />
Video on the Web presents new challenges and opportunities. How do you make your video more accessible to those with various disabilities and needs? I'll show you how. This presentation will focus on how to write and deliver captions, subtitles, audio descriptions, and timed metadata tracks for Web video using the WebVTT W3C standard. Encoding timed text tracks in this way opens up opportunities for new functionality on your websites beyond accessibility. The presentation will show some examples of the potential for using timed text tracks in creative ways. I'll cover all the HTML and JavaScript you will need to know as well as some of the CSS and other bits you could probably do without but are too fun to pass up.<br />
<br />
== Categorizing Records with Random Forests ==<br />
<br />
* Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library<br />
Academic libraries are increasingly responsible for providing ingest, search, discovery, and analysis for data sets. Emerging techniques from data science and machine learning can provide librarians and developers with an opportunity to generate new insights and services from these document collections. This presentation will provide a brief overview of common machine learning classification techniques, then dive into a more detailed example using a random forest to assign keywords to research data sets. The talk will emphasize the insight that can be gained from machine learning rather than the inner workings of the algorithms. The overall goal of this presentation is to provide librarians and developers with the context to recognize an opportunity to apply machine learning categorization techniques at their home campuses and organizations. <br />
<br />
== Data Science in Libraries ==<br />
<br />
* Devon Smith, smithde@oclc.org, OCLC<br />
<br />
Data Science is increasing in buzz and hype. I'll go over what it is, what it isn't, and how it fits in libraries.<br />
<br />
== PDF metadata extraction for academic literature == <br />
<br />
* Kevin Savage, kevin.savage at mendeley.com, Mendeley<br />
* Joyce Stack, joyce.stack at mendeley.com, Mendeley<br />
<br />
Mendeley recently added a, "document from file," endpoint to its API which attempts to extract metadata such as title and authors directly from PDF files. This talk will describe at a high level the machine learning methods we used including how we measured and tuned our model. We will then delve more deeply into our stack, the tools we used, some of the things that didn't work and why PDFs are the worst thing ever to compute over.<br />
<br />
== Giving Users What They Want: Record Grouping in VuFind ==<br />
<br />
* Mark Noble, mark@marmot.org, [//www.marmot.org Marmot Library Network]<br />
<br />
In 2013, Marmot did extensive usability studies with patrons to determine what was difficult in the catalog. Many patrons had problems sifting through all of the various formats and editions of a title. In 2014 we developed a method for [//mercury.marmot.org/Union/Search?lookfor=divergent grouping records] so only a single work is shown in search results and all formats and editions are listed under that work. We will discuss our definition of a 'work' based on FRBR principles; combining meta data from MARC records with metadata from other sources like OverDrive; the technical details of Record Grouping; the design decisions made during implementation; and the reaction from users and staff.<br />
<br />
== Topic Space: a mobile augmented reality recommendation app ==<br />
<br />
* Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign<br />
<br />
The Topic Space module (http://minrvaproject.org/modules_topicspace.php ) was developed with an IMLS Sparks! Grant to investigate augmented reality technologies for in-library recommendations. The funding allowed for sustained university community collaboration by the University Library, the Graduate School of Library and Information Science, as well as graduate student programmers sourced from the Department of Computer Science. Collaborators designed app functionality and identified relevant open source libraries that could power optical character recognition (OCR) functionality from within the mobile phone.<br />
<br />
Topic space allows a user to take a picture of an item's call number in the book stacks. The module will show the user other books that are relevant but that are not shelved nearby. It can also show users books that are normally shelved here but that are currently checked out. Recommendations are based on Library of Congress subject headings and ILS circulation data which indicate recommendation candidates based on total check-outs. <br />
<br />
Research questions included development of back end (server-side) pattern matching algorithms for recommendations, and a rapid formative evaluation of interface design that would provide optimal user experience for navigation of the book stacks as a context to recommendations.<br />
<br />
Along with the Topic Space native app, grant collaborators prototyped web based recommendations which could serve as a new way of providing readers advisory and “more like this” recommendations from discovery interfaces accessed through desktop browsers. Outcomes of the grant include the availability of the [https://play.google.com/store/apps/details?id=edu.illinois.ugl.minrva Topic Spaces module within Minrva app on the Android Play store] and an experimental [http://backbonejs.org/ Backbone.js] based [http://minrva-dev.library.illinois.edu Topic Space web app].<br />
<br />
== Leveling Up Your Git Workflow ==<br />
<br />
* Megan Kudzia, moneill@albion.edu, Albion College Library<br />
* Kate Sears, eks11@albion.edu, Albion College Library<br />
<br />
Have you started experimenting with Git on your own, but now you need to include others in your projects? Learn from our mistakes! Transitioning from a one-person git workflow and repo structure, to a structure that includes multiple people (including student workers), is not for the faint of heart. We'll talk about why we decided to work this way, our path to developing a git culture amongst ourselves, conceptual and technical difficulties we've faced, what we learned, and where we are now. Also with pretty pictures (aka workflow drawings).<br />
<br />
== Drone Loaning Program: Because Laptops are so last century ==<br />
<br />
* Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries<br />
* Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries<br />
<br />
At Univ. Maryland we are in the very early stages of looking into allowing our student body get their hands on a drone. Yes that's right we will let students take out a drone for n amount of hours to work on projects of their choosing. The talk will talk about the logistics of getting a program of this sort from concept to "Is the drone available?". If people sign waivers we will also promise not to crash the drone into code4lib attendees.<br />
<br />
== Got Git? Getting More Out of Your GitHub Repositories ==<br />
<br />
* Terry Brady, twb27@georgetown.edu, Georgetown University Library<br />
<br />
This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories. <br />
<br />
In additional to all of the great benefits of using Git for code management, the GitHub interface provides a powerful set of tools to showcase a project and to keep your users informed of developments to your project. These tools can assist with marketing and outreach - turning your code repository into a focus of conversation!<br />
<br />
* [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]<br />
* [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]<br />
* [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]<br />
* [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]<br />
* Gists for code sharing<br />
* Private Repositories and Organizational Groups<br />
* Pull Request Conversation Tracking<br />
* Customized Issue management<br />
<br />
== Quick Wins for Every Department in the Library - File Analyzer! ==<br />
<br />
* Terry Brady, twb27@georgetown.edu, Georgetown University Library<br />
<br />
The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.<br />
* Analyzing Marc Records for the Cataloging department<br />
* Transferring ILS invoices for the University Account System for the Acquisitions department <br />
* Delivering patron fines to the Bursar’s office for the Access Service department<br />
* Summarizing student worker timesheet data for the Finance department<br />
* Validating COUNTER compliant reports for the Electronic Resources department<br />
* Generating ingest packages for the Digital Services department<br />
* Validating checksums for the Preservation department<br />
<br />
Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!<br />
<br />
==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==<br />
<br />
* [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor<br />
<br />
The transition from paper maps to digital ones changed much more than the maps themselves; it changed the very foundation of how we work and how we find each other. Now maps are transforming again. The Geospatial World is moving from GIS systems that are institutionally-focused, expensive, feature-burdened, and binds data into a complicated and demanding user-hostile interface. From this transition from digital to web-based digital geospatial tools has come growth and development in new forms of map-based investigative journalism, activism, scholarship, and business ventures. This talk will highlight the conditions and strategies that made these changes possible as a means to draw a path by which librarians through our own work may follow, dragons notwithstanding. <br />
<br />
== Building Your Own Federated Search ==<br />
<br />
* Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco<br />
<br />
Advances in modern browsers have created some interesting possibilities for federated search. This presentation will cover common techniques and pitfalls in building a federated search. We will discuss what principles guided our decisions when implementing our own federated search. We will show tools we've built and our findings from building and using experimental prototypes.<br />
<br />
Your higher education institution likely offers dozens of online resources for educators, students, researchers, and the public. And each of these online resources likely has its own search tool. But users can't be expected to search in dozens of different interfaces to find what they're looking for. A typical solution for this issue is federated search. <br />
<br />
== Indexing Linked Data with LDPath ==<br />
<br />
* Chris Beer, cabeer@stanford.edu, Stanford University Libraries<br />
<br />
LDPath [1] is a simple query language for indexing linked open data, with support for caching, content negotiation, and integration with non-RDF endpoints. This talk will demonstrate the features and potential of the language and framework to index a resource with links into id.loc.gov, viaf.org, geonames.org, etc to build an application-ready document.<br />
<br />
[1] http://marmotta.apache.org/ldpath/language.html<br />
<br />
== Show Me the Money: Integrating an LMS with Payment Providers ==<br />
<br />
* Josh Weisman, Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group<br />
<br />
In order to provide an easy and convenient way for patrons to pay fines, we are exploring ways to integrate the library management system with online payment providers such as PayPal. With many LMS systems being designed and developed for the cloud, we should be able to provide the frictionless user experience our patrons have come to expect from online transactions. In this session we'll discuss strategies for integration and review a sample application which uses REST APIs from a library management system to integrate with PayPal.<br />
<br />
== Shibboleth Federated Authentication for Library Applications: ==<br />
<br />
* Scott Fisher, scott.fisher@ucop.edu, California Digital Library<br />
* Ken Weiss, ken.weiss@ucop.edu, California Digital Library<br />
<br />
Shibboleth is the most widely-used method to provide single-sign-on authentication to academic applications where users come from many different institutions. Shibboleth, the InCommon education and research trust framework, and the SAML protocol comprise a very powerful - but very complicated - solution to this very complicated problem. Scott and Ken have implemented Shibboleth for multiple library applications. They will share their understanding of the good, the bad, and the underlying spaghetti that makes it all work. Ken will discuss some of the technical aspects of the solution, touching on optimal and non-optimal use cases, administrative challenges, and authorization concerns. Scott will describe the implementation pattern for multi-institution single-sign-on that the California Digital Library has evolved, using the recently released Dash application (http://dash.cdlib.org) as an example.<br />
<br />
==Scientific Data: A Needs Assessment Journey==<br />
<br />
*[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History<br />
<br />
While surveying digital research and collections data in the research science divisions at the American Museum of Natural History in NYC (as a part of my [http://ndsr.nycdigital.org/ National Digital Stewardship Residency] project), I have come across the big data hogs (genome sequencing and CT scanning) and the little pieces of data (images, publications), all equally important to not only scientific discovery, but as nodes in the history of science. <br />
<br />
In this session, I will discuss the development of my needs assessment surveys for scientific datasets and the interview process with Museum curators and researchers as background, seguing into an explanation of the results. I will then combine my findings into preliminary selection criteria to choose tools for digital preservation and management unique to scientific datasets. This will brooke a discussion on emerging standards, tools, and technologies in big data, specific to research science. <br />
<br />
I will conclude with preliminary findings on emerging technology that can be used to answer concerns surrounding the management and digital preservation of these data. I am hoping the Q&A session can be used to both answer questions about my project, and function as a way for you (the larger tech-savy library community) to discuss the tools I’ve touched on in this talk. <br />
<br />
== Feminist Human Computer Interaction (HCI) in Library Software ==<br />
<br />
* Bess Sadler, bess@stanford.edu, Stanford University Libraries<br />
<br />
Libraries are not neutral repositories of knowledge. Library classification systems and search technologies tend to reflect the inequalities, biases, ethnocentrism, and power imbalances of the societies in which they are built [1]. How might we better resist these tendencies in the library software we create? This talk will examine some qualities of feminist HCI (pluralism, self-disclosure, participation, ecology, advocacy, and embodiment) [2] through the lens of library software. <br />
<br />
[1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.<br />
<br />
[2] Bardzell, Shaowen. Feminist HCI: Taking Stock and Outlining an Agenda for Design. CHI 2010: HCI For All. http://dmrussell.net/CHI2010/docs/p1301.pdf<br />
<br />
== Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==<br />
<br />
* Audrey Altman, audrey at dp.la, Digital Public Library of America<br />
* Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America<br />
* Mark Breedlove, mb at dp.la, Digital Public Library of America<br />
<br />
The Digital Public Library of America aggregates metadata for over 8 million objects from more than 24 direct partners, or Hubs, using its Metadata Application Profile (MAP), an RDF metadata application profile based on the Europeana Data Model. After working with the initial system for harvesting, mapping and enhancing our Hub’s metadata for a year, we realized that it was inadequate for working with data at this scale. There were architectural issues; it was opaque to non-developer and partner staff; there were inadequate tools for quality assurance and analysis; and the system was unaware that it was working with RDF data. As the network of Hubs expanded and we ingested more metadata, it became harder and harder to know when or why a harvest, a mapping task, or an enrichment went wrong because the tools for quality assurance were largely inadequate. <br />
<br />
The DPLA Content and Technology teams decided to develop a new system from the ground up to address those problems. Development of Heidrun, the internal version of the new system, started in October 2014. Heidrun’s goals are to make it easier for us to harvest and map metadata from various sources and in variety of schemas to the DPLA MAP, to better enrich that metadata using external data sources, and to actively involve our partners in the ingestion process through access to better QA tools. Heidrun and its componentry are built on Ruby on Rails, Blacklight, and ActiveTriples. Our presentation will give some background on our design principles and processes used during development, the architecture of the system, and its functionality. We plan to release a version of Heidrun and its components as a generalized metadata aggregation system for use by DPLA Hubs and others working to aggregate cultural heritage metadata.<br />
<br />
== OS or GTFO: Program or Perish ==<br />
*Tessa Fallon, tessa.fallon@gmail.com<br />
<br />
Description TBD<br />
<br />
== Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==<br />
* Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries<br />
Would your library like to have large digital signage that displays dynamic information such as library hours, weather, room availability, and more? Have you looked into purchasing large digital signage, only to be turned off by the high price tag and lack of customization available with commercial solutions? Our library has developed a cheap and effective alternative to these systems using HTML 5 authoring software, a large TV, and freely-available APIs from Google, Springshare, and others. At this session, you’ll learn about the system that we have in place for displaying dynamic and easily-updatable information on our library’s large digital display, and how you can easily create something similar for your library.<br />
<br />
== REPOX: Metadata Blender ==<br />
<br />
* John Mignault, jmignault@metro.org, Empire State Digital Network<br />
<br />
With the growth in the number of hubs providing metadata to the Digital Public Library of America, many of them are using REPOX, a tool originally created for the Europeana project, to aggregate disparate metadata feeds and transform them into formats suitable for ingest into DPLA. The Empire State Digital Network, the forthcoming DPLA service hub for NY state, is using it to prepare for our first ingest into DPLA in early 2015. We'll take a look at REPOX and its capabilities and how it can be useful for ingesting and transforming metadata, and also discuss some things we've learned in massaging widely varied metadata feeds.<br />
<br />
== Beyond Open Source ==<br />
<br />
* Jason Casden, jmcasden@ncsu.edu, NCSU Libraries<br />
* Bret Davidson, bddavids@ncsu.edu, NCSU Libraries<br />
<br />
The Code4Lib community has produced an increasingly impressive collection of open source software over the last decade, but much of this creative work remains out of reach for large portions of the library community. Do the relatively privileged institutions represented by a majority of Code4Lib participants have a professional responsibility to support the adoption of their innovations?<br />
<br />
Drawing from old and new software packaging and distribution approaches (from freeware to Docker), we will propose extending the open source software values of collaboration and transparency to include the wide and affordable distribution of software. We believe this will not only simplify the process of sharing our applications within the Code4Lib community, but also make it possible for less well resourced institutions to actually use our software. We will identify areas of need, present our experiences with the users of our own open source projects, discuss our attempts to go beyond open source, and make an argument for the internal value of supporting and encouraging a vibrant library ecosystem.<br />
<br />
[[Category:Code4Lib2015]] <br />
[[Category:Talk Proposals]]<br />
<br />
== Making It Work: Problem Solving Using Open Source at a Small Academic Library ==<br />
<br />
* Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology<br />
* Max King, mking9@iit.edu, Illinois Institute of Technology<br />
<br />
The Illinois Institute of Technology campus was added to the National Register of Historic Places in 2005, and contains a building, Mies van der Rohe's S.R. Crown Hall, that was named a National Historic Landmark in 2001. Creating a digital resource that can adequately showcase the campus and its architecture is challenge enough in and of itself, but doing so as a two-person team of relative newcomers, at a university library without dedicated programmers on staff, ups the ante considerably.<br />
The challenges of technical know-how, staff time, and funding are nothing new to anyone working on digital projects at a university library, and are amplified when doing so at a smaller institution. This talk covers the conception, development, and design of the campus map site that was built, concentrating on the problem-solving strategies developed to cope with limited technical and financial resources.<br />
We'll talk about our approach to development with Open Source software, including Omeka, along with the Neatline and Simile Timeline plugins. We'll also discuss the juggling act of designing for mobile mapping functionality without sacrificing desktop design, weighing the costs of increased functionality versus our ability to time-effectively include that functionality, and the challenge of building a site that could be developed iteratively, with an eye towards future enhancement and sustainability. Finally, we’ll provide recommendations for other librarians at smaller institutions for their own efforts at digital development.<br />
<br />
== Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==<br />
<br />
* Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art<br />
<br />
The Museum of Modern Art has amassed a large collection of audiovisual materials over its many decades of existence. In order to preserve these materials, much of the audiovisual collection has been digitized. This is a complex process involving numerous steps and devices, and the methods used for digitization can have an effect on the quality of the file that is preserved. Therefore, knowing exactly how something was digitized is critical for future stewards of these objects to be able to properly care for and preserve them. However, detailed technical information about the processes involved in the digitization of audiovisual materials is not defined explicitly in most metadata schemas used for audiovisual materials. In order to record process history using existing metadata standards, some level of creativity is required to allow existing standards to express this information.<br />
<br />
This talk will detail different metadata standards, including PBCore, PREMIS, and reVTMD, that can be implemented as methods of recording this information. Specifically, the talk will examine efforts to integrate this metadata into the Museum of Modern Art’s new digital repository, the DRMC. This talk will provide background on the DRMC as well as MoMA’s specific institutional needs for process history metadata, then discuss different metadata implementations we have considered to document process history.<br />
<br />
== Pig Kisses Elephant: Building Research Data Services for Web Archives ==<br />
<br />
* Jefferson Bailey, jefferson@archive.org, Internet Archive<br />
* Vinay Goel, vinay@archive.org, Internet Archive<br />
<br />
More and more libraries and archives are creating web archiving programs. For both new and established programs, these archives can consist of hundreds of thousands, if not millions, of born-digital resources within a single collection; as such, they are ideally suited for large-scale computational study and analysis. Yet current access methods for web archives consist largely of browsing the archived web in the same manner as browsing the live web and the size of these collections and complexity of the WARC format can make aggregate analysis difficult. This talk will describe a project to create new ways for users and researchers to access and study web archives by offering extracted and post-processed datasets derived from web collections. Working with the 325+ institutions and their 2600+ collections within the Archive-It service, the Internet Archive is building methods to deliver a variety of datasets culled from collections of web content, including extracted metadata packaged in JSON, longitudinal link graph data, named entities, and other types of data. The talk will cover the technical details of building dataset production pipelines with Apache Pig, Hadoop, and tools like Stanford NER, the programmatic aspects of building data services for archives and researchers, and ongoing work to create new ways to access and study web archives.<br />
<br />
== Awesome Pi, LOL! ==<br />
<br />
* Matt Connolly, mconnolly@cornell.edu, Cornell University Library<br />
* Jennifer Colt, jrc88@cornell.edu, Cornell University Library<br />
<br />
Inspired by Harvard Library Lab’s “Awesome Box” project, Cornell’s Library Outside the Library (LOL) group is piloting a more automated approach to letting our users tell us which materials they find particularly stunning. Armed with a Raspberry Pi, a barcode scanner, and some bits of kit that flash and glow, we have ventured into the foreign world of hardware development. This talk will discuss what it’s like for software developers and designers to get their hands dirty, how patrons are reacting to the Awesomizer, and LOL’s not-afraid-to-fail philosophy of experimentation.<br />
<br />
== You Gotta Keep 'em Separated: The Case for "Bento Box" Discovery Interfaces ==<br />
<br />
* Jason Thomale, jason.thomale@unt.edu, University of North Texas Libraries<br />
<br />
I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.<br />
<br />
The thing is, practically all of us--in academic libraries at least--have a similar set up for discovery, with just a few variations, and so talking about it still seems useful. Stop me if this sounds familiar. You've got a single search box on the library homepage as a starting point for discovery. And it's probably a tabbed affair, with an option for searching the catalog for books, an option for searching a discovery service for articles, an option for searching databases, and maybe a few others. Maybe you have an option to search everything at once--probably the default, if you have it. And, if you're a crazy hepcat, maybe you ''only'' have your one search that searches everything, with no tabs.<br />
<br />
Now, the question is, for your "everything" search, are you doing a combined list of results, or are you doing it bento-box style, with a short results list from each category displayed in its own compartment?<br />
<br />
At UNT, we've been holding off on implementing an "everything" search, for various reasons. One reason is that the evidence for either style hasn't been very clear. There's this persistent paradox that we just can't reconcile: users tell us, through word and action, that they prefer searching Google, yet, libraries aren't Google, and there are valid design reasons why we shouldn't try to oversimplify our discovery interfaces to be like Google. And there's user data that supports both sides.<br />
<br />
Holding off on making this decision has granted us 2 years of data on how people use our tabbed search interface that does ''not'' include an "everything" search. Recently I conducted a thorough analysis of this data--specifically the usage and query data for our catalog and discovery system (Summon). And I think it helps make the case for a bento box style discovery interface. To be clear, it isn't exactly the smoking gun that I was hoping for, but the picture it paints I think is telling. At the very least, it points away from a combined-results approach.<br />
<br />
I'm proposing a talk discussing the data we've collected, the trends we've seen, and what I think it all means--plus other reasons that we're jumping on the "bento box" discovery bandwagon and why I think "bento box" is at this point the path that least sells our souls.<br />
<br />
== Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift ==<br />
<br />
* Ashley Blewer!, ashley.blewer@gmail.com<br />
<br />
Checksum technology is used all over the place, from git commits to authenticating Linux packages. It is most commonly used in the digital preservation field to monitor materials in storage for changes that will occur over time or used in the transmission of files during duplication. But do you even checksum, bro? I want this talk to move checksums from a position of mysterious macho jargon to something everyone can understand and want to use. I think a lot of people have heard of checksum but don’t know where to begin when it comes to actually using it at their institution. And cryptography is hella intimidating! This talk will cover what checksums are, how they can be integrated into a library or archival workflow, protecting collections requiring additional levels of security, algorithms used to verify file fixity and how they are different, and other aspects of cryptographic technology. Oh, and please note that all points in this talk will be emphasized or lightly performed through Taylor Swift lyrics. Seriously, this talk will consist of at least 50% Taylor Swift. Can you, like, even?<br />
<br />
== Level Up Your Coding with Code Club (yes, you can talk about it) ==<br />
<br />
* Coral Sheldon-Hess, coral@sheldon-hess.org<br />
<br />
Reading code is a necessary part of becoming a better developer. It gives you more experience and more insight into How Things Are (or Aren't) Done; it builds your intuition about how to solve problems with code; and it increases your confidence that you, too, can tackle whatever technological problems you're facing.<br />
<br />
But you don't have to read code alone! (Which is good. It's really not fun to read code alone.) <br />
<br />
In late 2014, a group of librarians formed two Code Clubs, inspired by [http://bloggytoons.com/code-club/ this talk by Saron] (of Bloggytoons fame). I'd like to tell you about how we've structured our Code Clubs, what has gone well, what we've learned, and what you need to do to form your own Code Club. I'll share a list of the codebases we've looked at, too, to help you get your own Code Club off the ground! <br />
<br />
== The Growth of a Programmer ==<br />
<br />
* [[User:jgo | Joshua Gomez]], Getty Research Institute, jgomez@getty.edu<br />
<br />
Just like other creative endeavors, software developers can experience periods of great productivity or find themselves in a rut. After contemplating the alternating periods in my own career I've noticed several factors that have effected my own professional growth and happiness, including: mentorship, structure, community, teamwork, environment, formal education, etc. Not all of the factors need to be present at all times; but some mixture of them is critical for continued growth. In this talk, I will articulate these factors, discuss how they can effect a developer's career, and how they can be sought out when missing. This talk is aimed at both new developers looking to strike their own path as well as the veterans that lead or mentor them.<br />
<br />
== Developing a Fedora 4.0 Content Model for Disk Images ==<br />
<br />
* Matthew Farrell, matthew.j.farrell@duke.edu, Duke University Libraries<br />
* Alexandra Chassanoff, achass@email.unc.edu, BitCurator Access Project Manager<br />
<br />
As the acquisition of born-digital materials grows, institutions are seeking methods to facilitate easy ingest into their repositories and provide access to disk images and files derived or extracted from disk images. In this session, we describe our development of a Fedora 4.0 Content model for disk images, including acceptable image file formats and the rationale behind those choices. We will also discuss efforts to integrate the disk image content model into the BitCurator Access environment. Unlike generalized, format-agnostic content models which might treat the disk image as a generic bitstream, a content model designed for disk images enables expression of relationships among associated content in the collection such as files extracted from images and other born-digital and digitized material associated with the same creator. It also enables capture of file-system attributes such as file paths, timestamps, whether files are allocated/deleted, etc. Further, a disk image content model suggests further steps repositories can take in order to transform and re-use associated metadata generated during the creation and forensic analysis of the disk image.<br />
<br />
== Data acquisition and publishing tools in R ==<br />
<br />
* Scott Chamberlain, scott@ropensci.org, rOpenSci/UC Berkeley - first-time presenter<br />
<br />
R is an open source programming environment that is widely used among researchers in many fields. R is powerful because it's free, increasingly robust, and facilitates reproducible research, an increasingly sought after goal in academia. Although tools for data manipulation/visualization/analysis are well developed in R, data acquisition and publishing tools are not. rOpenSci is a collaborative effort to create the tools necessary to complete the reproducible research workflow. This presentation discusses the need for these tools, including examples, including interacting with the repositories Mendeley, Dryad, DataONE, and Figshare. In addition, we are building tools for searching scholarly metadata and acuiring full text of open access articles in a standarized way across metadata providers (e.g., Crossref, DataCite, DPLA) and publishers (e.g., PLOS, PeerJ, BMC, Pubmed). Last, we are building out tools for data reading and writing in Ecologial Metadata Language (EML).<br />
<br />
== SPLUNK: Log File Analysis ==<br />
<br />
* Jim LeFager, jlefager@depaul.edu, DePaul University Library<br />
DePaul University Library recently took over monitoring and maintaining of the library EZproxy servers this past year and using Splunk, a machine data analysis tool, we are able to gather information and statistics on our electronic resource usage in addition to monitoring the servers. Splunk is a tool that can collect, analyze, and visualize log files and other machine data in real time and this has allowed for gathering realtime usage statistics for our electronic resources allowing us to filter by multiple facets including IP Range, Group Membership (student, faculty), so that we can see who is accessing our resources and from where. Splunk allows our library to query our data and create rich custom dashboards as well as create alerts that can be triggered when certain conditions are met, such as error codes, which can send an email alert to a group of users. We will be leveraging Splunk to monitor all library web applications going forward. This talk will review setting up Splunk and best practices in using the available features and customizations available including creating queries, alerts, and custom dashboards. <br />
<br />
== Your code does not exist in a vacuum ==<br />
* Becky Yoose, yoosebec at grinnell dot edu, Grinnell College (Done a lightning talk, MC duties, but have not presented a prepared talk)<br />
<br />
“If you have something to say, then say it in code…” - Sebastian Hammer, code4lib 2009<br />
<br />
In its 10 year run, code4lib has covered the spectrum of libtech development, from search to repositories to interfaces. However, during this time there has been little discussion about this one little fact about development - code does not exist in a vacuum. <br />
<br />
Like the comment above, code has something to say. A person’s or organization’s culture and beliefs influences code in all steps of the development cycle. What development method you use, tools, programming languages, licenses - everything is interconnected with and influenced by the philosophies, economics, social structures, and cultural beliefs of the developer and their organization/community.<br />
<br />
This talk will discuss these interconnections and influences when one develops code for libraries, focusing on several development practices (such as “Fail Fast, Fail Often” and Agile) and licensing choices (such as open source) that libtech has either tried to model or incorporate into mainstream libtech practices. It’ll only scratch the surface of the many influences present in libtech development, but it will give folks a starting point to further investigate these connections at their own organizations and as a community as a whole.<br />
<br />
tl;dr - this will be a messy theoretical talk about technology and libraries. No shiny code slides, no live demos. You might come out of this talk feeling uncomfortable. Your code does not exist in a vacuum. Then again, you don’t exist in a vacuum either.<br />
<br />
== The Metadata Hopper: Mapping and Merging Metadata Standards for Simple, User-Friendly Access ==<br />
<br />
* Tracy Seneca, tjseneca@uic.edu, University of Illinois at Chicago<br />
* Esther Verreau: verreau1@uic.edu, University of Illinois at Chicago<br />
<br />
The Chicago Collections Consortium: 15 institutions and growing! 8 distinct EAD standards! At least 3 permutations of MARC, and we lost count of the varieties of custom CONTENTdm image collections. Not to mention the 14,730 unique subject terms, nearly all of which lead our poor end-users to exactly one organization's content. <br />
<br />
All large content aggregation projects have faced this challenge, and there are a few emerging tools to help us wrangle disparate metadata into new contexts. The Metadata Hopper is one such tool. The Metadata Hopper enables archivists to map their local metadata standards to standardized deposit records, and tags those materials using a shared vocabulary, integrating them into a user-friendly portal without disrupting local practices. In last year's Code4Lib lightning talk we described the challenges that the Chicago Collections Consortium faces in creating shared, in-depth access to archival and digital collections about Chicago history and culture across CCC member organizations. This year, thanks to the Andrew W. Mellon Foundation, we have a working Django application to demonstrate. In this talk we'll discuss the design that enables multiple layers of flexibility, from the ability to accept a variety of metadata standards to designing for an open source audience.<br />
<br />
http://chicagocollectionsconsortium.org<br />
<br />
== Programmers are not projects: lessons learned from managing humans ==<br />
<br />
* Erin White, erwhite@vcu.edu, Virginia Commonwealth University - first-time presenter<br />
<br />
Managing projects is one thing, but managing people is another. Whether we’re hired as managers or grow “organically” into management roles, sometimes technical people end up leading technical teams (gasp!). I’ll talk about lessons I’ve learned about hiring, retaining, and working long-term and day-to-day with highly tech-competent humans. I’ll also talk about navigating the politics of libraryland, juggling different types of projects, and working with constrained budgets to make good things and keep talented people engaged.<br />
<br />
== Practical Strategies for Picking Low-Hanging Fruits to Improve Your Library's Web Usability and UX ==<br />
<br />
* Bohyun Kim, bkim@hshsl.umaryland.edu, University of Maryland, Baltimore<br />
<br />
Have you ever tried to fix an obvious (to you at least!) problem in Web usability or UX (user experience) only to face strong resistance from the library staff? Are you a strong advocate for making library resources, systems, services, and space as usable as possible, but do you often find yourself struggling to get the point across and/or obtain the crucial buy-in from colleagues and administrators? <br />
<br />
There is no shortage of Web usability and UX guidelines. But applying them to a library and implementing desired changes often involve a long and slow process. To tackle this issue, this talk will focus on how to utilize the 'expert review' process (aka 'heuristic evaluation') as a preliminary or even preparatory step before embarking on more time-and-labor-intensive usability testing and user research. Several examples from simple fixes to more nuanced usability and UX issues in libraries will be discussed to your heart's content. The goal of this talk is to provide practical strategies for picking as many low-hanging fruits as possible to make a real (albeit small) difference to your library's Web usability and UX effectively and efficiently.<br />
<br />
== A Semantic Makeover for CMS Data ==<br />
<br />
* Bill Levay, wjlevay@gmail.com, Linked Jazz Project<br />
<br />
How can we take semi-structured but messy metadata from a repository like CONTENTdm and transform it into rich linked data? Working with metadata from Tulane’s Hogan Jazz Archive Photography Collection, the Linked Jazz Project used Open Refine and Python scripts to tease out proper names, match them with name authority URIs, and specify FOAF relationships between musicians who appear together in photographs. Additional RDF triples were created for any dates associated with the photos, and for those images with place information we employed GeoNames URIs. Historical images and data that were siloed can now interact with other datasets, like Linked Jazz’s rich set of names and personal relationships, and can be visualized [link to come] or otherwise presented on the web in any number of ways. I have not previously presented at a Code4Lib conference.<br />
<br />
== Taking User Experience (UX) to new heights ==<br />
<br />
* Kayne Richens, kayne.richens@deakin.edu.au, Deakin University<br />
<br />
User Experience, or "UX", is for more than just websites. At Deakin University Library we're exploring ways to improve the user experience inside our campus library spaces, by putting new technologies front and centre in the overall experience for our students. How are we doing this? We’re collaborating with the University's IT department and exploring the following Library-changing opportunities:<br />
<br />
- Augmented Reality for Way-finding: We’re tackling that infamous thing that all Libraries can't get right – way-finding. We're enhancing library tour information and way-finding experiences by introducing augmented reality solutions.<br />
<br />
- Heat mapping the library with wi-fi: We’re using our existing wi-fi infrastructure to present "heat maps" of library space utilisation, allowing our users to easily locate the space that best suits their needs, whether it be busy spaces to collaborate, or quiet spaces to study. And by overlaying computer usage and group study room bookings, users can quickly locate the space they need.<br />
<br />
- Video chat library service: We’re piloting video-conferencing facilities in our group study rooms and spaces, connecting users and librarians and other professionals.<br />
<br />
This talk will look at how these different technologies will be brought together to provide improved user experiences, as well some of the evidence and reasons that helped us to identify our needs, so you can too.<br />
<br />
==How to Hack it as a Working Parent: or, Should Your Face be Bathed in the Blue Glow of a Phone at 2 AM?==<br />
<br />
*Margaret Heller, Loyola University Chicago, mheller1@luc.edu<br />
*Christina Salazar, California State University Channel Islands, christina.salazar@csuci.edu<br />
*May Yan, Ryerson University, may.yan@ryerson.ca<br />
<br />
Modern technology has made it easier than ever for parents employed in technical environments to keep up with work at all hours and in all locations. This makes it possible to work a flexible schedule, but also may lead to problems with work/life balance and furthering unreasonable expectations about working hours. Add to that shifting gender roles and limited paid parental leave in the United States and you have potential for burnout and a certainty for anxiety. It raises the additioal question of whether the “always connected” mindset puts up a barrier to some populations who otherwise might be better represented in open source and library technology communities. <br />
<br />
This presentation will address tools that are useful for working parents in technical library positions, and share some lessons learned about using these tools while maintaining a reasonable work/life balance. We will consider a question that Karen Coyle raised back in 1996: <br />
“What if the thousands of hours of graveyard shift amateur hacking wasn't really the best way to get the job done? That would be unthinkable.” <br />
<br />
For those who are able to take an extended parental leave, we will present strategies for minimizing the impact to your career and your employer. For those (particularly in the United States) who are only able to take a short leave will require different strategies. Despite different levels of preparation, all are useful exercises in succession planning and making a stronger workplace and future ability to work a flexible schedule through reviewing workloads, cross-training personnel, hiring contract replacements, and creative divisions of labor. Such preparation makes work better for everyone, kids or no kids or caretakers of any kind.<br />
<br />
==Making your digital objects embeddable around the web==<br />
<br />
* Jessie Keck, jkeck@stanford.edu, Stanford University Libraries<br />
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries<br />
<br />
With more and more content from our digital repositories making their way into our discovery environments we quickly realize that we’re repeatedly re-inventing the wheel when it comes to creating “Viewers” for these digital objects. With various different types of viewers necessary (books, images, audio, video, geospatial data, etc) the burden of getting these viewers into various environments (topic guides, blogs, catalogs, etc) becomes exponential.<br />
<br />
In this talk we’ll discuss how Stanford University Libraries implemented an oEmbed service to create an extensible viewer framework for all of its digital content. Using this service we’ve been able to easily integrate viewers into various discovery applications as well as make it easy for end users who discover our objects to easily embed customized versions into their own websites and blogs.<br />
<br />
==So you want to make your geospatial data discoverable==<br />
<br />
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries<br />
<br />
Finding data for research or coursework can be one of the most time intensive tasks for a scholar or student. We introduce GeoBlacklight, an open source, multi-institutional software project focused on solving these common challenges at institutions across the world. GeoBlacklight prioritizes user experience, integrates with many GIS tools, and streamlines the use and organization of geospatial data. This talk will provide an introduction to the software, demonstrate current functionality, and provide a road map for future work.<br />
<br />
== Clueless-Driven Development: How I learned to migrate to Fedora 4 ==<br />
<br />
* Adam Wead, awead@psu.edu, Penn State University<br />
<br />
Recently I was tasked with migrating the content from our Fedora3 repository to the new Fedora4 repository architecture.<br />
Despite a wealth of community support, I had no idea how to approach, or even begin to solve this problem. I knew I<br />
wanted to follow best practices and use test-driven development to build my solution, but had no idea where to start.<br />
Despite this initial setback, I was able to start writing tests with only a vague understanding of the problem. As my<br />
tests exposed where my understanding of the problem was flawed, my code evolved, and within a week I had arrived at a<br />
working solution that exhibited all the hallmarks of good testing and software design.<br />
<br />
This talk recounts the process I went through from starting with practically nothing, to arriving at a working solution.<br />
You can follow the rules of test-driven development, but you can write tests in an expressive way to describe the<br />
problem instead of just describing what the code should do. It was also essential to begin testing from an integration<br />
viewpoint as opposed to a unit one, because at the outset the units were unknown and were later realized through further<br />
development. For the presentation, I will be demonstrating using RSpec and Ruby. All the code examples will be related<br />
to the Hydra software stack; however, I hope to show that the processes at work will be applicable in any context.<br />
<br />
<br />
== Designing and Leading a Kick A** Tech Team ==<br />
<br />
* Sibyl Schaefer, sschaefer@rockarch.org, Rockefeller Archive Center<br />
<br />
New managers are often promoted without receiving management training, yet management is not something you just figure out. The experience of being expected to know how to manage, yet not being trained to do so often results in new managers feeling isolated and unsure how to move from making to managing. In this talk I’ll focus on my own managerial experience of designing and leading an archival tech team in a small independent archives. Topics covered will include hiring, delegating, creating a team culture, and leading people whose specialized knowledge exceeds your own. The talk take-aways should be applicable to managers and employees at large and small institutions alike.<br />
<br />
<br />
==American (Archives) Horror Story: LTO Failure and Data Loss ==<br />
<br />
* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH<br />
* Casey Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH<br />
<br />
Here’s a story to send shivers down archival spines: when transferring video files off LTO for the American Archive project, WGBH got an initial failure rate of 57%. After repeat tries, the rates improved; still, an unnervingly large percentage of files were never able to be transferred successfully. Even more unnerving, going public with our horror story got a big response from other archives using LTO -- it seems like many institutions are having similarly scary results. What are the real risks with LTO tape? Are there steps that archives should be taking to better circumvent those risks? This presentation will share information about LTO storage failures across archives world and discuss the process of investigating the problem at WGBH by testing different methods of data retrieval from LTO (direct and networked downloads, individual file retrieval and bulk data dump, use of LTO 4 and LTO 6 decks) and using checksum comparisons and file analysis and characterization tools such as ffprobe, mediainfo and exiftool to analyze failed files. We'll also present whatever results we’ve managed to turn up by the time of Code4Lib!<br />
<br />
== PBCore in Action: Three Words, Not Two! ==<br />
<br />
* Casey E. Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH<br />
* Andrew (Drew) Myers, andrew_myers@wgbh.org, Supervising Developer, WGBH<br />
<br />
In 2001, public media representatives developed the PBCore XML schema to establish a common language for managing metadata about their analog and digital audio and video. Since then, PBCore has been adopted by a number of organizations and archivists in the moving image archival community. The schema has also undergone a few revisions, but on more than one occasion it was left orphaned and with little to no support.<br />
<br />
Times have changed. You may have heard the news that PBCore is back in action as part of the American Archive of Public Broadcasting initiative and via the Association of Moving Image Archivists (AMIA) PBCore Advisory Subcommittee. A group of archivists, public media stakeholders, and engaged users have come together to provide necessary, sustaining support for the standard and to see to its further development. <br />
<br />
At this session, we'll discuss the scope and uses of PBCore in digital preservation and access, report on the progress and goals of the PBCore Advisory Subcommittee, and share how the group (by the time of the conference) will have transformed the XML schema into an RDF ontology, bringing PBCore into the second decade of the 21st century. #PBHardcore<br />
<br />
==Collaborating to Avert the Digital Graveyard==<br />
<br />
* Harish Nayak, hnayak@library.rochester.edu, University of Rochester Libraries <br />
* Sean Morris, smorris@library.rochester.edu, University of Rochester Libraries <br />
<br />
In 1995, the Robbins Library at the University of Rochester created a digital collection of Arthurian texts, images, and bibliographies. Together with medieval scholars, we recently completed the redesign and development of an interface for this collection. Using FRBR concepts, we re-conceptualized organization and editing workflow from the ground up in a mobile-first Drupal-based project. <br />
<br />
In this talk we will describe the project as well as how we utilized the techniques of work practice study and user centered design to maintain engagement with reluctant stakeholders, nontechnical scholars, and VERY meticulous graduate students. Neither of us have previously presented at a Code4Lib conference.<br />
<br />
==Docker? VMs? EC2? Yes! With Packer.io==<br />
<br />
* Kevin S. Clarke, ksclarke@gmail.com, Digital Library Programmer, UCLA<br />
<br />
There are a lot of exciting ways to deploy a software stack nowadays. Many of our library systems are fully virtualized. Docker is a compelling alternative, and there are also cloud options like Amazon's EC2. This talk will introduce Packer.io, a tool for creating identical machine images for multiple platforms (e.g., Docker, VMWare, VirtualBox, EC2, GCE, OpenStack, et al.) all from a single source configuration. It works well with Ansible, Chef, Puppet, Salt, and plain old Bash scripts. And, it's designed to be scriptable so that builds can be automated. This presentation will show how easy it is to use Packer.io to bring up a set of related services like Fedora 4, Grinder (for stress testing), and Graphite (for charting metrics). As an added value, all the buzzwords in this proposal will be defined and explained!<br />
<br />
== Technology on your Wrist: Cross-platform Smartwatch Development for Libraries ==<br />
<br />
* [[User:sanderson|Steven Carl Anderson]], sanderson@bpl.org, [http://www.bpl.org Boston Public Library] (no previously accepted prepared talks but have done lightning talks in the past)<br />
<br />
I'll be the first to admit: smartwatches are unlikely to completely revolutionize how a library provides online services. But I believe they still represent an opportunity to further enhance existing library services and resources in a unique way.<br />
<br />
At the Boston Public Library (BPL), we're in the initial phases of designing a modest smartwatch app to provide notifications for circulation availability and checked-out-material due-date alerts by the end of current year. We're starting small, but we plan to evolve the concept over time as we see what (if any) traction such an application gets with potential users. For example, we plan to explore the possibility of adding "nearest branch to my current location" functionality to this app.<br />
<br />
Despite the "development phase" of this application as of this writing, this talk is not being given by a novice. As a technology enthusiast, I've released [http://www.phdgaming.com/smartwatch_projects/ five smartwatch applications] and have had two of those be finalists in a [http://www.phdgaming.com/samsung_challenge/ Samsung sponsored development challenge]. This experience not only will allow for the BPL to avoid many beginner mistakes in its smartwatch app development but also gives a much more complete understanding of the smartwatch development ecosystem.<br />
<br />
This talk will explore the following questions:<br />
<br />
* What kinds of online library services could potentially be transformed or translated into the smartwatch/wearable domain? What kinds of services are better left alone? These questions are currently being explored and I'll talk about our plans and experiences. Included will be any statistical information from our application launch along with statistics from my personal development.<br />
<br />
* How to support all the different operating systems these devices run without painful modifications to your codebase. (There's Tizen that is used by Samsung's Gear 2 and Gear S, Android Wear that is used by most other non-Apple manufacturers, then there is Apple's upcoming smartwatch itself, etc.)<br />
<br />
* How to support different screen resolutions on such a small device. From round to rectangular to perfectly square, smartwatches come in all different shapes these days.<br />
<br />
* What are the app stores like on these platforms? As I support multiple applications through different distribution networks, a guide to navigating how to distribute one's app is included and I'll reveal how these systems work “behind the curtain.”<br />
<br />
* What are common issues and pitfalls to avoid when doing development? Tips on broken APIs and how to cope or optimizing your code will be included.<br />
<br />
==Seeing the Forest From the Trees: The Art of Creating Workflows for Digital Projects ==<br />
<br />
* Jen LaBarbera, j.labarbera@neu.edu, NDSR Resident, Northeastern University<br />
* Joey Heinen, joseph_heinen@harvard.edu, NDSR Resident, Harvard University<br />
* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH<br />
* Tricia Patterson, triciap@mit.edu, NDSR Resident, MIT<br />
<br />
We have to "turn projects into programs" in order to create a solid and sustainable digital preservation initiative...but what the heck does that even mean? What does that look like?<br />
<br />
In this talk, members of the inaugural Boston cohort of the National Digital Stewardship Residency will discuss one piece of our digital preservation test kitchen: our stabs at creating digital workflows that will (hopefully) help our institutions turn digital preservation projects into programs. Specifically, we will talk about how difficult it is to create a general and overarching workflow for digital preservation tasks (e.g. ingest into repositories, format migrations, etc.) that incorporates various technical tools while also taking into account the myriad and unending list of possible exceptions or special scenarios. Turning these complicated, specific processes into a simplified and generalized workflow is an art. We haven't necessarily perfected that art yet, but in this talk, we'll share what has worked for us -- and what hasn't. We’ll also touch on the importance of documentation, and achieving that delicate balance of adequately thorough documentation that doesn’t pose the risk of information avalanche. These processes often create more questions than answers, but we'll share the answers that we (and our mentors) have found along the way!<br />
<br />
== Annotations as Linked Data with Fedora4 and Triannon (a Real Use Case for RDF!) ==<br />
<br />
* Rob Sanderson, azaroth@stanford.edu, Stanford University Libraries<br />
* Naomi Dushay, ndushay@stanford.edu, Stanford University Libraries<br />
<br />
Annotations on content resources allow users to contribute knowledge within the digital repository space. W3C Open Annotation provides a comprehensive model for web annotation on all types of content, using Linked Data as a fundamental framework. Annotation clients generate instances of this model, typically using a JSON serialization, but need to store that data somewhere using a standard interaction pattern so that best of breed clients, servers, and data can be mixed and matched.<br />
<br />
Stanford is using Fedora4 for managing Open Annotations, via a middleware component called Triannon. Triannon receives the JSON data from the annotation client, and uses the Linked Data Platform API implementation in Fedora4 to create, retrieve, update and delete the constituent resources. Triannon could be easily modified to use other LDP implementations, or could be modified to work with linked data other than annotations.<br />
<br />
== Hydras in the Wild: A survey of current projects ==<br />
<br />
* Mark Bussey, mark@curationexperts.com, Data Curation Experts<br />
<br />
You've seen the tutorials, but [https://github.com/projecthydra/hydra/wiki/Dive-into-Hydra Dive Into Hydra] seems to leave something wanting. What can you really do using the Hydra Framework? This talks looks at a number of current Hydra projects and highlights the design and functional features unique to each. Compare and contrast UX, design and functional capabilites from a range of hydra-based repositories including:<br />
* Avalon for media discovery and distribution (Indiana and Northwestern Univiersities) <br />
* HydraDam for media archive management(WGBH)<br />
* HyHull for general Institutional Repository needs (University of Hull)<br />
* T-DIL for slide library functions (Tufts University)<br />
* Sufia & Scholarsphere as a bundled self-deposit IR solution (Pennsylvania State University)<br />
* Curate & Worthwhile as general purpose repository platforms (Multiple Insititutions)<br />
This will be a whirlwind tour aimed at providing ideas and inspiration for your own repository development project.<br />
<br />
== Hydra Makeovers! ==<br />
<br />
* Alicia Cozine, alicia@curationexperts.com, Data Curation Experts<br />
* Patrick Feeley, pgf8@case.edu, Case Western Reserve University<br />
<br />
Compare two Hydra-based applications with the systems they replaced. Marvel at the Before and After snapshots of functionality, speed, and look & feel. <br />
* '''Digital Case 2.0''' is an institutional repository, complete with administrative tools, derivatives transcoding, flexible XML metadata storage, embargo and lease capability, faceted searching, and content viewers for texts/TEI, images, audio recordings, and videos. Digital Case 2.0 is based on worthwhile, an open-source IR starter gem. <br />
* '''The Tufts Digital Image Library''' is a specialized tool for art and art history resources, offering image collections with user access controls, image ordering, collection nesting, drag-and-drop organization, slideshows, and export capability. <br />
Both new systems are built on hydra, the open-source Ruby-on-Rails repository solution that incorporates Fedora for storage, Solr for indexing, and Blacklight for search optimization. Their beauty is not just skin-deep!<br />
<br />
<br />
<br />
== Helping Google (and scholars, researchers, educators, & the public) find archival audio ==<br />
<br />
* Anne Wootton, anne@popuparchive.org, Pop Up Archive (www.popuparchive.org)<br />
<br />
Culturally significant digital audio collections are hard to discover on the web. There are major barriers keeping this valuable media from scholars, researchers, and the general public:<br />
<br />
Audio is opaque: you can’t picture sound, or skim the words in a recording. <br />
Audio is hard to share: there’s no text to interact with. <br />
Audio is not text: but since text is the medium of the web, there’s no path for audiences to find content-rich audio.<br />
Audio metadata is inconsistent and incomplete.<br />
<br />
At Pop Up Archive, we're helping solve this problem making the spoken word searchable. We began as a UC-Berkeley School of Information Master's thesis to provide better access to recorded sound for audio producers, journalists, and historians. Today, Pop Up Archive processes thousands of hours of sound from all over the web to create automatic, timestamped transcripts and keywords, working with media companies and institutions like NPR, KQED, HuffPost Live, Princeton, and Stanford. We're building collections of sound from journalists, media organizations, and oral history archives from around the world. Pop Up Archive is supported by the John S. and James L. Knight Foundation, the National Endowment for the Humanities, and 500 Startups.<br />
<br />
== Digital Content Integrated with ILS Data for User Discovery: Lessons Learned ==<br />
<br />
* Naomi Dushay, ndushay@stanford.edu, Stanford University Libraries<br />
* Laney McGlohon, laneymcg@stanford.edu, Stanford University Libraries (first-time presenter)<br />
<br />
So you want to expose your digital content in your discovery interface, integrated with the data from your ILS? How do you make the best information user searchable? How do you present complete, up to date search results with a minimum of duplicate entries?<br />
<br />
At Stanford, we have these cases and more:<br />
* digital content with no metadata in ILS<br />
* digital content for metadata in ILS<br />
* digital content with its own metadata derived from ILS metadata.<br />
<br />
We will describe our efforts to accommodate multiple updatable metadata sources for materials in the ILS and our Digital Object Repository while presenting users with reduced duplication in SearchWorks. Included will be some failures, some successes, and an honest assessment of where we are now.<br />
<br />
== Show All the Things: Kanban for Libraries == <br />
<br />
* Mike Hagedon, mhagedon@email.arizona.edu, University of Arizona Libraries (first-time presenter)<br />
<br />
The web developers at the University of Arizona Libraries had a problem: we were working on a major website rebuild project with no clear way to prioritize it against our other work. We knew we wanted to follow Agile principles and initially chose Scrum to organize and communicate about our work. But we found that certain core pieces of Scrum did not work for our team. Then we discovered Kanban, an Agile meta-process for organizing work (team or individual) that treats the work more as a flow than as a series of fixed time boxes. I’ll be talking about our journey toward finding a process that works for our team and how we’ve applied the principles of Kanban to better get our work done. Specifically, I'll discuss principles like how to visualize all your work, how to limit how much you’re doing (to get more done!), and how to optimize the flow of your work.<br />
<br />
== DIY Catalog ==<br />
<br />
* Wayne Schneider, wschneider at [//www.hclib.org hclib.org], [//www.hclib.org Hennepin County Library]<br />
* Amy Drayer, adrayer at [//www.hclib.org hclib.org], [//www.hclib.org Hennepin County Library]<br />
<br />
With so many discovery layers being made available that didn’t quite fit user needs but still came with substantial costs, Hennepin County Library determined it would develop one that could handle its customizations. So they built their own ILS API, Web services, and an interface that provides all the features (and existing custom features) of the old catalog, with new features planned, all within a responsive layout. Get a look at the system architecture, how the front end communicates through the layers back to the databases, and how to manage the infrastructure.<br />
<br />
== OverDrive: Full Integration ==<br />
<br />
* Amy Drayer, adrayer at [//www.hclib.org hclib.org], [//www.hclib.org Hennepin County Library]<br />
* Wayne Schneider, wschneider at [//www.hclib.org hclib.org], [//www.hclib.org Hennepin County Library]<br />
<br />
How do you increase usage of your ebooks? Seamless integration in the catalog certainly helps. Users can search for digital titles, limit to just those that are available, place a request, borrow, and manage all their digital titles from the library website alongside all the other physical titles the library has. Get a quick demo and learn how this was all made possible.<br />
<br />
The [//www.hclib.org Hennepin County Library] is ranked one of [//www.thedigitalshift.com/2014/10/ebooks/overdrive-api-usage-indicates-growth-ebook-checkouts-via-opac/ the top users of OverDrive and OverDrive’s API] and is looking to more fully integrate 3M Cloud, OneClickDigital, and other digital resources.<br />
<br />
== Dynamic Indexing: a Tragic Solr Story ==<br />
<br />
* Wayne Schneider, wschneider at [//www.hclib.org hclib.org], [//www.hclib.org Hennepin County Library]<br />
<br />
Loading data from an ILS into Solr isn’t so hard, unless it needs to be dynamic, fast, and hold more data than what can be found in 1.5 million MARC records. Some additional information we’ve incorporated are from Syndetics, ILS circulation, and OverDrive. We’ll share the nitty gritty details and what we learned about dynamic Solr indexing, including how to get good performance, how to deal with indexing failures, how to schedule it all to keep the data up-to-date, and some things you can do with that data such as popularity ratings.<br />
<br />
== Fedora 4, Survey of Core Capabilities and External Modules: == <br />
* Andrew Woods, awoods@duraspace.org, DuraSpace<br />
<br />
Now that the production release of Fedora 4.0 is out, the time is right to take a step back and review the core capabilities offered by Fedora:<br />
* Basic CRUD<br />
* Versioning<br />
*- Transactions<br />
* etc<br />
<br />
...and take a closer look at the supported external modules:<br />
* Authorization<br />
* Solr integration<br />
* Triplestore integration<br />
* Camel integration<br />
* etc<br />
<br />
In addition to clarifying specific implementation details, this is an opportunity to surface community requirements which may have not been addressed in the initial release.<br />
<br />
== Bleeding edge beacons: redesign of a library tour with new technology ==<br />
<br />
* Neal Henshaw, Virginia Tech <br />
* Somiah Lattimore, Straight Up Creative<br />
* Keith Gilbertson, keith.gilbertson@vt.edu, Virginia Tech<br />
<br />
This group has not yet presented at Code4Lib<br />
<br />
A technology liaison, a designer, and a developer are working together to update a mobile audio tour of an academic library.<br />
<br />
The walking tour was originally conceived of and created by the technology liaison to provide an orientation experience for incoming students. In its current version, patrons visit several stations in the library and activate an audio description of each station by scanning a QR barcode with a mobile device.<br />
<br />
We are building a prototype to test with focus groups so that we can launch a new version of the tour in early 2015. The tour has been reimagined with a professional and communicative user interface that presents students with learning goals for each location in the library. The new version of the tour is a mobile application with integrated support for micro-location technology provided through Bluetooth low energy beacon devices, known informally as iBeacons, installed throughout the building. As a touring student walks through the library, her location is noted by the app so that an appropriate video segment is automatically played according to the current location.<br />
<br />
We will discuss perspectives on the design of the project, including<br />
<br />
* Designing with technology to achieve learning goals<br />
* Designing graphical elements, interaction, and user experience<br />
* Designing to maintain compatibility with older technologies<br />
<br />
We’ll explain our efforts to make the application usable by those with hearing impairments and mobility impairments, reactions from our first users, and challenges in working with the relatively new beacon technology.<br />
<br />
== Distributed Remediation: Small tools for big problems: ==<br />
<br />
* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs<br />
<br />
Remediation of legacy data can be automated only so much. Certain essential cleanup tasks, such as aligning a name with the correct authorized version, is very difficult for a computer yet trivial for a person. While it is these types remediations that will allow an institution to take advantage and participate in the web of Linked Open Data, a wholly manual approach is unrealistic. However, by augmenting automated remediation with a light human touch we can quickly and efficiently reach our goals. This talk will look at tools and methods being developed at NYPL Labs to empower library staff and the public to help clean up our legacy metadata through collaborative remediation.<br />
<br />
==VuFind + WorldCat: Open Source Discovery Meets Big Library Data==<br />
<br />
* Karen A. Coombs, coombsk@oclc.org, OCLC<br />
* Demian Katz, demian.katz@villanova.edu, Villanova University<br />
<br />
Good collaboration is crucial to any integration. Our project, to integrate the open source discovery tool, VuFind, with results from the new WorldCat Discovery API, is no different. We want to exploit the flexibility of VuFind and add the depth and breadth of WorldCat and central index content. Plus, the project has the potential to eliminate the hurdle of exporting and indexing MARC records for 32 VuFind libraries.<br />
<br />
While we are really excited about the UI enhancements, we are also curious to see how we can share our domain expertise between our two organizations to get the project done quickly. How will different perspectives shape our existing code bases? How will we adjust to working on the same code base simultaneously? And how can we best incorporate what we learn along the way?<br />
<br />
There is also new territory to explore using the API: integrating bibliographic and article data into a single results set. And the overarching question: will we be able to take advantage of Linked Data in the WorldCat Discovery API to create some “glue” between records in existing VuFind indexes and third-party data providers?<br />
<br />
This presentation will discuss our adventures in the OCLC WorldShare Platform/VuFind collaboration: the opportunities, challenges and results. You’ll learn what worked, what didn’t and how you can improve your own discovery interface integration project—no matter what provider or APIs you use.<br />
<br />
== Book Reader Bingo: Which Page-Turner Should I Use? ==<br />
<br />
* Eben English, eenglish [at] bpl.org, Boston Public Library<br />
<br />
Another day, another library reinventing the book-viewer wheel. When will the madness end? This talk will explore the current landscape of book-viewer/page-turner applications for digital library systems with an eye towards helping you make the right decision for your project. We'll look at some the major players on the market (such as Internet Archive BookReader, Wellcome Player, Mirador, and WDL-Viewer to name a few) and compare them based on a number of criteria: feature sets, mobile/tablet friendliness, ease of integration, code health, test coverage, "market share" (number of implementers), and other important factors. We'll look at the results of ACTUAL USABILITY TESTS to see what features users REALLY want in a book-viewer, and how each app measures up. <br />
<br />
We'll also discuss important recent trends (such as the IIIF Presentation API, ReadersFirst, and NYPL's Library Simplified initiative) that have the potential to shape the book-viewer development landscape in the immediate future. Which page-turner applications are best poised to adopt/integrate/leverage these emerging standards? Which will become obsolete? This talk has the answers you need.<br />
<br />
== Rich Citations ==<br />
<br />
* Adam Becker, abecker@plos.org, Public Library of Science<br />
* Erik Hetzner, ehetzner@plos.org, Public Library of Science<br />
<br />
Citations should connect you to the research you need. They should<br />
link directly to the relevant papers and data. They should tell you<br />
everything you need to know about how and where two pieces of research<br />
are connected. They should be easy to use and they should never get in<br />
the way of the reading experience. In short, citations should not<br />
clumsily point to a mere chunk of plain undifferentiated text sitting<br />
in a static list at the end of the paper. But with almost no<br />
exceptions, citations in scientific papers do just that.<br />
<br />
PLOS Labs has been working on a project to capture extra information<br />
about citations. To this end, we have designed a metadata structure<br />
describing the context of a paper's citations, called rich citations.<br />
This structured information includes complete bibliographic<br />
information for the cited items, location and context of the in-text<br />
citation, co-citations, reference license and status (updated,<br />
retracted, etc.), and more.<br />
<br />
We have processed the complete PLOS corpus to extract this rich<br />
citation metadata, and made this data available in an API located at<br />
http://api.richcitations.org/.<br />
<br />
We have also developed a JavaScript overlay to enhance a paper's view<br />
using rich citations (http://alpha.richcitations.org). This overlay<br />
uses the underlying rich citation metadata to allow the user to view<br />
information about an in-text citation, quickly navigate between<br />
citations, and sort and filter the paper's reference list.<br />
<br />
In this talk, we will describe the rich citation metadata that we are<br />
capturing. We will demonstrate how this metadata can enhance a<br />
reader's experience of an article and how it can be used by<br />
researchers to better understand how citations are used in the<br />
scientific community. We will also discuss our ongoing plans to extend<br />
this project to the wider literature beyond PLOS, and how interested<br />
members of the community can help.<br />
<br />
== Scriptaloging with ArchivesSpace and NodeJS ==<br />
<br />
* Brian Hoffman, brianjhoffman@gmail.com<br />
<br />
ArchivesSpace is a new web application for managing archival collections. It has a browser-based interface for entering and editing metadata, and can import data serialized as EAD, MARC, and several other formats. But there may be situations where neither of these are quite what you want. For instance, you may have a large folder of images that each need a digital object record; or you may want to export an EAD for every collection in your repository; or calculate the total extent of your collection; or execute a global search and replace; or batch-update barcodes, etc. You could write a plugin using ArchivesSpace’s plugin API, but that requires facility with Ruby as well as access to the environment where the application is running. A more lightweight approach is to access your data through ArchivesSpace’s powerful REST API, and process it using whatever scripting language you prefer. This talk will present some simple “scriptaloging” solutions that a moderately skilled programmer can use to automate data entry or import tasks using an extendable command line tool written in NodeJS (https://www.npmjs.org/package/as-cli) and loosely inspired by Drupal’s drush utilitly.<br />
<br />
== Consuming Big Linked Open Data in Practice: Authority Shifts and Identifier Drift ==<br />
<br />
* Kathryn Stine, katstine@berkeley.edu, UC Berkeley<br />
* Stephanie Collett, stephanie.collett@ucop.edu, California Digital Library, UC<br />
<br />
Increasingly, authoritative datasets of interest to libraries (subjects, names, classifications, etc.) are are available in bulk, exposed as linked open data. Unfettered access can allow libraries to aggregate, connect, and augment data in new ways that will benefit users. This talk will describe our exploratory experience integrating bulk data from the Virtual International Authority File (VIAF) into HathiTrust metadata to improve discovery and collection management.<br />
<br />
Authoritative data is not static - datasets change with new contributions and re-clustering, resulting in new identifier relationships. We will describe the challenges this presents with accessing, processing, and syncing our metadata with a massive, complex linked dataset. We will talk about our technical approach to navigating an ecosystem of identifiers and mitigating cached identifier drift between systems as authority data shifts. We aim to spark conversation about data accessibility and the relationships between local, consortial, and authoritative metadata as the library community moves beyond “Hello, world” linked data examples to integrating this data at scale into existing systems.<br />
<br />
== Your Chocolate is in My Peanut Butter! Mixing up Content and Presentation Layers to Build Smarter Books in Browsers with RDFa, Schema.org, and Linked Data Topics ==<br />
<br />
* Jason A. Clark <br />
* Head, Library Informatics & Computing, Montana State University<br />
* @jaclark jaclark@montana.edu<br />
<br />
*Scott W. H. Young <br />
*Digital Initiatives Librarian, Montana State University<br />
* @hei_scott<br />
<br />
Common methods of publishing book content have focused on various implementations of existing technologies such as LaTeX, Markdown, and .epub. A common theme within this development has been the separation of presentation layers and content layers. What if there was another way? In responding to that question, we’ll look at our local @msulibrary prototype software funded by an IMLS Sparks! Innovation grant for presenting books inside of web browsers (https://github.com/jasonclark/bib-template). Our talk will focus on the tools and technologies of open web publishing. We’ll consider the strange and wonderful benefits of integrating the presentation layer and content layer using semantic RDFa HTML5 markup, and we’ll demonstrate how describing and displaying books within an open web model impacts discovery, eBook production, and machine-readability.<br />
<br />
Our session will include:<br />
* The benefits of using RDFa, Schema.org, and linked data models for book production<br />
* How structured data models for book content can turn your webpage into your API<br />
* Analyze the effects of this practice for machine-understanding, SEO, and UX<br />
* Discuss the advantages and disadvantages of this model as it applies to a range of book genres, including web book prototypes for textbooks, fiction, and poetry.<br />
<br />
== Integration/Collaboration: Playing Well With Others ==<br />
<br />
* Sarah Romkey, sromkey@artefactual.com, Artefactual Systems<br />
* Justin Simpson, jsimpson@artefactual.com, Artefactual Systems<br />
<br />
There are many different software applications and systems being used in collecting institutions to handle all aspects of managing their digital collections. Within a single institution, it is possible to have several tools with overlapping functionality. Sometimes the biggest gains in functionality and productivity come from a focus on connecting these systems together. <br />
<br />
In this talk we will present several examples of integration and collaboration that we have been involved in while working on the Archivematica project. Examples of integrations with both open source and proprietary systems, as well as examples of collaborative development processes.<br />
<br />
== BYOB: Build Your Own Bootstrap ==<br />
<br />
* Axa Mei Liauw, aliauw@princeton.edu, Princeton University Library<br />
* Kevin Reiss, kr2@princeton.edu, Princeton University Library<br />
<br />
Bootstrap is awesome! It allows for quick and easy front-end development without demanding too much time with the design of the user interface. A framework like Bootstrap can also help libraries address one of our top usability problems: wild inconsistency of styles and layouts across our own in-house applications and websites.<br />
<br />
However, what if you do not want to compromise your creativity and make your project visually stand out? With enough Sass or Less knowledge it is possible to highly customize Bootstrap to fit your needs, but in the end you still end up with your design and code buying into Bootstrap's markup and design conventions, which are not always what you want. Sometimes you simply want to start with a clean slate and not fight the framework and use only the components and features you need.<br />
<br />
In that case, build your own Bootstrap! In this talk we will discuss techniques for using some of the emerging tools from the front-end development and design communities to create a maintainable, modular in-house Sass toolkit that we are implementing within a variety of tools including Drupal, Rails applications, in house PHP applications, as well as within vendor solutions like Libguides and ILLiad. Some specific tools we will discuss are Grunt, Bower, and Sass tools like Singularity, Breakpoint, and Bourbon.</div>Kevinreisshttps://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&diff=420172015 Prepared Talk Proposals2014-11-07T23:04:07Z<p>Kevinreiss: Kevin Reiss Addition</p>
<hr />
<div>Code4lib 2015 is a loosely-structured conference that provides people working at the intersection of libraries/archives/museums/cultural heritage and technology with a chance to share ideas, be inspired, and forge collaborations. For more information about the Code4lib community, please visit http://code4lib.org/about/. <br />
The conference will be held at the Portland Hilton & Executive Tower in Portland, Oregon, from February 9-12, 2015.<br />
<br />
'''Proposals for Prepared Talks:'''<br />
<br />
We encourage everyone to propose a talk.<br />
<br />
Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:<br />
* Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software<br />
* Tools and technologies – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)<br />
* Technical issues - Big issues in library technology that should be addressed or better understood<br />
* Relevant non-technical issues – Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc.<br />
<br />
Proposals can be submitted through Friday, November 7, 2014 at 5pm PST (GMT−8). Voting will start on November 11, 2014 and continue through November 25, 2014. The URL to submit votes will be announced on the Code4Lib website and mailing list and will require an active code4lib.org account to participate. The final list of presentations will be announced in early- to mid-December.<br />
<br />
'''Proposals for Prepared Talks:'''<br />
<br />
Log in to the Code4lib wiki and edit this wiki page using the prescribed format. If you are not already registered, follow the instructions to do so.<br />
Provide a title and brief (500 words or fewer) description of your proposed talk.<br />
If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist voters in opening the conference to new presenters.<br />
<br />
Please follow the formatting guidelines:<br />
<br />
<pre><br />
<br />
== Talk Title: ==<br />
<br />
* Speaker's name, email address, and (optional) affiliation<br />
* Second speaker's name, email address, and affiliation, if second speaker<br />
<br />
Abstract of no more than 500 words.<br />
<br />
</pre><br />
<br />
'''Talk Proposals'''<br />
== Zines + Gamification = Awesomest Metadata Literacy Outreach Event Ever! ==<br />
<br />
* [http://www.JenniferHecker.info Jennifer Hecker], jenniferraehecker@gmail.com, [http://www.lib.utexas.edu/subject/zines University of Texas Libraries] & [http://www.AustinFanzineProject.org Austin Fanzine Project]<br />
* [http://anomalily.net/ Lillian Karabaic], librarian@iprc.org, [http://www.iprc.org/ Independent Publishing Resource Center] (Portland)<br />
<br />
In academic libraries, and elsewhere, the popularity of zine (a magazine produced for love, not profit) collections is on the rise. At the same time, metadata literacy is becoming an increasingly important skill, helping people navigate and understand digital environments and interactions. We have found a way to teach metadata literacy to the general public that isn’t super-boring – in fact, we’ve made it downright fun!<br />
<br />
First, volunteer zine librarian Lillian Karabaic of Portland’s Independent Publishing Resource Center facilitated the creation of a gamified cataloging interface for the IPRC’s annual Raiders of the Lost Archives backlog-busting 24-hour volunteer cataloging event.<br />
<br />
Then, archivist Jennifer Hecker facilitated the adaptation of the IPRC’s game for use in a similar, but also very different context – promoting UT Libraries newly-acquired zine collections. The main goal of the academic-library-based event was increasing excitement around the collections, but with the side goal of building metadata literacy, and introducing an understanding of library cataloging issues.<br />
<br />
The Texas modification also conforms to the xZINECOREx metadata schema developed by the national [http://zinelibraries.info/ Zine Librarians Interest Group], and triggered interesting conversations with the Libraries’s cataloging department about evolving metadata standards and how to incorporate the products of crowd-sourcing projects into existing workflows.<br />
<br />
Both games will be demoed.<br />
<br />
We have never presented at Code4lib.<br />
<br />
== Do the Semantic FRBRoo ==<br />
* Rosie Le Faive, rlefaive@upei.ca, University of Prince Edward Island<br />
<br />
[http://www.islandora.ca Islandora] is great for creating repositories of any data type, but how can you model meaningful relationships between digital objects and use them to tell a story?<br />
<br />
At UPEI, I’m assembling an ethnography of Prince Edward Island’s traditional fiddle music that includes musical clips, video clips, oral histories, musical notation, images, and ethnographic commentaries. In order to present an exhibition-style site, I’m tying these digital objects together via the people, places, events, tunes and topics that they share or describe. <br />
<br />
To describe the relationships, I’m extending Islandora to use [http://www.cidoc-crm.org/frbr_inro.html FRBRoo], a vocabulary that combines the FRBR model with CIDOC-CRM, the the object-oriented museum documentation ontology. These modules being developed will allow other researchers to create a structured, navigable digital repository of diverse object types, that uses Islandora as an exhibition platform. <br />
<br />
== Our $50,000 Problem: Why Library School? ==<br />
* Jennie Rose Halperin, jhalperin@mozilla.com, Mozilla Corporation<br />
<br />
57 library schools in the United States are churning out approximately 100 graduates per year, many with debt upwards of $50,000. According to ONet, [http://www.inthelibrarywiththeleadpipe.org/2011/is-the-united-states-training-too-many-librarians-or-too-few-part-1/ 84% of library jobs in the US require an MLS.] The library profession is [http://dpeaflcio.org/programs-publications/issue-fact-sheets/library-workers-facts-figures/) 92% white and 82% female and entry-level librarians can expect to make $32,500 per year.]<br />
<br />
Contrasted with developers, who are almost [http://www.ncwit.org/blog/did-you-know-demographics-technical-women 90% male] and can expect to make [http://www.forbes.com/sites/jennagoudreau/2011/06/01/best-entry-level-jobs/ $70,000 in an entry-level position,] these numbers are dismal.<br />
<br />
According to a recent survey, the top skill that outgoing library students want to know is “programming” and yet many MLS programs still consider Microsoft Word an essential technology skill.<br />
<br />
What is going on here? Why do we accept this fate, where mostly female debt-burdened professionals continue to be thrown onto the work force without the education their expensive degrees promised?<br />
<br />
As a community we need to come together to stop this cycle. We need to provide better support and mentorship to diversify and keep the profession relevant and help librarianship move into the future it deserves.<br />
<br />
This talk will walk through the challenges of navigating a hostile employment environment as well as present models for better development and future state imagining.<br />
<br />
== No cataloging software? Need more than Dublin Core? No problem!: Experiences with CollectiveAccess ==<br />
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University<br />
* Rachel Wittmann, rwittma@clemson.edu, Clemson University<br />
<br />
Clemson University Libraries has implemented the open-source software CollectiveAccess for customized digital collection needs. CollectiveAccess is an open-source project with the goal of providing a flexible way to manage and publish museum and archival collections. There are several applications associated with the projects; most used are: Providence (for cataloging and entering metadata) and Pawtucket (for displaying objects in a collection for the public). It has many profiles readily available for installing with existing library standards, such as Dublin Core, and there is a robust syntax for creating your own profiles to fit custom tailored metadata schemas. Plus, the user interface allows you to modify the metadata profile quickly and easily.<br />
<br />
In this talk, we will discuss:<br />
* Our experiences with installing Providence and creating an installation profile that satisfies the needs of many of the Clemson Libraries digital archiving processes. <br />
* The stumbling blocks experienced in that process and how they were resolved.<br />
* The available plugins sourcing widely used authorities, such as Library of Congress thesauri and GeoNames.org, and how they have been used by our projects. <br />
* A brief overview of the export and import functions and also current workflow practices within Providence.<br />
* Future plans & the role of CollectiveAccess at Clemson University Libraries<br />
<br />
== Getting ContentDM and Wordpress to Play Together ==<br />
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University<br />
<br />
Clemson University Libraries has a very strong program for digitizing and archiving photographs, and the Digital Imaging team processes many hundreds of photographs every month. These images are managed using different methods, including ContentDM, a digital collection manager.<br />
<br />
ContentDM provides various methods for searching and displaying photographs, along with their metadata. However, recent initiatives have resulted in the need to leverage those collections into exhibits displayed on other library-related websites, such as our Special Collections unit. The Clemson Libraries has invested heavily in Wordpress as our content management system of choice, and it seemed most efficient not to have to export and import images into our Wordpress sites in order to provide exhibited images.<br />
<br />
Fortunately, ContentDM has provided an API to many of their functions, allowing the extraction of metadata and even rescaled images through URLs. This project has been developing a plugin for Wordpress that integrates with ContentDM through shortcodes that Wordpress editors can easily include in their content. These shortcodes allow editors to choose how many images, which images from which collections, thumbnail sizes, etc. to display in different gallery styles. Plans are for it to allow integration with different plugins such as Fancybox and Masonry.<br />
<br />
In this presentation, I will demonstrate the current state of the plugin and discuss future plans. <br />
<br />
==Refinery — An open source locally deployable web platform for the analysis of large document collections==<br />
<br />
* [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com<br />
<br />
Refinery is an open source web platform for the analysis of large unstructured document collections. It extracts meaningful semantic themes within documents also known as "topics" which can be thought of as word clouds composed of terms that highly co-occur with one another. Once this semantic index is formed, one can extract relevant documents related to these topics and further refine their contents through a summarization process that allows users to search for phrases that are relevant to them within the corpus. The goal of Refinery is to make this whole process easier and to provide some of the latest scalable versions of these learning algorithms in an intuitive web-based interface. Refinery is also meant to be run locally, thus bypassing the need for securing document collections over the internet. The talk will go through some of the technologies involved and a demo of the app.<br />
<br />
For more info check out http://www.docrefinery.org.<br />
<br />
==Drupal 8 — Evolution & Revolution==<br />
<br />
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com<br />
<br />
Drupal 8 is in beta and nearing release. Among its many features, it notably has become more developer friendly through its adoption of the Symfony PHP framework along with Symfony's outstanding set of libraries (like Guzzle) and tools (like Composer). And, in implementing the Twig theming system, it is can begin to escape PHPtemplate. These moves also make it easier to create headless systems that uses Angular.js and other systems for presentation, or even forgo presentation entirely.<br />
<br />
From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.<br />
<br />
==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==<br />
<br />
* [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]], stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]<br />
<br />
GameSalad is a popular tool for developing mobile and desktop games with little actual programming. In this presentation, Stan Bogdanov breaks down the development process he followed while building [https://github.com/stanrb/mobiLit mobiLit], a mobile app with the goal of being the first open-source gamified information literacy app to be used as part of a college-level information literacy curriculum. He will go through the basics of using GameSalad to create an app that can be easily customized by non-programmers and the instructional principles used to teach the material in a mobile medium. Stan will also go through two qualitative design studies he did on the app and discuss their results and the lessons learned from building mobiLit. The session will conclude with an overview of the next steps for the [https://github.com/stanrb/mobiLit mobiLit project].<br />
<br />
==The Impossible Search: Pulling data from multiple unknown sources==<br />
<br />
* Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com <br />
<br />
It's easy to search data you know the structure of, but what if you need to pull in data from sources that don't have a standard structure. The ability to search community events along with your standard catalog search results is an example, but often the only way to pull these events is through XML, JSON, (Insert structured format here), or even just raw html. But how do you get that structure? That simple question is what makes this impossible. The process to define and process this structure takes a lot of manual labor, especially if the data you are pulling is just HTML, and then every time you add data to the index you have to run all the data through a script to pull in data in a format Solr or an other index can use. This talk will focus on Solr, but the principles explained will apply to many other indexes.<br />
<br />
==What! You're Not Using Docker?==<br />
<br />
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com<br />
<br />
Boring part: Docker[1] is a container system that provides benefits similar to virtualization with only a fraction of the overhead. Scintillating part: Docker can host between four to six times the number of service instances than systems such as Xen or VMWare on a given piece of hardware. But thats not all! Docker also makes it simple(r) to create transportable instances, so you can spin up development servers on your laptop.<br />
<br />
*[1]https://www.docker.com/<br />
<br />
== Video Accessibility, WebVTT, and Timed Text Track Tricks ==<br />
<br />
* Jason Ronallo, jronallo@gmail.com, NCSU Libraries<br />
<br />
Video on the Web presents new challenges and opportunities. How do you make your video more accessible to those with various disabilities and needs? I'll show you how. This presentation will focus on how to write and deliver captions, subtitles, audio descriptions, and timed metadata tracks for Web video using the WebVTT W3C standard. Encoding timed text tracks in this way opens up opportunities for new functionality on your websites beyond accessibility. The presentation will show some examples of the potential for using timed text tracks in creative ways. I'll cover all the HTML and JavaScript you will need to know as well as some of the CSS and other bits you could probably do without but are too fun to pass up.<br />
<br />
== Categorizing Records with Random Forests ==<br />
<br />
* Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library<br />
Academic libraries are increasingly responsible for providing ingest, search, discovery, and analysis for data sets. Emerging techniques from data science and machine learning can provide librarians and developers with an opportunity to generate new insights and services from these document collections. This presentation will provide a brief overview of common machine learning classification techniques, then dive into a more detailed example using a random forest to assign keywords to research data sets. The talk will emphasize the insight that can be gained from machine learning rather than the inner workings of the algorithms. The overall goal of this presentation is to provide librarians and developers with the context to recognize an opportunity to apply machine learning categorization techniques at their home campuses and organizations. <br />
<br />
== Data Science in Libraries ==<br />
<br />
* Devon Smith, smithde@oclc.org, OCLC<br />
<br />
Data Science is increasing in buzz and hype. I'll go over what it is, what it isn't, and how it fits in libraries.<br />
<br />
== PDF metadata extraction for academic literature == <br />
<br />
* Kevin Savage, kevin.savage at mendeley.com, Mendeley<br />
* Joyce Stack, joyce.stack at mendeley.com, Mendeley<br />
<br />
Mendeley recently added a, "document from file," endpoint to its API which attempts to extract metadata such as title and authors directly from PDF files. This talk will describe at a high level the machine learning methods we used including how we measured and tuned our model. We will then delve more deeply into our stack, the tools we used, some of the things that didn't work and why PDFs are the worst thing ever to compute over.<br />
<br />
== Giving Users What They Want: Record Grouping in VuFind ==<br />
<br />
* Mark Noble, mark@marmot.org, [//www.marmot.org Marmot Library Network]<br />
<br />
In 2013, Marmot did extensive usability studies with patrons to determine what was difficult in the catalog. Many patrons had problems sifting through all of the various formats and editions of a title. In 2014 we developed a method for [//mercury.marmot.org/Union/Search?lookfor=divergent grouping records] so only a single work is shown in search results and all formats and editions are listed under that work. We will discuss our definition of a 'work' based on FRBR principles; combining meta data from MARC records with metadata from other sources like OverDrive; the technical details of Record Grouping; the design decisions made during implementation; and the reaction from users and staff.<br />
<br />
== Topic Space: a mobile augmented reality recommendation app ==<br />
<br />
* Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign<br />
<br />
The Topic Space module (http://minrvaproject.org/modules_topicspace.php ) was developed with an IMLS Sparks! Grant to investigate augmented reality technologies for in-library recommendations. The funding allowed for sustained university community collaboration by the University Library, the Graduate School of Library and Information Science, as well as graduate student programmers sourced from the Department of Computer Science. Collaborators designed app functionality and identified relevant open source libraries that could power optical character recognition (OCR) functionality from within the mobile phone.<br />
<br />
Topic space allows a user to take a picture of an item's call number in the book stacks. The module will show the user other books that are relevant but that are not shelved nearby. It can also show users books that are normally shelved here but that are currently checked out. Recommendations are based on Library of Congress subject headings and ILS circulation data which indicate recommendation candidates based on total check-outs. <br />
<br />
Research questions included development of back end (server-side) pattern matching algorithms for recommendations, and a rapid formative evaluation of interface design that would provide optimal user experience for navigation of the book stacks as a context to recommendations.<br />
<br />
Along with the Topic Space native app, grant collaborators prototyped web based recommendations which could serve as a new way of providing readers advisory and “more like this” recommendations from discovery interfaces accessed through desktop browsers. Outcomes of the grant include the availability of the [https://play.google.com/store/apps/details?id=edu.illinois.ugl.minrva Topic Spaces module within Minrva app on the Android Play store] and an experimental [http://backbonejs.org/ Backbone.js] based [http://minrva-dev.library.illinois.edu Topic Space web app].<br />
<br />
== Leveling Up Your Git Workflow ==<br />
<br />
* Megan Kudzia, moneill@albion.edu, Albion College Library<br />
* Kate Sears, eks11@albion.edu, Albion College Library<br />
<br />
Have you started experimenting with Git on your own, but now you need to include others in your projects? Learn from our mistakes! Transitioning from a one-person git workflow and repo structure, to a structure that includes multiple people (including student workers), is not for the faint of heart. We'll talk about why we decided to work this way, our path to developing a git culture amongst ourselves, conceptual and technical difficulties we've faced, what we learned, and where we are now. Also with pretty pictures (aka workflow drawings).<br />
<br />
== Drone Loaning Program: Because Laptops are so last century ==<br />
<br />
* Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries<br />
* Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries<br />
<br />
At Univ. Maryland we are in the very early stages of looking into allowing our student body get their hands on a drone. Yes that's right we will let students take out a drone for n amount of hours to work on projects of their choosing. The talk will talk about the logistics of getting a program of this sort from concept to "Is the drone available?". If people sign waivers we will also promise not to crash the drone into code4lib attendees.<br />
<br />
== Got Git? Getting More Out of Your GitHub Repositories ==<br />
<br />
* Terry Brady, twb27@georgetown.edu, Georgetown University Library<br />
<br />
This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories. <br />
<br />
In additional to all of the great benefits of using Git for code management, the GitHub interface provides a powerful set of tools to showcase a project and to keep your users informed of developments to your project. These tools can assist with marketing and outreach - turning your code repository into a focus of conversation!<br />
<br />
* [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]<br />
* [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]<br />
* [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]<br />
* [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]<br />
* Gists for code sharing<br />
* Private Repositories and Organizational Groups<br />
* Pull Request Conversation Tracking<br />
* Customized Issue management<br />
<br />
== Quick Wins for Every Department in the Library - File Analyzer! ==<br />
<br />
* Terry Brady, twb27@georgetown.edu, Georgetown University Library<br />
<br />
The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.<br />
* Analyzing Marc Records for the Cataloging department<br />
* Transferring ILS invoices for the University Account System for the Acquisitions department <br />
* Delivering patron fines to the Bursar’s office for the Access Service department<br />
* Summarizing student worker timesheet data for the Finance department<br />
* Validating COUNTER compliant reports for the Electronic Resources department<br />
* Generating ingest packages for the Digital Services department<br />
* Validating checksums for the Preservation department<br />
<br />
Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!<br />
<br />
==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==<br />
<br />
* [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor<br />
<br />
The transition from paper maps to digital ones changed much more than the maps themselves; it changed the very foundation of how we work and how we find each other. Now maps are transforming again. The Geospatial World is moving from GIS systems that are institutionally-focused, expensive, feature-burdened, and binds data into a complicated and demanding user-hostile interface. From this transition from digital to web-based digital geospatial tools has come growth and development in new forms of map-based investigative journalism, activism, scholarship, and business ventures. This talk will highlight the conditions and strategies that made these changes possible as a means to draw a path by which librarians through our own work may follow, dragons notwithstanding. <br />
<br />
== Building Your Own Federated Search ==<br />
<br />
* Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco<br />
<br />
Advances in modern browsers have created some interesting possibilities for federated search. This presentation will cover common techniques and pitfalls in building a federated search. We will discuss what principles guided our decisions when implementing our own federated search. We will show tools we've built and our findings from building and using experimental prototypes.<br />
<br />
Your higher education institution likely offers dozens of online resources for educators, students, researchers, and the public. And each of these online resources likely has its own search tool. But users can't be expected to search in dozens of different interfaces to find what they're looking for. A typical solution for this issue is federated search. <br />
<br />
== Indexing Linked Data with LDPath ==<br />
<br />
* Chris Beer, cabeer@stanford.edu, Stanford University Libraries<br />
<br />
LDPath [1] is a simple query language for indexing linked open data, with support for caching, content negotiation, and integration with non-RDF endpoints. This talk will demonstrate the features and potential of the language and framework to index a resource with links into id.loc.gov, viaf.org, geonames.org, etc to build an application-ready document.<br />
<br />
[1] http://marmotta.apache.org/ldpath/language.html<br />
<br />
== Show Me the Money: Integrating an LMS with Payment Providers ==<br />
<br />
* Josh Weisman, Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group<br />
<br />
In order to provide an easy and convenient way for patrons to pay fines, we are exploring ways to integrate the library management system with online payment providers such as PayPal. With many LMS systems being designed and developed for the cloud, we should be able to provide the frictionless user experience our patrons have come to expect from online transactions. In this session we'll discuss strategies for integration and review a sample application which uses REST APIs from a library management system to integrate with PayPal.<br />
<br />
== Shibboleth Federated Authentication for Library Applications: ==<br />
<br />
* Scott Fisher, scott.fisher@ucop.edu, California Digital Library<br />
* Ken Weiss, ken.weiss@ucop.edu, California Digital Library<br />
<br />
Shibboleth is the most widely-used method to provide single-sign-on authentication to academic applications where users come from many different institutions. Shibboleth, the InCommon education and research trust framework, and the SAML protocol comprise a very powerful - but very complicated - solution to this very complicated problem. Scott and Ken have implemented Shibboleth for multiple library applications. They will share their understanding of the good, the bad, and the underlying spaghetti that makes it all work. Ken will discuss some of the technical aspects of the solution, touching on optimal and non-optimal use cases, administrative challenges, and authorization concerns. Scott will describe the implementation pattern for multi-institution single-sign-on that the California Digital Library has evolved, using the recently released Dash application (http://dash.cdlib.org) as an example.<br />
<br />
==Scientific Data: A Needs Assessment Journey==<br />
<br />
*[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History<br />
<br />
While surveying digital research and collections data in the research science divisions at the American Museum of Natural History in NYC (as a part of my [http://ndsr.nycdigital.org/ National Digital Stewardship Residency] project), I have come across the big data hogs (genome sequencing and CT scanning) and the little pieces of data (images, publications), all equally important to not only scientific discovery, but as nodes in the history of science. <br />
<br />
In this session, I will discuss the development of my needs assessment surveys for scientific datasets and the interview process with Museum curators and researchers as background, seguing into an explanation of the results. I will then combine my findings into preliminary selection criteria to choose tools for digital preservation and management unique to scientific datasets. This will brooke a discussion on emerging standards, tools, and technologies in big data, specific to research science. <br />
<br />
I will conclude with preliminary findings on emerging technology that can be used to answer concerns surrounding the management and digital preservation of these data. I am hoping the Q&A session can be used to both answer questions about my project, and function as a way for you (the larger tech-savy library community) to discuss the tools I’ve touched on in this talk. <br />
<br />
== Feminist Human Computer Interaction (HCI) in Library Software ==<br />
<br />
* Bess Sadler, bess@stanford.edu, Stanford University Libraries<br />
<br />
Libraries are not neutral repositories of knowledge. Library classification systems and search technologies tend to reflect the inequalities, biases, ethnocentrism, and power imbalances of the societies in which they are built [1]. How might we better resist these tendencies in the library software we create? This talk will examine some qualities of feminist HCI (pluralism, self-disclosure, participation, ecology, advocacy, and embodiment) [2] through the lens of library software. <br />
<br />
[1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.<br />
<br />
[2] Bardzell, Shaowen. Feminist HCI: Taking Stock and Outlining an Agenda for Design. CHI 2010: HCI For All. http://dmrussell.net/CHI2010/docs/p1301.pdf<br />
<br />
== Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==<br />
<br />
* Audrey Altman, audrey at dp.la, Digital Public Library of America<br />
* Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America<br />
* Mark Breedlove, mb at dp.la, Digital Public Library of America<br />
<br />
The Digital Public Library of America aggregates metadata for over 8 million objects from more than 24 direct partners, or Hubs, using its Metadata Application Profile (MAP), an RDF metadata application profile based on the Europeana Data Model. After working with the initial system for harvesting, mapping and enhancing our Hub’s metadata for a year, we realized that it was inadequate for working with data at this scale. There were architectural issues; it was opaque to non-developer and partner staff; there were inadequate tools for quality assurance and analysis; and the system was unaware that it was working with RDF data. As the network of Hubs expanded and we ingested more metadata, it became harder and harder to know when or why a harvest, a mapping task, or an enrichment went wrong because the tools for quality assurance were largely inadequate. <br />
<br />
The DPLA Content and Technology teams decided to develop a new system from the ground up to address those problems. Development of Heidrun, the internal version of the new system, started in October 2014. Heidrun’s goals are to make it easier for us to harvest and map metadata from various sources and in variety of schemas to the DPLA MAP, to better enrich that metadata using external data sources, and to actively involve our partners in the ingestion process through access to better QA tools. Heidrun and its componentry are built on Ruby on Rails, Blacklight, and ActiveTriples. Our presentation will give some background on our design principles and processes used during development, the architecture of the system, and its functionality. We plan to release a version of Heidrun and its components as a generalized metadata aggregation system for use by DPLA Hubs and others working to aggregate cultural heritage metadata.<br />
<br />
== OS or GTFO: Program or Perish ==<br />
*Tessa Fallon, tessa.fallon@gmail.com<br />
<br />
Description TBD<br />
<br />
== Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==<br />
* Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries<br />
Would your library like to have large digital signage that displays dynamic information such as library hours, weather, room availability, and more? Have you looked into purchasing large digital signage, only to be turned off by the high price tag and lack of customization available with commercial solutions? Our library has developed a cheap and effective alternative to these systems using HTML 5 authoring software, a large TV, and freely-available APIs from Google, Springshare, and others. At this session, you’ll learn about the system that we have in place for displaying dynamic and easily-updatable information on our library’s large digital display, and how you can easily create something similar for your library.<br />
<br />
== REPOX: Metadata Blender ==<br />
<br />
* John Mignault, jmignault@metro.org, Empire State Digital Network<br />
<br />
With the growth in the number of hubs providing metadata to the Digital Public Library of America, many of them are using REPOX, a tool originally created for the Europeana project, to aggregate disparate metadata feeds and transform them into formats suitable for ingest into DPLA. The Empire State Digital Network, the forthcoming DPLA service hub for NY state, is using it to prepare for our first ingest into DPLA in early 2015. We'll take a look at REPOX and its capabilities and how it can be useful for ingesting and transforming metadata, and also discuss some things we've learned in massaging widely varied metadata feeds.<br />
<br />
== Beyond Open Source ==<br />
<br />
* Jason Casden, jmcasden@ncsu.edu, NCSU Libraries<br />
* Bret Davidson, bddavids@ncsu.edu, NCSU Libraries<br />
<br />
The Code4Lib community has produced an increasingly impressive collection of open source software over the last decade, but much of this creative work remains out of reach for large portions of the library community. Do the relatively privileged institutions represented by a majority of Code4Lib participants have a professional responsibility to support the adoption of their innovations?<br />
<br />
Drawing from old and new software packaging and distribution approaches (from freeware to Docker), we will propose extending the open source software values of collaboration and transparency to include the wide and affordable distribution of software. We believe this will not only simplify the process of sharing our applications within the Code4Lib community, but also make it possible for less well resourced institutions to actually use our software. We will identify areas of need, present our experiences with the users of our own open source projects, discuss our attempts to go beyond open source, and make an argument for the internal value of supporting and encouraging a vibrant library ecosystem.<br />
<br />
[[Category:Code4Lib2015]] <br />
[[Category:Talk Proposals]]<br />
<br />
== Making It Work: Problem Solving Using Open Source at a Small Academic Library ==<br />
<br />
* Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology<br />
* Max King, mking9@iit.edu, Illinois Institute of Technology<br />
<br />
The Illinois Institute of Technology campus was added to the National Register of Historic Places in 2005, and contains a building, Mies van der Rohe's S.R. Crown Hall, that was named a National Historic Landmark in 2001. Creating a digital resource that can adequately showcase the campus and its architecture is challenge enough in and of itself, but doing so as a two-person team of relative newcomers, at a university library without dedicated programmers on staff, ups the ante considerably.<br />
The challenges of technical know-how, staff time, and funding are nothing new to anyone working on digital projects at a university library, and are amplified when doing so at a smaller institution. This talk covers the conception, development, and design of the campus map site that was built, concentrating on the problem-solving strategies developed to cope with limited technical and financial resources.<br />
We'll talk about our approach to development with Open Source software, including Omeka, along with the Neatline and Simile Timeline plugins. We'll also discuss the juggling act of designing for mobile mapping functionality without sacrificing desktop design, weighing the costs of increased functionality versus our ability to time-effectively include that functionality, and the challenge of building a site that could be developed iteratively, with an eye towards future enhancement and sustainability. Finally, we’ll provide recommendations for other librarians at smaller institutions for their own efforts at digital development.<br />
<br />
== Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==<br />
<br />
* Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art<br />
<br />
The Museum of Modern Art has amassed a large collection of audiovisual materials over its many decades of existence. In order to preserve these materials, much of the audiovisual collection has been digitized. This is a complex process involving numerous steps and devices, and the methods used for digitization can have an effect on the quality of the file that is preserved. Therefore, knowing exactly how something was digitized is critical for future stewards of these objects to be able to properly care for and preserve them. However, detailed technical information about the processes involved in the digitization of audiovisual materials is not defined explicitly in most metadata schemas used for audiovisual materials. In order to record process history using existing metadata standards, some level of creativity is required to allow existing standards to express this information.<br />
<br />
This talk will detail different metadata standards, including PBCore, PREMIS, and reVTMD, that can be implemented as methods of recording this information. Specifically, the talk will examine efforts to integrate this metadata into the Museum of Modern Art’s new digital repository, the DRMC. This talk will provide background on the DRMC as well as MoMA’s specific institutional needs for process history metadata, then discuss different metadata implementations we have considered to document process history.<br />
<br />
== Pig Kisses Elephant: Building Research Data Services for Web Archives ==<br />
<br />
* Jefferson Bailey, jefferson@archive.org, Internet Archive<br />
* Vinay Goel, vinay@archive.org, Internet Archive<br />
<br />
More and more libraries and archives are creating web archiving programs. For both new and established programs, these archives can consist of hundreds of thousands, if not millions, of born-digital resources within a single collection; as such, they are ideally suited for large-scale computational study and analysis. Yet current access methods for web archives consist largely of browsing the archived web in the same manner as browsing the live web and the size of these collections and complexity of the WARC format can make aggregate analysis difficult. This talk will describe a project to create new ways for users and researchers to access and study web archives by offering extracted and post-processed datasets derived from web collections. Working with the 325+ institutions and their 2600+ collections within the Archive-It service, the Internet Archive is building methods to deliver a variety of datasets culled from collections of web content, including extracted metadata packaged in JSON, longitudinal link graph data, named entities, and other types of data. The talk will cover the technical details of building dataset production pipelines with Apache Pig, Hadoop, and tools like Stanford NER, the programmatic aspects of building data services for archives and researchers, and ongoing work to create new ways to access and study web archives.<br />
<br />
== Awesome Pi, LOL! ==<br />
<br />
* Matt Connolly, mconnolly@cornell.edu, Cornell University Library<br />
* Jennifer Colt, jrc88@cornell.edu, Cornell University Library<br />
<br />
Inspired by Harvard Library Lab’s “Awesome Box” project, Cornell’s Library Outside the Library (LOL) group is piloting a more automated approach to letting our users tell us which materials they find particularly stunning. Armed with a Raspberry Pi, a barcode scanner, and some bits of kit that flash and glow, we have ventured into the foreign world of hardware development. This talk will discuss what it’s like for software developers and designers to get their hands dirty, how patrons are reacting to the Awesomizer, and LOL’s not-afraid-to-fail philosophy of experimentation.<br />
<br />
== You Gotta Keep 'em Separated: The Case for "Bento Box" Discovery Interfaces ==<br />
<br />
* Jason Thomale, jason.thomale@unt.edu, University of North Texas Libraries<br />
<br />
I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.<br />
<br />
The thing is, practically all of us--in academic libraries at least--have a similar set up for discovery, with just a few variations, and so talking about it still seems useful. Stop me if this sounds familiar. You've got a single search box on the library homepage as a starting point for discovery. And it's probably a tabbed affair, with an option for searching the catalog for books, an option for searching a discovery service for articles, an option for searching databases, and maybe a few others. Maybe you have an option to search everything at once--probably the default, if you have it. And, if you're a crazy hepcat, maybe you ''only'' have your one search that searches everything, with no tabs.<br />
<br />
Now, the question is, for your "everything" search, are you doing a combined list of results, or are you doing it bento-box style, with a short results list from each category displayed in its own compartment?<br />
<br />
At UNT, we've been holding off on implementing an "everything" search, for various reasons. One reason is that the evidence for either style hasn't been very clear. There's this persistent paradox that we just can't reconcile: users tell us, through word and action, that they prefer searching Google, yet, libraries aren't Google, and there are valid design reasons why we shouldn't try to oversimplify our discovery interfaces to be like Google. And there's user data that supports both sides.<br />
<br />
Holding off on making this decision has granted us 2 years of data on how people use our tabbed search interface that does ''not'' include an "everything" search. Recently I conducted a thorough analysis of this data--specifically the usage and query data for our catalog and discovery system (Summon). And I think it helps make the case for a bento box style discovery interface. To be clear, it isn't exactly the smoking gun that I was hoping for, but the picture it paints I think is telling. At the very least, it points away from a combined-results approach.<br />
<br />
I'm proposing a talk discussing the data we've collected, the trends we've seen, and what I think it all means--plus other reasons that we're jumping on the "bento box" discovery bandwagon and why I think "bento box" is at this point the path that least sells our souls.<br />
<br />
== Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift ==<br />
<br />
* Ashley Blewer!, ashley.blewer@gmail.com<br />
<br />
Checksum technology is used all over the place, from git commits to authenticating Linux packages. It is most commonly used in the digital preservation field to monitor materials in storage for changes that will occur over time or used in the transmission of files during duplication. But do you even checksum, bro? I want this talk to move checksums from a position of mysterious macho jargon to something everyone can understand and want to use. I think a lot of people have heard of checksum but don’t know where to begin when it comes to actually using it at their institution. And cryptography is hella intimidating! This talk will cover what checksums are, how they can be integrated into a library or archival workflow, protecting collections requiring additional levels of security, algorithms used to verify file fixity and how they are different, and other aspects of cryptographic technology. Oh, and please note that all points in this talk will be emphasized or lightly performed through Taylor Swift lyrics. Seriously, this talk will consist of at least 50% Taylor Swift. Can you, like, even?<br />
<br />
== Level Up Your Coding with Code Club (yes, you can talk about it) ==<br />
<br />
* Coral Sheldon-Hess, coral@sheldon-hess.org<br />
<br />
Reading code is a necessary part of becoming a better developer. It gives you more experience and more insight into How Things Are (or Aren't) Done; it builds your intuition about how to solve problems with code; and it increases your confidence that you, too, can tackle whatever technological problems you're facing.<br />
<br />
But you don't have to read code alone! (Which is good. It's really not fun to read code alone.) <br />
<br />
In late 2014, a group of librarians formed two Code Clubs, inspired by [http://bloggytoons.com/code-club/ this talk by Saron] (of Bloggytoons fame). I'd like to tell you about how we've structured our Code Clubs, what has gone well, what we've learned, and what you need to do to form your own Code Club. I'll share a list of the codebases we've looked at, too, to help you get your own Code Club off the ground! <br />
<br />
== The Growth of a Programmer ==<br />
<br />
* [[User:jgo | Joshua Gomez]], Getty Research Institute, jgomez@getty.edu<br />
<br />
Just like other creative endeavors, software developers can experience periods of great productivity or find themselves in a rut. After contemplating the alternating periods in my own career I've noticed several factors that have effected my own professional growth and happiness, including: mentorship, structure, community, teamwork, environment, formal education, etc. Not all of the factors need to be present at all times; but some mixture of them is critical for continued growth. In this talk, I will articulate these factors, discuss how they can effect a developer's career, and how they can be sought out when missing. This talk is aimed at both new developers looking to strike their own path as well as the veterans that lead or mentor them.<br />
<br />
== Developing a Fedora 4.0 Content Model for Disk Images ==<br />
<br />
* Matthew Farrell, matthew.j.farrell@duke.edu, Duke University Libraries<br />
* Alexandra Chassanoff, achass@email.unc.edu, BitCurator Access Project Manager<br />
<br />
As the acquisition of born-digital materials grows, institutions are seeking methods to facilitate easy ingest into their repositories and provide access to disk images and files derived or extracted from disk images. In this session, we describe our development of a Fedora 4.0 Content model for disk images, including acceptable image file formats and the rationale behind those choices. We will also discuss efforts to integrate the disk image content model into the BitCurator Access environment. Unlike generalized, format-agnostic content models which might treat the disk image as a generic bitstream, a content model designed for disk images enables expression of relationships among associated content in the collection such as files extracted from images and other born-digital and digitized material associated with the same creator. It also enables capture of file-system attributes such as file paths, timestamps, whether files are allocated/deleted, etc. Further, a disk image content model suggests further steps repositories can take in order to transform and re-use associated metadata generated during the creation and forensic analysis of the disk image.<br />
<br />
== Data acquisition and publishing tools in R ==<br />
<br />
* Scott Chamberlain, scott@ropensci.org, rOpenSci/UC Berkeley - first-time presenter<br />
<br />
R is an open source programming environment that is widely used among researchers in many fields. R is powerful because it's free, increasingly robust, and facilitates reproducible research, an increasingly sought after goal in academia. Although tools for data manipulation/visualization/analysis are well developed in R, data acquisition and publishing tools are not. rOpenSci is a collaborative effort to create the tools necessary to complete the reproducible research workflow. This presentation discusses the need for these tools, including examples, including interacting with the repositories Mendeley, Dryad, DataONE, and Figshare. In addition, we are building tools for searching scholarly metadata and acuiring full text of open access articles in a standarized way across metadata providers (e.g., Crossref, DataCite, DPLA) and publishers (e.g., PLOS, PeerJ, BMC, Pubmed). Last, we are building out tools for data reading and writing in Ecologial Metadata Language (EML).<br />
<br />
== SPLUNK: Log File Analysis ==<br />
<br />
* Jim LeFager, jlefager@depaul.edu, DePaul University Library<br />
DePaul University Library recently took over monitoring and maintaining of the library EZproxy servers this past year and using Splunk, a machine data analysis tool, we are able to gather information and statistics on our electronic resource usage in addition to monitoring the servers. Splunk is a tool that can collect, analyze, and visualize log files and other machine data in real time and this has allowed for gathering realtime usage statistics for our electronic resources allowing us to filter by multiple facets including IP Range, Group Membership (student, faculty), so that we can see who is accessing our resources and from where. Splunk allows our library to query our data and create rich custom dashboards as well as create alerts that can be triggered when certain conditions are met, such as error codes, which can send an email alert to a group of users. We will be leveraging Splunk to monitor all library web applications going forward. This talk will review setting up Splunk and best practices in using the available features and customizations available including creating queries, alerts, and custom dashboards. <br />
<br />
== Your code does not exist in a vacuum ==<br />
* Becky Yoose, yoosebec at grinnell dot edu, Grinnell College (Done a lightning talk, MC duties, but have not presented a prepared talk)<br />
<br />
“If you have something to say, then say it in code…” - Sebastian Hammer, code4lib 2009<br />
<br />
In its 10 year run, code4lib has covered the spectrum of libtech development, from search to repositories to interfaces. However, during this time there has been little discussion about this one little fact about development - code does not exist in a vacuum. <br />
<br />
Like the comment above, code has something to say. A person’s or organization’s culture and beliefs influences code in all steps of the development cycle. What development method you use, tools, programming languages, licenses - everything is interconnected with and influenced by the philosophies, economics, social structures, and cultural beliefs of the developer and their organization/community.<br />
<br />
This talk will discuss these interconnections and influences when one develops code for libraries, focusing on several development practices (such as “Fail Fast, Fail Often” and Agile) and licensing choices (such as open source) that libtech has either tried to model or incorporate into mainstream libtech practices. It’ll only scratch the surface of the many influences present in libtech development, but it will give folks a starting point to further investigate these connections at their own organizations and as a community as a whole.<br />
<br />
tl;dr - this will be a messy theoretical talk about technology and libraries. No shiny code slides, no live demos. You might come out of this talk feeling uncomfortable. Your code does not exist in a vacuum. Then again, you don’t exist in a vacuum either.<br />
<br />
== The Metadata Hopper: Mapping and Merging Metadata Standards for Simple, User-Friendly Access ==<br />
<br />
* Tracy Seneca, tjseneca@uic.edu, University of Illinois at Chicago<br />
* Esther Verreau: verreau1@uic.edu, University of Illinois at Chicago<br />
<br />
The Chicago Collections Consortium: 15 institutions and growing! 8 distinct EAD standards! At least 3 permutations of MARC, and we lost count of the varieties of custom CONTENTdm image collections. Not to mention the 14,730 unique subject terms, nearly all of which lead our poor end-users to exactly one organization's content. <br />
<br />
All large content aggregation projects have faced this challenge, and there are a few emerging tools to help us wrangle disparate metadata into new contexts. The Metadata Hopper is one such tool. The Metadata Hopper enables archivists to map their local metadata standards to standardized deposit records, and tags those materials using a shared vocabulary, integrating them into a user-friendly portal without disrupting local practices. In last year's Code4Lib lightning talk we described the challenges that the Chicago Collections Consortium faces in creating shared, in-depth access to archival and digital collections about Chicago history and culture across CCC member organizations. This year, thanks to the Andrew W. Mellon Foundation, we have a working Django application to demonstrate. In this talk we'll discuss the design that enables multiple layers of flexibility, from the ability to accept a variety of metadata standards to designing for an open source audience.<br />
<br />
http://chicagocollectionsconsortium.org<br />
<br />
== Programmers are not projects: lessons learned from managing humans ==<br />
<br />
* Erin White, erwhite@vcu.edu, Virginia Commonwealth University - first-time presenter<br />
<br />
Managing projects is one thing, but managing people is another. Whether we’re hired as managers or grow “organically” into management roles, sometimes technical people end up leading technical teams (gasp!). I’ll talk about lessons I’ve learned about hiring, retaining, and working long-term and day-to-day with highly tech-competent humans. I’ll also talk about navigating the politics of libraryland, juggling different types of projects, and working with constrained budgets to make good things and keep talented people engaged.<br />
<br />
== Practical Strategies for Picking Low-Hanging Fruits to Improve Your Library's Web Usability and UX ==<br />
<br />
* Bohyun Kim, bkim@hshsl.umaryland.edu, University of Maryland, Baltimore<br />
<br />
Have you ever tried to fix an obvious (to you at least!) problem in Web usability or UX (user experience) only to face strong resistance from the library staff? Are you a strong advocate for making library resources, systems, services, and space as usable as possible, but do you often find yourself struggling to get the point across and/or obtain the crucial buy-in from colleagues and administrators? <br />
<br />
There is no shortage of Web usability and UX guidelines. But applying them to a library and implementing desired changes often involve a long and slow process. To tackle this issue, this talk will focus on how to utilize the 'expert review' process (aka 'heuristic evaluation') as a preliminary or even preparatory step before embarking on more time-and-labor-intensive usability testing and user research. Several examples from simple fixes to more nuanced usability and UX issues in libraries will be discussed to your heart's content. The goal of this talk is to provide practical strategies for picking as many low-hanging fruits as possible to make a real (albeit small) difference to your library's Web usability and UX effectively and efficiently.<br />
<br />
== A Semantic Makeover for CMS Data ==<br />
<br />
* Bill Levay, wjlevay@gmail.com, Linked Jazz Project<br />
<br />
How can we take semi-structured but messy metadata from a repository like CONTENTdm and transform it into rich linked data? Working with metadata from Tulane’s Hogan Jazz Archive Photography Collection, the Linked Jazz Project used Open Refine and Python scripts to tease out proper names, match them with name authority URIs, and specify FOAF relationships between musicians who appear together in photographs. Additional RDF triples were created for any dates associated with the photos, and for those images with place information we employed GeoNames URIs. Historical images and data that were siloed can now interact with other datasets, like Linked Jazz’s rich set of names and personal relationships, and can be visualized [link to come] or otherwise presented on the web in any number of ways. I have not previously presented at a Code4Lib conference.<br />
<br />
== Taking User Experience (UX) to new heights ==<br />
<br />
* Kayne Richens, kayne.richens@deakin.edu.au, Deakin University<br />
<br />
User Experience, or "UX", is for more than just websites. At Deakin University Library we're exploring ways to improve the user experience inside our campus library spaces, by putting new technologies front and centre in the overall experience for our students. How are we doing this? We’re collaborating with the University's IT department and exploring the following Library-changing opportunities:<br />
<br />
- Augmented Reality for Way-finding: We’re tackling that infamous thing that all Libraries can't get right – way-finding. We're enhancing library tour information and way-finding experiences by introducing augmented reality solutions.<br />
<br />
- Heat mapping the library with wi-fi: We’re using our existing wi-fi infrastructure to present "heat maps" of library space utilisation, allowing our users to easily locate the space that best suits their needs, whether it be busy spaces to collaborate, or quiet spaces to study. And by overlaying computer usage and group study room bookings, users can quickly locate the space they need.<br />
<br />
- Video chat library service: We’re piloting video-conferencing facilities in our group study rooms and spaces, connecting users and librarians and other professionals.<br />
<br />
This talk will look at how these different technologies will be brought together to provide improved user experiences, as well some of the evidence and reasons that helped us to identify our needs, so you can too.<br />
<br />
==How to Hack it as a Working Parent: or, Should Your Face be Bathed in the Blue Glow of a Phone at 2 AM?==<br />
<br />
*Margaret Heller, Loyola University Chicago, mheller1@luc.edu<br />
*Christina Salazar, California State University Channel Islands, christina.salazar@csuci.edu<br />
*May Yan, Ryerson University, may.yan@ryerson.ca<br />
<br />
Modern technology has made it easier than ever for parents employed in technical environments to keep up with work at all hours and in all locations. This makes it possible to work a flexible schedule, but also may lead to problems with work/life balance and furthering unreasonable expectations about working hours. Add to that shifting gender roles and limited paid parental leave in the United States and you have potential for burnout and a certainty for anxiety. It raises the additioal question of whether the “always connected” mindset puts up a barrier to some populations who otherwise might be better represented in open source and library technology communities. <br />
<br />
This presentation will address tools that are useful for working parents in technical library positions, and share some lessons learned about using these tools while maintaining a reasonable work/life balance. We will consider a question that Karen Coyle raised back in 1996: <br />
“What if the thousands of hours of graveyard shift amateur hacking wasn't really the best way to get the job done? That would be unthinkable.” <br />
<br />
For those who are able to take an extended parental leave, we will present strategies for minimizing the impact to your career and your employer. For those (particularly in the United States) who are only able to take a short leave will require different strategies. Despite different levels of preparation, all are useful exercises in succession planning and making a stronger workplace and future ability to work a flexible schedule through reviewing workloads, cross-training personnel, hiring contract replacements, and creative divisions of labor. Such preparation makes work better for everyone, kids or no kids or caretakers of any kind.<br />
<br />
==Making your digital objects embeddable around the web==<br />
<br />
* Jessie Keck, jkeck@stanford.edu, Stanford University Libraries<br />
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries<br />
<br />
With more and more content from our digital repositories making their way into our discovery environments we quickly realize that we’re repeatedly re-inventing the wheel when it comes to creating “Viewers” for these digital objects. With various different types of viewers necessary (books, images, audio, video, geospatial data, etc) the burden of getting these viewers into various environments (topic guides, blogs, catalogs, etc) becomes exponential.<br />
<br />
In this talk we’ll discuss how Stanford University Libraries implemented an oEmbed service to create an extensible viewer framework for all of its digital content. Using this service we’ve been able to easily integrate viewers into various discovery applications as well as make it easy for end users who discover our objects to easily embed customized versions into their own websites and blogs.<br />
<br />
==So you want to make your geospatial data discoverable==<br />
<br />
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries<br />
<br />
Finding data for research or coursework can be one of the most time intensive tasks for a scholar or student. We introduce GeoBlacklight, an open source, multi-institutional software project focused on solving these common challenges at institutions across the world. GeoBlacklight prioritizes user experience, integrates with many GIS tools, and streamlines the use and organization of geospatial data. This talk will provide an introduction to the software, demonstrate current functionality, and provide a road map for future work.<br />
<br />
== Clueless-Driven Development: How I learned to migrate to Fedora 4 ==<br />
<br />
* Adam Wead, awead@psu.edu, Penn State University<br />
<br />
Recently I was tasked with migrating the content from our Fedora3 repository to the new Fedora4 repository architecture.<br />
Despite a wealth of community support, I had no idea how to approach, or even begin to solve this problem. I knew I<br />
wanted to follow best practices and use test-driven development to build my solution, but had no idea where to start.<br />
Despite this initial setback, I was able to start writing tests with only a vague understanding of the problem. As my<br />
tests exposed where my understanding of the problem was flawed, my code evolved, and within a week I had arrived at a<br />
working solution that exhibited all the hallmarks of good testing and software design.<br />
<br />
This talk recounts the process I went through from starting with practically nothing, to arriving at a working solution.<br />
You can follow the rules of test-driven development, but you can write tests in an expressive way to describe the<br />
problem instead of just describing what the code should do. It was also essential to begin testing from an integration<br />
viewpoint as opposed to a unit one, because at the outset the units were unknown and were later realized through further<br />
development. For the presentation, I will be demonstrating using RSpec and Ruby. All the code examples will be related<br />
to the Hydra software stack; however, I hope to show that the processes at work will be applicable in any context.<br />
<br />
<br />
== Designing and Leading a Kick A** Tech Team ==<br />
<br />
* Sibyl Schaefer, sschaefer@rockarch.org, Rockefeller Archive Center<br />
<br />
New managers are often promoted without receiving management training, yet management is not something you just figure out. The experience of being expected to know how to manage, yet not being trained to do so often results in new managers feeling isolated and unsure how to move from making to managing. In this talk I’ll focus on my own managerial experience of designing and leading an archival tech team in a small independent archives. Topics covered will include hiring, delegating, creating a team culture, and leading people whose specialized knowledge exceeds your own. The talk take-aways should be applicable to managers and employees at large and small institutions alike.<br />
<br />
<br />
==American (Archives) Horror Story: LTO Failure and Data Loss ==<br />
<br />
* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH<br />
* Casey Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH<br />
<br />
Here’s a story to send shivers down archival spines: when transferring video files off LTO for the American Archive project, WGBH got an initial failure rate of 57%. After repeat tries, the rates improved; still, an unnervingly large percentage of files were never able to be transferred successfully. Even more unnerving, going public with our horror story got a big response from other archives using LTO -- it seems like many institutions are having similarly scary results. What are the real risks with LTO tape? Are there steps that archives should be taking to better circumvent those risks? This presentation will share information about LTO storage failures across archives world and discuss the process of investigating the problem at WGBH by testing different methods of data retrieval from LTO (direct and networked downloads, individual file retrieval and bulk data dump, use of LTO 4 and LTO 6 decks) and using checksum comparisons and file analysis and characterization tools such as ffprobe, mediainfo and exiftool to analyze failed files. We'll also present whatever results we’ve managed to turn up by the time of Code4Lib!<br />
<br />
== PBCore in Action: Three Words, Not Two! ==<br />
<br />
* Casey E. Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH<br />
* Andrew (Drew) Myers, andrew_myers@wgbh.org, Supervising Developer, WGBH<br />
<br />
In 2001, public media representatives developed the PBCore XML schema to establish a common language for managing metadata about their analog and digital audio and video. Since then, PBCore has been adopted by a number of organizations and archivists in the moving image archival community. The schema has also undergone a few revisions, but on more than one occasion it was left orphaned and with little to no support.<br />
<br />
Times have changed. You may have heard the news that PBCore is back in action as part of the American Archive of Public Broadcasting initiative and via the Association of Moving Image Archivists (AMIA) PBCore Advisory Subcommittee. A group of archivists, public media stakeholders, and engaged users have come together to provide necessary, sustaining support for the standard and to see to its further development. <br />
<br />
At this session, we'll discuss the scope and uses of PBCore in digital preservation and access, report on the progress and goals of the PBCore Advisory Subcommittee, and share how the group (by the time of the conference) will have transformed the XML schema into an RDF ontology, bringing PBCore into the second decade of the 21st century. #PBHardcore<br />
<br />
==Collaborating to Avert the Digital Graveyard==<br />
<br />
* Harish Nayak, hnayak@library.rochester.edu, University of Rochester Libraries <br />
* Sean Morris, smorris@library.rochester.edu, University of Rochester Libraries <br />
<br />
In 1995, the Robbins Library at the University of Rochester created a digital collection of Arthurian texts, images, and bibliographies. Together with medieval scholars, we recently completed the redesign and development of an interface for this collection. Using FRBR concepts, we re-conceptualized organization and editing workflow from the ground up in a mobile-first Drupal-based project. <br />
<br />
In this talk we will describe the project as well as how we utilized the techniques of work practice study and user centered design to maintain engagement with reluctant stakeholders, nontechnical scholars, and VERY meticulous graduate students. Neither of us have previously presented at a Code4Lib conference.<br />
<br />
==Docker? VMs? EC2? Yes! With Packer.io==<br />
<br />
* Kevin S. Clarke, ksclarke@gmail.com, Digital Library Programmer, UCLA<br />
<br />
There are a lot of exciting ways to deploy a software stack nowadays. Many of our library systems are fully virtualized. Docker is a compelling alternative, and there are also cloud options like Amazon's EC2. This talk will introduce Packer.io, a tool for creating identical machine images for multiple platforms (e.g., Docker, VMWare, VirtualBox, EC2, GCE, OpenStack, et al.) all from a single source configuration. It works well with Ansible, Chef, Puppet, Salt, and plain old Bash scripts. And, it's designed to be scriptable so that builds can be automated. This presentation will show how easy it is to use Packer.io to bring up a set of related services like Fedora 4, Grinder (for stress testing), and Graphite (for charting metrics). As an added value, all the buzzwords in this proposal will be defined and explained!<br />
<br />
== Technology on your Wrist: Cross-platform Smartwatch Development for Libraries ==<br />
<br />
* [[User:sanderson|Steven Carl Anderson]], sanderson@bpl.org, [http://www.bpl.org Boston Public Library] (no previously accepted prepared talks but have done lightning talks in the past)<br />
<br />
I'll be the first to admit: smartwatches are unlikely to completely revolutionize how a library provides online services. But I believe they still represent an opportunity to further enhance existing library services and resources in a unique way.<br />
<br />
At the Boston Public Library (BPL), we're in the initial phases of designing a modest smartwatch app to provide notifications for circulation availability and checked-out-material due-date alerts by the end of current year. We're starting small, but we plan to evolve the concept over time as we see what (if any) traction such an application gets with potential users. For example, we plan to explore the possibility of adding "nearest branch to my current location" functionality to this app.<br />
<br />
Despite the "development phase" of this application as of this writing, this talk is not being given by a novice. As a technology enthusiast, I've released [http://www.phdgaming.com/smartwatch_projects/ five smartwatch applications] and have had two of those be finalists in a [http://www.phdgaming.com/samsung_challenge/ Samsung sponsored development challenge]. This experience not only will allow for the BPL to avoid many beginner mistakes in its smartwatch app development but also gives a much more complete understanding of the smartwatch development ecosystem.<br />
<br />
This talk will explore the following questions:<br />
<br />
* What kinds of online library services could potentially be transformed or translated into the smartwatch/wearable domain? What kinds of services are better left alone? These questions are currently being explored and I'll talk about our plans and experiences. Included will be any statistical information from our application launch along with statistics from my personal development.<br />
<br />
* How to support all the different operating systems these devices run without painful modifications to your codebase. (There's Tizen that is used by Samsung's Gear 2 and Gear S, Android Wear that is used by most other non-Apple manufacturers, then there is Apple's upcoming smartwatch itself, etc.)<br />
<br />
* How to support different screen resolutions on such a small device. From round to rectangular to perfectly square, smartwatches come in all different shapes these days.<br />
<br />
* What are the app stores like on these platforms? As I support multiple applications through different distribution networks, a guide to navigating how to distribute one's app is included and I'll reveal how these systems work “behind the curtain.”<br />
<br />
* What are common issues and pitfalls to avoid when doing development? Tips on broken APIs and how to cope or optimizing your code will be included.<br />
<br />
==Seeing the Forest From the Trees: The Art of Creating Workflows for Digital Projects ==<br />
<br />
* Jen LaBarbera, j.labarbera@neu.edu, NDSR Resident, Northeastern University<br />
* Joey Heinen, joseph_heinen@harvard.edu, NDSR Resident, Harvard University<br />
* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH<br />
* Tricia Patterson, triciap@mit.edu, NDSR Resident, MIT<br />
<br />
We have to "turn projects into programs" in order to create a solid and sustainable digital preservation initiative...but what the heck does that even mean? What does that look like?<br />
<br />
In this talk, members of the inaugural Boston cohort of the National Digital Stewardship Residency will discuss one piece of our digital preservation test kitchen: our stabs at creating digital workflows that will (hopefully) help our institutions turn digital preservation projects into programs. Specifically, we will talk about how difficult it is to create a general and overarching workflow for digital preservation tasks (e.g. ingest into repositories, format migrations, etc.) that incorporates various technical tools while also taking into account the myriad and unending list of possible exceptions or special scenarios. Turning these complicated, specific processes into a simplified and generalized workflow is an art. We haven't necessarily perfected that art yet, but in this talk, we'll share what has worked for us -- and what hasn't. We’ll also touch on the importance of documentation, and achieving that delicate balance of adequately thorough documentation that doesn’t pose the risk of information avalanche. These processes often create more questions than answers, but we'll share the answers that we (and our mentors) have found along the way!<br />
<br />
== Annotations as Linked Data with Fedora4 and Triannon (a Real Use Case for RDF!) ==<br />
<br />
* Rob Sanderson, azaroth@stanford.edu, Stanford University Libraries<br />
* Naomi Dushay, ndushay@stanford.edu, Stanford University Libraries<br />
<br />
Annotations on content resources allow users to contribute knowledge within the digital repository space. W3C Open Annotation provides a comprehensive model for web annotation on all types of content, using Linked Data as a fundamental framework. Annotation clients generate instances of this model, typically using a JSON serialization, but need to store that data somewhere using a standard interaction pattern so that best of breed clients, servers, and data can be mixed and matched.<br />
<br />
Stanford is using Fedora4 for managing Open Annotations, via a middleware component called Triannon. Triannon receives the JSON data from the annotation client, and uses the Linked Data Platform API implementation in Fedora4 to create, retrieve, update and delete the constituent resources. Triannon could be easily modified to use other LDP implementations, or could be modified to work with linked data other than annotations.<br />
<br />
== Hydras in the Wild: A survey of current projects ==<br />
<br />
* Mark Bussey, mark@curationexperts.com, Data Curation Experts<br />
<br />
You've seen the tutorials, but [https://github.com/projecthydra/hydra/wiki/Dive-into-Hydra Dive Into Hydra] seems to leave something wanting. What can you really do using the Hydra Framework? This talks looks at a number of current Hydra projects and highlights the design and functional features unique to each. Compare and contrast UX, design and functional capabilites from a range of hydra-based repositories including:<br />
* Avalon for media discovery and distribution (Indiana and Northwestern Univiersities) <br />
* HydraDam for media archive management(WGBH)<br />
* HyHull for general Institutional Repository needs (University of Hull)<br />
* T-DIL for slide library functions (Tufts University)<br />
* Sufia & Scholarsphere as a bundled self-deposit IR solution (Pennsylvania State University)<br />
* Curate & Worthwhile as general purpose repository platforms (Multiple Insititutions)<br />
This will be a whirlwind tour aimed at providing ideas and inspiration for your own repository development project.<br />
<br />
== Hydra Makeovers! ==<br />
<br />
* Alicia Cozine, alicia@curationexperts.com, Data Curation Experts<br />
* Patrick Feeley, pgf8@case.edu, Case Western Reserve University<br />
<br />
Compare two Hydra-based applications with the systems they replaced. Marvel at the Before and After snapshots of functionality, speed, and look & feel. <br />
* '''Digital Case 2.0''' is an institutional repository, complete with administrative tools, derivatives transcoding, flexible XML metadata storage, embargo and lease capability, faceted searching, and content viewers for texts/TEI, images, audio recordings, and videos. Digital Case 2.0 is based on worthwhile, an open-source IR starter gem. <br />
* '''The Tufts Digital Image Library''' is a specialized tool for art and art history resources, offering image collections with user access controls, image ordering, collection nesting, drag-and-drop organization, slideshows, and export capability. <br />
Both new systems are built on hydra, the open-source Ruby-on-Rails repository solution that incorporates Fedora for storage, Solr for indexing, and Blacklight for search optimization. Their beauty is not just skin-deep!<br />
<br />
<br />
<br />
== Helping Google (and scholars, researchers, educators, & the public) find archival audio ==<br />
<br />
* Anne Wootton, anne@popuparchive.org, Pop Up Archive (www.popuparchive.org)<br />
<br />
Culturally significant digital audio collections are hard to discover on the web. There are major barriers keeping this valuable media from scholars, researchers, and the general public:<br />
<br />
Audio is opaque: you can’t picture sound, or skim the words in a recording. <br />
Audio is hard to share: there’s no text to interact with. <br />
Audio is not text: but since text is the medium of the web, there’s no path for audiences to find content-rich audio.<br />
Audio metadata is inconsistent and incomplete.<br />
<br />
At Pop Up Archive, we're helping solve this problem making the spoken word searchable. We began as a UC-Berkeley School of Information Master's thesis to provide better access to recorded sound for audio producers, journalists, and historians. Today, Pop Up Archive processes thousands of hours of sound from all over the web to create automatic, timestamped transcripts and keywords, working with media companies and institutions like NPR, KQED, HuffPost Live, Princeton, and Stanford. We're building collections of sound from journalists, media organizations, and oral history archives from around the world. Pop Up Archive is supported by the John S. and James L. Knight Foundation, the National Endowment for the Humanities, and 500 Startups.<br />
<br />
== Digital Content Integrated with ILS Data for User Discovery: Lessons Learned ==<br />
<br />
* Naomi Dushay, ndushay@stanford.edu, Stanford University Libraries<br />
* Laney McGlohon, laneymcg@stanford.edu, Stanford University Libraries (first-time presenter)<br />
<br />
So you want to expose your digital content in your discovery interface, integrated with the data from your ILS? How do you make the best information user searchable? How do you present complete, up to date search results with a minimum of duplicate entries?<br />
<br />
At Stanford, we have these cases and more:<br />
* digital content with no metadata in ILS<br />
* digital content for metadata in ILS<br />
* digital content with its own metadata derived from ILS metadata.<br />
<br />
We will describe our efforts to accommodate multiple updatable metadata sources for materials in the ILS and our Digital Object Repository while presenting users with reduced duplication in SearchWorks. Included will be some failures, some successes, and an honest assessment of where we are now.<br />
<br />
== Show All the Things: Kanban for Libraries == <br />
<br />
* Mike Hagedon, mhagedon@email.arizona.edu, University of Arizona Libraries (first-time presenter)<br />
<br />
The web developers at the University of Arizona Libraries had a problem: we were working on a major website rebuild project with no clear way to prioritize it against our other work. We knew we wanted to follow Agile principles and initially chose Scrum to organize and communicate about our work. But we found that certain core pieces of Scrum did not work for our team. Then we discovered Kanban, an Agile meta-process for organizing work (team or individual) that treats the work more as a flow than as a series of fixed time boxes. I’ll be talking about our journey toward finding a process that works for our team and how we’ve applied the principles of Kanban to better get our work done. Specifically, I'll discuss principles like how to visualize all your work, how to limit how much you’re doing (to get more done!), and how to optimize the flow of your work.<br />
<br />
== DIY Catalog ==<br />
<br />
* Wayne Schneider, wschneider at [//www.hclib.org hclib.org], [//www.hclib.org Hennepin County Library]<br />
* Amy Drayer, adrayer at [//www.hclib.org hclib.org], [//www.hclib.org Hennepin County Library]<br />
<br />
With so many discovery layers being made available that didn’t quite fit user needs but still came with substantial costs, Hennepin County Library determined it would develop one that could handle its customizations. So they built their own ILS API, Web services, and an interface that provides all the features (and existing custom features) of the old catalog, with new features planned, all within a responsive layout. Get a look at the system architecture, how the front end communicates through the layers back to the databases, and how to manage the infrastructure.<br />
<br />
== OverDrive: Full Integration ==<br />
<br />
* Amy Drayer, adrayer at [//www.hclib.org hclib.org], [//www.hclib.org Hennepin County Library]<br />
* Wayne Schneider, wschneider at [//www.hclib.org hclib.org], [//www.hclib.org Hennepin County Library]<br />
<br />
How do you increase usage of your ebooks? Seamless integration in the catalog certainly helps. Users can search for digital titles, limit to just those that are available, place a request, borrow, and manage all their digital titles from the library website alongside all the other physical titles the library has. Get a quick demo and learn how this was all made possible.<br />
<br />
The [//www.hclib.org Hennepin County Library] is ranked one of [//www.thedigitalshift.com/2014/10/ebooks/overdrive-api-usage-indicates-growth-ebook-checkouts-via-opac/ the top users of OverDrive and OverDrive’s API] and is looking to more fully integrate 3M Cloud, OneClickDigital, and other digital resources.<br />
<br />
== Dynamic Indexing: a Tragic Solr Story ==<br />
<br />
* Wayne Schneider, wschneider at [//www.hclib.org hclib.org], [//www.hclib.org Hennepin County Library]<br />
<br />
Loading data from an ILS into Solr isn’t so hard, unless it needs to be dynamic, fast, and hold more data than what can be found in 1.5 million MARC records. Some additional information we’ve incorporated are from Syndetics, ILS circulation, and OverDrive. We’ll share the nitty gritty details and what we learned about dynamic Solr indexing, including how to get good performance, how to deal with indexing failures, how to schedule it all to keep the data up-to-date, and some things you can do with that data such as popularity ratings.<br />
<br />
== Fedora 4, Survey of Core Capabilities and External Modules: == <br />
* Andrew Woods, awoods@duraspace.org, DuraSpace<br />
<br />
Now that the production release of Fedora 4.0 is out, the time is right to take a step back and review the core capabilities offered by Fedora:<br />
* Basic CRUD<br />
* Versioning<br />
*- Transactions<br />
* etc<br />
<br />
...and take a closer look at the supported external modules:<br />
* Authorization<br />
* Solr integration<br />
* Triplestore integration<br />
* Camel integration<br />
* etc<br />
<br />
In addition to clarifying specific implementation details, this is an opportunity to surface community requirements which may have not been addressed in the initial release.<br />
<br />
== Bleeding edge beacons: redesign of a library tour with new technology ==<br />
<br />
* Neal Henshaw, Virginia Tech <br />
* Somiah Lattimore, Straight Up Creative<br />
* Keith Gilbertson, keith.gilbertson@vt.edu, Virginia Tech<br />
<br />
This group has not yet presented at Code4Lib<br />
<br />
A technology liaison, a designer, and a developer are working together to update a mobile audio tour of an academic library.<br />
<br />
The walking tour was originally conceived of and created by the technology liaison to provide an orientation experience for incoming students. In its current version, patrons visit several stations in the library and activate an audio description of each station by scanning a QR barcode with a mobile device.<br />
<br />
We are building a prototype to test with focus groups so that we can launch a new version of the tour in early 2015. The tour has been reimagined with a professional and communicative user interface that presents students with learning goals for each location in the library. The new version of the tour is a mobile application with integrated support for micro-location technology provided through Bluetooth low energy beacon devices, known informally as iBeacons, installed throughout the building. As a touring student walks through the library, her location is noted by the app so that an appropriate video segment is automatically played according to the current location.<br />
<br />
We will discuss perspectives on the design of the project, including<br />
<br />
* Designing with technology to achieve learning goals<br />
* Designing graphical elements, interaction, and user experience<br />
* Designing to maintain compatibility with older technologies<br />
<br />
We’ll explain our efforts to make the application usable by those with hearing impairments and mobility impairments, reactions from our first users, and challenges in working with the relatively new beacon technology.<br />
<br />
== Distributed Remediation: Small tools for big problems: ==<br />
<br />
* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs<br />
<br />
Remediation of legacy data can be automated only so much. Certain essential cleanup tasks, such as aligning a name with the correct authorized version, is very difficult for a computer yet trivial for a person. While it is these types remediations that will allow an institution to take advantage and participate in the web of Linked Open Data, a wholly manual approach is unrealistic. However, by augmenting automated remediation with a light human touch we can quickly and efficiently reach our goals. This talk will look at tools and methods being developed at NYPL Labs to empower library staff and the public to help clean up our legacy metadata through collaborative remediation.<br />
<br />
==VuFind + WorldCat: Open Source Discovery Meets Big Library Data==<br />
<br />
* Karen A. Coombs, coombsk@oclc.org, OCLC<br />
* Demian Katz, demian.katz@villanova.edu, Villanova University<br />
<br />
Good collaboration is crucial to any integration. Our project, to integrate the open source discovery tool, VuFind, with results from the new WorldCat Discovery API, is no different. We want to exploit the flexibility of VuFind and add the depth and breadth of WorldCat and central index content. Plus, the project has the potential to eliminate the hurdle of exporting and indexing MARC records for 32 VuFind libraries.<br />
<br />
While we are really excited about the UI enhancements, we are also curious to see how we can share our domain expertise between our two organizations to get the project done quickly. How will different perspectives shape our existing code bases? How will we adjust to working on the same code base simultaneously? And how can we best incorporate what we learn along the way?<br />
<br />
There is also new territory to explore using the API: integrating bibliographic and article data into a single results set. And the overarching question: will we be able to take advantage of Linked Data in the WorldCat Discovery API to create some “glue” between records in existing VuFind indexes and third-party data providers?<br />
<br />
This presentation will discuss our adventures in the OCLC WorldShare Platform/VuFind collaboration: the opportunities, challenges and results. You’ll learn what worked, what didn’t and how you can improve your own discovery interface integration project—no matter what provider or APIs you use.<br />
<br />
== Book Reader Bingo: Which Page-Turner Should I Use? ==<br />
<br />
* Eben English, eenglish [at] bpl.org, Boston Public Library<br />
<br />
Another day, another library reinventing the book-viewer wheel. When will the madness end? This talk will explore the current landscape of book-viewer/page-turner applications for digital library systems with an eye towards helping you make the right decision for your project. We'll look at some the major players on the market (such as Internet Archive BookReader, Wellcome Player, Mirador, and WDL-Viewer to name a few) and compare them based on a number of criteria: feature sets, mobile/tablet friendliness, ease of integration, code health, test coverage, "market share" (number of implementers), and other important factors. We'll look at the results of ACTUAL USABILITY TESTS to see what features users REALLY want in a book-viewer, and how each app measures up. <br />
<br />
We'll also discuss important recent trends (such as the IIIF Presentation API, ReadersFirst, and NYPL's Library Simplified initiative) that have the potential to shape the book-viewer development landscape in the immediate future. Which page-turner applications are best poised to adopt/integrate/leverage these emerging standards? Which will become obsolete? This talk has the answers you need.<br />
<br />
== Rich Citations ==<br />
<br />
* Adam Becker, abecker@plos.org, Public Library of Science<br />
* Erik Hetzner, ehetzner@plos.org, Public Library of Science<br />
<br />
Citations should connect you to the research you need. They should<br />
link directly to the relevant papers and data. They should tell you<br />
everything you need to know about how and where two pieces of research<br />
are connected. They should be easy to use and they should never get in<br />
the way of the reading experience. In short, citations should not<br />
clumsily point to a mere chunk of plain undifferentiated text sitting<br />
in a static list at the end of the paper. But with almost no<br />
exceptions, citations in scientific papers do just that.<br />
<br />
PLOS Labs has been working on a project to capture extra information<br />
about citations. To this end, we have designed a metadata structure<br />
describing the context of a paper's citations, called rich citations.<br />
This structured information includes complete bibliographic<br />
information for the cited items, location and context of the in-text<br />
citation, co-citations, reference license and status (updated,<br />
retracted, etc.), and more.<br />
<br />
We have processed the complete PLOS corpus to extract this rich<br />
citation metadata, and made this data available in an API located at<br />
http://api.richcitations.org/.<br />
<br />
We have also developed a JavaScript overlay to enhance a paper's view<br />
using rich citations (http://alpha.richcitations.org). This overlay<br />
uses the underlying rich citation metadata to allow the user to view<br />
information about an in-text citation, quickly navigate between<br />
citations, and sort and filter the paper's reference list.<br />
<br />
In this talk, we will describe the rich citation metadata that we are<br />
capturing. We will demonstrate how this metadata can enhance a<br />
reader's experience of an article and how it can be used by<br />
researchers to better understand how citations are used in the<br />
scientific community. We will also discuss our ongoing plans to extend<br />
this project to the wider literature beyond PLOS, and how interested<br />
members of the community can help.<br />
<br />
== Scriptaloging with ArchivesSpace and NodeJS ==<br />
<br />
* Brian Hoffman, brianjhoffman@gmail.com<br />
<br />
ArchivesSpace is a new web application for managing archival collections. It has a browser-based interface for entering and editing metadata, and can import data serialized as EAD, MARC, and several other formats. But there may be situations where neither of these are quite what you want. For instance, you may have a large folder of images that each need a digital object record; or you may want to export an EAD for every collection in your repository; or calculate the total extent of your collection; or execute a global search and replace; or batch-update barcodes, etc. You could write a plugin using ArchivesSpace’s plugin API, but that requires facility with Ruby as well as access to the environment where the application is running. A more lightweight approach is to access your data through ArchivesSpace’s powerful REST API, and process it using whatever scripting language you prefer. This talk will present some simple “scriptaloging” solutions that a moderately skilled programmer can use to automate data entry or import tasks using an extendable command line tool written in NodeJS (https://www.npmjs.org/package/as-cli) and loosely inspired by Drupal’s drush utilitly.<br />
<br />
== Consuming Big Linked Open Data in Practice: Authority Shifts and Identifier Drift ==<br />
<br />
* Kathryn Stine, katstine@berkeley.edu, UC Berkeley<br />
* Stephanie Collett, stephanie.collett@ucop.edu, California Digital Library, UC<br />
<br />
Increasingly, authoritative datasets of interest to libraries (subjects, names, classifications, etc.) are are available in bulk, exposed as linked open data. Unfettered access can allow libraries to aggregate, connect, and augment data in new ways that will benefit users. This talk will describe our exploratory experience integrating bulk data from the Virtual International Authority File (VIAF) into HathiTrust metadata to improve discovery and collection management.<br />
<br />
Authoritative data is not static - datasets change with new contributions and re-clustering, resulting in new identifier relationships. We will describe the challenges this presents with accessing, processing, and syncing our metadata with a massive, complex linked dataset. We will talk about our technical approach to navigating an ecosystem of identifiers and mitigating cached identifier drift between systems as authority data shifts. We aim to spark conversation about data accessibility and the relationships between local, consortial, and authoritative metadata as the library community moves beyond “Hello, world” linked data examples to integrating this data at scale into existing systems.<br />
<br />
== Your Chocolate is in My Peanut Butter! Mixing up Content and Presentation Layers to Build Smarter Books in Browsers with RDFa, Schema.org, and Linked Data Topics ==<br />
<br />
* Jason A. Clark <br />
* Head, Library Informatics & Computing, Montana State University<br />
* @jaclark jaclark@montana.edu<br />
<br />
*Scott W. H. Young <br />
*Digital Initiatives Librarian, Montana State University<br />
* @hei_scott<br />
<br />
Common methods of publishing book content have focused on various implementations of existing technologies such as LaTeX, Markdown, and .epub. A common theme within this development has been the separation of presentation layers and content layers. What if there was another way? In responding to that question, we’ll look at our local @msulibrary prototype software funded by an IMLS Sparks! Innovation grant for presenting books inside of web browsers (https://github.com/jasonclark/bib-template). Our talk will focus on the tools and technologies of open web publishing. We’ll consider the strange and wonderful benefits of integrating the presentation layer and content layer using semantic RDFa HTML5 markup, and we’ll demonstrate how describing and displaying books within an open web model impacts discovery, eBook production, and machine-readability.<br />
<br />
Our session will include:<br />
* The benefits of using RDFa, Schema.org, and linked data models for book production<br />
* How structured data models for book content can turn your webpage into your API<br />
* Analyze the effects of this practice for machine-understanding, SEO, and UX<br />
* Discuss the advantages and disadvantages of this model as it applies to a range of book genres, including web book prototypes for textbooks, fiction, and poetry.<br />
<br />
== Integration/Collaboration: Playing Well With Others ==<br />
<br />
* Sarah Romkey, sromkey@artefactual.com, Artefactual Systems<br />
* Justin Simpson, jsimpson@artefactual.com, Artefactual Systems<br />
<br />
There are many different software applications and systems being used in collecting institutions to handle all aspects of managing their digital collections. Within a single institution, it is possible to have several tools with overlapping functionality. Sometimes the biggest gains in functionality and productivity come from a focus on connecting these systems together. <br />
<br />
In this talk we will present several examples of integration and collaboration that we have been involved in while working on the Archivematica project. Examples of integrations with both open source and proprietary systems, as well as examples of collaborative development processes.<br />
<br />
== BYOB: Build Your Own Bootstrap ==<br />
<br />
* Axa Mei Liauw, aliauw@princeton.edu, Princeton University Library<br />
* Kevin Reiss, kr2@princeton.edu, Princeton University Library<br />
<br />
Bootstrap is awesome! It allows for quick and easy front-end development without demanding too much time with the design of the user interface. A framework like Bootstrap can also help libraries address one of our top usability problems: wild inconsistency of styles and layouts across our own in-house applications and websites. It is just so easy!<br />
<br />
However, what if you do not want to compromise your creativity and make your project visually stand out? With enough Sass or Less knowledge it is possible to highly customize Bootstrap to fit your needs, but in the end you still end up with your design and code buying into Bootstrap's markup and design conventions, which are not always what you want. Sometimes you simply want to start with a clean slate and not fight the framework and use only the components and features you need.<br />
<br />
In that case, build your own Bootstrap! In this talk we will discuss techniques for using some of the emerging tools from the front-end development and design communities to create a maintainable, modular in-house Sass toolkit that we are implementing within a variety of tools including Drupal, Rails applications, in house PHP applications, as well as within vendor solutions like Libguides and ILLiad. Some specific tools we will discuss are Grunt, Bower, and Sass tools like Singularity, Breakpoint, and Bourbon.</div>Kevinreisshttps://wiki.code4lib.org/index.php?title=2014_preconference_proposals&diff=400612014 preconference proposals2013-12-04T15:38:56Z<p>Kevinreiss: /* Blacklight Hackfest */</p>
<hr />
<div>==Code4Lib 2014 Pre-Conference Proposals==<br />
<br />
Proposals will be accepted through December 6th, 2013.<br />
<br />
===Note===<br />
Attendance at a pre-conference will require a small fee ''due at the time of conference registration.<br />
<br />
Although this was specified in the email announcements relating to pre-conferences, it was not added to this page until December 2nd. I (Adam C.) apologize for the omission and I hope this will not cause any "sticker shock." Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.<br />
<br />
Please put your pre-conference on the list in the following format:<br />
<br />
===NAME===<br />
'''"Full-Day|Half-Day" [PREFERRED TIME]'''<br />
<br />
Description<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
----<br />
<br />
<br />
<br />
===Drupal4lib Sub-con Barcamp===<br />
=====Full Day=====<br />
<br />
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com<br />
<br />
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.<br />
<br />
This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).<br />
<br />
[[resources to help you learn drupal]]<br />
<br />
====Interested in Attending:====<br />
<br />
=====All Day=====<br />
Renna Tuten <br />
<br />
=====Morning=====<br />
<br />
Kevin Reiss<br />
<br />
=====Afternoon=====<br />
<br />
===Open Refine Hackfest===<br />
'''"Half-Day"'''<br />
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com<br />
<br />
[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control<br />
<br />
The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. <br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
----<br />
<br />
===Responsive Design Hackfest===<br />
'''"Half-Day [Afternoon]"''' <br />
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com<br />
* Contact David Ward, University of Illinois, dh-ward@illinois.edu<br />
<br />
This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. <br />
<br />
Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
=== Intro to Blacklight ===<br />
'''"Half-Day [Morning]"''' <br />
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu<br />
* TA: Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
This session will be walk-through of the architecture of Blacklight, the community, and an introduction to building a Blacklight-based application. Each participant will have the opportunity to build a simple Blacklight application, and make basic customizations, while using a test-driven approach.<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#Megan Kudzia<br />
#Bret Davidson<br />
#Coral Sheldon-Hess<br />
<br />
===Blacklight Hackfest===<br />
'''"Half-Day [Afternoon]"''' <br />
* Contact Chris Beer, Stanford University, cabeer@stanford.edu<br />
<br />
This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
1. Shaun Ellis<br />
2. Kevin Reiss<br />
<br />
===RailsBridge: Intro to programming in Ruby on Rails===<br />
'''"Half-Day" [morning]'''<br />
* Contact Justin Coyne, Data Curation Experts, justin@curationexperts.com<br />
<br />
Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! RailsBridge is a friendly place to get together and learn how to write some code.<br />
<br />
RailsBridge is a great workshop that opens the doors to projects like Blacklight and Hydra.<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
1. Ayla Stein<br />
<br />
2. Heidi Dowding<br />
<br />
===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===<br />
'''Full-Day'''<br />
<br />
Contact: <br />
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com<br />
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu<br />
<br />
This will be a full day session on project management. We'll cover<br />
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment<br />
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets<br />
* '''Executing the Project''' -- status meeting, status reports, issue management<br />
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product<br />
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
===Fail4Lib 2014===<br />
'''Half Day [TBD, probably afternoon]'''<br />
<br />
Contacts: <br />
* Andreas Orphanides, akorphan (at) ncsu.edu<br />
* Jason Casden, jmcasden (at) ncsu.edu<br />
<br />
The task of design (and the work that we do as library coders) is intimately tied to failure. Failures, both big and small, motivate us to create and improve. Failures are also occasionally the result of our work. Understanding and embracing failure, encouraging enlightened risk-taking, and seeking out opportunities to fail and learn are essential to success in our field. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be feared.<br />
<br />
The schedule may include the following:<br />
<br />
* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?<br />
* Confessionals, for those willing to share. Talk about your own experiences with rough starts, labor pains, and doomed projects in your own work: What can we learn from our own (and each others') failures?<br />
* Group therapy. Let's talk about how to deal with risk management, failed projects, experimental endeavors, and more: How can we make ourselves, our colleagues, and our organizations more fault tolerant? How do we make sure we fail as productively as possible?<br />
<br />
''Interested in attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#Bret Davidson<br />
<br />
<br />
===CLLAM @ code4lib===<br />
'''(Computational Linguistics for Libraries, Archives and Museums)'''<br />
<br />
'''Full Day'''<br />
<br />
Contacts: <br />
* Douglas W. Oard (primary), oard (at) umd.edu <br />
* Corey Harper, corey (dot) harper (at) nyu.edu<br />
* Robert Sanderson, azaroth42 (at) gmail.com <br />
* Robert Warren, rwarren (at) math.carleton.ca<br />
<br />
We will hack at the intersection of diverse content from Libraries, Archives and Museums and bleeding edge tools from computational linguistics for slicing and dicing that content. Did you just acquire the email archives of a startup company? Maybe you can automatically build an org chart. Have you got metadata in a slew of languages? Perhaps you can search it all using one query. Is name authority control for e-resources getting too costly? Let’s see if entity linking techniques can help. These are just a few teasers. <br />
<br />
There’ll be plenty of content and tools supplied, but please bring your own [data] too -- you’ll hack with it in new ways throughout the day. We’ll get started with some lightning talks on what we’ve brought,then we’ll break up into groups to experiment and work on the ideas that appeal. Three guaranteed outcomes: you’ll walk away with new ideas, new tools, and new people you’ll have met.<br />
<br />
''Interested in attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Devon Smith<br />
# Kevin S. Clarke<br />
<br />
=== GeoHydra: Managing geospatial content ===<br />
<br />
'''Half-day [Afternoon]'''<br />
<br />
* Contact: Darren Hardy, Stanford University, drh@stanford.edu<br />
* Moderator: Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,<br />
etc., all of which you want to integrate into your digital repository? In this<br />
workshop, we will discuss how Hydra can provide discovery, delivery, and<br />
management services for geospatial assets, as well as solicit questions about<br />
your own GIS projects. We aim to help answer the following questions you might have about putting geospatial data into your Hydra-based digital library:<br />
<br />
* What are the types of geospatial data?<br />
* How to dive into Hydra?<br />
* How to model geospatial holdings with Hydra?<br />
* How to discover and view geospatial data?<br />
* How to build a geospatial data infrastructure?<br />
* What are common approaches and problems?<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
===Technology, Librarianship, and Gender: Moving the conversation forward===<br />
'''Full Day'''<br />
<br />
Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]<br />
<br />
'''Description'''<br />
<br />
Librarianship is largely made up of women, yet women are significantly underrepresented in tech positions, on any level, within libraries themselves. Why? What are we doing to encourage women to become more involved in STEM within librarianship? What kind of message are we sending when library technology keynotes remain almost resolutely male? How are we changing the face of technology, not only within libraries, but with the field itself? How are we training our staff and colleagues in the areas of fairness and removal of bias? Our vendors?<br />
<br />
Lots of tough questions.<br />
<br />
While the conversation has been going on via various blogs and articles within the last few years, it was given a public face at [http://infotoday.com/il2013/day.asp?day=Monday#session_D105 Internet Librarian 2013] where a panel of 7 (four women, three men) gave personal experiences on the above and then opened up the conversation to the audience. As eye opening and enriching the conversation was, a 45 minute panel was not enough. One thing remains clear: We need to keep the conversation moving forward and start making some radical changes in the way we think, act, and how we need to harness this to start making real changes within librarianship itself.<br />
<br />
Topics to include: Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems, mentoring, ally support, and more<br />
<br />
Those attending should expect: Begin with opening up the conversation of experiences and talking about what is most needed, spending remaining time putting together live, usable solutions to start implementing as well as pushing the conversation forward at local levels<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
=====All Day=====<br />
1. Kate Kosturski<br />
<br />
2. Valerie Aurora<br />
<br />
3. Declan Fleming<br />
<br />
=====Morning=====<br />
1. Shaun Ellis<br />
<br />
=====Afternoon=====<br />
1. Ayla Stein<br />
<br />
2. Heidi Dowding<br />
<br />
3. Coral Sheldon-Hess<br />
----<br />
<br />
===FileAnalyzer: Rapid Development of File Manipulation Tasks===<br />
'''"Half-Day" [morning]'''<br />
* Contact Terry Brady, twb27@georgetown.edu<br />
<br />
The FileAnalyzer (https://github.com/Georgetown-University-Libraries/File-Analyzer) is an application designed to solve a number of library automation challenges:<br />
<br />
* validating digitized and reformatted files<br />
* validating vendor statistics for counter compliance<br />
* preparing collections of digital files for archiving and ingest<br />
* manipulating ILS import and export files<br />
<br />
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.<br />
<br />
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.<br />
<br />
The first half of this session will be targeted to potential users and developers. The second half of the session will be targeted towards developers who are interested in developing custom rules for the application.<br />
<br />
''Session Overview''<br />
* Overview of the application<br />
* Running sample file tests/transformations through the application<br />
* Compiling and building the application<br />
* Coding a custom file processing task<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
----<br />
<br />
<br />
===Collecting social media data with Social Feed Manager===<br />
'''Half-Day [Morning]'''<br />
<br />
Contacts: <br />
* Dan Chudnov, GW Libraries, dchud (at) gwu.edu<br />
* Dan Kerchner, GW Libraries, kerchner (at) gwu.edu<br />
* Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu<br />
<br />
Social media data is a popular material for research and a new format for building collections. What does it take to collect meaningfully from Twitter, Tumblr, YouTube, Weibo, Facebook, and other sites? We will:<br />
* Introduce options for collections, including both high- and low-end commercial offerings. Discuss what it means to collect these resources, covering boundaries, policies, and workflows required to develop a social media collection program in your institution.<br />
* Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them<br />
* Help you get started using the free [http://gwu-libraries.github.io/social-feed-manager Social Feed Manager] (SFM) app we're developing at GW to create your first collections. We’ll demo its use and demo a clean install (those w/environments can follow along)<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
Declan Fleming<br />
<br />
----<br />
<br />
<br />
=== Intro to Git ===<br />
'''"Half-Day [tbd - probably afternoon]"''' <br />
* Contact: Erin Fahy, Stanford University, efahy at stanford.edu<br />
* TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu<br />
<br />
This session will cover the fundamentals of git by discussing/going through (time allowing):<br />
* what is a distributed version control system<br />
* what is git and github<br />
* initializing a repo on a remote server/github<br />
* cloning an existing repo<br />
* creating a branch<br />
* contributing code to a repo<br />
* how to handle merge conflicts<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
----<br />
<br />
[[:Category:Code4Lib2014]]</div>Kevinreisshttps://wiki.code4lib.org/index.php?title=2014_preconference_proposals&diff=400602014 preconference proposals2013-12-04T15:37:38Z<p>Kevinreiss: /* Morning */</p>
<hr />
<div>==Code4Lib 2014 Pre-Conference Proposals==<br />
<br />
Proposals will be accepted through December 6th, 2013.<br />
<br />
===Note===<br />
Attendance at a pre-conference will require a small fee ''due at the time of conference registration.<br />
<br />
Although this was specified in the email announcements relating to pre-conferences, it was not added to this page until December 2nd. I (Adam C.) apologize for the omission and I hope this will not cause any "sticker shock." Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.<br />
<br />
Please put your pre-conference on the list in the following format:<br />
<br />
===NAME===<br />
'''"Full-Day|Half-Day" [PREFERRED TIME]'''<br />
<br />
Description<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
----<br />
<br />
<br />
<br />
===Drupal4lib Sub-con Barcamp===<br />
=====Full Day=====<br />
<br />
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com<br />
<br />
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.<br />
<br />
This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).<br />
<br />
[[resources to help you learn drupal]]<br />
<br />
====Interested in Attending:====<br />
<br />
=====All Day=====<br />
Renna Tuten <br />
<br />
=====Morning=====<br />
<br />
Kevin Reiss<br />
<br />
=====Afternoon=====<br />
<br />
===Open Refine Hackfest===<br />
'''"Half-Day"'''<br />
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com<br />
<br />
[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control<br />
<br />
The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. <br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
----<br />
<br />
===Responsive Design Hackfest===<br />
'''"Half-Day [Afternoon]"''' <br />
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com<br />
* Contact David Ward, University of Illinois, dh-ward@illinois.edu<br />
<br />
This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. <br />
<br />
Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
=== Intro to Blacklight ===<br />
'''"Half-Day [Morning]"''' <br />
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu<br />
* TA: Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
This session will be walk-through of the architecture of Blacklight, the community, and an introduction to building a Blacklight-based application. Each participant will have the opportunity to build a simple Blacklight application, and make basic customizations, while using a test-driven approach.<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#Megan Kudzia<br />
#Bret Davidson<br />
#Coral Sheldon-Hess<br />
<br />
===Blacklight Hackfest===<br />
'''"Half-Day [Afternoon]"''' <br />
* Contact Chris Beer, Stanford University, cabeer@stanford.edu<br />
<br />
This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
1. Shaun Ellis<br />
<br />
===RailsBridge: Intro to programming in Ruby on Rails===<br />
'''"Half-Day" [morning]'''<br />
* Contact Justin Coyne, Data Curation Experts, justin@curationexperts.com<br />
<br />
Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! RailsBridge is a friendly place to get together and learn how to write some code.<br />
<br />
RailsBridge is a great workshop that opens the doors to projects like Blacklight and Hydra.<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
1. Ayla Stein<br />
<br />
2. Heidi Dowding<br />
<br />
===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===<br />
'''Full-Day'''<br />
<br />
Contact: <br />
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com<br />
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu<br />
<br />
This will be a full day session on project management. We'll cover<br />
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment<br />
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets<br />
* '''Executing the Project''' -- status meeting, status reports, issue management<br />
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product<br />
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
===Fail4Lib 2014===<br />
'''Half Day [TBD, probably afternoon]'''<br />
<br />
Contacts: <br />
* Andreas Orphanides, akorphan (at) ncsu.edu<br />
* Jason Casden, jmcasden (at) ncsu.edu<br />
<br />
The task of design (and the work that we do as library coders) is intimately tied to failure. Failures, both big and small, motivate us to create and improve. Failures are also occasionally the result of our work. Understanding and embracing failure, encouraging enlightened risk-taking, and seeking out opportunities to fail and learn are essential to success in our field. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be feared.<br />
<br />
The schedule may include the following:<br />
<br />
* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?<br />
* Confessionals, for those willing to share. Talk about your own experiences with rough starts, labor pains, and doomed projects in your own work: What can we learn from our own (and each others') failures?<br />
* Group therapy. Let's talk about how to deal with risk management, failed projects, experimental endeavors, and more: How can we make ourselves, our colleagues, and our organizations more fault tolerant? How do we make sure we fail as productively as possible?<br />
<br />
''Interested in attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#Bret Davidson<br />
<br />
<br />
===CLLAM @ code4lib===<br />
'''(Computational Linguistics for Libraries, Archives and Museums)'''<br />
<br />
'''Full Day'''<br />
<br />
Contacts: <br />
* Douglas W. Oard (primary), oard (at) umd.edu <br />
* Corey Harper, corey (dot) harper (at) nyu.edu<br />
* Robert Sanderson, azaroth42 (at) gmail.com <br />
* Robert Warren, rwarren (at) math.carleton.ca<br />
<br />
We will hack at the intersection of diverse content from Libraries, Archives and Museums and bleeding edge tools from computational linguistics for slicing and dicing that content. Did you just acquire the email archives of a startup company? Maybe you can automatically build an org chart. Have you got metadata in a slew of languages? Perhaps you can search it all using one query. Is name authority control for e-resources getting too costly? Let’s see if entity linking techniques can help. These are just a few teasers. <br />
<br />
There’ll be plenty of content and tools supplied, but please bring your own [data] too -- you’ll hack with it in new ways throughout the day. We’ll get started with some lightning talks on what we’ve brought,then we’ll break up into groups to experiment and work on the ideas that appeal. Three guaranteed outcomes: you’ll walk away with new ideas, new tools, and new people you’ll have met.<br />
<br />
''Interested in attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Devon Smith<br />
# Kevin S. Clarke<br />
<br />
=== GeoHydra: Managing geospatial content ===<br />
<br />
'''Half-day [Afternoon]'''<br />
<br />
* Contact: Darren Hardy, Stanford University, drh@stanford.edu<br />
* Moderator: Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,<br />
etc., all of which you want to integrate into your digital repository? In this<br />
workshop, we will discuss how Hydra can provide discovery, delivery, and<br />
management services for geospatial assets, as well as solicit questions about<br />
your own GIS projects. We aim to help answer the following questions you might have about putting geospatial data into your Hydra-based digital library:<br />
<br />
* What are the types of geospatial data?<br />
* How to dive into Hydra?<br />
* How to model geospatial holdings with Hydra?<br />
* How to discover and view geospatial data?<br />
* How to build a geospatial data infrastructure?<br />
* What are common approaches and problems?<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
===Technology, Librarianship, and Gender: Moving the conversation forward===<br />
'''Full Day'''<br />
<br />
Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]<br />
<br />
'''Description'''<br />
<br />
Librarianship is largely made up of women, yet women are significantly underrepresented in tech positions, on any level, within libraries themselves. Why? What are we doing to encourage women to become more involved in STEM within librarianship? What kind of message are we sending when library technology keynotes remain almost resolutely male? How are we changing the face of technology, not only within libraries, but with the field itself? How are we training our staff and colleagues in the areas of fairness and removal of bias? Our vendors?<br />
<br />
Lots of tough questions.<br />
<br />
While the conversation has been going on via various blogs and articles within the last few years, it was given a public face at [http://infotoday.com/il2013/day.asp?day=Monday#session_D105 Internet Librarian 2013] where a panel of 7 (four women, three men) gave personal experiences on the above and then opened up the conversation to the audience. As eye opening and enriching the conversation was, a 45 minute panel was not enough. One thing remains clear: We need to keep the conversation moving forward and start making some radical changes in the way we think, act, and how we need to harness this to start making real changes within librarianship itself.<br />
<br />
Topics to include: Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems, mentoring, ally support, and more<br />
<br />
Those attending should expect: Begin with opening up the conversation of experiences and talking about what is most needed, spending remaining time putting together live, usable solutions to start implementing as well as pushing the conversation forward at local levels<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
=====All Day=====<br />
1. Kate Kosturski<br />
<br />
2. Valerie Aurora<br />
<br />
3. Declan Fleming<br />
<br />
=====Morning=====<br />
1. Shaun Ellis<br />
<br />
=====Afternoon=====<br />
1. Ayla Stein<br />
<br />
2. Heidi Dowding<br />
<br />
3. Coral Sheldon-Hess<br />
----<br />
<br />
===FileAnalyzer: Rapid Development of File Manipulation Tasks===<br />
'''"Half-Day" [morning]'''<br />
* Contact Terry Brady, twb27@georgetown.edu<br />
<br />
The FileAnalyzer (https://github.com/Georgetown-University-Libraries/File-Analyzer) is an application designed to solve a number of library automation challenges:<br />
<br />
* validating digitized and reformatted files<br />
* validating vendor statistics for counter compliance<br />
* preparing collections of digital files for archiving and ingest<br />
* manipulating ILS import and export files<br />
<br />
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.<br />
<br />
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.<br />
<br />
The first half of this session will be targeted to potential users and developers. The second half of the session will be targeted towards developers who are interested in developing custom rules for the application.<br />
<br />
''Session Overview''<br />
* Overview of the application<br />
* Running sample file tests/transformations through the application<br />
* Compiling and building the application<br />
* Coding a custom file processing task<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
----<br />
<br />
<br />
===Collecting social media data with Social Feed Manager===<br />
'''Half-Day [Morning]'''<br />
<br />
Contacts: <br />
* Dan Chudnov, GW Libraries, dchud (at) gwu.edu<br />
* Dan Kerchner, GW Libraries, kerchner (at) gwu.edu<br />
* Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu<br />
<br />
Social media data is a popular material for research and a new format for building collections. What does it take to collect meaningfully from Twitter, Tumblr, YouTube, Weibo, Facebook, and other sites? We will:<br />
* Introduce options for collections, including both high- and low-end commercial offerings. Discuss what it means to collect these resources, covering boundaries, policies, and workflows required to develop a social media collection program in your institution.<br />
* Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them<br />
* Help you get started using the free [http://gwu-libraries.github.io/social-feed-manager Social Feed Manager] (SFM) app we're developing at GW to create your first collections. We’ll demo its use and demo a clean install (those w/environments can follow along)<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
Declan Fleming<br />
<br />
----<br />
<br />
<br />
=== Intro to Git ===<br />
'''"Half-Day [tbd - probably afternoon]"''' <br />
* Contact: Erin Fahy, Stanford University, efahy at stanford.edu<br />
* TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu<br />
<br />
This session will cover the fundamentals of git by discussing/going through (time allowing):<br />
* what is a distributed version control system<br />
* what is git and github<br />
* initializing a repo on a remote server/github<br />
* cloning an existing repo<br />
* creating a branch<br />
* contributing code to a repo<br />
* how to handle merge conflicts<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
----<br />
<br />
[[:Category:Code4Lib2014]]</div>Kevinreisshttps://wiki.code4lib.org/index.php?title=2014_preconference_proposals&diff=396982014 preconference proposals2013-10-15T14:43:12Z<p>Kevinreiss: </p>
<hr />
<div>Code4Lib 2014 Pre-Conference Proposals<br />
<br />
Proposals will be accepted through December 6th, 2013.<br />
<br />
Please fill out your proposal in the following format. If you are interested in attending a proposed pre-conference add your name to the list for that proposal. <br />
<br />
<br />
Pitch Format:<br />
<br />
hr.<br />
h2. NAME<br />
h3. "Full-Day|Half-Day" [PREFERRED TIME]<br />
p. Description<br />
<br />
h4. Interested in Attending<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here</div>Kevinreisshttps://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39400Code4Lib 2014 Conference Planning Volunteers2013-08-05T15:44:23Z<p>Kevinreiss: /* Pre-conference Committee */</p>
<hr />
<div>= Code4Lib 2014 Committees =<br />
<br />
If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br />
<br />
We hope to include at least one local person on each committee.<br />
<br />
A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. It has been shared with code4libcon and code4lib2014 google groups.<br />
<br />
The Code42014 Conference Committee meets bi-weekly on Tuesdays at 11am EDT. If you would like to join the calls or have an agenda item, email one or both of the co-Leads: Emily Lynema (NCSU) and Tim McGeary (UNC).<br />
<br />
== Book Give-Away Committee ==<br />
<br />
This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br />
<br />
Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br />
<br />
* Kevin S. Clarke (O'Reilly) and general wrangling (nominated as lead)<br />
* Michael B. Klein (Pragmatic) and winner-picker app<br />
<br />
== Keynote Speakers Committee ==<br />
<br />
This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br />
<br />
Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013<br /><br />
Keynote speaker voting - September 9, 2013 - September 20, 2013<br /><br />
Have speakers finalized by November 15, 2013<br />
<br />
* Jason Casden (NCSU) -- lead<br />
* Tom Johnson (Johnson.tom@gmail.com)<br />
* Bret Davidson (NCSU)<br />
* Jeff Campbell (UNC)<br />
<br />
== Onsite Volunteer Committee ==<br />
<br />
This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br />
<br />
* Kevin S. Clarke<br />
* Kevin Beswick (NCSU)<br />
* Yan Wang (NCCU)<br />
<br />
== Pre-conference Committee ==<br />
<br />
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.<br />
<br />
Call for pre-conf proposals -- October 14, 2013<br /><br />
Deadline for pre-conf proposals -- December 6, 2013 <br /><br />
Finalize pre-confs before registration opens -- January 3, 2014<br /><br />
Send rosters to pre-conf organizers -- by February 21, 2014<br />
<br />
* Adam Constabaris (NCSU) -- nominated as lead<br />
* Tim Shearer (UNC)<br />
* Kevin Reiss (Princeton University) -- kr2 [at] princeton dot edu<br />
<br />
== Program Committee ==<br />
<br />
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.<br />
<br />
Call for talk proposals -- October 14 - November 8, 2013<br /><br />
First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013<br /><br />
Voting on talks -- November 18, 203 - December 6, 2013<br /><br />
Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013<br /><br />
Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)<br /><br />
Post final program schedule with talks - January 13, 2014<br />
<br />
* Tom Johnson (Johnson.tom@gmail.com) -- lead<br />
* Kevin Beswick (NCSU)<br />
* Ranti Junus (MSU)<br />
* Roy Tennant (OCLC)<br />
* Trevor Thornton (hellotrevorthornton@gmail.com)<br />
<br />
== Scholarships Committee ==<br />
<br />
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.<br />
<br />
Call for applicants -- November 18, 2013 - December 13, 2013<br /><br />
Determine winners -- December 14, 2014 - January 5, 2014<br /><br />
Notify winners -- January 6, 2014 (must be before registration)<br />
<br />
* Jason Ronallo (NCSU) -- lead<br />
* Cory Lown (NCSU)<br />
* Bohyun Kim (FIU)<br />
<br />
== Social Activities Committee ==<br />
<br />
The committee plans, proposes, and organizes the evening activities.<br />
<br />
* Jason Raitz<br />
* Rosalyn Metz<br />
* Dre<br />
* Becky Yoose<br />
* Bohyun Kim<br />
<br />
== Sponsorships Committee ==<br />
<br />
This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br />
<br />
* Tim McGeary (UNC, Lead, tim.mcgeary@unc.edu)<br />
* Roy Tennant (OCLC)<br />
* Shaun Ellis (shaune@princeton.edu)<br />
* Robert H. McDonald (Indiana)<br />
* Sean Chen (Duke)<br />
* Thomas Dowling (Wake Forest)<br />
* Will Sexton (Duke)<br />
* Jeff Campbell (UNC)<br />
* Brett Bonfield (Collingswood Public)<br />
<br />
== Streaming Video Committee ==<br />
<br />
This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br />
<br />
Work with local team to get solid A/V estimates by late November 2013 to use for final budget.<br />
<br />
- Francis Kayiwa<br />
* Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br />
<br />
== T-Shirt Committee ==<br />
<br />
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.<br />
<br />
Call for T-shirt designs - December 2, 2014 - January 3, 2014<br /><br />
Voting on T-shirt designs - January 13, 2014 - January 24, 2014<br /><br />
Get bids based on sizes and design - January 27, 2014 - February 14, 2014<br /><br />
Order t-shirts by February 17, 2014<br />
<br />
*Charlie Morris (NCSU) -- lead<br />
<br />
== Voting Activities Committee ==<br />
<br />
This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br />
<br />
*Adam Constabaris (NCSU)<br />
<br />
== Whatever Committee ==<br />
<br />
This committee does whatever the organizers can't talk anyone else into doing.<br />
<br />
* Francis Kayiwa<br />
* Kevin S. Clarke<br />
* Dre<br />
* Ranti Junus<br />
<br />
== Wifi / Electrical / IRC Committee==<br />
<br />
This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br />
<br />
* [[User:highermath|Cary Gordon]], cgordon@chillco.com<br />
<br />
This is a newly proposed committee.<br />
<br />
= Documentation =<br />
To help with documention, no need to sign up, just start editing.<br />
* [[How To Plan A Code4LibCon]]<br />
<br />
== Documentation Interest Group ==<br />
Promote ongoing documentation efforts.<br />
<br />
[[Category: Code4Lib2014]]</div>Kevinreisshttps://wiki.code4lib.org/index.php?title=2013_preconference_proposals&diff=291232013 preconference proposals2012-12-05T19:56:45Z<p>Kevinreiss: /* Drupal4lib Sub-con Barcamp */</p>
<hr />
<div>Proposals '''now closed'''.<br />
<br />
Spaces available: 4+ Rooms<br />
<br />
Please follow the formatting guidelines:<br />
<pre><br />
=== Talk Title ===<br />
<br />
* Presenter/Leader, affiliation (optional), and email address (mandatory!)<br />
* Second Presenter/Leader, affiliation, email address, if applicable<br />
<br />
Description.<br />
</pre><br />
<br />
==Full Day==<br />
<br />
===Drupal4lib Sub-con Barcamp===<br />
<br />
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or <br />
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu<br />
<br />
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.<br />
<br />
If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.<br />
<br />
Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.<br />
<br />
'''I plan on attending:'''<br />
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)<br />
<br />
==Half Day Morning==<br />
=== Open space session ===<br />
<br />
* Dan Chudnov, dchud at gwu edu<br />
<br />
The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.<br />
<br />
If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.<br />
<br />
'''I plan on attending:'''<br />
* Devon Smith<br />
* First and last name<br />
* Esmé Cowles<br />
<br />
=== Delivery services ===<br />
* Ted Lawless, Brown University Library, tlawless at brown edu. <br />
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.<br />
<br />
Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands. <br />
<br />
Possible topics/activities include:<br />
* panel discussion of what some libraries have done in this area<br />
* comparisons of different approaches to addressing delivery <br />
* overview of tools available <br />
* sharing of strategies and experiences<br />
* time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/py360link Py360 Link]. <br />
<br />
Resources and background information:<br />
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway] <br />
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]<br />
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]<br />
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
=== Intro to Blacklight ===<br />
* Bess Sadler, Stanford University Library (bess at stanford.edu)<br />
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)<br />
<br />
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter. <br />
<br />
Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
=== RailsBridge Intro to Ruby on Rails ===<br />
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu<br />
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br />
* Shaun Ellis, Princeton University Library, shaune@princeton.edu<br />
* Ross Singer, Talis, rossfsinger@gmail.com<br />
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org<br />
* Anyone else want to come and help folks? Contact Jason.<br />
<br />
RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language, the Rails framework, and version control with git. Participants will build a working Rails application. <br />
<br />
There will be some pre-preconference preparation needed so that we can effectively use our time. Details to come.<br />
<br />
* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Shawn Kiewel<br />
<br />
===Intro to NoSQL Databases===<br />
* Joshua Gomez, George Washington University, jngomez at gwu edu<br />
<br />
Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called "Big Data" problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, CouchDB, and Neo4j.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
==Half Day Afternoon==<br />
=== Data Visualization Hackfest ===<br />
* Chris Beer, cabeer at stanford.edu<br />
* Dan Chudnov, dchud at gwu edu<br />
<br />
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly: <br />
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.<br />
- we'll separate into groups and hack on stuff.<br />
- at the end of the day, we'll present our progress.<br />
<br />
Not a code hacker? No worries; all skill sets and backgrounds are valuable! <br />
<br />
'''I plan on attending:'''<br />
* Devon Smith<br />
* First and last name<br />
<br />
=== Intro to Hydra ===<br />
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)<br />
* Mike Giarlo, Penn State Information Technology Services (michael at psu.edu)<br />
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br />
<br />
Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame. <br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Jeremy Prevost<br />
<br />
=== Intro to Blacklight ===<br />
* Bess Sadler, Stanford University Library (bess at stanford.edu)<br />
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)<br />
* Jason Ronallo, NC State (jronallo at gmail.com)<br />
* Shaun Ellis, Princeton University Library, (shaune@princeton.edu)<br />
<br />
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter. <br />
<br />
Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Shawn Kiewel<br />
<br />
=== DPLA Intro/Hacking ===<br />
<br />
* Presenter(s)/Leader(s): TBD<br />
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)<br />
<br />
This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
=== Fail4lib ===<br />
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)<br />
<br />
The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans ("The Pivot"), and failing more cheaply.<br />
<br />
Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:<br />
<br />
# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.<br />
# Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:<br />
#* Technical failure<br />
#* Failure to effectively address a real user need<br />
#* Overinvestment<br />
#* Outreach/Promotion failure<br />
#* Design/UX failure<br />
#* Project team communication failure<br />
#* Missed opportunities (risk-averse failure)<br />
#* Successes gleaned from failures<br />
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.<br />
# A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.<br />
<br />
I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
=== Solr 4 In Depth ===<br />
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)<br />
<br />
The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Esmé Cowles<br />
<br />
[[Category:Code4Lib2013]]</div>Kevinreisshttps://wiki.code4lib.org/index.php?title=2013_preconference_proposals&diff=291222013 preconference proposals2012-12-05T19:54:27Z<p>Kevinreiss: /* Delivery services */</p>
<hr />
<div>Proposals '''now closed'''.<br />
<br />
Spaces available: 4+ Rooms<br />
<br />
Please follow the formatting guidelines:<br />
<pre><br />
=== Talk Title ===<br />
<br />
* Presenter/Leader, affiliation (optional), and email address (mandatory!)<br />
* Second Presenter/Leader, affiliation, email address, if applicable<br />
<br />
Description.<br />
</pre><br />
<br />
==Full Day==<br />
<br />
===Drupal4lib Sub-con Barcamp===<br />
<br />
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or <br />
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu<br />
<br />
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.<br />
<br />
If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.<br />
<br />
Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
==Half Day Morning==<br />
=== Open space session ===<br />
<br />
* Dan Chudnov, dchud at gwu edu<br />
<br />
The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.<br />
<br />
If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.<br />
<br />
'''I plan on attending:'''<br />
* Devon Smith<br />
* First and last name<br />
* Esmé Cowles<br />
<br />
=== Delivery services ===<br />
* Ted Lawless, Brown University Library, tlawless at brown edu. <br />
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.<br />
<br />
Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands. <br />
<br />
Possible topics/activities include:<br />
* panel discussion of what some libraries have done in this area<br />
* comparisons of different approaches to addressing delivery <br />
* overview of tools available <br />
* sharing of strategies and experiences<br />
* time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/py360link Py360 Link]. <br />
<br />
Resources and background information:<br />
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway] <br />
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]<br />
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]<br />
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
=== Intro to Blacklight ===<br />
* Bess Sadler, Stanford University Library (bess at stanford.edu)<br />
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)<br />
<br />
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter. <br />
<br />
Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
=== RailsBridge Intro to Ruby on Rails ===<br />
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu<br />
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br />
* Shaun Ellis, Princeton University Library, shaune@princeton.edu<br />
* Ross Singer, Talis, rossfsinger@gmail.com<br />
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org<br />
* Anyone else want to come and help folks? Contact Jason.<br />
<br />
RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language, the Rails framework, and version control with git. Participants will build a working Rails application. <br />
<br />
There will be some pre-preconference preparation needed so that we can effectively use our time. Details to come.<br />
<br />
* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Shawn Kiewel<br />
<br />
===Intro to NoSQL Databases===<br />
* Joshua Gomez, George Washington University, jngomez at gwu edu<br />
<br />
Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called "Big Data" problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, CouchDB, and Neo4j.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
==Half Day Afternoon==<br />
=== Data Visualization Hackfest ===<br />
* Chris Beer, cabeer at stanford.edu<br />
* Dan Chudnov, dchud at gwu edu<br />
<br />
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly: <br />
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.<br />
- we'll separate into groups and hack on stuff.<br />
- at the end of the day, we'll present our progress.<br />
<br />
Not a code hacker? No worries; all skill sets and backgrounds are valuable! <br />
<br />
'''I plan on attending:'''<br />
* Devon Smith<br />
* First and last name<br />
<br />
=== Intro to Hydra ===<br />
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)<br />
* Mike Giarlo, Penn State Information Technology Services (michael at psu.edu)<br />
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br />
<br />
Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame. <br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Jeremy Prevost<br />
<br />
=== Intro to Blacklight ===<br />
* Bess Sadler, Stanford University Library (bess at stanford.edu)<br />
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)<br />
* Jason Ronallo, NC State (jronallo at gmail.com)<br />
* Shaun Ellis, Princeton University Library, (shaune@princeton.edu)<br />
<br />
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter. <br />
<br />
Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Shawn Kiewel<br />
<br />
=== DPLA Intro/Hacking ===<br />
<br />
* Presenter(s)/Leader(s): TBD<br />
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)<br />
<br />
This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
=== Fail4lib ===<br />
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)<br />
<br />
The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans ("The Pivot"), and failing more cheaply.<br />
<br />
Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:<br />
<br />
# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.<br />
# Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:<br />
#* Technical failure<br />
#* Failure to effectively address a real user need<br />
#* Overinvestment<br />
#* Outreach/Promotion failure<br />
#* Design/UX failure<br />
#* Project team communication failure<br />
#* Missed opportunities (risk-averse failure)<br />
#* Successes gleaned from failures<br />
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.<br />
# A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.<br />
<br />
I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
=== Solr 4 In Depth ===<br />
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)<br />
<br />
The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Esmé Cowles<br />
<br />
[[Category:Code4Lib2013]]</div>Kevinreisshttps://wiki.code4lib.org/index.php?title=2013_preconference_proposals&diff=288482013 preconference proposals2012-11-27T18:17:11Z<p>Kevinreiss: </p>
<hr />
<div>Proposals '''now closed'''.<br />
<br />
Spaces available: 4+ Rooms<br />
<br />
Please follow the formatting guidelines:<br />
<pre><br />
=== Talk Title ===<br />
<br />
* Presenter/Leader, affiliation (optional), and email address (mandatory!)<br />
* Second Presenter/Leader, affiliation, email address, if applicable<br />
<br />
Description.<br />
</pre><br />
<br />
==Full Day==<br />
<br />
===Drupal4lib Sub-con Barcamp===<br />
<br />
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or <br />
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu<br />
<br />
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.<br />
<br />
If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.<br />
<br />
Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.<br />
<br />
==Half Day Morning==<br />
<br />
=== Open space session ===<br />
<br />
* Dan Chudnov, dchud at gwu edu<br />
<br />
The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.<br />
<br />
If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.<br />
<br />
<br />
=== Delivery services ===<br />
<br />
* Ted Lawless, Brown University Library, tlawless at brown edu. <br />
<br />
Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands. <br />
<br />
Possible topics/activities include:<br />
<br />
* panel discussion of what some libraries have done in this area<br />
* comparisons of different approaches to addressing delivery <br />
* overview of tools available <br />
* sharing of strategies and experiences<br />
* time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/py360link Py360 Link]. <br />
<br />
<br />
Resources and background information:<br />
<br />
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway] <br />
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]<br />
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]<br />
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]<br />
<br />
<br />
=== Intro to Blacklight ===<br />
<br />
* Bess Sadler, Stanford University Library (bess at stanford.edu)<br />
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)<br />
<br />
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter. <br />
<br />
* Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.<br />
* Duration: half-day, morning<br />
<br />
<br />
=== RailsBridge Intro to Ruby on Rails ===<br />
<br />
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu<br />
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br />
* Anyone else want to come and help folks? Contact Jason.<br />
<br />
RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language, the Rails framework, and version control with git. Participants will build a working Rails application. <br />
<br />
There will be some pre-preconference preparation needed so that we can effectively use our time. Details to come.<br />
<br />
* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby<br />
<br />
<br />
===Intro to NoSQL Databases===<br />
* Joshua Gomez, George Washington University, jngomez at gwu edu<br />
<br />
Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called "Big Data" problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, CouchDB, and Neo4j.<br />
<br />
==Half Day Afternoon==<br />
=== Data Visualization Hackfest ===<br />
* Chris Beer, cabeer at stanford.edu<br />
* Dan Chudnov, dchud at gwu edu<br />
<br />
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly: <br />
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.<br />
- we'll separate into groups and hack on stuff.<br />
- at the end of the day, we'll present our progress.<br />
<br />
Not a code hacker? No worries; all skill sets and backgrounds are valuable! <br />
<br />
* Duration: half-day<br />
<br />
=== Intro to Hydra ===<br />
* Adam Wead, Rock and Roll Hall of Fame (amsterdamos at gmail.com)<br />
* Mike Giarlo, Penn State Information Technology Services (michael at psu.edu)<br />
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br />
<br />
Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame. <br />
<br />
* Duration: half-day, afternoon<br />
<br />
=== Intro to Blacklight ===<br />
<br />
* Bess Sadler, Stanford University Library (bess at stanford.edu)<br />
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)<br />
* Jason Ronallo, NC State (jronallo at gmail.com)<br />
<br />
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter. <br />
<br />
* Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome<br />
* Duration: half-day, afternoon<br />
<br />
<br />
=== DPLA Intro/Hacking ===<br />
<br />
* Presenter(s)/Leader(s): TBD<br />
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)<br />
<br />
This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.<br />
<br />
<br />
=== Fail4lib ===<br />
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)<br />
<br />
The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans ("The Pivot"), and failing more cheaply.<br />
<br />
Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:<br />
<br />
# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.<br />
# Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:<br />
#* Technical failure<br />
#* Failure to effectively address a real user need<br />
#* Overinvestment<br />
#* Outreach/Promotion failure<br />
#* Design/UX failure<br />
#* Project team communication failure<br />
#* Missed opportunities (risk-averse failure)<br />
#* Successes gleaned from failures<br />
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.<br />
# A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.<br />
<br />
I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.<br />
<br />
==Half Day Evening==<br />
<br />
=== Solr 4 In Depth ===<br />
<br />
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)<br />
<br />
The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.<br />
<br />
* Duration: half-day<br />
* Note: I put this under "Half Day Evening" only because I didn't want to conflict with the other great half day sessions already proposed here. However it makes the most sense to arrange the sessions is fine with me though.<br />
<br />
[[Category:Code4Lib2013]]</div>Kevinreisshttps://wiki.code4lib.org/index.php?title=2013_committees_sign-up_page&diff=207232013 committees sign-up page2012-08-09T17:23:13Z<p>Kevinreiss: /* Keynote Speakers Committee */</p>
<hr />
<div>= Code4Lib 2013 Committees =<br />
<br />
If you are interested in helping out with a particular part of the Code4Lib 2013 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br />
<br />
[[During the Conference Volunteers]]<br />
<br />
== Book Give-Away Committee ==<br />
*Kevin S. Clarke, ksclarke@gmail.com<br />
*Anjanette Young<br />
<br />
== Sponsorships Committee ==<br />
<br />
This committee organizes the sponsorship activities. Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br />
<br />
* Margaret Heller mheller@dom.edu<br />
* [[User:DataGazetteer|Peter Murray]], peter.murray@lyrasis.org<br />
* Kyle Banerjee banerjek@uoregon.edu<br />
* Bohyun Kim kimb et fiu dot edu<br />
* [http://roytennant.com/ Roy Tennant], roytennant@gmail.com<br />
* [http://twitter.com/TheRealArty Cynthia Ng], cynthia.s.ng at gmail<br />
* [[User:highermath|Cary Gordon]], cgordon@chillco.com<br />
<br />
== Keynote Speakers Committee ==<br />
<br />
This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community) and work with the speakers to arrange their travel and arrangements.<br />
<br />
*Francis Kayiwa kayiwa@ YOU EYE SEE DOT edu<br />
*Anjanette Young<br />
*Kevin Reiss kr2 @ princeton . edu<br />
<br />
== Program Committee ==<br />
<br />
This committee plans the structure of the program, arranges the voting on presentations, etc. These folks will also announce speakers, etc.<br />
* [[User:DataGazetteer|Peter Murray]], peter.murray@lyrasis.org<br />
* [http://twitter.com/ranti Ranti Junus], ranti.junus@gmail.com<br />
* Ray Schwartz, schwartzr2@wpunj.edu<br />
* [http://twitter.com/TheRealArty Cynthia Ng], cynthia.s.ng at gmail<br />
* Tom Johnson, thomas.johnson@oregonstate.edu<br />
<br />
== Scholarships Committee ==<br />
<br />
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.<br />
<br />
<br />
== T-Shirt Committee ==<br />
<br />
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes.<br />
<br />
* akorphan (akorphan AT ncsu DOT edu)<br />
* [[User:Pberry|Pberry]] Patrick Berry (pberry@csuchico.edu)<br />
<br />
== Social Activities Committee ==<br />
<br />
The committee plans, proposes, and organizes the evening activities.<br />
<br />
*Francis Kayiwa kayiwa@ YOU EYE SEE DOT edu<br />
*Ray Schwartz, schwartzr2@wpunj.edu<br />
*Bohyun Kim kimb et fiu dot edu<br />
*Shane Beers, sbeers depaul edu<br />
*[[User:JonGorman|Jon Gorman]], jtgorman @ illinois dot edu<br />
<br />
== Voting Activities Committee ==<br />
<br />
This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br />
* [http://twitter.com/jlefager Jim LeFager], jameslefager at gmail<br />
<br />
== Whatever Committee ==<br />
<br />
This committee does whatever the organizers can't talk anyone else into doing.<br />
<br />
* [[User:highermath|Cary Gordon]], cgordon@chillco.com<br />
* [http://twitter.com/jlefager Jim LeFager], jameslefager at gmail<br />
* [[User:Wolf29|Wolf Halton]], wolf.halton@lyrasis.org./dev/null<br />
<br />
= Documentation =<br />
To help with documention, no need to sign up, just start editing.<br />
* [[How To Plan A Code4LibCon]]<br />
<br />
== Documentation Interest Group ==<br />
Promote ongoing documentation efforts.<br />
<br />
[[Category: Code4Lib2013]]</div>Kevinreisshttps://wiki.code4lib.org/index.php?title=2012_preconference_proposals&diff=108532012 preconference proposals2012-02-04T20:28:08Z<p>Kevinreiss: /* Interest in Attending */</p>
<hr />
<div>=Proposals for 2012 Code4LibCon Preconferences=<br />
Proposals closed Sunday, November 20, 2011, so we can finalize the list and add them to registration! (The deadline for preconference proposals has passed.)<br />
<br />
Spaces available: main meeting room (max 275) + 5 breakout rooms (max 30-50). <br />
<br />
'''Please include a "Contact/Responsible Individual" name and email address so we know who is willing to put on the proposed precon.<br />
'''<br />
==Full Day==<br />
<br />
<br />
<br />
<br />
=== Developing applications using REST web services ===<br />
<br />
Been hearing about web services but don’t know where to start to build something? Have you built applications that use read services but are stumped by OAuth, Content Negotiation and HTTP Headers? Come dig in and learn how to build applications that interact with both read and write REST services. We’ll cover the basic principles and practices of REST services and discuss the Atom Publishing Protocol as a REST service and its extensibility. The group will examine and test the CouchDB HTTP API by building a simple list creation tool. You’ll learn how OCLC’s platform web services leverage Atom to expose the data and business processes from OCLC’s library systems. By the end of the session, you’ll know the basic principles of REST services, be able to perform Create, Read, Update and Delete operations via REST and be able to authenticate to REST services via API keys and OAuth.<br />
<br />
Come ready to learn and code!<br />
<br />
Presenter: Karen Coombs - coombsk at oclc dot org<br />
<br />
==== Interest in Attending ====<br />
<br />
*Sam Kome<br />
*Ray Schwartz (schwartzr2@wpunj.edu)<br />
*Jim Robinson<br />
*David Bucknum<br />
*Jean Rainwater<br />
*Joshua Gomez<br />
*Andy Kohler<br />
*Michael North<br />
* Tom Keays (keaysht at lemoyne dot edu)<br />
*Charlie Morris<br />
*Michael Lindsey<br />
* Kåre Fiedler Christiansen (morning only)<br />
* Jørn Thøgersen<br />
* Michael Poltorak Nielsen<br />
* Dre<br />
* Timothy Clarke (tclarke@muhlenberg.edu)<br />
* Keith Folsom<br />
* Rebecca Jones<br />
* Michael Doran (doran@uta.edu)<br />
* Ray Henry (ray dot henry at pcc dot edu)<br />
* Stephanie Collett<br />
* Bohyun Kim<br />
* Matt Connolly<br />
* Cynthia Ng<br />
* Justin Littman<br />
* Sibyl Schaefer<br />
* Ron Peterson (ronp@udel.edu)<br />
<br />
==Half Day Morning==<br />
<br />
<br />
=== Linkfest ===<br />
<br />
We've had talks and sessions galore about Linked Data at code4lib in past years. Let's focus on linking. Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web. At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there. May a kajillion links bloom!<br />
<br />
If you need an "intro to linked data" we can prep a good list of readings/talks to review before you come. But please come ready to link!<br />
<br />
Organizer type person: Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu<br />
<br />
==== Interest in Attending ====<br />
* Becky Yoose<br />
* Tom Johnson<br />
* Ed Summers<br />
* bernardo gomez ( bgomez at emory dot edu )<br />
* William Gunn<br />
* Jason Ronallo<br />
* Keri Thompson<br />
* David Lacy<br />
* Corey A Harper<br />
* Matt Phillips (mphillips@law.harvard.edu)<br />
* Declan Fleming<br />
* Shaun Ellis (shaune@princeton.edu)<br />
* Wendy Robertson<br />
* Joel Richard (richardjm AT si DOT edu)<br />
* Devon Smith<br />
* Scott Hanrath (shanrath AT ku DOT edu)<br />
* Jason Stirnaman (jstirnaman AT kumc DOT edu)<br />
* Sean Chen<br />
* Laura Smart<br />
* Tommy Ingulfsen<br />
* Mark Mounts (mark.mounts@dartmouth.edu)<br />
* Kate Zwaard<br />
* Cindy Harper<br />
<br />
=== What's New in Solr ===<br />
<br />
UPDATE: Erik won't be making it to Seattle, but will tune in and call in as desired to that time slot. Discuss Solr!!! I'll be lurking and helping out however I can.<br />
<br />
This session will bring folks up to speed on the latest developments in Lucene and Solr. There's always a lot of new capabilities as well as tips and tricks on using Solr in clever and powerful ways. <br />
<br />
Presenter: Erik Hatcher - erik . hatcher @ lucidimagination dot com (remotely calling in and/or via IRC)<br />
<br />
==== Interest in Attending ====<br />
* "Gabriel Farrell" <gsf24@drexel.edu><br />
* "Erik Hetzner" <erik.hetzner AT ucop BORK edu><br />
* "Michael B. Klein" <mbklein@gmail><br />
* Demian Katz (demian DOT katz AT villanova DOT edu)<br />
* Anoop Atre ~ anoop.atre AT mnsu . edu<br />
* David Isaak <david.isaak@kpchr.org><br />
* John Pillans <jpillan@indiana.edu><br />
* John Wynstra (john.wynstra@uni.edu)<br />
* mark a. matienzo (mark at matienzo dot oh are gee)<br />
* Sepehr Mavedati (sepehr DOT mavedati AT utoronto DOT ca)<br />
* Mads Villadsen<br />
* Jonathan Rochkind<br />
* Shahin Sahebi (shahin.ezzatsahebi at utoronto dot ca)<br />
* Naomi Dushay (ndushay at stanford dot edu)<br />
* Jeremy Nelson<br />
* Kirk Hess <kirkhess@illinois.edu><br />
* Gary Thompson<br />
* Larry Baerveldt <lrbaerveldt@gmail.com><br />
* Dennis Schafroth <dennis @ indexdata.com><br />
* Bobbi Fox <bobbi_fox at harvard dot edu><br />
* Ed Fugikawa <ed at coalliance dot org><br />
* Eric James <eric dot james at yale dot edu><br />
* Robert Haschart <rh9ec at virginia dot edu><br />
* Ted Lawless<br />
<br />
=== Knocking Down Silos: Tools and Approaches for Simplifying Discovery ===<br />
<br />
What strategies have you used to merge silos to give users a more streamlined search experience? How are libraries using tools like Drupal, Islandora, Dublin Core, Solr and Blacklight to make article, catalog and/or repository content discoverable via a single interface? If you’re interested in these issues, challenges and conundrums join us for a morning of thinking, dreaming and scheming. <br />
<br />
Speakers/Facilitators will be:<br />
- Thom Cox - Manager of Library Information Technology Services - Tufts University<br />
- Ken Varnum – Web Systems Manager - University of Michigan Libraries<br />
- Stephen Westman – Analyst Programmer, Emerging Technologies and Services - Oregon State University Libraries <br />
<br />
Contact: Margaret Mellinger - margaret dot mellinger at oregonstate dot edu<br />
<br />
==== Interest in Attending ====<br />
<br />
* David Uspal (david DOT uspal AT villanova DOT edu)<br />
* Tammy Allgood Wolf<br />
* Wayne Schneider<br />
* Laney McGlohon<br />
* Andrea Schurr (Andrea-Schurr AT utc DOT edu)<br />
* "Kevin S. Clarke" <ksclarke@gmail><br />
*Kevin Reiss (kr2 AT princeton DOT edu)<br />
<br />
==Half Day Afternoon==<br />
<br />
<br />
=== Git -r done === <br />
<br />
A session to cover all things Git, everyone's favorite distributed version control system. This session should cover a little bit of the history of Git, how it works, and how it's different than other version controls systems like SVN. Practical application should also be covered, including how to clone existing repos and contribute code back to them, how to host your own repository, and best practices for setting up a distributed network.<br />
<br />
Looking for attendees with real-life Git experience to share it, so we can all broaden our understanding of possible use-cases and nifty advanced features.<br />
<br />
Coordinator: <del>Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com</del><br />
<br />
Coordinator Stand-In: Michael B. Klein, Stanford University Libraries, @mbklein or mbklein at stanford.edu<br />
<br />
Helper: Cary Gordon, Cherry Hill Company, @highermath / cgordon@chillco.com<br />
<br />
==== Interest in Attending ====<br />
<br />
* Patrick Berry (pberry@csuchico.edu)<br />
* Chris Sharp (csharp@georgialibraries.org)<br />
* Matt Critchlow (mcritchlow@ucsd.edu)<br />
* Peter Murray (Peter.Murray@lyrasis.org)<br />
* Margaret Heller (mheller@dom.edu)<br />
* Kevin S. Clarke (ksclarke@gmail)<br />
* Michael B. Klein (mbklein@gmail)<br />
* Demian Katz (demian DOT katz AT villanova DOT edu)<br />
* Benjamin Shum (bshum@biblio.org)<br />
* Sibyl Schaefer (sschaefer at rockarch dot org)<br />
* Tammy Allgood Wolf (tammy.allgood@asu.edu)<br />
* Chad Nelson (cnelson17 AT gsu DOT edu)<br />
* Lisa Kurt (lkurt@unr.edu)<br />
* Matt Phillips (mphillips@law.harvard.edu)<br />
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)<br />
* John Wynstra (john.wynstra@uni.edu)<br />
* Declan Fleming<br />
* Shaun Ellis (shaune@princeton.edu)<br />
* Mads Villadsen<br />
* Kåre Fiedler Christiansen<br />
* Shahin Sahebi (shahin.ezzatsahebi@utoronto.ca)<br />
* Devon Smith<br />
* Jeremy Nelson<br />
* Stephanie Collett<br />
* Gary Thompson<br />
* Brian McBride (brian.mcbride at utah.edu)<br />
* Jacob Reed (jacob.reed at utah.edu)<br />
* Bohyun Kim (bohyun.kim at fiu.edu)<br />
* Larry Baerveldt <lrbaerveldt@gmail.com><br />
* Wayne Schneider<br />
* Matt Connolly<br />
* ernesto valencia<br />
* Ed Fugikawa <ed at coalliance dot org><br />
* Andrea Schurr (Andrea-Schurr at utc dot edu)<br />
* David Uspal (david DOT uspal AT villanova DOT edu)<br />
* Kate Zwaard<br />
* Kevin Reiss (kr2 AT princeton DOT edu)<br />
<br />
=== Blacklight ===<br />
<br />
This session will be walk-through of the architecture of Blacklight and what we have been improving since the rails 3 upgrade. In addition to the architecture of the software, we will also briefly discuss the architecture of the Blacklight community and what has made it successful so far.<br />
<br />
For part of the session we will install Blacklight live and get it up and running. This install demo will include a How-To on basic customizations in Blacklight using a test-driven approach (one of the cornerstones of the Blacklight community).<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.<br />
<br />
Installation screencast: https://www.youtube.com/watch?v=VLuHuoB8Z6w<br />
<br />
Presenters: Jessie Keck, Stanford University - jkeck at stanford dot edu | Molly Pickral, University of Virginia - mpc3c at virginia dot edu<br />
<br />
==== Interest in Attending ====<br />
* bernardo gomez ( bgomez at emory dot edu )<br />
* Mark Mounts <mark.mounts@dartmouth.edu><br />
* Sibyl Schaefer (sschaefer@rockarch.org)<br />
* John Pillans (jpillan@indiana.edu)<br />
* Mang Sun (mang.dot sun at rice dot edu)<br />
* Emily Lynema (emily_lynema at ncsu dot edu)<br />
* mark a. matienzo (mark at matienzo dot oh are gee)<br />
* Daniel Lovins (daniel dot lovins at nyu dot edu)<br />
* Jonathan Rochkind<br />
* Keith Folsom<br />
* Kirk Hess <kirkhess@illinois.edu><br />
* Jason Stirnaman (jstirnaman AT kumc DOT edu)<br />
* David Drexler <ddrexler@eou.edu><br />
* Mike Giarlo (michael at psu.edu)<br />
* Scott Fisher<br />
<br />
=== DACS and EAD Overview ===<br />
<br />
This session will look at what DACS (Describing Archives: a Content Standard) is and describe the ten required elements. Then there will be an overview of what EAD is, how it works, and the required elements. The final part will be a practice session on taking a paper finding aid and coding it using DACS and EAD.<br />
<br />
Presenter: Doris Munson, Eastern Washington University, dmunson at ewu dot edu<br />
(please feel free to contact me if you are interested in being a co-presenter)<br />
<br />
==== Interest in Attending ====<br />
* Francis Kayiwa ( kayiwa@ YouEyeSee dot edu )<br />
* Carmen Mitchell (carmenmitchell at gmail dot com)<br />
* Cindy Harper (charper at colgate dot edu)<br />
<br />
=== [[Digging into metadata: context, code, and collaboration]] ===<br />
<br />
Working with library/archival metadata is difficult. This preconference will tackle pressing questions and will show some of the intricacies of metadata (including AACR2/MARC) with exercises to demonstrate why inconsistencies exist in the data. What steps can the cataloging & metadata community take to help improve the quality of this data? What tools & techniques could help? Rules have evolved over time leaving dirty legacy data. Systems have impacted--and will continue to impact--data structure & design. How can this data be aggregated and refined for use in a new emerging data environments? What assumptions can safely be made and when do you need to inquire about local practice? We will end with a hack-fest where you can ask questions of experienced catalogers and get help with your metadata related problems. Bring your laptops and data. <br />
<br />
Person Herder: Becky Yoose, Grinnell College, yoosebec at grinnell dot edu<br />
<br />
Collaborators/Facilitators: Corey Harper, New York University - corey dot harper at nyu dot edu | Shana L. McDanold, University of Pennsylvania - <br />
mcdanold at pobox dot upenn dot edu | Laura Smart, Caltech - laura at library dot caltech dot edu<br />
<br />
==== Interest in Attending ====<br />
* Peter Green (pmgreen@princeton.edu)<br />
* David Isaak (david.isaak@kpchr.org)<br />
* Alex Rolfe (arolfe@georgefox.edu)<br />
* mark a. matienzo (mark at matienzo dot oh are gee)<br />
* Sarah Johnston (johnsts@stolaf.edu)<br />
* Derek Merleaux (derek@merleaux d0t net)<br />
* Adam Wead (awead {at} rockhall d.t 0 R G)<br />
* Tania Fersenheim (tania dot fersenheim at gmail) (I'm only a maybe because I may have a conflict in this time slot)<br />
* Robin Dean (robin at coalliance dot org)<br />
* Takanori Hayashi (tzhaya at affrc dot go dot jp)<br />
<br />
=== "Geo" ===<br />
This session will explore, we hope collaboratively, the presentation of objects on maps. There will be a section on workflow, a section on discovering objects via "geobrowse," a section discovery of objects via "geosearch," and an exploration of the discovery and presentation of geo-referenced images (e.g. historic maps). There will be open discussion on other approaches to map-based discovery. Emphasis will be placed on simplicity of workflow and implementation. Technologies include: Atom, Django, Solr, and OpenLayers. <br />
<br />
Presenters: Mike Graves, UNC Chapel Hill, gravm at email dot unc dot edu; Tim Shearer, UNC Chapel Hill, tshearer at email dot unc dot edu<br />
(please feel free to contact Tim if you are interested in being a co-presenter)<br />
<br />
==== Interest in Attending ====<br />
* "Gabriel Farrell" <gsf24@drexel.edu><br />
* Anoop Atre ~ anoop.atre AT mnsu . edu<br />
* Chad Nelson (cnelson17 AT gsu DOT edu)<br />
* Jason Casden (jmcasden AT ncsu DOT edu<br />
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)<br />
* Sepehr Mavedati (sepehr DOT mavedati AT utoronto DOT ca)<br />
* Michael Poltorak Nielsen<br />
* Wendy Robertson<br />
* Joel Richard (richardjm AT si DOT edu)<br />
* Jonathan Rochkind<br />
* Naomi Dushay (ndushay at stanford dot edu)<br />
* Scott Hanrath (shanrath AT ku DOT edu)<br />
* Aaron Collier (acollier AT csufresno DOT edu)<br />
* David Lacy (david DOT lacy AT villanova DOT edu)<br />
* Jen Weintraub (jweintraub AT library dot ucla dot edu)<br />
* Sean Chen<br />
* Bobbi Fox (bobbi_fox AT harvard dot edu)<br />
* Eric James (eric dot james at yale dot edu)<br />
* Ted Lawless<br />
<br />
== Half-day Evening ==<br />
<br />
=== Microsoft Campus Visit ===<br />
Join us for a trip across Lake Washington to Microsoft Headquarters. Bus will depart from the conference hotel at 4:15pm on Monday. We will visit the Microsoft Home, the Envisioning Lab, and/or the MS Library. The we'll head over to Microsoft Research for drinks and appetizers, and you'll see some great demos of some cool new (and free!) technologies coming out of MSR. Bus will get back to hotel by 9:00pm, plenty of time to hit a pub. You'll learn about:<br />
<br />
1. Layerscape -[http://communities.worldwidetelescope.org/]<br />
<br />
2. ChronoZoom - [http://research.microsoft.com/chronozoom/]<br />
<br />
3. F# - [http://www.tryfsharp.org]<br />
<br />
4. Microsoft Academic Search - [http://academic.research.microsoft.com]<br />
<br />
5. Microsoft Audio Visual Indexing System - [http://research.microsoft.com/mavis] <br />
<br />
Space is limited, so reserve your seat today Email Alex at the address below. <br />
<br />
Coordinator: Alex Wade, Microsoft Research, awade at microsoft dot com <br />
<br />
Presenters: Behrooz Chitsaz; Rob Fatland; Christophe Poulain; Michael Zyskowski <br />
<br />
==== Interest in Attending (Registration closed! We are now at capacity.) ====<br />
* Declan Fleming<br />
* Matt Critchlow<br />
* Tom Keays (keaysht at lemoyne dot edu)<br />
* mark a. matienzo (mark at matienzo dot oh are gee)<br />
* Mark Mounts <mark.mounts@dartmouth.edu><br />
* Kyle Banerjee <banerjek@uoregon.edu><br />
* Evviva Weinraub<br />
* Emily Lynema <emily_lynema at ncsu dot edu><br />
* Jason Casden <jmcasden AT ncsu DOT edu><br />
* Daniel Lovins <daniel.lovins@nyu.edu><br />
* Cynthia Ng<br />
* "Gabriel Farrell" <gsf24@drexel.edu><br />
* Shaun Ellis (shaune AT princeton DOT edu)<br />
* Derek Merleaux (derek@merleaux d0t net)<br />
* Mads Villadsen<br />
* Kåre Fiedler Christiansen<br />
* Jørn Thøgersen<br />
* Michael Poltorak Nielsen<br />
* Dileshni Jayasinghe<br />
* Matt Phillips (mphillips@law.harvard.edu)<br />
* Wendy Robertson<br />
* Shahin Sahebi<br />
* Matt Connolly <mjc12 AT cornell dot edu><br />
* Jeremy Nelson<br />
* Naomi Dushay (ndushay at stanford dot edu)<br />
* Dre<br />
* Ken Varnum (varnum umich edu)<br />
* David Uspal (david DOT uspal AT villanova DOT edu)<br />
* REGISTRATION IS NOW CLOSED<br />
<br />
[[Category: Code4Lib2012]]</div>Kevinreisshttps://wiki.code4lib.org/index.php?title=2012_preconference_proposals&diff=108522012 preconference proposals2012-02-04T20:26:46Z<p>Kevinreiss: /* Interest in Attending */</p>
<hr />
<div>=Proposals for 2012 Code4LibCon Preconferences=<br />
Proposals closed Sunday, November 20, 2011, so we can finalize the list and add them to registration! (The deadline for preconference proposals has passed.)<br />
<br />
Spaces available: main meeting room (max 275) + 5 breakout rooms (max 30-50). <br />
<br />
'''Please include a "Contact/Responsible Individual" name and email address so we know who is willing to put on the proposed precon.<br />
'''<br />
==Full Day==<br />
<br />
<br />
<br />
<br />
=== Developing applications using REST web services ===<br />
<br />
Been hearing about web services but don’t know where to start to build something? Have you built applications that use read services but are stumped by OAuth, Content Negotiation and HTTP Headers? Come dig in and learn how to build applications that interact with both read and write REST services. We’ll cover the basic principles and practices of REST services and discuss the Atom Publishing Protocol as a REST service and its extensibility. The group will examine and test the CouchDB HTTP API by building a simple list creation tool. You’ll learn how OCLC’s platform web services leverage Atom to expose the data and business processes from OCLC’s library systems. By the end of the session, you’ll know the basic principles of REST services, be able to perform Create, Read, Update and Delete operations via REST and be able to authenticate to REST services via API keys and OAuth.<br />
<br />
Come ready to learn and code!<br />
<br />
Presenter: Karen Coombs - coombsk at oclc dot org<br />
<br />
==== Interest in Attending ====<br />
<br />
*Sam Kome<br />
*Ray Schwartz (schwartzr2@wpunj.edu)<br />
*Jim Robinson<br />
*David Bucknum<br />
*Jean Rainwater<br />
*Joshua Gomez<br />
*Andy Kohler<br />
*Michael North<br />
* Tom Keays (keaysht at lemoyne dot edu)<br />
*Charlie Morris<br />
*Michael Lindsey<br />
* Kåre Fiedler Christiansen (morning only)<br />
* Jørn Thøgersen<br />
* Michael Poltorak Nielsen<br />
* Dre<br />
* Timothy Clarke (tclarke@muhlenberg.edu)<br />
* Keith Folsom<br />
* Rebecca Jones<br />
* Michael Doran (doran@uta.edu)<br />
* Ray Henry (ray dot henry at pcc dot edu)<br />
* Stephanie Collett<br />
* Bohyun Kim<br />
* Matt Connolly<br />
* Cynthia Ng<br />
* Justin Littman<br />
* Sibyl Schaefer<br />
* Ron Peterson (ronp@udel.edu)<br />
<br />
==Half Day Morning==<br />
<br />
<br />
=== Linkfest ===<br />
<br />
We've had talks and sessions galore about Linked Data at code4lib in past years. Let's focus on linking. Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web. At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there. May a kajillion links bloom!<br />
<br />
If you need an "intro to linked data" we can prep a good list of readings/talks to review before you come. But please come ready to link!<br />
<br />
Organizer type person: Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu<br />
<br />
==== Interest in Attending ====<br />
* Becky Yoose<br />
* Tom Johnson<br />
* Ed Summers<br />
* bernardo gomez ( bgomez at emory dot edu )<br />
* William Gunn<br />
* Jason Ronallo<br />
* Keri Thompson<br />
* David Lacy<br />
* Corey A Harper<br />
* Matt Phillips (mphillips@law.harvard.edu)<br />
* Declan Fleming<br />
* Shaun Ellis (shaune@princeton.edu)<br />
* Wendy Robertson<br />
* Joel Richard (richardjm AT si DOT edu)<br />
* Devon Smith<br />
* Scott Hanrath (shanrath AT ku DOT edu)<br />
* Jason Stirnaman (jstirnaman AT kumc DOT edu)<br />
* Sean Chen<br />
* Laura Smart<br />
* Tommy Ingulfsen<br />
* Mark Mounts (mark.mounts@dartmouth.edu)<br />
* Kate Zwaard<br />
* Cindy Harper<br />
<br />
=== What's New in Solr ===<br />
<br />
UPDATE: Erik won't be making it to Seattle, but will tune in and call in as desired to that time slot. Discuss Solr!!! I'll be lurking and helping out however I can.<br />
<br />
This session will bring folks up to speed on the latest developments in Lucene and Solr. There's always a lot of new capabilities as well as tips and tricks on using Solr in clever and powerful ways. <br />
<br />
Presenter: Erik Hatcher - erik . hatcher @ lucidimagination dot com (remotely calling in and/or via IRC)<br />
<br />
==== Interest in Attending ====<br />
* "Gabriel Farrell" <gsf24@drexel.edu><br />
* "Erik Hetzner" <erik.hetzner AT ucop BORK edu><br />
* "Michael B. Klein" <mbklein@gmail><br />
* Demian Katz (demian DOT katz AT villanova DOT edu)<br />
* Anoop Atre ~ anoop.atre AT mnsu . edu<br />
* David Isaak <david.isaak@kpchr.org><br />
* John Pillans <jpillan@indiana.edu><br />
* John Wynstra (john.wynstra@uni.edu)<br />
* mark a. matienzo (mark at matienzo dot oh are gee)<br />
* Sepehr Mavedati (sepehr DOT mavedati AT utoronto DOT ca)<br />
* Mads Villadsen<br />
* Jonathan Rochkind<br />
* Shahin Sahebi (shahin.ezzatsahebi at utoronto dot ca)<br />
* Naomi Dushay (ndushay at stanford dot edu)<br />
* Jeremy Nelson<br />
* Kirk Hess <kirkhess@illinois.edu><br />
* Gary Thompson<br />
* Larry Baerveldt <lrbaerveldt@gmail.com><br />
* Dennis Schafroth <dennis @ indexdata.com><br />
* Bobbi Fox <bobbi_fox at harvard dot edu><br />
* Ed Fugikawa <ed at coalliance dot org><br />
* Eric James <eric dot james at yale dot edu><br />
* Robert Haschart <rh9ec at virginia dot edu><br />
* Ted Lawless<br />
<br />
=== Knocking Down Silos: Tools and Approaches for Simplifying Discovery ===<br />
<br />
What strategies have you used to merge silos to give users a more streamlined search experience? How are libraries using tools like Drupal, Islandora, Dublin Core, Solr and Blacklight to make article, catalog and/or repository content discoverable via a single interface? If you’re interested in these issues, challenges and conundrums join us for a morning of thinking, dreaming and scheming. <br />
<br />
Speakers/Facilitators will be:<br />
- Thom Cox - Manager of Library Information Technology Services - Tufts University<br />
- Ken Varnum – Web Systems Manager - University of Michigan Libraries<br />
- Stephen Westman – Analyst Programmer, Emerging Technologies and Services - Oregon State University Libraries <br />
<br />
Contact: Margaret Mellinger - margaret dot mellinger at oregonstate dot edu<br />
<br />
==== Interest in Attending ====<br />
<br />
* David Uspal (david DOT uspal AT villanova DOT edu)<br />
* Tammy Allgood Wolf<br />
* Wayne Schneider<br />
* Laney McGlohon<br />
* Andrea Schurr (Andrea-Schurr AT utc DOT edu)<br />
* "Kevin S. Clarke" <ksclarke@gmail><br />
*Kevin Reiss (kr2 AT princeton DOT edu)<br />
<br />
==Half Day Afternoon==<br />
<br />
<br />
=== Git -r done === <br />
<br />
A session to cover all things Git, everyone's favorite distributed version control system. This session should cover a little bit of the history of Git, how it works, and how it's different than other version controls systems like SVN. Practical application should also be covered, including how to clone existing repos and contribute code back to them, how to host your own repository, and best practices for setting up a distributed network.<br />
<br />
Looking for attendees with real-life Git experience to share it, so we can all broaden our understanding of possible use-cases and nifty advanced features.<br />
<br />
Coordinator: <del>Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com</del><br />
<br />
Coordinator Stand-In: Michael B. Klein, Stanford University Libraries, @mbklein or mbklein at stanford.edu<br />
<br />
Helper: Cary Gordon, Cherry Hill Company, @highermath / cgordon@chillco.com<br />
<br />
==== Interest in Attending ====<br />
<br />
* Patrick Berry (pberry@csuchico.edu)<br />
* Chris Sharp (csharp@georgialibraries.org)<br />
* Matt Critchlow (mcritchlow@ucsd.edu)<br />
* Peter Murray (Peter.Murray@lyrasis.org)<br />
* Margaret Heller (mheller@dom.edu)<br />
* Kevin S. Clarke (ksclarke@gmail)<br />
* Michael B. Klein (mbklein@gmail)<br />
* Demian Katz (demian DOT katz AT villanova DOT edu)<br />
* Benjamin Shum (bshum@biblio.org)<br />
* Sibyl Schaefer (sschaefer at rockarch dot org)<br />
* Tammy Allgood Wolf (tammy.allgood@asu.edu)<br />
* Chad Nelson (cnelson17 AT gsu DOT edu)<br />
* Lisa Kurt (lkurt@unr.edu)<br />
* Matt Phillips (mphillips@law.harvard.edu)<br />
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)<br />
* John Wynstra (john.wynstra@uni.edu)<br />
* Declan Fleming<br />
* Shaun Ellis (shaune@princeton.edu)<br />
* Mads Villadsen<br />
* Kåre Fiedler Christiansen<br />
* Shahin Sahebi (shahin.ezzatsahebi@utoronto.ca)<br />
* Devon Smith<br />
* Jeremy Nelson<br />
* Stephanie Collett<br />
* Gary Thompson<br />
* Brian McBride (brian.mcbride at utah.edu)<br />
* Jacob Reed (jacob.reed at utah.edu)<br />
* Bohyun Kim (bohyun.kim at fiu.edu)<br />
* Larry Baerveldt <lrbaerveldt@gmail.com><br />
* Wayne Schneider<br />
* Matt Connolly<br />
* ernesto valencia<br />
* Ed Fugikawa <ed at coalliance dot org><br />
* Andrea Schurr (Andrea-Schurr at utc dot edu)<br />
* David Uspal (david DOT uspal AT villanova DOT edu)<br />
* Kate Zwaard<br />
<br />
=== Blacklight ===<br />
<br />
This session will be walk-through of the architecture of Blacklight and what we have been improving since the rails 3 upgrade. In addition to the architecture of the software, we will also briefly discuss the architecture of the Blacklight community and what has made it successful so far.<br />
<br />
For part of the session we will install Blacklight live and get it up and running. This install demo will include a How-To on basic customizations in Blacklight using a test-driven approach (one of the cornerstones of the Blacklight community).<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.<br />
<br />
Installation screencast: https://www.youtube.com/watch?v=VLuHuoB8Z6w<br />
<br />
Presenters: Jessie Keck, Stanford University - jkeck at stanford dot edu | Molly Pickral, University of Virginia - mpc3c at virginia dot edu<br />
<br />
==== Interest in Attending ====<br />
* bernardo gomez ( bgomez at emory dot edu )<br />
* Mark Mounts <mark.mounts@dartmouth.edu><br />
* Sibyl Schaefer (sschaefer@rockarch.org)<br />
* John Pillans (jpillan@indiana.edu)<br />
* Mang Sun (mang.dot sun at rice dot edu)<br />
* Emily Lynema (emily_lynema at ncsu dot edu)<br />
* mark a. matienzo (mark at matienzo dot oh are gee)<br />
* Daniel Lovins (daniel dot lovins at nyu dot edu)<br />
* Jonathan Rochkind<br />
* Keith Folsom<br />
* Kirk Hess <kirkhess@illinois.edu><br />
* Jason Stirnaman (jstirnaman AT kumc DOT edu)<br />
* David Drexler <ddrexler@eou.edu><br />
* Mike Giarlo (michael at psu.edu)<br />
* Scott Fisher<br />
<br />
=== DACS and EAD Overview ===<br />
<br />
This session will look at what DACS (Describing Archives: a Content Standard) is and describe the ten required elements. Then there will be an overview of what EAD is, how it works, and the required elements. The final part will be a practice session on taking a paper finding aid and coding it using DACS and EAD.<br />
<br />
Presenter: Doris Munson, Eastern Washington University, dmunson at ewu dot edu<br />
(please feel free to contact me if you are interested in being a co-presenter)<br />
<br />
==== Interest in Attending ====<br />
* Francis Kayiwa ( kayiwa@ YouEyeSee dot edu )<br />
* Carmen Mitchell (carmenmitchell at gmail dot com)<br />
* Cindy Harper (charper at colgate dot edu)<br />
<br />
=== [[Digging into metadata: context, code, and collaboration]] ===<br />
<br />
Working with library/archival metadata is difficult. This preconference will tackle pressing questions and will show some of the intricacies of metadata (including AACR2/MARC) with exercises to demonstrate why inconsistencies exist in the data. What steps can the cataloging & metadata community take to help improve the quality of this data? What tools & techniques could help? Rules have evolved over time leaving dirty legacy data. Systems have impacted--and will continue to impact--data structure & design. How can this data be aggregated and refined for use in a new emerging data environments? What assumptions can safely be made and when do you need to inquire about local practice? We will end with a hack-fest where you can ask questions of experienced catalogers and get help with your metadata related problems. Bring your laptops and data. <br />
<br />
Person Herder: Becky Yoose, Grinnell College, yoosebec at grinnell dot edu<br />
<br />
Collaborators/Facilitators: Corey Harper, New York University - corey dot harper at nyu dot edu | Shana L. McDanold, University of Pennsylvania - <br />
mcdanold at pobox dot upenn dot edu | Laura Smart, Caltech - laura at library dot caltech dot edu<br />
<br />
==== Interest in Attending ====<br />
* Peter Green (pmgreen@princeton.edu)<br />
* David Isaak (david.isaak@kpchr.org)<br />
* Alex Rolfe (arolfe@georgefox.edu)<br />
* mark a. matienzo (mark at matienzo dot oh are gee)<br />
* Sarah Johnston (johnsts@stolaf.edu)<br />
* Derek Merleaux (derek@merleaux d0t net)<br />
* Adam Wead (awead {at} rockhall d.t 0 R G)<br />
* Tania Fersenheim (tania dot fersenheim at gmail) (I'm only a maybe because I may have a conflict in this time slot)<br />
* Robin Dean (robin at coalliance dot org)<br />
* Takanori Hayashi (tzhaya at affrc dot go dot jp)<br />
<br />
=== "Geo" ===<br />
This session will explore, we hope collaboratively, the presentation of objects on maps. There will be a section on workflow, a section on discovering objects via "geobrowse," a section discovery of objects via "geosearch," and an exploration of the discovery and presentation of geo-referenced images (e.g. historic maps). There will be open discussion on other approaches to map-based discovery. Emphasis will be placed on simplicity of workflow and implementation. Technologies include: Atom, Django, Solr, and OpenLayers. <br />
<br />
Presenters: Mike Graves, UNC Chapel Hill, gravm at email dot unc dot edu; Tim Shearer, UNC Chapel Hill, tshearer at email dot unc dot edu<br />
(please feel free to contact Tim if you are interested in being a co-presenter)<br />
<br />
==== Interest in Attending ====<br />
* "Gabriel Farrell" <gsf24@drexel.edu><br />
* Anoop Atre ~ anoop.atre AT mnsu . edu<br />
* Chad Nelson (cnelson17 AT gsu DOT edu)<br />
* Jason Casden (jmcasden AT ncsu DOT edu<br />
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)<br />
* Sepehr Mavedati (sepehr DOT mavedati AT utoronto DOT ca)<br />
* Michael Poltorak Nielsen<br />
* Wendy Robertson<br />
* Joel Richard (richardjm AT si DOT edu)<br />
* Jonathan Rochkind<br />
* Naomi Dushay (ndushay at stanford dot edu)<br />
* Scott Hanrath (shanrath AT ku DOT edu)<br />
* Aaron Collier (acollier AT csufresno DOT edu)<br />
* David Lacy (david DOT lacy AT villanova DOT edu)<br />
* Jen Weintraub (jweintraub AT library dot ucla dot edu)<br />
* Sean Chen<br />
* Bobbi Fox (bobbi_fox AT harvard dot edu)<br />
* Eric James (eric dot james at yale dot edu)<br />
* Ted Lawless<br />
<br />
== Half-day Evening ==<br />
<br />
=== Microsoft Campus Visit ===<br />
Join us for a trip across Lake Washington to Microsoft Headquarters. Bus will depart from the conference hotel at 4:15pm on Monday. We will visit the Microsoft Home, the Envisioning Lab, and/or the MS Library. The we'll head over to Microsoft Research for drinks and appetizers, and you'll see some great demos of some cool new (and free!) technologies coming out of MSR. Bus will get back to hotel by 9:00pm, plenty of time to hit a pub. You'll learn about:<br />
<br />
1. Layerscape -[http://communities.worldwidetelescope.org/]<br />
<br />
2. ChronoZoom - [http://research.microsoft.com/chronozoom/]<br />
<br />
3. F# - [http://www.tryfsharp.org]<br />
<br />
4. Microsoft Academic Search - [http://academic.research.microsoft.com]<br />
<br />
5. Microsoft Audio Visual Indexing System - [http://research.microsoft.com/mavis] <br />
<br />
Space is limited, so reserve your seat today Email Alex at the address below. <br />
<br />
Coordinator: Alex Wade, Microsoft Research, awade at microsoft dot com <br />
<br />
Presenters: Behrooz Chitsaz; Rob Fatland; Christophe Poulain; Michael Zyskowski <br />
<br />
==== Interest in Attending (Registration closed! We are now at capacity.) ====<br />
* Declan Fleming<br />
* Matt Critchlow<br />
* Tom Keays (keaysht at lemoyne dot edu)<br />
* mark a. matienzo (mark at matienzo dot oh are gee)<br />
* Mark Mounts <mark.mounts@dartmouth.edu><br />
* Kyle Banerjee <banerjek@uoregon.edu><br />
* Evviva Weinraub<br />
* Emily Lynema <emily_lynema at ncsu dot edu><br />
* Jason Casden <jmcasden AT ncsu DOT edu><br />
* Daniel Lovins <daniel.lovins@nyu.edu><br />
* Cynthia Ng<br />
* "Gabriel Farrell" <gsf24@drexel.edu><br />
* Shaun Ellis (shaune AT princeton DOT edu)<br />
* Derek Merleaux (derek@merleaux d0t net)<br />
* Mads Villadsen<br />
* Kåre Fiedler Christiansen<br />
* Jørn Thøgersen<br />
* Michael Poltorak Nielsen<br />
* Dileshni Jayasinghe<br />
* Matt Phillips (mphillips@law.harvard.edu)<br />
* Wendy Robertson<br />
* Shahin Sahebi<br />
* Matt Connolly <mjc12 AT cornell dot edu><br />
* Jeremy Nelson<br />
* Naomi Dushay (ndushay at stanford dot edu)<br />
* Dre<br />
* Ken Varnum (varnum umich edu)<br />
* David Uspal (david DOT uspal AT villanova DOT edu)<br />
* REGISTRATION IS NOW CLOSED<br />
<br />
[[Category: Code4Lib2012]]</div>Kevinreiss