https://wiki.code4lib.org/api.php?action=feedcontributions&user=Ckang&feedformat=atomCode4Lib - User contributions [en]2024-03-29T06:01:00ZUser contributionsMediaWiki 1.26.2https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&diff=404642014 preconference proposals2014-03-04T17:15:30Z<p>Ckang: /* Obey the Testing Goat!: Test Driven Web Development From The Ground Up */</p>
<hr />
<div>= PROPOSALS ARE CLOSED : PLEASE DO NOT ADD NEW PRECONFERENCES TO THIS PAGE =<br />
<br />
Proposals were accepted through December 6th, 2013.<br />
<br />
It would be really, super duper helpful if folks who think they might want to attend a pre-conference could indicate interest by adding your name to a session below. <br />
<br />
<br />
===Note===<br />
Attendance at a pre-conference will require a small fee ''due at the time of conference registration".<br />
<br />
Although this was specified in the email announcements relating to pre-conferences, it was not added to this page until December 2nd. I (Adam C.) apologize for the omission and I hope this will not cause any "sticker shock." Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.<br />
<br />
Please put your pre-conference on the list in the following format:<br />
<br />
=Code4Lib 2014 Pre-Conference Proposals=<br />
<br />
===Drupal4lib Sub-con Barcamp===<br />
=====Full Day=====<br />
<br />
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com<br />
<br />
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.<br />
<br />
This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).<br />
<br />
[[resources to help you learn drupal]]<br />
<br />
====Interested in Attending:====<br />
<br />
=====All Day=====<br />
<br />
* Renna Tuten <br />
<br />
=====Morning=====<br />
<br />
* Kevin Reiss<br />
* Charlie Morris (NCSU) - glad to see this again this year!<br />
* Paula Gray-Overtoom<br />
* Laurie Lee Moses<br />
<br />
=====Afternoon=====<br />
<br />
&nbsp;<br />
<br />
----<br />
<br />
===Open Refine Hackfest===<br />
'''"Half-Day"'''<br />
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com<br />
<br />
[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control<br />
<br />
The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. <br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<ol><br />
<li>Adam Constabaris<br />
<li>Jason Stirnaman<br />
<li>Joshua Gomez<br />
<li>Sam Kome<br />
<li>Mike Beccaria<br />
<li>Angela Zoss<br />
<li>A. Soroka<br />
<li> Matt Zumwalt<br />
</ol><br />
----<br />
<br />
===Responsive Design Hackfest===<br />
'''"Half-Day [Afternoon]"''' <br />
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com<br />
* Contact David Ward, University of Illinois, dh-ward@illinois.edu<br />
<br />
This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. <br />
<br />
Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
----<br />
<br />
=== Intro to Blacklight ===<br />
'''"Half-Day [Morning]"''' <br />
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu<br />
* TA: Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
This session will be walk-through of the architecture of Blacklight, the community, and an introduction to building a Blacklight-based application. Each participant will have the opportunity to build a simple Blacklight application, and make basic customizations, while using a test-driven approach.<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Megan Kudzia<br />
# Bret Davidson<br />
# Coral Sheldon-Hess<br />
# Cory Lown<br />
# Emily Daly<br />
# Angela Zoss<br />
# Sean Aery<br />
# Francis Kayiwa<br />
# Heidi Frank<br />
# Junior Tidal<br />
# Ian Chan<br />
# Ted Lawless<br />
----<br />
<br />
===Blacklight Hackfest===<br />
'''"Half-Day [Afternoon]"''' <br />
* Contact Chris Beer, Stanford University, cabeer@stanford.edu<br />
<br />
This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Shaun Ellis<br />
# Kevin Reiss<br />
# Megan Kudzia<br />
# Erik Hatcher<br />
# Emily Daly<br />
# Laurie Lee Moses<br />
# Francis Kayiwa<br />
# Ted Lawless<br />
<br />
----<br />
<br />
===RailsBridge: Intro to programming in Ruby on Rails===<br />
'''"Half-Day" [morning]'''<br />
* Contact Justin Coyne, Data Curation Experts, justin@curationexperts.com<br />
<br />
Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! RailsBridge is a friendly place to get together and learn how to write some code.<br />
<br />
RailsBridge is a great workshop that opens the doors to projects like Blacklight and Hydra.<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
1. Ayla Stein<br />
<br />
2. Heidi Dowding<br />
<br />
3. Caitlin Christian-Lamb<br />
<br />
4. Scott Bacon<br />
<br />
5. [[User:RileyChilds | Riley Childs]]<br />
<br />
6. Carolina Garcia<br />
<br />
----<br />
<br />
===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===<br />
'''Full-Day'''<br />
<br />
Contact: <br />
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com<br />
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu<br />
<br />
This will be a full day session on project management. We'll cover<br />
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment<br />
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets<br />
* '''Executing the Project''' -- status meeting, status reports, issue management<br />
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product<br />
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Robin Dean<br />
# Erin White<br />
# Andrew Darby<br />
# Sam Kome<br />
# Ryan Scherle<br />
# Will Shaw<br />
# Liz Milewicz<br />
# Cynthia "Arty" Ng<br />
# Laurie Lee Moses (if I don't do the Hackfest for Blacklight)<br />
# Ranti Junus<br />
# Bohyun Kim (Afternoon)<br />
<br />
----<br />
<br />
===Fail4Lib 2014===<br />
'''Half Day [TBD, probably afternoon]'''<br />
<br />
Contacts: <br />
* Andreas Orphanides, akorphan (at) ncsu.edu<br />
* Jason Casden, jmcasden (at) ncsu.edu<br />
<br />
The task of design (and the work that we do as library coders) is intimately tied to failure. Failures, both big and small, motivate us to create and improve. Failures are also occasionally the result of our work. Understanding and embracing failure, encouraging enlightened risk-taking, and seeking out opportunities to fail and learn are essential to success in our field. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be feared.<br />
<br />
The schedule may include the following:<br />
<br />
* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?<br />
* Confessionals, for those willing to share. Talk about your own experiences with rough starts, labor pains, and doomed projects in your own work: What can we learn from our own (and each others') failures?<br />
* Group therapy. Let's talk about how to deal with risk management, failed projects, experimental endeavors, and more: How can we make ourselves, our colleagues, and our organizations more fault tolerant? How do we make sure we fail as productively as possible?<br />
<br />
''Interested in attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#Bret Davidson<br />
#Mike Graves<br />
#Jason Stirnaman<br />
#Julia Bauder<br />
#Linda Ballinger<br />
#Scott Hanrath<br />
#Caitlin Christian-Lamb<br />
#Ian Walls<br />
#Scott Bacon <br />
#mx matienzo<br />
#Chris Sharp<br />
#Junior Tidal<br />
#Julie Rudder<br />
----<br />
<br />
===CLLAM @ code4lib===<br />
'''(Computational Linguistics for Libraries, Archives and Museums)'''<br />
<br />
'''Full Day'''<br />
<br />
Contacts: <br />
* Douglas W. Oard (primary), oard (at) umd.edu <br />
* Corey Harper, corey (dot) harper (at) nyu.edu<br />
* Robert Sanderson, azaroth42 (at) gmail.com <br />
* Robert Warren, rwarren (at) math.carleton.ca<br />
<br />
We will hack at the intersection of diverse content from Libraries, Archives and Museums and bleeding edge tools from computational linguistics for slicing and dicing that content. Did you just acquire the email archives of a startup company? Maybe you can automatically build an org chart. Have you got metadata in a slew of languages? Perhaps you can search it all using one query. Is name authority control for e-resources getting too costly? Let’s see if entity linking techniques can help. These are just a few teasers. <br />
<br />
There’ll be plenty of content and tools supplied, but please bring your own [data] too -- you’ll hack with it in new ways throughout the day. We’ll get started with some lightning talks on what we’ve brought,then we’ll break up into groups to experiment and work on the ideas that appeal. Three guaranteed outcomes: you’ll walk away with new ideas, new tools, and new people you’ll have met.<br />
<br />
''Interested in attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Devon Smith<br />
# Kevin S. Clarke<br />
# Jason Stirnaman<br />
# Joshua Gomez<br />
# Carolina Garcia<br />
# Tom Burton-West<br />
# Dan Scott<br />
# Devin Higgins<br />
# Mark Breedlove<br />
----<br />
<br />
=== GeoHydra: Managing geospatial content ===<br />
<br />
'''Half-day [Afternoon]'''<br />
<br />
* Contact: Darren Hardy, Stanford University, drh@stanford.edu<br />
* Moderator: Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,<br />
etc., all of which you want to integrate into your digital repository? In this<br />
workshop, we will discuss how Hydra can provide discovery, delivery, and<br />
management services for geospatial assets, as well as solicit questions about<br />
your own GIS projects. We aim to help answer the following questions you might have about putting geospatial data into your Hydra-based digital library:<br />
<br />
* What are the types of geospatial data?<br />
* How to dive into Hydra?<br />
* How to model geospatial holdings with Hydra?<br />
* How to discover and view geospatial data?<br />
* How to build a geospatial data infrastructure?<br />
* What are common approaches and problems?<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Esmé Cowles<br />
# David Drexler<br />
----<br />
<br />
===Technology, Librarianship, and Gender: Moving the conversation forward===<br />
'''Full Day'''<br />
<br />
Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]<br />
<br />
'''Description'''<br />
<br />
Librarianship is largely made up of women, yet women are significantly underrepresented in tech positions, on any level, within libraries themselves. Why? What are we doing to encourage women to become more involved in STEM within librarianship? What kind of message are we sending when library technology keynotes remain almost resolutely male? How are we changing the face of technology, not only within libraries, but with the field itself? How are we training our staff and colleagues in the areas of fairness and removal of bias? Our vendors?<br />
<br />
Lots of tough questions.<br />
<br />
While the conversation has been going on via various blogs and articles within the last few years, it was given a public face at [http://infotoday.com/il2013/day.asp?day=Monday#session_D105 Internet Librarian 2013] where a panel of 7 (four women, three men) gave personal experiences on the above and then opened up the conversation to the audience. As eye opening and enriching the conversation was, a 45 minute panel was not enough. One thing remains clear: We need to keep the conversation moving forward and start making some radical changes in the way we think, act, and how we need to harness this to start making real changes within librarianship itself.<br />
<br />
Topics to include: Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems, mentoring, ally support, and more<br />
<br />
Those attending should expect: Begin with opening up the conversation of experiences and talking about what is most needed, spending remaining time putting together live, usable solutions to start implementing as well as pushing the conversation forward at local levels<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
=====All Day=====<br />
1. Kate Kosturski<br />
<br />
2. Valerie Aurora<br />
<br />
3. Declan Fleming (I'd be good with a half day too)<br />
<br />
4. mx matienzo (likewise ok w/ half day)<br />
<br />
5. Ginny Boyer (I'd be good with a half day too)<br />
<br />
=====Morning=====<br />
1. Shaun Ellis<br />
<br />
2. Jason Casden<br />
<br />
3. Bohyun Kim<br />
<br />
=====Afternoon=====<br />
1. Ayla Stein<br />
<br />
2. Heidi Dowding<br />
<br />
3. Coral Sheldon-Hess<br />
<br />
4. Cory Lown<br />
----<br />
<br />
===FileAnalyzer: Rapid Development of File Manipulation Tasks===<br />
'''"Half-Day" [morning]'''<br />
* Contact Terry Brady, twb27@georgetown.edu<br />
<br />
The FileAnalyzer (http://georgetown-university-libraries.github.io/File-Analyzer/) is an application designed to solve a number of library automation challenges:<br />
<br />
* validating digitized and reformatted files<br />
* validating vendor statistics for counter compliance<br />
* preparing collections of digital files for archiving and ingest<br />
* manipulating ILS import and export files<br />
<br />
The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census. After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform. Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.<br />
<br />
The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules. As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.<br />
<br />
The first half of this session will be targeted to potential users and developers. The second half of the session will be targeted towards developers who are interested in developing custom rules for the application.<br />
<br />
''Session Overview''<br />
* Overview of the application<br />
* Running sample file tests/transformations through the application<br />
* Compiling and building the application<br />
* Coding a custom file processing task<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Michael Doran<br />
----<br />
<br />
===Collecting social media data with Social Feed Manager===<br />
'''Half-Day [Morning]'''<br />
<br />
Contacts: <br />
* Dan Chudnov, GW Libraries, dchud (at) gwu.edu<br />
* Dan Kerchner, GW Libraries, kerchner (at) gwu.edu<br />
* Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu<br />
<br />
Social media data is a popular material for research and a new format for building collections. What does it take to collect meaningfully from Twitter, Tumblr, YouTube, Weibo, Facebook, and other sites? We will:<br />
* Introduce options for collections, including both high- and low-end commercial offerings. Discuss what it means to collect these resources, covering boundaries, policies, and workflows required to develop a social media collection program in your institution.<br />
* Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them<br />
* Help you get started using the free [http://gwu-libraries.github.io/social-feed-manager Social Feed Manager] (SFM) app we're developing at GW to create your first collections. We’ll demo its use and demo a clean install (those w/environments can follow along)<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Declan Fleming<br />
# Esmé Cowles<br />
# Jason Stirnaman<br />
# Liz Milewicz<br />
# Ranti Junus<br />
<br />
----<br />
<br />
=== Intro to Git ===<br />
'''"Half-Day [tbd - probably afternoon]"''' <br />
* Contact: Erin Fahy, Stanford University, efahy at stanford.edu<br />
* TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu<br />
<br />
This session will cover the fundamentals of git by discussing/going through (time allowing):<br />
* what is a distributed version control system<br />
* what is git and github<br />
* initializing a repo on a remote server/github<br />
* cloning an existing repo<br />
* creating a branch<br />
* contributing code to a repo<br />
* how to handle merge conflicts<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Sam Kome<br />
# Paula Gray-Overtoom<br />
# Liz Milewicz<br />
# Michael Doran<br />
# Caitlin Christian-Lamb<br />
# [[User:RileyChilds|Riley Childs]]<br />
----<br />
<br />
=== Archival discovery and use ===<br />
'''Full Day''' <br />
<br />
Contacts: <br />
* Tim Shearer, UNC Chapel Hill, tshearer at email.unc.edu, <br />
* Will Sexton, Duke, will.sexton at duke.edu<br />
<br />
This is a full day pre-conference about archival collections and will cover the intersections of archives, workflows, technologies, discovery, and use.<br />
<br />
Morning agenda: focused talks around (but not limited to) issues such as:<br />
* Crowd-sourcing description to enhance collecitons<br />
* Linked data and authority<br />
* Mass digitization and sustainable workflows<br />
* Digitized objects in context (images and other objects in finding aids)<br />
* Too many cooks in the kitchen: versioning<br />
* Global-, intra-, and inter- discovery of archival materials via finding aids <br />
* and more...<br />
<br />
Afternoon agenda: Focused talks around specific tools followed by general discussion, connections, opportunities, aspirations, and planning.<br />
<br />
Tool examples:<br />
* Archivespace<br />
* STEADy<br />
* "RAMP" (Remixing Archival Metadata Project)<br />
* OpenRefine<br />
* Aeon<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
Morning:<br />
* Julia Bauder<br />
<br />
Afternoon:<br />
* your name<br />
<br />
All day:<br />
<br />
# Josh Wilson<br />
# Sam Kome<br />
# Linda Ballinger<br />
# Caitlin Christian-Lamb<br />
# Laurie Lee Moses (seriously hard to decide here!)<br />
# David Bass<br />
# John Rees<br />
# Lynn Eaton<br />
# Hillel Arnold<br />
# Susan Ivey<br />
# Kristen Merryman<br />
----<br />
<br />
===AV Content Slam===<br />
'''Half-Day [morning]'''<br />
Contacts:<br />
* Kara Van Malssen, kara (at) avpreserve.com<br />
* Lauren Sorenson, laurens (at) bavc.org<br />
* Steven Villereal , villereal (at) gmail.com<br />
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.<br />
Possible topics of discussion might include:<br />
* Use of format id and characterization/metadata extraction tools for AV<br />
* Creating and using time-based metadata<br />
* Managing (moving, fixity checking, etc) massive files (like uncompressed video)<br />
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] .<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:<br />
<br />
# A. Soroka<br />
<br />
----<br />
<br />
===OCLC Web Services Hackfest===<br />
<br />
"Half-Day" [afternoon]<br />
<br />
Contact: Shelley Hostetler, Community Manager, Developer Network hostetls[at]oclc.org<br />
<br />
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.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:<br />
<br />
<br />
----<br />
<br />
<br />
===Obey the Testing Goat!: Test Driven Web Development From The Ground Up===<br />
'''Half-Day [tbd - probably afternoon]'''<br />
* Contact [[User:Mredar|Mark Redar]], mredar[at]gmail.com<br />
<br />
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.<br />
<br />
In this session, we will follow the excellent book [http://shop.oreilly.com/product/0636920029533.do "Test-Driven Web Development with Python"] 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.<br />
<br />
By the end of this session, you should be able to [http://www.obeythetestinggoat.com/ "Obey the Testing Goat"] from the start to finish for your next project.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:<br />
<br />
# Charlie Morris (NCSU)<br />
# Jason Stirnaman<br />
# Joshua Gomez<br />
# Liz Milewicz<br />
# Scott Hanrath<br />
# Mike Beccaria<br />
# Sean Aery<br />
# Carolina Garcia<br />
# Heidi Frank<br />
# Chung Kang<br />
----<br />
<br />
===Summon Hackfest ===<br />
<br />
Presenter: Eddie Newwirth and presenters from Summon libraries<br />
Contact: Scott Schuetze (first DOT last @ serialssolutions. com)<br />
<br />
The Summon Hackfest (10:30am-12pm) will be a great opportunity for libraries using the Summon service to talk about improving discovery of resources, share their creative customizations and code, and exchange ideas about ways they can leverage the Summon API to better meet the needs of their users.<br />
<br />
The Summon Hackfest is open to all libraries currently using ProQuest discovery and management services (Intota, Summon, Ulrich’s or the 360 suite of services), whether they are attending Code4Lib or are just in the area.<br />
<br />
----<br />
<br />
[[:Category:Code4Lib2014]]</div>Ckanghttps://wiki.code4lib.org/index.php?title=2013_preconference_proposals&diff=291742013 preconference proposals2012-12-05T22:50:14Z<p>Ckang: /* Intro to Blacklight */</p>
<hr />
<div>Proposals '''now closed'''.<br />
<br />
Spaces available: 4+ Rooms<br />
<br />
Please follow the formatting guidelines:<br />
<pre><br />
=== Talk Title ===<br />
<br />
* Presenter/Leader, affiliation (optional), and email address (mandatory!)<br />
* Second Presenter/Leader, affiliation, email address, if applicable<br />
<br />
Description.<br />
</pre><br />
<br />
==Full Day==<br />
<br />
===Drupal4lib Sub-con Barcamp===<br />
<br />
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or <br />
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu<br />
<br />
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.<br />
<br />
If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.<br />
<br />
Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.<br />
<br />
'''I plan on attending:'''<br />
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)<br />
* Christina Salazar (afternoon only)<br />
<br />
==Half Day Morning==<br />
=== Open space session ===<br />
<br />
* Dan Chudnov, dchud at gwu edu<br />
<br />
The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.<br />
<br />
If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.<br />
<br />
'''I plan on attending:'''<br />
* Devon Smith<br />
* First and last name<br />
* Esmé Cowles<br />
* Jason Casden<br />
<br />
=== Delivery services ===<br />
* Ted Lawless, Brown University Library, tlawless at brown edu. <br />
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.<br />
<br />
Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands. <br />
<br />
Possible topics/activities include:<br />
* panel discussion of what some libraries have done in this area<br />
* comparisons of different approaches to addressing delivery <br />
* overview of tools available <br />
* sharing of strategies and experiences<br />
* time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/py360link Py360 Link]. <br />
<br />
Resources and background information:<br />
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway] <br />
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]<br />
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]<br />
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
=== Intro to Blacklight ===<br />
* Bess Sadler, Stanford University Library (bess at stanford.edu)<br />
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)<br />
<br />
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter. <br />
<br />
Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.<br />
<br />
'''I plan on attending:'''<br />
* Linda Ballinger<br />
* Terry Brady<br />
* First and last name<br />
<br />
=== RailsBridge Intro to Ruby on Rails ===<br />
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu<br />
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br />
* Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu<br />
* Ross Singer, Talis, rossfsinger@gmail.com<br />
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org<br />
* Anyone else want to come and help folks? Contact Jason.<br />
<br />
RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language, the Rails framework, and version control with git. Participants will build a working Rails application. <br />
<br />
There will be some pre-preconference preparation needed so that we can effectively use our time. Details to come.<br />
<br />
* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Shawn Kiewel<br />
* Jon Stroop<br />
* Christina Salazar<br />
* Karen Coombs - coombsk{at}oclc{dot}org<br />
* Becky Yoose<br />
* Jeremy Morse<br />
* Julia Bauder<br />
* Chung Kang<br />
* Karen Miller<br />
* Betsy Coles<br />
<br />
===Intro to NoSQL Databases===<br />
* Joshua Gomez, George Washington University, jngomez at gwu edu<br />
<br />
Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called "Big Data" problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, CouchDB, and Neo4j.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Esha Datta<br />
* Trevor Thornton<br />
* Michael Doran<br />
* Ray Schwartz<br />
* Kevin Clarke<br />
* Andreas Orphanides<br />
* Tommy Ingulfsen<br />
<br />
==Half Day Afternoon==<br />
=== Data Visualization Hackfest ===<br />
* Chris Beer, cabeer at stanford.edu<br />
* Dan Chudnov, dchud at gwu edu<br />
<br />
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly: <br />
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.<br />
- we'll separate into groups and hack on stuff.<br />
- at the end of the day, we'll present our progress.<br />
<br />
Not a code hacker? No worries; all skill sets and backgrounds are valuable! <br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Devon Smith<br />
* Esha Datta<br />
* Ray Schwartz<br />
* Karen Coombs - coombsk{at}oclc{dot}org<br />
* Julia Bauder<br />
* Jason Stirnaman (jstirnaman at kumc.edu)<br />
<br />
=== Intro to Hydra ===<br />
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)<br />
* Mike Giarlo, Penn State Information Technology Services (michael at psu.edu)<br />
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br />
<br />
Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame. <br />
<br />
'''I plan on attending:'''<br />
* Jeremy Prevost<br />
* Dennis Ogg<br />
* Linda Ballinger<br />
* Terry Brady<br />
* Betsy Coles<br />
* First and last name<br />
<br />
=== Intro to Blacklight ===<br />
* Bess Sadler, Stanford University Library (bess at stanford.edu)<br />
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)<br />
* Jason Ronallo, NC State (jronallo at gmail.com)<br />
* Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)<br />
<br />
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter. <br />
<br />
Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Shawn Kiewel<br />
* Jon Stroop<br />
* Jeremy Morse<br />
* Karen Miller<br />
* Tommy Ingulfsen<br />
* Chung Kang<br />
<br />
=== DPLA Intro/Hacking ===<br />
<br />
* Presenter(s)/Leader(s): TBD<br />
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)<br />
<br />
This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
=== Fail4lib ===<br />
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)<br />
* Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)<br />
<br />
The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans ("The Pivot"), and failing more cheaply.<br />
<br />
Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:<br />
<br />
# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.<br />
# Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:<br />
#* Technical failure<br />
#* Failure to effectively address a real user need<br />
#* Overinvestment<br />
#* Outreach/Promotion failure<br />
#* Design/UX failure<br />
#* Project team communication failure<br />
#* Missed opportunities (risk-averse failure)<br />
#* Successes gleaned from failures<br />
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.<br />
# A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.<br />
<br />
I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Becky Yoose<br />
<br />
=== Solr 4 In Depth ===<br />
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)<br />
<br />
The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Esmé Cowles<br />
* Jon Stroop<br />
* Adam Constabars<br />
* Kevin Clarke<br />
* Jacob Andresen<br />
<br />
[[Category:Code4Lib2013]]</div>Ckanghttps://wiki.code4lib.org/index.php?title=2013_preconference_proposals&diff=291712013 preconference proposals2012-12-05T22:49:34Z<p>Ckang: /* Data Visualization Hackfest */</p>
<hr />
<div>Proposals '''now closed'''.<br />
<br />
Spaces available: 4+ Rooms<br />
<br />
Please follow the formatting guidelines:<br />
<pre><br />
=== Talk Title ===<br />
<br />
* Presenter/Leader, affiliation (optional), and email address (mandatory!)<br />
* Second Presenter/Leader, affiliation, email address, if applicable<br />
<br />
Description.<br />
</pre><br />
<br />
==Full Day==<br />
<br />
===Drupal4lib Sub-con Barcamp===<br />
<br />
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or <br />
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu<br />
<br />
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.<br />
<br />
If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.<br />
<br />
Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.<br />
<br />
'''I plan on attending:'''<br />
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)<br />
* Christina Salazar (afternoon only)<br />
<br />
==Half Day Morning==<br />
=== Open space session ===<br />
<br />
* Dan Chudnov, dchud at gwu edu<br />
<br />
The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.<br />
<br />
If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.<br />
<br />
'''I plan on attending:'''<br />
* Devon Smith<br />
* First and last name<br />
* Esmé Cowles<br />
* Jason Casden<br />
<br />
=== Delivery services ===<br />
* Ted Lawless, Brown University Library, tlawless at brown edu. <br />
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.<br />
<br />
Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands. <br />
<br />
Possible topics/activities include:<br />
* panel discussion of what some libraries have done in this area<br />
* comparisons of different approaches to addressing delivery <br />
* overview of tools available <br />
* sharing of strategies and experiences<br />
* time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/py360link Py360 Link]. <br />
<br />
Resources and background information:<br />
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway] <br />
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]<br />
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]<br />
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
=== Intro to Blacklight ===<br />
* Bess Sadler, Stanford University Library (bess at stanford.edu)<br />
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)<br />
<br />
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter. <br />
<br />
Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.<br />
<br />
'''I plan on attending:'''<br />
* Linda Ballinger<br />
* Terry Brady<br />
* First and last name<br />
<br />
=== RailsBridge Intro to Ruby on Rails ===<br />
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu<br />
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br />
* Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu<br />
* Ross Singer, Talis, rossfsinger@gmail.com<br />
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org<br />
* Anyone else want to come and help folks? Contact Jason.<br />
<br />
RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language, the Rails framework, and version control with git. Participants will build a working Rails application. <br />
<br />
There will be some pre-preconference preparation needed so that we can effectively use our time. Details to come.<br />
<br />
* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Shawn Kiewel<br />
* Jon Stroop<br />
* Christina Salazar<br />
* Karen Coombs - coombsk{at}oclc{dot}org<br />
* Becky Yoose<br />
* Jeremy Morse<br />
* Julia Bauder<br />
* Chung Kang<br />
* Karen Miller<br />
<br />
===Intro to NoSQL Databases===<br />
* Joshua Gomez, George Washington University, jngomez at gwu edu<br />
<br />
Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called "Big Data" problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, CouchDB, and Neo4j.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Esha Datta<br />
* Trevor Thornton<br />
* Michael Doran<br />
* Ray Schwartz<br />
* Kevin Clarke<br />
* Andreas Orphanides<br />
* Tommy Ingulfsen<br />
<br />
==Half Day Afternoon==<br />
=== Data Visualization Hackfest ===<br />
* Chris Beer, cabeer at stanford.edu<br />
* Dan Chudnov, dchud at gwu edu<br />
<br />
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly: <br />
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.<br />
- we'll separate into groups and hack on stuff.<br />
- at the end of the day, we'll present our progress.<br />
<br />
Not a code hacker? No worries; all skill sets and backgrounds are valuable! <br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Devon Smith<br />
* Esha Datta<br />
* Ray Schwartz<br />
* Karen Coombs - coombsk{at}oclc{dot}org<br />
* Julia Bauder<br />
* Jason Stirnaman (jstirnaman at kumc.edu)<br />
<br />
=== Intro to Hydra ===<br />
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)<br />
* Mike Giarlo, Penn State Information Technology Services (michael at psu.edu)<br />
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br />
<br />
Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame. <br />
<br />
'''I plan on attending:'''<br />
* Jeremy Prevost<br />
* Dennis Ogg<br />
* Linda Ballinger<br />
* Terry Brady<br />
* First and last name<br />
<br />
=== Intro to Blacklight ===<br />
* Bess Sadler, Stanford University Library (bess at stanford.edu)<br />
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)<br />
* Jason Ronallo, NC State (jronallo at gmail.com)<br />
* Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)<br />
<br />
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter. <br />
<br />
Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Shawn Kiewel<br />
* Jon Stroop<br />
* Jeremy Morse<br />
* Karen Miller<br />
* Tommy Ingulfsen<br />
<br />
=== DPLA Intro/Hacking ===<br />
<br />
* Presenter(s)/Leader(s): TBD<br />
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)<br />
<br />
This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
=== Fail4lib ===<br />
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)<br />
* Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)<br />
<br />
The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans ("The Pivot"), and failing more cheaply.<br />
<br />
Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:<br />
<br />
# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.<br />
# Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:<br />
#* Technical failure<br />
#* Failure to effectively address a real user need<br />
#* Overinvestment<br />
#* Outreach/Promotion failure<br />
#* Design/UX failure<br />
#* Project team communication failure<br />
#* Missed opportunities (risk-averse failure)<br />
#* Successes gleaned from failures<br />
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.<br />
# A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.<br />
<br />
I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Becky Yoose<br />
<br />
=== Solr 4 In Depth ===<br />
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)<br />
<br />
The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Esmé Cowles<br />
* Jon Stroop<br />
* Adam Constabars<br />
* Kevin Clarke<br />
* Jacob Andresen<br />
<br />
[[Category:Code4Lib2013]]</div>Ckanghttps://wiki.code4lib.org/index.php?title=2013_preconference_proposals&diff=291702013 preconference proposals2012-12-05T22:48:30Z<p>Ckang: /* Intro to NoSQL Databases */</p>
<hr />
<div>Proposals '''now closed'''.<br />
<br />
Spaces available: 4+ Rooms<br />
<br />
Please follow the formatting guidelines:<br />
<pre><br />
=== Talk Title ===<br />
<br />
* Presenter/Leader, affiliation (optional), and email address (mandatory!)<br />
* Second Presenter/Leader, affiliation, email address, if applicable<br />
<br />
Description.<br />
</pre><br />
<br />
==Full Day==<br />
<br />
===Drupal4lib Sub-con Barcamp===<br />
<br />
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or <br />
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu<br />
<br />
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.<br />
<br />
If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.<br />
<br />
Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.<br />
<br />
'''I plan on attending:'''<br />
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)<br />
* Christina Salazar (afternoon only)<br />
<br />
==Half Day Morning==<br />
=== Open space session ===<br />
<br />
* Dan Chudnov, dchud at gwu edu<br />
<br />
The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.<br />
<br />
If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.<br />
<br />
'''I plan on attending:'''<br />
* Devon Smith<br />
* First and last name<br />
* Esmé Cowles<br />
* Jason Casden<br />
<br />
=== Delivery services ===<br />
* Ted Lawless, Brown University Library, tlawless at brown edu. <br />
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.<br />
<br />
Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands. <br />
<br />
Possible topics/activities include:<br />
* panel discussion of what some libraries have done in this area<br />
* comparisons of different approaches to addressing delivery <br />
* overview of tools available <br />
* sharing of strategies and experiences<br />
* time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/py360link Py360 Link]. <br />
<br />
Resources and background information:<br />
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway] <br />
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]<br />
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]<br />
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
=== Intro to Blacklight ===<br />
* Bess Sadler, Stanford University Library (bess at stanford.edu)<br />
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)<br />
<br />
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter. <br />
<br />
Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.<br />
<br />
'''I plan on attending:'''<br />
* Linda Ballinger<br />
* Terry Brady<br />
* First and last name<br />
<br />
=== RailsBridge Intro to Ruby on Rails ===<br />
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu<br />
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br />
* Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu<br />
* Ross Singer, Talis, rossfsinger@gmail.com<br />
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org<br />
* Anyone else want to come and help folks? Contact Jason.<br />
<br />
RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language, the Rails framework, and version control with git. Participants will build a working Rails application. <br />
<br />
There will be some pre-preconference preparation needed so that we can effectively use our time. Details to come.<br />
<br />
* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Shawn Kiewel<br />
* Jon Stroop<br />
* Christina Salazar<br />
* Karen Coombs - coombsk{at}oclc{dot}org<br />
* Becky Yoose<br />
* Jeremy Morse<br />
* Julia Bauder<br />
* Chung Kang<br />
* Karen Miller<br />
<br />
===Intro to NoSQL Databases===<br />
* Joshua Gomez, George Washington University, jngomez at gwu edu<br />
<br />
Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called "Big Data" problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, CouchDB, and Neo4j.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Esha Datta<br />
* Trevor Thornton<br />
* Michael Doran<br />
* Ray Schwartz<br />
* Kevin Clarke<br />
* Andreas Orphanides<br />
* Tommy Ingulfsen<br />
<br />
==Half Day Afternoon==<br />
=== Data Visualization Hackfest ===<br />
* Chris Beer, cabeer at stanford.edu<br />
* Dan Chudnov, dchud at gwu edu<br />
<br />
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly: <br />
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.<br />
- we'll separate into groups and hack on stuff.<br />
- at the end of the day, we'll present our progress.<br />
<br />
Not a code hacker? No worries; all skill sets and backgrounds are valuable! <br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Devon Smith<br />
* Esha Datta<br />
* Ray Schwartz<br />
* Karen Coombs - coombsk{at}oclc{dot}org<br />
* Julia Bauder<br />
* Jason Stirnaman (jstirnaman at kumc.edu)<br />
* Chung Kang<br />
<br />
=== Intro to Hydra ===<br />
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)<br />
* Mike Giarlo, Penn State Information Technology Services (michael at psu.edu)<br />
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br />
<br />
Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame. <br />
<br />
'''I plan on attending:'''<br />
* Jeremy Prevost<br />
* Dennis Ogg<br />
* Linda Ballinger<br />
* Terry Brady<br />
* First and last name<br />
<br />
=== Intro to Blacklight ===<br />
* Bess Sadler, Stanford University Library (bess at stanford.edu)<br />
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)<br />
* Jason Ronallo, NC State (jronallo at gmail.com)<br />
* Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)<br />
<br />
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter. <br />
<br />
Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Shawn Kiewel<br />
* Jon Stroop<br />
* Jeremy Morse<br />
* Karen Miller<br />
* Tommy Ingulfsen<br />
<br />
=== DPLA Intro/Hacking ===<br />
<br />
* Presenter(s)/Leader(s): TBD<br />
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)<br />
<br />
This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
=== Fail4lib ===<br />
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)<br />
* Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)<br />
<br />
The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans ("The Pivot"), and failing more cheaply.<br />
<br />
Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:<br />
<br />
# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.<br />
# Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:<br />
#* Technical failure<br />
#* Failure to effectively address a real user need<br />
#* Overinvestment<br />
#* Outreach/Promotion failure<br />
#* Design/UX failure<br />
#* Project team communication failure<br />
#* Missed opportunities (risk-averse failure)<br />
#* Successes gleaned from failures<br />
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.<br />
# A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.<br />
<br />
I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Becky Yoose<br />
<br />
=== Solr 4 In Depth ===<br />
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)<br />
<br />
The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Esmé Cowles<br />
* Jon Stroop<br />
* Adam Constabars<br />
* Kevin Clarke<br />
* Jacob Andresen<br />
<br />
[[Category:Code4Lib2013]]</div>Ckanghttps://wiki.code4lib.org/index.php?title=2013_preconference_proposals&diff=291632013 preconference proposals2012-12-05T22:10:55Z<p>Ckang: /* Intro to NoSQL Databases */</p>
<hr />
<div>Proposals '''now closed'''.<br />
<br />
Spaces available: 4+ Rooms<br />
<br />
Please follow the formatting guidelines:<br />
<pre><br />
=== Talk Title ===<br />
<br />
* Presenter/Leader, affiliation (optional), and email address (mandatory!)<br />
* Second Presenter/Leader, affiliation, email address, if applicable<br />
<br />
Description.<br />
</pre><br />
<br />
==Full Day==<br />
<br />
===Drupal4lib Sub-con Barcamp===<br />
<br />
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or <br />
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu<br />
<br />
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.<br />
<br />
If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.<br />
<br />
Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.<br />
<br />
'''I plan on attending:'''<br />
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)<br />
* Christina Salazar (afternoon only)<br />
<br />
==Half Day Morning==<br />
=== Open space session ===<br />
<br />
* Dan Chudnov, dchud at gwu edu<br />
<br />
The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.<br />
<br />
If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.<br />
<br />
'''I plan on attending:'''<br />
* Devon Smith<br />
* First and last name<br />
* Esmé Cowles<br />
* Jason Casden<br />
<br />
=== Delivery services ===<br />
* Ted Lawless, Brown University Library, tlawless at brown edu. <br />
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.<br />
<br />
Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands. <br />
<br />
Possible topics/activities include:<br />
* panel discussion of what some libraries have done in this area<br />
* comparisons of different approaches to addressing delivery <br />
* overview of tools available <br />
* sharing of strategies and experiences<br />
* time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/py360link Py360 Link]. <br />
<br />
Resources and background information:<br />
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway] <br />
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]<br />
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]<br />
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
=== Intro to Blacklight ===<br />
* Bess Sadler, Stanford University Library (bess at stanford.edu)<br />
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)<br />
<br />
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter. <br />
<br />
Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.<br />
<br />
'''I plan on attending:'''<br />
* Linda Ballinger<br />
* First and last name<br />
<br />
=== RailsBridge Intro to Ruby on Rails ===<br />
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu<br />
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br />
* Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu<br />
* Ross Singer, Talis, rossfsinger@gmail.com<br />
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org<br />
* Anyone else want to come and help folks? Contact Jason.<br />
<br />
RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language, the Rails framework, and version control with git. Participants will build a working Rails application. <br />
<br />
There will be some pre-preconference preparation needed so that we can effectively use our time. Details to come.<br />
<br />
* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Shawn Kiewel<br />
* Jon Stroop<br />
* Christina Salazar<br />
* Karen Coombs - coombsk{at}oclc{dot}org<br />
* Becky Yoose<br />
* Jeremy Morse<br />
* Julia Bauder<br />
* Chung Kang<br />
* Karen Miller<br />
<br />
===Intro to NoSQL Databases===<br />
* Joshua Gomez, George Washington University, jngomez at gwu edu<br />
<br />
Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called "Big Data" problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, CouchDB, and Neo4j.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Esha Datta<br />
* Trevor Thornton<br />
* Michael Doran<br />
* Ray Schwartz<br />
* Kevin Clarke<br />
* Andreas Orphanides<br />
* Chung Kang<br />
<br />
==Half Day Afternoon==<br />
=== Data Visualization Hackfest ===<br />
* Chris Beer, cabeer at stanford.edu<br />
* Dan Chudnov, dchud at gwu edu<br />
<br />
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly: <br />
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.<br />
- we'll separate into groups and hack on stuff.<br />
- at the end of the day, we'll present our progress.<br />
<br />
Not a code hacker? No worries; all skill sets and backgrounds are valuable! <br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Devon Smith<br />
* Esha Datta<br />
* Ray Schwartz<br />
* Karen Coombs - coombsk{at}oclc{dot}org<br />
* Julia Bauder<br />
* Jason Stirnaman (jstirnaman at kumc.edu)<br />
* Chung Kang<br />
<br />
=== Intro to Hydra ===<br />
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)<br />
* Mike Giarlo, Penn State Information Technology Services (michael at psu.edu)<br />
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br />
<br />
Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame. <br />
<br />
'''I plan on attending:'''<br />
* Jeremy Prevost<br />
* Dennis Ogg<br />
* Linda Ballinger<br />
* First and last name<br />
<br />
=== Intro to Blacklight ===<br />
* Bess Sadler, Stanford University Library (bess at stanford.edu)<br />
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)<br />
* Jason Ronallo, NC State (jronallo at gmail.com)<br />
* Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)<br />
<br />
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter. <br />
<br />
Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Shawn Kiewel<br />
* Jon Stroop<br />
* Jeremy Morse<br />
<br />
=== DPLA Intro/Hacking ===<br />
<br />
* Presenter(s)/Leader(s): TBD<br />
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)<br />
<br />
This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
=== Fail4lib ===<br />
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)<br />
* Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)<br />
<br />
The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans ("The Pivot"), and failing more cheaply.<br />
<br />
Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:<br />
<br />
# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.<br />
# Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:<br />
#* Technical failure<br />
#* Failure to effectively address a real user need<br />
#* Overinvestment<br />
#* Outreach/Promotion failure<br />
#* Design/UX failure<br />
#* Project team communication failure<br />
#* Missed opportunities (risk-averse failure)<br />
#* Successes gleaned from failures<br />
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.<br />
# A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.<br />
<br />
I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Becky Yoose<br />
<br />
=== Solr 4 In Depth ===<br />
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)<br />
<br />
The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Esmé Cowles<br />
* Jon Stroop<br />
* Adam Constabars<br />
* Kevin Clarke<br />
* Jacob Andresen<br />
<br />
[[Category:Code4Lib2013]]</div>Ckanghttps://wiki.code4lib.org/index.php?title=2013_preconference_proposals&diff=291612013 preconference proposals2012-12-05T22:09:39Z<p>Ckang: /* Half Day Afternoon */</p>
<hr />
<div>Proposals '''now closed'''.<br />
<br />
Spaces available: 4+ Rooms<br />
<br />
Please follow the formatting guidelines:<br />
<pre><br />
=== Talk Title ===<br />
<br />
* Presenter/Leader, affiliation (optional), and email address (mandatory!)<br />
* Second Presenter/Leader, affiliation, email address, if applicable<br />
<br />
Description.<br />
</pre><br />
<br />
==Full Day==<br />
<br />
===Drupal4lib Sub-con Barcamp===<br />
<br />
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or <br />
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu<br />
<br />
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.<br />
<br />
If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.<br />
<br />
Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.<br />
<br />
'''I plan on attending:'''<br />
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)<br />
* Christina Salazar (afternoon only)<br />
<br />
==Half Day Morning==<br />
=== Open space session ===<br />
<br />
* Dan Chudnov, dchud at gwu edu<br />
<br />
The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.<br />
<br />
If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.<br />
<br />
'''I plan on attending:'''<br />
* Devon Smith<br />
* First and last name<br />
* Esmé Cowles<br />
* Jason Casden<br />
<br />
=== Delivery services ===<br />
* Ted Lawless, Brown University Library, tlawless at brown edu. <br />
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.<br />
<br />
Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands. <br />
<br />
Possible topics/activities include:<br />
* panel discussion of what some libraries have done in this area<br />
* comparisons of different approaches to addressing delivery <br />
* overview of tools available <br />
* sharing of strategies and experiences<br />
* time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/py360link Py360 Link]. <br />
<br />
Resources and background information:<br />
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway] <br />
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]<br />
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]<br />
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
=== Intro to Blacklight ===<br />
* Bess Sadler, Stanford University Library (bess at stanford.edu)<br />
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)<br />
<br />
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter. <br />
<br />
Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.<br />
<br />
'''I plan on attending:'''<br />
* Linda Ballinger<br />
* First and last name<br />
<br />
=== RailsBridge Intro to Ruby on Rails ===<br />
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu<br />
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br />
* Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu<br />
* Ross Singer, Talis, rossfsinger@gmail.com<br />
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org<br />
* Anyone else want to come and help folks? Contact Jason.<br />
<br />
RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language, the Rails framework, and version control with git. Participants will build a working Rails application. <br />
<br />
There will be some pre-preconference preparation needed so that we can effectively use our time. Details to come.<br />
<br />
* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Shawn Kiewel<br />
* Jon Stroop<br />
* Christina Salazar<br />
* Karen Coombs - coombsk{at}oclc{dot}org<br />
* Becky Yoose<br />
* Jeremy Morse<br />
* Julia Bauder<br />
* Chung Kang<br />
<br />
===Intro to NoSQL Databases===<br />
* Joshua Gomez, George Washington University, jngomez at gwu edu<br />
<br />
Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called "Big Data" problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, CouchDB, and Neo4j.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Esha Datta<br />
* Trevor Thornton<br />
* Michael Doran<br />
* Ray Schwartz<br />
* Kevin Clarke<br />
* Andreas Orphanides<br />
<br />
==Half Day Afternoon==<br />
=== Data Visualization Hackfest ===<br />
* Chris Beer, cabeer at stanford.edu<br />
* Dan Chudnov, dchud at gwu edu<br />
<br />
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly: <br />
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.<br />
- we'll separate into groups and hack on stuff.<br />
- at the end of the day, we'll present our progress.<br />
<br />
Not a code hacker? No worries; all skill sets and backgrounds are valuable! <br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Devon Smith<br />
* Esha Datta<br />
* Ray Schwartz<br />
* Karen Coombs - coombsk{at}oclc{dot}org<br />
* Julia Bauder<br />
* Jason Stirnaman (jstirnaman at kumc.edu)<br />
* Chung Kang<br />
<br />
=== Intro to Hydra ===<br />
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)<br />
* Mike Giarlo, Penn State Information Technology Services (michael at psu.edu)<br />
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br />
<br />
Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame. <br />
<br />
'''I plan on attending:'''<br />
* Jeremy Prevost<br />
* Dennis Ogg<br />
* Linda Ballinger<br />
* First and last name<br />
<br />
=== Intro to Blacklight ===<br />
* Bess Sadler, Stanford University Library (bess at stanford.edu)<br />
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)<br />
* Jason Ronallo, NC State (jronallo at gmail.com)<br />
* Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)<br />
<br />
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter. <br />
<br />
Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Shawn Kiewel<br />
* Jon Stroop<br />
* Jeremy Morse<br />
<br />
=== DPLA Intro/Hacking ===<br />
<br />
* Presenter(s)/Leader(s): TBD<br />
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)<br />
<br />
This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
=== Fail4lib ===<br />
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)<br />
* Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)<br />
<br />
The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans ("The Pivot"), and failing more cheaply.<br />
<br />
Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:<br />
<br />
# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.<br />
# Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:<br />
#* Technical failure<br />
#* Failure to effectively address a real user need<br />
#* Overinvestment<br />
#* Outreach/Promotion failure<br />
#* Design/UX failure<br />
#* Project team communication failure<br />
#* Missed opportunities (risk-averse failure)<br />
#* Successes gleaned from failures<br />
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.<br />
# A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.<br />
<br />
I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Becky Yoose<br />
<br />
=== Solr 4 In Depth ===<br />
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)<br />
<br />
The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Esmé Cowles<br />
* Jon Stroop<br />
* Adam Constabars<br />
* Kevin Clarke<br />
* Jacob Andresen<br />
<br />
[[Category:Code4Lib2013]]</div>Ckanghttps://wiki.code4lib.org/index.php?title=2013_preconference_proposals&diff=291602013 preconference proposals2012-12-05T22:09:24Z<p>Ckang: /* RailsBridge Intro to Ruby on Rails */</p>
<hr />
<div>Proposals '''now closed'''.<br />
<br />
Spaces available: 4+ Rooms<br />
<br />
Please follow the formatting guidelines:<br />
<pre><br />
=== Talk Title ===<br />
<br />
* Presenter/Leader, affiliation (optional), and email address (mandatory!)<br />
* Second Presenter/Leader, affiliation, email address, if applicable<br />
<br />
Description.<br />
</pre><br />
<br />
==Full Day==<br />
<br />
===Drupal4lib Sub-con Barcamp===<br />
<br />
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or <br />
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu<br />
<br />
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.<br />
<br />
If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.<br />
<br />
Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.<br />
<br />
'''I plan on attending:'''<br />
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)<br />
* Christina Salazar (afternoon only)<br />
<br />
==Half Day Morning==<br />
=== Open space session ===<br />
<br />
* Dan Chudnov, dchud at gwu edu<br />
<br />
The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.<br />
<br />
If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.<br />
<br />
'''I plan on attending:'''<br />
* Devon Smith<br />
* First and last name<br />
* Esmé Cowles<br />
* Jason Casden<br />
<br />
=== Delivery services ===<br />
* Ted Lawless, Brown University Library, tlawless at brown edu. <br />
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.<br />
<br />
Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands. <br />
<br />
Possible topics/activities include:<br />
* panel discussion of what some libraries have done in this area<br />
* comparisons of different approaches to addressing delivery <br />
* overview of tools available <br />
* sharing of strategies and experiences<br />
* time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/py360link Py360 Link]. <br />
<br />
Resources and background information:<br />
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway] <br />
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]<br />
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]<br />
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
=== Intro to Blacklight ===<br />
* Bess Sadler, Stanford University Library (bess at stanford.edu)<br />
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)<br />
<br />
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter. <br />
<br />
Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.<br />
<br />
'''I plan on attending:'''<br />
* Linda Ballinger<br />
* First and last name<br />
<br />
=== RailsBridge Intro to Ruby on Rails ===<br />
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu<br />
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br />
* Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu<br />
* Ross Singer, Talis, rossfsinger@gmail.com<br />
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org<br />
* Anyone else want to come and help folks? Contact Jason.<br />
<br />
RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language, the Rails framework, and version control with git. Participants will build a working Rails application. <br />
<br />
There will be some pre-preconference preparation needed so that we can effectively use our time. Details to come.<br />
<br />
* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Shawn Kiewel<br />
* Jon Stroop<br />
* Christina Salazar<br />
* Karen Coombs - coombsk{at}oclc{dot}org<br />
* Becky Yoose<br />
* Jeremy Morse<br />
* Julia Bauder<br />
* Chung Kang<br />
<br />
===Intro to NoSQL Databases===<br />
* Joshua Gomez, George Washington University, jngomez at gwu edu<br />
<br />
Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called "Big Data" problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, CouchDB, and Neo4j.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Esha Datta<br />
* Trevor Thornton<br />
* Michael Doran<br />
* Ray Schwartz<br />
* Kevin Clarke<br />
* Andreas Orphanides<br />
<br />
==Half Day Afternoon==<br />
=== Data Visualization Hackfest ===<br />
* Chris Beer, cabeer at stanford.edu<br />
* Dan Chudnov, dchud at gwu edu<br />
<br />
* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly: <br />
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.<br />
- we'll separate into groups and hack on stuff.<br />
- at the end of the day, we'll present our progress.<br />
<br />
Not a code hacker? No worries; all skill sets and backgrounds are valuable! <br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Devon Smith<br />
* Esha Datta<br />
* Ray Schwartz<br />
* Karen Coombs - coombsk{at}oclc{dot}org<br />
* Julia Bauder<br />
* Jason Stirnaman (jstirnaman at kumc.edu)<br />
<br />
=== Intro to Hydra ===<br />
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)<br />
* Mike Giarlo, Penn State Information Technology Services (michael at psu.edu)<br />
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)<br />
<br />
Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame. <br />
<br />
'''I plan on attending:'''<br />
* Jeremy Prevost<br />
* Dennis Ogg<br />
* Linda Ballinger<br />
* First and last name<br />
<br />
=== Intro to Blacklight ===<br />
* Bess Sadler, Stanford University Library (bess at stanford.edu)<br />
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)<br />
* Jason Ronallo, NC State (jronallo at gmail.com)<br />
* Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)<br />
<br />
Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter. <br />
<br />
Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Shawn Kiewel<br />
* Jon Stroop<br />
* Jeremy Morse<br />
<br />
=== DPLA Intro/Hacking ===<br />
<br />
* Presenter(s)/Leader(s): TBD<br />
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)<br />
<br />
This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
<br />
=== Fail4lib ===<br />
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)<br />
* Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)<br />
<br />
The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans ("The Pivot"), and failing more cheaply.<br />
<br />
Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:<br />
<br />
# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.<br />
# Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:<br />
#* Technical failure<br />
#* Failure to effectively address a real user need<br />
#* Overinvestment<br />
#* Outreach/Promotion failure<br />
#* Design/UX failure<br />
#* Project team communication failure<br />
#* Missed opportunities (risk-averse failure)<br />
#* Successes gleaned from failures<br />
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.<br />
# A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.<br />
<br />
I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Becky Yoose<br />
<br />
=== Solr 4 In Depth ===<br />
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)<br />
<br />
The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.<br />
<br />
'''I plan on attending:'''<br />
* First and last name<br />
* Esmé Cowles<br />
* Jon Stroop<br />
* Adam Constabars<br />
* Kevin Clarke<br />
* Jacob Andresen<br />
<br />
[[Category:Code4Lib2013]]</div>Ckang