<?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=Cwlown</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=Cwlown"/>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/Special:Contributions/Cwlown"/>
		<updated>2026-04-08T11:19:49Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.26.2</generator>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_Breakout_II_(Wednesday)&amp;diff=40943</id>
		<title>2014 Breakout II (Wednesday)</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_Breakout_II_(Wednesday)&amp;diff=40943"/>
				<updated>2014-03-26T20:32:50Z</updated>
		
		<summary type="html">&lt;p&gt;Cwlown: /* Unusual searches &amp;amp; long searches */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==UX==&lt;br /&gt;
&lt;br /&gt;
''Notes by @erinrwhite again. Y'all cannot escape me''&lt;br /&gt;
&lt;br /&gt;
NCSU's UX department is cross-functional and has members from across departments. Looking at creating cross-channel experiences from digital to real life. Working on consistency across experiences. Expanded on UMich's UX department to create a UX research team.&lt;br /&gt;
&lt;br /&gt;
Research: the NCSU does a research project every month. NCSU is also training new library fellows to infuse User Experience work into their projects. Growing the culture of UX within the organization.&lt;br /&gt;
&lt;br /&gt;
===Process===&lt;br /&gt;
&lt;br /&gt;
How do you work in harmony with a dev team when sometimes the UX team can be the roadblock to development? Need to get a workflow that works so that everyone can move quickly. &lt;br /&gt;
&lt;br /&gt;
UXing web pages vs. entire web applications: they're totally different experiences so need different approaches to user experience evaluation.&lt;br /&gt;
&lt;br /&gt;
===Research===&lt;br /&gt;
&lt;br /&gt;
Guerrilla research: go out into the public spaces of your library to test prototypes or design ideas. Make it quick. User research doesn't have to be a huge deal. &lt;br /&gt;
&lt;br /&gt;
If you can't give money as remuneration, give 'em candy bars. But make the candy bars full-size, not the minis. &lt;br /&gt;
&lt;br /&gt;
===Librarians are users too...right?===&lt;br /&gt;
&lt;br /&gt;
How do we push back against librarians' assertions that pages/interfaces should look a certain way?&lt;br /&gt;
&lt;br /&gt;
Research with users can *sometimes* help.&lt;br /&gt;
&lt;br /&gt;
Need to communicate your evidence to your library. UT hired someone last year just to do IT communication (!). &lt;br /&gt;
&lt;br /&gt;
Numbers don't always work. Need a visual tool if possible (i.e. a heatmap). If you can compile a video or audio of user interviews or usability testing, that can be very powerful.&lt;br /&gt;
&lt;br /&gt;
===Resources===&lt;br /&gt;
&lt;br /&gt;
Recommendation: 37Signals' book [https://gettingreal.37signals.com/ Getting Real] on helping choose things that are/aren't important and moving on.&lt;br /&gt;
&lt;br /&gt;
===Publish your damn work!===&lt;br /&gt;
&lt;br /&gt;
As a community, we need to get better about sharing our work with each other so we don't have to keep reinventing the wheel.&lt;br /&gt;
&lt;br /&gt;
==Securing EZproxy==&lt;br /&gt;
Mag II&lt;br /&gt;
&lt;br /&gt;
==Tech service==&lt;br /&gt;
Pine Oak&lt;br /&gt;
&lt;br /&gt;
==AngularJS==&lt;br /&gt;
Capitol&lt;br /&gt;
&lt;br /&gt;
==BIBFRAME 2 &amp;amp; Linked Data==&lt;br /&gt;
in Ballroom&lt;br /&gt;
&lt;br /&gt;
==Unusual searches &amp;amp; long searches==&lt;br /&gt;
Willow Oak&lt;br /&gt;
&lt;br /&gt;
This group met to talk about unusual searches, especially extremely long searches, copied and pasted citations, and other issues related to serving niche searches.&lt;br /&gt;
&lt;br /&gt;
Some of the possible solutions include:&lt;br /&gt;
&lt;br /&gt;
*Looking for DOI, ISBN or other identifiers in the query, extract these, and make the request to a service using these IDs.&lt;br /&gt;
*Remove extraneous characters from the beginning of a string that may indicate copied and pasted text.&lt;br /&gt;
*Truncate a long query at a certain character length (80 to 100?) assuming that the most useful text appears at the start of the query.&lt;br /&gt;
*Use a regex to identify a citation by detecting some combination of words commonly used in citations (Vol., Iss., pp.), four digit years, and other combinations of numbers.&lt;br /&gt;
**It would be useful to test this regex against a search corpus to check for false matches.&lt;br /&gt;
**Once a citation is identified either certain characters could be removed from the query or a citation parser such as the Brown's FreeCite [http://freecite.library.brown.edu/].&lt;br /&gt;
&lt;br /&gt;
Other things noted:&lt;br /&gt;
&lt;br /&gt;
*If you truncate a query don't truncate in the middle of a word or else recall may be worse.&lt;br /&gt;
*Log queries that provide zero hit as way to find types of queries that may need some post processing.&lt;br /&gt;
*Is there way to provide smarter, live results for libraries for thing such as library hours, similar to the way Google provides live flight tracking information directly in the results list.&lt;br /&gt;
&lt;br /&gt;
==ResCarta==&lt;br /&gt;
We gathered in the ballroom and had an active conversation about the philosophy of keeping archives in a reduced set of file formats with standardized metadata. We reviewed directory structures and METS collection level details.&lt;br /&gt;
For a future reduction of coding and costs we advise the reduction of file formats (normalization) on ingestion into a structured archive.&lt;br /&gt;
&lt;br /&gt;
Justin from Artefactual shared their philosophy and thoughts on use of METS collection level file contents.&lt;br /&gt;
&lt;br /&gt;
Historically systems like NDNP are gate keeper validation systems and we should be building digital archive creation systems. Build to a standard under code control rather than code to check hand made datasets.&lt;br /&gt;
&lt;br /&gt;
==OCLC institution RDF project==&lt;br /&gt;
in ballroom&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Digital Preservation ==&lt;br /&gt;
&lt;br /&gt;
Cost issues, billing departments, charging grant projects one-time vs. multiple&lt;br /&gt;
&lt;br /&gt;
Internal vs. external hosting&lt;br /&gt;
&lt;br /&gt;
Trusted Digital Repository, TRAC, ISO standard&lt;br /&gt;
&lt;br /&gt;
Geographic distribution, what does that actually mean&lt;br /&gt;
&lt;br /&gt;
? who is using checksums and how often they are verifying&lt;br /&gt;
&amp;lt;br/&amp;gt;UNC - make sure checksums checked every quarter, throttle/stagger checking&lt;br /&gt;
&lt;br /&gt;
? Has anyone had checksum checks fail? &lt;br /&gt;
&amp;lt;br/&amp;gt;only time is user error, checking wrong one, files are changed after initial checksum&lt;br /&gt;
&lt;br /&gt;
video - frame-level checksum, part of ffmpeg, make frame level information and checksum that&lt;br /&gt;
&lt;br /&gt;
? how much code/time is done to check on problems with checksums? &lt;br /&gt;
&amp;lt;br/&amp;gt;manual vs. auto repair, prefer manual intervention&lt;br /&gt;
&lt;br /&gt;
how often to check tapes, without further damaging tape&lt;br /&gt;
&lt;br /&gt;
for testing, there's a tool that will flip bits&lt;br /&gt;
&amp;lt;br/&amp;gt;disaster recovery testing&lt;br /&gt;
&amp;lt;br/&amp;gt;hesitance to test/break files on production &lt;br /&gt;
&lt;br /&gt;
ZFS, self-healing filesystem, replication (worried about replicating checksum errors)&lt;br /&gt;
&lt;br /&gt;
? about viruses, malicious scripts&lt;br /&gt;
&amp;lt;br/&amp;gt;UNC runs ClamAV on everything, does make sure everyone is authorized user&lt;br /&gt;
&lt;br /&gt;
AV Artifact Atlas - visual glossary of damage types to a/v files&lt;br /&gt;
&lt;br /&gt;
tape backup of everything can take too long to run (days)&lt;br /&gt;
&amp;lt;br/&amp;gt;rely on multiple copies of objects on disk&lt;br /&gt;
&lt;br /&gt;
format migrations - no one has really done it yet&lt;br /&gt;
&amp;lt;br/&amp;gt;archivematica wiki is great resource&lt;br /&gt;
&lt;br /&gt;
normalization on ingest&lt;br /&gt;
&amp;lt;br/&amp;gt;emulation as a service - possible collaboration in community&lt;br /&gt;
&amp;lt;br/&amp;gt;internet archive emulation service using javascript/jsmess&lt;br /&gt;
&lt;br /&gt;
=== Major issues for Digital Preservation ===&lt;br /&gt;
* storage (terabytes coming in each year, no cost-effective solutions for growing needs)&lt;br /&gt;
* staffing (for smaller institutions)&lt;br /&gt;
* funding model/sustainability (some charge for services, some funding by Campus IT)&lt;br /&gt;
** research data, grants, data management planning tool&lt;br /&gt;
** how long can we offer to store files&lt;br /&gt;
** trying to convince Provost that library storage is like library shelf space and needs to be funded&lt;br /&gt;
** split funding, from graduate schools or president's office&lt;br /&gt;
* some work on service level agreements, tiers of service&lt;br /&gt;
* file retrievals may not be tracked anywhere, if so can't tell what hasn't been retrieved&lt;br /&gt;
&lt;br /&gt;
NDSA Levels of Preservation - http://www.digitalpreservation.gov/ndsa/activities/levels.html&lt;/div&gt;</summary>
		<author><name>Cwlown</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&amp;diff=40103</id>
		<title>2014 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&amp;diff=40103"/>
				<updated>2013-12-09T16:10:15Z</updated>
		
		<summary type="html">&lt;p&gt;Cwlown: /* Afternoon */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Code4Lib 2014 Pre-Conference Proposals==&lt;br /&gt;
&lt;br /&gt;
= PROPOSALS ARE CLOSED : PLEASE DO NOT EDIT THIS PAGE =&lt;br /&gt;
&lt;br /&gt;
Proposals were accepted through December 6th, 2013.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Note===&lt;br /&gt;
Attendance at a pre-conference will require a small fee ''due at the time of conference registration.&lt;br /&gt;
 &lt;br /&gt;
Although this was specified in the email announcements relating to pre-conferences, it was not added to this page until December 2nd.  I (Adam C.) apologize for the omission and I hope this will not cause any &amp;quot;sticker shock.&amp;quot;  Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.&lt;br /&gt;
&lt;br /&gt;
Please put your pre-conference on the list in the following format:&lt;br /&gt;
&lt;br /&gt;
===NAME===&lt;br /&gt;
'''&amp;quot;Full-Day|Half-Day&amp;quot; [PREFERRED TIME]'''&lt;br /&gt;
&lt;br /&gt;
Description&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Drupal4lib Sub-con Barcamp===&lt;br /&gt;
=====Full Day=====&lt;br /&gt;
&lt;br /&gt;
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com&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;
This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).&lt;br /&gt;
&lt;br /&gt;
[[resources to help you learn drupal]]&lt;br /&gt;
&lt;br /&gt;
====Interested in Attending:====&lt;br /&gt;
&lt;br /&gt;
=====All Day=====&lt;br /&gt;
&lt;br /&gt;
* Renna Tuten &lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
&lt;br /&gt;
* Kevin Reiss&lt;br /&gt;
* Charlie Morris (NCSU) - glad to see this again this year!&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Open Refine Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot;'''&lt;br /&gt;
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com&lt;br /&gt;
&lt;br /&gt;
[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control&lt;br /&gt;
&lt;br /&gt;
The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. &lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&amp;lt;ol&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Adam Constabaris&lt;br /&gt;
&amp;lt;li&amp;gt;Ray Schwartz&lt;br /&gt;
&amp;lt;li&amp;gt;Jason Stirnaman&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Responsive Design Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day [Afternoon]&amp;quot;''' &lt;br /&gt;
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com&lt;br /&gt;
* Contact David Ward, University of Illinois, dh-ward@illinois.edu&lt;br /&gt;
&lt;br /&gt;
This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. &lt;br /&gt;
&lt;br /&gt;
Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
=== Intro to Blacklight ===&lt;br /&gt;
'''&amp;quot;Half-Day [Morning]&amp;quot;''' &lt;br /&gt;
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
* TA: Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
This session will be walk-through of the architecture of Blacklight, the community, and an introduction to building a Blacklight-based application. Each participant will have the opportunity to build a simple Blacklight application, and make basic customizations, while using a test-driven approach.&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;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Megan Kudzia&lt;br /&gt;
# Bret Davidson&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Cory Lown&lt;br /&gt;
&lt;br /&gt;
===Blacklight Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day [Afternoon]&amp;quot;''' &lt;br /&gt;
* Contact Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
&lt;br /&gt;
This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.&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 ).&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Kevin Reiss&lt;br /&gt;
# Megan Kudzia&lt;br /&gt;
# Erik Hatcher&lt;br /&gt;
&lt;br /&gt;
===RailsBridge: Intro to programming in Ruby on Rails===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
* Contact Justin Coyne, Data Curation Experts, justin@curationexperts.com&lt;br /&gt;
&lt;br /&gt;
Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! RailsBridge is a friendly place to get together and learn how to write some code.&lt;br /&gt;
&lt;br /&gt;
RailsBridge is a great workshop that opens the doors to projects like Blacklight and Hydra.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
1. Ayla Stein&lt;br /&gt;
&lt;br /&gt;
2. Heidi Dowding&lt;br /&gt;
&lt;br /&gt;
===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===&lt;br /&gt;
'''Full-Day'''&lt;br /&gt;
&lt;br /&gt;
Contact: &lt;br /&gt;
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com&lt;br /&gt;
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu&lt;br /&gt;
&lt;br /&gt;
This will be a full day session on project management.  We'll cover&lt;br /&gt;
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment&lt;br /&gt;
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets&lt;br /&gt;
* '''Executing the Project''' -- status meeting, status reports, issue management&lt;br /&gt;
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product&lt;br /&gt;
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Robin Dean&lt;br /&gt;
# Erin White&lt;br /&gt;
# Andrew Darby&lt;br /&gt;
&lt;br /&gt;
===Fail4Lib 2014===&lt;br /&gt;
'''Half Day [TBD, probably afternoon]'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Andreas Orphanides, akorphan (at) ncsu.edu&lt;br /&gt;
* Jason Casden, jmcasden (at) ncsu.edu&lt;br /&gt;
&lt;br /&gt;
The task of design (and the work that we do as library coders) is intimately tied to failure. Failures, both big and small, motivate us to create and improve. Failures are also occasionally the result of our work. Understanding and embracing failure, encouraging enlightened risk-taking, and seeking out opportunities to fail and learn are essential to success in our field. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be feared.&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
&lt;br /&gt;
* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?&lt;br /&gt;
* Confessionals, for those willing to share. Talk about your own experiences with rough starts, labor pains, and doomed projects in your own work: What can we learn from our own (and each others') failures?&lt;br /&gt;
* Group therapy. Let's talk about how to deal with risk management, failed projects, experimental endeavors, and more: How can we make ourselves, our colleagues, and our organizations more fault tolerant? How do we make sure we fail as productively as possible?&lt;br /&gt;
&lt;br /&gt;
''Interested in attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#Bret Davidson&lt;br /&gt;
#Mike Graves&lt;br /&gt;
#Ray Schwartz&lt;br /&gt;
#Jason Stirnaman&lt;br /&gt;
&lt;br /&gt;
===CLLAM @ code4lib===&lt;br /&gt;
'''(Computational Linguistics for Libraries, Archives and Museums)'''&lt;br /&gt;
&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Douglas W. Oard (primary), oard (at) umd.edu &lt;br /&gt;
* Corey Harper, corey (dot) harper (at) nyu.edu&lt;br /&gt;
* Robert Sanderson, azaroth42 (at) gmail.com &lt;br /&gt;
* Robert Warren, rwarren (at) math.carleton.ca&lt;br /&gt;
&lt;br /&gt;
We will hack at the intersection of diverse content from Libraries, Archives and Museums and bleeding edge tools from computational linguistics for slicing and dicing that content. Did you just acquire the email archives of a startup company? Maybe you can automatically build an org chart. Have you got metadata in a slew of languages? Perhaps you can search it all using one query. Is name authority control for e-resources getting too costly? Let’s see if entity linking techniques can help. These are just a few teasers. &lt;br /&gt;
&lt;br /&gt;
There’ll be plenty of content and tools supplied, but please bring your own [data] too -- you’ll hack with it in new ways throughout the day. We’ll get started with some lightning talks on what we’ve brought,then we’ll break up into groups to experiment and work on the ideas that appeal. Three guaranteed outcomes: you’ll walk away with new ideas, new tools, and new people you’ll have met.&lt;br /&gt;
&lt;br /&gt;
''Interested in attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Devon Smith&lt;br /&gt;
# Kevin S. Clarke&lt;br /&gt;
# Jason Stirnaman&lt;br /&gt;
&lt;br /&gt;
=== GeoHydra: Managing geospatial content ===&lt;br /&gt;
&lt;br /&gt;
'''Half-day [Afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Contact: Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Moderator: Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,&lt;br /&gt;
etc., all of which you want to integrate into your digital repository? In this&lt;br /&gt;
workshop, we will discuss how Hydra can provide discovery, delivery, and&lt;br /&gt;
management services for geospatial assets, as well as solicit questions about&lt;br /&gt;
your own GIS projects. We aim to help answer the following questions you might have about putting geospatial data into your Hydra-based digital library:&lt;br /&gt;
&lt;br /&gt;
* What are the types of geospatial data?&lt;br /&gt;
* How to dive into Hydra?&lt;br /&gt;
* How to model geospatial holdings with Hydra?&lt;br /&gt;
* How to discover and view geospatial data?&lt;br /&gt;
* How to build a geospatial data infrastructure?&lt;br /&gt;
* What are common approaches and problems?&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Esmé Cowles&lt;br /&gt;
&lt;br /&gt;
===Technology, Librarianship, and Gender: Moving the conversation forward===&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]&lt;br /&gt;
&lt;br /&gt;
'''Description'''&lt;br /&gt;
&lt;br /&gt;
Librarianship is largely made up of women, yet women are significantly underrepresented in tech positions, on any level, within libraries themselves. Why? What are we doing to encourage women to become more involved in STEM within librarianship? What kind of message are we sending when library technology keynotes remain almost resolutely male? How are we changing the face of technology, not only within libraries, but with the field itself? How are we training our staff and colleagues in the areas of fairness and removal of bias? Our vendors?&lt;br /&gt;
&lt;br /&gt;
Lots of tough questions.&lt;br /&gt;
&lt;br /&gt;
While the conversation has been going on via various blogs and articles within the last few years, it was given a public face at [http://infotoday.com/il2013/day.asp?day=Monday#session_D105 Internet Librarian 2013] where a panel of 7 (four women, three men) gave personal experiences on the above and then opened up the conversation to the audience. As eye opening and enriching the conversation was, a 45 minute panel was not enough. One thing remains clear: We need to keep the conversation moving forward and start making some radical changes in the way we think, act, and how we need to harness this to start making real changes within librarianship itself.&lt;br /&gt;
&lt;br /&gt;
Topics to include:  Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems,  mentoring, ally support, and more&lt;br /&gt;
&lt;br /&gt;
Those attending should expect: Begin with opening up the conversation of experiences and talking about what is most needed, spending remaining time putting together live, usable solutions to start implementing as well as pushing the conversation forward at local levels&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
=====All Day=====&lt;br /&gt;
1. Kate Kosturski&lt;br /&gt;
&lt;br /&gt;
2. Valerie Aurora&lt;br /&gt;
&lt;br /&gt;
3. Declan Fleming&lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
1. Shaun Ellis&lt;br /&gt;
&lt;br /&gt;
2. Jason Casden&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
1. Ayla Stein&lt;br /&gt;
&lt;br /&gt;
2. Heidi Dowding&lt;br /&gt;
&lt;br /&gt;
3. Coral Sheldon-Hess&lt;br /&gt;
&lt;br /&gt;
4. Cory Lown&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===FileAnalyzer: Rapid Development of File Manipulation Tasks===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
* Contact Terry Brady, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The FileAnalyzer (https://github.com/Georgetown-University-Libraries/File-Analyzer) is an application designed to solve a number of library automation challenges:&lt;br /&gt;
&lt;br /&gt;
* validating digitized and reformatted files&lt;br /&gt;
* validating vendor statistics for counter compliance&lt;br /&gt;
* preparing collections of digital files for archiving and ingest&lt;br /&gt;
* manipulating ILS import and export files&lt;br /&gt;
&lt;br /&gt;
The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census. After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform. Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.&lt;br /&gt;
&lt;br /&gt;
The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules. As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.&lt;br /&gt;
&lt;br /&gt;
The first half of this session will be targeted to potential users and developers.  The second half of the session will be targeted towards developers who are interested in developing custom rules for the application.&lt;br /&gt;
&lt;br /&gt;
''Session Overview''&lt;br /&gt;
* Overview of the application&lt;br /&gt;
* Running sample file tests/transformations through the application&lt;br /&gt;
* Compiling and building the application&lt;br /&gt;
* Coding a custom file processing task&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#Ray Schwartz&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Collecting social media data with Social Feed Manager===&lt;br /&gt;
'''Half-Day [Morning]'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Dan Chudnov, GW Libraries, dchud (at) gwu.edu&lt;br /&gt;
* Dan Kerchner, GW Libraries, kerchner (at) gwu.edu&lt;br /&gt;
* Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu&lt;br /&gt;
&lt;br /&gt;
Social media data is a popular material for research and a new format for building collections.  What does it take to collect meaningfully from Twitter, Tumblr, YouTube, Weibo, Facebook, and other sites?  We will:&lt;br /&gt;
* Introduce options for collections, including both high- and low-end commercial offerings. Discuss what it means to collect these resources, covering boundaries, policies, and workflows required to develop a social media collection program in your institution.&lt;br /&gt;
* Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them&lt;br /&gt;
* Help you get started using the free [http://gwu-libraries.github.io/social-feed-manager Social Feed Manager] (SFM) app we're developing at GW to create your first collections. We’ll demo its use and demo a clean install (those w/environments can follow along)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Declan Fleming&lt;br /&gt;
# Esmé Cowles&lt;br /&gt;
# Jason Stirnaman&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Intro to Git ===&lt;br /&gt;
'''&amp;quot;Half-Day [tbd - probably afternoon]&amp;quot;''' &lt;br /&gt;
* Contact: Erin Fahy, Stanford University, efahy at stanford.edu&lt;br /&gt;
* TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu&lt;br /&gt;
&lt;br /&gt;
This session will cover the fundamentals of git by discussing/going through (time allowing):&lt;br /&gt;
* what is a distributed version control system&lt;br /&gt;
* what is git and github&lt;br /&gt;
* initializing a repo on a remote server/github&lt;br /&gt;
* cloning an existing repo&lt;br /&gt;
* creating a branch&lt;br /&gt;
* contributing code to a repo&lt;br /&gt;
* how to handle merge conflicts&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Archival discovery and use ===&lt;br /&gt;
'''Full Day''' &lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Tim Shearer, UNC Chapel Hill, tshearer at email.unc.edu, &lt;br /&gt;
* Will Sexton, Duke, will.sexton at duke.edu&lt;br /&gt;
&lt;br /&gt;
This is a full day pre-conference about archival collections and will cover the intersections of archives, workflows, technologies, discovery, and use.&lt;br /&gt;
&lt;br /&gt;
Morning agenda: focused talks around (but not limited to) issues such as:&lt;br /&gt;
* Crowd-sourcing description to enhance collecitons&lt;br /&gt;
* Linked data and authority&lt;br /&gt;
* Mass digitization and sustainable workflows&lt;br /&gt;
* Digitized objects in context (images and other objects in finding aids)&lt;br /&gt;
* Too many cooks in the kitchen: versioning&lt;br /&gt;
* Global-, intra-, and inter- discovery of archival materials via finding aids &lt;br /&gt;
* and more...&lt;br /&gt;
&lt;br /&gt;
Afternoon agenda:  Focused talks around specific tools followed by general discussion, connections, opportunities, aspirations, and planning.&lt;br /&gt;
&lt;br /&gt;
Tool examples:&lt;br /&gt;
* Archivespace&lt;br /&gt;
* STEADy&lt;br /&gt;
* &amp;quot;RAMP&amp;quot; (Remixing Archival Metadata Project)&lt;br /&gt;
* OpenRefine&lt;br /&gt;
* Aeon&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
Morning:&lt;br /&gt;
* your name&lt;br /&gt;
&lt;br /&gt;
Afternoon:&lt;br /&gt;
* your name&lt;br /&gt;
&lt;br /&gt;
All day:&lt;br /&gt;
&lt;br /&gt;
# Josh Wilson&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===AV Content Slam===&lt;br /&gt;
'''Half-Day [morning]'''&lt;br /&gt;
Contacts:&lt;br /&gt;
* Kara Van Malssen, kara (at) avpreserve.com&lt;br /&gt;
* Lauren Sorenson, laurens (at) bavc.org&lt;br /&gt;
* Steven Villereal , villereal (at) gmail.com&lt;br /&gt;
A morning BarCamp/unconference for practitioners and coders who work with audiovisual content. The agenda will be attendee-driven, with a focus on sharing, synthesizing, and improving workflow strategies and documentation for software-based approaches to wrangling and providing access to audio and video content.&lt;br /&gt;
Possible topics of discussion might include:&lt;br /&gt;
* Use of format id and characterization/metadata extraction tools for AV&lt;br /&gt;
* Creating and using time-based metadata&lt;br /&gt;
* Managing (moving, fixity checking, etc) massive files (like uncompressed video)&lt;br /&gt;
For a better idea of the topics and concerns that have informed some past AV-themed events, check out the event wikis for [http://wiki.curatecamp.org/index.php/CURATEcamp_AVpres_2013 CURATEcamp AVpres 2013] as well as the [http://wiki.curatecamp.org/index.php/Association_of_Moving_Image_Archivists_%26_Digital_Library_Federation_Hack_Day_2013 AMIA/DLF 2013 Hack Day] .&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===OCLC Web Services Hackfest===&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Half-Day&amp;quot; [afternoon]&lt;br /&gt;
&lt;br /&gt;
Contact: Shelley Hostetler, Community Manager, Developer Network hostetls[at]oclc.org&lt;br /&gt;
&lt;br /&gt;
This half-day hackfest will explore some of the OCLC Developer Network web services. We will provide an overview of some of the common topics such as the general REST-based architecture for most services and how to use some new authentication clients. The group can then decide to take a deep dive into a particular API and/or write a client library for the community.&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Obey the Testing Goat!: Test Driven Web Development From The Ground Up===&lt;br /&gt;
'''Half-Day [tbd - probably afternoon]'''&lt;br /&gt;
* Contact [[User:Mredar|Mark Redar]], mredar[at]gmail.com&lt;br /&gt;
&lt;br /&gt;
Test driven development is a proven method for producing better quality code. But I've found it hard to follow a strict TDD methodology when starting new web projects. How do you write that first test when there is no code or web pages created yet.&lt;br /&gt;
&lt;br /&gt;
In this session, we will follow the excellent book [http://shop.oreilly.com/product/0636920029533.do &amp;quot;Test-Driven Web Development with Python&amp;quot;] to create a simple web site in Django following TDD from the first character typed. Come ready to code and test. No prior knowledge of python or Django required.&lt;br /&gt;
&lt;br /&gt;
By the end of this session, you should be able to  [http://www.obeythetestinggoat.com/ &amp;quot;Obey the Testing Goat&amp;quot;] from the start to finish for your next project.&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:&lt;br /&gt;
&lt;br /&gt;
# Charlie Morris (NCSU)&lt;br /&gt;
# Jason Stirnaman&lt;br /&gt;
&lt;br /&gt;
===Summon Camp===&lt;br /&gt;
Placeholder by Tim McGeary for Gillian Cain (Serials Solutions)&lt;br /&gt;
Description to be provided by Gillian after account issues resolved. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
[[:Category:Code4Lib2014]]&lt;/div&gt;</summary>
		<author><name>Cwlown</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&amp;diff=40097</id>
		<title>2014 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&amp;diff=40097"/>
				<updated>2013-12-09T15:58:38Z</updated>
		
		<summary type="html">&lt;p&gt;Cwlown: /* Fail4Lib 2014 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Code4Lib 2014 Pre-Conference Proposals==&lt;br /&gt;
&lt;br /&gt;
= PROPOSALS ARE CLOSED : PLEASE DO NOT EDIT THIS PAGE =&lt;br /&gt;
&lt;br /&gt;
Proposals were accepted through December 6th, 2013.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Note===&lt;br /&gt;
Attendance at a pre-conference will require a small fee ''due at the time of conference registration.&lt;br /&gt;
 &lt;br /&gt;
Although this was specified in the email announcements relating to pre-conferences, it was not added to this page until December 2nd.  I (Adam C.) apologize for the omission and I hope this will not cause any &amp;quot;sticker shock.&amp;quot;  Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.&lt;br /&gt;
&lt;br /&gt;
Please put your pre-conference on the list in the following format:&lt;br /&gt;
&lt;br /&gt;
===NAME===&lt;br /&gt;
'''&amp;quot;Full-Day|Half-Day&amp;quot; [PREFERRED TIME]'''&lt;br /&gt;
&lt;br /&gt;
Description&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Drupal4lib Sub-con Barcamp===&lt;br /&gt;
=====Full Day=====&lt;br /&gt;
&lt;br /&gt;
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com&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;
This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).&lt;br /&gt;
&lt;br /&gt;
[[resources to help you learn drupal]]&lt;br /&gt;
&lt;br /&gt;
====Interested in Attending:====&lt;br /&gt;
&lt;br /&gt;
=====All Day=====&lt;br /&gt;
&lt;br /&gt;
* Renna Tuten &lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
&lt;br /&gt;
* Kevin Reiss&lt;br /&gt;
* Charlie Morris (NCSU) - glad to see this again this year!&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Open Refine Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot;'''&lt;br /&gt;
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com&lt;br /&gt;
&lt;br /&gt;
[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control&lt;br /&gt;
&lt;br /&gt;
The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. &lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&amp;lt;ol&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Adam Constabaris&lt;br /&gt;
&amp;lt;li&amp;gt;Ray Schwartz&lt;br /&gt;
&amp;lt;li&amp;gt;Jason Stirnaman&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Responsive Design Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day [Afternoon]&amp;quot;''' &lt;br /&gt;
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com&lt;br /&gt;
* Contact David Ward, University of Illinois, dh-ward@illinois.edu&lt;br /&gt;
&lt;br /&gt;
This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. &lt;br /&gt;
&lt;br /&gt;
Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
=== Intro to Blacklight ===&lt;br /&gt;
'''&amp;quot;Half-Day [Morning]&amp;quot;''' &lt;br /&gt;
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
* TA: Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
This session will be walk-through of the architecture of Blacklight, the community, and an introduction to building a Blacklight-based application. Each participant will have the opportunity to build a simple Blacklight application, and make basic customizations, while using a test-driven approach.&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;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Megan Kudzia&lt;br /&gt;
# Bret Davidson&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Cory Lown&lt;br /&gt;
&lt;br /&gt;
===Blacklight Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day [Afternoon]&amp;quot;''' &lt;br /&gt;
* Contact Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
&lt;br /&gt;
This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.&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 ).&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Kevin Reiss&lt;br /&gt;
# Megan Kudzia&lt;br /&gt;
# Erik Hatcher&lt;br /&gt;
&lt;br /&gt;
===RailsBridge: Intro to programming in Ruby on Rails===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
* Contact Justin Coyne, Data Curation Experts, justin@curationexperts.com&lt;br /&gt;
&lt;br /&gt;
Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! RailsBridge is a friendly place to get together and learn how to write some code.&lt;br /&gt;
&lt;br /&gt;
RailsBridge is a great workshop that opens the doors to projects like Blacklight and Hydra.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
1. Ayla Stein&lt;br /&gt;
&lt;br /&gt;
2. Heidi Dowding&lt;br /&gt;
&lt;br /&gt;
===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===&lt;br /&gt;
'''Full-Day'''&lt;br /&gt;
&lt;br /&gt;
Contact: &lt;br /&gt;
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com&lt;br /&gt;
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu&lt;br /&gt;
&lt;br /&gt;
This will be a full day session on project management.  We'll cover&lt;br /&gt;
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment&lt;br /&gt;
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets&lt;br /&gt;
* '''Executing the Project''' -- status meeting, status reports, issue management&lt;br /&gt;
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product&lt;br /&gt;
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Robin Dean&lt;br /&gt;
# Erin White&lt;br /&gt;
# Andrew Darby&lt;br /&gt;
&lt;br /&gt;
===Fail4Lib 2014===&lt;br /&gt;
'''Half Day [TBD, probably afternoon]'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Andreas Orphanides, akorphan (at) ncsu.edu&lt;br /&gt;
* Jason Casden, jmcasden (at) ncsu.edu&lt;br /&gt;
&lt;br /&gt;
The task of design (and the work that we do as library coders) is intimately tied to failure. Failures, both big and small, motivate us to create and improve. Failures are also occasionally the result of our work. Understanding and embracing failure, encouraging enlightened risk-taking, and seeking out opportunities to fail and learn are essential to success in our field. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be feared.&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
&lt;br /&gt;
* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?&lt;br /&gt;
* Confessionals, for those willing to share. Talk about your own experiences with rough starts, labor pains, and doomed projects in your own work: What can we learn from our own (and each others') failures?&lt;br /&gt;
* Group therapy. Let's talk about how to deal with risk management, failed projects, experimental endeavors, and more: How can we make ourselves, our colleagues, and our organizations more fault tolerant? How do we make sure we fail as productively as possible?&lt;br /&gt;
&lt;br /&gt;
''Interested in attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#Bret Davidson&lt;br /&gt;
#Mike Graves&lt;br /&gt;
#Ray Schwartz&lt;br /&gt;
&lt;br /&gt;
===CLLAM @ code4lib===&lt;br /&gt;
'''(Computational Linguistics for Libraries, Archives and Museums)'''&lt;br /&gt;
&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Douglas W. Oard (primary), oard (at) umd.edu &lt;br /&gt;
* Corey Harper, corey (dot) harper (at) nyu.edu&lt;br /&gt;
* Robert Sanderson, azaroth42 (at) gmail.com &lt;br /&gt;
* Robert Warren, rwarren (at) math.carleton.ca&lt;br /&gt;
&lt;br /&gt;
We will hack at the intersection of diverse content from Libraries, Archives and Museums and bleeding edge tools from computational linguistics for slicing and dicing that content. Did you just acquire the email archives of a startup company? Maybe you can automatically build an org chart. Have you got metadata in a slew of languages? Perhaps you can search it all using one query. Is name authority control for e-resources getting too costly? Let’s see if entity linking techniques can help. These are just a few teasers. &lt;br /&gt;
&lt;br /&gt;
There’ll be plenty of content and tools supplied, but please bring your own [data] too -- you’ll hack with it in new ways throughout the day. We’ll get started with some lightning talks on what we’ve brought,then we’ll break up into groups to experiment and work on the ideas that appeal. Three guaranteed outcomes: you’ll walk away with new ideas, new tools, and new people you’ll have met.&lt;br /&gt;
&lt;br /&gt;
''Interested in attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Devon Smith&lt;br /&gt;
# Kevin S. Clarke&lt;br /&gt;
&lt;br /&gt;
=== GeoHydra: Managing geospatial content ===&lt;br /&gt;
&lt;br /&gt;
'''Half-day [Afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Contact: Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Moderator: Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,&lt;br /&gt;
etc., all of which you want to integrate into your digital repository? In this&lt;br /&gt;
workshop, we will discuss how Hydra can provide discovery, delivery, and&lt;br /&gt;
management services for geospatial assets, as well as solicit questions about&lt;br /&gt;
your own GIS projects. We aim to help answer the following questions you might have about putting geospatial data into your Hydra-based digital library:&lt;br /&gt;
&lt;br /&gt;
* What are the types of geospatial data?&lt;br /&gt;
* How to dive into Hydra?&lt;br /&gt;
* How to model geospatial holdings with Hydra?&lt;br /&gt;
* How to discover and view geospatial data?&lt;br /&gt;
* How to build a geospatial data infrastructure?&lt;br /&gt;
* What are common approaches and problems?&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Esmé Cowles&lt;br /&gt;
&lt;br /&gt;
===Technology, Librarianship, and Gender: Moving the conversation forward===&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]&lt;br /&gt;
&lt;br /&gt;
'''Description'''&lt;br /&gt;
&lt;br /&gt;
Librarianship is largely made up of women, yet women are significantly underrepresented in tech positions, on any level, within libraries themselves. Why? What are we doing to encourage women to become more involved in STEM within librarianship? What kind of message are we sending when library technology keynotes remain almost resolutely male? How are we changing the face of technology, not only within libraries, but with the field itself? How are we training our staff and colleagues in the areas of fairness and removal of bias? Our vendors?&lt;br /&gt;
&lt;br /&gt;
Lots of tough questions.&lt;br /&gt;
&lt;br /&gt;
While the conversation has been going on via various blogs and articles within the last few years, it was given a public face at [http://infotoday.com/il2013/day.asp?day=Monday#session_D105 Internet Librarian 2013] where a panel of 7 (four women, three men) gave personal experiences on the above and then opened up the conversation to the audience. As eye opening and enriching the conversation was, a 45 minute panel was not enough. One thing remains clear: We need to keep the conversation moving forward and start making some radical changes in the way we think, act, and how we need to harness this to start making real changes within librarianship itself.&lt;br /&gt;
&lt;br /&gt;
Topics to include:  Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems,  mentoring, ally support, and more&lt;br /&gt;
&lt;br /&gt;
Those attending should expect: Begin with opening up the conversation of experiences and talking about what is most needed, spending remaining time putting together live, usable solutions to start implementing as well as pushing the conversation forward at local levels&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
=====All Day=====&lt;br /&gt;
1. Kate Kosturski&lt;br /&gt;
&lt;br /&gt;
2. Valerie Aurora&lt;br /&gt;
&lt;br /&gt;
3. Declan Fleming&lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
1. Shaun Ellis&lt;br /&gt;
&lt;br /&gt;
2. Jason Casden&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
1. Ayla Stein&lt;br /&gt;
&lt;br /&gt;
2. Heidi Dowding&lt;br /&gt;
&lt;br /&gt;
3. Coral Sheldon-Hess&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===FileAnalyzer: Rapid Development of File Manipulation Tasks===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
* Contact Terry Brady, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The FileAnalyzer (https://github.com/Georgetown-University-Libraries/File-Analyzer) is an application designed to solve a number of library automation challenges:&lt;br /&gt;
&lt;br /&gt;
* validating digitized and reformatted files&lt;br /&gt;
* validating vendor statistics for counter compliance&lt;br /&gt;
* preparing collections of digital files for archiving and ingest&lt;br /&gt;
* manipulating ILS import and export files&lt;br /&gt;
&lt;br /&gt;
The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census. After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform. Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.&lt;br /&gt;
&lt;br /&gt;
The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules. As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.&lt;br /&gt;
&lt;br /&gt;
The first half of this session will be targeted to potential users and developers.  The second half of the session will be targeted towards developers who are interested in developing custom rules for the application.&lt;br /&gt;
&lt;br /&gt;
''Session Overview''&lt;br /&gt;
* Overview of the application&lt;br /&gt;
* Running sample file tests/transformations through the application&lt;br /&gt;
* Compiling and building the application&lt;br /&gt;
* Coding a custom file processing task&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#Ray Schwartz&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Collecting social media data with Social Feed Manager===&lt;br /&gt;
'''Half-Day [Morning]'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Dan Chudnov, GW Libraries, dchud (at) gwu.edu&lt;br /&gt;
* Dan Kerchner, GW Libraries, kerchner (at) gwu.edu&lt;br /&gt;
* Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu&lt;br /&gt;
&lt;br /&gt;
Social media data is a popular material for research and a new format for building collections.  What does it take to collect meaningfully from Twitter, Tumblr, YouTube, Weibo, Facebook, and other sites?  We will:&lt;br /&gt;
* Introduce options for collections, including both high- and low-end commercial offerings. Discuss what it means to collect these resources, covering boundaries, policies, and workflows required to develop a social media collection program in your institution.&lt;br /&gt;
* Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them&lt;br /&gt;
* Help you get started using the free [http://gwu-libraries.github.io/social-feed-manager Social Feed Manager] (SFM) app we're developing at GW to create your first collections. We’ll demo its use and demo a clean install (those w/environments can follow along)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Declan Fleming&lt;br /&gt;
# Esmé Cowles&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Intro to Git ===&lt;br /&gt;
'''&amp;quot;Half-Day [tbd - probably afternoon]&amp;quot;''' &lt;br /&gt;
* Contact: Erin Fahy, Stanford University, efahy at stanford.edu&lt;br /&gt;
* TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu&lt;br /&gt;
&lt;br /&gt;
This session will cover the fundamentals of git by discussing/going through (time allowing):&lt;br /&gt;
* what is a distributed version control system&lt;br /&gt;
* what is git and github&lt;br /&gt;
* initializing a repo on a remote server/github&lt;br /&gt;
* cloning an existing repo&lt;br /&gt;
* creating a branch&lt;br /&gt;
* contributing code to a repo&lt;br /&gt;
* how to handle merge conflicts&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Archival discovery and use ===&lt;br /&gt;
'''Full Day''' &lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Tim Shearer, UNC Chapel Hill, tshearer at email.unc.edu, &lt;br /&gt;
* Will Sexton, Duke, will.sexton at duke.edu&lt;br /&gt;
&lt;br /&gt;
This is a full day pre-conference about archival collections and will cover the intersections of archives, workflows, technologies, discovery, and use.&lt;br /&gt;
&lt;br /&gt;
Morning agenda: focused talks around (but not limited to) issues such as:&lt;br /&gt;
* Crowd-sourcing description to enhance collecitons&lt;br /&gt;
* Linked data and authority&lt;br /&gt;
* Mass digitization and sustainable workflows&lt;br /&gt;
* Digitized objects in context (images and other objects in finding aids)&lt;br /&gt;
* Too many cooks in the kitchen: versioning&lt;br /&gt;
* Global-, intra-, and inter- discovery of archival materials via finding aids &lt;br /&gt;
* and more...&lt;br /&gt;
&lt;br /&gt;
Afternoon agenda:  Focused talks around specific tools followed by general discussion, connections, opportunities, aspirations, and planning.&lt;br /&gt;
&lt;br /&gt;
Tool examples:&lt;br /&gt;
* Archivespace&lt;br /&gt;
* STEADy&lt;br /&gt;
* &amp;quot;RAMP&amp;quot; (Remixing Archival Metadata Project)&lt;br /&gt;
* OpenRefine&lt;br /&gt;
* Aeon&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
Morning:&lt;br /&gt;
* your name&lt;br /&gt;
&lt;br /&gt;
Afternoon:&lt;br /&gt;
* your name&lt;br /&gt;
&lt;br /&gt;
All day:&lt;br /&gt;
&lt;br /&gt;
# Josh Wilson&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===AV Content Slam===&lt;br /&gt;
'''Half-Day [morning]'''&lt;br /&gt;
Contacts:&lt;br /&gt;
* Kara Van Malssen, kara (at) avpreserve.com&lt;br /&gt;
* Lauren Sorenson, laurens (at) bavc.org&lt;br /&gt;
* Steven Villereal , villereal (at) gmail.com&lt;br /&gt;
A morning BarCamp/unconference for practitioners and coders who work with audiovisual content. The agenda will be attendee-driven, with a focus on sharing, synthesizing, and improving workflow strategies and documentation for software-based approaches to wrangling and providing access to audio and video content.&lt;br /&gt;
Possible topics of discussion might include:&lt;br /&gt;
* Use of format id and characterization/metadata extraction tools for AV&lt;br /&gt;
* Creating and using time-based metadata&lt;br /&gt;
* Managing (moving, fixity checking, etc) massive files (like uncompressed video)&lt;br /&gt;
For a better idea of the topics and concerns that have informed some past AV-themed events, check out the event wikis for [http://wiki.curatecamp.org/index.php/CURATEcamp_AVpres_2013 CURATEcamp AVpres 2013] as well as the [http://wiki.curatecamp.org/index.php/Association_of_Moving_Image_Archivists_%26_Digital_Library_Federation_Hack_Day_2013 AMIA/DLF 2013 Hack Day] .&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===OCLC Web Services Hackfest===&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Half-Day&amp;quot; [afternoon]&lt;br /&gt;
&lt;br /&gt;
Contact: Shelley Hostetler, Community Manager, Developer Network hostetls[at]oclc.org&lt;br /&gt;
&lt;br /&gt;
This half-day hackfest will explore some of the OCLC Developer Network web services. We will provide an overview of some of the common topics such as the general REST-based architecture for most services and how to use some new authentication clients. The group can then decide to take a deep dive into a particular API and/or write a client library for the community.&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Obey the Testing Goat!: Test Driven Web Development From The Ground Up===&lt;br /&gt;
'''Half-Day [tbd - probably afternoon]'''&lt;br /&gt;
* Contact [[User:Mredar|Mark Redar]], mredar[at]gmail.com&lt;br /&gt;
&lt;br /&gt;
Test driven development is a proven method for producing better quality code. But I've found it hard to follow a strict TDD methodology when starting new web projects. How do you write that first test when there is no code or web pages created yet.&lt;br /&gt;
&lt;br /&gt;
In this session, we will follow the excellent book [http://shop.oreilly.com/product/0636920029533.do &amp;quot;Test-Driven Web Development with Python&amp;quot;] to create a simple web site in Django following TDD from the first character typed. Come ready to code and test. No prior knowledge of python or Django required.&lt;br /&gt;
&lt;br /&gt;
By the end of this session, you should be able to  [http://www.obeythetestinggoat.com/ &amp;quot;Obey the Testing Goat&amp;quot;] from the start to finish for your next project.&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:&lt;br /&gt;
&lt;br /&gt;
* Charlie Morris (NCSU)&lt;br /&gt;
&lt;br /&gt;
===Summon Camp===&lt;br /&gt;
Placeholder by Tim McGeary for Gillian Cain (Serials Solutions)&lt;br /&gt;
Description to be provided by Gillian after account issues resolved. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
[[:Category:Code4Lib2014]]&lt;/div&gt;</summary>
		<author><name>Cwlown</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&amp;diff=40096</id>
		<title>2014 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&amp;diff=40096"/>
				<updated>2013-12-09T15:58:13Z</updated>
		
		<summary type="html">&lt;p&gt;Cwlown: /* Fail4Lib 2014 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Code4Lib 2014 Pre-Conference Proposals==&lt;br /&gt;
&lt;br /&gt;
= PROPOSALS ARE CLOSED : PLEASE DO NOT EDIT THIS PAGE =&lt;br /&gt;
&lt;br /&gt;
Proposals were accepted through December 6th, 2013.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Note===&lt;br /&gt;
Attendance at a pre-conference will require a small fee ''due at the time of conference registration.&lt;br /&gt;
 &lt;br /&gt;
Although this was specified in the email announcements relating to pre-conferences, it was not added to this page until December 2nd.  I (Adam C.) apologize for the omission and I hope this will not cause any &amp;quot;sticker shock.&amp;quot;  Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.&lt;br /&gt;
&lt;br /&gt;
Please put your pre-conference on the list in the following format:&lt;br /&gt;
&lt;br /&gt;
===NAME===&lt;br /&gt;
'''&amp;quot;Full-Day|Half-Day&amp;quot; [PREFERRED TIME]'''&lt;br /&gt;
&lt;br /&gt;
Description&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Drupal4lib Sub-con Barcamp===&lt;br /&gt;
=====Full Day=====&lt;br /&gt;
&lt;br /&gt;
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com&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;
This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).&lt;br /&gt;
&lt;br /&gt;
[[resources to help you learn drupal]]&lt;br /&gt;
&lt;br /&gt;
====Interested in Attending:====&lt;br /&gt;
&lt;br /&gt;
=====All Day=====&lt;br /&gt;
&lt;br /&gt;
* Renna Tuten &lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
&lt;br /&gt;
* Kevin Reiss&lt;br /&gt;
* Charlie Morris (NCSU) - glad to see this again this year!&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Open Refine Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot;'''&lt;br /&gt;
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com&lt;br /&gt;
&lt;br /&gt;
[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control&lt;br /&gt;
&lt;br /&gt;
The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. &lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&amp;lt;ol&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Adam Constabaris&lt;br /&gt;
&amp;lt;li&amp;gt;Ray Schwartz&lt;br /&gt;
&amp;lt;li&amp;gt;Jason Stirnaman&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Responsive Design Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day [Afternoon]&amp;quot;''' &lt;br /&gt;
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com&lt;br /&gt;
* Contact David Ward, University of Illinois, dh-ward@illinois.edu&lt;br /&gt;
&lt;br /&gt;
This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. &lt;br /&gt;
&lt;br /&gt;
Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
=== Intro to Blacklight ===&lt;br /&gt;
'''&amp;quot;Half-Day [Morning]&amp;quot;''' &lt;br /&gt;
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
* TA: Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
This session will be walk-through of the architecture of Blacklight, the community, and an introduction to building a Blacklight-based application. Each participant will have the opportunity to build a simple Blacklight application, and make basic customizations, while using a test-driven approach.&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;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Megan Kudzia&lt;br /&gt;
# Bret Davidson&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Cory Lown&lt;br /&gt;
&lt;br /&gt;
===Blacklight Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day [Afternoon]&amp;quot;''' &lt;br /&gt;
* Contact Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
&lt;br /&gt;
This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.&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 ).&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Kevin Reiss&lt;br /&gt;
# Megan Kudzia&lt;br /&gt;
# Erik Hatcher&lt;br /&gt;
&lt;br /&gt;
===RailsBridge: Intro to programming in Ruby on Rails===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
* Contact Justin Coyne, Data Curation Experts, justin@curationexperts.com&lt;br /&gt;
&lt;br /&gt;
Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! RailsBridge is a friendly place to get together and learn how to write some code.&lt;br /&gt;
&lt;br /&gt;
RailsBridge is a great workshop that opens the doors to projects like Blacklight and Hydra.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
1. Ayla Stein&lt;br /&gt;
&lt;br /&gt;
2. Heidi Dowding&lt;br /&gt;
&lt;br /&gt;
===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===&lt;br /&gt;
'''Full-Day'''&lt;br /&gt;
&lt;br /&gt;
Contact: &lt;br /&gt;
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com&lt;br /&gt;
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu&lt;br /&gt;
&lt;br /&gt;
This will be a full day session on project management.  We'll cover&lt;br /&gt;
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment&lt;br /&gt;
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets&lt;br /&gt;
* '''Executing the Project''' -- status meeting, status reports, issue management&lt;br /&gt;
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product&lt;br /&gt;
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Robin Dean&lt;br /&gt;
# Erin White&lt;br /&gt;
# Andrew Darby&lt;br /&gt;
&lt;br /&gt;
===Fail4Lib 2014===&lt;br /&gt;
'''Half Day [TBD, probably afternoon]'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Andreas Orphanides, akorphan (at) ncsu.edu&lt;br /&gt;
* Jason Casden, jmcasden (at) ncsu.edu&lt;br /&gt;
&lt;br /&gt;
The task of design (and the work that we do as library coders) is intimately tied to failure. Failures, both big and small, motivate us to create and improve. Failures are also occasionally the result of our work. Understanding and embracing failure, encouraging enlightened risk-taking, and seeking out opportunities to fail and learn are essential to success in our field. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be feared.&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
&lt;br /&gt;
* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?&lt;br /&gt;
* Confessionals, for those willing to share. Talk about your own experiences with rough starts, labor pains, and doomed projects in your own work: What can we learn from our own (and each others') failures?&lt;br /&gt;
* Group therapy. Let's talk about how to deal with risk management, failed projects, experimental endeavors, and more: How can we make ourselves, our colleagues, and our organizations more fault tolerant? How do we make sure we fail as productively as possible?&lt;br /&gt;
&lt;br /&gt;
''Interested in attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#Bret Davidson&lt;br /&gt;
#Mike Graves&lt;br /&gt;
#Ray Schwartz&lt;br /&gt;
#Cory Lown&lt;br /&gt;
&lt;br /&gt;
===CLLAM @ code4lib===&lt;br /&gt;
'''(Computational Linguistics for Libraries, Archives and Museums)'''&lt;br /&gt;
&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Douglas W. Oard (primary), oard (at) umd.edu &lt;br /&gt;
* Corey Harper, corey (dot) harper (at) nyu.edu&lt;br /&gt;
* Robert Sanderson, azaroth42 (at) gmail.com &lt;br /&gt;
* Robert Warren, rwarren (at) math.carleton.ca&lt;br /&gt;
&lt;br /&gt;
We will hack at the intersection of diverse content from Libraries, Archives and Museums and bleeding edge tools from computational linguistics for slicing and dicing that content. Did you just acquire the email archives of a startup company? Maybe you can automatically build an org chart. Have you got metadata in a slew of languages? Perhaps you can search it all using one query. Is name authority control for e-resources getting too costly? Let’s see if entity linking techniques can help. These are just a few teasers. &lt;br /&gt;
&lt;br /&gt;
There’ll be plenty of content and tools supplied, but please bring your own [data] too -- you’ll hack with it in new ways throughout the day. We’ll get started with some lightning talks on what we’ve brought,then we’ll break up into groups to experiment and work on the ideas that appeal. Three guaranteed outcomes: you’ll walk away with new ideas, new tools, and new people you’ll have met.&lt;br /&gt;
&lt;br /&gt;
''Interested in attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Devon Smith&lt;br /&gt;
# Kevin S. Clarke&lt;br /&gt;
&lt;br /&gt;
=== GeoHydra: Managing geospatial content ===&lt;br /&gt;
&lt;br /&gt;
'''Half-day [Afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Contact: Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Moderator: Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,&lt;br /&gt;
etc., all of which you want to integrate into your digital repository? In this&lt;br /&gt;
workshop, we will discuss how Hydra can provide discovery, delivery, and&lt;br /&gt;
management services for geospatial assets, as well as solicit questions about&lt;br /&gt;
your own GIS projects. We aim to help answer the following questions you might have about putting geospatial data into your Hydra-based digital library:&lt;br /&gt;
&lt;br /&gt;
* What are the types of geospatial data?&lt;br /&gt;
* How to dive into Hydra?&lt;br /&gt;
* How to model geospatial holdings with Hydra?&lt;br /&gt;
* How to discover and view geospatial data?&lt;br /&gt;
* How to build a geospatial data infrastructure?&lt;br /&gt;
* What are common approaches and problems?&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Esmé Cowles&lt;br /&gt;
&lt;br /&gt;
===Technology, Librarianship, and Gender: Moving the conversation forward===&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]&lt;br /&gt;
&lt;br /&gt;
'''Description'''&lt;br /&gt;
&lt;br /&gt;
Librarianship is largely made up of women, yet women are significantly underrepresented in tech positions, on any level, within libraries themselves. Why? What are we doing to encourage women to become more involved in STEM within librarianship? What kind of message are we sending when library technology keynotes remain almost resolutely male? How are we changing the face of technology, not only within libraries, but with the field itself? How are we training our staff and colleagues in the areas of fairness and removal of bias? Our vendors?&lt;br /&gt;
&lt;br /&gt;
Lots of tough questions.&lt;br /&gt;
&lt;br /&gt;
While the conversation has been going on via various blogs and articles within the last few years, it was given a public face at [http://infotoday.com/il2013/day.asp?day=Monday#session_D105 Internet Librarian 2013] where a panel of 7 (four women, three men) gave personal experiences on the above and then opened up the conversation to the audience. As eye opening and enriching the conversation was, a 45 minute panel was not enough. One thing remains clear: We need to keep the conversation moving forward and start making some radical changes in the way we think, act, and how we need to harness this to start making real changes within librarianship itself.&lt;br /&gt;
&lt;br /&gt;
Topics to include:  Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems,  mentoring, ally support, and more&lt;br /&gt;
&lt;br /&gt;
Those attending should expect: Begin with opening up the conversation of experiences and talking about what is most needed, spending remaining time putting together live, usable solutions to start implementing as well as pushing the conversation forward at local levels&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
=====All Day=====&lt;br /&gt;
1. Kate Kosturski&lt;br /&gt;
&lt;br /&gt;
2. Valerie Aurora&lt;br /&gt;
&lt;br /&gt;
3. Declan Fleming&lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
1. Shaun Ellis&lt;br /&gt;
&lt;br /&gt;
2. Jason Casden&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
1. Ayla Stein&lt;br /&gt;
&lt;br /&gt;
2. Heidi Dowding&lt;br /&gt;
&lt;br /&gt;
3. Coral Sheldon-Hess&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===FileAnalyzer: Rapid Development of File Manipulation Tasks===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
* Contact Terry Brady, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The FileAnalyzer (https://github.com/Georgetown-University-Libraries/File-Analyzer) is an application designed to solve a number of library automation challenges:&lt;br /&gt;
&lt;br /&gt;
* validating digitized and reformatted files&lt;br /&gt;
* validating vendor statistics for counter compliance&lt;br /&gt;
* preparing collections of digital files for archiving and ingest&lt;br /&gt;
* manipulating ILS import and export files&lt;br /&gt;
&lt;br /&gt;
The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census. After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform. Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.&lt;br /&gt;
&lt;br /&gt;
The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules. As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.&lt;br /&gt;
&lt;br /&gt;
The first half of this session will be targeted to potential users and developers.  The second half of the session will be targeted towards developers who are interested in developing custom rules for the application.&lt;br /&gt;
&lt;br /&gt;
''Session Overview''&lt;br /&gt;
* Overview of the application&lt;br /&gt;
* Running sample file tests/transformations through the application&lt;br /&gt;
* Compiling and building the application&lt;br /&gt;
* Coding a custom file processing task&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#Ray Schwartz&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Collecting social media data with Social Feed Manager===&lt;br /&gt;
'''Half-Day [Morning]'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Dan Chudnov, GW Libraries, dchud (at) gwu.edu&lt;br /&gt;
* Dan Kerchner, GW Libraries, kerchner (at) gwu.edu&lt;br /&gt;
* Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu&lt;br /&gt;
&lt;br /&gt;
Social media data is a popular material for research and a new format for building collections.  What does it take to collect meaningfully from Twitter, Tumblr, YouTube, Weibo, Facebook, and other sites?  We will:&lt;br /&gt;
* Introduce options for collections, including both high- and low-end commercial offerings. Discuss what it means to collect these resources, covering boundaries, policies, and workflows required to develop a social media collection program in your institution.&lt;br /&gt;
* Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them&lt;br /&gt;
* Help you get started using the free [http://gwu-libraries.github.io/social-feed-manager Social Feed Manager] (SFM) app we're developing at GW to create your first collections. We’ll demo its use and demo a clean install (those w/environments can follow along)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Declan Fleming&lt;br /&gt;
# Esmé Cowles&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Intro to Git ===&lt;br /&gt;
'''&amp;quot;Half-Day [tbd - probably afternoon]&amp;quot;''' &lt;br /&gt;
* Contact: Erin Fahy, Stanford University, efahy at stanford.edu&lt;br /&gt;
* TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu&lt;br /&gt;
&lt;br /&gt;
This session will cover the fundamentals of git by discussing/going through (time allowing):&lt;br /&gt;
* what is a distributed version control system&lt;br /&gt;
* what is git and github&lt;br /&gt;
* initializing a repo on a remote server/github&lt;br /&gt;
* cloning an existing repo&lt;br /&gt;
* creating a branch&lt;br /&gt;
* contributing code to a repo&lt;br /&gt;
* how to handle merge conflicts&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Archival discovery and use ===&lt;br /&gt;
'''Full Day''' &lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Tim Shearer, UNC Chapel Hill, tshearer at email.unc.edu, &lt;br /&gt;
* Will Sexton, Duke, will.sexton at duke.edu&lt;br /&gt;
&lt;br /&gt;
This is a full day pre-conference about archival collections and will cover the intersections of archives, workflows, technologies, discovery, and use.&lt;br /&gt;
&lt;br /&gt;
Morning agenda: focused talks around (but not limited to) issues such as:&lt;br /&gt;
* Crowd-sourcing description to enhance collecitons&lt;br /&gt;
* Linked data and authority&lt;br /&gt;
* Mass digitization and sustainable workflows&lt;br /&gt;
* Digitized objects in context (images and other objects in finding aids)&lt;br /&gt;
* Too many cooks in the kitchen: versioning&lt;br /&gt;
* Global-, intra-, and inter- discovery of archival materials via finding aids &lt;br /&gt;
* and more...&lt;br /&gt;
&lt;br /&gt;
Afternoon agenda:  Focused talks around specific tools followed by general discussion, connections, opportunities, aspirations, and planning.&lt;br /&gt;
&lt;br /&gt;
Tool examples:&lt;br /&gt;
* Archivespace&lt;br /&gt;
* STEADy&lt;br /&gt;
* &amp;quot;RAMP&amp;quot; (Remixing Archival Metadata Project)&lt;br /&gt;
* OpenRefine&lt;br /&gt;
* Aeon&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
Morning:&lt;br /&gt;
* your name&lt;br /&gt;
&lt;br /&gt;
Afternoon:&lt;br /&gt;
* your name&lt;br /&gt;
&lt;br /&gt;
All day:&lt;br /&gt;
&lt;br /&gt;
# Josh Wilson&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===AV Content Slam===&lt;br /&gt;
'''Half-Day [morning]'''&lt;br /&gt;
Contacts:&lt;br /&gt;
* Kara Van Malssen, kara (at) avpreserve.com&lt;br /&gt;
* Lauren Sorenson, laurens (at) bavc.org&lt;br /&gt;
* Steven Villereal , villereal (at) gmail.com&lt;br /&gt;
A morning BarCamp/unconference for practitioners and coders who work with audiovisual content. The agenda will be attendee-driven, with a focus on sharing, synthesizing, and improving workflow strategies and documentation for software-based approaches to wrangling and providing access to audio and video content.&lt;br /&gt;
Possible topics of discussion might include:&lt;br /&gt;
* Use of format id and characterization/metadata extraction tools for AV&lt;br /&gt;
* Creating and using time-based metadata&lt;br /&gt;
* Managing (moving, fixity checking, etc) massive files (like uncompressed video)&lt;br /&gt;
For a better idea of the topics and concerns that have informed some past AV-themed events, check out the event wikis for [http://wiki.curatecamp.org/index.php/CURATEcamp_AVpres_2013 CURATEcamp AVpres 2013] as well as the [http://wiki.curatecamp.org/index.php/Association_of_Moving_Image_Archivists_%26_Digital_Library_Federation_Hack_Day_2013 AMIA/DLF 2013 Hack Day] .&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===OCLC Web Services Hackfest===&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Half-Day&amp;quot; [afternoon]&lt;br /&gt;
&lt;br /&gt;
Contact: Shelley Hostetler, Community Manager, Developer Network hostetls[at]oclc.org&lt;br /&gt;
&lt;br /&gt;
This half-day hackfest will explore some of the OCLC Developer Network web services. We will provide an overview of some of the common topics such as the general REST-based architecture for most services and how to use some new authentication clients. The group can then decide to take a deep dive into a particular API and/or write a client library for the community.&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Obey the Testing Goat!: Test Driven Web Development From The Ground Up===&lt;br /&gt;
'''Half-Day [tbd - probably afternoon]'''&lt;br /&gt;
* Contact [[User:Mredar|Mark Redar]], mredar[at]gmail.com&lt;br /&gt;
&lt;br /&gt;
Test driven development is a proven method for producing better quality code. But I've found it hard to follow a strict TDD methodology when starting new web projects. How do you write that first test when there is no code or web pages created yet.&lt;br /&gt;
&lt;br /&gt;
In this session, we will follow the excellent book [http://shop.oreilly.com/product/0636920029533.do &amp;quot;Test-Driven Web Development with Python&amp;quot;] to create a simple web site in Django following TDD from the first character typed. Come ready to code and test. No prior knowledge of python or Django required.&lt;br /&gt;
&lt;br /&gt;
By the end of this session, you should be able to  [http://www.obeythetestinggoat.com/ &amp;quot;Obey the Testing Goat&amp;quot;] from the start to finish for your next project.&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:&lt;br /&gt;
&lt;br /&gt;
* Charlie Morris (NCSU)&lt;br /&gt;
&lt;br /&gt;
===Summon Camp===&lt;br /&gt;
Placeholder by Tim McGeary for Gillian Cain (Serials Solutions)&lt;br /&gt;
Description to be provided by Gillian after account issues resolved. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
[[:Category:Code4Lib2014]]&lt;/div&gt;</summary>
		<author><name>Cwlown</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&amp;diff=40089</id>
		<title>2014 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&amp;diff=40089"/>
				<updated>2013-12-09T15:27:06Z</updated>
		
		<summary type="html">&lt;p&gt;Cwlown: /* Intro to Blacklight */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Code4Lib 2014 Pre-Conference Proposals==&lt;br /&gt;
&lt;br /&gt;
= PROPOSALS ARE CLOSED : PLEASE DO NOT EDIT THIS PAGE =&lt;br /&gt;
&lt;br /&gt;
Proposals were accepted through December 6th, 2013.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Note===&lt;br /&gt;
Attendance at a pre-conference will require a small fee ''due at the time of conference registration.&lt;br /&gt;
 &lt;br /&gt;
Although this was specified in the email announcements relating to pre-conferences, it was not added to this page until December 2nd.  I (Adam C.) apologize for the omission and I hope this will not cause any &amp;quot;sticker shock.&amp;quot;  Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.&lt;br /&gt;
&lt;br /&gt;
Please put your pre-conference on the list in the following format:&lt;br /&gt;
&lt;br /&gt;
===NAME===&lt;br /&gt;
'''&amp;quot;Full-Day|Half-Day&amp;quot; [PREFERRED TIME]'''&lt;br /&gt;
&lt;br /&gt;
Description&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Drupal4lib Sub-con Barcamp===&lt;br /&gt;
=====Full Day=====&lt;br /&gt;
&lt;br /&gt;
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com&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;
This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).&lt;br /&gt;
&lt;br /&gt;
[[resources to help you learn drupal]]&lt;br /&gt;
&lt;br /&gt;
====Interested in Attending:====&lt;br /&gt;
&lt;br /&gt;
=====All Day=====&lt;br /&gt;
&lt;br /&gt;
* Renna Tuten &lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
&lt;br /&gt;
* Kevin Reiss&lt;br /&gt;
* Charlie Morris (NCSU) - glad to see this again this year!&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Open Refine Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot;'''&lt;br /&gt;
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com&lt;br /&gt;
&lt;br /&gt;
[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control&lt;br /&gt;
&lt;br /&gt;
The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. &lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
Adam Constabaris&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Responsive Design Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day [Afternoon]&amp;quot;''' &lt;br /&gt;
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com&lt;br /&gt;
* Contact David Ward, University of Illinois, dh-ward@illinois.edu&lt;br /&gt;
&lt;br /&gt;
This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. &lt;br /&gt;
&lt;br /&gt;
Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
=== Intro to Blacklight ===&lt;br /&gt;
'''&amp;quot;Half-Day [Morning]&amp;quot;''' &lt;br /&gt;
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
* TA: Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
This session will be walk-through of the architecture of Blacklight, the community, and an introduction to building a Blacklight-based application. Each participant will have the opportunity to build a simple Blacklight application, and make basic customizations, while using a test-driven approach.&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;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Megan Kudzia&lt;br /&gt;
# Bret Davidson&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Cory Lown&lt;br /&gt;
&lt;br /&gt;
===Blacklight Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day [Afternoon]&amp;quot;''' &lt;br /&gt;
* Contact Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
&lt;br /&gt;
This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.&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 ).&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Kevin Reiss&lt;br /&gt;
# Megan Kudzia&lt;br /&gt;
# Erik Hatcher&lt;br /&gt;
&lt;br /&gt;
===RailsBridge: Intro to programming in Ruby on Rails===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
* Contact Justin Coyne, Data Curation Experts, justin@curationexperts.com&lt;br /&gt;
&lt;br /&gt;
Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! RailsBridge is a friendly place to get together and learn how to write some code.&lt;br /&gt;
&lt;br /&gt;
RailsBridge is a great workshop that opens the doors to projects like Blacklight and Hydra.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
1. Ayla Stein&lt;br /&gt;
&lt;br /&gt;
2. Heidi Dowding&lt;br /&gt;
&lt;br /&gt;
===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===&lt;br /&gt;
'''Full-Day'''&lt;br /&gt;
&lt;br /&gt;
Contact: &lt;br /&gt;
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com&lt;br /&gt;
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu&lt;br /&gt;
&lt;br /&gt;
This will be a full day session on project management.  We'll cover&lt;br /&gt;
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment&lt;br /&gt;
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets&lt;br /&gt;
* '''Executing the Project''' -- status meeting, status reports, issue management&lt;br /&gt;
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product&lt;br /&gt;
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Robin Dean&lt;br /&gt;
# Erin White&lt;br /&gt;
# Andrew Darby&lt;br /&gt;
&lt;br /&gt;
===Fail4Lib 2014===&lt;br /&gt;
'''Half Day [TBD, probably afternoon]'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Andreas Orphanides, akorphan (at) ncsu.edu&lt;br /&gt;
* Jason Casden, jmcasden (at) ncsu.edu&lt;br /&gt;
&lt;br /&gt;
The task of design (and the work that we do as library coders) is intimately tied to failure. Failures, both big and small, motivate us to create and improve. Failures are also occasionally the result of our work. Understanding and embracing failure, encouraging enlightened risk-taking, and seeking out opportunities to fail and learn are essential to success in our field. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be feared.&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
&lt;br /&gt;
* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?&lt;br /&gt;
* Confessionals, for those willing to share. Talk about your own experiences with rough starts, labor pains, and doomed projects in your own work: What can we learn from our own (and each others') failures?&lt;br /&gt;
* Group therapy. Let's talk about how to deal with risk management, failed projects, experimental endeavors, and more: How can we make ourselves, our colleagues, and our organizations more fault tolerant? How do we make sure we fail as productively as possible?&lt;br /&gt;
&lt;br /&gt;
''Interested in attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#Bret Davidson&lt;br /&gt;
#Mike Graves&lt;br /&gt;
&lt;br /&gt;
===CLLAM @ code4lib===&lt;br /&gt;
'''(Computational Linguistics for Libraries, Archives and Museums)'''&lt;br /&gt;
&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Douglas W. Oard (primary), oard (at) umd.edu &lt;br /&gt;
* Corey Harper, corey (dot) harper (at) nyu.edu&lt;br /&gt;
* Robert Sanderson, azaroth42 (at) gmail.com &lt;br /&gt;
* Robert Warren, rwarren (at) math.carleton.ca&lt;br /&gt;
&lt;br /&gt;
We will hack at the intersection of diverse content from Libraries, Archives and Museums and bleeding edge tools from computational linguistics for slicing and dicing that content. Did you just acquire the email archives of a startup company? Maybe you can automatically build an org chart. Have you got metadata in a slew of languages? Perhaps you can search it all using one query. Is name authority control for e-resources getting too costly? Let’s see if entity linking techniques can help. These are just a few teasers. &lt;br /&gt;
&lt;br /&gt;
There’ll be plenty of content and tools supplied, but please bring your own [data] too -- you’ll hack with it in new ways throughout the day. We’ll get started with some lightning talks on what we’ve brought,then we’ll break up into groups to experiment and work on the ideas that appeal. Three guaranteed outcomes: you’ll walk away with new ideas, new tools, and new people you’ll have met.&lt;br /&gt;
&lt;br /&gt;
''Interested in attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Devon Smith&lt;br /&gt;
# Kevin S. Clarke&lt;br /&gt;
&lt;br /&gt;
=== GeoHydra: Managing geospatial content ===&lt;br /&gt;
&lt;br /&gt;
'''Half-day [Afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Contact: Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Moderator: Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,&lt;br /&gt;
etc., all of which you want to integrate into your digital repository? In this&lt;br /&gt;
workshop, we will discuss how Hydra can provide discovery, delivery, and&lt;br /&gt;
management services for geospatial assets, as well as solicit questions about&lt;br /&gt;
your own GIS projects. We aim to help answer the following questions you might have about putting geospatial data into your Hydra-based digital library:&lt;br /&gt;
&lt;br /&gt;
* What are the types of geospatial data?&lt;br /&gt;
* How to dive into Hydra?&lt;br /&gt;
* How to model geospatial holdings with Hydra?&lt;br /&gt;
* How to discover and view geospatial data?&lt;br /&gt;
* How to build a geospatial data infrastructure?&lt;br /&gt;
* What are common approaches and problems?&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Esmé Cowles&lt;br /&gt;
&lt;br /&gt;
===Technology, Librarianship, and Gender: Moving the conversation forward===&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]&lt;br /&gt;
&lt;br /&gt;
'''Description'''&lt;br /&gt;
&lt;br /&gt;
Librarianship is largely made up of women, yet women are significantly underrepresented in tech positions, on any level, within libraries themselves. Why? What are we doing to encourage women to become more involved in STEM within librarianship? What kind of message are we sending when library technology keynotes remain almost resolutely male? How are we changing the face of technology, not only within libraries, but with the field itself? How are we training our staff and colleagues in the areas of fairness and removal of bias? Our vendors?&lt;br /&gt;
&lt;br /&gt;
Lots of tough questions.&lt;br /&gt;
&lt;br /&gt;
While the conversation has been going on via various blogs and articles within the last few years, it was given a public face at [http://infotoday.com/il2013/day.asp?day=Monday#session_D105 Internet Librarian 2013] where a panel of 7 (four women, three men) gave personal experiences on the above and then opened up the conversation to the audience. As eye opening and enriching the conversation was, a 45 minute panel was not enough. One thing remains clear: We need to keep the conversation moving forward and start making some radical changes in the way we think, act, and how we need to harness this to start making real changes within librarianship itself.&lt;br /&gt;
&lt;br /&gt;
Topics to include:  Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems,  mentoring, ally support, and more&lt;br /&gt;
&lt;br /&gt;
Those attending should expect: Begin with opening up the conversation of experiences and talking about what is most needed, spending remaining time putting together live, usable solutions to start implementing as well as pushing the conversation forward at local levels&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
=====All Day=====&lt;br /&gt;
1. Kate Kosturski&lt;br /&gt;
&lt;br /&gt;
2. Valerie Aurora&lt;br /&gt;
&lt;br /&gt;
3. Declan Fleming&lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
1. Shaun Ellis&lt;br /&gt;
&lt;br /&gt;
2. Jason Casden&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
1. Ayla Stein&lt;br /&gt;
&lt;br /&gt;
2. Heidi Dowding&lt;br /&gt;
&lt;br /&gt;
3. Coral Sheldon-Hess&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===FileAnalyzer: Rapid Development of File Manipulation Tasks===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
* Contact Terry Brady, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The FileAnalyzer (https://github.com/Georgetown-University-Libraries/File-Analyzer) is an application designed to solve a number of library automation challenges:&lt;br /&gt;
&lt;br /&gt;
* validating digitized and reformatted files&lt;br /&gt;
* validating vendor statistics for counter compliance&lt;br /&gt;
* preparing collections of digital files for archiving and ingest&lt;br /&gt;
* manipulating ILS import and export files&lt;br /&gt;
&lt;br /&gt;
The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census. After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform. Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.&lt;br /&gt;
&lt;br /&gt;
The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules. As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.&lt;br /&gt;
&lt;br /&gt;
The first half of this session will be targeted to potential users and developers.  The second half of the session will be targeted towards developers who are interested in developing custom rules for the application.&lt;br /&gt;
&lt;br /&gt;
''Session Overview''&lt;br /&gt;
* Overview of the application&lt;br /&gt;
* Running sample file tests/transformations through the application&lt;br /&gt;
* Compiling and building the application&lt;br /&gt;
* Coding a custom file processing task&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Collecting social media data with Social Feed Manager===&lt;br /&gt;
'''Half-Day [Morning]'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Dan Chudnov, GW Libraries, dchud (at) gwu.edu&lt;br /&gt;
* Dan Kerchner, GW Libraries, kerchner (at) gwu.edu&lt;br /&gt;
* Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu&lt;br /&gt;
&lt;br /&gt;
Social media data is a popular material for research and a new format for building collections.  What does it take to collect meaningfully from Twitter, Tumblr, YouTube, Weibo, Facebook, and other sites?  We will:&lt;br /&gt;
* Introduce options for collections, including both high- and low-end commercial offerings. Discuss what it means to collect these resources, covering boundaries, policies, and workflows required to develop a social media collection program in your institution.&lt;br /&gt;
* Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them&lt;br /&gt;
* Help you get started using the free [http://gwu-libraries.github.io/social-feed-manager Social Feed Manager] (SFM) app we're developing at GW to create your first collections. We’ll demo its use and demo a clean install (those w/environments can follow along)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Declan Fleming&lt;br /&gt;
# Esmé Cowles&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Intro to Git ===&lt;br /&gt;
'''&amp;quot;Half-Day [tbd - probably afternoon]&amp;quot;''' &lt;br /&gt;
* Contact: Erin Fahy, Stanford University, efahy at stanford.edu&lt;br /&gt;
* TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu&lt;br /&gt;
&lt;br /&gt;
This session will cover the fundamentals of git by discussing/going through (time allowing):&lt;br /&gt;
* what is a distributed version control system&lt;br /&gt;
* what is git and github&lt;br /&gt;
* initializing a repo on a remote server/github&lt;br /&gt;
* cloning an existing repo&lt;br /&gt;
* creating a branch&lt;br /&gt;
* contributing code to a repo&lt;br /&gt;
* how to handle merge conflicts&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Archival discovery and use ===&lt;br /&gt;
'''Full Day''' &lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Tim Shearer, UNC Chapel Hill, tshearer at email.unc.edu, &lt;br /&gt;
* Will Sexton, Duke, will.sexton at duke.edu&lt;br /&gt;
&lt;br /&gt;
This is a full day pre-conference about archival collections and will cover the intersections of archives, workflows, technologies, discovery, and use.&lt;br /&gt;
&lt;br /&gt;
Morning agenda: focused talks around (but not limited to) issues such as:&lt;br /&gt;
* Crowd-sourcing description to enhance collecitons&lt;br /&gt;
* Linked data and authority&lt;br /&gt;
* Mass digitization and sustainable workflows&lt;br /&gt;
* Digitized objects in context (images and other objects in finding aids)&lt;br /&gt;
* Too many cooks in the kitchen: versioning&lt;br /&gt;
* Global-, intra-, and inter- discovery of archival materials via finding aids &lt;br /&gt;
* and more...&lt;br /&gt;
&lt;br /&gt;
Afternoon agenda:  Focused talks around specific tools followed by general discussion, connections, opportunities, aspirations, and planning.&lt;br /&gt;
&lt;br /&gt;
Tool examples:&lt;br /&gt;
* Archivespace&lt;br /&gt;
* STEADy&lt;br /&gt;
* &amp;quot;RAMP&amp;quot; (Remixing Archival Metadata Project)&lt;br /&gt;
* OpenRefine&lt;br /&gt;
* Aeon&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
Morning:&lt;br /&gt;
* your name&lt;br /&gt;
&lt;br /&gt;
Afternoon:&lt;br /&gt;
* your name&lt;br /&gt;
&lt;br /&gt;
All day:&lt;br /&gt;
&lt;br /&gt;
# Josh Wilson&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===AV Content Slam===&lt;br /&gt;
'''Half-Day [morning]'''&lt;br /&gt;
Contacts:&lt;br /&gt;
* Kara Van Malssen, kara (at) avpreserve.com&lt;br /&gt;
* Lauren Sorenson, laurens (at) bavc.org&lt;br /&gt;
* Steven Villereal , villereal (at) gmail.com&lt;br /&gt;
A morning BarCamp/unconference for practitioners and coders who work with audiovisual content. The agenda will be attendee-driven, with a focus on sharing, synthesizing, and improving workflow strategies and documentation for software-based approaches to wrangling and providing access to audio and video content.&lt;br /&gt;
Possible topics of discussion might include:&lt;br /&gt;
* Use of format id and characterization/metadata extraction tools for AV&lt;br /&gt;
* Creating and using time-based metadata&lt;br /&gt;
* Managing (moving, fixity checking, etc) massive files (like uncompressed video)&lt;br /&gt;
For a better idea of the topics and concerns that have informed some past AV-themed events, check out the event wikis for [http://wiki.curatecamp.org/index.php/CURATEcamp_AVpres_2013 CURATEcamp AVpres 2013] as well as the [http://wiki.curatecamp.org/index.php/Association_of_Moving_Image_Archivists_%26_Digital_Library_Federation_Hack_Day_2013 AMIA/DLF 2013 Hack Day] .&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===OCLC Web Services Hackfest===&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Half-Day&amp;quot; [afternoon]&lt;br /&gt;
&lt;br /&gt;
Contact: Shelley Hostetler, Community Manager, Developer Network hostetls[at]oclc.org&lt;br /&gt;
&lt;br /&gt;
This half-day hackfest will explore some of the OCLC Developer Network web services. We will provide an overview of some of the common topics such as the general REST-based architecture for most services and how to use some new authentication clients. The group can then decide to take a deep dive into a particular API and/or write a client library for the community.&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Obey the Testing Goat!: Test Driven Web Development From The Ground Up===&lt;br /&gt;
'''Half-Day [tbd - probably afternoon]'''&lt;br /&gt;
* Contact [[User:Mredar|Mark Redar]], mredar[at]gmail.com&lt;br /&gt;
&lt;br /&gt;
Test driven development is a proven method for producing better quality code. But I've found it hard to follow a strict TDD methodology when starting new web projects. How do you write that first test when there is no code or web pages created yet.&lt;br /&gt;
&lt;br /&gt;
In this session, we will follow the excellent book [http://shop.oreilly.com/product/0636920029533.do &amp;quot;Test-Driven Web Development with Python&amp;quot;] to create a simple web site in Django following TDD from the first character typed. Come ready to code and test. No prior knowledge of python or Django required.&lt;br /&gt;
&lt;br /&gt;
By the end of this session, you should be able to  [http://www.obeythetestinggoat.com/ &amp;quot;Obey the Testing Goat&amp;quot;] from the start to finish for your next project.&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:&lt;br /&gt;
&lt;br /&gt;
* Charlie Morris (NCSU)&lt;br /&gt;
&lt;br /&gt;
===Summon Camp===&lt;br /&gt;
Placeholder by Tim McGeary for Gillian Cain (Serials Solutions)&lt;br /&gt;
Description to be provided by Gillian after account issues resolved. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
[[:Category:Code4Lib2014]]&lt;/div&gt;</summary>
		<author><name>Cwlown</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_Prepared_Talk_Proposals&amp;diff=39779</id>
		<title>2014 Prepared Talk Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_Prepared_Talk_Proposals&amp;diff=39779"/>
				<updated>2013-11-07T15:41:16Z</updated>
		
		<summary type="html">&lt;p&gt;Cwlown: /* The Why and How of Very Large Displays in Libraries. */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==2014 Prepared Talk Proposals==&lt;br /&gt;
&lt;br /&gt;
'''Proposals for Prepared Talks:'''&lt;br /&gt;
&lt;br /&gt;
Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:&lt;br /&gt;
 &lt;br /&gt;
* ''Projects'' you've worked on which incorporate innovative implementation of existing technologies and/or development of new software&lt;br /&gt;
* ''Tools and technologies'' – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)&lt;br /&gt;
* ''Technical issues'' - Big issues in library technology that should be addressed or better understood&lt;br /&gt;
* ''Relevant non-technical issues'' – Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc.&lt;br /&gt;
&lt;br /&gt;
'''To Propose a Talk'''&lt;br /&gt;
* Log in to the wiki in order to submit a proposal. If you are not already registered, follow the instructions to do so.&lt;br /&gt;
* Provide a title and brief (500 words or fewer) description of your proposed talk.&lt;br /&gt;
* If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist us in opening the conference to new presenters.&lt;br /&gt;
&lt;br /&gt;
As in past years, the Code4Lib community will vote on proposals that they would like to see included in the program. This year, however, only the top 10 proposals will be guaranteed a slot at the conference. Additional presentations will be selected by the Program Committee in an effort to ensure diversity in program content. Community votes will, of course, still weigh heavily in these decisions.&lt;br /&gt;
&lt;br /&gt;
Presenters whose proposals are selected for inclusion in the program will be guaranteed an opportunity to register for the conference. The standard conference registration fee will still apply.&lt;br /&gt;
&lt;br /&gt;
''Proposals can be submitted through '''Friday, November 8, 2013, at 5pm PST'''''. Voting will commence on November 18, 2013 and continue through December 6, 2013. The final line-up of presentations will be announced in early January, 2014.&lt;br /&gt;
&lt;br /&gt;
'''Talk Proposals'''&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Using Drupal to drive alternative presentation systems ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Recently, we have been building systems that use angular.js, Rails, or other systems for presentation, while leveraging Drupal's sophisticated content management capabilities on the back end.&lt;br /&gt;
&lt;br /&gt;
So far, these have been one-way systems, but as we move to Drupal 8 we are beginning to explore ways to further decouple the presentation and CMS functions.&lt;br /&gt;
&lt;br /&gt;
== A Book, a Web Browser and a Tablet: How Bibliotheca Alexandrina's Book Viewer Framework Makes It Possible ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Mohammed.abuouda|Mohammed Abu ouda]], Bibliotheca Alexandrina (The new Library of Alexandria)&lt;br /&gt;
&lt;br /&gt;
A lot of institutions around the world are engaged in multiple digitization projects aiming at preserving the human knowledge present in books and availing them through multiple channels to people around the whole globe. These efforts will sure help close the digital gap particularly with the arrival of affordable e-readers, mobile phones and network coverage. However, the digital reading experience has not yet arrived to its maximum potential. Many readers miss features they like in their good old books and wish to find them in their digital counterpart. In an attempt to create a unique digital reading experience, Bibliotheca Alexandria (BA) created a flexible book viewing framework that is currently used to access its current collection of more than 300,000 digital books in five different languages which includes the largest collection of digitized Arabic books.&lt;br /&gt;
&lt;br /&gt;
Using open source tools, BA used the framework to develop a modular book viewer that can be deployed in different environments and is currently at the heart of various BA projects. The Book viewer provides several features creating a more natural reading experience. As with physical books, the reader can now personalize the books he reads by adding annotations like highlights, underlines and sticky notes to capture his thoughts and ideas in addition to being able to share the book with friends on social networks. The reader can perform a search across the content of the book receiving highlighted search results within the pages of the book. More features can be further added to the book viewer through its plugin architecture.&lt;br /&gt;
&lt;br /&gt;
== Structured data NOW: seeding schema.org in library systems ==&lt;br /&gt;
 &lt;br /&gt;
* [http://coffeecode.net Dan Scott], Laurentian University&lt;br /&gt;
** Previous code4lib presentations: [https://archive.org/details/code4lib.conf.2008.pres.CouchDBsacrilege CouchDB is sacrilege... mmm, delicious sacrilege] at Code4Lib 2008&lt;br /&gt;
&lt;br /&gt;
The semantic web, linked data, and structured data are all fantastic ideas with a barrier imposed by implementation constraints. If their system does not allow customizations, or the institution lacks skilled human resources, it does not matter how enthused a given library might be about publishing structured data... it will not happen. However, if the software in use simply publishes structured data by default, then the web will be populated for free. Really! No extra resources necessary.&lt;br /&gt;
&lt;br /&gt;
This presentation highlights Dan's work with systems such as Evergreen, Koha, and VuFind to enable the publication of schema.org structured data out-of-the-box. Along the way, we reflect the current state of the W3C Schema.org Bibliographic Extension community group efforts to shape the evolution of the schema.org vocabulary. Finally, hold on tight as we contemplate next steps and the possibilities of a world where structured data is the norm on the web.&lt;br /&gt;
&lt;br /&gt;
== Towards Pasta Code Nirvana: Using JavaScript MVC to Fill Your Programming Ravioli ==&lt;br /&gt;
&lt;br /&gt;
* Bret Davidson, North Carolina State University Libraries, bret_davidson@ncsu.edu&lt;br /&gt;
** Previous Code4Lib Presentations: [http://wiki.code4lib.org/index.php/2013_talks_proposals#Data-Driven_Documents:_Visualizing_library_data_with_D3.js Visualizing library data with D3.js] at Code4Lib 2013&lt;br /&gt;
&lt;br /&gt;
JavaScript MVC frameworks are ushering in a golden age of robust and responsive web applications that take advantage of evergreen browsers, performant JS engines, and the unprecedented reach provided by billions of personal computing devices. The web browser has emerged as the world’s most popular application runtime and the complexity[1] and scope of JavaScript applications has exploded accordingly. Server-side web frameworks like Rails and Django have helped developers adhere to best practices like modularity, dependency injection, and unit testing for years, practices that are now being applied to JavaScript development through projects like Backbone[2], Ember[3], and Angular[4].&lt;br /&gt;
&lt;br /&gt;
This talk will discuss the issues JavaScript MVC frameworks are trying to solve, common features like data binding, implications for the future of web development[5], and the appropriateness of JavaScript MVC for library applications.&lt;br /&gt;
&lt;br /&gt;
*[1]http://en.wikipedia.org/wiki/Spaghetti_code&lt;br /&gt;
*[2]http://backbonejs.org&lt;br /&gt;
*[3]http://emberjs.com&lt;br /&gt;
*[4]http://angularjs.org&lt;br /&gt;
*[5]http://tomdale.net/2013/09/progressive-enhancement-is-dead/&lt;br /&gt;
&lt;br /&gt;
== WebSockets for Real-Time and Interactive Interfaces ==&lt;br /&gt;
&lt;br /&gt;
* [http://ronallo.com Jason Ronallo], NCSU Libraries, jason_ronallo@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Previous Code4Lib presentations:&lt;br /&gt;
* [http://code4lib.org/conference/2012/ronallo HTML5 Microdata and Schema.org] 2012&lt;br /&gt;
* [http://code4lib.org/conference/2013/ronallo HTML5 Video Now!] 2013&lt;br /&gt;
&lt;br /&gt;
Watching the Google Analytics Real-Time dashboard for the first time was mesmerizing. As soon as someone visited a site, I could see what page they were on. For a digital collections site with a lot of images, it was fun to see what visitors were looking at. But getting from Google Analytics to the image or other content of what was currently being viewed was cumbersome. The real-time experience was something I wanted share with others. I'll show you how I used a WebSocket service to create a real-time interface to digital collections.&lt;br /&gt;
&lt;br /&gt;
In the Hunt Library at NCSU we have some large video walls. I wanted to make HTML-based exhibits that featured viewer interactions. I'll show you how I converted Listen to Wikipedia [1] into an bring-your-own-device interactive exhibit. With WebSockets any HTML page can be remote controlled by any internet connected device.&lt;br /&gt;
&lt;br /&gt;
I will attempt to include real-time audience participation.&lt;br /&gt;
&lt;br /&gt;
[1] http://listen.hatnote.com/&lt;br /&gt;
&lt;br /&gt;
== Rapid Development of Automated Tasks with the File Analyzer ==&lt;br /&gt;
&lt;br /&gt;
* Terry Brady, Georgetown University Libraries, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Libraries have customized the File Analyzer and Metadata Harvester application (https://github.com/Georgetown-University-Libraries/File-Analyzer) to solve a number of library automation challenges:&lt;br /&gt;
* validating digitized and reformatted files&lt;br /&gt;
* validating vendor statistics for counter compliance&lt;br /&gt;
* preparing collections of digital files for archiving and ingest&lt;br /&gt;
* manipulating ILS import and export files&lt;br /&gt;
&lt;br /&gt;
The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census.  After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform.  Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.&lt;br /&gt;
&lt;br /&gt;
The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules.  As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.&lt;br /&gt;
&lt;br /&gt;
Learn about the functionality that is available for download, how you can use this tool to automate workflows from digital collections to ILS ingests to electronic resources statistics and also discuss the opportunities to collaborate on enhancements to this application!&lt;br /&gt;
&lt;br /&gt;
== GeoHydra: How to Build a Geospatial Digital Library with Fedora ==&lt;br /&gt;
 &lt;br /&gt;
* [http://stanford.edu/~drh Darren Hardy], Stanford University, drh@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Geographically-rich data are exploding and putting fear in those trying to&lt;br /&gt;
tackle integrating them into existing digital library infrastructures.&lt;br /&gt;
Building a spatial data infrastructure that integrates with your digital&lt;br /&gt;
library infrastructure need not be a daunting task. We have successfully&lt;br /&gt;
deployed a geospatial digital library infrastructure using Fedora and&lt;br /&gt;
open-source geospatial software [1]. We'll discuss the primary design&lt;br /&gt;
decisions and technologies that led to a production deployment within a few&lt;br /&gt;
months. Briefly, our architecture revolves around discovery, delivery, and&lt;br /&gt;
metadata pipelines using open-source OpenGeoPortal [2], Solr [3], GeoServer&lt;br /&gt;
[4], PostGIS [5], and GeoNetwork [6] technologies, plus the proprietary ESRI&lt;br /&gt;
ArcMap [7] -- the GIS industry's workhorse. Finally, we'll discuss the key&lt;br /&gt;
skillsets needed to build and maintain a spatial data infrastructure.&lt;br /&gt;
&lt;br /&gt;
[1] http://foss4g.org&lt;br /&gt;
[2] http://opengeoportal.org&lt;br /&gt;
[3] http://lucene.apache.org/solr&lt;br /&gt;
[4] http://geoserver.org&lt;br /&gt;
[5] http://postgis.net&lt;br /&gt;
[6] http://geonetwork-opensource.org&lt;br /&gt;
[7] http://esri.com&lt;br /&gt;
&lt;br /&gt;
==Under the Hood of Hadoop Processing at OCLC Research ==&lt;br /&gt;
&lt;br /&gt;
[http://roytennant.com/ Roy Tennant]&lt;br /&gt;
&lt;br /&gt;
* Previous Code4Lib presentations: 2006: &amp;quot;The Case for Code4Lib 501c(3)&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[http://hadoop.apache.org/ Apache Hadoop] is widely used by Yahoo!, Google, and many others to process massive amounts of data quickly. OCLC Research uses a 40-node compute cluster with Hadoop and HBase to process the 300 million MARC records of WorldCat in various ways. This presentation will explain how Hadoop MapReduce works and illustrate it with specific examples and code. The role of the jobtracker in both monitoring and reporting on processes will be explained. String searching WorldCat will also be demonstrated live.&lt;br /&gt;
&lt;br /&gt;
== Quick and Easy Data Visualization with Google Visualization API and Google Chart Libraries ==&lt;br /&gt;
 &lt;br /&gt;
[http://bohyunkim.net/blog Bohyun Kim], Florida International University, bohyun.kim@fiu.edu&lt;br /&gt;
* 'No' previous Code4Lib presentations &lt;br /&gt;
&lt;br /&gt;
Do most of the data that your library collects stay in spreadsheets or are published as a static table with a series of boring numbers? Do your library stakeholders spend more time collecting the data than using it as a decision-making tool because the data is presented in a way that makes it hard for them [http://developers.google.com/chart/interactive/docs/gallery to quickly grasp its significance? ]&lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of [http://developers.google.com/chart/interactive/docs/reference Google Visualization API] [2] and [http://developers.google.com/chart/ Google Chart Libraries] [3] to get you started on the way to quickly query and visualize your library data from remote data sources (e.g. a Google Spreadsheet or your own database) with (or without) cool-looking user-controls, animation effects, and even a dashboard.&lt;br /&gt;
&lt;br /&gt;
== Leap Motion + Rare Books: A hands-free way to view and interact with rare books in 3D ==&lt;br /&gt;
 &lt;br /&gt;
[http://http://www.youtube.com/user/jpdenzer Juan Denzer], Binghamton University, jdenzer@binghamton.edu&lt;br /&gt;
* 'No' previous Code4Lib presentations &lt;br /&gt;
&lt;br /&gt;
As rare books become more delicate over time, making them available to the public becomes harder.  We at Binghamton University Library have developed an application that makes it easier to view rare books without ever having to touch them.  We have combined the Leap Motion hands-free device and 3D rendered models to create a new virtual experience for the viewer.&lt;br /&gt;
&lt;br /&gt;
The application allows the user to rotate and zoom in on a 3D representation of a rare book.  The user is also able to ‘open’ the virtual book and flip through it using a natural user interface.  Such as swiping the hand left or right to turn the page.&lt;br /&gt;
&lt;br /&gt;
The application is built on the .Net framework and is written in C#.  3D models are created using simple 3D software such as sketchup or Blender.  Scans of the book cover and spine are created using simple flatbed scanners.  The inside pages are scanned using overhead scanners. &lt;br /&gt;
&lt;br /&gt;
This talk with discuss the technologies used in developing the application and virtually any library could implement the application with virtually no coding at all. This presentation will have a demonstration of the software and also a chance for audience members to experience the Rare Book Leap Motion App themselves.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Course Reserves Unleashed! ==&lt;br /&gt;
 &lt;br /&gt;
* Bobbi Fox, Library Technology Services, Harvard University, bobbi_fox@harvard.edu&lt;br /&gt;
* Gloria Korsman, Andover-Harvard Theological Library&lt;br /&gt;
** No previous Code4Lib presentations &lt;br /&gt;
&lt;br /&gt;
Hey kids!  Remember when SOAP was used for something other than washing?  Our sophisticated (and highly functional) Course Reserves Request system does!&lt;br /&gt;
&lt;br /&gt;
However, while the system is great for submitting and  processing course reserve requests, the student-facing presentation through Havard’s home-grown -- and soon to be replaced -- LMS leaves a lot to be desired.  &lt;br /&gt;
&lt;br /&gt;
Follow along as we leverage Solr 4 as a No-SQL database, along with more progressive RESTful API techniques, to release Reserves data into the wild without interfering with reserves request processing -- and, in the process, open up the opportunity for other schools to feed their data in as well.&lt;br /&gt;
&lt;br /&gt;
== We Are All Disabled! Universal Web Design Making Web Services Accessible for Everyone ==&lt;br /&gt;
 &lt;br /&gt;
Cynthia Ng, Accessibility Librarian, CILS at Langara College&lt;br /&gt;
* No previous Code4Lib presentations (not counting lightning talks)&lt;br /&gt;
&lt;br /&gt;
We’re building and improving tools and services all the time, but do you only develop for the “average” user or add things for “disabled” users? We all use “assistive” technology accessing information in a multitude of ways with different platforms, devices, etc. Let’s focus on providing web services that are accessible to everyone without it being onerous or ugly. The aim is to get you thinking about what you can do to make web-based services and content more accessible for all from the beginning or with small amounts of effort whether you're a developer or not.&lt;br /&gt;
&lt;br /&gt;
The goal of the presentation is to provide both developers and content creators with information on simple, practical ways to make web content and web services more accessible. However, rather than thinking about putting in extra effort or making adjustment for those with disabilities, I want to help people think about how to make their websites more accessible for all users through universal web design.&lt;br /&gt;
&lt;br /&gt;
== Personalize your Google Analytics Data with Custom Events and Variables ==&lt;br /&gt;
&lt;br /&gt;
[http://joshwilson.net Josh Wilson], Systems Integration Librarian, State Library of North Carolina - joshwilsonnc@gmail.com&lt;br /&gt;
&lt;br /&gt;
At the State Library of North Carolina, we had more specific questions about the use of our digital collections than standard GA could provide. A few implementations of custom events and custom variables later, we have our answers.&lt;br /&gt;
&lt;br /&gt;
I'll demonstrate how these analytics add-ons work, and why implementation can sometimes be more complicated than just adding a few lines of JavaScript to your ga.js. I'll discuss some specific examples in use at the SLNC:&lt;br /&gt;
&lt;br /&gt;
* Capturing the content of specific metadata fields in CONTENTdm as Custom Events &lt;br /&gt;
* Recording Drupal taxonomy terms as Custom Variables&lt;br /&gt;
&lt;br /&gt;
In both instances, this data deepened our understanding of how our sites and collections were being used, and in turn, we were able to report usage more accurately to content contributors and other stakeholders.&lt;br /&gt;
&lt;br /&gt;
More on: [https://developers.google.com/analytics/devguides/collection/gajs/eventTrackerGuide GA Custom Events] | [https://developers.google.com/analytics/devguides/collection/gajs/gaTrackingCustomVariables GA Custom Variables]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Behold Fedora 4: The Incredible Shrinking Repository! ==&lt;br /&gt;
&lt;br /&gt;
Esmé Cowles, UC San Diego Library.  Previous talk: [http://code4lib.org/conference/2013/cowles-critchlow-westbrook All Teh Metadatas Re-Revisited] (2013)&lt;br /&gt;
&lt;br /&gt;
* One repository contains untold numbers of digital objects and powers many Hydra and Islandora apps&lt;br /&gt;
* It speaks RDF, but contains no triplestore! (triplestores sold separately, SPARQL Update may be involved, some restrictions apply)&lt;br /&gt;
* Flexible enough to tie itself in knots implementing storage and access control policies&lt;br /&gt;
* Witness feats of strength and scalability, with dramatically increased performance and clustering&lt;br /&gt;
* Plumb the depths of bottomless hierarchies, and marvel at the metadata woven into the very fabric of the repository&lt;br /&gt;
* Ponder the paradox of ingesting large files by not ingesting them&lt;br /&gt;
* Be amazed as Fedora 4 swallows other systems whole (including Fedora 3 repositories)&lt;br /&gt;
* Watch novice developers setup Fedora 4 from scratch, with just a handful of incantations to Git and Maven&lt;br /&gt;
&lt;br /&gt;
The Fedora Commons Repository is the foundation of many digital collections, e-research, digital library, archives, digital preservation, institutional repository and open access publishing systems.  This talk will focus on how Fedora 4 improves core repository functionality, adds new features, maintains backwards compatibility, and addresses the shortcomings of Fedora 3.&lt;br /&gt;
&lt;br /&gt;
== Organic Free-Range API Development - Making Web Services That You Will Actually Want to Consume ==&lt;br /&gt;
&lt;br /&gt;
Steve Meyer and Karen Coombs, OCLC&lt;br /&gt;
&lt;br /&gt;
Building web services can have great benefits by providing reusability of data and functionality. Underpinning your applications with a web service will allow you to write code once and support multiple environments: your library's web app, mobile applications, the embedded widget in your campus portal. However, building a web service is its own kind of artful programming. Doing it well requires attention to many of the same techniques and requirements as building web applications, though with different outcomes. &lt;br /&gt;
&lt;br /&gt;
So what are the usability principles for web services? How do you build a web service that you (and others) will actually want to use? In this talk, we’ll share some of the lessons learned - the good, the bad, and the ugly - through OCLC's work on the WorldCat Metadata API. This web service is a sophisticated API that provides external clients with read and write access to WorldCat data. It provides a model to help aspiring API creators navigate the potential complications of crafting a web service. We'll cover:&lt;br /&gt;
&lt;br /&gt;
* Loose coupling of data assets and resource-oriented data modeling at the core&lt;br /&gt;
* Coding to standards vs. exposure of an internal data model&lt;br /&gt;
* Authentication and security for web services: API Keys, Digital Signing, OAuth Flows&lt;br /&gt;
* Building web services that behave as a suite so it looks like the left hand knows what the right hand is doing&lt;br /&gt;
&lt;br /&gt;
So at the end of the day, your team will know your API is a very good egg after all. &lt;br /&gt;
&lt;br /&gt;
If accepted, the presenters intend to produce and share a Quick Guide for building a web service that will reflect content presented in the talk.&lt;br /&gt;
&lt;br /&gt;
== Lucene's Latest (for Libraries) ==&lt;br /&gt;
&lt;br /&gt;
erik.hatcher@lucidworks.com&lt;br /&gt;
&lt;br /&gt;
Lucene powers the search capabilities of practically all library discovery platforms, by way of Solr, etc.  The Lucene project evolves rapidly, and it's a full-time job to keep up with the ever improving features and scalability.   This talk will distill and showcase the most relevant(!) advancements to date.&lt;br /&gt;
&lt;br /&gt;
== The Why and How of Very Large Displays in Libraries. ==&lt;br /&gt;
&lt;br /&gt;
* Cory Lown, NCSU Libraries, cwlown@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Previous Code4Lib Presentations:&lt;br /&gt;
* [http://code4lib.org/conference/2012/lown How People Search the Library from a Single Search Box]  2012&lt;br /&gt;
* [http://code4lib.org/conference/2010/orphanides_lown_lynema Enhancing Discoverability with Virtual Shelf Browse] 2010&lt;br /&gt;
&lt;br /&gt;
Built into the walls of NC State's new Hunt Library are several [http://www.christiedigital.com/en-us/digital-signage/products/microtiles/pages/microtiles-digital-signage-video-wall.aspx Christie MicroTile Display Wall Systems]. What does a library do with a display that's seven feet tall and over twenty feet wide? I'll talk about why libraries might want large displays like this, what we're doing with them right now, and what we might do with them in the future. I'll talk about how these displays factor into planning for new and existing web projects. And I'll get into the fun details of how you build web applications that scale from the very small browser window on a phone all the way up to a browser window with about 14 million pixels (about 10 million more than a dual 24&amp;quot; monitor desktop setup).&lt;br /&gt;
&lt;br /&gt;
[[:Category:Code4Lib2014]]&lt;/div&gt;</summary>
		<author><name>Cwlown</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_Prepared_Talk_Proposals&amp;diff=39778</id>
		<title>2014 Prepared Talk Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_Prepared_Talk_Proposals&amp;diff=39778"/>
				<updated>2013-11-07T15:39:10Z</updated>
		
		<summary type="html">&lt;p&gt;Cwlown: /* The Why and How of Very Large Displays in Libraries. */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==2014 Prepared Talk Proposals==&lt;br /&gt;
&lt;br /&gt;
'''Proposals for Prepared Talks:'''&lt;br /&gt;
&lt;br /&gt;
Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:&lt;br /&gt;
 &lt;br /&gt;
* ''Projects'' you've worked on which incorporate innovative implementation of existing technologies and/or development of new software&lt;br /&gt;
* ''Tools and technologies'' – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)&lt;br /&gt;
* ''Technical issues'' - Big issues in library technology that should be addressed or better understood&lt;br /&gt;
* ''Relevant non-technical issues'' – Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc.&lt;br /&gt;
&lt;br /&gt;
'''To Propose a Talk'''&lt;br /&gt;
* Log in to the wiki in order to submit a proposal. If you are not already registered, follow the instructions to do so.&lt;br /&gt;
* Provide a title and brief (500 words or fewer) description of your proposed talk.&lt;br /&gt;
* If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist us in opening the conference to new presenters.&lt;br /&gt;
&lt;br /&gt;
As in past years, the Code4Lib community will vote on proposals that they would like to see included in the program. This year, however, only the top 10 proposals will be guaranteed a slot at the conference. Additional presentations will be selected by the Program Committee in an effort to ensure diversity in program content. Community votes will, of course, still weigh heavily in these decisions.&lt;br /&gt;
&lt;br /&gt;
Presenters whose proposals are selected for inclusion in the program will be guaranteed an opportunity to register for the conference. The standard conference registration fee will still apply.&lt;br /&gt;
&lt;br /&gt;
''Proposals can be submitted through '''Friday, November 8, 2013, at 5pm PST'''''. Voting will commence on November 18, 2013 and continue through December 6, 2013. The final line-up of presentations will be announced in early January, 2014.&lt;br /&gt;
&lt;br /&gt;
'''Talk Proposals'''&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Using Drupal to drive alternative presentation systems ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Recently, we have been building systems that use angular.js, Rails, or other systems for presentation, while leveraging Drupal's sophisticated content management capabilities on the back end.&lt;br /&gt;
&lt;br /&gt;
So far, these have been one-way systems, but as we move to Drupal 8 we are beginning to explore ways to further decouple the presentation and CMS functions.&lt;br /&gt;
&lt;br /&gt;
== A Book, a Web Browser and a Tablet: How Bibliotheca Alexandrina's Book Viewer Framework Makes It Possible ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Mohammed.abuouda|Mohammed Abu ouda]], Bibliotheca Alexandrina (The new Library of Alexandria)&lt;br /&gt;
&lt;br /&gt;
A lot of institutions around the world are engaged in multiple digitization projects aiming at preserving the human knowledge present in books and availing them through multiple channels to people around the whole globe. These efforts will sure help close the digital gap particularly with the arrival of affordable e-readers, mobile phones and network coverage. However, the digital reading experience has not yet arrived to its maximum potential. Many readers miss features they like in their good old books and wish to find them in their digital counterpart. In an attempt to create a unique digital reading experience, Bibliotheca Alexandria (BA) created a flexible book viewing framework that is currently used to access its current collection of more than 300,000 digital books in five different languages which includes the largest collection of digitized Arabic books.&lt;br /&gt;
&lt;br /&gt;
Using open source tools, BA used the framework to develop a modular book viewer that can be deployed in different environments and is currently at the heart of various BA projects. The Book viewer provides several features creating a more natural reading experience. As with physical books, the reader can now personalize the books he reads by adding annotations like highlights, underlines and sticky notes to capture his thoughts and ideas in addition to being able to share the book with friends on social networks. The reader can perform a search across the content of the book receiving highlighted search results within the pages of the book. More features can be further added to the book viewer through its plugin architecture.&lt;br /&gt;
&lt;br /&gt;
== Structured data NOW: seeding schema.org in library systems ==&lt;br /&gt;
 &lt;br /&gt;
* [http://coffeecode.net Dan Scott], Laurentian University&lt;br /&gt;
** Previous code4lib presentations: [https://archive.org/details/code4lib.conf.2008.pres.CouchDBsacrilege CouchDB is sacrilege... mmm, delicious sacrilege] at Code4Lib 2008&lt;br /&gt;
&lt;br /&gt;
The semantic web, linked data, and structured data are all fantastic ideas with a barrier imposed by implementation constraints. If their system does not allow customizations, or the institution lacks skilled human resources, it does not matter how enthused a given library might be about publishing structured data... it will not happen. However, if the software in use simply publishes structured data by default, then the web will be populated for free. Really! No extra resources necessary.&lt;br /&gt;
&lt;br /&gt;
This presentation highlights Dan's work with systems such as Evergreen, Koha, and VuFind to enable the publication of schema.org structured data out-of-the-box. Along the way, we reflect the current state of the W3C Schema.org Bibliographic Extension community group efforts to shape the evolution of the schema.org vocabulary. Finally, hold on tight as we contemplate next steps and the possibilities of a world where structured data is the norm on the web.&lt;br /&gt;
&lt;br /&gt;
== Towards Pasta Code Nirvana: Using JavaScript MVC to Fill Your Programming Ravioli ==&lt;br /&gt;
&lt;br /&gt;
* Bret Davidson, North Carolina State University Libraries, bret_davidson@ncsu.edu&lt;br /&gt;
** Previous Code4Lib Presentations: [http://wiki.code4lib.org/index.php/2013_talks_proposals#Data-Driven_Documents:_Visualizing_library_data_with_D3.js Visualizing library data with D3.js] at Code4Lib 2013&lt;br /&gt;
&lt;br /&gt;
JavaScript MVC frameworks are ushering in a golden age of robust and responsive web applications that take advantage of evergreen browsers, performant JS engines, and the unprecedented reach provided by billions of personal computing devices. The web browser has emerged as the world’s most popular application runtime and the complexity[1] and scope of JavaScript applications has exploded accordingly. Server-side web frameworks like Rails and Django have helped developers adhere to best practices like modularity, dependency injection, and unit testing for years, practices that are now being applied to JavaScript development through projects like Backbone[2], Ember[3], and Angular[4].&lt;br /&gt;
&lt;br /&gt;
This talk will discuss the issues JavaScript MVC frameworks are trying to solve, common features like data binding, implications for the future of web development[5], and the appropriateness of JavaScript MVC for library applications.&lt;br /&gt;
&lt;br /&gt;
*[1]http://en.wikipedia.org/wiki/Spaghetti_code&lt;br /&gt;
*[2]http://backbonejs.org&lt;br /&gt;
*[3]http://emberjs.com&lt;br /&gt;
*[4]http://angularjs.org&lt;br /&gt;
*[5]http://tomdale.net/2013/09/progressive-enhancement-is-dead/&lt;br /&gt;
&lt;br /&gt;
== WebSockets for Real-Time and Interactive Interfaces ==&lt;br /&gt;
&lt;br /&gt;
* [http://ronallo.com Jason Ronallo], NCSU Libraries, jason_ronallo@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Previous Code4Lib presentations:&lt;br /&gt;
* [http://code4lib.org/conference/2012/ronallo HTML5 Microdata and Schema.org] 2012&lt;br /&gt;
* [http://code4lib.org/conference/2013/ronallo HTML5 Video Now!] 2013&lt;br /&gt;
&lt;br /&gt;
Watching the Google Analytics Real-Time dashboard for the first time was mesmerizing. As soon as someone visited a site, I could see what page they were on. For a digital collections site with a lot of images, it was fun to see what visitors were looking at. But getting from Google Analytics to the image or other content of what was currently being viewed was cumbersome. The real-time experience was something I wanted share with others. I'll show you how I used a WebSocket service to create a real-time interface to digital collections.&lt;br /&gt;
&lt;br /&gt;
In the Hunt Library at NCSU we have some large video walls. I wanted to make HTML-based exhibits that featured viewer interactions. I'll show you how I converted Listen to Wikipedia [1] into an bring-your-own-device interactive exhibit. With WebSockets any HTML page can be remote controlled by any internet connected device.&lt;br /&gt;
&lt;br /&gt;
I will attempt to include real-time audience participation.&lt;br /&gt;
&lt;br /&gt;
[1] http://listen.hatnote.com/&lt;br /&gt;
&lt;br /&gt;
== Rapid Development of Automated Tasks with the File Analyzer ==&lt;br /&gt;
&lt;br /&gt;
* Terry Brady, Georgetown University Libraries, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Libraries have customized the File Analyzer and Metadata Harvester application (https://github.com/Georgetown-University-Libraries/File-Analyzer) to solve a number of library automation challenges:&lt;br /&gt;
* validating digitized and reformatted files&lt;br /&gt;
* validating vendor statistics for counter compliance&lt;br /&gt;
* preparing collections of digital files for archiving and ingest&lt;br /&gt;
* manipulating ILS import and export files&lt;br /&gt;
&lt;br /&gt;
The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census.  After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform.  Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.&lt;br /&gt;
&lt;br /&gt;
The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules.  As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.&lt;br /&gt;
&lt;br /&gt;
Learn about the functionality that is available for download, how you can use this tool to automate workflows from digital collections to ILS ingests to electronic resources statistics and also discuss the opportunities to collaborate on enhancements to this application!&lt;br /&gt;
&lt;br /&gt;
== GeoHydra: How to Build a Geospatial Digital Library with Fedora ==&lt;br /&gt;
 &lt;br /&gt;
* [http://stanford.edu/~drh Darren Hardy], Stanford University, drh@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Geographically-rich data are exploding and putting fear in those trying to&lt;br /&gt;
tackle integrating them into existing digital library infrastructures.&lt;br /&gt;
Building a spatial data infrastructure that integrates with your digital&lt;br /&gt;
library infrastructure need not be a daunting task. We have successfully&lt;br /&gt;
deployed a geospatial digital library infrastructure using Fedora and&lt;br /&gt;
open-source geospatial software [1]. We'll discuss the primary design&lt;br /&gt;
decisions and technologies that led to a production deployment within a few&lt;br /&gt;
months. Briefly, our architecture revolves around discovery, delivery, and&lt;br /&gt;
metadata pipelines using open-source OpenGeoPortal [2], Solr [3], GeoServer&lt;br /&gt;
[4], PostGIS [5], and GeoNetwork [6] technologies, plus the proprietary ESRI&lt;br /&gt;
ArcMap [7] -- the GIS industry's workhorse. Finally, we'll discuss the key&lt;br /&gt;
skillsets needed to build and maintain a spatial data infrastructure.&lt;br /&gt;
&lt;br /&gt;
[1] http://foss4g.org&lt;br /&gt;
[2] http://opengeoportal.org&lt;br /&gt;
[3] http://lucene.apache.org/solr&lt;br /&gt;
[4] http://geoserver.org&lt;br /&gt;
[5] http://postgis.net&lt;br /&gt;
[6] http://geonetwork-opensource.org&lt;br /&gt;
[7] http://esri.com&lt;br /&gt;
&lt;br /&gt;
==Under the Hood of Hadoop Processing at OCLC Research ==&lt;br /&gt;
&lt;br /&gt;
[http://roytennant.com/ Roy Tennant]&lt;br /&gt;
&lt;br /&gt;
* Previous Code4Lib presentations: 2006: &amp;quot;The Case for Code4Lib 501c(3)&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[http://hadoop.apache.org/ Apache Hadoop] is widely used by Yahoo!, Google, and many others to process massive amounts of data quickly. OCLC Research uses a 40-node compute cluster with Hadoop and HBase to process the 300 million MARC records of WorldCat in various ways. This presentation will explain how Hadoop MapReduce works and illustrate it with specific examples and code. The role of the jobtracker in both monitoring and reporting on processes will be explained. String searching WorldCat will also be demonstrated live.&lt;br /&gt;
&lt;br /&gt;
== Quick and Easy Data Visualization with Google Visualization API and Google Chart Libraries ==&lt;br /&gt;
 &lt;br /&gt;
[http://bohyunkim.net/blog Bohyun Kim], Florida International University, bohyun.kim@fiu.edu&lt;br /&gt;
* 'No' previous Code4Lib presentations &lt;br /&gt;
&lt;br /&gt;
Do most of the data that your library collects stay in spreadsheets or are published as a static table with a series of boring numbers? Do your library stakeholders spend more time collecting the data than using it as a decision-making tool because the data is presented in a way that makes it hard for them [http://developers.google.com/chart/interactive/docs/gallery to quickly grasp its significance? ]&lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of [http://developers.google.com/chart/interactive/docs/reference Google Visualization API] [2] and [http://developers.google.com/chart/ Google Chart Libraries] [3] to get you started on the way to quickly query and visualize your library data from remote data sources (e.g. a Google Spreadsheet or your own database) with (or without) cool-looking user-controls, animation effects, and even a dashboard.&lt;br /&gt;
&lt;br /&gt;
== Leap Motion + Rare Books: A hands-free way to view and interact with rare books in 3D ==&lt;br /&gt;
 &lt;br /&gt;
[http://http://www.youtube.com/user/jpdenzer Juan Denzer], Binghamton University, jdenzer@binghamton.edu&lt;br /&gt;
* 'No' previous Code4Lib presentations &lt;br /&gt;
&lt;br /&gt;
As rare books become more delicate over time, making them available to the public becomes harder.  We at Binghamton University Library have developed an application that makes it easier to view rare books without ever having to touch them.  We have combined the Leap Motion hands-free device and 3D rendered models to create a new virtual experience for the viewer.&lt;br /&gt;
&lt;br /&gt;
The application allows the user to rotate and zoom in on a 3D representation of a rare book.  The user is also able to ‘open’ the virtual book and flip through it using a natural user interface.  Such as swiping the hand left or right to turn the page.&lt;br /&gt;
&lt;br /&gt;
The application is built on the .Net framework and is written in C#.  3D models are created using simple 3D software such as sketchup or Blender.  Scans of the book cover and spine are created using simple flatbed scanners.  The inside pages are scanned using overhead scanners. &lt;br /&gt;
&lt;br /&gt;
This talk with discuss the technologies used in developing the application and virtually any library could implement the application with virtually no coding at all. This presentation will have a demonstration of the software and also a chance for audience members to experience the Rare Book Leap Motion App themselves.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Course Reserves Unleashed! ==&lt;br /&gt;
 &lt;br /&gt;
* Bobbi Fox, Library Technology Services, Harvard University, bobbi_fox@harvard.edu&lt;br /&gt;
* Gloria Korsman, Andover-Harvard Theological Library&lt;br /&gt;
** No previous Code4Lib presentations &lt;br /&gt;
&lt;br /&gt;
Hey kids!  Remember when SOAP was used for something other than washing?  Our sophisticated (and highly functional) Course Reserves Request system does!&lt;br /&gt;
&lt;br /&gt;
However, while the system is great for submitting and  processing course reserve requests, the student-facing presentation through Havard’s home-grown -- and soon to be replaced -- LMS leaves a lot to be desired.  &lt;br /&gt;
&lt;br /&gt;
Follow along as we leverage Solr 4 as a No-SQL database, along with more progressive RESTful API techniques, to release Reserves data into the wild without interfering with reserves request processing -- and, in the process, open up the opportunity for other schools to feed their data in as well.&lt;br /&gt;
&lt;br /&gt;
== We Are All Disabled! Universal Web Design Making Web Services Accessible for Everyone ==&lt;br /&gt;
 &lt;br /&gt;
Cynthia Ng, Accessibility Librarian, CILS at Langara College&lt;br /&gt;
* No previous Code4Lib presentations (not counting lightning talks)&lt;br /&gt;
&lt;br /&gt;
We’re building and improving tools and services all the time, but do you only develop for the “average” user or add things for “disabled” users? We all use “assistive” technology accessing information in a multitude of ways with different platforms, devices, etc. Let’s focus on providing web services that are accessible to everyone without it being onerous or ugly. The aim is to get you thinking about what you can do to make web-based services and content more accessible for all from the beginning or with small amounts of effort whether you're a developer or not.&lt;br /&gt;
&lt;br /&gt;
The goal of the presentation is to provide both developers and content creators with information on simple, practical ways to make web content and web services more accessible. However, rather than thinking about putting in extra effort or making adjustment for those with disabilities, I want to help people think about how to make their websites more accessible for all users through universal web design.&lt;br /&gt;
&lt;br /&gt;
== Personalize your Google Analytics Data with Custom Events and Variables ==&lt;br /&gt;
&lt;br /&gt;
[http://joshwilson.net Josh Wilson], Systems Integration Librarian, State Library of North Carolina - joshwilsonnc@gmail.com&lt;br /&gt;
&lt;br /&gt;
At the State Library of North Carolina, we had more specific questions about the use of our digital collections than standard GA could provide. A few implementations of custom events and custom variables later, we have our answers.&lt;br /&gt;
&lt;br /&gt;
I'll demonstrate how these analytics add-ons work, and why implementation can sometimes be more complicated than just adding a few lines of JavaScript to your ga.js. I'll discuss some specific examples in use at the SLNC:&lt;br /&gt;
&lt;br /&gt;
* Capturing the content of specific metadata fields in CONTENTdm as Custom Events &lt;br /&gt;
* Recording Drupal taxonomy terms as Custom Variables&lt;br /&gt;
&lt;br /&gt;
In both instances, this data deepened our understanding of how our sites and collections were being used, and in turn, we were able to report usage more accurately to content contributors and other stakeholders.&lt;br /&gt;
&lt;br /&gt;
More on: [https://developers.google.com/analytics/devguides/collection/gajs/eventTrackerGuide GA Custom Events] | [https://developers.google.com/analytics/devguides/collection/gajs/gaTrackingCustomVariables GA Custom Variables]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Behold Fedora 4: The Incredible Shrinking Repository! ==&lt;br /&gt;
&lt;br /&gt;
Esmé Cowles, UC San Diego Library.  Previous talk: [http://code4lib.org/conference/2013/cowles-critchlow-westbrook All Teh Metadatas Re-Revisited] (2013)&lt;br /&gt;
&lt;br /&gt;
* One repository contains untold numbers of digital objects and powers many Hydra and Islandora apps&lt;br /&gt;
* It speaks RDF, but contains no triplestore! (triplestores sold separately, SPARQL Update may be involved, some restrictions apply)&lt;br /&gt;
* Flexible enough to tie itself in knots implementing storage and access control policies&lt;br /&gt;
* Witness feats of strength and scalability, with dramatically increased performance and clustering&lt;br /&gt;
* Plumb the depths of bottomless hierarchies, and marvel at the metadata woven into the very fabric of the repository&lt;br /&gt;
* Ponder the paradox of ingesting large files by not ingesting them&lt;br /&gt;
* Be amazed as Fedora 4 swallows other systems whole (including Fedora 3 repositories)&lt;br /&gt;
* Watch novice developers setup Fedora 4 from scratch, with just a handful of incantations to Git and Maven&lt;br /&gt;
&lt;br /&gt;
The Fedora Commons Repository is the foundation of many digital collections, e-research, digital library, archives, digital preservation, institutional repository and open access publishing systems.  This talk will focus on how Fedora 4 improves core repository functionality, adds new features, maintains backwards compatibility, and addresses the shortcomings of Fedora 3.&lt;br /&gt;
&lt;br /&gt;
== Organic Free-Range API Development - Making Web Services That You Will Actually Want to Consume ==&lt;br /&gt;
&lt;br /&gt;
Steve Meyer and Karen Coombs, OCLC&lt;br /&gt;
&lt;br /&gt;
Building web services can have great benefits by providing reusability of data and functionality. Underpinning your applications with a web service will allow you to write code once and support multiple environments: your library's web app, mobile applications, the embedded widget in your campus portal. However, building a web service is its own kind of artful programming. Doing it well requires attention to many of the same techniques and requirements as building web applications, though with different outcomes. &lt;br /&gt;
&lt;br /&gt;
So what are the usability principles for web services? How do you build a web service that you (and others) will actually want to use? In this talk, we’ll share some of the lessons learned - the good, the bad, and the ugly - through OCLC's work on the WorldCat Metadata API. This web service is a sophisticated API that provides external clients with read and write access to WorldCat data. It provides a model to help aspiring API creators navigate the potential complications of crafting a web service. We'll cover:&lt;br /&gt;
&lt;br /&gt;
* Loose coupling of data assets and resource-oriented data modeling at the core&lt;br /&gt;
* Coding to standards vs. exposure of an internal data model&lt;br /&gt;
* Authentication and security for web services: API Keys, Digital Signing, OAuth Flows&lt;br /&gt;
* Building web services that behave as a suite so it looks like the left hand knows what the right hand is doing&lt;br /&gt;
&lt;br /&gt;
So at the end of the day, your team will know your API is a very good egg after all. &lt;br /&gt;
&lt;br /&gt;
If accepted, the presenters intend to produce and share a Quick Guide for building a web service that will reflect content presented in the talk.&lt;br /&gt;
&lt;br /&gt;
== Lucene's Latest (for Libraries) ==&lt;br /&gt;
&lt;br /&gt;
erik.hatcher@lucidworks.com&lt;br /&gt;
&lt;br /&gt;
Lucene powers the search capabilities of practically all library discovery platforms, by way of Solr, etc.  The Lucene project evolves rapidly, and it's a full-time job to keep up with the ever improving features and scalability.   This talk will distill and showcase the most relevant(!) advancements to date.&lt;br /&gt;
&lt;br /&gt;
== The Why and How of Very Large Displays in Libraries. ==&lt;br /&gt;
&lt;br /&gt;
* Cory Lown, NCSU Libraries, cwlown@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Previous Code4Lib Presentations:&lt;br /&gt;
* [http://code4lib.org/conference/2012/lown How People Search the Library from a Single Search Box]  2012&lt;br /&gt;
* [http://code4lib.org/conference/2010/orphanides_lown_lynema Enhancing Discoverability with Virtual Shelf Browse] 2010&lt;br /&gt;
&lt;br /&gt;
Built into the walls of NC State's new Hunt Library are several [http://www.christiedigital.com/en-us/digital-signage/products/microtiles/pages/microtiles-digital-signage-video-wall.aspx Christie MicroTile Display Wall Systems]. What does a library do with a display that's seven feet tall and over twenty feet wide? I'll talk about why libraries might want large displays like this, what we're doing with them right now, and what we might do with them in the future. And I'll get into the fun details of how you build web applications that scale from the very small browser window on a phone all the way up to a browser window with about 14 million pixels (about 10 million more than a dual 24&amp;quot; monitor desktop setup).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[:Category:Code4Lib2014]]&lt;/div&gt;</summary>
		<author><name>Cwlown</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_Prepared_Talk_Proposals&amp;diff=39777</id>
		<title>2014 Prepared Talk Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_Prepared_Talk_Proposals&amp;diff=39777"/>
				<updated>2013-11-07T15:37:39Z</updated>
		
		<summary type="html">&lt;p&gt;Cwlown: /* The Why and How of Very Large Displays in Libraries. */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==2014 Prepared Talk Proposals==&lt;br /&gt;
&lt;br /&gt;
'''Proposals for Prepared Talks:'''&lt;br /&gt;
&lt;br /&gt;
Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:&lt;br /&gt;
 &lt;br /&gt;
* ''Projects'' you've worked on which incorporate innovative implementation of existing technologies and/or development of new software&lt;br /&gt;
* ''Tools and technologies'' – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)&lt;br /&gt;
* ''Technical issues'' - Big issues in library technology that should be addressed or better understood&lt;br /&gt;
* ''Relevant non-technical issues'' – Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc.&lt;br /&gt;
&lt;br /&gt;
'''To Propose a Talk'''&lt;br /&gt;
* Log in to the wiki in order to submit a proposal. If you are not already registered, follow the instructions to do so.&lt;br /&gt;
* Provide a title and brief (500 words or fewer) description of your proposed talk.&lt;br /&gt;
* If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist us in opening the conference to new presenters.&lt;br /&gt;
&lt;br /&gt;
As in past years, the Code4Lib community will vote on proposals that they would like to see included in the program. This year, however, only the top 10 proposals will be guaranteed a slot at the conference. Additional presentations will be selected by the Program Committee in an effort to ensure diversity in program content. Community votes will, of course, still weigh heavily in these decisions.&lt;br /&gt;
&lt;br /&gt;
Presenters whose proposals are selected for inclusion in the program will be guaranteed an opportunity to register for the conference. The standard conference registration fee will still apply.&lt;br /&gt;
&lt;br /&gt;
''Proposals can be submitted through '''Friday, November 8, 2013, at 5pm PST'''''. Voting will commence on November 18, 2013 and continue through December 6, 2013. The final line-up of presentations will be announced in early January, 2014.&lt;br /&gt;
&lt;br /&gt;
'''Talk Proposals'''&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Using Drupal to drive alternative presentation systems ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Recently, we have been building systems that use angular.js, Rails, or other systems for presentation, while leveraging Drupal's sophisticated content management capabilities on the back end.&lt;br /&gt;
&lt;br /&gt;
So far, these have been one-way systems, but as we move to Drupal 8 we are beginning to explore ways to further decouple the presentation and CMS functions.&lt;br /&gt;
&lt;br /&gt;
== A Book, a Web Browser and a Tablet: How Bibliotheca Alexandrina's Book Viewer Framework Makes It Possible ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Mohammed.abuouda|Mohammed Abu ouda]], Bibliotheca Alexandrina (The new Library of Alexandria)&lt;br /&gt;
&lt;br /&gt;
A lot of institutions around the world are engaged in multiple digitization projects aiming at preserving the human knowledge present in books and availing them through multiple channels to people around the whole globe. These efforts will sure help close the digital gap particularly with the arrival of affordable e-readers, mobile phones and network coverage. However, the digital reading experience has not yet arrived to its maximum potential. Many readers miss features they like in their good old books and wish to find them in their digital counterpart. In an attempt to create a unique digital reading experience, Bibliotheca Alexandria (BA) created a flexible book viewing framework that is currently used to access its current collection of more than 300,000 digital books in five different languages which includes the largest collection of digitized Arabic books.&lt;br /&gt;
&lt;br /&gt;
Using open source tools, BA used the framework to develop a modular book viewer that can be deployed in different environments and is currently at the heart of various BA projects. The Book viewer provides several features creating a more natural reading experience. As with physical books, the reader can now personalize the books he reads by adding annotations like highlights, underlines and sticky notes to capture his thoughts and ideas in addition to being able to share the book with friends on social networks. The reader can perform a search across the content of the book receiving highlighted search results within the pages of the book. More features can be further added to the book viewer through its plugin architecture.&lt;br /&gt;
&lt;br /&gt;
== Structured data NOW: seeding schema.org in library systems ==&lt;br /&gt;
 &lt;br /&gt;
* [http://coffeecode.net Dan Scott], Laurentian University&lt;br /&gt;
** Previous code4lib presentations: [https://archive.org/details/code4lib.conf.2008.pres.CouchDBsacrilege CouchDB is sacrilege... mmm, delicious sacrilege] at Code4Lib 2008&lt;br /&gt;
&lt;br /&gt;
The semantic web, linked data, and structured data are all fantastic ideas with a barrier imposed by implementation constraints. If their system does not allow customizations, or the institution lacks skilled human resources, it does not matter how enthused a given library might be about publishing structured data... it will not happen. However, if the software in use simply publishes structured data by default, then the web will be populated for free. Really! No extra resources necessary.&lt;br /&gt;
&lt;br /&gt;
This presentation highlights Dan's work with systems such as Evergreen, Koha, and VuFind to enable the publication of schema.org structured data out-of-the-box. Along the way, we reflect the current state of the W3C Schema.org Bibliographic Extension community group efforts to shape the evolution of the schema.org vocabulary. Finally, hold on tight as we contemplate next steps and the possibilities of a world where structured data is the norm on the web.&lt;br /&gt;
&lt;br /&gt;
== Towards Pasta Code Nirvana: Using JavaScript MVC to Fill Your Programming Ravioli ==&lt;br /&gt;
&lt;br /&gt;
* Bret Davidson, North Carolina State University Libraries, bret_davidson@ncsu.edu&lt;br /&gt;
** Previous Code4Lib Presentations: [http://wiki.code4lib.org/index.php/2013_talks_proposals#Data-Driven_Documents:_Visualizing_library_data_with_D3.js Visualizing library data with D3.js] at Code4Lib 2013&lt;br /&gt;
&lt;br /&gt;
JavaScript MVC frameworks are ushering in a golden age of robust and responsive web applications that take advantage of evergreen browsers, performant JS engines, and the unprecedented reach provided by billions of personal computing devices. The web browser has emerged as the world’s most popular application runtime and the complexity[1] and scope of JavaScript applications has exploded accordingly. Server-side web frameworks like Rails and Django have helped developers adhere to best practices like modularity, dependency injection, and unit testing for years, practices that are now being applied to JavaScript development through projects like Backbone[2], Ember[3], and Angular[4].&lt;br /&gt;
&lt;br /&gt;
This talk will discuss the issues JavaScript MVC frameworks are trying to solve, common features like data binding, implications for the future of web development[5], and the appropriateness of JavaScript MVC for library applications.&lt;br /&gt;
&lt;br /&gt;
*[1]http://en.wikipedia.org/wiki/Spaghetti_code&lt;br /&gt;
*[2]http://backbonejs.org&lt;br /&gt;
*[3]http://emberjs.com&lt;br /&gt;
*[4]http://angularjs.org&lt;br /&gt;
*[5]http://tomdale.net/2013/09/progressive-enhancement-is-dead/&lt;br /&gt;
&lt;br /&gt;
== WebSockets for Real-Time and Interactive Interfaces ==&lt;br /&gt;
&lt;br /&gt;
* [http://ronallo.com Jason Ronallo], NCSU Libraries, jason_ronallo@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Previous Code4Lib presentations:&lt;br /&gt;
* [http://code4lib.org/conference/2012/ronallo HTML5 Microdata and Schema.org] 2012&lt;br /&gt;
* [http://code4lib.org/conference/2013/ronallo HTML5 Video Now!] 2013&lt;br /&gt;
&lt;br /&gt;
Watching the Google Analytics Real-Time dashboard for the first time was mesmerizing. As soon as someone visited a site, I could see what page they were on. For a digital collections site with a lot of images, it was fun to see what visitors were looking at. But getting from Google Analytics to the image or other content of what was currently being viewed was cumbersome. The real-time experience was something I wanted share with others. I'll show you how I used a WebSocket service to create a real-time interface to digital collections.&lt;br /&gt;
&lt;br /&gt;
In the Hunt Library at NCSU we have some large video walls. I wanted to make HTML-based exhibits that featured viewer interactions. I'll show you how I converted Listen to Wikipedia [1] into an bring-your-own-device interactive exhibit. With WebSockets any HTML page can be remote controlled by any internet connected device.&lt;br /&gt;
&lt;br /&gt;
I will attempt to include real-time audience participation.&lt;br /&gt;
&lt;br /&gt;
[1] http://listen.hatnote.com/&lt;br /&gt;
&lt;br /&gt;
== Rapid Development of Automated Tasks with the File Analyzer ==&lt;br /&gt;
&lt;br /&gt;
* Terry Brady, Georgetown University Libraries, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Libraries have customized the File Analyzer and Metadata Harvester application (https://github.com/Georgetown-University-Libraries/File-Analyzer) to solve a number of library automation challenges:&lt;br /&gt;
* validating digitized and reformatted files&lt;br /&gt;
* validating vendor statistics for counter compliance&lt;br /&gt;
* preparing collections of digital files for archiving and ingest&lt;br /&gt;
* manipulating ILS import and export files&lt;br /&gt;
&lt;br /&gt;
The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census.  After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform.  Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.&lt;br /&gt;
&lt;br /&gt;
The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules.  As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.&lt;br /&gt;
&lt;br /&gt;
Learn about the functionality that is available for download, how you can use this tool to automate workflows from digital collections to ILS ingests to electronic resources statistics and also discuss the opportunities to collaborate on enhancements to this application!&lt;br /&gt;
&lt;br /&gt;
== GeoHydra: How to Build a Geospatial Digital Library with Fedora ==&lt;br /&gt;
 &lt;br /&gt;
* [http://stanford.edu/~drh Darren Hardy], Stanford University, drh@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Geographically-rich data are exploding and putting fear in those trying to&lt;br /&gt;
tackle integrating them into existing digital library infrastructures.&lt;br /&gt;
Building a spatial data infrastructure that integrates with your digital&lt;br /&gt;
library infrastructure need not be a daunting task. We have successfully&lt;br /&gt;
deployed a geospatial digital library infrastructure using Fedora and&lt;br /&gt;
open-source geospatial software [1]. We'll discuss the primary design&lt;br /&gt;
decisions and technologies that led to a production deployment within a few&lt;br /&gt;
months. Briefly, our architecture revolves around discovery, delivery, and&lt;br /&gt;
metadata pipelines using open-source OpenGeoPortal [2], Solr [3], GeoServer&lt;br /&gt;
[4], PostGIS [5], and GeoNetwork [6] technologies, plus the proprietary ESRI&lt;br /&gt;
ArcMap [7] -- the GIS industry's workhorse. Finally, we'll discuss the key&lt;br /&gt;
skillsets needed to build and maintain a spatial data infrastructure.&lt;br /&gt;
&lt;br /&gt;
[1] http://foss4g.org&lt;br /&gt;
[2] http://opengeoportal.org&lt;br /&gt;
[3] http://lucene.apache.org/solr&lt;br /&gt;
[4] http://geoserver.org&lt;br /&gt;
[5] http://postgis.net&lt;br /&gt;
[6] http://geonetwork-opensource.org&lt;br /&gt;
[7] http://esri.com&lt;br /&gt;
&lt;br /&gt;
==Under the Hood of Hadoop Processing at OCLC Research ==&lt;br /&gt;
&lt;br /&gt;
[http://roytennant.com/ Roy Tennant]&lt;br /&gt;
&lt;br /&gt;
* Previous Code4Lib presentations: 2006: &amp;quot;The Case for Code4Lib 501c(3)&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[http://hadoop.apache.org/ Apache Hadoop] is widely used by Yahoo!, Google, and many others to process massive amounts of data quickly. OCLC Research uses a 40-node compute cluster with Hadoop and HBase to process the 300 million MARC records of WorldCat in various ways. This presentation will explain how Hadoop MapReduce works and illustrate it with specific examples and code. The role of the jobtracker in both monitoring and reporting on processes will be explained. String searching WorldCat will also be demonstrated live.&lt;br /&gt;
&lt;br /&gt;
== Quick and Easy Data Visualization with Google Visualization API and Google Chart Libraries ==&lt;br /&gt;
 &lt;br /&gt;
[http://bohyunkim.net/blog Bohyun Kim], Florida International University, bohyun.kim@fiu.edu&lt;br /&gt;
* 'No' previous Code4Lib presentations &lt;br /&gt;
&lt;br /&gt;
Do most of the data that your library collects stay in spreadsheets or are published as a static table with a series of boring numbers? Do your library stakeholders spend more time collecting the data than using it as a decision-making tool because the data is presented in a way that makes it hard for them [http://developers.google.com/chart/interactive/docs/gallery to quickly grasp its significance? ]&lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of [http://developers.google.com/chart/interactive/docs/reference Google Visualization API] [2] and [http://developers.google.com/chart/ Google Chart Libraries] [3] to get you started on the way to quickly query and visualize your library data from remote data sources (e.g. a Google Spreadsheet or your own database) with (or without) cool-looking user-controls, animation effects, and even a dashboard.&lt;br /&gt;
&lt;br /&gt;
== Leap Motion + Rare Books: A hands-free way to view and interact with rare books in 3D ==&lt;br /&gt;
 &lt;br /&gt;
[http://http://www.youtube.com/user/jpdenzer Juan Denzer], Binghamton University, jdenzer@binghamton.edu&lt;br /&gt;
* 'No' previous Code4Lib presentations &lt;br /&gt;
&lt;br /&gt;
As rare books become more delicate over time, making them available to the public becomes harder.  We at Binghamton University Library have developed an application that makes it easier to view rare books without ever having to touch them.  We have combined the Leap Motion hands-free device and 3D rendered models to create a new virtual experience for the viewer.&lt;br /&gt;
&lt;br /&gt;
The application allows the user to rotate and zoom in on a 3D representation of a rare book.  The user is also able to ‘open’ the virtual book and flip through it using a natural user interface.  Such as swiping the hand left or right to turn the page.&lt;br /&gt;
&lt;br /&gt;
The application is built on the .Net framework and is written in C#.  3D models are created using simple 3D software such as sketchup or Blender.  Scans of the book cover and spine are created using simple flatbed scanners.  The inside pages are scanned using overhead scanners. &lt;br /&gt;
&lt;br /&gt;
This talk with discuss the technologies used in developing the application and virtually any library could implement the application with virtually no coding at all. This presentation will have a demonstration of the software and also a chance for audience members to experience the Rare Book Leap Motion App themselves.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Course Reserves Unleashed! ==&lt;br /&gt;
 &lt;br /&gt;
* Bobbi Fox, Library Technology Services, Harvard University, bobbi_fox@harvard.edu&lt;br /&gt;
* Gloria Korsman, Andover-Harvard Theological Library&lt;br /&gt;
** No previous Code4Lib presentations &lt;br /&gt;
&lt;br /&gt;
Hey kids!  Remember when SOAP was used for something other than washing?  Our sophisticated (and highly functional) Course Reserves Request system does!&lt;br /&gt;
&lt;br /&gt;
However, while the system is great for submitting and  processing course reserve requests, the student-facing presentation through Havard’s home-grown -- and soon to be replaced -- LMS leaves a lot to be desired.  &lt;br /&gt;
&lt;br /&gt;
Follow along as we leverage Solr 4 as a No-SQL database, along with more progressive RESTful API techniques, to release Reserves data into the wild without interfering with reserves request processing -- and, in the process, open up the opportunity for other schools to feed their data in as well.&lt;br /&gt;
&lt;br /&gt;
== We Are All Disabled! Universal Web Design Making Web Services Accessible for Everyone ==&lt;br /&gt;
 &lt;br /&gt;
Cynthia Ng, Accessibility Librarian, CILS at Langara College&lt;br /&gt;
* No previous Code4Lib presentations (not counting lightning talks)&lt;br /&gt;
&lt;br /&gt;
We’re building and improving tools and services all the time, but do you only develop for the “average” user or add things for “disabled” users? We all use “assistive” technology accessing information in a multitude of ways with different platforms, devices, etc. Let’s focus on providing web services that are accessible to everyone without it being onerous or ugly. The aim is to get you thinking about what you can do to make web-based services and content more accessible for all from the beginning or with small amounts of effort whether you're a developer or not.&lt;br /&gt;
&lt;br /&gt;
The goal of the presentation is to provide both developers and content creators with information on simple, practical ways to make web content and web services more accessible. However, rather than thinking about putting in extra effort or making adjustment for those with disabilities, I want to help people think about how to make their websites more accessible for all users through universal web design.&lt;br /&gt;
&lt;br /&gt;
== Personalize your Google Analytics Data with Custom Events and Variables ==&lt;br /&gt;
&lt;br /&gt;
[http://joshwilson.net Josh Wilson], Systems Integration Librarian, State Library of North Carolina - joshwilsonnc@gmail.com&lt;br /&gt;
&lt;br /&gt;
At the State Library of North Carolina, we had more specific questions about the use of our digital collections than standard GA could provide. A few implementations of custom events and custom variables later, we have our answers.&lt;br /&gt;
&lt;br /&gt;
I'll demonstrate how these analytics add-ons work, and why implementation can sometimes be more complicated than just adding a few lines of JavaScript to your ga.js. I'll discuss some specific examples in use at the SLNC:&lt;br /&gt;
&lt;br /&gt;
* Capturing the content of specific metadata fields in CONTENTdm as Custom Events &lt;br /&gt;
* Recording Drupal taxonomy terms as Custom Variables&lt;br /&gt;
&lt;br /&gt;
In both instances, this data deepened our understanding of how our sites and collections were being used, and in turn, we were able to report usage more accurately to content contributors and other stakeholders.&lt;br /&gt;
&lt;br /&gt;
More on: [https://developers.google.com/analytics/devguides/collection/gajs/eventTrackerGuide GA Custom Events] | [https://developers.google.com/analytics/devguides/collection/gajs/gaTrackingCustomVariables GA Custom Variables]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Behold Fedora 4: The Incredible Shrinking Repository! ==&lt;br /&gt;
&lt;br /&gt;
Esmé Cowles, UC San Diego Library.  Previous talk: [http://code4lib.org/conference/2013/cowles-critchlow-westbrook All Teh Metadatas Re-Revisited] (2013)&lt;br /&gt;
&lt;br /&gt;
* One repository contains untold numbers of digital objects and powers many Hydra and Islandora apps&lt;br /&gt;
* It speaks RDF, but contains no triplestore! (triplestores sold separately, SPARQL Update may be involved, some restrictions apply)&lt;br /&gt;
* Flexible enough to tie itself in knots implementing storage and access control policies&lt;br /&gt;
* Witness feats of strength and scalability, with dramatically increased performance and clustering&lt;br /&gt;
* Plumb the depths of bottomless hierarchies, and marvel at the metadata woven into the very fabric of the repository&lt;br /&gt;
* Ponder the paradox of ingesting large files by not ingesting them&lt;br /&gt;
* Be amazed as Fedora 4 swallows other systems whole (including Fedora 3 repositories)&lt;br /&gt;
* Watch novice developers setup Fedora 4 from scratch, with just a handful of incantations to Git and Maven&lt;br /&gt;
&lt;br /&gt;
The Fedora Commons Repository is the foundation of many digital collections, e-research, digital library, archives, digital preservation, institutional repository and open access publishing systems.  This talk will focus on how Fedora 4 improves core repository functionality, adds new features, maintains backwards compatibility, and addresses the shortcomings of Fedora 3.&lt;br /&gt;
&lt;br /&gt;
== Organic Free-Range API Development - Making Web Services That You Will Actually Want to Consume ==&lt;br /&gt;
&lt;br /&gt;
Steve Meyer and Karen Coombs, OCLC&lt;br /&gt;
&lt;br /&gt;
Building web services can have great benefits by providing reusability of data and functionality. Underpinning your applications with a web service will allow you to write code once and support multiple environments: your library's web app, mobile applications, the embedded widget in your campus portal. However, building a web service is its own kind of artful programming. Doing it well requires attention to many of the same techniques and requirements as building web applications, though with different outcomes. &lt;br /&gt;
&lt;br /&gt;
So what are the usability principles for web services? How do you build a web service that you (and others) will actually want to use? In this talk, we’ll share some of the lessons learned - the good, the bad, and the ugly - through OCLC's work on the WorldCat Metadata API. This web service is a sophisticated API that provides external clients with read and write access to WorldCat data. It provides a model to help aspiring API creators navigate the potential complications of crafting a web service. We'll cover:&lt;br /&gt;
&lt;br /&gt;
* Loose coupling of data assets and resource-oriented data modeling at the core&lt;br /&gt;
* Coding to standards vs. exposure of an internal data model&lt;br /&gt;
* Authentication and security for web services: API Keys, Digital Signing, OAuth Flows&lt;br /&gt;
* Building web services that behave as a suite so it looks like the left hand knows what the right hand is doing&lt;br /&gt;
&lt;br /&gt;
So at the end of the day, your team will know your API is a very good egg after all. &lt;br /&gt;
&lt;br /&gt;
If accepted, the presenters intend to produce and share a Quick Guide for building a web service that will reflect content presented in the talk.&lt;br /&gt;
&lt;br /&gt;
== Lucene's Latest (for Libraries) ==&lt;br /&gt;
&lt;br /&gt;
erik.hatcher@lucidworks.com&lt;br /&gt;
&lt;br /&gt;
Lucene powers the search capabilities of practically all library discovery platforms, by way of Solr, etc.  The Lucene project evolves rapidly, and it's a full-time job to keep up with the ever improving features and scalability.   This talk will distill and showcase the most relevant(!) advancements to date.&lt;br /&gt;
&lt;br /&gt;
== The Why and How of Very Large Displays in Libraries. ==&lt;br /&gt;
&lt;br /&gt;
* Cory Lown, NCSU Libraries, cwlown@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Previous Code4Lib Presentations:&lt;br /&gt;
* [http://code4lib.org/conference/2012/lown How People Search the Library from a Single Search Box]  2012&lt;br /&gt;
* [http://code4lib.org/conference/2010/orphanides_lown_lynema Enhancing Discoverability with Virtual Shelf Browse] 2010&lt;br /&gt;
&lt;br /&gt;
Built into the walls of NC State's new Hunt Library are several [http://www.christiedigital.com/en-us/digital-signage/products/microtiles/pages/microtiles-digital-signage-video-wall.aspx Christie MicroTile Display Wall Systems]. What does a library do with a display that's seven feet tall and over twenty feet wide? I'll talk about why libraries might want large displays like this, what we're doing with them right now, and what we might do with them in the future. And I'll get into the fun details of how you build web applications for a browser window with about 14 million pixels (about 10 million more than a dual 24&amp;quot; monitor desktop setup).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[:Category:Code4Lib2014]]&lt;/div&gt;</summary>
		<author><name>Cwlown</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_Prepared_Talk_Proposals&amp;diff=39776</id>
		<title>2014 Prepared Talk Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_Prepared_Talk_Proposals&amp;diff=39776"/>
				<updated>2013-11-07T15:36:07Z</updated>
		
		<summary type="html">&lt;p&gt;Cwlown: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==2014 Prepared Talk Proposals==&lt;br /&gt;
&lt;br /&gt;
'''Proposals for Prepared Talks:'''&lt;br /&gt;
&lt;br /&gt;
Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:&lt;br /&gt;
 &lt;br /&gt;
* ''Projects'' you've worked on which incorporate innovative implementation of existing technologies and/or development of new software&lt;br /&gt;
* ''Tools and technologies'' – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)&lt;br /&gt;
* ''Technical issues'' - Big issues in library technology that should be addressed or better understood&lt;br /&gt;
* ''Relevant non-technical issues'' – Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc.&lt;br /&gt;
&lt;br /&gt;
'''To Propose a Talk'''&lt;br /&gt;
* Log in to the wiki in order to submit a proposal. If you are not already registered, follow the instructions to do so.&lt;br /&gt;
* Provide a title and brief (500 words or fewer) description of your proposed talk.&lt;br /&gt;
* If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist us in opening the conference to new presenters.&lt;br /&gt;
&lt;br /&gt;
As in past years, the Code4Lib community will vote on proposals that they would like to see included in the program. This year, however, only the top 10 proposals will be guaranteed a slot at the conference. Additional presentations will be selected by the Program Committee in an effort to ensure diversity in program content. Community votes will, of course, still weigh heavily in these decisions.&lt;br /&gt;
&lt;br /&gt;
Presenters whose proposals are selected for inclusion in the program will be guaranteed an opportunity to register for the conference. The standard conference registration fee will still apply.&lt;br /&gt;
&lt;br /&gt;
''Proposals can be submitted through '''Friday, November 8, 2013, at 5pm PST'''''. Voting will commence on November 18, 2013 and continue through December 6, 2013. The final line-up of presentations will be announced in early January, 2014.&lt;br /&gt;
&lt;br /&gt;
'''Talk Proposals'''&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Using Drupal to drive alternative presentation systems ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Recently, we have been building systems that use angular.js, Rails, or other systems for presentation, while leveraging Drupal's sophisticated content management capabilities on the back end.&lt;br /&gt;
&lt;br /&gt;
So far, these have been one-way systems, but as we move to Drupal 8 we are beginning to explore ways to further decouple the presentation and CMS functions.&lt;br /&gt;
&lt;br /&gt;
== A Book, a Web Browser and a Tablet: How Bibliotheca Alexandrina's Book Viewer Framework Makes It Possible ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Mohammed.abuouda|Mohammed Abu ouda]], Bibliotheca Alexandrina (The new Library of Alexandria)&lt;br /&gt;
&lt;br /&gt;
A lot of institutions around the world are engaged in multiple digitization projects aiming at preserving the human knowledge present in books and availing them through multiple channels to people around the whole globe. These efforts will sure help close the digital gap particularly with the arrival of affordable e-readers, mobile phones and network coverage. However, the digital reading experience has not yet arrived to its maximum potential. Many readers miss features they like in their good old books and wish to find them in their digital counterpart. In an attempt to create a unique digital reading experience, Bibliotheca Alexandria (BA) created a flexible book viewing framework that is currently used to access its current collection of more than 300,000 digital books in five different languages which includes the largest collection of digitized Arabic books.&lt;br /&gt;
&lt;br /&gt;
Using open source tools, BA used the framework to develop a modular book viewer that can be deployed in different environments and is currently at the heart of various BA projects. The Book viewer provides several features creating a more natural reading experience. As with physical books, the reader can now personalize the books he reads by adding annotations like highlights, underlines and sticky notes to capture his thoughts and ideas in addition to being able to share the book with friends on social networks. The reader can perform a search across the content of the book receiving highlighted search results within the pages of the book. More features can be further added to the book viewer through its plugin architecture.&lt;br /&gt;
&lt;br /&gt;
== Structured data NOW: seeding schema.org in library systems ==&lt;br /&gt;
 &lt;br /&gt;
* [http://coffeecode.net Dan Scott], Laurentian University&lt;br /&gt;
** Previous code4lib presentations: [https://archive.org/details/code4lib.conf.2008.pres.CouchDBsacrilege CouchDB is sacrilege... mmm, delicious sacrilege] at Code4Lib 2008&lt;br /&gt;
&lt;br /&gt;
The semantic web, linked data, and structured data are all fantastic ideas with a barrier imposed by implementation constraints. If their system does not allow customizations, or the institution lacks skilled human resources, it does not matter how enthused a given library might be about publishing structured data... it will not happen. However, if the software in use simply publishes structured data by default, then the web will be populated for free. Really! No extra resources necessary.&lt;br /&gt;
&lt;br /&gt;
This presentation highlights Dan's work with systems such as Evergreen, Koha, and VuFind to enable the publication of schema.org structured data out-of-the-box. Along the way, we reflect the current state of the W3C Schema.org Bibliographic Extension community group efforts to shape the evolution of the schema.org vocabulary. Finally, hold on tight as we contemplate next steps and the possibilities of a world where structured data is the norm on the web.&lt;br /&gt;
&lt;br /&gt;
== Towards Pasta Code Nirvana: Using JavaScript MVC to Fill Your Programming Ravioli ==&lt;br /&gt;
&lt;br /&gt;
* Bret Davidson, North Carolina State University Libraries, bret_davidson@ncsu.edu&lt;br /&gt;
** Previous Code4Lib Presentations: [http://wiki.code4lib.org/index.php/2013_talks_proposals#Data-Driven_Documents:_Visualizing_library_data_with_D3.js Visualizing library data with D3.js] at Code4Lib 2013&lt;br /&gt;
&lt;br /&gt;
JavaScript MVC frameworks are ushering in a golden age of robust and responsive web applications that take advantage of evergreen browsers, performant JS engines, and the unprecedented reach provided by billions of personal computing devices. The web browser has emerged as the world’s most popular application runtime and the complexity[1] and scope of JavaScript applications has exploded accordingly. Server-side web frameworks like Rails and Django have helped developers adhere to best practices like modularity, dependency injection, and unit testing for years, practices that are now being applied to JavaScript development through projects like Backbone[2], Ember[3], and Angular[4].&lt;br /&gt;
&lt;br /&gt;
This talk will discuss the issues JavaScript MVC frameworks are trying to solve, common features like data binding, implications for the future of web development[5], and the appropriateness of JavaScript MVC for library applications.&lt;br /&gt;
&lt;br /&gt;
*[1]http://en.wikipedia.org/wiki/Spaghetti_code&lt;br /&gt;
*[2]http://backbonejs.org&lt;br /&gt;
*[3]http://emberjs.com&lt;br /&gt;
*[4]http://angularjs.org&lt;br /&gt;
*[5]http://tomdale.net/2013/09/progressive-enhancement-is-dead/&lt;br /&gt;
&lt;br /&gt;
== WebSockets for Real-Time and Interactive Interfaces ==&lt;br /&gt;
&lt;br /&gt;
* [http://ronallo.com Jason Ronallo], NCSU Libraries, jason_ronallo@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Previous Code4Lib presentations:&lt;br /&gt;
* [http://code4lib.org/conference/2012/ronallo HTML5 Microdata and Schema.org] 2012&lt;br /&gt;
* [http://code4lib.org/conference/2013/ronallo HTML5 Video Now!] 2013&lt;br /&gt;
&lt;br /&gt;
Watching the Google Analytics Real-Time dashboard for the first time was mesmerizing. As soon as someone visited a site, I could see what page they were on. For a digital collections site with a lot of images, it was fun to see what visitors were looking at. But getting from Google Analytics to the image or other content of what was currently being viewed was cumbersome. The real-time experience was something I wanted share with others. I'll show you how I used a WebSocket service to create a real-time interface to digital collections.&lt;br /&gt;
&lt;br /&gt;
In the Hunt Library at NCSU we have some large video walls. I wanted to make HTML-based exhibits that featured viewer interactions. I'll show you how I converted Listen to Wikipedia [1] into an bring-your-own-device interactive exhibit. With WebSockets any HTML page can be remote controlled by any internet connected device.&lt;br /&gt;
&lt;br /&gt;
I will attempt to include real-time audience participation.&lt;br /&gt;
&lt;br /&gt;
[1] http://listen.hatnote.com/&lt;br /&gt;
&lt;br /&gt;
== Rapid Development of Automated Tasks with the File Analyzer ==&lt;br /&gt;
&lt;br /&gt;
* Terry Brady, Georgetown University Libraries, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Libraries have customized the File Analyzer and Metadata Harvester application (https://github.com/Georgetown-University-Libraries/File-Analyzer) to solve a number of library automation challenges:&lt;br /&gt;
* validating digitized and reformatted files&lt;br /&gt;
* validating vendor statistics for counter compliance&lt;br /&gt;
* preparing collections of digital files for archiving and ingest&lt;br /&gt;
* manipulating ILS import and export files&lt;br /&gt;
&lt;br /&gt;
The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census.  After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform.  Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.&lt;br /&gt;
&lt;br /&gt;
The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules.  As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.&lt;br /&gt;
&lt;br /&gt;
Learn about the functionality that is available for download, how you can use this tool to automate workflows from digital collections to ILS ingests to electronic resources statistics and also discuss the opportunities to collaborate on enhancements to this application!&lt;br /&gt;
&lt;br /&gt;
== GeoHydra: How to Build a Geospatial Digital Library with Fedora ==&lt;br /&gt;
 &lt;br /&gt;
* [http://stanford.edu/~drh Darren Hardy], Stanford University, drh@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Geographically-rich data are exploding and putting fear in those trying to&lt;br /&gt;
tackle integrating them into existing digital library infrastructures.&lt;br /&gt;
Building a spatial data infrastructure that integrates with your digital&lt;br /&gt;
library infrastructure need not be a daunting task. We have successfully&lt;br /&gt;
deployed a geospatial digital library infrastructure using Fedora and&lt;br /&gt;
open-source geospatial software [1]. We'll discuss the primary design&lt;br /&gt;
decisions and technologies that led to a production deployment within a few&lt;br /&gt;
months. Briefly, our architecture revolves around discovery, delivery, and&lt;br /&gt;
metadata pipelines using open-source OpenGeoPortal [2], Solr [3], GeoServer&lt;br /&gt;
[4], PostGIS [5], and GeoNetwork [6] technologies, plus the proprietary ESRI&lt;br /&gt;
ArcMap [7] -- the GIS industry's workhorse. Finally, we'll discuss the key&lt;br /&gt;
skillsets needed to build and maintain a spatial data infrastructure.&lt;br /&gt;
&lt;br /&gt;
[1] http://foss4g.org&lt;br /&gt;
[2] http://opengeoportal.org&lt;br /&gt;
[3] http://lucene.apache.org/solr&lt;br /&gt;
[4] http://geoserver.org&lt;br /&gt;
[5] http://postgis.net&lt;br /&gt;
[6] http://geonetwork-opensource.org&lt;br /&gt;
[7] http://esri.com&lt;br /&gt;
&lt;br /&gt;
==Under the Hood of Hadoop Processing at OCLC Research ==&lt;br /&gt;
&lt;br /&gt;
[http://roytennant.com/ Roy Tennant]&lt;br /&gt;
&lt;br /&gt;
* Previous Code4Lib presentations: 2006: &amp;quot;The Case for Code4Lib 501c(3)&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[http://hadoop.apache.org/ Apache Hadoop] is widely used by Yahoo!, Google, and many others to process massive amounts of data quickly. OCLC Research uses a 40-node compute cluster with Hadoop and HBase to process the 300 million MARC records of WorldCat in various ways. This presentation will explain how Hadoop MapReduce works and illustrate it with specific examples and code. The role of the jobtracker in both monitoring and reporting on processes will be explained. String searching WorldCat will also be demonstrated live.&lt;br /&gt;
&lt;br /&gt;
== Quick and Easy Data Visualization with Google Visualization API and Google Chart Libraries ==&lt;br /&gt;
 &lt;br /&gt;
[http://bohyunkim.net/blog Bohyun Kim], Florida International University, bohyun.kim@fiu.edu&lt;br /&gt;
* 'No' previous Code4Lib presentations &lt;br /&gt;
&lt;br /&gt;
Do most of the data that your library collects stay in spreadsheets or are published as a static table with a series of boring numbers? Do your library stakeholders spend more time collecting the data than using it as a decision-making tool because the data is presented in a way that makes it hard for them [http://developers.google.com/chart/interactive/docs/gallery to quickly grasp its significance? ]&lt;br /&gt;
&lt;br /&gt;
This talk will provide an overview of [http://developers.google.com/chart/interactive/docs/reference Google Visualization API] [2] and [http://developers.google.com/chart/ Google Chart Libraries] [3] to get you started on the way to quickly query and visualize your library data from remote data sources (e.g. a Google Spreadsheet or your own database) with (or without) cool-looking user-controls, animation effects, and even a dashboard.&lt;br /&gt;
&lt;br /&gt;
== Leap Motion + Rare Books: A hands-free way to view and interact with rare books in 3D ==&lt;br /&gt;
 &lt;br /&gt;
[http://http://www.youtube.com/user/jpdenzer Juan Denzer], Binghamton University, jdenzer@binghamton.edu&lt;br /&gt;
* 'No' previous Code4Lib presentations &lt;br /&gt;
&lt;br /&gt;
As rare books become more delicate over time, making them available to the public becomes harder.  We at Binghamton University Library have developed an application that makes it easier to view rare books without ever having to touch them.  We have combined the Leap Motion hands-free device and 3D rendered models to create a new virtual experience for the viewer.&lt;br /&gt;
&lt;br /&gt;
The application allows the user to rotate and zoom in on a 3D representation of a rare book.  The user is also able to ‘open’ the virtual book and flip through it using a natural user interface.  Such as swiping the hand left or right to turn the page.&lt;br /&gt;
&lt;br /&gt;
The application is built on the .Net framework and is written in C#.  3D models are created using simple 3D software such as sketchup or Blender.  Scans of the book cover and spine are created using simple flatbed scanners.  The inside pages are scanned using overhead scanners. &lt;br /&gt;
&lt;br /&gt;
This talk with discuss the technologies used in developing the application and virtually any library could implement the application with virtually no coding at all. This presentation will have a demonstration of the software and also a chance for audience members to experience the Rare Book Leap Motion App themselves.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Course Reserves Unleashed! ==&lt;br /&gt;
 &lt;br /&gt;
* Bobbi Fox, Library Technology Services, Harvard University, bobbi_fox@harvard.edu&lt;br /&gt;
* Gloria Korsman, Andover-Harvard Theological Library&lt;br /&gt;
** No previous Code4Lib presentations &lt;br /&gt;
&lt;br /&gt;
Hey kids!  Remember when SOAP was used for something other than washing?  Our sophisticated (and highly functional) Course Reserves Request system does!&lt;br /&gt;
&lt;br /&gt;
However, while the system is great for submitting and  processing course reserve requests, the student-facing presentation through Havard’s home-grown -- and soon to be replaced -- LMS leaves a lot to be desired.  &lt;br /&gt;
&lt;br /&gt;
Follow along as we leverage Solr 4 as a No-SQL database, along with more progressive RESTful API techniques, to release Reserves data into the wild without interfering with reserves request processing -- and, in the process, open up the opportunity for other schools to feed their data in as well.&lt;br /&gt;
&lt;br /&gt;
== We Are All Disabled! Universal Web Design Making Web Services Accessible for Everyone ==&lt;br /&gt;
 &lt;br /&gt;
Cynthia Ng, Accessibility Librarian, CILS at Langara College&lt;br /&gt;
* No previous Code4Lib presentations (not counting lightning talks)&lt;br /&gt;
&lt;br /&gt;
We’re building and improving tools and services all the time, but do you only develop for the “average” user or add things for “disabled” users? We all use “assistive” technology accessing information in a multitude of ways with different platforms, devices, etc. Let’s focus on providing web services that are accessible to everyone without it being onerous or ugly. The aim is to get you thinking about what you can do to make web-based services and content more accessible for all from the beginning or with small amounts of effort whether you're a developer or not.&lt;br /&gt;
&lt;br /&gt;
The goal of the presentation is to provide both developers and content creators with information on simple, practical ways to make web content and web services more accessible. However, rather than thinking about putting in extra effort or making adjustment for those with disabilities, I want to help people think about how to make their websites more accessible for all users through universal web design.&lt;br /&gt;
&lt;br /&gt;
== Personalize your Google Analytics Data with Custom Events and Variables ==&lt;br /&gt;
&lt;br /&gt;
[http://joshwilson.net Josh Wilson], Systems Integration Librarian, State Library of North Carolina - joshwilsonnc@gmail.com&lt;br /&gt;
&lt;br /&gt;
At the State Library of North Carolina, we had more specific questions about the use of our digital collections than standard GA could provide. A few implementations of custom events and custom variables later, we have our answers.&lt;br /&gt;
&lt;br /&gt;
I'll demonstrate how these analytics add-ons work, and why implementation can sometimes be more complicated than just adding a few lines of JavaScript to your ga.js. I'll discuss some specific examples in use at the SLNC:&lt;br /&gt;
&lt;br /&gt;
* Capturing the content of specific metadata fields in CONTENTdm as Custom Events &lt;br /&gt;
* Recording Drupal taxonomy terms as Custom Variables&lt;br /&gt;
&lt;br /&gt;
In both instances, this data deepened our understanding of how our sites and collections were being used, and in turn, we were able to report usage more accurately to content contributors and other stakeholders.&lt;br /&gt;
&lt;br /&gt;
More on: [https://developers.google.com/analytics/devguides/collection/gajs/eventTrackerGuide GA Custom Events] | [https://developers.google.com/analytics/devguides/collection/gajs/gaTrackingCustomVariables GA Custom Variables]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Behold Fedora 4: The Incredible Shrinking Repository! ==&lt;br /&gt;
&lt;br /&gt;
Esmé Cowles, UC San Diego Library.  Previous talk: [http://code4lib.org/conference/2013/cowles-critchlow-westbrook All Teh Metadatas Re-Revisited] (2013)&lt;br /&gt;
&lt;br /&gt;
* One repository contains untold numbers of digital objects and powers many Hydra and Islandora apps&lt;br /&gt;
* It speaks RDF, but contains no triplestore! (triplestores sold separately, SPARQL Update may be involved, some restrictions apply)&lt;br /&gt;
* Flexible enough to tie itself in knots implementing storage and access control policies&lt;br /&gt;
* Witness feats of strength and scalability, with dramatically increased performance and clustering&lt;br /&gt;
* Plumb the depths of bottomless hierarchies, and marvel at the metadata woven into the very fabric of the repository&lt;br /&gt;
* Ponder the paradox of ingesting large files by not ingesting them&lt;br /&gt;
* Be amazed as Fedora 4 swallows other systems whole (including Fedora 3 repositories)&lt;br /&gt;
* Watch novice developers setup Fedora 4 from scratch, with just a handful of incantations to Git and Maven&lt;br /&gt;
&lt;br /&gt;
The Fedora Commons Repository is the foundation of many digital collections, e-research, digital library, archives, digital preservation, institutional repository and open access publishing systems.  This talk will focus on how Fedora 4 improves core repository functionality, adds new features, maintains backwards compatibility, and addresses the shortcomings of Fedora 3.&lt;br /&gt;
&lt;br /&gt;
== Organic Free-Range API Development - Making Web Services That You Will Actually Want to Consume ==&lt;br /&gt;
&lt;br /&gt;
Steve Meyer and Karen Coombs, OCLC&lt;br /&gt;
&lt;br /&gt;
Building web services can have great benefits by providing reusability of data and functionality. Underpinning your applications with a web service will allow you to write code once and support multiple environments: your library's web app, mobile applications, the embedded widget in your campus portal. However, building a web service is its own kind of artful programming. Doing it well requires attention to many of the same techniques and requirements as building web applications, though with different outcomes. &lt;br /&gt;
&lt;br /&gt;
So what are the usability principles for web services? How do you build a web service that you (and others) will actually want to use? In this talk, we’ll share some of the lessons learned - the good, the bad, and the ugly - through OCLC's work on the WorldCat Metadata API. This web service is a sophisticated API that provides external clients with read and write access to WorldCat data. It provides a model to help aspiring API creators navigate the potential complications of crafting a web service. We'll cover:&lt;br /&gt;
&lt;br /&gt;
* Loose coupling of data assets and resource-oriented data modeling at the core&lt;br /&gt;
* Coding to standards vs. exposure of an internal data model&lt;br /&gt;
* Authentication and security for web services: API Keys, Digital Signing, OAuth Flows&lt;br /&gt;
* Building web services that behave as a suite so it looks like the left hand knows what the right hand is doing&lt;br /&gt;
&lt;br /&gt;
So at the end of the day, your team will know your API is a very good egg after all. &lt;br /&gt;
&lt;br /&gt;
If accepted, the presenters intend to produce and share a Quick Guide for building a web service that will reflect content presented in the talk.&lt;br /&gt;
&lt;br /&gt;
== Lucene's Latest (for Libraries) ==&lt;br /&gt;
&lt;br /&gt;
erik.hatcher@lucidworks.com&lt;br /&gt;
&lt;br /&gt;
Lucene powers the search capabilities of practically all library discovery platforms, by way of Solr, etc.  The Lucene project evolves rapidly, and it's a full-time job to keep up with the ever improving features and scalability.   This talk will distill and showcase the most relevant(!) advancements to date.&lt;br /&gt;
&lt;br /&gt;
== The Why and How of Very Large Displays in Libraries. ==&lt;br /&gt;
&lt;br /&gt;
* Cory Lown, NCSU Libraries, cwlown@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Previous Code4Lib Presentations:&lt;br /&gt;
[http://code4lib.org/conference/2012/lown How People Search the Library from a Single Search Box]  2012&lt;br /&gt;
[http://code4lib.org/conference/2010/orphanides_lown_lynema Enhancing Discoverability with Virtual Shelf Browse] 2010&lt;br /&gt;
&lt;br /&gt;
Built into the walls of NC State's new Hunt Library are several [http://www.christiedigital.com/en-us/digital-signage/products/microtiles/pages/microtiles-digital-signage-video-wall.aspx Christie MicroTile Display Wall Systems]. What does a library do with a display that's seven feet tall and over twenty feet wide? I'll talk about why libraries might want large displays like this, what we're doing with them right now, and what we might do with them in the future. And I'll get into the fun details of how you build web applications for a browser window with about 14 million pixels (about 10 million more than a dual 24&amp;quot; monitor desktop setup).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[:Category:Code4Lib2014]]&lt;/div&gt;</summary>
		<author><name>Cwlown</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&amp;diff=39291</id>
		<title>Code4Lib 2014 Conference Planning Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&amp;diff=39291"/>
				<updated>2013-06-14T19:12:40Z</updated>
		
		<summary type="html">&lt;p&gt;Cwlown: /* Scholarships Committee */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2014 Committees =&lt;br /&gt;
&lt;br /&gt;
If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term).  Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site.  Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference.  Please feel free to improve the summary statements for each of the committees.&lt;br /&gt;
&lt;br /&gt;
We hope to include at least one local person on each committee.&lt;br /&gt;
&lt;br /&gt;
== Book Give-Away Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.&lt;br /&gt;
&lt;br /&gt;
* Kevin S. Clarke (O'Reilly) and general wrangling&lt;br /&gt;
* Michael B. Klein (Pragmatic) and winner-picker app&lt;br /&gt;
&lt;br /&gt;
== Keynote Speakers Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.&lt;br /&gt;
&lt;br /&gt;
* Jason Casden (NCSU)&lt;br /&gt;
* Tom Johnson (Johnson.tom@gmail.com)&lt;br /&gt;
&lt;br /&gt;
== Onsite Volunteer Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee solicits volunteers to do whatever tasks are needed in person at the conference.&lt;br /&gt;
&lt;br /&gt;
* Kevin S. Clarke&lt;br /&gt;
* Kevin Beswick (NCSU)&lt;br /&gt;
* Yan Wang (NCCU)&lt;br /&gt;
&lt;br /&gt;
== Pre-conference Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee plans the pre-conference day.  It keeps strong lines of communications open with the Program Committee.  It also helps shepherd events on the day itself.&lt;br /&gt;
&lt;br /&gt;
* Adam Constabaris (NCSU)&lt;br /&gt;
* Tim Shearer (UNC)&lt;br /&gt;
&lt;br /&gt;
== Program Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting both pre-conferences and regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.&lt;br /&gt;
&lt;br /&gt;
* Tom Johnson (Johnson.tom@gmail.com)&lt;br /&gt;
* Kevin Beswick (NCSU)&lt;br /&gt;
* Ranti Junus (MSU)&lt;br /&gt;
&lt;br /&gt;
== Scholarships Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee works with funding institutions to arrange the scholarships offered.  They solicit submissions and select winners of the scholarship(s).  They also work with the winners to plan their travel and arrangements.&lt;br /&gt;
&lt;br /&gt;
* Jason Ronallo (NCSU)&lt;br /&gt;
* Cory Lown (NCSU)&lt;br /&gt;
&lt;br /&gt;
== Social Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
The committee plans, proposes, and organizes the evening activities.&lt;br /&gt;
&lt;br /&gt;
* Jason Raitz&lt;br /&gt;
* Rosalyn Metz&lt;br /&gt;
* Dre&lt;br /&gt;
* Becky Yoose&lt;br /&gt;
&lt;br /&gt;
== Sponsorships Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.).  Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference.  These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.&lt;br /&gt;
&lt;br /&gt;
* Tim McGeary (lead worrier)&lt;br /&gt;
* Roy Tennant (OCLC)&lt;br /&gt;
* Shaun Ellis (shaune@princeton.edu)&lt;br /&gt;
* Robert H. McDonald (Indiana)&lt;br /&gt;
* Sean Chen (Duke)&lt;br /&gt;
* Thomas Dowling (Wake Forest)&lt;br /&gt;
* Will Sexton (Duke)&lt;br /&gt;
* Jeff Campbell (UNC-CH)&lt;br /&gt;
* Brett Bonfield (Collingswood Public)&lt;br /&gt;
&lt;br /&gt;
== Streaming Video Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.&lt;br /&gt;
&lt;br /&gt;
- Francis Kayiwa&lt;br /&gt;
&lt;br /&gt;
== T-Shirt Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference.&lt;br /&gt;
&lt;br /&gt;
*Charlie Morris (NCSU)&lt;br /&gt;
&lt;br /&gt;
== Voting Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.&lt;br /&gt;
&lt;br /&gt;
*Adam Constabaris (NCSU)&lt;br /&gt;
&lt;br /&gt;
== Whatever Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee does whatever the organizers can't talk anyone else into doing.&lt;br /&gt;
&lt;br /&gt;
* Francis Kayiwa&lt;br /&gt;
* Kevin S. Clarke&lt;br /&gt;
* Dre&lt;br /&gt;
* Ranti Junus&lt;br /&gt;
&lt;br /&gt;
== Wifi / Electrical / IRC Committee==&lt;br /&gt;
&lt;br /&gt;
This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.&lt;br /&gt;
&lt;br /&gt;
* [[User:highermath|Cary Gordon]], cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
This is a newly proposed committee.&lt;br /&gt;
&lt;br /&gt;
= Documentation =&lt;br /&gt;
To help with documention, no need to sign up, just start editing.&lt;br /&gt;
* [[How To Plan A Code4LibCon]]&lt;br /&gt;
&lt;br /&gt;
== Documentation Interest Group ==&lt;br /&gt;
Promote ongoing documentation efforts.&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2014]]&lt;/div&gt;</summary>
		<author><name>Cwlown</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_Lightning_Talks_Signup&amp;diff=36977</id>
		<title>2013 Lightning Talks Signup</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_Lightning_Talks_Signup&amp;diff=36977"/>
				<updated>2013-02-18T14:19:03Z</updated>
		
		<summary type="html">&lt;p&gt;Cwlown: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Sign up for Lightning Talks!!'''&lt;br /&gt;
&lt;br /&gt;
Lightning talks are scheduled on all three days of the conference. A lightning talk is a fast-paced 5 minute talk on a topic of your choosing. Sign-ups for lightning talks will open immediately following the first keynote.&lt;br /&gt;
&lt;br /&gt;
Mark Jason Dominus has a nice page [http://perl.plover.com/lt/lightning-talks.html about lightning talks], which includes this summary of why you might want to do one:&lt;br /&gt;
&lt;br /&gt;
''Maybe you've never given a talk before, and you'd like to start small. For a Lightning Talk, you don't need to make slides, and if you do decide to make slides, you only need to make three.''&lt;br /&gt;
&lt;br /&gt;
''Maybe you're nervous and you're afraid you'll mess up. It's a lot easier to plan and deliver a five minute talk than it is to deliver a long talk. And if you do mess up, at least the painful part will be over quickly.''&lt;br /&gt;
&lt;br /&gt;
''Maybe you don't have much to say. Maybe you just want to ask a question, or invite people to help you with your project, or boast about something you did, or tell a short cautionary story. These things are all interesting and worth talking about, but there might not be enough to say about them to fill up thirty minutes.''&lt;br /&gt;
&lt;br /&gt;
You might also like Mark Fowler's's [http://www.perl.com/pub/2004/07/30/lightningtalk.html Advice for Giving a Lightning Talk].&lt;br /&gt;
&lt;br /&gt;
Have something to add but didn't get a chance to do it in Chicago?  Consider signing up to present at the [[Virtual Lightning Talks]] on April 3rd, 2013.&lt;br /&gt;
&lt;br /&gt;
'''LIGHTNING TALK SIGNUPS OPEN AT 10 AM EST ON FEBRUARY 12'''&lt;br /&gt;
&lt;br /&gt;
Those who already have presentation slots, please hold off and give those without slots lightning talk chances, to spread around the opportunity to talk to the conference. &lt;br /&gt;
&lt;br /&gt;
=== Tuesday, 4:20-5:20pm [12 slots] ===&lt;br /&gt;
&lt;br /&gt;
Enter ''Name'' -- ''Title of Talk''&lt;br /&gt;
&lt;br /&gt;
# Cynthia Ng -- [http://apps.library.ryerson.ca/bookfinder/ RULA Bookfinder]&lt;br /&gt;
# Julien Gibert - turning a solr response into a rdf file&lt;br /&gt;
# Bill Dueber -- Datamart report generator at UMich&lt;br /&gt;
# Jonathan Rochkind -- bento_search&lt;br /&gt;
# Ross Singer - How are you managing copyright?&lt;br /&gt;
# Masao Takaku - [http://www.slideshare.net/tmasao/savemlak-project saveMLAK project for two years] - http://savemlak.jp/&lt;br /&gt;
# Jon Stroop - [https://gist.github.com/jpstroop/4771145 Loris Image Server]&lt;br /&gt;
# Eric Nord - Candybars for bugs&lt;br /&gt;
# Megan O'Neill Kudzia -- games for pedagogy in the library&lt;br /&gt;
# Geoffrey Boushey - GEDI reference app for Inter Library Loan&lt;br /&gt;
# john sarnowski - [http://t.co/KKsP7gwd Audio archiving with full text search]&lt;br /&gt;
# George Campbell - [http://tallgeorge.com/3d/about/ three.js: 3D Objects in the browser]&lt;br /&gt;
&lt;br /&gt;
=== Wenesday, 4:20-5:20pm [12 slots] ===&lt;br /&gt;
&lt;br /&gt;
Enter ''Name'' -- ''Title of Talk''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
# Demian Katz - gamebooks.org, Geeby-Deeby, and the Dime Novel Bibliography Project.&lt;br /&gt;
# Rachel Frick -- LODLAM Summit 2013 and Challenge&lt;br /&gt;
# Kenny Ketner -- Occam's Reader&lt;br /&gt;
# Al Cornish - Orbis Cascade Alliance Shared ILS Project&lt;br /&gt;
# Makoto Okamoto -- [http://www.slideshare.net/arg_editor/code4-lib201320130213 Crowd Funding for Library in Japan]&lt;br /&gt;
# William Denton - Code4Lib 2013 augmented reality view in Layar&lt;br /&gt;
# Rosalyn Metz -- What I learned while I was away&lt;br /&gt;
# Nettie Lagace -- recent cool fun NISO activities&lt;br /&gt;
# chuck koscher-- Fundref&lt;br /&gt;
# Andromeda Yelton -- Five Conversations About Coding&lt;br /&gt;
#  Jeremy Morse -- mPach: Publishing directly into HathiTrust&lt;br /&gt;
# Rob Dumas -- Git in Five Minutes&lt;br /&gt;
&lt;br /&gt;
=== Thursday, 10:15-11:00am [9 slots] ===&lt;br /&gt;
&lt;br /&gt;
Enter ''Name'' -- ''Title of Talk''&lt;br /&gt;
&lt;br /&gt;
# Mark A. Matienzo - [http://matienzo.org/storage/2013/2013Feb-code4lib-lightning-talk Wielding the Whip: Affect, Archives, &amp;amp; Ontological Fusion]&lt;br /&gt;
# Jason Casden and Cory Lown - [http://www.lib.ncsu.edu/documents/dli/projects/myhuntlibrary/casdenLownLightningTalkC4l13.pdf My #HuntLibrary]&lt;br /&gt;
# Steven Anderson - [http://goo.gl/q0QfF Javascript Streaming Clientside Checksumming w/ HTML5 file upload]&lt;br /&gt;
# Will Hicks - Metadata entry beyond usability&lt;br /&gt;
# Kelly Lucas - Drupal as front-end to any Solr index&lt;br /&gt;
# Karen Coyle - Nerd Poetry&lt;br /&gt;
# Mark Redar - Django Dublin Core app and RecordExpress aka &amp;quot;Mullet EAD Maker&amp;quot;&lt;br /&gt;
# James Stuart -  Taming Email&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2013]]&lt;/div&gt;</summary>
		<author><name>Cwlown</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_Twitter_List&amp;diff=36736</id>
		<title>2013 Twitter List</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_Twitter_List&amp;diff=36736"/>
				<updated>2013-02-13T20:47:09Z</updated>
		
		<summary type="html">&lt;p&gt;Cwlown: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Put your twitter handle in here, if you're at Code4Lib 2013 Chicago. I'll add you to the [https://twitter.com/code4lib/attendees-2013 Attendees 2013 twitter list] for @code4lib when I get a chance. Thanks! -Sean&lt;br /&gt;
&lt;br /&gt;
# Becky Yoose (@yo_bj)&lt;br /&gt;
# Beatrice Pulliam (@beatricepulliam)&lt;br /&gt;
# Cynthia Ng (@TheRealArty)&lt;br /&gt;
# Nettie Lagace (@abugseye)&lt;br /&gt;
# Erin White (@erinrwhite)&lt;br /&gt;
# Maccabee Levine (@maccabeelevine)&lt;br /&gt;
# Steven Bassett (@bassettsj)&lt;br /&gt;
# Steve Oberg (@techsvcslib)&lt;br /&gt;
# Carmen Mitchell (@carmendarlene)&lt;br /&gt;
# Christie Peterson (@save4use)&lt;br /&gt;
# Jason Casden (@cazzerson)&lt;br /&gt;
# Michael Poltorak (@michaelpoltorak)&lt;br /&gt;
# Ron Gilmour (@gilmour70)&lt;br /&gt;
# James Staub (@jamesstaub)&lt;br /&gt;
# Curtis Thacker (@curtisthacker)&lt;br /&gt;
# Masao Takaku (@tmasao)&lt;br /&gt;
# Colin Watt (@colinmwatt)&lt;br /&gt;
# Dave Green (@icookwithwine)&lt;br /&gt;
# Alan Dyck (@Alan_Dyck)&lt;br /&gt;
# Megan O'Neill Kudzia (@meganoneill)&lt;br /&gt;
# Keith Nickum (@keithnickum)&lt;br /&gt;
# Matt Critchlow (@mattcritchlow)&lt;br /&gt;
# Matt Bernhardt (@morphosis7)&lt;br /&gt;
# Zorian Sasyk (@restlesslib)&lt;br /&gt;
# May Chan (@msuicat)&lt;br /&gt;
# Courtney C. Mumma (@snarkivist, @Archivematica)&lt;br /&gt;
# Scott Hanrath (@rshanrath)&lt;br /&gt;
# John Barneson (@johnbarneson)&lt;br /&gt;
# Jacob Andresen (@jacobandresen)&lt;br /&gt;
# Annie Pho (@catladylib)	&lt;br /&gt;
# Sharona Ginsberg (@linguomancer)&lt;br /&gt;
# Ayla Stein (@thestackscat)&lt;br /&gt;
# Barbara Hui (@barbarahui)&lt;br /&gt;
# Bradley Woodruff (@bofmouais)&lt;br /&gt;
# Mads Villadsen (@maxxkrakoa)&lt;br /&gt;
# Jørn Thøgersen (@jorntx)&lt;br /&gt;
# Raman Chandrasekar (@synthesiser)&lt;br /&gt;
# Mark Bussey (@clark_tc)&lt;br /&gt;
# Ian Walls (@sekjal)&lt;br /&gt;
# Kosuke Tanabe (@nabeta)&lt;br /&gt;
# Ranti Junus (@ranti)&lt;br /&gt;
# Al Cornish (@alncornish)&lt;br /&gt;
# Chad Nelson (@bibliotechy)&lt;br /&gt;
# Jon Gorman (@codexmonkey)&lt;br /&gt;
# Ryan Wick (@ryanwick)&lt;br /&gt;
# Jen Young (@jen_young)&lt;br /&gt;
# Jason Ronallo (@ronallo)&lt;br /&gt;
# Richard Wolf (@richwolf) &lt;br /&gt;
# Sharon Clapp (@sclapp)&lt;br /&gt;
# Virginia Schilling (@vlschilling)&lt;br /&gt;
# Courtney Greene (@xocg)&lt;br /&gt;
# Peter Murray (@DataG)&lt;br /&gt;
# Carl Wiedemann (@c4rl)&lt;br /&gt;
# Patrick Berry (@pberry)&lt;br /&gt;
# Cory Lown (@cowilo)&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2013]]&lt;/div&gt;</summary>
		<author><name>Cwlown</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_preconference_proposals&amp;diff=36102</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=36102"/>
				<updated>2013-02-08T21:03:45Z</updated>
		
		<summary type="html">&lt;p&gt;Cwlown: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Please sign up to attend by January 15th. Doesn't mean you can't change your mind, but we will use the host committee will use these numbers to assign rooms.&lt;br /&gt;
&lt;br /&gt;
Proposals '''now closed'''.&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;
====UIC Forum, 9:00 am to 5:00 pm on Monday, February 11====&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;
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;
This event is open to the library community. There is a nominal fee ($10) for non-Code4LibCon attendees.&lt;br /&gt;
&lt;br /&gt;
Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.&lt;br /&gt;
&lt;br /&gt;
====I plan on attending:====&lt;br /&gt;
&lt;br /&gt;
=====All Day=====&lt;br /&gt;
*Margaret Heller&lt;br /&gt;
*Mahria Lebow, mahria at uw edu&lt;br /&gt;
*Paula Gray-Overtoom, pgrayove at gmail.com&lt;br /&gt;
*Dhanushka Samarakoon, dhanu80 at g mail com&lt;br /&gt;
*Leo Robert Klein &amp;lt;del&amp;gt;(when he figures out what date this is)&amp;lt;/del&amp;gt; - 2/11 (9a-5p).  P.S. Oh Great One!  Who do we hand the 10 bucks to?&lt;br /&gt;
*Sarah Shealy, sarah.shealy at gmail.com&lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
* [[User:Kevenj|Keven Jeffery]]&lt;br /&gt;
* Sean Chen&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)&lt;br /&gt;
* Christina Salazar (afternoon only)&lt;br /&gt;
* Sarah Dooley (afternoon)&lt;br /&gt;
* Josh Wilson, joshwilsonnc at gmail (likely afternoon only)&lt;br /&gt;
* Ken Varnum, varnum at umich e-d-u&lt;br /&gt;
* Cody Hennesy, chennesy at library berkeley edu&lt;br /&gt;
* Colin Koteles, koteles at cod dot edu&lt;br /&gt;
&lt;br /&gt;
==Half Day Morning==&lt;br /&gt;
=== Open space session ===&lt;br /&gt;
====Boardroom, Crowne Plaza Hotel, 9:00 am to 12:00 pm on Monday, February 11====&lt;br /&gt;
* Dan Chudnov, daniel.chudnov at gmail dot etc&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;
'''I plan on attending:'''&lt;br /&gt;
* Devon Smith&lt;br /&gt;
* Esmé Cowles, escowles@ucsd.edu&lt;br /&gt;
* Jason Casden&lt;br /&gt;
* Ryan Eby&lt;br /&gt;
* mark matienzo&lt;br /&gt;
* Donald Mennerich&lt;br /&gt;
* Patrick Berry, pberry@csuchico.edu&lt;br /&gt;
* Kåre Fiedler Christiansen, kfc@statsbiblioteket.dk&lt;br /&gt;
* Michael Poltorak Nielsen mn at statsbiblioteket dot dk&lt;br /&gt;
* Joe Atzberger, ohiocore@gmail.com&lt;br /&gt;
* Shawn Carraway carraways at midlandstech dot edu&lt;br /&gt;
* Emily F. Shaw emily-f-shaw at uiowa dot edu&lt;br /&gt;
&lt;br /&gt;
=== Delivery services ===&lt;br /&gt;
====1-1010 Richard J. Daley Library, 9:00 am to 12:00 pm on Monday, February 11====&lt;br /&gt;
* Ted Lawless, Brown University Library, tlawless at brown edu.  &lt;br /&gt;
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.&lt;br /&gt;
&lt;br /&gt;
Are you interested in making it easier for users to obtain copies of known items?  Do you feel your OpenURL and Interlibrary Loan software could be streamlined?  This pre-conference workshop will focus on providing services that deliver content to users.  Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.  &lt;br /&gt;
&lt;br /&gt;
Possible topics/activities include:&lt;br /&gt;
* group discussion of what some libraries have done in this area&lt;br /&gt;
* comparisons of different approaches to addressing delivery &lt;br /&gt;
* overview of tools available &lt;br /&gt;
* sharing of strategies and experiences&lt;br /&gt;
* time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/heroku-360link Py360 Link]. &lt;br /&gt;
 &lt;br /&gt;
Resources and background information:&lt;br /&gt;
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway] &lt;br /&gt;
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]&lt;br /&gt;
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]&lt;br /&gt;
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* Ken Varnum, varnum at umich e-d-u&lt;br /&gt;
* Curtis Thacker&lt;br /&gt;
* Rosalyn Metz rosalynmetz at gmail com&lt;br /&gt;
* James Van Mil - james.vanmil at gmail com&lt;br /&gt;
* Andrew Nagy&lt;br /&gt;
* Ranti Junus&lt;br /&gt;
* Aaron Collier - acollier at csufresno edu&lt;br /&gt;
* Demian Katz - demian dot katz at villanova dot edu&lt;br /&gt;
* Jacob Andresen - jacob at reindex dot dk&lt;br /&gt;
* Erin White - erwhite at vcu edu&lt;br /&gt;
* Zeno Tajoli tajoli at cilea it&lt;br /&gt;
* William Hicks - William{dot}hicks{at}unt{dot}edu&lt;br /&gt;
* Beatrice Pulliam bpulliam at providence edu&lt;br /&gt;
* David Bietila dbietila at uchicago edu&lt;br /&gt;
* James Staub - james dot staub at nashville dot gov&lt;br /&gt;
* Cory Lown - cwlown at ncsu dot edu&lt;br /&gt;
&lt;br /&gt;
=== Intro to Blacklight CANCELED ===&lt;br /&gt;
&lt;br /&gt;
PLEASE NOTE: This pre-conference has been canceled in favor of joining forces with the RailsBridge workshop. The afternoon Blacklight session will still be offered.&lt;br /&gt;
&lt;br /&gt;
=== RailsBridge Intro to Ruby on Rails ===&lt;br /&gt;
====UIC Forum, 9:00 am to 12:00 pm on Monday, February 11====&lt;br /&gt;
* Jason Ronallo, North Carolina State University Libraries, jronallo@gmail.com&lt;br /&gt;
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)&lt;br /&gt;
* Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu&lt;br /&gt;
* Ross Singer, Talis, rossfsinger@gmail.com&lt;br /&gt;
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org&lt;br /&gt;
* Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
* James Stuart &lt;br /&gt;
* Jason Stirnaman (helper), University of Kansas Medical Center, jstirnaman@kumc.edu &lt;br /&gt;
* Anyone else want to come and help folks? Contact Jason.&lt;br /&gt;
* Richard Aroksaar, National Park Service, richard_aroksaar@nps.gov&lt;br /&gt;
&lt;br /&gt;
RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language and the Rails framework. Participants will build a working Rails application. &lt;br /&gt;
&lt;br /&gt;
* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby&lt;br /&gt;
&lt;br /&gt;
There is some pre-preconference preparation needed so that we can effectively use our time.&lt;br /&gt;
&lt;br /&gt;
'''IMPORTANT''': From this point on if you sign up you '''must''' do the following in order to be prepared for the preconference workshop:&lt;br /&gt;
# Add your name below&lt;br /&gt;
# fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dEpxd0tzU1ZscnU5QUUtd0JGUk9qQkE6MA#gid=0 experience survey]&lt;br /&gt;
# read [https://docs.google.com/document/d/1lQEvljB6MWOdxqcibYsQDVMT2hCevk7Y5cm3143_eaU/edit the emails you have missed] &lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
# First and last name and email address&lt;br /&gt;
# John MacGillivray&lt;br /&gt;
# Christina Salazar - christina{dot}salazar{at}csuci{dot}edu&lt;br /&gt;
# Karen Coombs - coombsk{at}oclc{dot}org&lt;br /&gt;
# Becky Yoose - b dot yoose at google overlord&lt;br /&gt;
# Jeremy Morse - jgmorse at umich&lt;br /&gt;
# Julia Bauder - julia{dot}bauder{at}gmail{dot}com &lt;br /&gt;
# Chung Kang&lt;br /&gt;
# Karen Miller - k-miller3{at}northwestern{dot}edu&lt;br /&gt;
# Betsy Coles - bcoles{at}caltech{dot}edu&lt;br /&gt;
# Jay Luker - jay{dot}luker{at}gmail{dot}com&lt;br /&gt;
# Santi Thompson&lt;br /&gt;
# Sarah Dooley - sarah{at}nclive{dot}org&lt;br /&gt;
# Brandon Dudley&lt;br /&gt;
# Ken Irwin&lt;br /&gt;
# Dennis Ogg - ogg{at}ucar{dot}edu&lt;br /&gt;
# Ian Walls - iwalls{at}library{dot}umass{dot}edu&lt;br /&gt;
# Steven Villereal – villereal{at}gmail{dot}com&lt;br /&gt;
# Hillel Arnold - hillel{dot}arnold{at}gmail{dot}com&lt;br /&gt;
# Josh Wilson - joshwilsonnc at gmail&lt;br /&gt;
# Cynthia Ng - cynthia [dot] s [dot] ng [at] gmail&lt;br /&gt;
# Ian Chan&lt;br /&gt;
# Heidi Frank - hf36{at}nyu{dot}edu&lt;br /&gt;
# Mark Mounts - mark{dot}mounts{at}dartmouth{dot}edu&lt;br /&gt;
# Bill McMillin - wmcmilli{at}pratt {dot}edu&lt;br /&gt;
# David Lacy - david dot lacy at villanova dot edu&lt;br /&gt;
# Courtney Greene - crgreene at indiana dot edu&lt;br /&gt;
# Laney McGlohon - lmcglohon@getty.edu&lt;br /&gt;
# Nancy Enneking - nenneking@getty.edu&lt;br /&gt;
# Jason Raitz - jcraitz at ncsu dot edu&lt;br /&gt;
# Nick Cappadona&lt;br /&gt;
# Steven Marsden - steven.marsden@ryerson.ca&lt;br /&gt;
# Linda Ballinger - ballingerl at newberry dot org&lt;br /&gt;
# Brendan Quinn - brendan-quinn at northwestern dot edu&lt;br /&gt;
# Michael Levy - mlevy {at}ushmm {dot}org&lt;br /&gt;
# Michael North   (m-north at northwestern dot edu)&lt;br /&gt;
# Shawn Averkamp - shawnaverkamp{at}gmail{dot}com&lt;br /&gt;
# Allan Berry - allan{dot}berry{at}gmail{dot}com&lt;br /&gt;
# Cody Hennesy - chennesy at library dot berkeley dot edu&lt;br /&gt;
# Devin Higgins - higgi135 at msu dot edu&lt;br /&gt;
# Emily Zervas - emily{dot}zervas{at}gmail{dot}com&lt;br /&gt;
# Rob Dumas - rdumas {at} chipublib {dot} org&lt;br /&gt;
# Evan Boyd - eboyd /at/ ctschicago /period/ edu&lt;br /&gt;
# Lauren Ajamie - lauren dot ajamie at nd dot edu&lt;br /&gt;
# David Anderson - david dot anderson3 at nih dot gov&lt;br /&gt;
# David Bucknum - dabu at loc dot gov&lt;br /&gt;
# Dave Menninger - dave.menninger at gmail dot com&lt;br /&gt;
# Chris Day - cday2 at saic dot edu&lt;br /&gt;
# Corey Harper - corey dot harper at nyu dot edu&lt;br /&gt;
# Dileshni Jayasinghe - d dot jayasinghe at utoronto dot ca&lt;br /&gt;
# Harish Nayak - hnayak at library dot rochester dot edu&lt;br /&gt;
# David Cliff dgcliff@iu.edu&lt;br /&gt;
# Cody Hanson codyhanson@umn.edu&lt;br /&gt;
# Sean Purcell seanpurc{at}uga{dot}edu&lt;br /&gt;
# Laurie Lee Moses lmoses{at}colum{dot}edu&lt;br /&gt;
# Sibyl Schaefer sibylschaefer at gmail dot com&lt;br /&gt;
# Alisak Sanavongsay asanavongsay{at}ucmerced.edu&lt;br /&gt;
# Wayne Schneider wschneider at hclib dot org&lt;br /&gt;
# Carolyn Caizzi - carolyn{dot}caizzi {at}northwestern{dot}edu&lt;br /&gt;
# Julie Rudder - j-rudder at northwestern dot edu&lt;br /&gt;
# Matthew Butler - matthew-butler at uiowa dot edu&lt;br /&gt;
# Andromeda Yelton - andromeda.yelton at gmail&lt;br /&gt;
# Adam Strohm - adamstrohm at gmail dot com&lt;br /&gt;
# Kelly Thompson - thompson {dot} kelly {dot} j {at} gmail {dot} com&lt;br /&gt;
# Jane Sandberg - sandbrg2 {at} illinois {dot} edu&lt;br /&gt;
# Colin Koteles - koteles at cod dot edu&lt;br /&gt;
# George Campbell - campbelg{at}oclc{dot}org&lt;br /&gt;
# Sarah Thorngate - scthorngate{at}northpark{dot}edu&lt;br /&gt;
# Will Clarke - wfu.edu at clarkewd&lt;br /&gt;
# Terry Brady - twb27 at georgetown dot edu&lt;br /&gt;
# Patrick Feeley - pgf8 {at} case {dot} edu&lt;br /&gt;
# Bennett Magnino - bennett {dot} magnino {at} gmail {dot} com&lt;br /&gt;
# Christine McClure camcclure {at} gmail {dot} com&lt;br /&gt;
# Cole Hudson - Cole dot Hudson at wayne dot edu&lt;br /&gt;
'''IMPORTANT''': From this point on if you sign up you '''must''' do the following in order to be prepared for the preconference workshop:&lt;br /&gt;
# Add your name above&lt;br /&gt;
# fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dEpxd0tzU1ZscnU5QUUtd0JGUk9qQkE6MA#gid=0 experience survey]&lt;br /&gt;
# read [https://docs.google.com/document/d/1lQEvljB6MWOdxqcibYsQDVMT2hCevk7Y5cm3143_eaU/edit the emails you have missed]&lt;br /&gt;
&lt;br /&gt;
===Intro to NoSQL Databases===&lt;br /&gt;
====1-470 Richard J. Daley Library, 9:00 am to 12:00 pm on Monday, February 11====&lt;br /&gt;
* Joshua Gomez, George Washington University, jngomez at gwu edu&lt;br /&gt;
&lt;br /&gt;
Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called &amp;quot;Big Data&amp;quot; problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, MongoDB, and Neo4j.&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* Esha Datta&lt;br /&gt;
* Trevor Thornton&lt;br /&gt;
* Michael Doran&lt;br /&gt;
* Ray Schwartz - schwartzr2@wpunj.edu&lt;br /&gt;
* Kevin Clarke&lt;br /&gt;
* Andreas Orphanides&lt;br /&gt;
* Tommy Ingulfsen - tommying{at}caltech{dot}edu&lt;br /&gt;
* Harrison Dekker&lt;br /&gt;
* Eric James eric dot james at yale dot edu&lt;br /&gt;
* Sean Crowe - sean.crowe@uc.edu&lt;br /&gt;
* Scott Hanrath - shanrath@ku.edu&lt;br /&gt;
* Erin Fahy - erin.fahy at mtholyoke edu&lt;br /&gt;
* Karen Coyle - kcoyle at kcoyle.net&lt;br /&gt;
* Charles Draper&lt;br /&gt;
* David Uspal&lt;br /&gt;
* Shawn Kiewel - smkiewel at uga dot edu&lt;br /&gt;
* Stephanie Collett - stephanie dot collett at ucop dot edu&lt;br /&gt;
* Declan Fleming - declan at declan dot net&lt;br /&gt;
* David Gonzalez - d.gonzalez26 at umiami dot edu&lt;br /&gt;
* Jeff Peterson - gpeterso at umn dot edu&lt;br /&gt;
* May Chan - msuicat at gmail dot com&lt;br /&gt;
* Kathryn Stine - kathryn dot stine at ucop dot edu&lt;br /&gt;
* Tim Thompson - t.thompson5{at}miami{dot}edu&lt;br /&gt;
* Eben English - eenglish [at] bpl dot org&lt;br /&gt;
* Marisa Strong - marisa dot strong at ucop dot edu&lt;br /&gt;
* Michael Lindsey - mackeral at gmail dot com&lt;br /&gt;
* Mike Hagedon - hagedonm at u dot library dot arizona dot edu&lt;br /&gt;
* Scott Fisher - first/last name with dot in between at ucop dot edu&lt;br /&gt;
* James Griffin - griffinj at lafayette dot edu&lt;br /&gt;
* Jesse Brown - jfbrown78 at gmail dot com&lt;br /&gt;
* [[User:gdave|Dave Green]] david dot L dot green at dartmouth dot edu&lt;br /&gt;
* Michael Poltorak Nielsen mn at statsbiblioteket dot dk&lt;br /&gt;
* Mads Villadsen, mv@statsbiblioteket.dk&lt;br /&gt;
* Jørn Thøgersen, jt@statsbiblioteket.dk&lt;br /&gt;
* Julien Gibert, gibert at abes dot fr&lt;br /&gt;
* Lisa Gonzalez, lgonzalez@ctu.edu&lt;br /&gt;
* Charles Ledvina, charles@indexdata.com&lt;br /&gt;
* Jim LeFager, jlefager@depaul.edu&lt;br /&gt;
* Debbie Maron, dmaron@purdue.edu&lt;br /&gt;
* Carolina Garcia - cg116 nyu&lt;br /&gt;
* Tracy Seneca- tjseneca@uic.edu&lt;br /&gt;
* William Denton - wtd@pobox.com&lt;br /&gt;
* Andrew Darby - agdarby at miami dot edu&lt;br /&gt;
* Gary Maixner maixner2 at uiuc dot edu&lt;br /&gt;
* Jeremy Prevost&lt;br /&gt;
* Esther Verreau everreau skokielibrary info&lt;br /&gt;
* Matthew Short, mshort@niu.edu&lt;br /&gt;
* Kate Flynn, kef@uic.edu&lt;br /&gt;
* Jon Stroop - jstroop at princeton&lt;br /&gt;
* Mark Redar&lt;br /&gt;
* Robert Haschart - rh9ec at virginia dot edu&lt;br /&gt;
* Xiaoming Wang - xw5d at virginia dot edu&lt;br /&gt;
* Graham Hukill - graham dot hukill at wayne edu&lt;br /&gt;
* Susan Price&lt;br /&gt;
* Virginia Schilling - virginia dot schilling at ucr dot edu&lt;br /&gt;
* Bret Davidson&lt;br /&gt;
* Jason Thomale - jason dot thomale at unt dot edu&lt;br /&gt;
&lt;br /&gt;
==Half Day Afternoon==&lt;br /&gt;
=== Data Visualization Hackfest ===&lt;br /&gt;
====1-470 Richard J. Daley Library, 1:30 pm to 5:30 pm on Monday, February 11====&lt;br /&gt;
* Chris Beer, cabeer at stanford.edu&lt;br /&gt;
* Dan Chudnov, dchud at gwu edu&lt;br /&gt;
&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;
'''I plan on attending:'''&lt;br /&gt;
# Devon Smith&lt;br /&gt;
# Esha Datta&lt;br /&gt;
# Ray Schwartz - schwartzr2@wpunj.edu&lt;br /&gt;
# Karen Coombs - coombsk{at}oclc{dot}org&lt;br /&gt;
# Julia Bauder - julia{dot}bauder{at}gmail{dot}com&lt;br /&gt;
# Jason Stirnaman (jstirnaman at kumc.edu)&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Ayla Stein (astein at uh.edu)&lt;br /&gt;
# Harrison Dekker&lt;br /&gt;
# Ian Walls - iwalls{at}library{dot}umass{dot}edu&lt;br /&gt;
# Scott Hanrath - shanrath@ku.edu&lt;br /&gt;
# Annie Pho&lt;br /&gt;
# [[User:Kevenj|Keven Jeffery]]&lt;br /&gt;
# James Van Mil - james.vanmil at gmail com&lt;br /&gt;
# Sean Crowe - sean.crowe@uc.edu&lt;br /&gt;
# Karen coyle - kcoyle at kcoyle.net&lt;br /&gt;
# David Lacy - david dot lacy at villanova dot edu&lt;br /&gt;
# mark matienzo&lt;br /&gt;
# David Uspal&lt;br /&gt;
# Emily Lynema - ejlynema at ncsu dot edu&lt;br /&gt;
# Sean Chen&lt;br /&gt;
# Donald Mennerich&lt;br /&gt;
# Allan Berry - allan{dot}berry{at}gmail{dot}com&lt;br /&gt;
# Declan Fleming - declan at declan dot net&lt;br /&gt;
# Chick Markley -- chick at qrhino dot com&lt;br /&gt;
# Devin Higgins - higgi135 at msu dot edu&lt;br /&gt;
# Emily Zervas emily{dot}zervas{at}gmail{dot}com&lt;br /&gt;
# May Chan -- msuicat at gmail dot com&lt;br /&gt;
# Kathryn Stine - kathryn dot stine at ucop dot edu&lt;br /&gt;
# James Griffin - griffinj at lafayette dot edu&lt;br /&gt;
# Dave Menninger dave.menninger at gmail dot com&lt;br /&gt;
# [[User:gdave|Dave Green]] david dot L dot green at dartmouth dot edu&lt;br /&gt;
# Rikke Willer - riwi at dtic dot dtu dot dk&lt;br /&gt;
# Michael Poltorak NIelsen mn at statsbiblioteket dot dk&lt;br /&gt;
# Mads Villadsen, mv@statsbiblioteket.dk&lt;br /&gt;
# Jørn Thøgersen, jt@statsbiblioteket.dk&lt;br /&gt;
# Joe Atzberger, ohiocore@gmail.com&lt;br /&gt;
# Julien Gibert, gibert at abes dot fr&lt;br /&gt;
# Christie Peterson - cpeterson at jhu dot edu&lt;br /&gt;
# Jim LeFager - jlefager@depaul.edu&lt;br /&gt;
# Harish Nayak - hnayak at library dot rochester dot edu&lt;br /&gt;
# William Denton - wtd@pobox.com&lt;br /&gt;
# Shawn Carraway carraways at midlandstech dot edu&lt;br /&gt;
# Naomi Dushay - ndushay at stanford dot edu&lt;br /&gt;
# William Hicks - William{dot}hicks{at}unt{dot}edu&lt;br /&gt;
# Beatrice Pulliam bpulliam at providence edu&lt;br /&gt;
# Matthew Short, mshort@niu.edu&lt;br /&gt;
# George Campbell, campbelg{at}oclc{dot}org&lt;br /&gt;
# James Staub - james dot staub at nashville dot gov&lt;br /&gt;
# Will Clarke - wfu dot edu at clarkewd&lt;br /&gt;
&lt;br /&gt;
=== Intro to Hydra ===&lt;br /&gt;
====303 Library of the Health Sciences, 1:30 pm to 5:30 pm on Monday, February 11====&lt;br /&gt;
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)&lt;br /&gt;
* Justin Coyne, Data Curation Experts (justin.coyne at curationexperts.com)&lt;br /&gt;
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)&lt;br /&gt;
&lt;br /&gt;
Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content.  Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame. &lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* Jeremy Prevost&lt;br /&gt;
* Dennis Ogg - ogg{at}ucar{dot}edu&lt;br /&gt;
* Terry Brady&lt;br /&gt;
* Betsy Coles - bcoles{at}caltech{dot}edu&lt;br /&gt;
* Brendan Quinn - brendan-quinn at northwestern dot edu&lt;br /&gt;
* Shawn Kiewel - smkiewel at uga dot edu&lt;br /&gt;
* Steven Villereal – villereal{at}gmail{dot}com&lt;br /&gt;
* Ryan Eby&lt;br /&gt;
* Dean Farrell&lt;br /&gt;
* Ian Chan&lt;br /&gt;
* Mark Mounts - mark{dot}mounts{at}dartmouth{dot}edu&lt;br /&gt;
* Carl Jones&lt;br /&gt;
* Laney McGlohon - lmcglohon@getty.edu&lt;br /&gt;
* Nancy Enneking - nenneking@getty.edu&lt;br /&gt;
* Allan Berry - allan{dot}berry{at}gmail{dot}com&lt;br /&gt;
* Andrew Darby - agdarby at miami dot edu&lt;br /&gt;
* Kåre Fiedler Christiansen - kfc@statsbiblioteket.dk&lt;br /&gt;
* Corey Harper - corey dot harper at nyu dot edu&lt;br /&gt;
* Gary Maixner - maixner2 at uiuc dot edu&lt;br /&gt;
* Sibyl Schaefer - sibylschaefer at gmail dot com&lt;br /&gt;
* Emily F. Shaw - emily-f-shaw{at}uiowa{dot}edu&lt;br /&gt;
* Alicia Morris - alicia.morris@tufts.edu&lt;br /&gt;
* Tim Thompson - t.thompson5{at}miami{dot}edu&lt;br /&gt;
* Kate Flynn, kef@uic.edu&lt;br /&gt;
* Shawn Averkamp, shawn-averkamp{at}uiowa{dot}edu&lt;br /&gt;
&lt;br /&gt;
=== Intro to Blacklight ===&lt;br /&gt;
====1-1010 Richard J. Daley Library, 1:30 pm to 5:30 pm on Monday, February 11====&lt;br /&gt;
* Bess Sadler, Stanford University Library (bess at stanford.edu)&lt;br /&gt;
* Jason Ronallo, NC State (jronallo at gmail.com)&lt;br /&gt;
* Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)&lt;br /&gt;
&lt;br /&gt;
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&amp;amp;A around local issues people might encounter. &lt;br /&gt;
&lt;br /&gt;
Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* John MacGillivray&lt;br /&gt;
* Jon Stroop&lt;br /&gt;
* Jeremy Morse - jgmorse at umich&lt;br /&gt;
* Karen Miller - k-miller3{at}northwestern{dot}edu&lt;br /&gt;
* Tommy Ingulfsen - tommying{at}caltech{dot}edu&lt;br /&gt;
* Chung Kang&lt;br /&gt;
* Santi Thompson&lt;br /&gt;
* Brandon Dudley&lt;br /&gt;
* Ken Irwin&lt;br /&gt;
* Hillel Arnold&lt;br /&gt;
* Heidi Frank - hf36{at}nyu{dot}com&lt;br /&gt;
* Chris Sharp - csharp{at}georgialibraries{dot}org&lt;br /&gt;
* Bill McMillin - wmcmilli{at} pratt{dot} edu&lt;br /&gt;
* Jason Raitz - jcraitz at ncsu dot edu&lt;br /&gt;
* Linda Ballinger - ballingerl at newberry dot org&lt;br /&gt;
* Tim Thompson - t.thompson5{at}miami{dot}edu&lt;br /&gt;
* David Gonzalez - d.gonzalez26 at umiami dot edu&lt;br /&gt;
* Courtney Greene - crgreene at indiana dot edu&lt;br /&gt;
* Evan Boyd - eboyd /at/ ctschicago /period/ edu&lt;br /&gt;
* Lauren Ajamie - lauren dot ajamie at nd dot edu&lt;br /&gt;
* David Anderson - david dot anderson3 at nih dot gov&lt;br /&gt;
* Michael Lindsey - mackeral at gmail dot com&lt;br /&gt;
* David Bucknum - dabu at loc dot gov&lt;br /&gt;
* Chris Day - cday2 at saic dot edu&lt;br /&gt;
* Carolina Garcia - cg116 nyu&lt;br /&gt;
* David Cliff dgcliff@iu.edu&lt;br /&gt;
* Cody Hanson codyhanson@umn.edu&lt;br /&gt;
* Sean Purcell seanpurc{at}uga{dot}edu&lt;br /&gt;
* Laurie Lee Moses lmoses{at}colum{dot}edu&lt;br /&gt;
* Alisak Sanavongsay asanavongsay{at}ucmerced.edu&lt;br /&gt;
* Wayne Schneider wschneider at hclib dot org&lt;br /&gt;
* Carolyn Caizzi carolyn{dot}caizzi{at}northwestern{dot}edu&lt;br /&gt;
* Julie Rudder - j-rudder at northwestern dot edu&lt;br /&gt;
* Andromeda Yelton - andromeda.yelton at gmail&lt;br /&gt;
* Adam Strohm - adamstrohm at gmail dot com&lt;br /&gt;
* Luke Gaudreau - luke underscore gaudreau at harvard dot edu&lt;br /&gt;
* Cole Hudson - cole dot hudson at wayne dot edu&lt;br /&gt;
&lt;br /&gt;
=== DPLA Intro/Hacking ===&lt;br /&gt;
====Seminar Room A of Richard J. Daley Library, 1:30 pm to 5:30 pm on Monday, February 11==== &lt;br /&gt;
* Presenter(s)/Leader(s): Nate Hill (Chattanooga Public Library, DPLA Audience and Participation Co-chair), SJ Klein (Wikimedia, OLPC, DPLA Technical Aspects Co-chair), Jeff Licht (DPLA Technical Development Project Manager)&lt;br /&gt;
&lt;br /&gt;
The [http://dp.la Digital Public Library of America] (DPLA) is an open source metadata repository that provides read-only access to millions of records from across the United States via an open REST API. All API queries are returned as JSON-LD, a lightweight linked data format, and the metadata is freely reusable under a CC0 public domain license. A front-end portal is currently under development and will be launched in April 2013, though it will serve as but one way into the DPLA’s data. The DPLA encourages the development of applications and tools by developers of all skill levels and backgrounds.  In this workshop, participants will actively code against the API to make apps, visualization tools, plug-ins, and other interesting tools that make use of DPLA data. &lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* First and last name, Affiliation&lt;br /&gt;
* Justin Clark, Berkman Center for Internet and Society&lt;br /&gt;
* Anita Patel, Berkman Center for Internet and Society&lt;br /&gt;
* Peter Murray, LYRASIS&lt;br /&gt;
* Christine McClure, Illinois Institute of Technology&lt;br /&gt;
* Richard Aroksaar, National Park Service&lt;br /&gt;
&lt;br /&gt;
'''I plan on making:'''&lt;br /&gt;
* App name (your name): app description&lt;br /&gt;
&lt;br /&gt;
=== Fail4lib ===&lt;br /&gt;
====1-360 Richard J. Daley Library, 1:30 pm to 5:30 pm on Monday, February 11====&lt;br /&gt;
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)&lt;br /&gt;
* Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)&lt;br /&gt;
&lt;br /&gt;
The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans (&amp;quot;The Pivot&amp;quot;), and failing more cheaply.&lt;br /&gt;
&lt;br /&gt;
Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:&lt;br /&gt;
&lt;br /&gt;
# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.&lt;br /&gt;
# Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:&lt;br /&gt;
#* Technical failure&lt;br /&gt;
#* Failure to effectively address a real user need&lt;br /&gt;
#* Overinvestment&lt;br /&gt;
#* Outreach/Promotion failure&lt;br /&gt;
#* Design/UX failure&lt;br /&gt;
#* Project team communication failure&lt;br /&gt;
#* Missed opportunities (risk-averse failure)&lt;br /&gt;
#* Successes gleaned from failures&lt;br /&gt;
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.&lt;br /&gt;
# A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.&lt;br /&gt;
&lt;br /&gt;
I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* Becky Yoose&lt;br /&gt;
* Lisa Rabey&lt;br /&gt;
* Cynthia Ng (maybe) - cynthia [dot] s [dot] ng [at] gmail&lt;br /&gt;
* Patrick Berry, pberry@csuchico.edu&lt;br /&gt;
* Erin White, erwhite at vcu edu&lt;br /&gt;
* Ranti Junus, ranti.junus at gmail&lt;br /&gt;
* Rosalyn Metz -- rosalynmetz at gmail com&lt;br /&gt;
* Bret Davidson&lt;br /&gt;
&lt;br /&gt;
=== Solr 4 In Depth ===&lt;br /&gt;
====UIC Forum, 1:30 pm to 5:30 pm on Monday, February 11====&lt;br /&gt;
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)&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. Sounds like this is an evening thing that might happen at a bar somewhere?&lt;br /&gt;
&lt;br /&gt;
'''I plan on attending:'''&lt;br /&gt;
* First and last name&lt;br /&gt;
* Erin Fahy - erin.fahy at mtholyoke edu&lt;br /&gt;
* Esmé Cowles, escowles@ucsd.edu&lt;br /&gt;
* Jon Stroop&lt;br /&gt;
* Adam Constabars&lt;br /&gt;
* Kevin Clarke&lt;br /&gt;
* Jacob Andresen (jacob at reindex dot dk)&lt;br /&gt;
* Ted Lawless (tlawless at brown dot edu)&lt;br /&gt;
* Tom Burton-West&lt;br /&gt;
* Curtis Thacker&lt;br /&gt;
* Eric James eric dot james at yale dot edu&lt;br /&gt;
* Bess Sadler (bess at stanford dot edu)&lt;br /&gt;
* Michael North&lt;br /&gt;
* Charles Draper&lt;br /&gt;
* Nick Cappadona&lt;br /&gt;
* Stephanie Collett - stephanie dot collett at ucop dot edu&lt;br /&gt;
* Kalee Sprague - kalee dot sprague at yale dot edu&lt;br /&gt;
* Jeff Peterson - gpeterso at umn dot edu&lt;br /&gt;
* Erik Hetzner&lt;br /&gt;
* Demian Katz - demian dot katz at villanova dot edu&lt;br /&gt;
* Eben English - eenglish at bpl dot org&lt;br /&gt;
* Raman Chandrasekar &lt;br /&gt;
* Jason Ronallo - jnronall@ncsu.edu&lt;br /&gt;
* Eric Larson - elarson@library.wisc.edu&lt;br /&gt;
* Mike Hagedon - hagedonm at u dot library dot arizona dot edu&lt;br /&gt;
* Jesse Brown - jfbrown78 at gmail dot com&lt;br /&gt;
* Steven Marsden - steven.marsden@ryerson.ca&lt;br /&gt;
* Zeno Tajoli - tajoli at cilea it&lt;br /&gt;
* Charles Ledvina - charles att indexdata dott com&lt;br /&gt;
* Tracy Seneca - tjseneca@uic.edu&lt;br /&gt;
* Tod Olson - tod at uchicago dot edu&lt;br /&gt;
* Esther Verreau - everreau skokielibrary info&lt;br /&gt;
* Jane Sandberg - sandbrg2 at illinois dot edu&lt;br /&gt;
* Mark Redar&lt;br /&gt;
* Robert Haschart - rh9ec at virginia dot edu&lt;br /&gt;
* Xiaoming Wang - xw5d at virginia dot edu&lt;br /&gt;
* Graham Hukill - graham dot hukill at wayne edu&lt;br /&gt;
* Susan Price&lt;br /&gt;
* Cory Lown - cwlown at ncsu dot edu&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2013]]&lt;/div&gt;</summary>
		<author><name>Cwlown</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_social_activities&amp;diff=35798</id>
		<title>2013 social activities</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_social_activities&amp;diff=35798"/>
				<updated>2013-02-05T19:57:28Z</updated>
		
		<summary type="html">&lt;p&gt;Cwlown: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Ideas ==&lt;br /&gt;
&lt;br /&gt;
* Aviary: super-crazy cocktails. http://www.molecularrecipes.com/molecular-mixology/aviary-cocktails/ . List your name if you're interested, whether Sunday, Monday, and/or Tuesday (after newcomer dinners) work, and whether you're just interested in stopping by, or doing a 7 cocktail tasting flight.*&lt;br /&gt;
** statsfool: sunday/monday/tuesday, either drinks or flight.&lt;br /&gt;
** Amyhannah: monday/tuesday, drinks, probably not the flight.&lt;br /&gt;
** anarchivist: sunday/monday, prefer drinks over flight but could be convinced&lt;br /&gt;
** [[User:highermath|highermath]]: monday (could use 10 cocktails after Drupal subCon, I am sure). Uber now works in Chicago, so I would do the flight.&lt;br /&gt;
** [[User:pberry|pberry]]: any night but Wednesday (that's  Goose Island night) and I'd be up for drinks or flight, although leaning away from flight.&lt;br /&gt;
** [[User:thatandromeda|thatandromeda]] oh my gosh yes, any time, probably not the flight.&lt;br /&gt;
** [[User:Gdave|gdave]] beautiful site, I would be interested, Sun,Mon,Tues.  either drink or flight.&lt;br /&gt;
** scollett: sun, drinks, maybe flight.&lt;br /&gt;
** [[User:shawnc12|shawnc12]]: sunday/monday, either drink or flight&lt;br /&gt;
** beatricep: sunday/monday drink, highly susceptible to flight by peer pressure..&lt;br /&gt;
* Brewery tour - some possible candidates would be Goose Island, Brew Bus http://www.chicagobrewbus.com/, Piece, Revolution, Half Acre.&lt;br /&gt;
* Library field trips - because we're library geeks. Possible places include Newberry and Read/Write.--Read/Write Library confirmed for February 12.--Newberry Library confirmed for February 14.&lt;br /&gt;
* Art Institute of Chicago - Only open until 5pm, but possible for people coming in early enough on Sunday.&lt;br /&gt;
** escowles: I'm getting in around noon on Sunday, and interested in this.&lt;br /&gt;
** pgrayove: I'm getting in around noon on Sunday too.  I'm interested.&lt;br /&gt;
* Local Option http://localoptionbier.com/ - So you've heard of Hopleaf, you've heard of Maproom. Come to Chicago's *ahem* best kept secret for good food and an evening session on Monday. We will need a tally to make requisite arrangements.&lt;br /&gt;
** kayiwa&lt;br /&gt;
** Linda Ballinger&lt;br /&gt;
** Courtney Greene&lt;br /&gt;
** John Pillans&lt;br /&gt;
&lt;br /&gt;
== Planned Events ==&lt;br /&gt;
&lt;br /&gt;
=== Newcomer Dinner, Tuesday 2/12 ===&lt;br /&gt;
&lt;br /&gt;
First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating &amp;lt;strike&amp;gt;discussions about&amp;lt;/strike&amp;gt; demonstrations of the many uses of &amp;lt;strike&amp;gt;bacon&amp;lt;/strike&amp;gt; &amp;lt;strike&amp;gt;dongles&amp;lt;/strike&amp;gt; XML.&lt;br /&gt;
&lt;br /&gt;
Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!&lt;br /&gt;
&lt;br /&gt;
'''Plans'''&lt;br /&gt;
* When: Tuesday evening (2/12)&lt;br /&gt;
* Time: 6 PM (ish) or whenever you can get your group together&lt;br /&gt;
* Mastermind (if you have any questions): [mailto:yoosebec@grinnell.edu Becky Yoose]&lt;br /&gt;
&lt;br /&gt;
''Guidelines:''&lt;br /&gt;
*Max of '''6''' per group&lt;br /&gt;
**Please, no waitlisting&lt;br /&gt;
*ID yourselves so we can get a good mix of new people and veterans in each group&lt;br /&gt;
**New folks - n&lt;br /&gt;
**c4l vets - v&lt;br /&gt;
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group''')&lt;br /&gt;
**Leader duties&lt;br /&gt;
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library coders &lt;br /&gt;
***Herd folks from hotel to restaurant (know where you're going!)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Restaurants'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Restaurants within .25 miles of the hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://www.athenarestaurantchicago.com/index.php Athena] (Greek)&lt;br /&gt;
&lt;br /&gt;
* Al Cornish - v (leader)&lt;br /&gt;
* Carolyn Cole - n&lt;br /&gt;
&lt;br /&gt;
[http://www.dinerestaurant.com/ Dine] (Contemporary)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;del&amp;gt;[http://www.girlandthegoat.com/ Girl and the Goat] (American) Top Chef fans take note! This is Stephanie Izard's award-winning resto.&amp;lt;/del&amp;gt; Totally booked.&lt;br /&gt;
&lt;br /&gt;
[http://littlegoatchicago.com/ Little Goat] - Izard just opened a diner across the street from G&amp;amp;G that is walk-in only.&lt;br /&gt;
&lt;br /&gt;
[http://www.haymarketbrewing.com/ Haymarket Pub &amp;amp; Brewery] (Pub food)&lt;br /&gt;
&lt;br /&gt;
[http://www.karynsongreen.com/ Karyn’s on Green] (Vegan)&lt;br /&gt;
Completely vegan and close to the conference hotel. We'll meet in the conference hotel at around 6:45 (reservation at 7:00 for 6). Google maps says it is a 5 minute walk.&lt;br /&gt;
&lt;br /&gt;
*Jason Ronallo (leader)- v&lt;br /&gt;
*Alicia Cozine - n&lt;br /&gt;
*Mark Mounts - v&lt;br /&gt;
*Barbara Hui - n&lt;br /&gt;
*Amy Deschenes - n&lt;br /&gt;
*Adam Strohm - n&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://niarestaurant.com/nia-restaurant-mediterranean-cuisine/ Nia] (Mediterranean tapas)&lt;br /&gt;
&lt;br /&gt;
[http://www.pegasuschicago.com/index.php Pegasus] (Greek)&lt;br /&gt;
&lt;br /&gt;
[http://www.roditys.com/index.html Roditys] (Greek) -- Reservations made for 6:30pm.  Let's meet in the hotel lobby at 6pm and walk over from there.&lt;br /&gt;
&lt;br /&gt;
* Rosalyn Metz (leader) - v&lt;br /&gt;
* [[User:highermath|Cary Gordon]] - v&lt;br /&gt;
* [[User:Jacobandresen|Jacob Andresen]] - n&lt;br /&gt;
* Karen Miller - n&lt;br /&gt;
* Dre - v&lt;br /&gt;
* Mahria Lebow - n&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
'''Restaurants between .25 miles and .5 miles of the hotel'''&lt;br /&gt;
&lt;br /&gt;
Code4lib Chicago Celery Salt Society - [http://www.alsbeef.com/ Al's Beef]&lt;br /&gt;
&lt;br /&gt;
* Jason Casden (leader) - v - No reservations. We can walk from the hotel at 7.&lt;br /&gt;
* Charlie Morris - n&lt;br /&gt;
* Cory Lown - v&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
[http://avecrestaurant.com/# Avec] (Small plate)&lt;br /&gt;
Family-style small plate and tapas.  Great Yelp reviews.  We'll meet in the conference hotel at 6:00 &amp;lt;strike&amp;gt;6:45&amp;lt;/strike&amp;gt; (they don't take reservations, but have stuff to sip on if there's a wait).  Less than 10 minute walk from hotel.&lt;br /&gt;
&lt;br /&gt;
* Shaun Ellis (leader) - v&lt;br /&gt;
* Jon Stroop - v&lt;br /&gt;
* Paula Gray-Overtoom - n&lt;br /&gt;
* Emily Zervas - n&lt;br /&gt;
* Cynthia Ng - neither&lt;br /&gt;
* Sarah Dooley - n&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.babavillage.com/ Baba’s Village] (Indian/Pakistani)&lt;br /&gt;
&lt;br /&gt;
[http://blackbirdrestaurant.com/ Blackbird] (Contemporary)&lt;br /&gt;
&lt;br /&gt;
* Justin Coyne (reserver) - v - Reservation for Blackbird for 6 at 8:30pm&lt;br /&gt;
* Matt Cordial - v&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://www.carnivalechicago.com/menu Carnivale] (Nuevo Latino)&lt;br /&gt;
&lt;br /&gt;
[http://decero.hellotacos.com/ De Cero] (Mexican)&lt;br /&gt;
&lt;br /&gt;
[http://www.dragonflymandarin.com/  Dragonfly] (Chinese, sushi)&lt;br /&gt;
&lt;br /&gt;
[http://giordanos.com/ Giordano's] (Chicago Style Pizza) This place should be able to handle multiple groups...&lt;br /&gt;
&lt;br /&gt;
[http://www.grangehallburgerbar.com/ Grange Hall Burger Bar] (Local food)&lt;br /&gt;
&lt;br /&gt;
[http://www.idreamoffalafel.com/  I Dream of Falafel] (Mediterranean)&lt;br /&gt;
&lt;br /&gt;
* Emily Lynema (leader) - v&lt;br /&gt;
* Christie Peterson - n&lt;br /&gt;
&lt;br /&gt;
[http://www.jaipurchicago.com/ Jaipur] (Indian)&lt;br /&gt;
&lt;br /&gt;
* Andrew Darby (leader) - v&lt;br /&gt;
* Josh Wilson (joshwilsonnc at gmail) - n&lt;br /&gt;
* Tim Thompson - n&lt;br /&gt;
&lt;br /&gt;
[http://lasardine.com/ La Sardine] (French)&lt;br /&gt;
&lt;br /&gt;
[http://www.mythaitakumi.com/index.html MyThai Takumi] (Japanese Thai) Reservation at 6:15. Meet in the hotel lobby at 6 pm. Look for the women in a trench coat and hat.&lt;br /&gt;
&lt;br /&gt;
*Becky Yoose (leader) b dot yoose at gmail - v&lt;br /&gt;
*May Chan - n&lt;br /&gt;
*David Anderson - newby&lt;br /&gt;
*Terry Brady - new&lt;br /&gt;
* Dave Menninger - n&lt;br /&gt;
*Shawn Carraway -n&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.nellcoterestaurant.com/ Nellcôte] (French)&lt;br /&gt;
&lt;br /&gt;
[http://chicago.provincerestaurant.com/ Province] (American with Central/South American/Spanish influence)&lt;br /&gt;
&lt;br /&gt;
[http://thepublicanrestaurant.com/ The Publican] (Seafood)&lt;br /&gt;
&lt;br /&gt;
* Jay Luker (eater) - v - Rezzie is for 8pm&lt;br /&gt;
* Mark Matienzo (tweeter) - v&lt;br /&gt;
* Devon Smith (pickle eater) - repeat offender&lt;br /&gt;
* Chris Sharp (dead horse beater) - v&lt;br /&gt;
* Michael B. Klein (greeter) - v&lt;br /&gt;
* Bill McMillin (meeter) - n&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://saigonsisters.tumblr.com/ Saigon Sisters] (Vietnamese)&lt;br /&gt;
&lt;br /&gt;
[http://www.thaiurbankitchen.com/ Thai Urban Kitchen] (Thai, sushi)&lt;br /&gt;
&lt;br /&gt;
[http://www.trattoriaisabellachicago.com/rest.html Trattoria Isabella] (Italian)&lt;br /&gt;
&lt;br /&gt;
[http://www.vivo-chicago.com/homepage-2 Vivo] (Italian) &lt;br /&gt;
&lt;br /&gt;
[http://www.wishbonechicago.com/dining/westloop/ Wishbone] (Southern Reconstruction)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Restaurants between .5 miles and .75 miles of the hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://currentsontheriver.com/ Currents on the River] (Eclectic)&lt;br /&gt;
&lt;br /&gt;
[http://n9ne.com/ N9NE Steakhouse] (Steak)&lt;br /&gt;
&lt;br /&gt;
[http://www.verachicago.com/menu Vera Chicago] (Spanish)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Restaurants between .75 miles and 1 mile of the hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://www.theberghoff.com/default.aspx The Berghoff] (German)&lt;br /&gt;
* Declan Fleming - v (leader)  I checked reservations, and for 6 people, the first time open after the conf is 7:30, so I grabbed that.&lt;br /&gt;
* Dave Green - n &lt;br /&gt;
* Steven Villereal - n&lt;br /&gt;
* Peter Murray - v&lt;br /&gt;
* Trey Terrell - n&lt;br /&gt;
* Mike Giarlo - v&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.yelp.com/biz/frontera-grill-chicago Frontera] (a Rick Bayliss Mex-American restaurant) Reservations are for 7:30, so perhaps the group could get a drink in the lobby beforehand.  Either way, we'll depart at 7pm.&lt;br /&gt;
: (''note: the drinks at the bar at frontera are very tasty.'')&lt;br /&gt;
*Dan Suchy (leader and over-eater) - v&lt;br /&gt;
*Matt Critchlow - v&lt;br /&gt;
*Carmen Mitchell - v&lt;br /&gt;
*Maureen Callahan - n&lt;br /&gt;
*David Cliff - n&lt;br /&gt;
* Patrick Berry - 3rd year red-shirt freshman&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.nativefoods.com/ Native Foods] (Vegan)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Restaurants more than 1 mile from the hotel'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://www.greenzebrachicago.com/index.html Green Zebra] (Vegan)&lt;br /&gt;
&lt;br /&gt;
[http://honkytonkbbqchicago.com/ Honky Tonk Barbeque] (BBQ)&lt;br /&gt;
&lt;br /&gt;
[http://www.karynraw.com/cooked Karyn’s Cooked] (Vegan)&lt;br /&gt;
&lt;br /&gt;
[http://www.latabernatapas.com/ La Taberna Tapas] (Mediterranean)&lt;br /&gt;
&lt;br /&gt;
[http://www.morganschicago.com/ Morgan's on Maxwell] (Pub food)&lt;br /&gt;
&lt;br /&gt;
[http://www.chezjoelbistro.com/ Chez Joël] (French/Tangiers food) I am leaning towards an early dinner of 6:15 as I have to take-off to make sure the Game Night takes off without a hitch. So leave the conference hotel by 5:45 if it is walk weather or 6PM if it is taxi weather.&lt;br /&gt;
&lt;br /&gt;
* Francis Kayiwa (knackered leader) - v&lt;br /&gt;
* Megan O'Neill Kudzia - n&lt;br /&gt;
* Esther Verreau - n&lt;br /&gt;
&lt;br /&gt;
=== Veg*n Dinner ===&lt;br /&gt;
&lt;br /&gt;
Let's have dinner at a veg*n-friendly place one night of the conference. Folks of all eating styles welcome.&lt;br /&gt;
&lt;br /&gt;
Max *6* people per party this year.&lt;br /&gt;
&lt;br /&gt;
'''Party #1: Chicago Diner''', Wednesday Night http://www.veggiediner.com/ &amp;quot;meat free since '83&amp;quot; &lt;br /&gt;
Will they easily be able to accommodate 6 folks walking in?&lt;br /&gt;
We'll plan on meeting in the conference hotel at 6pm and taking the 8 bus up there (3411 N. Halsted St  Chicago, IL 60657). &lt;br /&gt;
# Jason Ronallo (jronallo@gmail.com)&lt;br /&gt;
# Linda Ballinger (linda dot ballinger at gmail)&lt;br /&gt;
# May Chan (msuicat at gmail dot com)&lt;br /&gt;
# Demian Katz (demian DOT katz AT villanova DOT edu)&lt;br /&gt;
# David Uspal (david dot uspal at villanova dot edu) In for the Country Fried StAEk and/or the Soul Bowl.  Ex-Vegetarian (which may make it a crime for me to go), so if the list is full and you still want in, feel free to email me and I'll gladly turn over my spot to an actual Veg*n.&lt;br /&gt;
# Cynthia Ng (cynthia dot s dot ng at gmail)&lt;br /&gt;
Capped at 6&lt;br /&gt;
&lt;br /&gt;
=== Code4lib/Goose Island Brewing Pull Request ===&lt;br /&gt;
'''When:''' Wednesday, 2/13, 8:00 PM to 11:00 PM&lt;br /&gt;
&lt;br /&gt;
More information and sign up at [https://code4lib2013-estw.eventbrite.com/|https://code4lib2013-estw.eventbrite.com/]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Non-beery get together ===&lt;br /&gt;
'''When:''' Wednesday, 2/13, Meet at hotel lobby at around 6:30 (and take public transport over to the park) OR meet us at the rink at 6:45, skating rink closes at 8 PM&lt;br /&gt;
&lt;br /&gt;
'''Where:''' [https://www.cityofchicago.org/city/en/depts/dca/supp_info/ice_skating_at_themccormicktribuneicerink.html McCormick Tribune Ice Rink]&lt;br /&gt;
&lt;br /&gt;
'''Contact:''' @dchud, @ranti, @yo_bj (b dot yoose at gmail), @wendyrlibrarian&lt;br /&gt;
&lt;br /&gt;
'''Cost:''' $10 skate rental, people watching free&lt;br /&gt;
&lt;br /&gt;
Come and (attempt to) skate with us! This is also a good people watching opportunity, so if you don't want to skate, there will be places to hang out around the rink and the park. There is a [http://www.parkgrillchicago.com/cafe/food-menu cafe] near the rink as well, with hot drinks and food.&lt;br /&gt;
&lt;br /&gt;
FYI - For those of you who want something else to munch on while hanging out, there's a [http://www.garrettpopcorn.com/chicago-locations/4-east-madison-street/ Garrett Popcorn Shop] a couple blocks away.&lt;br /&gt;
&lt;br /&gt;
# Chris Sharp (indicating interest)&lt;br /&gt;
# Becky Yoose (ready to fall on her butt repeatedly for the entertainment of others)&lt;br /&gt;
# Peter Murray&lt;br /&gt;
# Shawn Carraway&lt;br /&gt;
# Karen Coombs&lt;br /&gt;
# Michael Levy&lt;br /&gt;
# Christie Peterson&lt;br /&gt;
&lt;br /&gt;
=== Flying Trapeze ===&lt;br /&gt;
'''When:''' Monday, 2/11, TBD&lt;br /&gt;
&lt;br /&gt;
'''Contact:''' rosalynmetz at gmail dot com&lt;br /&gt;
&lt;br /&gt;
No this is not a joke. If you haven't heard Rosy is an aspiring trapeze artists and wants to bring the fun to her friends in Code4Lib.  There is a trapeze rig in Chicago and she plans on visiting it and hopes that some of you can come along as well.  If its your first time taking a trapeze class, they'll start you off learning [http://www.youtube.com/watch?v=_oqPi_zuX7A a knee hang] and depending on how that goes you might be able to catch it at the end of class.  If you have any questions about whether or not this is for you, [http://chicago.trapezeschool.com/classes/trapeze.php TSNY Chicago's website] should have the answer, if not feel free to contact Rosy.&lt;br /&gt;
&lt;br /&gt;
Trapeze classes are $57, last 2 hours, and are limited to 10 people.  Currently TSNY Chicago hasn't release their class schedule for February -- they should be doing that around Jan. 1.  If we can get enough people interested before then, we can buy out a whole class.  If not it'll be first come, first serve (along with the general public).&lt;br /&gt;
&lt;br /&gt;
If you're interested in signing up, feel free to add your name and contact info to the list below.&lt;br /&gt;
&lt;br /&gt;
'''''Sign Up List'''''&lt;br /&gt;
# Jay Luker (first!)&lt;br /&gt;
# Bill McMillin&lt;br /&gt;
# Bess Sadler&lt;br /&gt;
# Karen Coyle&lt;br /&gt;
# Sibyl Schaefer&lt;br /&gt;
# Rosalyn Metz (because I'm organizing)&lt;br /&gt;
# Alicia Cozine&lt;br /&gt;
# &lt;br /&gt;
# &lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Game Night! ===&lt;br /&gt;
&lt;br /&gt;
Moved this from idea to an actual event.  Still getting some details, but here's what we know:&lt;br /&gt;
&lt;br /&gt;
We have a conference room at the UIC library reserved for 7:30 on Tuesday the 11th.  Not sure how late we'll play.  I'll bring some board games and pick up some cards. List below were people who were interested in games and what games they are bringing.&lt;br /&gt;
&lt;br /&gt;
(Note, there's also some discussion on Cards Against Humanity.  I will try to make sure there's an alternative game, but I don't know if I want to prohibit any games. I would say though to remember to be respectful and curteous to those around you. I will probably be pondering this issue for a while)&lt;br /&gt;
&lt;br /&gt;
This will get updated more as I have time to spend on it.&lt;br /&gt;
&lt;br /&gt;
 Game Night!  Type of games might vary due to interest, could range from party games like Werewolf, Wits &amp;amp; Wagers, Telestrations, Taboo, Apples to Apples to perhaps more strategic games like De Vulgari Eloquentia or Eclipse.  Jon Gorman is willing to bring some games, are you? Jon will try to send out an email soon to get some interest.&lt;br /&gt;
** yo_bj: I have some games I can bring as well (Kill Doctor Lucky, Fluxx, Godzilla: Stomp, Munchkin Zombies, etc.). Monday doesn't have anything major planned...&lt;br /&gt;
**danwho:  I 'll bring the Cards Against Humanity set.&lt;br /&gt;
**escowles (Mon/Tue preferred): I've got lots of games I could bring like Settlers of Catan, Carcassonne, Ticket to Ride, Age of Renaissance, Elfenland, Agricola, Le Havre, Smallworld, RoboRally, etc. etc.&lt;br /&gt;
**jen_young: I'm local and I have quite a few games. Just about every version of Fluxx, Bananagrams, Gloom, Munchkin Cthulu,Cards Against Humanity, Apples to Apples, Risk, Last Night on Earth, etc.)&lt;br /&gt;
** decasm: Interested in Go (aka igo, weiqi, baduk) anytime, not just game night. I can do Catan as well. (And as much as I love it, Cards Against Humanity is probably a violation of the new Code of Conduct.)&lt;br /&gt;
** csharp: I'm interested in playing games - whatever people bring.  I almost always travel with a pack or two of playing cards ;-).  Monday or Tuesday nights are fine.&lt;br /&gt;
** moneill: I would love to join in! I have a version of Catchphrase floating around somewhere, and I think I have Battleship...I need to go weed around in that drawer and see what else presents itself. Tuesday would be my preferred night, but I will make it work!&lt;br /&gt;
** demiankatz: I'm always up for a game.  I'm hoping to travel light so probably shouldn't bring anything, but if there's a local game shop, I might be persuaded to pick up something new as a souvenir.&lt;br /&gt;
** sekjal: I've got [http://boardgamegeek.com/boardgame/36218/dominion Dominion], [http://boardgamegeek.com/boardgame/68448/7-wonders 7 Wonders], [http://boardgamegeek.com/boardgame/30933/bang-the-bullet Bang!], [http://boardgamegeek.com/boardgame/18333/ecofluxx EcoFluxx] and [http://boardgamegeek.com/boardgame/116/guillotine Guillotine] that I can bring.  ++ on Cards against Humanity!  Prefer non-conflict with beer night.&lt;br /&gt;
** arty: so totally interested. Unfortunately, I have no games to contribute.&lt;br /&gt;
** sanderson: I would be interested. I can bring [http://boardgamegeek.com/boardgame/478/citadels Citadels] (2-7 players)&lt;br /&gt;
** dvdndrsn: Definitely in! Can bring Innovation, Tichu, Dominion, but Cards Against Humanity sounds good. &lt;br /&gt;
** smkiewel: I'm likely to join. Can bring Arkham Horror and Munchkin.&lt;br /&gt;
** jkwilson: I'd like to attend Monday or Tuesday. I have a bunch of games but I'd prefer not to travel with them, and anyway it sounds like they're covered above. I'll bring the 5-6 player Catan extension.&lt;br /&gt;
** ejlynema: Interested, but will probably attend Newcomer dinner on Tuesday. Like Dominion and 7 Wonders, but probably don't have room to bring in suitcase. Anyone bringing Tsuro?&lt;br /&gt;
** Christie Peterson (save4use): Also interested, but also probably attending newcomer dinner on Tuesday. Can bring [http://boardgamegeek.com/boardgame/11/bohnanza Bohnanza] and one deck of [http://en.wikipedia.org/wiki/Set_%28game%29 Set]. &lt;br /&gt;
** dgcliff: I'd be interested. Can bring Ticket to Ride.&lt;br /&gt;
** mbklein: definitely interested. Will check on my (currently unpacked) games. I am dying to play Cards Against Humanity. If we can't find a way to reconcile it with the Code of Conduct, we need a different Code of Conduct.&lt;br /&gt;
*** Considering that this is a public event, and that no one knows everyone's sensitivity levels in the room, it might not be a good idea to break out a crass, adult version of apples to apples in the middle of the gaming room. :cP (yo_bj)&lt;br /&gt;
** duspal:  In.  My board game collection is small but mighty (Arkham Horror, Catan, Vampire: Prince of the City, Deadlands: Battle for Slaughter Gulch, Arabian Nights, Diplomacy, Shogun, and Cosmic Encounter off the top of my head, amongst a few others).  Let me know ahead of time if anyone is interested, since they're all relatively big...&lt;br /&gt;
**librarywebchic: I'm willing to bring a set and teach folks how to play Majhong. Need at least three to play though.&lt;br /&gt;
**beatricep:  Uno gets no respect. ;-)  @librarywebchic: I have always wanted to learn to play Majhong.  If you're still bringing it, I'm in!&lt;br /&gt;
** jcraitz: I'm in after the newcomer dinner.  I'll bring Citadels and Bang!&lt;br /&gt;
&lt;br /&gt;
== Social Map - Places of Interest==&lt;br /&gt;
&lt;br /&gt;
https://maps.google.com/maps/ms?msid=213549257652679418473.0004ce6c25e6cdeb0319d&amp;amp;msa=0&lt;br /&gt;
&lt;br /&gt;
== Local Events ==&lt;br /&gt;
Events Listings&lt;br /&gt;
* Chicago Reader http://www.chicagoreader.com/&lt;br /&gt;
* The City of Chicago’s Events Guide: http://www.choosechicago.com/ &lt;br /&gt;
* Metromix Chicago: http://chicago.metromix.com/events &lt;br /&gt;
* Timeout Chicago: http://timeoutchicago.com/&lt;br /&gt;
&lt;br /&gt;
== Local Food ==&lt;br /&gt;
== Local Drinks ==&lt;br /&gt;
==Chicago Events Feb 11-14==&lt;br /&gt;
===Monday February 11===&lt;br /&gt;
&lt;br /&gt;
Music - [http://www.hideoutchicago.com/event/208497-robbie-fulks-michael-miles-chicago/ Robbie Fulks at the Hideout]&lt;br /&gt;
&lt;br /&gt;
[http://fedora4lib.org/ fedora4lib] - 7 pm to whenever&lt;br /&gt;
&lt;br /&gt;
===Tuesday, February 12===&lt;br /&gt;
Field trip to the Read/Write Library (details to follow). 6-9 PM+&lt;br /&gt;
Come help catalog the Read/Write Library catalog and hack on the library catalog. We will also invite friends from Code for America to hang out and talk civic data.&lt;br /&gt;
&lt;br /&gt;
Concert - [http://www.thefatbabies.com/ The Fat Babies] playing at an awesome venue, [http://greenmilljazz.com/ The Green Mill].&lt;br /&gt;
&lt;br /&gt;
[http://fedora4lib.org/ fedora4lib] - 7 pm to whenever&lt;br /&gt;
&lt;br /&gt;
===Wednesday, February 13===&lt;br /&gt;
===Thursday, February 14===&lt;br /&gt;
Tour of the [http://www.newberry.org/ Newberry Library] -- 3:30 p.m.&lt;br /&gt;
This will be a special tour for Code4Lib attendees, so please sign up below if you are interested, as I'll need to give the tour guide an estimate of how many people will come. Details on how to get to the Newberry will follow. Questions? Contact ballingerl at newberry dot org&lt;br /&gt;
&lt;br /&gt;
'''''Sign Up List'''''&lt;br /&gt;
# Michael Doran - doran@uta.edu&lt;br /&gt;
# William Denton - wtd@pobox.com&lt;br /&gt;
# Wayne Schneider - wschneider@hclib.org&lt;br /&gt;
# Matt Cordial - rev3lator [at] gmail.com&lt;br /&gt;
# [name] - [email address]&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2013]]&lt;/div&gt;</summary>
		<author><name>Cwlown</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_twitter_list&amp;diff=11184</id>
		<title>2012 twitter list</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_twitter_list&amp;diff=11184"/>
				<updated>2012-02-07T19:43:05Z</updated>
		
		<summary type="html">&lt;p&gt;Cwlown: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Put your twitter handle in here, if you're at Code4Lib 2012 Seattle.  I'll add you to the [https://twitter.com/#!/code4lib/attendees-2012 Attendees 2012 twitter list] for @code4lib when I get a chance. Thanks! -Sean&lt;br /&gt;
&lt;br /&gt;
# Sean Hannan (@MrDys)&lt;br /&gt;
# Cynthia Ng (@TheRealArty)&lt;br /&gt;
# Becky Yoose (@yo_bj)&lt;br /&gt;
# Jason Ronallo (@ronallo)&lt;br /&gt;
# Kåre Fiedler Christiansen (@kaarefc)&lt;br /&gt;
# Joe Montibello (@firstweet)&lt;br /&gt;
# Charlie Morris (@cdmo)&lt;br /&gt;
# Laura Smart (@infod1va)&lt;br /&gt;
# Keri Thompson (@DigiKeri_SIL)&lt;br /&gt;
# Misty De Meo (@mistydemeo)&lt;br /&gt;
# Robert H. McDonald (@mcdonald) - attending virtually&lt;br /&gt;
# Takanori Hayashi (@tzhaya)&lt;br /&gt;
# Jason Casden (@cazzerson)&lt;br /&gt;
# Corey Harper (@chrpr)&lt;br /&gt;
# Heather Pitts (@HLPitts)&lt;br /&gt;
# Alex Wade (@alexwade)&lt;br /&gt;
# Zoe Chao (@zoechao)&lt;br /&gt;
# Joel Richard (@cajunjoel)&lt;br /&gt;
# Mark Matienzo (@anarchivist)&lt;br /&gt;
# Tim Lepczyk (@singlesoliloquy)&lt;br /&gt;
# Scott Hanrath (@rshanrath)&lt;br /&gt;
# Mads Villadsen (@maxxkrakoa)&lt;br /&gt;
# Hillel Arnold (@helrond)&lt;br /&gt;
# Sam Kome (@skome)&lt;br /&gt;
# Ryan Wick (@ryanwick)&lt;br /&gt;
# Ken Varnum (@varnum)&lt;br /&gt;
# Al Cornish (@alncornish)&lt;br /&gt;
# Kate Zwaard (@kzwa)&lt;br /&gt;
# Sibyl Schaefer (@sibylschaefer)&lt;br /&gt;
# Jason Clark (@jaclark)&lt;br /&gt;
# Derek Merleaux (@dmer)&lt;br /&gt;
# Jay Dela Cruz (@delacruzjay)&lt;br /&gt;
# Jen Weintraub (@spiralstars)&lt;br /&gt;
# Ed Summers (@edsu)&lt;br /&gt;
# Luis Baquera (@mexkn)&lt;br /&gt;
# Makoto Okamoto (@arg)&lt;br /&gt;
# Peter Murray (@datag)&lt;br /&gt;
# Peter Binkley (@pabinkley) - virtual&lt;br /&gt;
#Carmen Mitchell (@carmendarlene)&lt;br /&gt;
# Kosuke Tanabe (@nabeta)&lt;br /&gt;
# Shirley Lew (@shlew)&lt;br /&gt;
# Mike Giarlo (@mjgiarlo)&lt;br /&gt;
# Ben Shum (@bshum)&lt;br /&gt;
# Tara Robertson (@tararobertson)&lt;br /&gt;
# Margaret Heller (@margaret_heller)&lt;br /&gt;
# Jennifer Bowen (@jbbowen)&lt;br /&gt;
# Masao Takaku (@tmasao)&lt;br /&gt;
# Sam Meister (@samalanmeister)&lt;br /&gt;
# Ranti Junus (@ranti) - virtual&lt;br /&gt;
# Rachel Frick (@rlfrick)&lt;br /&gt;
# Bethany Nowviskie (@nowviskie)&lt;br /&gt;
# Cory Lown (@cowilo)&lt;br /&gt;
#&lt;br /&gt;
#&lt;/div&gt;</summary>
		<author><name>Cwlown</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_c4l2012_social_activities&amp;diff=10845</id>
		<title>2012 c4l2012 social activities</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_c4l2012_social_activities&amp;diff=10845"/>
				<updated>2012-02-04T13:53:24Z</updated>
		
		<summary type="html">&lt;p&gt;Cwlown: /* Newcomer dinner Tuesday */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Ideas==&lt;br /&gt;
* Woodinville distillery tour&lt;br /&gt;
* Seattle distillery tour&lt;br /&gt;
* Favorite local breweries&lt;br /&gt;
* Favorite local tea houses&lt;br /&gt;
* Favorite local used bookstores&lt;br /&gt;
* Visit hackerspace&lt;br /&gt;
** +1&lt;br /&gt;
* Evergreen/Koha - Open Source ILS brewery/tea house meetup&lt;br /&gt;
&lt;br /&gt;
==Planned events==&lt;br /&gt;
&lt;br /&gt;
===Pre-Newcomer + Veterans dinner /drink-up Monday===&lt;br /&gt;
Early in town for pre-conference? &lt;br /&gt;
First time at code4lib? &lt;br /&gt;
Don't know anyone at code4lib?&lt;br /&gt;
Join fellow c4l newbies + 2nd + 3rd timers + veterans. &lt;br /&gt;
You will gain a bunch of new/veteran code4libbers in one night!&lt;br /&gt;
Sign up below (NO CAP). You can show up only for dinner or drinks or both! &lt;br /&gt;
&lt;br /&gt;
But put your name so that we have a rough idea about the number of ppl who will show up =)&lt;br /&gt;
&lt;br /&gt;
'''Plans'''&lt;br /&gt;
* When: Monday evening (2/6) &lt;br /&gt;
* For Dinner: Meet at 6PM (ish)at the hotel lobby&lt;br /&gt;
* For Drinks: show up at Hideout between 8 -10 PM for local art, fancy cocktails, or Belgian beer&lt;br /&gt;
* For Hangout: show up at 10 PM - midnight? at hospitality suite&lt;br /&gt;
&lt;br /&gt;
Dinner: [http://www.yelp.com/biz/kastoori-grill-seattle Kastoori Grill -Indian &amp;amp; Himalayan/Nepalese/Tibetan (vegetarian-friendly)]&lt;br /&gt;
0.8 miles 15 min. walk&lt;br /&gt;
* Bohyun Kim - n/v (2nd-timer) (leader)&lt;br /&gt;
* Jason Clark - leader&lt;br /&gt;
* Margaret Heller&lt;br /&gt;
* Sarah Johnston - n&lt;br /&gt;
* Andrea Schurr - n/v (2nd-timer)&lt;br /&gt;
* Jason Ronallo&lt;br /&gt;
* Karen Coombs - v&lt;br /&gt;
* Eric James&lt;br /&gt;
* Misty De Meo - n&lt;br /&gt;
* Keri Thompson - n&lt;br /&gt;
&lt;br /&gt;
Drinks: [http://www.yelp.com/biz/the-hideout-seattle Hideout Lounge] for local art, fancy cocktails, and Belgian beer&lt;br /&gt;
0.3 miles 8 min. walk&lt;br /&gt;
* Bohyun Kim - n/v (2nd-timer) (leader)&lt;br /&gt;
* Jason Clark - leader&lt;br /&gt;
* Lisa Kurt - n&lt;br /&gt;
* Margaret Heller&lt;br /&gt;
* Andrea Schurr - n/v (2nd-timer)&lt;br /&gt;
* Anoop Atre (Would love to if back from MS visit)&lt;br /&gt;
* Heather Pitts (maybe) - n&lt;br /&gt;
* Evviva Weinraub - Hope to join up if back from MS visit)&lt;br /&gt;
* Megan Banasek -n&lt;br /&gt;
* Misty De Meo (maybe) - n&lt;br /&gt;
* Keri Thompson (definitely)&lt;br /&gt;
* David Drexler (likely) - n&lt;br /&gt;
&lt;br /&gt;
Hangout: just show up at the hospitality suite - no sign up required.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Morning Run Tuesday===&lt;br /&gt;
I (Ray Schwartz) am organizing a morning run for anyone that would like to join me.  It will be around 5 to 6 miles.  I usually run a 10 minute per mile pace. And I would like to start around 7am.  Select which days Tuesday or Wednesday or both mornings.  Choose the date you wish via this Doodle link http://www.doodle.com/3tbigutqvkda5ib8&lt;br /&gt;
&lt;br /&gt;
I will map out a course when I arrive and will post it on the wiki.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Newcomer dinner Tuesday===&lt;br /&gt;
First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating &amp;lt;strike&amp;gt;discussions about&amp;lt;/strike&amp;gt; demonstrations of the many uses of &amp;lt;strike&amp;gt;bacon&amp;lt;/strike&amp;gt; &amp;lt;strike&amp;gt;dongles&amp;lt;/strike&amp;gt; XML.&lt;br /&gt;
&lt;br /&gt;
Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!&lt;br /&gt;
&lt;br /&gt;
'''Plans'''&lt;br /&gt;
* When: Tuesday evening (2/7) '''Note that this year's dinner is on Tuesday'''&lt;br /&gt;
* Time: 6 PM (ish) or whenever you can get your group together&lt;br /&gt;
* Mastermind (if you have any questions): [mailto:yoosebec@grinnell.edu Becky Yoose]&lt;br /&gt;
&lt;br /&gt;
''Guidelines:''&lt;br /&gt;
*Max of '''6''' per group&lt;br /&gt;
**Please, no waitlisting :(&lt;br /&gt;
*ID yourselves so we can get a good mix of new people and veterans in each group&lt;br /&gt;
**New folks - n&lt;br /&gt;
**c4l vets - v&lt;br /&gt;
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group :)''')&lt;br /&gt;
**Leader duties&lt;br /&gt;
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library coders &lt;br /&gt;
***Herd folks from hotel to restaurant (know where you're going!)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Restaurants'''&lt;br /&gt;
&lt;br /&gt;
'''Restaurants within .25 miles of the hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://www.sazeracrestaurant.com/index.php Sazerac] (AWESOME happy hour menu that runs until 8)&lt;br /&gt;
* Martin Haye - n&lt;br /&gt;
* William Gunn - n&lt;br /&gt;
* Rebecca Jones - n&lt;br /&gt;
* Chick Markley - v&lt;br /&gt;
* Al Cornish - v&lt;br /&gt;
* Keri Thompson - n&lt;br /&gt;
*'''capped at 6''' ''(So, who's the fearless leader of this group? ~yo_bj)''&lt;br /&gt;
&lt;br /&gt;
[http://oasiankitchen.com/ O'Asian Kitchen and Lounge]  (Asian) &lt;br /&gt;
&lt;br /&gt;
'''Restaurants between .25 miles and .5 miles of the hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://www.pikebrewing.com/index_html.shtml Pike Brewing] (local brewery, pub food)&lt;br /&gt;
* Ken Varnum - n&lt;br /&gt;
* Chad Nelson - n&lt;br /&gt;
* Ed Summers - v&lt;br /&gt;
* Tommy Ingulfsen - n&lt;br /&gt;
* Adam Wead - v or .5n&lt;br /&gt;
* Dan Coughlin - n&lt;br /&gt;
*'''capped at 6''' ''(So, who's the fearless leader of this group? ~yo_bj)''&lt;br /&gt;
&lt;br /&gt;
[http://www.rockbottom.com/ The Rock Bottom Restaurant &amp;amp; Brewery] (American)&lt;br /&gt;
&lt;br /&gt;
[http://www.wildginger.net/ Wild Ginger] (Asian, a bit overpriced)&lt;br /&gt;
* Tamar Sadeh - n&lt;br /&gt;
* Kevin Clarke - v&lt;br /&gt;
&lt;br /&gt;
[http://www.thepurplecafe.com/index.html Purple Cafe] (American, Wine Bar) ''reservation made under Calvin Mah for 6:30pm for the 6 of us.  I'll be meeting in the hotel lobby at 6pm with some sort of sign.  See you then!''&lt;br /&gt;
* Calvin Mah - (leader) - v&lt;br /&gt;
* David Isaak - n&lt;br /&gt;
* Aaron Collier - n&lt;br /&gt;
* Sean Hannan - v&lt;br /&gt;
* Joshua Gomez - v&lt;br /&gt;
* Charlie Morris - n&lt;br /&gt;
* '''capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.cafepaloma.com/ Cafe Paloma] (Mediterranean)&lt;br /&gt;
* Jean Rainwater (leader) - v&lt;br /&gt;
* Kelley McGrath - n&lt;br /&gt;
* Lori Robare - n&lt;br /&gt;
* Emily Lynema - v&lt;br /&gt;
* Sarah Johnston - n&lt;br /&gt;
&lt;br /&gt;
[http://www.thecollinspub.com/ Collins Pub] (Pub Food, great beer selection)&lt;br /&gt;
* Francis Kayiwa - (leader) &amp;quot;(get hold of me at first dot last name at goog as the date gets closer with your mobile)&amp;quot; v&lt;br /&gt;
* Michael Lindsey - v&lt;br /&gt;
* Dan Suchy - v&lt;br /&gt;
* David Drexler - n&lt;br /&gt;
* Laura Smart - n&lt;br /&gt;
* Heather Pitts - n&lt;br /&gt;
*'''capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.mcmenamins.com/311-six-arms-home Six Arms - McMenamins] (Pub Food &amp;amp; they brew their own beer) ''Meet in the Lobby at 6pm. I've also emailed you. --Joel''&lt;br /&gt;
* Joel Richard (richardjm AT si.edu) (leader) - v&lt;br /&gt;
* Margaret Heller - v&lt;br /&gt;
* Sibyl Schaefer (sschaefer AT rockarch . org) - v&lt;br /&gt;
* Tim Lepczyk (timlepczyk AT gmail.com) - n&lt;br /&gt;
* Ray Schwartz (schwartzr2@wpunj.edu) - v&lt;br /&gt;
* Andrea Schurr (andrea-schurr AT utc DOT edu) - v(2nd-timer)&lt;br /&gt;
* '''capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.611supreme.com/ 611 Supreme] (Crepes and Full Bar) ''Reservation for 6 at 6:30. Meet in the conference hotel lobby at 6pm. Look for the short woman in a trench coat and wide brim hat ~Becky''&lt;br /&gt;
&lt;br /&gt;
*Becky Yoose (leader) - v &lt;br /&gt;
*Cynthia Ng - n&lt;br /&gt;
*Zoe Chao - v&lt;br /&gt;
*Stephanie Collett - n (2nd-timer)&lt;br /&gt;
*Bethany Nowviskie - n&lt;br /&gt;
* Ben Shum - n&lt;br /&gt;
*'''capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.panafricamarket.com/wp/ Pan Africa Restaurant &amp;amp; Bar] (Pan African) &lt;br /&gt;
CLOSED TUESDAYS!!!!!!!!!!!!!!!!!!&lt;br /&gt;
Sorry for the confusion. I have moved everyone to Long Provincial, so that you'll have a place held in case you want it. If Long Provincial doesn't suit you, please remove your name in case someone else wants the spot. Again, I'm sorry. --Jason&lt;br /&gt;
&lt;br /&gt;
[http://longprovincial.com/ Long Provincial] Vietnamese (.7 miles from hotel; 15 minute walk)&lt;br /&gt;
&lt;br /&gt;
Reservation for 6 for 6:30 (and I have a confirmation number!). Meet in the hotel lobby at 6 to allow for a strolling pace to walk over there.&lt;br /&gt;
&lt;br /&gt;
Has a jellyfish tank.&lt;br /&gt;
&lt;br /&gt;
*Jason Ronallo (leader?) - v?&lt;br /&gt;
*Nettie Lagace - n&lt;br /&gt;
*Bohyun Kim - n/v (2nd-timer)&lt;br /&gt;
*Wendy Robertson - n&lt;br /&gt;
*Jennifer Bowen - n/v (3rd timer)&lt;br /&gt;
*James Stuart - n&lt;br /&gt;
*'''capped at six'''&lt;br /&gt;
&lt;br /&gt;
'''Restaurants between .5 and 1 mile from hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://momijiseattle.com/ Momiji] New Japanese restaurant in Seattle - [http://www.concierge.com/tools/blogs/unpacked/2011/10/momiji-seattle.html Reviewed in Concierge.com]&lt;br /&gt;
&lt;br /&gt;
* Andrew Nagy (leader) - v&lt;br /&gt;
* Cory Lown - v&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[http://tomdouglas.com/index.php?page=palace-kitchen-dinner Palace Kitchen] (another Tom Douglas restaurant, w/ a focus on meat).  ''I have made a reservation for 6 at 8pm. Let's meet in the conference lobby at 6:30pm and make our way slowly over; we will find things to do in the interim. Look for Mike Giarlo, a man who may be holding a sign that says &amp;quot;HI I'M MIKE GIARLO&amp;quot; or otherwise shouting his name or looking confused.''&lt;br /&gt;
&lt;br /&gt;
* Mike Giarlo (leader) - v&lt;br /&gt;
* Carmen Mitchell - n&lt;br /&gt;
* Daniel Lovins - v&lt;br /&gt;
* Cary Gordon - v &lt;br /&gt;
* Declan Fleming - v&lt;br /&gt;
* Amy Unger - n&lt;br /&gt;
* (CAPPED AT SIX!)&lt;br /&gt;
&lt;br /&gt;
[http://sitkaandspruce.com/ Sitka and Spruce] (Eclectic, super-local and super-seasonal.) ''We have a reservation for 6 at 8:15pm. We'll meet in the conference lobby at 6:30 pm and head over - the owners also run [http://www.ferdinandthebar.com/home/ Bar Ferd'nand], a wine shop/bar in the same building, and we can kill time there before we eat. Look for Mark Matienzo or Hillel Arnold.''&lt;br /&gt;
&lt;br /&gt;
* Mark Matienzo (leader) - v&lt;br /&gt;
* Hillel Arnold - sophomore&lt;br /&gt;
* Devon Smith - v&lt;br /&gt;
* bernardo gomez - n&lt;br /&gt;
* Derek Merleaux - sophmore&lt;br /&gt;
* Jennifer Weintraub - n&lt;br /&gt;
* (CAPPED AT SIX!)&lt;br /&gt;
&lt;br /&gt;
[http://www.yelp.com/biz/japonessa-seattle Japonessa Restaurant] (Japanese + full bar)&lt;br /&gt;
* Kate Zwaard - n&lt;br /&gt;
* Joe Atzberger - v&lt;br /&gt;
* Scott Fisher - n (2nd-timer)&lt;br /&gt;
* Anoop Atre - n&lt;br /&gt;
&lt;br /&gt;
[http://tomdouglas.com/index.php?page=serious-pie Serious Pie] (Tom Douglas restaurant, inventive pizzas, good local beer list). &lt;br /&gt;
&lt;br /&gt;
* Christopher Spalding (leader) - v&lt;br /&gt;
* Robin Schaaf - n&lt;br /&gt;
* Jason Stirnaman - v&lt;br /&gt;
* Christina Morris - n&lt;br /&gt;
* Lisa Kurt - n&lt;br /&gt;
&lt;br /&gt;
[http://www.allmenus.com/wa/seattle/204592-ballet-restaurant/menu/ Ballet] (Vietnamese)&lt;br /&gt;
&lt;br /&gt;
[http://www.kokebrestaurant.com/ Kokeb Ethiopian Restaurant] (Ethiopian) ''Let's say meet at the lobby at 6pm like everyone else. Woohoo!''&lt;br /&gt;
&lt;br /&gt;
''We have reservations for 6 at 6:45.''&lt;br /&gt;
&lt;br /&gt;
* Andreas Orphanides (leader) - v&lt;br /&gt;
* Mark Mounts - v&lt;br /&gt;
* Joe Montibello - n&lt;br /&gt;
* Justin Littman - n&lt;br /&gt;
* Ron Peterson&lt;br /&gt;
* Bobbi Fox - sophmore&lt;br /&gt;
* (CAPPED AT SIX!)&lt;br /&gt;
Crashing the [http://www.seattlerb.org/ Seattle Ruby] meetup, which meets on Capital Hill at 7:00 on Tuesdays. Eat at [http://www.yelp.com/biz/poppy-seattle Poppy] before.  Leaving from the hotel lobby at 6:00.  ''If you dig Ruby, come to this.  Seattle ruby produced Nokogiri, Vlad, Rubygems.org ....''&lt;br /&gt;
* Matt Zumwalt (leader) - v&lt;br /&gt;
* *Justin Coyne - n&lt;br /&gt;
* Misty De Meo - n&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://tomdouglas.com/index.php?page=dahlia-lounge Dahlia Lounge] (Pacific Northwest cuisine, $$$)&lt;br /&gt;
&lt;br /&gt;
[http://www.mattsinthemarket.com/ Matt's in the Market] (Northwest Cuisine, $$$)&lt;br /&gt;
&lt;br /&gt;
[http://www.placepigalle-seattle.com/ Place Pigalle] (French)&lt;br /&gt;
&lt;br /&gt;
[http://www.chezshea.com/ Chez Shea] (French)&lt;br /&gt;
&lt;br /&gt;
[http://www.elysianbrewing.com/elysian.html Elysian Breweries and Pubs] (Pub Food)&lt;br /&gt;
&lt;br /&gt;
[http://www.mezaseattle.com/index.html Meza] (Latin Fare)&lt;br /&gt;
* Tara Robertson - n&lt;br /&gt;
* Shawn Averkamp - sophomore&lt;br /&gt;
* Corey Harper - v&lt;br /&gt;
* Shaun Ellis - sophomore&lt;br /&gt;
* Jon Stroop - fifth year senior&lt;br /&gt;
* Birkin James Diana - v (hi Jon!; hey newcomers, I'm taking the 6th slot, but, if you're stuck for a signup, plz do feel free to bump/overwrite me - seriously!)&lt;br /&gt;
* '''capped at 6'''''(So, who's the fearless leader of this group? ~yo_bj)''&lt;br /&gt;
&lt;br /&gt;
[http://inthebowlbistro.com/index.php In the Bowl] (Veg*n, Asian)&lt;br /&gt;
&lt;br /&gt;
[http://www.plumbistro.com/ Plumb Bistro] (Veg*n)&lt;br /&gt;
&lt;br /&gt;
[http://highlineseattle.com/ Highline] (Veg*n, bar)&lt;br /&gt;
  &lt;br /&gt;
'''Restaurants more than 1 miles from the hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://bravehorsetavern.com/ Brave Horse Tavern] (another Tom Douglas, good regional beer list, yummy food. Near South Lake Union. Would require a ride on the South Lake Union Trolley (SLUT), but it's easy to get to/use from downtown. &lt;br /&gt;
&lt;br /&gt;
[http://www.temperodobrasil.net/ Tempero do Brasil] I was excited to see Ipanema Grill 6 blocks from the hotel, unfortunately it seems to be closed for good.  So this restaurant which is a 10 minute ($15) cab ride away and which also serves Brazilian cuisine (including the ever-tasty feijoada) will have to do.&lt;br /&gt;
* Robert Haschart - leader - v third year&lt;br /&gt;
* Molly Pickral - n&lt;br /&gt;
&lt;br /&gt;
[http://flyingfishrestaurant.com/ Flying Fish] (Seafood)&lt;br /&gt;
&lt;br /&gt;
[http://www.allmenus.com/wa/seattle/3437-cafe-flora/menu/dinner/ Cafe Flora] (FANTASTIC Veg*n restaurant. Use Metro bus #11 to get there)&lt;br /&gt;
&lt;br /&gt;
[http://www.teapotvegetarianhouse.com/index.htm Teapot Vegetarian House] (Veg*n, Asian)&lt;br /&gt;
&lt;br /&gt;
[http://spaceneedle.com/restaurant/ Space Needle] (American, Pricy; but what the heck, listed it anyway for those who want the experience)&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Get Lamp&amp;quot; viewing Tuesday (9 PM) ===&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Tuesday, February 7, 9 PM or shortly after -Courtyard Ballroom&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Adam Wead and Michael Klein are organizing a viewing of [http://www.getlamp.com/ Get Lamp: The Text Adventure Documentary]&lt;br /&gt;
&lt;br /&gt;
It's not about Linux, Apache, MySQL or PHP, but if you don't have a one, you might get eaten by a grue.&lt;br /&gt;
&lt;br /&gt;
If there is additional interest, there may be another viewing this week.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Morning Run Wednesday===&lt;br /&gt;
I (Ray Schwartz) am organizing a morning run for anyone that would like to join me.  It will be around 5 to 6 miles.  I usually run a 10 minute per mile pace. And I would like to start around 7am.  Select which days Tuesday or Wednesday or both mornings.  Choose the date you wish via this Doodle link http://www.doodle.com/3tbigutqvkda5ib8&lt;br /&gt;
&lt;br /&gt;
I will map out a course when I arrive and will post it on the wiki.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Veg*n Dinner Wednesday===&lt;br /&gt;
&lt;br /&gt;
We'll pick a place with lots of veg*n options to go eat Wednesday for dinner. Vegetarians and non-vegetarians welcome.&lt;br /&gt;
&lt;br /&gt;
*[http://lovinghut.us/seattle/index.html Loving Hut] Modest price. 1 mile from hotel. Will do bill splitting if we let them know up front. &lt;br /&gt;
&lt;br /&gt;
Talked with Loving Hut and made a reservation for 15 for 6:30. Meet in the hotel lobby at 6.&lt;br /&gt;
&lt;br /&gt;
*Jason Ronallo (jronallo AT gmail.com)&lt;br /&gt;
*Sean Hannan&lt;br /&gt;
*Ed Summers&lt;br /&gt;
*James Stuart&lt;br /&gt;
*Bohyun Kim&lt;br /&gt;
*Bethany Nowviskie&lt;br /&gt;
*Margaret Heller&lt;br /&gt;
*Laura Smart&lt;br /&gt;
*Sibyl Schaefer&lt;br /&gt;
*Cynthia Ng&lt;br /&gt;
*Andrea Shurr&lt;br /&gt;
*Eric James&lt;br /&gt;
*Birkin James Diana&lt;br /&gt;
*Sheree F&lt;br /&gt;
*Misty De Meo&lt;br /&gt;
*Reservation is for 15.&lt;br /&gt;
&lt;br /&gt;
===Meat-Up Dinner Wednesday===&lt;br /&gt;
&lt;br /&gt;
[http://www.bokaseattle.com/ BOKA Kitchen + Bar], 1010 1st Ave (between Spring St &amp;amp; Madison St) - about 1/3 mile/5 min from hotel. We head over from the Amazon Technology Open House and get there by 8PM.&lt;br /&gt;
Very much a eat-local place. Beecher cheddar - yum. Nice, mellow room. We should be back in plenty of time to hit the Drink-Up.&lt;br /&gt;
&lt;br /&gt;
* Cary Gordon&lt;br /&gt;
* Anoop Atre&lt;br /&gt;
&lt;br /&gt;
Note that they have some excellent non-meat options for any meat groupies that want to hang with us.&lt;br /&gt;
&lt;br /&gt;
(if you do not find a suitable burger joint, there are also some top-notch steakhouses in Seattle. Both the Metropolitan Grill and El Gaucho are delightful if folks are OK with $50 steaks. Just FYI, not trying to hijack your meat-up, Cary!. -mjgiarlo)&lt;br /&gt;
&lt;br /&gt;
===[[2012 Craft Brew Drinkup|Craft Brew Drinkup]], Wednesday (9 PM)===&lt;br /&gt;
&lt;br /&gt;
'''Wednesday, February 8, 9 PM-ish -Hospitality Suite'''&lt;br /&gt;
&lt;br /&gt;
Like good beer? Bring some in your luggage! Some of us are planning to bring some of our favorite local, special, or homebrewed beers to share. Interested? Sign up on the [[2012 Craft Brew Drinkup]] page!&lt;br /&gt;
&lt;br /&gt;
===Dim Sum Lunch Thursday===&lt;br /&gt;
&lt;br /&gt;
For those of you staying in town after the last session on Thursday, [http://oasiankitchen.com/ O'Asian Kitchen] has dim sum service during the weekdays. Meet up around 12:35, meeting location tba. Bring cash for easier bill splitting.&lt;br /&gt;
&lt;br /&gt;
*Becky Yoose&lt;br /&gt;
* Declan Fleming - love me some Dim Sum!&lt;br /&gt;
* Adam Wead&lt;br /&gt;
* Heather Pitts&lt;br /&gt;
* Sibyl Schaefer&lt;br /&gt;
* Anoop Atre&lt;br /&gt;
* Dan Suchy&lt;br /&gt;
* Carmen Mitchell&lt;br /&gt;
* Tara Robertson&lt;br /&gt;
* Ray Schwartz&lt;br /&gt;
* Cynthia Ng&lt;br /&gt;
* Corey Harper&lt;br /&gt;
* Joshua Gomez&lt;br /&gt;
* Cary Gordon&lt;br /&gt;
* Mike Giarlo&lt;br /&gt;
* Joe Atzberger&lt;br /&gt;
* Dileshni Jayasinghe&lt;br /&gt;
* Ryan Wick&lt;br /&gt;
&lt;br /&gt;
==Social Map - places of interest==&lt;br /&gt;
[http://g.co/maps/4m5pk Code4lib 2012 - Seattle - social events, hangouts, and places to see]&lt;br /&gt;
&lt;br /&gt;
==Seattle Events Feb 5-9==&lt;br /&gt;
===Saturday, February 4, 2012===&lt;br /&gt;
In case you are showing up really early.&lt;br /&gt;
* Belgianfest: http://www.washingtonbeer.com/belgianfest/&lt;br /&gt;
===Sunday, February 5, 2012===&lt;br /&gt;
* Clinton Fearon &amp;amp; The Boogie Brown Band/Live Wyya/Adrian Xavier/Selecta Raiford/DJ Courtland, Neumos: http://neumos.com/neumos.php&lt;br /&gt;
* Michael The Blind/The Els, Skylark: http://www.skylarkcafe.com/&lt;br /&gt;
* Addaura/Alda/Hallow, Comet&lt;br /&gt;
* &amp;quot;I Am My Own Wife&amp;quot; 7:30pm at Seattle Repertory Theatre (Seattle Center) http://www.seattlerep.org/Plays/1112/IM/&lt;br /&gt;
&lt;br /&gt;
===Monday, February 6, 2012===&lt;br /&gt;
* Silent Movie Mondays:  Last Command 1928, http://stgpresents.org/artists/?artist=1829#, Show at 7:00pm, The Paramount Theatre $10&lt;br /&gt;
This all-classic film series, First Oscars, is accompanied by live music from the historic Mighty Wurlitzer organ, one of the last three remaining organs of its kind to reside in its original environment, played by critically acclaimed organist Jim Riggs.&lt;br /&gt;
&lt;br /&gt;
===Tuesday, February 7, 2012===&lt;br /&gt;
* Lionize/Maylene &amp;amp; The Sons Of Disaster, El Corazon: http://elcorazonseattle.com/&lt;br /&gt;
* The Pulltab Playboys/Rachel Lyn Harrington &amp;amp; The Knock Outs/The James Low Western Front, Sunset: http://sunsettavern.com/&lt;br /&gt;
* Twin Sister, Vera: http://theveraproject.org/shows/&lt;br /&gt;
* The Features, Chop Suey: http://www.chopsuey.com/&lt;br /&gt;
* Wilco/White Denim, Paramount Theatre: http://stgpresents.org/&lt;br /&gt;
* &amp;quot;I Am My Own Wife&amp;quot; 7:30pm at Seattle Repertory Theatre (Seattle Center) http://www.seattlerep.org/Plays/1112/IM/&lt;br /&gt;
* Intro to Arduino Workshop, 7pm at Metrix Create Space http://metrixcreatespace.com/&lt;br /&gt;
&lt;br /&gt;
===Wednesday, February 8, 2012===&lt;br /&gt;
* The Golden Blondes/The Jet Age/Mr. Drinx &amp;amp; The Pot Heads, Sunset: http://sunsettavern.com/&lt;br /&gt;
* Pipsisewah/The Chasers/The Magic Mirrors, Tractor: http://www.tractortavern.com/ &lt;br /&gt;
* Dengue Fever vs Secret Chiefs 3, Moe Bar http://bit.ly/yJtfXv  (how could you pass the opportunity to see someone play this thing :http://bit.ly/wB5AgZ&lt;br /&gt;
* Amazon Tech in Seattle is having an open house next Wednesday at 5:30 PM with Werner Vogels and David Friedberg of the Climate Corporation. https://aws.amazon.com/amazon-open-house-february-2012/ ([http://g.co/maps/adpnt map])&lt;br /&gt;
&lt;br /&gt;
===Thursday, February 9, 2012===&lt;br /&gt;
* SAM Opening - Gauguin and Polynesia: An Elusive Paradise: http://www.seattleartmuseum.org/gauguin&lt;br /&gt;
* The Jayhawks, Neptune Theater: http://stgpresents.org/&lt;br /&gt;
* Digital Leather, Comet &lt;br /&gt;
* Savani World Quintet/Super Sones, Columbia City Theater: http://www.columbiacitytheater.com/&lt;br /&gt;
* Blvd Park {album release}/Nettle Honey/Creeping Time, Tractor: http://www.tractortavern.com/&lt;br /&gt;
* Eleanor Friedberger, Crocodile: http://thecrocodile.com/index.html&lt;br /&gt;
&lt;br /&gt;
===Ongoing Events===&lt;br /&gt;
* Seattle Art Museum: Tours are every Saturday &amp;amp; Sunday at noon, and the First Thursday of every month at 10:30, 11:30 am, 12:30 &amp;amp; 1:30 pm.&lt;br /&gt;
* EMP:  Exhibits on display include: Battlestar Galactica, Nirvana, Avatar, and Can’t Look Away: The Lure of Horror Film&lt;br /&gt;
* Teatro ZinZanni: ¡Caliente! http://dreams.zinzanni.org/&lt;br /&gt;
* Pacific NW Ballet: performing Don Quixote at McCaw Hall http://www.pnb.org/&lt;br /&gt;
* Oklahoma!, Sunday matinee and nightly: 5th Avenue Theatre, 1308 Fifth Avenue http://www.5thavenue.org/show/oklahoma&lt;br /&gt;
&lt;br /&gt;
==Local events/places==&lt;br /&gt;
* Metrix Create Space&lt;br /&gt;
* Ada's Technical Books&lt;br /&gt;
* Northwest Outdoor Center&lt;br /&gt;
* Center for Wooden Boats&lt;br /&gt;
* Empty Sea Studios acoustic music&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Local Beer Places==&lt;br /&gt;
* Map of [http://beermapping.com/maps/citymaps.php?m=seattle#lat=47.66723703450515&amp;amp;lng=-122.28263854980469&amp;amp;z=5 beer venues] maintained at Beermapping.com.&lt;br /&gt;
* List of [http://www.washingtonbeer.com/breweries/seattle-king-co/ local breweries] ([http://maps.google.com/maps/ms?hl=en&amp;amp;ie=UTF8&amp;amp;msa=0&amp;amp;msid=201783184139227541123.0004813e64758434cb054&amp;amp;source=embed&amp;amp;ll=47.558921,-122.106171&amp;amp;spn=0.442982,1.234589&amp;amp;z=10&amp;amp;source=embed map]) maintained by the Washington Beer Commission&lt;br /&gt;
* Map of [http://www.ratebeer.com/Places/RegionMap.asp?rid=7600 beer venues] maintained by Ratebeer.com.&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
[http://orbiscascade.org/index/c4l-things-to-do-in-seattle Things to do in Seattle, from the hosts]&lt;/div&gt;</summary>
		<author><name>Cwlown</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_talks_proposals&amp;diff=9707</id>
		<title>2012 talks proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_talks_proposals&amp;diff=9707"/>
				<updated>2011-11-15T19:39:39Z</updated>
		
		<summary type="html">&lt;p&gt;Cwlown: /* How people search the library from a single search box */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Deadline for talk submission is ''Sunday, November 20''.&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;
 * diversity of topics&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;
&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 second speaker&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;
== VuFind 2.0: Why and How? ==&lt;br /&gt;
&lt;br /&gt;
* Demian Katz, Villanova University, demian.katz@villanova.edu&lt;br /&gt;
&lt;br /&gt;
A major new version of the VuFind discovery software is currently in development.  While VuFind 1.x remains extremely popular, some of its components are beginning to show their age.  VuFind 2.0 aims to retain all the strengths of the previous version of the software while making the architecture cleaner, more modern and more standards-based.  This presentation will examine the motivation behind the update, preview some of the new features to look forward to, and discuss the challenges of creating a developer-friendly open source package in PHP.&lt;br /&gt;
&lt;br /&gt;
== Open Source Software Registry ==&lt;br /&gt;
&lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]], LYRASIS, Peter.Murray@lyrasis.org&lt;br /&gt;
&lt;br /&gt;
LYRASIS is creating and shepherding a [[Registry_E-R_Diagram|registry of library open source software]] as part of its [http://www.lyrasis.org/News/Press-Releases/2011/LYRASIS-Receives-Grant-to-Support-Open-Source.aspx grant from the Mellon Foundation to support the adoption of open source software by libraries].  &lt;br /&gt;
The goal of the grant is to help libraries of all types determine if open source software is right for them, and what combination of software, hosting, training, and consulting works for their situation.  &lt;br /&gt;
The registry is intended to become a community exchange point and stimulant for growth of the library open source ecosystem by connecting libraries with projects, service providers, and events.&lt;br /&gt;
&lt;br /&gt;
The first half of this session will demonstrate the registry functions and describe how projects and providers can get involved.  &lt;br /&gt;
The second half of the session will be a brainstorming suggestion of how to expand the functionality and usefulness of the registry.&lt;br /&gt;
&lt;br /&gt;
== Property Graphs And TinkerPop Applications in Digital Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Brian Tingle, California Digital Library, brian.tingle.cdlib.org@gmail.com&lt;br /&gt;
&lt;br /&gt;
[http://www.tinkerpop.com/ TinkerPop] is an open source software development group focusing on technologies in the [http://en.wikipedia.org/wiki/Graph_database graph database] space.   &lt;br /&gt;
This talk will provide a general introduction to the TinkerPop Graph Stack and the [https://github.com/tinkerpop/gremlin/wiki/Defining-a-Property-Graph property graph model] is uses.  The introduction will include code examples and explanations of the property graph models used by the [http://socialarchive.iath.virginia.edu/ Social Networks in Archival Context] project and show how the historical social graph is exposed as a JSON/REST API implemented by a TinkerPop [https://github.com/tinkerpop/rexster rexster] [https://github.com/tinkerpop/rexster-kibbles Kibble] that contains the application's graph theory logic.  Other graph database applications possible with TinkerPop such as RDF support, and citation analysis will also be discussed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Security in Mind ==&lt;br /&gt;
 &lt;br /&gt;
* Erin Germ, United States Naval Academy, Nimitz Library, germ@usna.edu&lt;br /&gt;
&lt;br /&gt;
I would like to talk about security of library software.&lt;br /&gt;
&lt;br /&gt;
Over the Summer, I discovered a critical vulnerability in a vendor’s software that (verified) allowed me to assume any user’s identity for that site, (verified) switch to any user, and to (unverified, meaning I didn’t not perform this as I didn’t want to “hack” another library’s site) assume the role of any user for any other library who used this particular vendor's software.&lt;br /&gt;
&lt;br /&gt;
Within a 3 hour period, I discovered a 2 vulnerabilities: 1) minor one allowing me to access any backups from any library site, and 2) a critical vulnerability.  From start to finish, the examination, discovery in the vulnerability, and execution of a working exploit was done in less than 2 hours. The vulnerability was a result of poor cookie implementation. The exploit itself revolved around modifying the cookie, and then altering the browser’s permissions by assuming the role of another user.&lt;br /&gt;
&lt;br /&gt;
I do not intend on stating which vendor it was, but I will show how I was able to perform this. If needed, I can do further research and “investigation” into other vendor's software to see what I can “find”.&lt;br /&gt;
&lt;br /&gt;
''If selected, I will contact the vendor to inform them that I will present about this at C4L2012. I do not intend on releasing the name of the vendor.''&lt;br /&gt;
&lt;br /&gt;
== Search Engines and Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Greg Lindahl, blekko CTO, greg@blekko.com&lt;br /&gt;
&lt;br /&gt;
[https://blekko.com blekko] is a new web-scale search engine which enables end-users to create vertical search engines, through a feature called [http://help.blekko.com/index.php/category/slashtags/ slashtags]. Slashtags can contain as few as 1 or as many as tens of thousands of websites relevant to a narrow or broad topic. We have an extensive set of slashtags curated by a combination of volunteers and an in-house librarian team, or end-users can create and share their own. This talk will cover examples of slashtag creation relevant to libraries, and show how to embed this search into a library website, either using javascript or via our API.&lt;br /&gt;
&lt;br /&gt;
''We have exhibited at a couple of library conferences, and have received a lot of interest. blekko is a free service.''&lt;br /&gt;
&lt;br /&gt;
== Beyond code. Versioning data with Git and Mercurial. ==&lt;br /&gt;
&lt;br /&gt;
* Stephanie Collett, California Digital Library, stephanie.collett@ucop.edu&lt;br /&gt;
* Martin Haye, California Digital Library, martin.haye@ucop.edu&lt;br /&gt;
&lt;br /&gt;
Within a relatively short time since their introduction, [http://en.wikipedia.org/wiki/Distributed_Version_Control_System distributed version control systems] (DVCS) like [http://git-scm.com/ Git] and [http://mercurial.selenic.com/ Mercurial] have enjoyed widespread adoption for versioning code. It didn’t take long for the library development community to start discussing the potential for using DVCS within our applications and repositories to version data. After all, many of the features that have made some of these systems popular in the open source community to version code (e.g. lightweight, file-based, compressed, reliable) also make them compelling options for versioning data.  And why write an entire versioning system from scratch if a DVCS solution can be a drop-in solution? At the [http://www.cdlib.org/ California Digital Library] (CDL) we’ve started using Git and Mercurial in some of our applications to version data. This has proven effective in some situations and unworkable in others. This presentation will be a practical case study of CDL’s experiences with using DVCS to version data. We will explain how we’re incorporating Git and Mercurial in our applications, describe our successes and failures and consider the issues involved in repurposing these systems for data versioning.&lt;br /&gt;
&lt;br /&gt;
==Design for Developers==&lt;br /&gt;
&lt;br /&gt;
*Lisa Kurt, University of Nevada, Reno, lkurt@unr.edu&lt;br /&gt;
&lt;br /&gt;
Users expect good design. This talk will delve into what makes really great design, what to look for, and how to do it. Learn the principles of great design to take your applications, user interfaces, and projects to a higher level. With years of experience in graphic design and illustration, Lisa will discuss design principles, trends, process, tools, and development. Design examples will be from her own projects as well as a variety from industry. You’ll walk away with design knowledge that you can apply immediately to a variety of applications and a number of top notch go-to resources to get you up and running.&lt;br /&gt;
&lt;br /&gt;
==Building research applications with Mendeley==&lt;br /&gt;
&lt;br /&gt;
William Gunn, Mendeley william.gunn@mendeley.com (@mrgunn)&lt;br /&gt;
&lt;br /&gt;
This is partly a tool talk and partly a big idea one.&lt;br /&gt;
&lt;br /&gt;
Mendeley has built the world's largest open database of research and we've now begun to collect some interesting social metadata around the document metadata. I would like to share with the Code4Lib attendees information about using this resource to do things within your application that have previously been impossible for the library community, or in some cases impossible without expensive database subscriptions. One thing that's now possible is to augment catalog search by surfacing information about content usage, allowing people to not only find things matching a query, but popular things or things read by their colleagues. In addition to augmenting search, you can also use this information to augment discovery. Imagine an online exhibit of artifacts from a newly discovered dig not just linking to papers which discuss the artifact, but linking to really good interesting papers about the place and the people who made the artifacts. So the big idea is, &amp;quot;How will looking at the literature from a broader perspective than simple citation analysis change how research is done and communicated? How can we build tools that make this process easier and faster?&amp;quot; I can show some examples of applications that have been built using the Mendeley and PLoS APIs to begin to address this question, and I can also present results from Mendeley's developer challenge which shows what kinds of applications researchers are looking for, what kind of applications peope are building, and illustrates some interesting places where the two don't overlap.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Your UI can make or break the application (to the user, anyway)==&lt;br /&gt;
&lt;br /&gt;
* Robin Schaaf, University of Notre Dame, schaaf.4@nd.edu&lt;br /&gt;
&lt;br /&gt;
UI development is hard and too often ends up as an after-thought to computer programmers - if you were a CS major in college I'll bet you didn't have many, if any, design courses.  I'll talk about how to involve the users upfront with design and some common pitfalls of this approach.  I'll also make a case for why you should do the screen design before a single line of code is written.  And I'll throw in some ideas for increasing usability and attractiveness of your web applications.  I'd like to make a case study of the UI development of our open source ERMS.&lt;br /&gt;
&lt;br /&gt;
==Why Nobody Knows How Big The Library Really Is - Perspective of a Library Outside Turned Insider==&lt;br /&gt;
&lt;br /&gt;
* Patrick Berry, California State University, Chico, pberry@csuchico.edu&lt;br /&gt;
&lt;br /&gt;
In this talk I would like to bring the perspective of an &amp;quot;outsider&amp;quot; (although an avowed IT insider) to let you know that people don't understand the full scope of the library.  As we &amp;quot;rethink education&amp;quot;, it is incumbent upon us to help educate our institutions as to the scope of the library.  I will present some of the tactics I'm employing to help people outside, and in some cases inside, the library to understand our size and the value we bring to the institution.&lt;br /&gt;
&lt;br /&gt;
==Building a URL Management Module using the Concrete5 Package Architecture==&lt;br /&gt;
&lt;br /&gt;
* David Uspal, Villanova University, david.uspal@villanova.edu&lt;br /&gt;
&lt;br /&gt;
Keeping track of URLs utilized across a large website such as a university library, and keeping that content up to date for subject and course guides, can be a pain, and as an open source shop, we’d like to have open source solution for this issue.  For this talk, I intend to detail our solution to this issue by walking step-by-step through the building process for our URL Management module -- including why a new solution was necessary; a quick rundown of our CMS ([http://www.concrete5.org Concrete5], a CMS that isn’t Drupal); utilizing the Concrete5 APIs to isolate our solution from core code (to avoid complications caused by core updates); how our solution was integrated into the CMS architecture for easy installation; and our future plans on the project.&lt;br /&gt;
&lt;br /&gt;
==Building an NCIP connector to OpenSRF to facilitate resource sharing==&lt;br /&gt;
&lt;br /&gt;
* Jon Scott, Lyrasis, jon_scott@wsu.edu and Kyle Banerjee, Orbis Cascade Alliance, banerjek@uoregon.edu &lt;br /&gt;
&lt;br /&gt;
How do you reverse engineer any protocol to provide a new service? Humans (and worse yet, committees) often design verbose protocols built around use cases that don't line up current reality. To compound difficulties, the contents of protocol containers are not sufficiently defined/predictable and the only assistance available is sketchy documentation and kind individuals on the internet willing to share what they learned via trial by fire.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCIP (Niso Circulation Interchange Protocol) is an open standard that defines a set of messages to support exchange of circulation data between disparate circulation, interlibrary loan, and related applications -- widespread adoption of NCIP would eliminate huge amounts of duplicate processing in separate systems. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This presentation discusses how we learned enough about NCIP and OpenSRF from scratch to build an NCIP responder for Evergreen to facilitate resource sharing in a large consortium that relies on over 20 different ILSes.&lt;br /&gt;
&lt;br /&gt;
==Practical Agile: What's Working for Stanford, Blacklight, and Hydra==&lt;br /&gt;
&lt;br /&gt;
* Naomi Dushay, Stanford University Libraries, ndushay@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Agile development techniques can be difficult to adopt in the context of library software development.  Maybe your shop has only one or two developers, or you always have too many simultaneous projects.   Maybe your new projects can’t be started until 27 librarians reach consensus on the specifications.&lt;br /&gt;
&lt;br /&gt;
This talk will present successful Agile- and Silicon-Valley-inspired practices we’ve adopted at Stanford and/or in the Blacklight and Hydra projects.  We’ve targeted developer happiness as well as improved productivity with our recent changes.  User stories, dead week, sight lines … it’ll be a grab bag of goodies to bring back to your institution, including some ideas on how to adopt these practices without overt management buy in.&lt;br /&gt;
&lt;br /&gt;
==Quick and &amp;lt;strike&amp;gt;Dirty&amp;lt;/strike&amp;gt; Clean Usability: Rapid Prototyping with Bootstrap==&lt;br /&gt;
&lt;br /&gt;
* Shaun Ellis, Princeton University Libraries, shaune@princeton.edu &lt;br /&gt;
&lt;br /&gt;
''&amp;quot;The code itself is unimportant; a project is only as useful as people actually find it.&amp;quot;  - Linus Torvalds'' [http://bit.ly/p4uuyy]&lt;br /&gt;
&lt;br /&gt;
Usability has been a buzzword for some time now, but what is the process for making the the transition toward a better user experience, and hence, better designed library sites?  I will discuss the one facet of the process my team is using to redesign the Finding Aids site for Princeton University Libraries (still in development).  The approach involves the use of rapid prototyping, with Bootstrap [http://twitter.github.com/bootstrap/], to make sure we are on track with what users and stakeholders expect up front, and throughout the development process.&lt;br /&gt;
&lt;br /&gt;
Because Bootstrap allows for early and iterative user feedback, it is more effective than the historic Photoshop mockups/wireframe technique.  The Photoshop approach allows stakeholders to test the look, but not the feel -- and often leaves developers scratching their heads.  Being a CSS/HTML/Javascript grid-based framework, Bootstrap makes it easy for anyone with a bit of HTML/CSS chops to quickly build slick, interactive prototypes right in the browser -- tangible solutions which can be shared, evaluated, revised, and followed by all stakeholders (see Minimum Viable Products [http://en.wikipedia.org/wiki/Minimum_viable_product]).  Efficiency is multiplied because the customized prototypes can flow directly into production use, as is the goal with iterative development approaches, such as the Agile methodology.&lt;br /&gt;
&lt;br /&gt;
While Bootstrap is not the only framework that offers grid-based layout, development is expedited and usability is enhanced by Bootstraps use of of &amp;quot;prefabbed&amp;quot; conventional UI patterns, clean typography, and lean Javascript for interactivity.   Furthermore, out-of-the box Bootstrap comes in a fairly neutral palette, so focus remains on usability, and does not devolve into premature discussions of color or branding choices.  Finally, using Less can be a powerful tool in conjunction with Bootstrap, but is not necessary.  I will discuss the pros and cons, and offer examples for how to getting up and running with or without Less.&lt;br /&gt;
&lt;br /&gt;
==Search Engine Relevancy Tuning - A Static Rank Framework for Solr/Lucene==&lt;br /&gt;
&lt;br /&gt;
* Mike Schultz, Amazon.com (formerly Summon Search Architect) mike.schultz@gmail.com&lt;br /&gt;
&lt;br /&gt;
Solr/Lucene provides a lot of flexibility for adjusting relevancy scoring and improving search results.  Roughly speaking there are two areas of concern: Firstly, a 'dynamic rank' calculation that is a function of the user query and document text fields.  And secondly, a 'static rank' which is independent of the query and generally is a function of non-text document metadata.  In this talk I will outline an easily understood, hand-tunable static rank system with a minimal number of parameters.&lt;br /&gt;
&lt;br /&gt;
The obvious major feature of a search engine is to return results relevant to a user query.  Perhaps less obvious is the huge role query independent document features play in achieving that. Google's PageRank is an example of a static ranking of web pages based on links and other secret sauce.  In the Summon service, our 800 million documents have features like publication date, document type, citation count and Boolean features like the-article-is-peer-reviewed.  These fields aren't textual and remain 'static' from query to query, but need to influence a document's relevancy score.  In our search results, with all query related features being equal, we'd rather have more recent documents above older ones, Journals above Newspapers, and articles that are peer reviewed above those that are not. The static rank system I will describe achieves this and has the following features:&lt;br /&gt;
&lt;br /&gt;
* Query-time only calculation - nothing is baked into the index - with parameters adjustable at query time.&lt;br /&gt;
* The system is based on a signal metaphor where components are 'wired' together.  System components allow multiplexing, amplifying, summing, tunable band-pass filtering, string-to-value-mapping all with a bare minimum of parameters.&lt;br /&gt;
* An intuitive approach for mixing dynamic and static rank that is more effective than simple adding or multiplying.&lt;br /&gt;
* A way of equating disparate static metadata types that leads to understandable results ordering.&lt;br /&gt;
&lt;br /&gt;
==Submitting Digitized Book-like things to the Internet Archive==&lt;br /&gt;
&lt;br /&gt;
* Joel Richard, Smithsonian Institution Libraries, richardjm@si.edu&lt;br /&gt;
&lt;br /&gt;
The Smithsonian Libraries has submitted thousands of out-of-copyright items to the Internet Archive over the years. Specifically in relation to the Biodiversity Heritage Library, we have developed an in-house boutique scanning and upload process that became a learning experience in automated uploading to the Archive. As part of the software development, we created a whitepaper that details the combined learning experiences of the Smithsonian Libraries and the Missouri Botanical Garden. We will discuss some of the the contents of this whitepaper in the context of our scanning process and the manner in which we upload items to the Archive. &lt;br /&gt;
&lt;br /&gt;
Our talk will include a discussion of the types of files and their formats used by the Archive, processes that the Archive performs on uploaded items, ways of interacting and affecting those processes, potential pitfalls and solutions that you may encounter when uploading, and tools that the Archive provides to help monitor and manage your uploaded documents. &lt;br /&gt;
&lt;br /&gt;
Finally, we'll wrap up with a brief summary of how to use things that are on the Internet Archive in your own websites.&lt;br /&gt;
&lt;br /&gt;
== So... you think you want to Host a Code4Lib National Conference, do you? ==&lt;br /&gt;
&lt;br /&gt;
* Elizabeth Duell, Orbis Cascade Alliance, eduell@uoregon.edu&lt;br /&gt;
&lt;br /&gt;
Are you interested in hosting your own Code4Lib Conference? Do you know what it would take? What does BEO stands for? What does F&amp;amp;B Minimum mean? Who would you talk to for support/mentoring? There are so many things to think about: internet support, venue size, rooming blocks, contracts, dietary restrictions and coffee (can't forget the coffee!) just to name a few. Putting together a conference of any size can look daunting, so let's take the scary out of it and replace it with a can do attitude!&lt;br /&gt;
&lt;br /&gt;
Be a step ahead of the game by learning from the people behind the curtain. Ask questions and be given templates/ cheat sheets! &lt;br /&gt;
&lt;br /&gt;
== HTML5 Microdata and Schema.org ==&lt;br /&gt;
 &lt;br /&gt;
* Jason Ronallo, North Carolina State University Libraries, jason_ronallo@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
When the big search engines announced support for HTML5 microdata and the schema.org vocabularies, the balance of power for semantic markup in HTML shifted. &lt;br /&gt;
* What is microdata? &lt;br /&gt;
* Where does microdata fit with regards to other approaches like RDFa and microformats? &lt;br /&gt;
* Where do libraries stand in the worldview of Schema.org and what can they do about it? &lt;br /&gt;
* How can implementing microdata and schema.org optimize your sites for search engines?&lt;br /&gt;
* What tools are available?&lt;br /&gt;
&lt;br /&gt;
== Stack View: A Library Browsing Tool ==&lt;br /&gt;
 &lt;br /&gt;
* Annie Cain, Harvard Library Innovation Lab, acain@law.harvard.edu&lt;br /&gt;
* Jeff Goldenson, Harvard Library Innovation Lab, jgoldenson@law.harvard.edu&lt;br /&gt;
&lt;br /&gt;
In an effort to recreate and build upon the traditional method of browsing a physical library, we used catalog data, including dimensions and page count, to create a [http://librarylab.law.harvard.edu/projects/stackview/ virtual shelf].&lt;br /&gt;
&lt;br /&gt;
This CSS and JavaScript backed visualization allows items to sit on any number of different shelves, really taking advantage of its digital nature.  See how we built Stack View on top of our data and learn how you can create shelves of your own using our open source code.&lt;br /&gt;
&lt;br /&gt;
== “Linked-Data-Ready” Software for Libraries ==&lt;br /&gt;
&lt;br /&gt;
* Jennifer Bowen, University of Rochester River Campus Libraries, jbowen@library.rochester.edu&lt;br /&gt;
&lt;br /&gt;
Linked data is poised to replace MARC as the basis for the new library bibliographic framework.  For libraries to benefit from linked data, they must learn about it, experiment with it, demonstrate its usefulness, and take a leadership role in its deployment. &lt;br /&gt;
&lt;br /&gt;
The eXtensible Catalog Organization (XCO) offers open-source software for libraries that is “linked-data-ready.” XC software prepares MARC and Dublin Core metadata for exposure to the semantic web, incorporating FRBR Group 1 entities and registered vocabularies for RDA elements and roles. This presentation will include a software demonstration, proposed software architecture for creation and management of linked data, a vision for how libraries can migrate from MARC to linked data, and an update on XCO progress toward linked data goals.&lt;br /&gt;
&lt;br /&gt;
== How people search the library from a single search box ==&lt;br /&gt;
&lt;br /&gt;
* Cory Lown, North Carolina State University Libraries, cory_lown@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Searching the library is complex. There's the catalog, article databases, journal title and database title look-ups, the library website, finding aids, knowledge bases, etc. How would users search if they could get to all of these resources from a single search box? I'll share what we've learned about single search at NCSU Libraries by tracking use of QuickSearch (http://www.lib.ncsu.edu/search/index.php?q=aerospace+engineering), our home-grown unified search application. As part of this talk I will suggest low-cost ways to collect real world use data that can be applied to improve search. I will try to convince you that data collection must be carefully planned and designed to be an effective tool to help you understand what your users are telling you through their behavior. I will talk about how the fragmented library resource environment challenges us to provide useful and understandable search environments. Finally, I will share findings from analyzing millions of user transactions about how people search the library from a production single search box at a large university library.&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Cwlown</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_talks_proposals&amp;diff=9706</id>
		<title>2012 talks proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_talks_proposals&amp;diff=9706"/>
				<updated>2011-11-15T19:38:57Z</updated>
		
		<summary type="html">&lt;p&gt;Cwlown: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Deadline for talk submission is ''Sunday, November 20''.&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;
 * diversity of topics&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;
&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 second speaker&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;
== VuFind 2.0: Why and How? ==&lt;br /&gt;
&lt;br /&gt;
* Demian Katz, Villanova University, demian.katz@villanova.edu&lt;br /&gt;
&lt;br /&gt;
A major new version of the VuFind discovery software is currently in development.  While VuFind 1.x remains extremely popular, some of its components are beginning to show their age.  VuFind 2.0 aims to retain all the strengths of the previous version of the software while making the architecture cleaner, more modern and more standards-based.  This presentation will examine the motivation behind the update, preview some of the new features to look forward to, and discuss the challenges of creating a developer-friendly open source package in PHP.&lt;br /&gt;
&lt;br /&gt;
== Open Source Software Registry ==&lt;br /&gt;
&lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]], LYRASIS, Peter.Murray@lyrasis.org&lt;br /&gt;
&lt;br /&gt;
LYRASIS is creating and shepherding a [[Registry_E-R_Diagram|registry of library open source software]] as part of its [http://www.lyrasis.org/News/Press-Releases/2011/LYRASIS-Receives-Grant-to-Support-Open-Source.aspx grant from the Mellon Foundation to support the adoption of open source software by libraries].  &lt;br /&gt;
The goal of the grant is to help libraries of all types determine if open source software is right for them, and what combination of software, hosting, training, and consulting works for their situation.  &lt;br /&gt;
The registry is intended to become a community exchange point and stimulant for growth of the library open source ecosystem by connecting libraries with projects, service providers, and events.&lt;br /&gt;
&lt;br /&gt;
The first half of this session will demonstrate the registry functions and describe how projects and providers can get involved.  &lt;br /&gt;
The second half of the session will be a brainstorming suggestion of how to expand the functionality and usefulness of the registry.&lt;br /&gt;
&lt;br /&gt;
== Property Graphs And TinkerPop Applications in Digital Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Brian Tingle, California Digital Library, brian.tingle.cdlib.org@gmail.com&lt;br /&gt;
&lt;br /&gt;
[http://www.tinkerpop.com/ TinkerPop] is an open source software development group focusing on technologies in the [http://en.wikipedia.org/wiki/Graph_database graph database] space.   &lt;br /&gt;
This talk will provide a general introduction to the TinkerPop Graph Stack and the [https://github.com/tinkerpop/gremlin/wiki/Defining-a-Property-Graph property graph model] is uses.  The introduction will include code examples and explanations of the property graph models used by the [http://socialarchive.iath.virginia.edu/ Social Networks in Archival Context] project and show how the historical social graph is exposed as a JSON/REST API implemented by a TinkerPop [https://github.com/tinkerpop/rexster rexster] [https://github.com/tinkerpop/rexster-kibbles Kibble] that contains the application's graph theory logic.  Other graph database applications possible with TinkerPop such as RDF support, and citation analysis will also be discussed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Security in Mind ==&lt;br /&gt;
 &lt;br /&gt;
* Erin Germ, United States Naval Academy, Nimitz Library, germ@usna.edu&lt;br /&gt;
&lt;br /&gt;
I would like to talk about security of library software.&lt;br /&gt;
&lt;br /&gt;
Over the Summer, I discovered a critical vulnerability in a vendor’s software that (verified) allowed me to assume any user’s identity for that site, (verified) switch to any user, and to (unverified, meaning I didn’t not perform this as I didn’t want to “hack” another library’s site) assume the role of any user for any other library who used this particular vendor's software.&lt;br /&gt;
&lt;br /&gt;
Within a 3 hour period, I discovered a 2 vulnerabilities: 1) minor one allowing me to access any backups from any library site, and 2) a critical vulnerability.  From start to finish, the examination, discovery in the vulnerability, and execution of a working exploit was done in less than 2 hours. The vulnerability was a result of poor cookie implementation. The exploit itself revolved around modifying the cookie, and then altering the browser’s permissions by assuming the role of another user.&lt;br /&gt;
&lt;br /&gt;
I do not intend on stating which vendor it was, but I will show how I was able to perform this. If needed, I can do further research and “investigation” into other vendor's software to see what I can “find”.&lt;br /&gt;
&lt;br /&gt;
''If selected, I will contact the vendor to inform them that I will present about this at C4L2012. I do not intend on releasing the name of the vendor.''&lt;br /&gt;
&lt;br /&gt;
== Search Engines and Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Greg Lindahl, blekko CTO, greg@blekko.com&lt;br /&gt;
&lt;br /&gt;
[https://blekko.com blekko] is a new web-scale search engine which enables end-users to create vertical search engines, through a feature called [http://help.blekko.com/index.php/category/slashtags/ slashtags]. Slashtags can contain as few as 1 or as many as tens of thousands of websites relevant to a narrow or broad topic. We have an extensive set of slashtags curated by a combination of volunteers and an in-house librarian team, or end-users can create and share their own. This talk will cover examples of slashtag creation relevant to libraries, and show how to embed this search into a library website, either using javascript or via our API.&lt;br /&gt;
&lt;br /&gt;
''We have exhibited at a couple of library conferences, and have received a lot of interest. blekko is a free service.''&lt;br /&gt;
&lt;br /&gt;
== Beyond code. Versioning data with Git and Mercurial. ==&lt;br /&gt;
&lt;br /&gt;
* Stephanie Collett, California Digital Library, stephanie.collett@ucop.edu&lt;br /&gt;
* Martin Haye, California Digital Library, martin.haye@ucop.edu&lt;br /&gt;
&lt;br /&gt;
Within a relatively short time since their introduction, [http://en.wikipedia.org/wiki/Distributed_Version_Control_System distributed version control systems] (DVCS) like [http://git-scm.com/ Git] and [http://mercurial.selenic.com/ Mercurial] have enjoyed widespread adoption for versioning code. It didn’t take long for the library development community to start discussing the potential for using DVCS within our applications and repositories to version data. After all, many of the features that have made some of these systems popular in the open source community to version code (e.g. lightweight, file-based, compressed, reliable) also make them compelling options for versioning data.  And why write an entire versioning system from scratch if a DVCS solution can be a drop-in solution? At the [http://www.cdlib.org/ California Digital Library] (CDL) we’ve started using Git and Mercurial in some of our applications to version data. This has proven effective in some situations and unworkable in others. This presentation will be a practical case study of CDL’s experiences with using DVCS to version data. We will explain how we’re incorporating Git and Mercurial in our applications, describe our successes and failures and consider the issues involved in repurposing these systems for data versioning.&lt;br /&gt;
&lt;br /&gt;
==Design for Developers==&lt;br /&gt;
&lt;br /&gt;
*Lisa Kurt, University of Nevada, Reno, lkurt@unr.edu&lt;br /&gt;
&lt;br /&gt;
Users expect good design. This talk will delve into what makes really great design, what to look for, and how to do it. Learn the principles of great design to take your applications, user interfaces, and projects to a higher level. With years of experience in graphic design and illustration, Lisa will discuss design principles, trends, process, tools, and development. Design examples will be from her own projects as well as a variety from industry. You’ll walk away with design knowledge that you can apply immediately to a variety of applications and a number of top notch go-to resources to get you up and running.&lt;br /&gt;
&lt;br /&gt;
==Building research applications with Mendeley==&lt;br /&gt;
&lt;br /&gt;
William Gunn, Mendeley william.gunn@mendeley.com (@mrgunn)&lt;br /&gt;
&lt;br /&gt;
This is partly a tool talk and partly a big idea one.&lt;br /&gt;
&lt;br /&gt;
Mendeley has built the world's largest open database of research and we've now begun to collect some interesting social metadata around the document metadata. I would like to share with the Code4Lib attendees information about using this resource to do things within your application that have previously been impossible for the library community, or in some cases impossible without expensive database subscriptions. One thing that's now possible is to augment catalog search by surfacing information about content usage, allowing people to not only find things matching a query, but popular things or things read by their colleagues. In addition to augmenting search, you can also use this information to augment discovery. Imagine an online exhibit of artifacts from a newly discovered dig not just linking to papers which discuss the artifact, but linking to really good interesting papers about the place and the people who made the artifacts. So the big idea is, &amp;quot;How will looking at the literature from a broader perspective than simple citation analysis change how research is done and communicated? How can we build tools that make this process easier and faster?&amp;quot; I can show some examples of applications that have been built using the Mendeley and PLoS APIs to begin to address this question, and I can also present results from Mendeley's developer challenge which shows what kinds of applications researchers are looking for, what kind of applications peope are building, and illustrates some interesting places where the two don't overlap.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Your UI can make or break the application (to the user, anyway)==&lt;br /&gt;
&lt;br /&gt;
* Robin Schaaf, University of Notre Dame, schaaf.4@nd.edu&lt;br /&gt;
&lt;br /&gt;
UI development is hard and too often ends up as an after-thought to computer programmers - if you were a CS major in college I'll bet you didn't have many, if any, design courses.  I'll talk about how to involve the users upfront with design and some common pitfalls of this approach.  I'll also make a case for why you should do the screen design before a single line of code is written.  And I'll throw in some ideas for increasing usability and attractiveness of your web applications.  I'd like to make a case study of the UI development of our open source ERMS.&lt;br /&gt;
&lt;br /&gt;
==Why Nobody Knows How Big The Library Really Is - Perspective of a Library Outside Turned Insider==&lt;br /&gt;
&lt;br /&gt;
* Patrick Berry, California State University, Chico, pberry@csuchico.edu&lt;br /&gt;
&lt;br /&gt;
In this talk I would like to bring the perspective of an &amp;quot;outsider&amp;quot; (although an avowed IT insider) to let you know that people don't understand the full scope of the library.  As we &amp;quot;rethink education&amp;quot;, it is incumbent upon us to help educate our institutions as to the scope of the library.  I will present some of the tactics I'm employing to help people outside, and in some cases inside, the library to understand our size and the value we bring to the institution.&lt;br /&gt;
&lt;br /&gt;
==Building a URL Management Module using the Concrete5 Package Architecture==&lt;br /&gt;
&lt;br /&gt;
* David Uspal, Villanova University, david.uspal@villanova.edu&lt;br /&gt;
&lt;br /&gt;
Keeping track of URLs utilized across a large website such as a university library, and keeping that content up to date for subject and course guides, can be a pain, and as an open source shop, we’d like to have open source solution for this issue.  For this talk, I intend to detail our solution to this issue by walking step-by-step through the building process for our URL Management module -- including why a new solution was necessary; a quick rundown of our CMS ([http://www.concrete5.org Concrete5], a CMS that isn’t Drupal); utilizing the Concrete5 APIs to isolate our solution from core code (to avoid complications caused by core updates); how our solution was integrated into the CMS architecture for easy installation; and our future plans on the project.&lt;br /&gt;
&lt;br /&gt;
==Building an NCIP connector to OpenSRF to facilitate resource sharing==&lt;br /&gt;
&lt;br /&gt;
* Jon Scott, Lyrasis, jon_scott@wsu.edu and Kyle Banerjee, Orbis Cascade Alliance, banerjek@uoregon.edu &lt;br /&gt;
&lt;br /&gt;
How do you reverse engineer any protocol to provide a new service? Humans (and worse yet, committees) often design verbose protocols built around use cases that don't line up current reality. To compound difficulties, the contents of protocol containers are not sufficiently defined/predictable and the only assistance available is sketchy documentation and kind individuals on the internet willing to share what they learned via trial by fire.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NCIP (Niso Circulation Interchange Protocol) is an open standard that defines a set of messages to support exchange of circulation data between disparate circulation, interlibrary loan, and related applications -- widespread adoption of NCIP would eliminate huge amounts of duplicate processing in separate systems. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This presentation discusses how we learned enough about NCIP and OpenSRF from scratch to build an NCIP responder for Evergreen to facilitate resource sharing in a large consortium that relies on over 20 different ILSes.&lt;br /&gt;
&lt;br /&gt;
==Practical Agile: What's Working for Stanford, Blacklight, and Hydra==&lt;br /&gt;
&lt;br /&gt;
* Naomi Dushay, Stanford University Libraries, ndushay@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Agile development techniques can be difficult to adopt in the context of library software development.  Maybe your shop has only one or two developers, or you always have too many simultaneous projects.   Maybe your new projects can’t be started until 27 librarians reach consensus on the specifications.&lt;br /&gt;
&lt;br /&gt;
This talk will present successful Agile- and Silicon-Valley-inspired practices we’ve adopted at Stanford and/or in the Blacklight and Hydra projects.  We’ve targeted developer happiness as well as improved productivity with our recent changes.  User stories, dead week, sight lines … it’ll be a grab bag of goodies to bring back to your institution, including some ideas on how to adopt these practices without overt management buy in.&lt;br /&gt;
&lt;br /&gt;
==Quick and &amp;lt;strike&amp;gt;Dirty&amp;lt;/strike&amp;gt; Clean Usability: Rapid Prototyping with Bootstrap==&lt;br /&gt;
&lt;br /&gt;
* Shaun Ellis, Princeton University Libraries, shaune@princeton.edu &lt;br /&gt;
&lt;br /&gt;
''&amp;quot;The code itself is unimportant; a project is only as useful as people actually find it.&amp;quot;  - Linus Torvalds'' [http://bit.ly/p4uuyy]&lt;br /&gt;
&lt;br /&gt;
Usability has been a buzzword for some time now, but what is the process for making the the transition toward a better user experience, and hence, better designed library sites?  I will discuss the one facet of the process my team is using to redesign the Finding Aids site for Princeton University Libraries (still in development).  The approach involves the use of rapid prototyping, with Bootstrap [http://twitter.github.com/bootstrap/], to make sure we are on track with what users and stakeholders expect up front, and throughout the development process.&lt;br /&gt;
&lt;br /&gt;
Because Bootstrap allows for early and iterative user feedback, it is more effective than the historic Photoshop mockups/wireframe technique.  The Photoshop approach allows stakeholders to test the look, but not the feel -- and often leaves developers scratching their heads.  Being a CSS/HTML/Javascript grid-based framework, Bootstrap makes it easy for anyone with a bit of HTML/CSS chops to quickly build slick, interactive prototypes right in the browser -- tangible solutions which can be shared, evaluated, revised, and followed by all stakeholders (see Minimum Viable Products [http://en.wikipedia.org/wiki/Minimum_viable_product]).  Efficiency is multiplied because the customized prototypes can flow directly into production use, as is the goal with iterative development approaches, such as the Agile methodology.&lt;br /&gt;
&lt;br /&gt;
While Bootstrap is not the only framework that offers grid-based layout, development is expedited and usability is enhanced by Bootstraps use of of &amp;quot;prefabbed&amp;quot; conventional UI patterns, clean typography, and lean Javascript for interactivity.   Furthermore, out-of-the box Bootstrap comes in a fairly neutral palette, so focus remains on usability, and does not devolve into premature discussions of color or branding choices.  Finally, using Less can be a powerful tool in conjunction with Bootstrap, but is not necessary.  I will discuss the pros and cons, and offer examples for how to getting up and running with or without Less.&lt;br /&gt;
&lt;br /&gt;
==Search Engine Relevancy Tuning - A Static Rank Framework for Solr/Lucene==&lt;br /&gt;
&lt;br /&gt;
* Mike Schultz, Amazon.com (formerly Summon Search Architect) mike.schultz@gmail.com&lt;br /&gt;
&lt;br /&gt;
Solr/Lucene provides a lot of flexibility for adjusting relevancy scoring and improving search results.  Roughly speaking there are two areas of concern: Firstly, a 'dynamic rank' calculation that is a function of the user query and document text fields.  And secondly, a 'static rank' which is independent of the query and generally is a function of non-text document metadata.  In this talk I will outline an easily understood, hand-tunable static rank system with a minimal number of parameters.&lt;br /&gt;
&lt;br /&gt;
The obvious major feature of a search engine is to return results relevant to a user query.  Perhaps less obvious is the huge role query independent document features play in achieving that. Google's PageRank is an example of a static ranking of web pages based on links and other secret sauce.  In the Summon service, our 800 million documents have features like publication date, document type, citation count and Boolean features like the-article-is-peer-reviewed.  These fields aren't textual and remain 'static' from query to query, but need to influence a document's relevancy score.  In our search results, with all query related features being equal, we'd rather have more recent documents above older ones, Journals above Newspapers, and articles that are peer reviewed above those that are not. The static rank system I will describe achieves this and has the following features:&lt;br /&gt;
&lt;br /&gt;
* Query-time only calculation - nothing is baked into the index - with parameters adjustable at query time.&lt;br /&gt;
* The system is based on a signal metaphor where components are 'wired' together.  System components allow multiplexing, amplifying, summing, tunable band-pass filtering, string-to-value-mapping all with a bare minimum of parameters.&lt;br /&gt;
* An intuitive approach for mixing dynamic and static rank that is more effective than simple adding or multiplying.&lt;br /&gt;
* A way of equating disparate static metadata types that leads to understandable results ordering.&lt;br /&gt;
&lt;br /&gt;
==Submitting Digitized Book-like things to the Internet Archive==&lt;br /&gt;
&lt;br /&gt;
* Joel Richard, Smithsonian Institution Libraries, richardjm@si.edu&lt;br /&gt;
&lt;br /&gt;
The Smithsonian Libraries has submitted thousands of out-of-copyright items to the Internet Archive over the years. Specifically in relation to the Biodiversity Heritage Library, we have developed an in-house boutique scanning and upload process that became a learning experience in automated uploading to the Archive. As part of the software development, we created a whitepaper that details the combined learning experiences of the Smithsonian Libraries and the Missouri Botanical Garden. We will discuss some of the the contents of this whitepaper in the context of our scanning process and the manner in which we upload items to the Archive. &lt;br /&gt;
&lt;br /&gt;
Our talk will include a discussion of the types of files and their formats used by the Archive, processes that the Archive performs on uploaded items, ways of interacting and affecting those processes, potential pitfalls and solutions that you may encounter when uploading, and tools that the Archive provides to help monitor and manage your uploaded documents. &lt;br /&gt;
&lt;br /&gt;
Finally, we'll wrap up with a brief summary of how to use things that are on the Internet Archive in your own websites.&lt;br /&gt;
&lt;br /&gt;
== So... you think you want to Host a Code4Lib National Conference, do you? ==&lt;br /&gt;
&lt;br /&gt;
* Elizabeth Duell, Orbis Cascade Alliance, eduell@uoregon.edu&lt;br /&gt;
&lt;br /&gt;
Are you interested in hosting your own Code4Lib Conference? Do you know what it would take? What does BEO stands for? What does F&amp;amp;B Minimum mean? Who would you talk to for support/mentoring? There are so many things to think about: internet support, venue size, rooming blocks, contracts, dietary restrictions and coffee (can't forget the coffee!) just to name a few. Putting together a conference of any size can look daunting, so let's take the scary out of it and replace it with a can do attitude!&lt;br /&gt;
&lt;br /&gt;
Be a step ahead of the game by learning from the people behind the curtain. Ask questions and be given templates/ cheat sheets! &lt;br /&gt;
&lt;br /&gt;
== HTML5 Microdata and Schema.org ==&lt;br /&gt;
 &lt;br /&gt;
* Jason Ronallo, North Carolina State University Libraries, jason_ronallo@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
When the big search engines announced support for HTML5 microdata and the schema.org vocabularies, the balance of power for semantic markup in HTML shifted. &lt;br /&gt;
* What is microdata? &lt;br /&gt;
* Where does microdata fit with regards to other approaches like RDFa and microformats? &lt;br /&gt;
* Where do libraries stand in the worldview of Schema.org and what can they do about it? &lt;br /&gt;
* How can implementing microdata and schema.org optimize your sites for search engines?&lt;br /&gt;
* What tools are available?&lt;br /&gt;
&lt;br /&gt;
== Stack View: A Library Browsing Tool ==&lt;br /&gt;
 &lt;br /&gt;
* Annie Cain, Harvard Library Innovation Lab, acain@law.harvard.edu&lt;br /&gt;
* Jeff Goldenson, Harvard Library Innovation Lab, jgoldenson@law.harvard.edu&lt;br /&gt;
&lt;br /&gt;
In an effort to recreate and build upon the traditional method of browsing a physical library, we used catalog data, including dimensions and page count, to create a [http://librarylab.law.harvard.edu/projects/stackview/ virtual shelf].&lt;br /&gt;
&lt;br /&gt;
This CSS and JavaScript backed visualization allows items to sit on any number of different shelves, really taking advantage of its digital nature.  See how we built Stack View on top of our data and learn how you can create shelves of your own using our open source code.&lt;br /&gt;
&lt;br /&gt;
== “Linked-Data-Ready” Software for Libraries ==&lt;br /&gt;
&lt;br /&gt;
* Jennifer Bowen, University of Rochester River Campus Libraries, jbowen@library.rochester.edu&lt;br /&gt;
&lt;br /&gt;
Linked data is poised to replace MARC as the basis for the new library bibliographic framework.  For libraries to benefit from linked data, they must learn about it, experiment with it, demonstrate its usefulness, and take a leadership role in its deployment. &lt;br /&gt;
&lt;br /&gt;
The eXtensible Catalog Organization (XCO) offers open-source software for libraries that is “linked-data-ready.” XC software prepares MARC and Dublin Core metadata for exposure to the semantic web, incorporating FRBR Group 1 entities and registered vocabularies for RDA elements and roles. This presentation will include a software demonstration, proposed software architecture for creation and management of linked data, a vision for how libraries can migrate from MARC to linked data, and an update on XCO progress toward linked data goals.&lt;br /&gt;
&lt;br /&gt;
== How people search the library from a single search box ==&lt;br /&gt;
&lt;br /&gt;
* Cory Lown, NCSU Libraries, cory_lown@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Searching the library is complex. There's the catalog, article databases, journal title and database title look-ups, the library website, finding aids, knowledge bases, etc. How would users search if they could get to all of these resources from a single search box? I'll share what we've learned about single search at NCSU Libraries by tracking use of QuickSearch (http://www.lib.ncsu.edu/search/index.php?q=aerospace+engineering), our home-grown unified search application. As part of this talk I will suggest low-cost ways to collect real world use data that can be applied to improve search. I will try to convince you that data collection must be carefully planned and designed to be an effective tool to help you understand what your users are telling you through their behavior. I will talk about how the fragmented library resource environment challenges us to provide useful and understandable search environments. Finally, I will share findings from analyzing millions of user transactions about how people search the library from a production single search box at a large university library.&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Cwlown</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2011_Lightning_Talks_Signup&amp;diff=7530</id>
		<title>2011 Lightning Talks Signup</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2011_Lightning_Talks_Signup&amp;diff=7530"/>
				<updated>2011-02-10T16:20:18Z</updated>
		
		<summary type="html">&lt;p&gt;Cwlown: /* Wednesday, 3:50-5pm, Alumni Hall [14 slots] */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Sign up for Lightning Talks Now!!'''&lt;br /&gt;
&lt;br /&gt;
Lightning talks are scheduled on all three days of the conference. A lightning talk is a fast-paced 5 minute talk on a topic of your choosing.&lt;br /&gt;
&lt;br /&gt;
Mark Jason Dominus has a nice page [http://perl.plover.com/lt/lightning-talks.html about lightning talks], which includes this summary of why you might want to do one:&lt;br /&gt;
&lt;br /&gt;
Maybe you've never given a talk before, and you'd like to start small. For a Lightning Talk, you don't need to make slides, and if you do decide to make slides, you only need to make three.&lt;br /&gt;
&lt;br /&gt;
Maybe you're nervous and you're afraid you'll mess up. It's a lot easier to plan and deliver a five minute talk than it is to deliver a long talk. And if you do mess up, at least the painful part will be over quickly.&lt;br /&gt;
&lt;br /&gt;
Maybe you don't have much to say. Maybe you just want to ask a question, or invite people to help you with your project, or boast about something you did, or tell a short cautionary story. These things are all interesting and worth talking about, but there might not be enough to say about them to fill up thirty minutes.&lt;br /&gt;
&lt;br /&gt;
You might also like Mark Fowler's's [http://www.perl.com/pub/2004/07/30/lightningtalk.html Advice for Giving a Lightning Talk]&lt;br /&gt;
&lt;br /&gt;
Note to presenters: Projector resolution is 1024x768&lt;br /&gt;
&lt;br /&gt;
=== Tuesday, 4-5pm, Alumni Hall [12 slots] ===&lt;br /&gt;
&lt;br /&gt;
(changed to actual order)&lt;br /&gt;
&lt;br /&gt;
# [http://robotlibrarian.billdueber.com/code4lib-2011-lightning-talk-slides/ 5 minutes of OPAC stats that might surprise you, or maybe not]. -- Bill Dueber&lt;br /&gt;
# [http://socialarchive.iath.virginia.edu/ Social Networks and Archival Context] [http://socialarchive.iath.virginia.edu/xtf/search Prototype] [http://btingle.bitbucket.org/c4l11/ slides]- Brian Tingle&lt;br /&gt;
# AjaxyDialog jquery-ui widget jonathan rochkind&lt;br /&gt;
# 2 little EAD gems - Jason Ronallo&lt;br /&gt;
# LYRASIS' Open Source Software Efforts - [[User:DataGazetteer|Peter Murray]]&lt;br /&gt;
# UC San Diego Mobile Apps - Esme Cowles&lt;br /&gt;
# Blacklight and Hydra at the Rock and Roll Hall of Fame - Adam Wead&lt;br /&gt;
# [http://www.hathitrust.org/blogs HathiTrust Large Scale Search] update.  - Tom Burton-West&lt;br /&gt;
# Open data and the Biodiversity Heritage Library experience - Trish Rose-Sandler&lt;br /&gt;
# [http://iss.ndl.go.jp/?locale=en NDL Search] [http://www.slideshare.net/nabeta/ndl-search-beta-6856823 slides] - Kosuke Tanabe&lt;br /&gt;
# Making integrated search system which your choice - primo central index or summon? - Takanori Hayashi&lt;br /&gt;
&lt;br /&gt;
=== Wednesday, 3:50-5pm, Alumni Hall [14 slots] ===&lt;br /&gt;
&lt;br /&gt;
(changed to actual order)&lt;br /&gt;
&lt;br /&gt;
# Edward Corrado - EPrints (was: Small Scale Koha)&lt;br /&gt;
# [http://www.slideshare.net/villadsen/summasummon-something-something Summa/Summon: Something, something] (merging search results) - Mads Villadsen, Toke Eskildsen&lt;br /&gt;
# Tracy Seneca. (Web) Archiving the oil spill – UI changes driven by context&lt;br /&gt;
# Andreas Orphanides - User interaction patterns on a touch-screen kiosk [https://docs.google.com/present/edit?id=0Acqxz6BpsdaqZGZxMjM5cHhfMzNkamRrNDM3cA&amp;amp;hl=en (Slides)]&lt;br /&gt;
# Haruki Ono - Two Engineering Projects of LIS at Tsukuba in Japan: [http://www.shizuku.ne.jp/ Project Shizuku] and [http://ustream.tv/channel/l1gp Project Lie] ([http://slidesha.re/fF7HNj Slides])&lt;br /&gt;
# Stephen Meyer - Better Subject Browsing &lt;br /&gt;
# Cory Lown - Mobile Web Apps for Library Exhibits - [http://www.lib.ncsu.edu/m/exhibits/4h/ Exhibit Page] - [http://www.lib.ncsu.edu/dli/projects/mobileexhibits/ Project Page] - ([http://www.slideshare.net/corylown/mobile-web-apps-for-library-exhibits Slides])&lt;br /&gt;
# Eric Lease Morgan - Beyond full-text indexing in &amp;quot;next-generation&amp;quot; library catalogs&lt;br /&gt;
# Theodor Tolstoy - Experiences from implementing Ebsco Discovery Service through their Web Service.&lt;br /&gt;
# [http://www.abes.fr/abes/documents/tef/recommandation/index.html French Electronic Theses] : having oracle &amp;amp; solr working together. Aurélien Charot, [http://www.abes.fr ABES]&lt;br /&gt;
# [http://www.abes.fr/abes/documents/tef/recommandation/index.html French Electronic Theses] : edit an xml into a form. Olivier Martinez, [http://www.abes.fr ABES]&lt;br /&gt;
# Hillel Arnold - [http://dlibdev.nyu.edu/tamimentapa Asian/Pacific American Documentary Heritage Archives Survey]&lt;br /&gt;
# Ryan Eby - Does anyone else hate this shit? (metadata and what not)&lt;br /&gt;
# Bess Sadler - let's build a code4lib curriculum [[A Guide for the Perplexed]]&lt;br /&gt;
&lt;br /&gt;
=== Thursday, 10:15-11:00, Alumni Hall [9 slots] ===&lt;br /&gt;
# Alex Berry - Scherzo, a FRBR based music search tool&lt;br /&gt;
# Shian Chang - Build Mobile Library on Drupal with Library Website&lt;br /&gt;
# David Uspal - Generating a Sitemap from a Solr Index&lt;br /&gt;
# Chick Markley - Your next language&lt;br /&gt;
# Ranti Junus - Something that web designer/developer would need to consider&lt;br /&gt;
# Dot Porter - Text Image Linking Environment, an editing tool for scholars&lt;br /&gt;
# Andrea Schurr - Freshmen, Zombies, and Libraries&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
[9 slots only]&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2011]]&lt;/div&gt;</summary>
		<author><name>Cwlown</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2011_Lightning_Talks_Signup&amp;diff=7526</id>
		<title>2011 Lightning Talks Signup</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2011_Lightning_Talks_Signup&amp;diff=7526"/>
				<updated>2011-02-10T15:01:54Z</updated>
		
		<summary type="html">&lt;p&gt;Cwlown: /* Wednesday, 3:50-5pm, Alumni Hall [14 slots] */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Sign up for Lightning Talks Now!!'''&lt;br /&gt;
&lt;br /&gt;
Lightning talks are scheduled on all three days of the conference. A lightning talk is a fast-paced 5 minute talk on a topic of your choosing.&lt;br /&gt;
&lt;br /&gt;
Mark Jason Dominus has a nice page [http://perl.plover.com/lt/lightning-talks.html about lightning talks], which includes this summary of why you might want to do one:&lt;br /&gt;
&lt;br /&gt;
Maybe you've never given a talk before, and you'd like to start small. For a Lightning Talk, you don't need to make slides, and if you do decide to make slides, you only need to make three.&lt;br /&gt;
&lt;br /&gt;
Maybe you're nervous and you're afraid you'll mess up. It's a lot easier to plan and deliver a five minute talk than it is to deliver a long talk. And if you do mess up, at least the painful part will be over quickly.&lt;br /&gt;
&lt;br /&gt;
Maybe you don't have much to say. Maybe you just want to ask a question, or invite people to help you with your project, or boast about something you did, or tell a short cautionary story. These things are all interesting and worth talking about, but there might not be enough to say about them to fill up thirty minutes.&lt;br /&gt;
&lt;br /&gt;
You might also like Mark Fowler's's [http://www.perl.com/pub/2004/07/30/lightningtalk.html Advice for Giving a Lightning Talk]&lt;br /&gt;
&lt;br /&gt;
Note to presenters: Projector resolution is 1024x768&lt;br /&gt;
&lt;br /&gt;
=== Tuesday, 4-5pm, Alumni Hall [12 slots] ===&lt;br /&gt;
&lt;br /&gt;
(changed to actual order)&lt;br /&gt;
&lt;br /&gt;
# 5 minutes of OPAC stats that might surprise you, or maybe not. -- Bill Dueber&lt;br /&gt;
# [http://socialarchive.iath.virginia.edu/ Social Networks and Archival Context] [http://socialarchive.iath.virginia.edu/xtf/search Prototype] [http://btingle.bitbucket.org/c4l11/ slides]- Brian Tingle&lt;br /&gt;
# AjaxyDialog jquery-ui widget jonathan rochkind&lt;br /&gt;
# 2 little EAD gems - Jason Ronallo&lt;br /&gt;
# LYRASIS' Open Source Software Efforts - [[User:DataGazetteer|Peter Murray]]&lt;br /&gt;
# UC San Diego Mobile Apps - Esme Cowles&lt;br /&gt;
# Blacklight and Hydra at the Rock and Roll Hall of Fame - Adam Wead&lt;br /&gt;
# [http://www.hathitrust.org/blogs HathiTrust Large Scale Search] update.  - Tom Burton-West&lt;br /&gt;
# Open data and the Biodiversity Heritage Library experience - Trish Rose-Sandler&lt;br /&gt;
# [http://iss.ndl.go.jp/?locale=en NDL Search] [http://www.slideshare.net/nabeta/ndl-search-beta-6856823 slides] - Kosuke Tanabe&lt;br /&gt;
# Making integrated search system which your choice - primo central index or summon? - Takanori Hayashi&lt;br /&gt;
&lt;br /&gt;
=== Wednesday, 3:50-5pm, Alumni Hall [14 slots] ===&lt;br /&gt;
&lt;br /&gt;
(changed to actual order)&lt;br /&gt;
&lt;br /&gt;
# Edward Corrado - EPrints (was: Small Scale Koha)&lt;br /&gt;
# [http://www.slideshare.net/villadsen/summasummon-something-something Summa/Summon: Something, something] (merging search results) - Mads Villadsen, Toke Eskildsen&lt;br /&gt;
# Tracy Seneca. (Web) Archiving the oil spill – UI changes driven by context&lt;br /&gt;
# Andreas Orphanides - User interaction patterns on a touch-screen kiosk [https://docs.google.com/present/edit?id=0Acqxz6BpsdaqZGZxMjM5cHhfMzNkamRrNDM3cA&amp;amp;hl=en (Slides)]&lt;br /&gt;
# Haruki Ono - Two Engineering Projects of LIS at Tsukuba in Japan: [http://www.shizuku.ne.jp/ Project Shizuku] and [http://ustream.tv/channel/l1gp Project Lie] ([http://slidesha.re/fF7HNj Slides])&lt;br /&gt;
# Stephen Meyer - Better Subject Browsing &lt;br /&gt;
# Cory Lown - Mobile Web Apps for Library Exhibits - [http://www.lib.ncsu.edu/m/exhibits/4h/ Exhibit Page] - [http://www.lib.ncsu.edu/dli/projects/mobileexhibits/ Project Page] - (Slides)&lt;br /&gt;
# Eric Lease Morgan - Beyond full-text indexing in &amp;quot;next-generation&amp;quot; library catalogs&lt;br /&gt;
# Theodor Tolstoy - Experiences from implementing Ebsco Discovery Service through their Web Service.&lt;br /&gt;
# [http://www.abes.fr/abes/documents/tef/recommandation/index.html French Electronic Theses] : having oracle &amp;amp; solr working together. Aurélien Charot, [http://www.abes.fr ABES]&lt;br /&gt;
# [http://www.abes.fr/abes/documents/tef/recommandation/index.html French Electronic Theses] : edit an xml into a form. Olivier Martinez, [http://www.abes.fr ABES]&lt;br /&gt;
# Hillel Arnold - [http://dlibdev.nyu.edu/tamimentapa Asian/Pacific American Documentary Heritage Archives Survey]&lt;br /&gt;
# Ryan Eby - Does anyone else hate this shit? (metadata and what not)&lt;br /&gt;
# Bess Sadler - let's build a code4lib curriculum [[A Guide for the Perplexed]]&lt;br /&gt;
&lt;br /&gt;
=== Thursday, 10:15-11:00, Alumni Hall [9 slots] ===&lt;br /&gt;
# Alex Berry - Scherzo, a FRBR based music search tool&lt;br /&gt;
# Shian Chang - Build Mobile Library on Drupal with Library Website&lt;br /&gt;
# David Uspal - Generating a Sitemap from a Solr Index&lt;br /&gt;
# Chick Markley - Your next language&lt;br /&gt;
# Ranti Junus - Something that web designer/developer would need to consider&lt;br /&gt;
# Dot Porter - Text Image Linking Environment, an editing tool for scholars&lt;br /&gt;
# Andrea Schurr - Freshmen, Zombies, and Libraries&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
[9 slots only]&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2011]]&lt;/div&gt;</summary>
		<author><name>Cwlown</name></author>	</entry>

	</feed>