<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.code4lib.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=ErikHatcher</id>
		<title>Code4Lib - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.code4lib.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=ErikHatcher"/>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/Special:Contributions/ErikHatcher"/>
		<updated>2026-04-09T02:59:22Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.26.2</generator>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_talks_proposals&amp;diff=27836</id>
		<title>2013 talks proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_talks_proposals&amp;diff=27836"/>
				<updated>2012-10-31T19:59:52Z</updated>
		
		<summary type="html">&lt;p&gt;ErikHatcher: /* Solr Update */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Deadline for talk submission is ''Friday, November 2'' at 5pm PT. We ask that no changes be made after this point, so that every voter reads the same thing. You can update your description again after voting closes.&lt;br /&gt;
&lt;br /&gt;
Prepared talks are 20 minutes (including setup and questions), and focus on one or more of the following areas:&lt;br /&gt;
* tools (some cool new software, software library or integration platform)&lt;br /&gt;
* specs (how to get the most out of some protocols, or proposals for new ones)&lt;br /&gt;
* challenges (one or more big problems we should collectively address)&lt;br /&gt;
&lt;br /&gt;
The community will vote on proposals using the criteria of:&lt;br /&gt;
* usefulness&lt;br /&gt;
* newness&lt;br /&gt;
* geekiness&lt;br /&gt;
* uniqueness&lt;br /&gt;
* awesomeness&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
== Talk Title ==&lt;br /&gt;
 &lt;br /&gt;
* Speaker's name, affiliation, and email address&lt;br /&gt;
* Second speaker's name, affiliation, email address, if applicable&lt;br /&gt;
&lt;br /&gt;
Abstract of no more than 500 words.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Modernizing VuFind with Zend Framework 2 ==&lt;br /&gt;
&lt;br /&gt;
* Demian Katz, Villanova University, demian DOT katz AT villanova DOT edu&lt;br /&gt;
&lt;br /&gt;
When setting goals for a new major release of VuFind, use of an existing web framework was an important decision to encourage standardization and avoid reinvention of the wheel.  Zend Framework 2 was selected as providing the best balance between the cutting-edge (ZF2 was released in 2012) and stability (ZF1 has a long history and many adopters).  This talk will examine some of the architecture and features of the new framework and discuss how it has been used to improve the VuFind project.&lt;br /&gt;
&lt;br /&gt;
== Did You Really Say That Out Loud?  Tools and Techniques for Safe Public WiFi Computing  ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]], LYRASIS, Peter.Murray@lyrasis.org&lt;br /&gt;
&lt;br /&gt;
Public WiFi networks, even those that have passwords, are nothing more that an old-time [https://en.wikipedia.org/wiki/Party_line_(telephony) party line]: what every you say can be easily heard by anyone nearby.  &lt;br /&gt;
Remember [https://en.wikipedia.org/wiki/Firesheep Firesheep]?  &lt;br /&gt;
It was an extension to Firefox that demonstrated how easy it was to snag session cookies and impersonate someone else.&lt;br /&gt;
So what are you sending out over the airwaves, and what techniques are available to prevent eavesdropping?&lt;br /&gt;
This talk will demonstrate tools and techniques for desktop and mobile operating systems that you should be using right now -- right here at Code4Lib -- to protect your data and your network activity.&lt;br /&gt;
&lt;br /&gt;
== Drupal 8 Preview — Symfony and Twig ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Drupal is a great platform for building web applications. Last year, the core developers decided to adopt the Symfony PHP framework, because it would lay the groundwork for the modernization (and de-PHP4ification) of the Drupal codebase. As I write this, the Symfony ClassLoader and HttpFoundation libraries are committed to Drupal core, with more elements likely before Drupal 8 code freeze.&lt;br /&gt;
&lt;br /&gt;
It seems almost certain that the Twig templating engine will supplant PHPtemplate as the core Drupal template engine. Twig is a powerful, secure theme building tool that removes PHP from the templating system, the result being a very concise and powerful theme layer.&lt;br /&gt;
&lt;br /&gt;
Symfony and Twig have a common creator, Fabien Potencier, who's overall goal is to rid the world of the excesses of PHP 4.&lt;br /&gt;
&lt;br /&gt;
== Neat! But How Do We Do It? - The Real-world Problem of Digitizing Complex Corporate Digital Objects ==&lt;br /&gt;
&lt;br /&gt;
* Matthew Mariner, University of Colorado Denver, Auraria Library, matthew.mariner@ucdenver.edu&lt;br /&gt;
&lt;br /&gt;
Isn't it neat when you discover that you are the steward of dozens of Sanborn Fire Instance Maps, hundreds of issues of a city directory, and thousands of photographs of persons in either aforementioned medium? And it's even cooler when you decide, &amp;quot;Let's digitize these together and make them one big awesome project to support public urban history&amp;quot;?  Unfortunately it's a far more difficult process than one imagines at inception and, sadly, doesn't always come to fruition.  My goal here is to discuss the technological (and philosophical) problems librarians and archivists face when trying to create ultra-rich complex corporate digital projects, or, rather, projects consisting of at least three facets interrelated by theme.  I intend to address these problems by suggesting management solutions, web workarounds, and, perhaps, a philosophy that might help in determining whether to even move forward or not.  Expect a few case studies of &amp;quot;grand ideas crushed by technological limitations&amp;quot; and &amp;quot;projects on the right track&amp;quot; to follow.   &lt;br /&gt;
 &lt;br /&gt;
== ResCarta Tools building a standard format for audio archiving, discovery and display ==&lt;br /&gt;
&lt;br /&gt;
* [[User:sarney|John Sarnowski]], The ResCarta Foundation, john.sarnowski@rescarta.org&lt;br /&gt;
&lt;br /&gt;
The free ResCarta Toolkit has been used by libraries and archives around the world to host city directories, newspapers, and historic photographs and by aerospace companies to search and find millions of engineering documents.  Now the ResCarta team has released audio additions to the toolkit. &lt;br /&gt;
&lt;br /&gt;
Create full text searchable oral histories, news stories, interviews. or build an archive of lectures; all done to Library of Congress standards.  The included transcription editor allows for accurate correction of the data conversion tool’s output.  Build true archives of text, photos and audio.  A single audio file carries the embedded Axml metadata, transcription, and word location information. Checks with the FADGI BWF Metaedit.&lt;br /&gt;
&lt;br /&gt;
ResCarta-Web presents your audio to IE, Chome, Firefox, Safari, and Opera browsers with full playback and word search capability. Display format is OGG!! &lt;br /&gt;
&lt;br /&gt;
You have to see this tool in action.  Twenty minutes from an audio file to transcribed, text-searchable website.  Be there or be L seven (Yeah, I’m that old)   &lt;br /&gt;
&lt;br /&gt;
== Format Designation in MARC Records: A Trip Down the Rabbit-Hole ==&lt;br /&gt;
 &lt;br /&gt;
* Michael Doran, University of Texas at Arlington, doran@uta.edu&lt;br /&gt;
&lt;br /&gt;
This presentation will use a seemingly simple data point, the &amp;quot;format&amp;quot; of the item being described, to illustrate some of the complexities and challenges inherent in the parsing of MARC records.  I will talk about abstract vs. concrete forms; format designation in the Leader, 006, 007, and 008 fixed fields as well as the 245 and 300 variable fields; pseudo-formats; what is mandatory vs. optional in respect to format designation in cataloging practice; and the differences between cataloging theory and practice as observed via format-related data mining of a mid-size academic library collection. &lt;br /&gt;
&lt;br /&gt;
I understand that most of us go to code4lib to hear about the latest sexy technologies.  While MARC isn't sexy, many of the new tools being discussed still need to be populated with data gleaned from MARC records.  MARC format designation has ramifications for search and retrieval, limits, and facets, both in the ILS and further downstream in next generation OPACs and web-scale discovery tools.  Even veteran library coders will learn something from this session. &lt;br /&gt;
&lt;br /&gt;
== Touch Kiosk 2: Piezoelectric Boogaloo ==&lt;br /&gt;
&lt;br /&gt;
* Andreas Orphanides, North Carolina State University Libraries, akorphan@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
At the NCSU Libraries, we provide realtime access to information on library spaces and services through an interactive touchscreen kiosk in our Learning Commons. In the summer of 2012, two years after its initial deployment, I redeveloped the kiosk application from the ground up, with an entirely new codebase and a completely redesigned user interface. The changes I implemented were designed to remedy previously identified shortcomings in the code and the interface design [1], and to enhance overall stability and performance of the application.&lt;br /&gt;
&lt;br /&gt;
In this presentation I will outline my revision process, highlighting the lessons I learned and the practices I implemented in the course of redevelopment. I will highlight the key features of the HTML/Javascript codebase that allow for increased stability, flexibility, and ease of maintenance; and identify the changes to the user interface that resulted from the usability findings I uncovered in my previous research. Finally, I will compare the usage patterns of the new interface to the analysis of the previous implementation to examine the practical effect of the implemented changes.&lt;br /&gt;
&lt;br /&gt;
I will also provide access to a genericized version of the interface code for others to build their own implementations of similar kiosk applications.&lt;br /&gt;
&lt;br /&gt;
[1] http://journal.code4lib.org/articles/5832&lt;br /&gt;
&lt;br /&gt;
== Wayfinding in a Cloud: Location Service for libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Petteri Kivimäki, The National Library of Finland, petteri.kivimaki@helsinki.fi&lt;br /&gt;
&lt;br /&gt;
Searching for books in large libraries can be a difficult task for a novice library user. This paper presents The Location Service, software as a service (SaaS) wayfinding application developed and managed by The National Library of Finland, which is targeted for all the libraries. The service provides additional information and map-based guidance to books and collections by showing their location on a map, and it can be integrated with any library management system, as the integration happens by adding a link to the service in the search interface. The service is being developed continuously based on the feedback received from the users.&lt;br /&gt;
&lt;br /&gt;
The service has two user interfaces: One for the customers and one for the library staff for managing the information related to the locations. The UI for the customers is fully customizable by the libraries, and the customization is done via template files by using the following techniques: HTML, CSS, and Javascript/jQuery. The service supports multiple languages, and the libraries have a full control of the languages, which they want to support in their environment.&lt;br /&gt;
&lt;br /&gt;
The service is written in Java and it uses Spring and Hibernate frameworks. The data is stored in PostgreSQL database, which is shared by all the libraries. They do not possess a direct access to the database, but the service offers an interface, which makes it possible to retrieve XML data over HTTP. Modification of the data via admin UI, however, is restricted, and access on the other libraries’ data is blocked.&lt;br /&gt;
&lt;br /&gt;
== Empowering Collection Owners with Automated Bulk Ingest Tools for DSpace ==&lt;br /&gt;
&lt;br /&gt;
* Terry Brady, Georgetown University, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Library has developed a number of applications to expedite the process of ingesting content into DSpace.&lt;br /&gt;
* Automatically inventory a collection of documents or images to be uploaded&lt;br /&gt;
* Generate a spreadsheet for metadata capture based on the inventory&lt;br /&gt;
* Generate item-level ingest folders, contents files and dublin core metadata for the items to be ingested&lt;br /&gt;
* Validate the contents of ingest folders prior to initiating the ingest to DSpace&lt;br /&gt;
* Present users with a simple, web-based form to initiate the batch ingest process&lt;br /&gt;
&lt;br /&gt;
The applications have eliminated a number of error-prone steps from the ingest workflow and have significantly reduced a number of tedious data editing steps.  These applications have empowered content experts to be in charge of their own collections. &lt;br /&gt;
&lt;br /&gt;
In this presentation, I will provide a demonstration of the tools that were built and discuss the development process that was followed.&lt;br /&gt;
&lt;br /&gt;
== Quality Assurance Reports for DSpace Collections ==&lt;br /&gt;
&lt;br /&gt;
* Terry Brady, Georgetown University, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Library has developed a collection of quality assurance reports to improve the consistency of the metadata in our DSpace collections.  The report infrastructure permits the creation of query snippets to test for possible consistency errors within the repository such as items missing thumbnails, items with multiple thumbnails, items missing a creation date, items containing improperly formatted dates, items without duplicated metadata fields, items recently added items across the repository, a community or a collection&lt;br /&gt;
&lt;br /&gt;
These reports have served to prioritize programmatic data cleanup tasks and manual data cleanup tasks.  The reports have served as a progress tracker for data cleanup work and will provide on-going monitoring of the metadata consistency of the repository.&lt;br /&gt;
&lt;br /&gt;
In this presentation, I will provide a demonstration of the tools that were built and discuss the development process that was followed.&lt;br /&gt;
&lt;br /&gt;
== A Hybrid Solution for Improving Single Sign-On to a Proxy Service with Squid and EZproxy through Shibboleth and ExLibris’ Aleph X-Server ==&lt;br /&gt;
&lt;br /&gt;
* Alexander Jerabek, UQAM - Université du Québec à Montréal, jerabek.alexander_j@uqam.ca&lt;br /&gt;
* Minh-Quang Nguyen, UQAM - Université du Québec à Montréal, nguyen.minh-quang@uqam.ca&lt;br /&gt;
&lt;br /&gt;
In this talk, we will describe how we developed and implemented a hybrid solution for improving single sign-on in conjunction with the library’s proxy service. This hybrid solution consists of integrating the disparate elements of EZproxy, the Squid workflow, Shibboleth, and the Aleph X-Server. We will report how this new integrated service improves the user experience. To our knowledge, this new service is unique and has not been implemented anywhere else. We will also present some statistics after approximately one year in production.&lt;br /&gt;
&lt;br /&gt;
See article: http://journal.code4lib.org/articles/7470&lt;br /&gt;
&lt;br /&gt;
== HTML5 Video Now! ==&lt;br /&gt;
&lt;br /&gt;
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Can you use HTML5 video now? Yes.&lt;br /&gt;
&lt;br /&gt;
I'll show you how to get started using HTML5 video, including gotchas, tips, and tricks. Beyond the basics we'll see the power of having video integrated into HTML and the browser. Finally, we'll look at examples that push the limits and show the exciting future of video on the Web.&lt;br /&gt;
&lt;br /&gt;
My experience comes from technical development of an oral history video clips project. I developed the technical aspects of the project, including video processing, server configuration, development of a public site, creation of an administrative interface, and video engagement analytics. Major portions of this work have been open sourced under an MIT license.&lt;br /&gt;
&lt;br /&gt;
== Hybrid Archival Collections Using Blacklight and Hydra ==&lt;br /&gt;
&lt;br /&gt;
* Adam Wead, Rock and Roll Hall of Fame and Museum, awead@rockhall.org&lt;br /&gt;
&lt;br /&gt;
At the Library and Archives of the Rock and Roll Hall of Fame, we use available tools such as Archivists' Toolkit to create EAD finding aids of our collections.  However, managing digital content created from these materials and the born-digital content that is also part of these collections represents a significant challenge.  In my presentation, I will discuss how we solve the problem of our hybrid collections by using Hydra as a digital asset manager and Blacklight as a unified presentation and discovery interface for all our materials.&lt;br /&gt;
&lt;br /&gt;
Our strategy centers around indexing ead xml into Solr as multiple documents: one for each collection, and one for every series, sub-series and item contained within a collection.  For discovery, we use this strategy to leverage item-level searching of archival collections alongside our traditional library content.  For digital collections, we use this same technique to represent a finding aid in Hydra as a set of linked objects using RDF.  New digital items are then linked to these parent objects at the collection and series level.  Once this is done, the items can be exported back out to the Blacklight solr index and the digital content appears along with the rest of the items in the collection.&lt;br /&gt;
&lt;br /&gt;
== Making the Web Accessible through Solid Design ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Cynthia|Cynthia Ng]] from Ryerson University Library &amp;amp; Archives&lt;br /&gt;
&lt;br /&gt;
In libraries, we are always trying our best to be accessible to everyone and we make every effort to do so physically, but what about our websites? Web designers are great at talking about the user experience and how to improve it, but what sometimes gets overlooked is how to make a site more accessible and meet accessibility guidelines. While guidelines are necessary to cover a minimum standard, web accessibility should come from good web design without ‘sacrificing’ features. While it's difficult to make a website fully accessible to everyone, there are easy, practical ways to make a site as accessible as possible.&lt;br /&gt;
&lt;br /&gt;
While the focus will be on websites and meeting the Web Accessibility Guidelines WCAG, the presentation will also touch on how to make custom web interfaces accessible.&lt;br /&gt;
&lt;br /&gt;
== Getting People to What They Need Fast! A Wayfinding Tool to Locate Books &amp;amp; Much More ==&lt;br /&gt;
 &lt;br /&gt;
* Steven Marsden, Ryerson University Library &amp;amp; Archives, steven dot marsden at ryerson dot ca&lt;br /&gt;
* [[User:Cynthia|Cynthia Ng]], Ryerson University Library &amp;amp; Archives&lt;br /&gt;
&lt;br /&gt;
Having a bewildered, lost user in the building or stacks is a common occurrence, but we can help our users find their way through enhanced maps and floor plans.  While not a new concept, these maps are integrated into the user’s flow of information without having to load a special app. The map not only highlights the location, but also provides all the related information with a link back to the detailed item view. During the first stage of the project, it has only be implemented for books (and other physical items), but the 'RULA Finder' is built to help users find just about anything and everything in the library including study rooms, computer labs, and staff. With a simple to use admin interface, it makes it easy for everyone, staff and users. &lt;br /&gt;
&lt;br /&gt;
The application is written in PHP with data stored in a MySQL database. The end-user interface involves jQuery, JSON, and the library's discovery layer (Summon) API.&lt;br /&gt;
&lt;br /&gt;
The presentation will not only cover the technical aspects, but also the implementation and usability findings.&lt;br /&gt;
&lt;br /&gt;
== De-sucking the Library User Experience ==&lt;br /&gt;
 &lt;br /&gt;
* Jeremy Prevost, Northwestern University, j-prevost {AT} northwestern [DOT] edu&lt;br /&gt;
&lt;br /&gt;
Have you ever thought that library vendors purposely create the worst possible user experience they can imagine because they just hate users? Have you ever thought that your own library website feels like it was created by committee rather than for users because, well, it was? I’ll talk about how we used vendor supplied APIs to our ILS and Discovery tool to create an experience for our users that sucks at least a little bit less.&lt;br /&gt;
&lt;br /&gt;
The talk will provide specific examples of how inefficient or confusing vendor supplied solutions are from a user perspective along with our specific streamlined solutions to the same problems. Code examples will be minimal as the focus will be on improving user experience rather than any one code solution of doing that. Examples may include the seemingly simple tasks of renewing a book or requesting an item from another campus library.&lt;br /&gt;
&lt;br /&gt;
== Solr Testing Is Easy with Rspec-Solr Gem ==&lt;br /&gt;
&lt;br /&gt;
* Naomi Dushay, Stanford University, ndushay AT stanford DOT edu&lt;br /&gt;
&lt;br /&gt;
How do you know if &lt;br /&gt;
&lt;br /&gt;
* your idea for &amp;quot;left anchoring&amp;quot; searches actually works?&lt;br /&gt;
* your field analysis for LC call numbers accommodates a suffix between the first and second cutter without breaking the rest of LC call number parsing?&lt;br /&gt;
* tweaking Solr configs to improve, say, Chinese searching, won't break Turkish and Cyrillic?&lt;br /&gt;
* changes to your solrconfig file accomplish what you wanted without breaking anything else?&lt;br /&gt;
&lt;br /&gt;
Avoid the whole app stack when writing Solr acceptance/relevancy/regression tests!  Forget cucumber and capybara.  This gem lets you easily (only 4 short files needed!) write tests like this, passing arbitrary parameters to Solr:&lt;br /&gt;
&lt;br /&gt;
  it &amp;quot;unstemmed author name Zare should precede stemmed variants&amp;quot; do&lt;br /&gt;
    resp = solr_response(author_search_args('Zare').merge({'fl'=&amp;gt;'id,author_person_display', 'facet'=&amp;gt;false}))&lt;br /&gt;
    resp.should include(&amp;quot;author_person_display&amp;quot; =&amp;gt; /\bZare\W/).in_each_of_first(3).documents&lt;br /&gt;
    resp.should_not include(&amp;quot;author_person_display&amp;quot; =&amp;gt; /Zaring/).in_each_of_first(20).documents&lt;br /&gt;
  end&lt;br /&gt;
      &lt;br /&gt;
  it &amp;quot;Cyrillic searching should work:  Восемьсoт семьдесят один день&amp;quot; do&lt;br /&gt;
    resp = solr_resp_doc_ids_only({'q'=&amp;gt;'Восемьсoт семьдесят один день'})&lt;br /&gt;
    resp.should include(&amp;quot;9091779&amp;quot;)&lt;br /&gt;
  end&lt;br /&gt;
   &lt;br /&gt;
  it &amp;quot;q of 'String quartets Parts' and variants should be plausible &amp;quot; do&lt;br /&gt;
    resp = solr_resp_doc_ids_only({'q'=&amp;gt;'String quartets Parts'})&lt;br /&gt;
    resp.should have_at_least(2000).documents&lt;br /&gt;
    resp.should have_the_same_number_of_results_as(solr_resp_doc_ids_only({'q'=&amp;gt;'(String quartets Parts)'}))&lt;br /&gt;
    resp.should have_more_results_than(solr_resp_doc_ids_only({'q'=&amp;gt;'&amp;quot;String quartets Parts&amp;quot;'}))&lt;br /&gt;
  end&lt;br /&gt;
   &lt;br /&gt;
  it &amp;quot;Traditional Chinese chars 三國誌 should get the same results as simplified chars 三国志&amp;quot; do&lt;br /&gt;
    resp = solr_response({'q'=&amp;gt;'三國誌', 'fl'=&amp;gt;'id', 'facet'=&amp;gt;false}) &lt;br /&gt;
    resp.should have_at_least(240).documents&lt;br /&gt;
    resp.should have_the_same_number_of_results_as(solr_resp_doc_ids_only({'q'=&amp;gt;'三国志'})) &lt;br /&gt;
  end&lt;br /&gt;
&lt;br /&gt;
See&lt;br /&gt;
   http://rubydoc.info/github/sul-dlss/rspec-solr/frames&lt;br /&gt;
   https://github.com/sul-dlss/rspec-solr&lt;br /&gt;
&lt;br /&gt;
and our production relevancy/acceptance/regression tests slowly migrating from cucumber to:&lt;br /&gt;
   https://github.com/sul-dlss/sw_index_tests&lt;br /&gt;
&lt;br /&gt;
== Northwestern's Digital Image Library ==&lt;br /&gt;
&lt;br /&gt;
*Mike Stroming, Northwestern University Library, m-stroming AT northwestern DOT edu&lt;br /&gt;
*Edgar Garcia, Northwestern University Library, edgar-garcia AT northwestern DOT edu&lt;br /&gt;
&lt;br /&gt;
At Northwestern University Library, we are about to release a beta version of our Digital Image Library (DIL).  DIL is an implementation of the Hydra technology that provides a Fedora repository solution for discovery of and access to over 100,000 images for staff, students, and scholars. Some important features are:&lt;br /&gt;
&lt;br /&gt;
*Build custom collection of images using drag-and-drop&lt;br /&gt;
*Re-order images within a collection using drag-and-drop&lt;br /&gt;
*Nest collections within other collections&lt;br /&gt;
*Create details/crops of images&lt;br /&gt;
*Zoom, rotate images&lt;br /&gt;
*Upload personal images&lt;br /&gt;
*Retrieve your own uploads and details from a collection&lt;br /&gt;
*Export a collection to a PowerPoint presentation&lt;br /&gt;
*Create a group of users and authorize access to your images&lt;br /&gt;
*Batch edit image metadata&lt;br /&gt;
&lt;br /&gt;
Our presentation will include a demo, explanation of the architecture, and a discussion of the benefits of being a part of the Hydra open-source community.&lt;br /&gt;
&lt;br /&gt;
== Two standards in a software (to say nothing of Normarc) ==&lt;br /&gt;
&lt;br /&gt;
*Zeno Tajoli, CINECA (Italy), z DOT tajoli AT cineca DOT it&lt;br /&gt;
&lt;br /&gt;
With this presentation I want to show how ILS Koha handles the support of three differnt MARC dialects:&lt;br /&gt;
MARC21, Unimarc and Normarc. The main points of the presentation:&lt;br /&gt;
&lt;br /&gt;
*Three MARC at MySQL level&lt;br /&gt;
*Three MARC at API level&lt;br /&gt;
*Three MARC at display&lt;br /&gt;
*Can I add a new format ?&lt;br /&gt;
&lt;br /&gt;
== Future Friendly Web Design for Libraries ==&lt;br /&gt;
&lt;br /&gt;
*[[User:michaelschofield|Michael Schofield]], Alvin Sherman Library, Research, and Information Technology Center, mschofied[dot]nova[dot]edu&lt;br /&gt;
&lt;br /&gt;
Libraries on the web are afterthoughts. Often their design is stymied on one hand by red tape imposed by the larger institution and on the other by an overload of too democratic input from colleagues. Slashed budgets / staff stretched too thin foul-up the R-word (that'd be &amp;quot;redesign&amp;quot;) - but things are getting pretty strange. Notions about the Web (and where it can be accessed) are changing. &lt;br /&gt;
&lt;br /&gt;
So libraries can only avoid refabbing their fixed-width desktop and jQuery Mobile m-dot websites for so long until desktop users evaporate and demand from patrons with web-ready refrigerators becomes deafening. Just when we have largely hopped on the bandwagon and gotten enthusiastic about being online, our users expect a library's site to look and perform great on everything. &lt;br /&gt;
&lt;br /&gt;
Our presence on the web should be built to weather ever-increasing device complexity. To meet users at their point of need, libraries must start thinking Future Friendly.&lt;br /&gt;
&lt;br /&gt;
This overview rehashes the approach and philosophy of library web design, re-orienting it for maximum accessibility and maximum efficiency of design. While just 20 minutes, we'll mull over techniques like mobile-first responsive web design, modular CSS, browser feature detection for progressive enhancement, and lots of nifty tricks.&lt;br /&gt;
&lt;br /&gt;
==BYU's discovery layer service aggregator==&lt;br /&gt;
&lt;br /&gt;
*Curtis	Thacker, Brigham Young University, curtis.thacker AT byu DOT edu&lt;br /&gt;
&lt;br /&gt;
It is clear that libraries will continue to experience rapid change based on the speed of technology. To acknowledge this new reality and to provide rapid response to shifting end user paradigms BYU has developed a custom service aggregator. At first our vendors looked at us a bit funny; however, in the last year they have been astonished with the fluid implementation of new services – here’s the short list:&lt;br /&gt;
&lt;br /&gt;
*filmfinder - a tool for browsing and searching films&lt;br /&gt;
*A custom book recommender service based on checkout data&lt;br /&gt;
*Integrated library services like personell, library hours, study room scheduler and database finder through a custom adwords system.&lt;br /&gt;
*A very geeky and powerful utility used for converting marc XML into primo compliant xml.&lt;br /&gt;
*Embedded floormaps&lt;br /&gt;
*A responsive web design&lt;br /&gt;
*Bing did-you-mean&lt;br /&gt;
*And many more.&lt;br /&gt;
&lt;br /&gt;
I will demo the system, review the archtecture and talk about future plans.&lt;br /&gt;
&lt;br /&gt;
==The Avalon Media System: A Next Generation Hydra Head For Audio and Video Delivery==&lt;br /&gt;
&lt;br /&gt;
* Michael Klein, Senior Software Developer, Northwestern University LIbrary, michael.klein AT northwestern DOT edu&lt;br /&gt;
* Nathan Rogers, Programmer/Analyst, Indiana University, rogersna AT indiana DOT edu&lt;br /&gt;
&lt;br /&gt;
Based on the success of the [http://www.dml.indiana.edu/ Variations] digital music platform, Indiana University and Northwestern University have developed a next generation educational tool for delivering multimedia resources to the classroom. The Avalon Media System (formerly Variations on Video) supports the ingest, media processing, management, and access-controlled delivery of library-managed video and audio collections. To do so, the system draws on several existing, mature, open source technologies:&lt;br /&gt;
&lt;br /&gt;
* The ingest, search, and discovery functionality of the Hydra framework&lt;br /&gt;
* The powerful multimedia workflow management features of Opencast Matterhorn&lt;br /&gt;
* The flexible Engage audio/video player&lt;br /&gt;
* The streaming capabilities of both Red5 Media Server (open source) and Adobe Flash Media Server (proprietary)&lt;br /&gt;
&lt;br /&gt;
Extensive customization options are built into the framework for tailoring the application to the needs of a specific institution.&lt;br /&gt;
&lt;br /&gt;
Our goal is to create an open platform that can be used by other institutions to serve the needs of the academic community. Release 1 is planned for a late February launch with future versions released every couple of months following. For more information visit http://avalonmediasystem.org/ and https://github.com/variations-on-video/hydrant.&lt;br /&gt;
&lt;br /&gt;
== The DH Curation Guide: Building a Community Resource == &lt;br /&gt;
&lt;br /&gt;
*Robin Davis, John Jay College of Criminal Justice, robdavis AT jjay.cuny.edu &lt;br /&gt;
*James Little, University of Illinois Urbana-Champaign, little9 AT illinois.edu  &lt;br /&gt;
&lt;br /&gt;
Data curation for the digital humanities is an emerging area of research and practice. The DH Curation Guide, launched in July 2012, is an educational resource that addresses aspects of humanities data curation in a series of expert-written articles. Each provides a succinct introduction to a topic with annotated lists of useful tools, projects, standards, and good examples of data curation done right. The DH Curation Guide is intended to be a go-to resource for data curation practitioners and learners in libraries, archives, museums, and academic institutions.  &lt;br /&gt;
&lt;br /&gt;
Because it's a growing field, we designed the DH Curation Guide to be a community-driven, living document. We developed a granular commenting system that encourages data curation community members to contribute remarks on articles, article sections, and article paragraphs. Moreover, we built in a way for readers to contribute and annotate resources for other data curation practitioners.  &lt;br /&gt;
&lt;br /&gt;
This talk will address how the DH Curation Guide is currently used and will include a sneak peek at the articles that are in store for the Guide’s future. We will talk about the difficulties and successes of launching a site that encourages community. We are all builders here, so we will also walk through developing the granular commenting/annotation system and the XSLT-powered publication workflow. &lt;br /&gt;
&lt;br /&gt;
== Solr Update == &lt;br /&gt;
&lt;br /&gt;
*Erik Hatcher, LucidWorks, erik.hatcher AT lucidworks.com &lt;br /&gt;
&lt;br /&gt;
Solr is continually improving.  Solr 4 was recently released, bringing dramatic changes in the underlying Lucene library and Solr-level features.  It's tough for us all to keep up with the various versions and capabilities.&lt;br /&gt;
&lt;br /&gt;
This talk will blaze through the highlights of new features and improvements in Solr 4 (and up).  Topics will include: SolrCloud, direct spell checking, surround query parser, and many other features.  We will focus on the features library coders really need to know about.&lt;br /&gt;
&lt;br /&gt;
== Reports for the People == &lt;br /&gt;
&lt;br /&gt;
*Kara Young, Keene State College, NH, kyoung1 at keene.edu&lt;br /&gt;
*Dana Clark, Keene State College, NH, dclark5 at keene.edu&lt;br /&gt;
&lt;br /&gt;
Libraries are increasingly being called upon to provide information on how our programs and services are moving our institutional strategic goals forward.  In support of College and departmental Information Literacy learning outcomes, Mason Library Systems at Keene State College developed an assessment database to record and report assessment activities by Library faculty.  Frustrated by the lack of freely available options for intuitively recording, accounting for, and outputting useful reports on instructional activities, Librarians requested a tool to make capturing and reporting activities (and their lives) easier.  Library Systems was able to respond to this need by working with librarians to identify what information is necessary to capture, where other assessment tools had fallen short, and ultimately by developing an application that supports current reporting imperatives while providing flexibility for future changes.&lt;br /&gt;
&lt;br /&gt;
The result of our efforts was an in-house browser interfaced Assessment Database to improve the process of data collection and analysis.  The application is written in PHP, data stored in a MySQL database, and presented via browser making extensive use of JQuery and JQuery plug-ins for data collection, manipulation, and presentation. &lt;br /&gt;
The presentation will outline the process undertaken to build a successful collaboration with Library faculty from conception to implementation, as well as the technical aspects of our trial-and-error approach. Plus: cool charts and graphs!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2013]]&lt;/div&gt;</summary>
		<author><name>ErikHatcher</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_preconference_proposals&amp;diff=27835</id>
		<title>2013 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_preconference_proposals&amp;diff=27835"/>
				<updated>2012-10-31T19:39:11Z</updated>
		
		<summary type="html">&lt;p&gt;ErikHatcher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Proposals close ''Friday, November 2'' at 5pm PT.&lt;br /&gt;
&lt;br /&gt;
Spaces available: 4+ Rooms&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
=== Talk Title ===&lt;br /&gt;
 &lt;br /&gt;
* Presenter/Leader, affiliation (optional), and email address (mandatory!)&lt;br /&gt;
* Second Presenter/Leader, affiliation, email address, if applicable&lt;br /&gt;
&lt;br /&gt;
Description.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Full Day==&lt;br /&gt;
&lt;br /&gt;
===Drupal4lib Sub-con Barcamp===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
We will attempt to get one of the local Drupal uber-ninjas to do the keynote and give us some guidance.&lt;br /&gt;
&lt;br /&gt;
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or &lt;br /&gt;
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
==Half Day Morning==&lt;br /&gt;
&lt;br /&gt;
=== Open space session ===&lt;br /&gt;
&lt;br /&gt;
* Dan Chudnov, dchud at gwu edu&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If there's interest, we could start with a &amp;quot;welcome to code4lib&amp;quot; introductory session for newcomers.&lt;br /&gt;
&lt;br /&gt;
==Half Day Afternoon==&lt;br /&gt;
=== Data Visualization Hackfest ===&lt;br /&gt;
* 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 &amp;quot;Where Librarians Go To Hack&amp;quot;] 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: &lt;br /&gt;
 - we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.&lt;br /&gt;
 - we'll separate into groups and hack on stuff.&lt;br /&gt;
 - at the end of the day, we'll present our progress.&lt;br /&gt;
&lt;br /&gt;
Not a code hacker?  No worries; all skill sets and backgrounds are valuable! &lt;br /&gt;
&lt;br /&gt;
* Duration: half-day&lt;br /&gt;
* Contact: Chris Beer (cabeer at stanford.edu)&lt;br /&gt;
&lt;br /&gt;
==Half Day Evening==&lt;br /&gt;
&lt;br /&gt;
=== Solr 4 In Depth ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Duration: half-day&lt;br /&gt;
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)&lt;br /&gt;
* Note: I put this under &amp;quot;Half Day Evening&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2013]]&lt;/div&gt;</summary>
		<author><name>ErikHatcher</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_preconference_proposals&amp;diff=27834</id>
		<title>2013 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_preconference_proposals&amp;diff=27834"/>
				<updated>2012-10-31T19:37:52Z</updated>
		
		<summary type="html">&lt;p&gt;ErikHatcher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Proposals close ''Friday, November 2'' at 5pm PT.&lt;br /&gt;
&lt;br /&gt;
Spaces available: 4+ Rooms&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
=== Talk Title ===&lt;br /&gt;
 &lt;br /&gt;
* Presenter/Leader, affiliation (optional), and email address (mandatory!)&lt;br /&gt;
* Second Presenter/Leader, affiliation, email address, if applicable&lt;br /&gt;
&lt;br /&gt;
Description.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Full Day==&lt;br /&gt;
&lt;br /&gt;
===Drupal4lib Sub-con Barcamp===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
We will attempt to get one of the local Drupal uber-ninjas to do the keynote and give us some guidance.&lt;br /&gt;
&lt;br /&gt;
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or &lt;br /&gt;
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
==Half Day Morning==&lt;br /&gt;
&lt;br /&gt;
=== Open space session ===&lt;br /&gt;
&lt;br /&gt;
* Dan Chudnov, dchud at gwu edu&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If there's interest, we could start with a &amp;quot;welcome to code4lib&amp;quot; introductory session for newcomers.&lt;br /&gt;
&lt;br /&gt;
==Half Day Afternoon==&lt;br /&gt;
=== Data Visualization Hackfest ===&lt;br /&gt;
* 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 &amp;quot;Where Librarians Go To Hack&amp;quot;] 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: &lt;br /&gt;
 - we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.&lt;br /&gt;
 - we'll separate into groups and hack on stuff.&lt;br /&gt;
 - at the end of the day, we'll present our progress.&lt;br /&gt;
&lt;br /&gt;
Not a code hacker?  No worries; all skill sets and backgrounds are valuable! &lt;br /&gt;
&lt;br /&gt;
* Duration: half-day&lt;br /&gt;
* Contact: Chris Beer (cabeer at stanford.edu)&lt;br /&gt;
&lt;br /&gt;
==Half Day Evening==&lt;br /&gt;
&lt;br /&gt;
=== Solr 4 In Depth ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Duration: half-day&lt;br /&gt;
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2013]]&lt;/div&gt;</summary>
		<author><name>ErikHatcher</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_talks_proposals&amp;diff=27830</id>
		<title>2013 talks proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_talks_proposals&amp;diff=27830"/>
				<updated>2012-10-31T19:15:31Z</updated>
		
		<summary type="html">&lt;p&gt;ErikHatcher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Deadline for talk submission is ''Friday, November 2'' at 5pm PT. We ask that no changes be made after this point, so that every voter reads the same thing. You can update your description again after voting closes.&lt;br /&gt;
&lt;br /&gt;
Prepared talks are 20 minutes (including setup and questions), and focus on one or more of the following areas:&lt;br /&gt;
* tools (some cool new software, software library or integration platform)&lt;br /&gt;
* specs (how to get the most out of some protocols, or proposals for new ones)&lt;br /&gt;
* challenges (one or more big problems we should collectively address)&lt;br /&gt;
&lt;br /&gt;
The community will vote on proposals using the criteria of:&lt;br /&gt;
* usefulness&lt;br /&gt;
* newness&lt;br /&gt;
* geekiness&lt;br /&gt;
* uniqueness&lt;br /&gt;
* awesomeness&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
== Talk Title ==&lt;br /&gt;
 &lt;br /&gt;
* Speaker's name, affiliation, and email address&lt;br /&gt;
* Second speaker's name, affiliation, email address, if applicable&lt;br /&gt;
&lt;br /&gt;
Abstract of no more than 500 words.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Modernizing VuFind with Zend Framework 2 ==&lt;br /&gt;
&lt;br /&gt;
* Demian Katz, Villanova University, demian DOT katz AT villanova DOT edu&lt;br /&gt;
&lt;br /&gt;
When setting goals for a new major release of VuFind, use of an existing web framework was an important decision to encourage standardization and avoid reinvention of the wheel.  Zend Framework 2 was selected as providing the best balance between the cutting-edge (ZF2 was released in 2012) and stability (ZF1 has a long history and many adopters).  This talk will examine some of the architecture and features of the new framework and discuss how it has been used to improve the VuFind project.&lt;br /&gt;
&lt;br /&gt;
== Did You Really Say That Out Loud?  Tools and Techniques for Safe Public WiFi Computing  ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]], LYRASIS, Peter.Murray@lyrasis.org&lt;br /&gt;
&lt;br /&gt;
Public WiFi networks, even those that have passwords, are nothing more that an old-time [https://en.wikipedia.org/wiki/Party_line_(telephony) party line]: what every you say can be easily heard by anyone nearby.  &lt;br /&gt;
Remember [https://en.wikipedia.org/wiki/Firesheep Firesheep]?  &lt;br /&gt;
It was an extension to Firefox that demonstrated how easy it was to snag session cookies and impersonate someone else.&lt;br /&gt;
So what are you sending out over the airwaves, and what techniques are available to prevent eavesdropping?&lt;br /&gt;
This talk will demonstrate tools and techniques for desktop and mobile operating systems that you should be using right now -- right here at Code4Lib -- to protect your data and your network activity.&lt;br /&gt;
&lt;br /&gt;
== Drupal 8 Preview — Symfony and Twig ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Drupal is a great platform for building web applications. Last year, the core developers decided to adopt the Symfony PHP framework, because it would lay the groundwork for the modernization (and de-PHP4ification) of the Drupal codebase. As I write this, the Symfony ClassLoader and HttpFoundation libraries are committed to Drupal core, with more elements likely before Drupal 8 code freeze.&lt;br /&gt;
&lt;br /&gt;
It seems almost certain that the Twig templating engine will supplant PHPtemplate as the core Drupal template engine. Twig is a powerful, secure theme building tool that removes PHP from the templating system, the result being a very concise and powerful theme layer.&lt;br /&gt;
&lt;br /&gt;
Symfony and Twig have a common creator, Fabien Potencier, who's overall goal is to rid the world of the excesses of PHP 4.&lt;br /&gt;
&lt;br /&gt;
== Neat! But How Do We Do It? - The Real-world Problem of Digitizing Complex Corporate Digital Objects ==&lt;br /&gt;
&lt;br /&gt;
* Matthew Mariner, University of Colorado Denver, Auraria Library, matthew.mariner@ucdenver.edu&lt;br /&gt;
&lt;br /&gt;
Isn't it neat when you discover that you are the steward of dozens of Sanborn Fire Instance Maps, hundreds of issues of a city directory, and thousands of photographs of persons in either aforementioned medium? And it's even cooler when you decide, &amp;quot;Let's digitize these together and make them one big awesome project to support public urban history&amp;quot;?  Unfortunately it's a far more difficult process than one imagines at inception and, sadly, doesn't always come to fruition.  My goal here is to discuss the technological (and philosophical) problems librarians and archivists face when trying to create ultra-rich complex corporate digital projects, or, rather, projects consisting of at least three facets interrelated by theme.  I intend to address these problems by suggesting management solutions, web workarounds, and, perhaps, a philosophy that might help in determining whether to even move forward or not.  Expect a few case studies of &amp;quot;grand ideas crushed by technological limitations&amp;quot; and &amp;quot;projects on the right track&amp;quot; to follow.   &lt;br /&gt;
 &lt;br /&gt;
== ResCarta Tools building a standard format for audio archiving, discovery and display ==&lt;br /&gt;
&lt;br /&gt;
* [[User:sarney|John Sarnowski]], The ResCarta Foundation, john.sarnowski@rescarta.org&lt;br /&gt;
&lt;br /&gt;
The free ResCarta Toolkit has been used by libraries and archives around the world to host city directories, newspapers, and historic photographs and by aerospace companies to search and find millions of engineering documents.  Now the ResCarta team has released audio additions to the toolkit. &lt;br /&gt;
&lt;br /&gt;
Create full text searchable oral histories, news stories, interviews. or build an archive of lectures; all done to Library of Congress standards.  The included transcription editor allows for accurate correction of the data conversion tool’s output.  Build true archives of text, photos and audio.  A single audio file carries the embedded Axml metadata, transcription, and word location information. Checks with the FADGI BWF Metaedit.&lt;br /&gt;
&lt;br /&gt;
ResCarta-Web presents your audio to IE, Chome, Firefox, Safari, and Opera browsers with full playback and word search capability. Display format is OGG!! &lt;br /&gt;
&lt;br /&gt;
You have to see this tool in action.  Twenty minutes from an audio file to transcribed, text-searchable website.  Be there or be L seven (Yeah, I’m that old)   &lt;br /&gt;
&lt;br /&gt;
== Format Designation in MARC Records: A Trip Down the Rabbit-Hole ==&lt;br /&gt;
 &lt;br /&gt;
* Michael Doran, University of Texas at Arlington, doran@uta.edu&lt;br /&gt;
&lt;br /&gt;
This presentation will use a seemingly simple data point, the &amp;quot;format&amp;quot; of the item being described, to illustrate some of the complexities and challenges inherent in the parsing of MARC records.  I will talk about abstract vs. concrete forms; format designation in the Leader, 006, 007, and 008 fixed fields as well as the 245 and 300 variable fields; pseudo-formats; what is mandatory vs. optional in respect to format designation in cataloging practice; and the differences between cataloging theory and practice as observed via format-related data mining of a mid-size academic library collection. &lt;br /&gt;
&lt;br /&gt;
I understand that most of us go to code4lib to hear about the latest sexy technologies.  While MARC isn't sexy, many of the new tools being discussed still need to be populated with data gleaned from MARC records.  MARC format designation has ramifications for search and retrieval, limits, and facets, both in the ILS and further downstream in next generation OPACs and web-scale discovery tools.  Even veteran library coders will learn something from this session. &lt;br /&gt;
&lt;br /&gt;
== Touch Kiosk 2: Piezoelectric Boogaloo ==&lt;br /&gt;
&lt;br /&gt;
* Andreas Orphanides, North Carolina State University Libraries, akorphan@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
At the NCSU Libraries, we provide realtime access to information on library spaces and services through an interactive touchscreen kiosk in our Learning Commons. In the summer of 2012, two years after its initial deployment, I redeveloped the kiosk application from the ground up, with an entirely new codebase and a completely redesigned user interface. The changes I implemented were designed to remedy previously identified shortcomings in the code and the interface design [1], and to enhance overall stability and performance of the application.&lt;br /&gt;
&lt;br /&gt;
In this presentation I will outline my revision process, highlighting the lessons I learned and the practices I implemented in the course of redevelopment. I will highlight the key features of the HTML/Javascript codebase that allow for increased stability, flexibility, and ease of maintenance; and identify the changes to the user interface that resulted from the usability findings I uncovered in my previous research. Finally, I will compare the usage patterns of the new interface to the analysis of the previous implementation to examine the practical effect of the implemented changes.&lt;br /&gt;
&lt;br /&gt;
I will also provide access to a genericized version of the interface code for others to build their own implementations of similar kiosk applications.&lt;br /&gt;
&lt;br /&gt;
[1] http://journal.code4lib.org/articles/5832&lt;br /&gt;
&lt;br /&gt;
== Wayfinding in a Cloud: Location Service for libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Petteri Kivimäki, The National Library of Finland, petteri.kivimaki@helsinki.fi&lt;br /&gt;
&lt;br /&gt;
Searching for books in large libraries can be a difficult task for a novice library user. This paper presents The Location Service, software as a service (SaaS) wayfinding application developed and managed by The National Library of Finland, which is targeted for all the libraries. The service provides additional information and map-based guidance to books and collections by showing their location on a map, and it can be integrated with any library management system, as the integration happens by adding a link to the service in the search interface. The service is being developed continuously based on the feedback received from the users.&lt;br /&gt;
&lt;br /&gt;
The service has two user interfaces: One for the customers and one for the library staff for managing the information related to the locations. The UI for the customers is fully customizable by the libraries, and the customization is done via template files by using the following techniques: HTML, CSS, and Javascript/jQuery. The service supports multiple languages, and the libraries have a full control of the languages, which they want to support in their environment.&lt;br /&gt;
&lt;br /&gt;
The service is written in Java and it uses Spring and Hibernate frameworks. The data is stored in PostgreSQL database, which is shared by all the libraries. They do not possess a direct access to the database, but the service offers an interface, which makes it possible to retrieve XML data over HTTP. Modification of the data via admin UI, however, is restricted, and access on the other libraries’ data is blocked.&lt;br /&gt;
&lt;br /&gt;
== Empowering Collection Owners with Automated Bulk Ingest Tools for DSpace ==&lt;br /&gt;
&lt;br /&gt;
* Terry Brady, Georgetown University, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Library has developed a number of applications to expedite the process of ingesting content into DSpace.&lt;br /&gt;
* Automatically inventory a collection of documents or images to be uploaded&lt;br /&gt;
* Generate a spreadsheet for metadata capture based on the inventory&lt;br /&gt;
* Generate item-level ingest folders, contents files and dublin core metadata for the items to be ingested&lt;br /&gt;
* Validate the contents of ingest folders prior to initiating the ingest to DSpace&lt;br /&gt;
* Present users with a simple, web-based form to initiate the batch ingest process&lt;br /&gt;
&lt;br /&gt;
The applications have eliminated a number of error-prone steps from the ingest workflow and have significantly reduced a number of tedious data editing steps.  These applications have empowered content experts to be in charge of their own collections. &lt;br /&gt;
&lt;br /&gt;
In this presentation, I will provide a demonstration of the tools that were built and discuss the development process that was followed.&lt;br /&gt;
&lt;br /&gt;
== Quality Assurance Reports for DSpace Collections ==&lt;br /&gt;
&lt;br /&gt;
* Terry Brady, Georgetown University, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Library has developed a collection of quality assurance reports to improve the consistency of the metadata in our DSpace collections.  The report infrastructure permits the creation of query snippets to test for possible consistency errors within the repository such as items missing thumbnails, items with multiple thumbnails, items missing a creation date, items containing improperly formatted dates, items without duplicated metadata fields, items recently added items across the repository, a community or a collection&lt;br /&gt;
&lt;br /&gt;
These reports have served to prioritize programmatic data cleanup tasks and manual data cleanup tasks.  The reports have served as a progress tracker for data cleanup work and will provide on-going monitoring of the metadata consistency of the repository.&lt;br /&gt;
&lt;br /&gt;
In this presentation, I will provide a demonstration of the tools that were built and discuss the development process that was followed.&lt;br /&gt;
&lt;br /&gt;
== A Hybrid Solution for Improving Single Sign-On to a Proxy Service with Squid and EZproxy through Shibboleth and ExLibris’ Aleph X-Server ==&lt;br /&gt;
&lt;br /&gt;
* Alexander Jerabek, UQAM - Université du Québec à Montréal, jerabek.alexander_j@uqam.ca&lt;br /&gt;
* Minh-Quang Nguyen, UQAM - Université du Québec à Montréal, nguyen.minh-quang@uqam.ca&lt;br /&gt;
&lt;br /&gt;
In this talk, we will describe how we developed and implemented a hybrid solution for improving single sign-on in conjunction with the library’s proxy service. This hybrid solution consists of integrating the disparate elements of EZproxy, the Squid workflow, Shibboleth, and the Aleph X-Server. We will report how this new integrated service improves the user experience. To our knowledge, this new service is unique and has not been implemented anywhere else. We will also present some statistics after approximately one year in production.&lt;br /&gt;
&lt;br /&gt;
See article: http://journal.code4lib.org/articles/7470&lt;br /&gt;
&lt;br /&gt;
== HTML5 Video Now! ==&lt;br /&gt;
&lt;br /&gt;
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Can you use HTML5 video now? Yes.&lt;br /&gt;
&lt;br /&gt;
I'll show you how to get started using HTML5 video, including gotchas, tips, and tricks. Beyond the basics we'll see the power of having video integrated into HTML and the browser. Finally, we'll look at examples that push the limits and show the exciting future of video on the Web.&lt;br /&gt;
&lt;br /&gt;
My experience comes from technical development of an oral history video clips project. I developed the technical aspects of the project, including video processing, server configuration, development of a public site, creation of an administrative interface, and video engagement analytics. Major portions of this work have been open sourced under an MIT license.&lt;br /&gt;
&lt;br /&gt;
== Hybrid Archival Collections Using Blacklight and Hydra ==&lt;br /&gt;
&lt;br /&gt;
* Adam Wead, Rock and Roll Hall of Fame and Museum, awead@rockhall.org&lt;br /&gt;
&lt;br /&gt;
At the Library and Archives of the Rock and Roll Hall of Fame, we use available tools such as Archivists' Toolkit to create EAD finding aids of our collections.  However, managing digital content created from these materials and the born-digital content that is also part of these collections represents a significant challenge.  In my presentation, I will discuss how we solve the problem of our hybrid collections by using Hydra as a digital asset manager and Blacklight as a unified presentation and discovery interface for all our materials.&lt;br /&gt;
&lt;br /&gt;
Our strategy centers around indexing ead xml into Solr as multiple documents: one for each collection, and one for every series, sub-series and item contained within a collection.  For discovery, we use this strategy to leverage item-level searching of archival collections alongside our traditional library content.  For digital collections, we use this same technique to represent a finding aid in Hydra as a set of linked objects using RDF.  New digital items are then linked to these parent objects at the collection and series level.  Once this is done, the items can be exported back out to the Blacklight solr index and the digital content appears along with the rest of the items in the collection.&lt;br /&gt;
&lt;br /&gt;
== Making the Web Accessible through Solid Design ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Cynthia|Cynthia Ng]] from Ryerson University Library &amp;amp; Archives&lt;br /&gt;
&lt;br /&gt;
In libraries, we are always trying our best to be accessible to everyone and we make every effort to do so physically, but what about our websites? Web designers are great at talking about the user experience and how to improve it, but what sometimes gets overlooked is how to make a site more accessible and meet accessibility guidelines. While guidelines are necessary to cover a minimum standard, web accessibility should come from good web design without ‘sacrificing’ features. While it's difficult to make a website fully accessible to everyone, there are easy, practical ways to make a site as accessible as possible.&lt;br /&gt;
&lt;br /&gt;
While the focus will be on websites and meeting the Web Accessibility Guidelines WCAG, the presentation will also touch on how to make custom web interfaces accessible.&lt;br /&gt;
&lt;br /&gt;
== Getting People to What They Need Fast! A Wayfinding Tool to Locate Books &amp;amp; Much More ==&lt;br /&gt;
 &lt;br /&gt;
* Steven Marsden, Ryerson University Library &amp;amp; Archives, steven dot marsden at ryerson dot ca&lt;br /&gt;
* [[User:Cynthia|Cynthia Ng]], Ryerson University Library &amp;amp; Archives&lt;br /&gt;
&lt;br /&gt;
Having a bewildered, lost user in the building or stacks is a common occurrence, but we can help our users find their way through enhanced maps and floor plans.  While not a new concept, these maps are integrated into the user’s flow of information without having to load a special app. The map not only highlights the location, but also provides all the related information with a link back to the detailed item view. During the first stage of the project, it has only be implemented for books (and other physical items), but the 'RULA Finder' is built to help users find just about anything and everything in the library including study rooms, computer labs, and staff. With a simple to use admin interface, it makes it easy for everyone, staff and users. &lt;br /&gt;
&lt;br /&gt;
The application is written in PHP with data stored in a MySQL database. The end-user interface involves jQuery, JSON, and the library's discovery layer (Summon) API.&lt;br /&gt;
&lt;br /&gt;
The presentation will not only cover the technical aspects, but also the implementation and usability findings.&lt;br /&gt;
&lt;br /&gt;
== De-sucking the Library User Experience ==&lt;br /&gt;
 &lt;br /&gt;
* Jeremy Prevost, Northwestern University, j-prevost {AT} northwestern [DOT] edu&lt;br /&gt;
&lt;br /&gt;
Have you ever thought that library vendors purposely create the worst possible user experience they can imagine because they just hate users? Have you ever thought that your own library website feels like it was created by committee rather than for users because, well, it was? I’ll talk about how we used vendor supplied APIs to our ILS and Discovery tool to create an experience for our users that sucks at least a little bit less.&lt;br /&gt;
&lt;br /&gt;
The talk will provide specific examples of how inefficient or confusing vendor supplied solutions are from a user perspective along with our specific streamlined solutions to the same problems. Code examples will be minimal as the focus will be on improving user experience rather than any one code solution of doing that. Examples may include the seemingly simple tasks of renewing a book or requesting an item from another campus library.&lt;br /&gt;
&lt;br /&gt;
== Solr Testing Is Easy with Rspec-Solr Gem ==&lt;br /&gt;
&lt;br /&gt;
* Naomi Dushay, Stanford University, ndushay AT stanford DOT edu&lt;br /&gt;
&lt;br /&gt;
How do you know if &lt;br /&gt;
&lt;br /&gt;
* your idea for &amp;quot;left anchoring&amp;quot; searches actually works?&lt;br /&gt;
* your field analysis for LC call numbers accommodates a suffix between the first and second cutter without breaking the rest of LC call number parsing?&lt;br /&gt;
* tweaking Solr configs to improve, say, Chinese searching, won't break Turkish and Cyrillic?&lt;br /&gt;
* changes to your solrconfig file accomplish what you wanted without breaking anything else?&lt;br /&gt;
&lt;br /&gt;
Avoid the whole app stack when writing Solr acceptance/relevancy/regression tests!  Forget cucumber and capybara.  This gem lets you easily (only 4 short files needed!) write tests like this, passing arbitrary parameters to Solr:&lt;br /&gt;
&lt;br /&gt;
  it &amp;quot;unstemmed author name Zare should precede stemmed variants&amp;quot; do&lt;br /&gt;
    resp = solr_response(author_search_args('Zare').merge({'fl'=&amp;gt;'id,author_person_display', 'facet'=&amp;gt;false}))&lt;br /&gt;
    resp.should include(&amp;quot;author_person_display&amp;quot; =&amp;gt; /\bZare\W/).in_each_of_first(3).documents&lt;br /&gt;
    resp.should_not include(&amp;quot;author_person_display&amp;quot; =&amp;gt; /Zaring/).in_each_of_first(20).documents&lt;br /&gt;
  end&lt;br /&gt;
      &lt;br /&gt;
  it &amp;quot;Cyrillic searching should work:  Восемьсoт семьдесят один день&amp;quot; do&lt;br /&gt;
    resp = solr_resp_doc_ids_only({'q'=&amp;gt;'Восемьсoт семьдесят один день'})&lt;br /&gt;
    resp.should include(&amp;quot;9091779&amp;quot;)&lt;br /&gt;
  end&lt;br /&gt;
   &lt;br /&gt;
  it &amp;quot;q of 'String quartets Parts' and variants should be plausible &amp;quot; do&lt;br /&gt;
    resp = solr_resp_doc_ids_only({'q'=&amp;gt;'String quartets Parts'})&lt;br /&gt;
    resp.should have_at_least(2000).documents&lt;br /&gt;
    resp.should have_the_same_number_of_results_as(solr_resp_doc_ids_only({'q'=&amp;gt;'(String quartets Parts)'}))&lt;br /&gt;
    resp.should have_more_results_than(solr_resp_doc_ids_only({'q'=&amp;gt;'&amp;quot;String quartets Parts&amp;quot;'}))&lt;br /&gt;
  end&lt;br /&gt;
   &lt;br /&gt;
  it &amp;quot;Traditional Chinese chars 三國誌 should get the same results as simplified chars 三国志&amp;quot; do&lt;br /&gt;
    resp = solr_response({'q'=&amp;gt;'三國誌', 'fl'=&amp;gt;'id', 'facet'=&amp;gt;false}) &lt;br /&gt;
    resp.should have_at_least(240).documents&lt;br /&gt;
    resp.should have_the_same_number_of_results_as(solr_resp_doc_ids_only({'q'=&amp;gt;'三国志'})) &lt;br /&gt;
  end&lt;br /&gt;
&lt;br /&gt;
See&lt;br /&gt;
   http://rubydoc.info/github/sul-dlss/rspec-solr/frames&lt;br /&gt;
   https://github.com/sul-dlss/rspec-solr&lt;br /&gt;
&lt;br /&gt;
and our production relevancy/acceptance/regression tests slowly migrating from cucumber to:&lt;br /&gt;
   https://github.com/sul-dlss/sw_index_tests&lt;br /&gt;
&lt;br /&gt;
== Northwestern's Digital Image Library ==&lt;br /&gt;
&lt;br /&gt;
*Mike Stroming, Northwestern University Library, m-stroming AT northwestern DOT edu&lt;br /&gt;
*Edgar Garcia, Northwestern University Library, edgar-garcia AT northwestern DOT edu&lt;br /&gt;
&lt;br /&gt;
At Northwestern University Library, we are about to release a beta version of our Digital Image Library (DIL).  DIL is an implementation of the Hydra technology that provides a Fedora repository solution for discovery of and access to over 100,000 images for staff, students, and scholars. Some important features are:&lt;br /&gt;
&lt;br /&gt;
*Build custom collection of images using drag-and-drop&lt;br /&gt;
*Re-order images within a collection using drag-and-drop&lt;br /&gt;
*Nest collections within other collections&lt;br /&gt;
*Create details/crops of images&lt;br /&gt;
*Zoom, rotate images&lt;br /&gt;
*Upload personal images&lt;br /&gt;
*Retrieve your own uploads and details from a collection&lt;br /&gt;
*Export a collection to a PowerPoint presentation&lt;br /&gt;
*Create a group of users and authorize access to your images&lt;br /&gt;
*Batch edit image metadata&lt;br /&gt;
&lt;br /&gt;
Our presentation will include a demo, explanation of the architecture, and a discussion of the benefits of being a part of the Hydra open-source community.&lt;br /&gt;
&lt;br /&gt;
== Two standards in a software (to say nothing of Normarc) ==&lt;br /&gt;
&lt;br /&gt;
*Zeno Tajoli, CINECA (Italy), z DOT tajoli AT cineca DOT it&lt;br /&gt;
&lt;br /&gt;
With this presentation I want to show how ILS Koha handles the support of three differnt MARC dialects:&lt;br /&gt;
MARC21, Unimarc and Normarc. The main points of the presentation:&lt;br /&gt;
&lt;br /&gt;
*Three MARC at MySQL level&lt;br /&gt;
*Three MARC at API level&lt;br /&gt;
*Three MARC at display&lt;br /&gt;
*Can I add a new format ?&lt;br /&gt;
&lt;br /&gt;
== Future Friendly Web Design for Libraries ==&lt;br /&gt;
&lt;br /&gt;
*[[User:michaelschofield|Michael Schofield]], Alvin Sherman Library, Research, and Information Technology Center, mschofied[dot]nova[dot]edu&lt;br /&gt;
&lt;br /&gt;
Libraries on the web are afterthoughts. Often their design is stymied on one hand by red tape imposed by the larger institution and on the other by an overload of too democratic input from colleagues. Slashed budgets / staff stretched too thin foul-up the R-word (that'd be &amp;quot;redesign&amp;quot;) - but things are getting pretty strange. Notions about the Web (and where it can be accessed) are changing. &lt;br /&gt;
&lt;br /&gt;
So libraries can only avoid refabbing their fixed-width desktop and jQuery Mobile m-dot websites for so long until desktop users evaporate and demand from patrons with web-ready refrigerators becomes deafening. Just when we have largely hopped on the bandwagon and gotten enthusiastic about being online, our users expect a library's site to look and perform great on everything. &lt;br /&gt;
&lt;br /&gt;
Our presence on the web should be built to weather ever-increasing device complexity. To meet users at their point of need, libraries must start thinking Future Friendly.&lt;br /&gt;
&lt;br /&gt;
This overview rehashes the approach and philosophy of library web design, re-orienting it for maximum accessibility and maximum efficiency of design. While just 20 minutes, we'll mull over techniques like mobile-first responsive web design, modular CSS, browser feature detection for progressive enhancement, and lots of nifty tricks.&lt;br /&gt;
&lt;br /&gt;
==BYU's discovery layer service aggregator==&lt;br /&gt;
&lt;br /&gt;
*Curtis	Thacker, Brigham Young University, curtis.thacker AT byu DOT edu&lt;br /&gt;
&lt;br /&gt;
It is clear that libraries will continue to experience rapid change based on the speed of technology. To acknowledge this new reality and to provide rapid response to shifting end user paradigms BYU has developed a custom service aggregator. At first our vendors looked at us a bit funny; however, in the last year they have been astonished with the fluid implementation of new services – here’s the short list:&lt;br /&gt;
&lt;br /&gt;
*filmfinder - a tool for browsing and searching films&lt;br /&gt;
*A custom book recommender service based on checkout data&lt;br /&gt;
*Integrated library services like personell, library hours, study room scheduler and database finder through a custom adwords system.&lt;br /&gt;
*A very geeky and powerful utility used for converting marc XML into primo compliant xml.&lt;br /&gt;
*Embedded floormaps&lt;br /&gt;
*A responsive web design&lt;br /&gt;
*Bing did-you-mean&lt;br /&gt;
*And many more.&lt;br /&gt;
&lt;br /&gt;
I will demo the system, review the archtecture and talk about future plans.&lt;br /&gt;
&lt;br /&gt;
==The Avalon Meda System: A Next Generation Hydra Head For Audio and Video Delivery==&lt;br /&gt;
&lt;br /&gt;
* Michael Klein, Senior Software Developer, Northwestern University LIbrary, michael.klein AT northwestern DOT edu&lt;br /&gt;
* Nathan Rogers, Programmer/Analyst, Indiana University, rogersna AT indiana DOT edu&lt;br /&gt;
&lt;br /&gt;
Based on the success of the [http://www.dml.indiana.edu/ Variations] digital music platform, Indiana University and Northwestern University have developed a next generation educational tool for delivering multimedia resources to the classroom. The Avalon Media System (formerly Variations on Video) supports the ingest, media processing, management, and access-controlled delivery of library-managed video and audio collections. To do so, the system draws on several existing, mature, open source technologies:&lt;br /&gt;
&lt;br /&gt;
* The ingest, search, and discovery functionality of the Hydra framework&lt;br /&gt;
* The powerful multimedia workflow management features of Opencast Matterhorn&lt;br /&gt;
* The flexible Engage audio/video player&lt;br /&gt;
* The streaming capabilities of both Red5 Media Server (open source) and Adobe Flash Media Server (proprietary)&lt;br /&gt;
&lt;br /&gt;
Extensive customization options are built into the framework for tailoring the application to the needs of a specific institution.&lt;br /&gt;
&lt;br /&gt;
Our goal is to create an open platform that can be used by other institutions to serve the needs of the academic community. Release 1 is planned for a late February launch with future versions released every couple of months following. For more information visit http://avalonmediasystem.org/ and https://github.com/variations-on-video/hydrant.&lt;br /&gt;
&lt;br /&gt;
== The DH Curation Guide: Building a Community Resource == &lt;br /&gt;
&lt;br /&gt;
*Robin Davis, John Jay College of Criminal Justice, robdavis AT jjay.cuny.edu &lt;br /&gt;
*James Little, University of Illinois Urbana-Champaign, little9 AT illinois.edu  &lt;br /&gt;
&lt;br /&gt;
Data curation for the digital humanities is an emerging area of research and practice. The DH Curation Guide, launched in July 2012, is an educational resource that addresses aspects of humanities data curation in a series of expert-written articles. Each provides a succinct introduction to a topic with annotated lists of useful tools, projects, standards, and good examples of data curation done right. The DH Curation Guide is intended to be a go-to resource for data curation practitioners and learners in libraries, archives, museums, and academic institutions.  &lt;br /&gt;
&lt;br /&gt;
Because it's a growing field, we designed the DH Curation Guide to be a community-driven, living document. We developed a granular commenting system that encourages data curation community members to contribute remarks on articles, article sections, and article paragraphs. Moreover, we built in a way for readers to contribute and annotate resources for other data curation practitioners.  &lt;br /&gt;
&lt;br /&gt;
This talk will address how the DH Curation Guide is currently used and will include a sneak peek at the articles that are in store for the Guide’s future. We will talk about the difficulties and successes of launching a site that encourages community. We are all builders here, so we will also walk through developing the granular commenting/annotation system and the XSLT-powered publication workflow. &lt;br /&gt;
&lt;br /&gt;
== Solr Update == &lt;br /&gt;
&lt;br /&gt;
*Erik Hatcher, LucidWorks, erik.hatcher AT lucidworks.com &lt;br /&gt;
&lt;br /&gt;
Solr is continually improving.  Solr 4 was recently released, bringing dramatic changes in the underlying Lucene library and Solr-level features.  It's tough for us all to keep up with the various versions and capabilities.&lt;br /&gt;
&lt;br /&gt;
This talk will blaze through the highlights of new features and improvements in Solr 4 (and up).  Topics will include: SolrCloud, direct spell checking, surround query parser, and many other features.  We will focus on the features the library coders really needs to know about.&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2013]]&lt;/div&gt;</summary>
		<author><name>ErikHatcher</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_preconference_proposals&amp;diff=10732</id>
		<title>2012 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_preconference_proposals&amp;diff=10732"/>
				<updated>2012-02-02T00:11:48Z</updated>
		
		<summary type="html">&lt;p&gt;ErikHatcher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Proposals for 2012 Code4LibCon Preconferences=&lt;br /&gt;
Proposals closed Sunday, November 20, 2011, so we can finalize the list and add them to registration! (The deadline for preconference proposals has passed.)&lt;br /&gt;
&lt;br /&gt;
Spaces available: main meeting room (max 275) + 5 breakout rooms (max 30-50). &lt;br /&gt;
&lt;br /&gt;
'''Please include a &amp;quot;Contact/Responsible Individual&amp;quot; name and email address so we know who is willing to put on the proposed precon.&lt;br /&gt;
'''&lt;br /&gt;
==Full Day==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Developing applications using REST web services ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Come ready to learn and code!&lt;br /&gt;
&lt;br /&gt;
Presenter: Karen Coombs - coombsk at oclc dot org&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
*Sam Kome&lt;br /&gt;
*Ray Schwartz (schwartzr2@wpunj.edu)&lt;br /&gt;
*Jim Robinson&lt;br /&gt;
*David Bucknum&lt;br /&gt;
*Jean Rainwater&lt;br /&gt;
*Joshua Gomez&lt;br /&gt;
*Andy Kohler&lt;br /&gt;
*Michael North&lt;br /&gt;
* Tom Keays (keaysht at lemoyne dot edu)&lt;br /&gt;
*Charlie Morris&lt;br /&gt;
*Michael Lindsey&lt;br /&gt;
* Kåre Fiedler Christiansen (morning only)&lt;br /&gt;
* Jørn Thøgersen&lt;br /&gt;
* Michael Poltorak Nielsen&lt;br /&gt;
* Dre&lt;br /&gt;
* Andrew Darby&lt;br /&gt;
* Timothy Clarke (tclarke@muhlenberg.edu)&lt;br /&gt;
* Keith Folsom&lt;br /&gt;
* Rebecca Jones&lt;br /&gt;
* Michael Doran (doran@uta.edu)&lt;br /&gt;
* Ray Henry (ray dot henry at pcc dot edu)&lt;br /&gt;
* Stephanie Collett&lt;br /&gt;
* Bohyun Kim&lt;br /&gt;
* Matt Connolly&lt;br /&gt;
* Cynthia Ng&lt;br /&gt;
* Justin Littman&lt;br /&gt;
&lt;br /&gt;
==Half Day Morning==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Linkfest ===&lt;br /&gt;
&lt;br /&gt;
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!&lt;br /&gt;
&lt;br /&gt;
If you need an &amp;quot;intro to linked data&amp;quot; we can prep a good list of readings/talks to review before you come.  But please come ready to link!&lt;br /&gt;
&lt;br /&gt;
Organizer type person:  Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
* Becky Yoose&lt;br /&gt;
* Tom Johnson&lt;br /&gt;
* Ed Summers&lt;br /&gt;
* bernardo gomez ( bgomez at emory dot edu )&lt;br /&gt;
* William Gunn&lt;br /&gt;
* Jason Ronallo&lt;br /&gt;
* Keri Thompson&lt;br /&gt;
* David Lacy&lt;br /&gt;
* Corey A Harper&lt;br /&gt;
* Matt Phillips (mphillips@law.harvard.edu)&lt;br /&gt;
* Declan Fleming&lt;br /&gt;
* Shaun Ellis (shaune@princeton.edu)&lt;br /&gt;
* Wendy Robertson&lt;br /&gt;
* Joel Richard (richardjm AT si DOT edu)&lt;br /&gt;
* Devon Smith&lt;br /&gt;
* Ron Peterson (ronp@udel.edu0&lt;br /&gt;
* Scott Hanrath (shanrath AT ku DOT edu)&lt;br /&gt;
* Jason Stirnaman (jstirnaman AT kumc DOT edu)&lt;br /&gt;
* Sean Chen&lt;br /&gt;
* Laura Smart&lt;br /&gt;
* Tommy Ingulfsen&lt;br /&gt;
&lt;br /&gt;
=== What's New in Solr ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.  &lt;br /&gt;
&lt;br /&gt;
Presenter: Erik Hatcher - erik . hatcher @ lucidimagination dot com (remotely calling in and/or via IRC)&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
* &amp;quot;Gabriel Farrell&amp;quot; &amp;lt;gsf24@drexel.edu&amp;gt;&lt;br /&gt;
* &amp;quot;Erik Hetzner&amp;quot; &amp;lt;erik.hetzner AT ucop BORK edu&amp;gt;&lt;br /&gt;
* &amp;quot;Kevin S. Clarke&amp;quot; &amp;lt;ksclarke@gmail&amp;gt;&lt;br /&gt;
* &amp;quot;Michael B. Klein&amp;quot; &amp;lt;mbklein@gmail&amp;gt;&lt;br /&gt;
* Demian Katz (demian DOT katz AT villanova DOT edu)&lt;br /&gt;
* &amp;quot;Mark Mounts&amp;quot; &amp;lt;mark.mounts@dartmouth.edu&amp;gt;&lt;br /&gt;
* Anoop Atre ~ anoop.atre AT mnsu . edu&lt;br /&gt;
* David Isaak &amp;lt;david.isaak@kpchr.org&amp;gt;&lt;br /&gt;
* John Pillans &amp;lt;jpillan@indiana.edu&amp;gt;&lt;br /&gt;
* John Wynstra (john.wynstra@uni.edu)&lt;br /&gt;
* mark a. matienzo (mark at matienzo dot oh are gee)&lt;br /&gt;
* Sepehr Mavedati (sepehr DOT mavedati AT utoronto DOT ca)&lt;br /&gt;
* Mads Villadsen&lt;br /&gt;
* Jonathan Rochkind&lt;br /&gt;
* Shahin Sahebi (shahin.ezzatsahebi at utoronto dot ca)&lt;br /&gt;
* Naomi Dushay (ndushay at stanford dot edu)&lt;br /&gt;
* Jeremy Nelson&lt;br /&gt;
* Kirk Hess &amp;lt;kirkhess@illinois.edu&amp;gt;&lt;br /&gt;
* Gary Thompson&lt;br /&gt;
* Larry Baerveldt &amp;lt;lrbaerveldt@gmail.com&amp;gt;&lt;br /&gt;
* Dennis Schafroth &amp;lt;dennis @ indexdata.com&amp;gt;&lt;br /&gt;
* Bobbi Fox &amp;lt;bobbi_fox at harvard dot edu&amp;gt;&lt;br /&gt;
* Ed Fugikawa &amp;lt;ed at coalliance dot org&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Knocking Down Silos: Tools and Approaches for Simplifying Discovery ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Speakers/Facilitators will be:&lt;br /&gt;
 - Thom Cox - Manager of Library Information Technology Services - Tufts University&lt;br /&gt;
 - Ken Varnum – Web Systems Manager - University of Michigan Libraries&lt;br /&gt;
 - Stephen Westman – Analyst Programmer, Emerging Technologies and Services - Oregon State University Libraries &lt;br /&gt;
&lt;br /&gt;
Contact:  Margaret Mellinger - margaret dot mellinger at oregonstate dot edu&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
*David Uspal (david DOT uspal AT villanova DOT edu)&lt;br /&gt;
*Tammy Allgood Wolf&lt;br /&gt;
*Wayne Schneider&lt;br /&gt;
*Laney McGlohon&lt;br /&gt;
*Andrea Schurr (Andrea-Schurr AT utc DOT edu)&lt;br /&gt;
&lt;br /&gt;
==Half Day Afternoon==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Git -r done === &lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Coordinator:  &amp;lt;del&amp;gt;Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com&amp;lt;/del&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Coordinator Stand-In: Michael B. Klein, Stanford University Libraries, @mbklein or mbklein at stanford.edu&lt;br /&gt;
&lt;br /&gt;
Helper: Cary Gordon, Cherry Hill Company, @highermath / cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
* Patrick Berry (pberry@csuchico.edu)&lt;br /&gt;
* Chris Sharp (csharp@georgialibraries.org)&lt;br /&gt;
* Matt Critchlow (mcritchlow@ucsd.edu)&lt;br /&gt;
* Peter Murray (Peter.Murray@lyrasis.org)&lt;br /&gt;
* Margaret Heller (mheller@dom.edu)&lt;br /&gt;
* Kevin S. Clarke (ksclarke@gmail)&lt;br /&gt;
* Michael B. Klein (mbklein@gmail)&lt;br /&gt;
* Demian Katz (demian DOT katz AT villanova DOT edu)&lt;br /&gt;
* Benjamin Shum (bshum@biblio.org)&lt;br /&gt;
* Sibyl Schaefer (sschaefer@rockarch.org)&lt;br /&gt;
* Tammy Allgood Wolf (tammy.allgood@asu.edu)&lt;br /&gt;
* Chad Nelson (cnelson17 AT gsu DOT edu)&lt;br /&gt;
* Lisa Kurt (lkurt@unr.edu)&lt;br /&gt;
* Matt Phillips (mphillips@law.harvard.edu)&lt;br /&gt;
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)&lt;br /&gt;
* John Wynstra (john.wynstra@uni.edu)&lt;br /&gt;
* Declan Fleming&lt;br /&gt;
* Shaun Ellis (shaune@princeton.edu)&lt;br /&gt;
* Mads Villadsen&lt;br /&gt;
* Kåre Fiedler Christiansen&lt;br /&gt;
* Shahin Sahebi (shahin.ezzatsahebi@utoronto.ca)&lt;br /&gt;
* Devon Smith&lt;br /&gt;
* Jeremy Nelson&lt;br /&gt;
* Stephanie Collett&lt;br /&gt;
* Ron Peterson (ronp@udel.edu)&lt;br /&gt;
* Gary Thompson&lt;br /&gt;
* Brian McBride (brian.mcbride at utah.edu)&lt;br /&gt;
* Jacob Reed (jacob.reed at utah.edu)&lt;br /&gt;
* Bohyun Kim (bohyun.kim at fiu.edu)&lt;br /&gt;
* Larry Baerveldt &amp;lt;lrbaerveldt@gmail.com&amp;gt;&lt;br /&gt;
* Wayne Schneider&lt;br /&gt;
* Matt Connolly&lt;br /&gt;
* ernesto valencia&lt;br /&gt;
* Ed Fugikawa &amp;lt;ed at coalliance dot org&amp;gt;&lt;br /&gt;
* Andrea Schurr (Andrea-Schurr at utc dot edu)&lt;br /&gt;
&lt;br /&gt;
=== Blacklight ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Presenters: Jessie Keck, Stanford University - jkeck at stanford dot edu | Molly Pickral, University of Virginia - mpc3c at virginia dot edu&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
* bernardo gomez ( bgomez at emory dot edu )&lt;br /&gt;
* Mark Mounts &amp;lt;mark.mounts@dartmouth.edu&amp;gt;&lt;br /&gt;
* Sibyl Schaefer (sschaefer@rockarch.org)&lt;br /&gt;
* John Pillans (jpillan@indiana.edu)&lt;br /&gt;
* Mang Sun (mang.dot sun at rice dot edu)&lt;br /&gt;
* Emily Lynema (emily_lynema at ncsu dot edu)&lt;br /&gt;
* mark a. matienzo (mark at matienzo dot oh are gee)&lt;br /&gt;
* Daniel Lovins (daniel dot lovins at nyu dot edu)&lt;br /&gt;
* Jonathan Rochkind&lt;br /&gt;
* Keith Folsom&lt;br /&gt;
* Kirk Hess &amp;lt;kirkhess@illinois.edu&amp;gt;&lt;br /&gt;
* Jason Stirnaman (jstirnaman AT kumc DOT edu)&lt;br /&gt;
* David Drexler &amp;lt;ddrexler@eou.edu&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== DACS and EAD Overview ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Presenter:  Doris Munson, Eastern Washington University, dmunson at ewu dot edu&lt;br /&gt;
(please feel free to contact me if you are interested in being a co-presenter)&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
* Francis Kayiwa ( kayiwa@ YouEyeSee dot edu )&lt;br /&gt;
* Carmen Mitchell (carmenmitchell at gmail dot com)&lt;br /&gt;
&lt;br /&gt;
=== [[Digging into metadata: context, code, and collaboration]] ===&lt;br /&gt;
&lt;br /&gt;
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 &amp;amp; metadata community take to help improve the quality of this data?  What tools &amp;amp; techniques could help?  Rules have evolved over time leaving dirty legacy data.  Systems have impacted--and will continue to impact--data structure &amp;amp; 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.   &lt;br /&gt;
&lt;br /&gt;
Person Herder: Becky Yoose, Grinnell College, yoosebec at grinnell dot edu&lt;br /&gt;
&lt;br /&gt;
Collaborators/Facilitators: Corey Harper, New York University - corey dot harper at nyu dot edu | Shana L. McDanold, University of Pennsylvania - 	&lt;br /&gt;
mcdanold at pobox dot upenn dot edu  | Laura Smart, Caltech - laura at library dot caltech dot edu&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
* Peter Green (pmgreen@princeton.edu)&lt;br /&gt;
* David Isaak (david.isaak@kpchr.org)&lt;br /&gt;
* Alex Rolfe (arolfe@georgefox.edu)&lt;br /&gt;
* mark a. matienzo (mark at matienzo dot oh are gee)&lt;br /&gt;
* Sarah Johnston (johnsts@stolaf.edu)&lt;br /&gt;
* Derek Merleaux (derek@merleaux d0t net)&lt;br /&gt;
* Adam Wead (awead {at} rockhall d.t 0 R G)&lt;br /&gt;
* Tania Fersenheim (tania dot fersenheim at gmail) (I'm only a maybe because I may have a conflict in this time slot)&lt;br /&gt;
* Robin Dean (robin at coalliance dot org)&lt;br /&gt;
&lt;br /&gt;
=== &amp;quot;Geo&amp;quot; ===&lt;br /&gt;
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 &amp;quot;geobrowse,&amp;quot; a section discovery of objects via &amp;quot;geosearch,&amp;quot; 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.  &lt;br /&gt;
&lt;br /&gt;
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&lt;br /&gt;
(please feel free to contact Tim if you are interested in being a co-presenter)&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
* &amp;quot;Gabriel Farrell&amp;quot; &amp;lt;gsf24@drexel.edu&amp;gt;&lt;br /&gt;
* Anoop Atre ~ anoop.atre AT mnsu . edu&lt;br /&gt;
* Chad Nelson (cnelson17 AT gsu DOT edu)&lt;br /&gt;
* Jason Casden (jmcasden AT ncsu DOT edu&lt;br /&gt;
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)&lt;br /&gt;
* Sepehr Mavedati (sepehr DOT mavedati AT utoronto DOT ca)&lt;br /&gt;
* Michael Poltorak Nielsen&lt;br /&gt;
* Wendy Robertson&lt;br /&gt;
* Joel Richard (richardjm AT si DOT edu)&lt;br /&gt;
* Jonathan Rochkind&lt;br /&gt;
* Naomi Dushay (ndushay at stanford dot edu)&lt;br /&gt;
* Scott Hanrath (shanrath AT ku DOT edu)&lt;br /&gt;
* Aaron Collier (acollier AT csufresno DOT edu)&lt;br /&gt;
* David Lacy (david DOT lacy AT villanova DOT edu)&lt;br /&gt;
* Jen Weintraub (jweintraub AT library dot ucla dot edu)&lt;br /&gt;
* Sean Chen&lt;br /&gt;
* Bobbi Fox (bobbi_fox AT harvard dot edu)&lt;br /&gt;
&lt;br /&gt;
== Half-day Evening ==&lt;br /&gt;
&lt;br /&gt;
=== Microsoft Campus Visit ===&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
1. Layerscape -[http://communities.worldwidetelescope.org/]&lt;br /&gt;
&lt;br /&gt;
2. ChronoZoom - [http://research.microsoft.com/chronozoom/]&lt;br /&gt;
&lt;br /&gt;
3. F# - [http://www.tryfsharp.org]&lt;br /&gt;
&lt;br /&gt;
4. Microsoft Academic Search - [http://academic.research.microsoft.com]&lt;br /&gt;
&lt;br /&gt;
5. Microsoft Audio Visual Indexing System - [http://research.microsoft.com/mavis] &lt;br /&gt;
&lt;br /&gt;
Space is limited, so reserve your seat today  Email Alex at the address below.    &lt;br /&gt;
&lt;br /&gt;
Coordinator: Alex Wade, Microsoft Research, awade at microsoft dot com &lt;br /&gt;
&lt;br /&gt;
Presenters: Behrooz Chitsaz; Rob Fatland; Christophe Poulain; Michael Zyskowski &lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending (Registration closed! We are now at capacity.)   ====&lt;br /&gt;
* Declan Fleming&lt;br /&gt;
* Matt Critchlow&lt;br /&gt;
* Tom Keays (keaysht at lemoyne dot edu)&lt;br /&gt;
* mark a. matienzo (mark at matienzo dot oh are gee)&lt;br /&gt;
* Mark Mounts &amp;lt;mark.mounts@dartmouth.edu&amp;gt;&lt;br /&gt;
* Kyle Banerjee &amp;lt;banerjek@uoregon.edu&amp;gt;&lt;br /&gt;
* Evviva Weinraub&lt;br /&gt;
* Emily Lynema &amp;lt;emily_lynema at ncsu dot edu&amp;gt;&lt;br /&gt;
* Jason Casden &amp;lt;jmcasden AT ncsu DOT edu&amp;gt;&lt;br /&gt;
* Daniel Lovins &amp;lt;daniel.lovins@nyu.edu&amp;gt;&lt;br /&gt;
* Cynthia Ng&lt;br /&gt;
* &amp;quot;Gabriel Farrell&amp;quot; &amp;lt;gsf24@drexel.edu&amp;gt;&lt;br /&gt;
* Shaun Ellis (shaune AT princeton DOT edu)&lt;br /&gt;
* Derek Merleaux (derek@merleaux d0t net)&lt;br /&gt;
* Mads Villadsen&lt;br /&gt;
* Kåre Fiedler Christiansen&lt;br /&gt;
* Jørn Thøgersen&lt;br /&gt;
* Michael Poltorak Nielsen&lt;br /&gt;
* Dileshni Jayasinghe&lt;br /&gt;
* Matt Phillips (mphillips@law.harvard.edu)&lt;br /&gt;
* Wendy Robertson&lt;br /&gt;
* Shahin Sahebi&lt;br /&gt;
* Matt Connolly &amp;lt;mjc12 AT cornell dot edu&amp;gt;&lt;br /&gt;
* Jeremy Nelson&lt;br /&gt;
* Naomi Dushay (ndushay at stanford dot edu)&lt;br /&gt;
* Dre&lt;br /&gt;
* Ken Varnum (varnum umich edu)&lt;br /&gt;
* Andrew Darby (agdarby at miami dot edu)&lt;br /&gt;
* David Uspal (david DOT uspal AT villanova DOT edu)&lt;br /&gt;
* REGISTRATION IS NOW CLOSED&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>ErikHatcher</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_preconference_proposals&amp;diff=9435</id>
		<title>2012 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_preconference_proposals&amp;diff=9435"/>
				<updated>2011-10-07T18:49:50Z</updated>
		
		<summary type="html">&lt;p&gt;ErikHatcher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Proposals for 2012 Code4LibCon Preconferences=&lt;br /&gt;
Proposals will close Sunday, November 20 so we can finalize the list and add them to registration!&lt;br /&gt;
&lt;br /&gt;
Spaces available: main meeting room (max 275) + 5 breakout rooms (max 30-50). &lt;br /&gt;
&lt;br /&gt;
'''Please include a &amp;quot;Contact/Responsible Individual&amp;quot; name and email address so we know who is willing to put on the proposed precon.&lt;br /&gt;
'''&lt;br /&gt;
==Full Day==&lt;br /&gt;
&lt;br /&gt;
==Half Day Morning==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Linkfest ===&lt;br /&gt;
&lt;br /&gt;
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!&lt;br /&gt;
&lt;br /&gt;
If you need an &amp;quot;intro to linked data&amp;quot; we can prep a good list of readings/talks to review before you come.  But please come ready to link!&lt;br /&gt;
&lt;br /&gt;
Organizer type person:  Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu&lt;br /&gt;
&lt;br /&gt;
=== What's New in Solr ===&lt;br /&gt;
&lt;br /&gt;
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.  &lt;br /&gt;
&lt;br /&gt;
Presenter: Erik Hatcher - erik . hatcher @ lucidimagination dot com&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Half Day Afternoon==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Git -r done === &lt;br /&gt;
&lt;br /&gt;
A session to cover all things Git, everyone's favourite 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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Coordinator:  Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>ErikHatcher</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=C4L2011_rideshare&amp;diff=6918</id>
		<title>C4L2011 rideshare</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=C4L2011_rideshare&amp;diff=6918"/>
				<updated>2011-01-24T16:28:00Z</updated>
		
		<summary type="html">&lt;p&gt;ErikHatcher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;See also [http://bit.ly/hftKKD Google Map]&lt;br /&gt;
&lt;br /&gt;
=== Indianapolis International Airport ===&lt;br /&gt;
&lt;br /&gt;
'''Arrivals'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; class=&amp;quot;sortable&amp;quot; &lt;br /&gt;
|- style=&amp;quot;text-align: left;&amp;quot;&lt;br /&gt;
! Name !! Flight Arriving  !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?&lt;br /&gt;
|-&lt;br /&gt;
| [mailto:andrew.nagy@serialssolutions.com Andrew Nagy] || 2011-02-07 9:30 (Monday; 9:30am) || Yes || No || No || Me || No || 1. 2. 3. &lt;br /&gt;
|-&lt;br /&gt;
| [mailto:cgordon@chillco.com Cary Gordon] || 2011-02-06 18:00 (Sunday; 6pm) || Yes || No || No || Me || No || 1.  2. &lt;br /&gt;
|-&lt;br /&gt;
| [mailto:kirwin@wittenberg.edu Ken Irwin] || 2011-02-07 (Monday evening - driving, so time is flexible) || Driving || No || If you wish || Me || No || 1.  2. &lt;br /&gt;
|-&lt;br /&gt;
| [mailto:erik.hatcher@lucidimagination.com Erik Hatcher] || 2011-02-06 (Sunday afternoon, 2:02pm) || Yes || No || No || Me || No || 1.  2. 3.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Departures'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; class=&amp;quot;sortable&amp;quot; &lt;br /&gt;
|- style=&amp;quot;text-align: left;&amp;quot;&lt;br /&gt;
! Name !! Flight Departing !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?&lt;br /&gt;
|-&lt;br /&gt;
| [mailto:andrew.nagy@serialssolutions.com Andrew Nagy] || 2011-02-10 15:00 (Thursday; 3pm) || Yes || No || No || Me || No || 1. Tim McGeary 2. Paul Joseph 3. Jason Fowler &lt;br /&gt;
|-&lt;br /&gt;
| [mailto:cgordon@chillco.com Cary Gordon] || 2011-02-10 19:00 (Thursday; 7pm) || Yes || No || No || Me || No || 1. 2.&lt;br /&gt;
|-&lt;br /&gt;
| [mailto:kirwin@wittenberg.edu Ken Irwin] || 2011-02-07 (Thursday evening - driving, so time is flexible) || Driving || No || If you wish || Me || No || 1.  2. &lt;br /&gt;
|-&lt;br /&gt;
| [mailto:erik.hatcher@lucidimagination.com Erik Hatcher] || 2011-02-08 (Tuesday evening; 7:17pm), leaving conf. mid-afternoon || Driving || No || No || Me || No || 1.  2. 3.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Northwest Columbus, OH ===&lt;br /&gt;
'''Arrivals'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; class=&amp;quot;sortable&amp;quot; &lt;br /&gt;
|- style=&amp;quot;text-align: left;&amp;quot;&lt;br /&gt;
! Name !! Departing Columbus  !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?&lt;br /&gt;
|-&lt;br /&gt;
| [[User:DataGazetteer|Peter Murray]] || 2011-02-07 08:00 (Monday, 8am) || Yes || No || No || Yes || No || 1. 2. 3. &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Departures'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; class=&amp;quot;sortable&amp;quot; &lt;br /&gt;
|- style=&amp;quot;text-align: left;&amp;quot;&lt;br /&gt;
! Name !! Departing Bloomington  !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?&lt;br /&gt;
|-&lt;br /&gt;
| [[User:DataGazetteer|Peter Murray]] || 2011-02-10 12:00 (Thursday, noon) || Yes || No || No || Yes || No || 1. 2. 3. &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Chattanooga, TN (via Nashville, Bowling Green &amp;amp; Louisville) ===&lt;br /&gt;
'''Arrivals'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; class=&amp;quot;sortable&amp;quot; &lt;br /&gt;
|- style=&amp;quot;text-align: left;&amp;quot;&lt;br /&gt;
! Name !! Departing Chattanooga  !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?&lt;br /&gt;
|-&lt;br /&gt;
| [[User:Rsinger|Ross Singer]] || 2011-02-07 (Monday AM) || No || No || If you're willing || Yes || No || 1. 2. 3. &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Departures'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;5&amp;quot; class=&amp;quot;sortable&amp;quot; &lt;br /&gt;
|- style=&amp;quot;text-align: left;&amp;quot;&lt;br /&gt;
! Name !! Departing Bloomington  !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?&lt;br /&gt;
|-&lt;br /&gt;
| [[User:Rsinger|Ross Singer]] || 2011-02-10 12:00 (Thursday PM) || No || No || Your call || Yes || No || 1. 2. 3. &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2011]]&lt;/div&gt;</summary>
		<author><name>ErikHatcher</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2011_Preconference_Proposals&amp;diff=6201</id>
		<title>2011 Preconference Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2011_Preconference_Proposals&amp;diff=6201"/>
				<updated>2010-10-20T15:30:50Z</updated>
		
		<summary type="html">&lt;p&gt;ErikHatcher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Proposals for 2011 Code4LibCon Preconferences ==&lt;br /&gt;
&lt;br /&gt;
Proposals will close Friday November 19 so we can finalize the list and add them to registration!&lt;br /&gt;
&lt;br /&gt;
We'll have space for up to 3 full-day pre-conferences and 3-6 half-day pre-conferences.&lt;br /&gt;
&lt;br /&gt;
'''Please include a &amp;quot;Contact/Responsible Individual&amp;quot; name and email address so we know who is willing to put on the proposed precon.'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== What's New In Solr ==&lt;br /&gt;
* Description: The library world is fired up about Solr.  Practically every next-gen catalog is using it (via Blacklight, VuFind, or other technologies).  Solr has continued improving in some dramatic ways, including geospatial support, field collapsing/grouping, extended dismax query parsing, pivot/grid/matrix/tree faceting, autosuggest, and more.  This session will cover all of these new features, showcasing live examples of them all, including anything new that is implemented prior to the conference.&lt;br /&gt;
* Duration: half-day&lt;br /&gt;
* Speaker Bio: Erik has spoken at several code4lib conferences (Keynoted Athens '07 along with the infamous pioneering Solr preconference, presented at Providence '09, and pre-conferenced Asheville '10).  Erik co-authored &amp;quot;Lucene in Action&amp;quot;, and he's a Lucene and Solr committer.  His library world claims to fame are founding and naming Blacklight, original developer on Collex and the Rossetti Archive search.&lt;br /&gt;
* Contact: Erik Hatcher (erik.hatcher at lucidimagination.com)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2011]]&lt;/div&gt;</summary>
		<author><name>ErikHatcher</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2011_Preconference_Proposals&amp;diff=6200</id>
		<title>2011 Preconference Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2011_Preconference_Proposals&amp;diff=6200"/>
				<updated>2010-10-20T15:27:25Z</updated>
		
		<summary type="html">&lt;p&gt;ErikHatcher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Proposals for 2011 Code4LibCon Preconferences ==&lt;br /&gt;
&lt;br /&gt;
Proposals will close Friday November 19 so we can finalize the list and add them to registration!&lt;br /&gt;
&lt;br /&gt;
We'll have space for up to 3 full-day pre-conferences and 3-6 half-day pre-conferences.&lt;br /&gt;
&lt;br /&gt;
'''Please include a &amp;quot;Contact/Responsible Individual&amp;quot; name and email address so we know who is willing to put on the proposed precon.'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== What's New In Solr ==&lt;br /&gt;
* Description: The library world is fired up about Solr.  Practically every next-gen catalog is using it (via Blacklight, VuFind, or other technologies).  Solr has continued improving in some dramatic ways, including geospatial support, field collapsing/grouping, extended dismax query parsing, pivot/grid/matrix/tree faceting, autosuggest, etc, including anything new that is implemented prior to the conference.  This session will cover all of these new features, showcasing live examples of them all.&lt;br /&gt;
* Duration: half-day&lt;br /&gt;
* Speaker Bio: Erik has spoken at several code4lib conferences (Keynoted Athens '07 along with the infamous pioneering Solr preconference, presented at Providence '09, and pre-conferenced Asheville '10).  Erik co-authored &amp;quot;Lucene in Action&amp;quot;, and he's a Lucene and Solr committer.  His library world claims to fame are founding and naming Blacklight, original developer on Collex and the Rossetti Archive search.&lt;br /&gt;
* Contact: Erik Hatcher (erik.hatcher at lucidimagination.com)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2011]]&lt;/div&gt;</summary>
		<author><name>ErikHatcher</name></author>	</entry>

	</feed>