Code4Lib - User contributions [en]

2015 Conference Committees

2015-02-02T22:17:37Z

Christinasalazar: added self to onsite volunteer committee

= Code4Lib 2015 Committees =

If you are interested in helping out with a particular part of the Code4Lib 2015 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.

We will assign a local contact to each committee.

== Location and Dates ==

(more details at [http://code4lib.org/conference/2015 http://code4lib.org/conference/2015])
* Location: Hilton Portland and Executive Tower, Portland, Oregon
* Dates:
** Pre-conferences - February 9th, 2015
** Main meeting - February 10th - 12th, 2015
** Post conference activities?

== Book Give-Away Committee ==

This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.

Need about 2 months to get books shipped to the conference location.

* [[User:JasonMichel|Jason Paul Michel]]
* [[User:TerrellT|Trey Terrell]] - Local Contact

== Keynote Speakers Committee ==

This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.

* [[User:Phette23|Eric Phetteplace]]
* Heidi Dowding

== Onsite Volunteer Committee ==

This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.
* Whitni Watkins
* Dre
* [[User:evviva|Evviva Weinraub Lajoie]] - Local Contact
* Bojana Skarich - Local Contact
* Bobbi Fox
* Christina Salazar

== Pre-conference Committee ==

This committee plans the pre-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.
* [[User:ChristinaHarlow|Christina]]
* [[User:LauraKrier|Laura Krier]]
* [[User:aaroncollie|Aaron Collie]]
* [[User:wickr|Ryan Wick]] - Local Contact

== Program Committee ==

This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.

* mx matienzo
* cbeer
* Tod Olson
* [[User:Cynthia|Arty]]
* [[User:Ssimpkin|Sarah Simpkin]]
* Ranti Junus
* [[User:DataGazetteer|Peter Murray]] - v

== Scholarships Committee ==

This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.

* Ruth Kitchin Tillman
* Francis Kayiwa
* Bohyun Kim
* Mairelys Lemus-Rojas
* [[User:zhanghu|Hui Zhang]] - Local Contact

== Social Activities Committee ==

The committee plans, proposes, and organizes the evening activities.

* Becky Yoose - v(committee member 4 life)
* Whitni Watkins
* [[User:eatonml|Mike Eaton]] - Local Contact

== Childcare Committee ==

Committee to evaluate needs and explore possibilities for on-site child care at the conference. Will implement whatever is determined to be possible this year and develop guidelines for future conferences.

* Sara Amato (lead)
* Christina Salazar
* [[User:zhanghu|Hui Zhang]] - Local Contact

== Sponsorships Committee ==

This committee organizes the sponsorship activities. Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts. See the [http://wiki.code4lib.org/images/4/42/Code4LibProspectus.pdf Prospectus] for potential sponsors.

* Roy Tennant, OCLC, firstnamelastname@gmail.com
* [[User:evviva|Evviva Weinraub Lajoie]] - Local Contact
* [[User:Terrellt|Trey Terrell]] - Local Contact

== Streaming Video Committee ==

*[[User:highermath|Cary Gordon]] has equipment, experience and domain knowledge to share.
*[[User:RileyChilds|Riley Childs]] can help, but will not be attending conf
*[[User:wickr|Ryan Wick]] - Local Contact

== T-Shirt Committee ==

This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.

*[[User:ChristinaHarlow|Christina]]
*[[User:Eatonm|Mike Eaton]] - Local Contact

== Voting Activities Committee ==

This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.

*[[User:Wickr|Ryan Wick]] - Local Contact
*[[User:Wickr|Sheila Yeh]]

== Whatever Committee ==

This committee does whatever the organizers can't talk anyone else into doing.

* Francis Kayiwa
* Becky Yoose (will do things for mortgage payment assistance)
* [[User:ChristinaHarlow|Christina]]
* [[User:Ssimpkin|Sarah Simpkin]]
* Ranti Junus
* Sarah Park
* [[User:KimPham|Kim Pham]]
* Bojana Skarich - Local Contact
* Ryan Wick - Local Contact

== Wifi / Electrical / IRC ==

This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community.

* [[User:highermath|Cary Gordon]], cgordon@chillco.com
* [[User:RileyChilds|Riley Childs]] is able to assist with Wireless planning and IRC stuffs, rchilds@cucawarriors.com
* [[User:Wickr|Ryan Wick]] - Local Contact

= Documentation =
To help with documention, no need to sign up, just start editing.
* [[How To Plan A Code4LibCon]]

== Documentation Interest Group ==
Promote ongoing documentation efforts.

[[Category:Code4Lib2015]]

2015 Preconference Proposals

2015-02-02T22:13:46Z

Christinasalazar: added myself to couple preconf sessions

Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions.

== Preconference Schedule (draft) ==
There may be some room switching when registration opens. Rooms will be confirmed the week before Code4Lib. See below for further information on each session.

{| class="wikitable sortable"
|-
! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1:30 PM - 4:30 PM)
|-
| '''Parlor A (30''') || Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable (9: Needs: projector, internet connection, and power strips) || Intro to Git & possibly beyond (40: Needs: projector/screen)
|-
| '''Parlor B (30)''' || Code Retreat (18: Needs whiteboard, dry-erase markers, projector) || Code Retreat (15: Needs whiteboard, dry-erase markers, projector)
|-
| '''Parlor C (30)''' || [[code4lib/Write The Docs barcamp]] (8: Needs: projector/screen, flipboard/whiteboard, power sources for laptops) || [[code4lib/Write The Docs barcamp]] (5)
|-
| '''Grand Ballroom''' I (320) || '''CANCELLED''': [UXtravaganza] || Presentations workshop (1: Needs: projector/screen)
|-
| '''Grand Ballroom''' II (200) || Visualizing Library Data (60: Needs: projector) || DPLA API Workshop (34: Bringing their own projector)
|-
| '''Galleria I (35)''' || Coding Custom Solutions for Every Department in the Library with File Analyzer (1: Needs PC laptop projection, monitor, internet access/wifi, attendees bring laptops) || Fail4Lib 2015 (13: Needs: projector/screen; Requested: Conference table seating, limit 20 attendants)
|-
| '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (25: Needs: internet/wifi, overhead projection) || CollectionSpace: Getting it up and running at your museum (5: Needs: Projector)
|-
| '''Galleria III (35)''' || Replace yourself with a painfully complex bash script...or try Ansible (20: Need projector) || Intro to Docker (52)
|-
| '''Studio (35)''' || Linked Data Workshop (56: Bringing their own projector) || Dive into Hydra (29: Needs: projector/screen; Requests: classroom style seating)
|-
| '''Directors (35)''' || Code4Arc (20: Needs: projector) || Code4Arc (18: Needs: projector)
|-
| '''Council (45)''' || Delivering and Preserving GIS Data (10: Projector, Video connector for MacBook Pro, wifi, power outlets) || A hands-on introduction to GeoBlacklight (19: Needs: projector, outlets; Requests: list of attendees)
|}

== Pre-conferences ==
===MORNING:===
==== Coding Custom Solutions for Every Department in the Library with File Analyzer ====
Morning, Galleria I
* Terry Brady, Georgetown University Library, twb27@georgetown.edu

The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.
* Analyzing Marc Records for the Cataloging department
* Transferring ILS invoices for the University Account System for the Acquisitions department
* Delivering patron fines to the Bursar’s office for the Access Service department
* Summarizing student worker timesheet data for the Finance department
* Validating counter compliant reports for the Electronic Resources department
* Preparing ingest packages for the Digital Services department
* Validating checksums for the Preservation department

This hands on workshop will step through the components of the application framework and the process of customizing the application.

TRAINING OUTLINE
* https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training-Code4Lib-2015

''Interested in Attending''
# Megan Kudzia
# Julie Swierczek

====Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable:====
Morning, Parlor A
* Karen A. Coombs, OCLC, coombsk@oclc.org

Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.

We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.

''Interested in Attending''
# Peggy Griesinger
# Ray Schwartz
# Josh Wilson

==== Delivering and Preserving GIS Data ====
Morning, Council
* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu

We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.

''Interested in Attending''
# [[User:Ssimpkin|Sarah Simpkin]]
# Vicky Steeves
# Andrew Battista
# Peggy Griesinger

====Linked Data Workshop====
Morning, Studio
* Karen Estlund, University of Oregon, kestlund@uoregon.edu
* Tom Johnson, DPLA, tom@dp.la

Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.

''Interested in Attending''
# Logan Cox
# Ray Schwartz
# Chris Hallberg
# Derek Merleaux
# Steven Anderson
# Eben English
# Mark Mounts
# Heather Pitts
# Andrew Woods
# Carol Bean
# Naomi Dushay (probably)
# David Lacy
# David Uspal
# David Bass
# Brendan Quinn
# Chrissy Rissmeyer
# Sharon Clapp
# Anjanette Young
# Brooke Sansosti
# Richard Tan

====RailsBridge: Intro to programming in Ruby on Rails====
Morning, Galleria II
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu
* Laney McGlohon, Stanford University, laneymcg@stanford.edu
* Additional instructors welcome

''HOME WORK: Please do in advance!! http://docs.railsbridge.org/installfest/''
To help the class run smoothly please complete the install fest before attending the class. If you have problems contact us!

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! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.

RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].

''Interested in Attending''
# Maura Carbone
#Vicky Steeves
# Peggy Griesinger
# Mike Price
# Jean Rainwater
# Coral Sheldon-Hess
# Margaret Heller
# Bohyun Kim
# Mark Jarrell
# Bojana Skarich
#Sarah Bavier
# Christina Salazar

====Replace yourself with a painfully complex bash script...or try Ansible====
Morning, Galleria III
* Chad Nelson, chad dot nelson @ lyrasis dot org
* Blake Carver, Blake dot carver @lyrasis dot org

[http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.

''Interested in Attending''
# Ray Schwartz
# Coral Sheldon-Hess
# Kevin S. Clarke
# Joshua Gomez
# Charlie Morris
# Andy Mardesich
# Anna Headley
# Chelsea Lobdell
# Shaun Ellis
# Mark Mounts
# Chris Sharp
# Heidi Frank
# Anjanette Young

====Visualizing Library Data====
Morning, Grand Ballroom II
* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs

Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.

''Interested in Attending''
# Ashley Blewer!
# Bobbi Fox
# Ray Schwartz
# Ranti Junus
# Eric Phetteplace
# Joshua Gomez
# Charlie Morris
# Andy Mardesich
# Tao Zhao
# Chris Hallberg
# Derek Merleaux
# Bohyun Kim
# Mark Jarrell
# Eben English
# Shaun Ellis
# Sarah Simpkin
# Mark Mounts
# Kathryn Stine
# Steve Meyer
# Matt Critchlow
# Andrew Pasterfield
# Ray Henry
# Bret Davidson
# Naomi Dushay (maybe)
# Eric Frierson
# Matt Bernhardt
# Greg Bem (Morning only)
# Dominic Bordelon

===FULL DAY:===

====Code Retreat====
Full Day, Parlor B
* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu
* Additional facilitators welcome; Especially if you have CodeRetreat experience.

"Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.
By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.
Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time." [http://coderetreat.org/about About Code Retreat]

''Interested in Attending''
# Mike Giarlo
# Charlie Morris
# Devon Smith
# Barbara Hui
# Carol Bean
# Matt Connolly
# James Van Mil
# Glen Horton

====Code4Arc ====
Full Day, Directors
* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com
* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org
* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com

What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how?

Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.

The schedule may include the following:
* Panel type conversations about the State of Art in Archives
* Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed
* Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)

Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with.

When signing up, please indicate if you are an end-user or a developer.

''Interested in Attending''
# Laney McGlohon - developer
# Shaun Ellis
# Ryan Rotter - sysadmin/developer
# Matt LaChance
# Maureen Callahan - archivist, often-times product owner
# Liza Harrell-Edge - end-user
# Jessica Venlet - end-user/archivist (can be there in the afternoon)
# Andrew Berger - "digital" archivist
# Bill Kelm - sysadmin
# Jeremy Floyd - end-user (archivist turned metadata librarian)

====[http://wiki.code4lib.org/Code4lib/Write_The_Docs_barcamp code4lib/Write The Docs barcamp]====
Full day, Parlor C
* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu
* Write the Docs contacts: TBA

'''Event page where you can find the latest information and... documentation(!) at [http://wiki.code4lib.org/Code4lib/Write_The_Docs_barcamp]'''

Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization.

Remember, like metadata, documentation is a love note to the future.

More information about Write the Docs at http://conf.writethedocs.org/ There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).

''Interested in Attending''
'''Full day'''
#

'''Morning'''
# Ranti Junus
# Mita Williams
# Whitni Watkins
# Jason Raitz

'''Afternoon'''
# Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon.
# Chris Sharp
# Julie Swierczek

===AFTERNOON:===
==== A hands-on introduction to GeoBlacklight ====
Afternoon, Council
* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu

GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop "Delivering and Preserving GIS Data".

''Interested in Attending''
# [[User:Ssimpkin|Sarah Simpkin]]
# Vicky Steeves
# Andrew Battista
# Peggy Griesinger

==== CollectionSpace: Getting it up and running at your museum ====
Afternoon, Galleria II
* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org
* Becky Escamilla, Oakland Museum of California, rescamilla@museumca.org

This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org

Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.

''Interested in Attending''
# Terry Brady
# Sharon Clapp

==== Dive into Hydra ====
Afternoon, Studio
* Justin Coyne, Data Curation Experts, justin@curationexperts.com
* Bess Sadler, Stanford University, bess@stanford.edu

Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend "RailsBridge" prior to this workshop.

''Interested in Attending''
# Maura Carbone
# Peggy Griesinger
# Mike Price
# Jean Rainwater
# Sara Amato
# David Bass
# Scott Fisher
# Brian E. Davis
# Sarah Bavier
# Christina Salazar

==== DPLA API Workshop: ====
Afternoon, Grand Ballroom II
* Audrey Altman, DPLA
* Mark Breedlove, DPLA
* Mark Matienzo, DPLA
* Tom Johnson, DPLA

The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
# Ranti Junus
# Jean Rainwater
# Mita Williams
# Margaret Heller
# Bohyun Kim
# Steven Anderson
# Shaun Ellis
# Sarah Simpkin
# Mark Jarrell
# Heather Pitts
# Kathryn Stine
# Andrew Woods
# Greg Bem
# Brooke Sansosti

==== Fail4Lib 2015 ====
Afternoon, Galleria I
* Andreas Orphanides, akorphan (at) ncsu.edu
* Jason Casden, jmcasden (at) ncsu.edu

Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. 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 shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.

This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)

The schedule may include the following:
* Case studies. Avoid our own mistakes by bearing witness to the failures of others.
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.
* Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.

''Interested in attending''
# Ray Schwartz
# Charlie Morris
# Emily Lynema
# Bret Davidson
# Hannah Sommers

==== Intro to Docker ====
Afternoon, Galleria III
* John Fink, McMaster University, john dot fink at gmail dot com
* Francis Kayiwa, University of Maryland Libraries , fkayiwa at umd dot edu

[http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.

''Interested in Attending''
# Jim Hahn
# Joshua Gomez
# Bobbi Fox
# Ray Schwartz
# Megan Kudzia
# Coral Sheldon-Hess (pleeeeaaase put this in a different slot from Ansible!)
# Cary Gordon (uses Docker in production on AWS)
# Eric Phetteplace
# Esther Verreau
# Charlie Morris
# Anna Headley (voting for afternoon, compliments ansible)
# Shaun Ellis
# Mark Mounts
# Matt Critchlow
# Ray Henry
# Eric Frierson
# Sara Amato
# David Lacy
# David Uspal
# Matt Bernhardt
# Brendan Quinn
# Anjanette Young
# Kevin S. Clarke

==== Intro to Git & possibly beyond ====
Afternoon, Parlor A
* Erin Fahy, Stanford University, efahy@stanford.edu
* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu

We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:
* What is a Distributed Version Control System?
* What's the difference between Git and Github.com?
* How to initialize new Git projects locally and on a remote server/Github
* Cloning/Forking existing projects and keeping up to date
* The wonderful world of Git branches
* Interactive rebasing
* Contributing code to existing projects & what pull requests are
* How to handle merge conflicts
* Overview of workflows and branch best practices
* (time allowing) Advanced git: pre/post hooks, submodules, anything else?

''Interested in Attending''
# Jeannie Graham
# Derek Merleaux
# Laurie Reeves
# Bojana Skarich
# Heidi Frank
# Jason Raitz
# Emily Lynema
# Brian E. Davis
# Dominic Bordelon
# Richard Tan

==== Presentations workshop ====
Afternoon, Grand Ballroom I
* Chris Beer, Stanford University, cabeer@stanford.edu
* Additional facilitators welcome.

This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.

''Interested in Attending''
#Vicky Steeves

[[Category:Code4Lib2015]]

2014 Breakout I (Tuesday)

2014-04-03T22:07:20Z

Christinasalazar: Added tiny amount of notes to Tools for Instruction break out session

==Islandora==

Institutions that are live w/Examples
*Colorado Alliance of Research Libraries [https://www.coalliance.org/software/digital-repository/members]
**Hosts Islandora 6 repositories on Drupal 6; migrating to Drupal 7
*Florida State University ([http://fsu.digital.flvc.org])
*Grinnell [http://digital.grinnell.edu/drupal/]

Question about new installation: additional resources aside from documentation
Additional resources:
*Islandora Google Group [https://groups.google.com/forum/#!forum/islandora]
* series of cookbooks with Chef for one-click installation of Islandora [https://github.com/LibraryChef/islandora]
** Could use Vagrant and virtual box
* New release of Islandora expected soon
* Lyrasis is asked to review the documentation and will do sanity checks on the documentation
* Should see improvements to documentation soon

Hosted solutions available to purchase:
* Lyrasis [https://www.lyrasis.org/LYRASIS%20Digital/Pages/Repository.aspx]
* DiscoveryGarden [http://discoverygarden.ca/solutions_ir.php]
* Cherry Hill Co. (coming soon) [http://chillco.com]

What's the learning curve with Drupal - easier/harder than Hydra?
* Drupal 7 is easier to learn than Drupal 6
* Recommend the Using Drupal / O'Reilly Book [http://www.worldcat.org/title/using-drupal/oclc/233931612]
** Useful to understand theming / design
* Drupal may be more widely-held skill set than Ruby on Rails (in which Hydra is based)
* Though at least one school's Islandora developer started with Islandora without a PHP/Drupal background
* DrupalCon - first week in June, Austin TX in 2014
* Islandora Camp ([http://islandora.ca/camps])

Setup difficulty?
* Documentation for setting up Solr / Gsearch - some confusion between v. 6 & 7 documentation
* Would be better for things to be more grouped together

Using Islandora for Media Streaming
*Video streaming: streams in HTML5 / used to use Flash in Islandora 6
*Every video gets an Mp4; audio files use Mp3
*How are storing the original videos? In Fedora. Note: objects do not have to be stored in Fedora
*Can still think of Fedora as the repository - include all master files and metadata. if need to migrate out of Fedora in the future, could simply retain master files and metdata.
*Media Streaming installed on Drupal server
**FlowPlayer; jwplayer available for Islandora 7
*Grinnel contracted with Discovery Garden to create generic content solution pack that allowed the creation of an object that held multiple types of files (pdf images, audio, video). Traded the ability to stream for the ability to create a compound object. Now need to do additional work to standardize for Islandora 7.
*Binary object created by Discovery Garden - for download.
*Islandora has several solution packs for multiple file types (video, audio, compound, large images, small images). Colorado use case involved oral history (video, audio, text documents together) which should be possible to use with the compound solution packs.

Versioning problems encountered:
*For each object - new folder is created? Can turn off versioning based upon file type; do version the metadata, but not the actual master files themselves.
*Could also use Fedora as a registry - not store the objects themselves because of versioning and performance/scaling issues.

How to handle updates to metadata?
*Checkbox to version or not.
*METS-like XML schema as a container (FOXML). When version -it adds it in to FOXML; Islandora only displays the most recent version

Note about custom modules:
*Custom modules can be difficult to get community support. out-of-house development makes it difficult to join back with the larger community and core code.

Long-term preservation:
*MetaArchive - locked server, dark archive. May be module available for checksum generator and checksum checker - runs checksum on ingest and periodically check them.
*DuraCloud - application on top of Amazon storage run by DuraSpace
*Premise - preservation metadata system that helps record whenever records are touched or changed for audit trail.

What happened to Hylandora?
* Came down to the content model: Islandora and Hydra were too divergent.

Reasons to go with Islandora over Hydra:
* Just depends on the skill set available
* Both Hydra and Islandora have active communities

Issues:
* Upgrades can be painful / difficult in both Hydra and Islandora

What kinds of content is appropriate for Islandora?
* Good for special collections and ETDs, images from Athletic departments and ContentDM
* Crossover with Content Management systems, emphasize a policy on what should be included for long-term preservation
* Grinnell - small liberal arts college; emphasize promoting a place for faculty and students to store their research (undergraduate papers, faculty white papers/publication, data sets, digital humanities, videos of performances, audio of music performances, preserving websites (difficult with Islandora 6 vs. 7, which has a WARCIVE module)
** Don't want to necessarily limit to a library-only thing; include instructional designers, academic affairs, art gallery, history,
* Florida: modules: large images, small image, pdf and books. Books module - good for yearbooks. Want to use it for ETDs and research.
** Workflow module - has been useful. Similar to DSpace workflow for ETDs. When we ingest objects and they're not ready to be published - can work with metadata, wait to publish and not be visible to the public until they are ready to publish.

Access Controls/Embargoes, Harvesting, and Statistics
* Access controls for data: Fedora use XacMole (sp)? to set permissions. can set embargoes for ETDs. IP embargo module. Could extend to the bitstream level. Pretty easy to do without breaking anything.
* OAI:PMH module - might not like how the Dublin Core looks out of the box - can use MODS out of the box to do the MODS to DC transform. Needs additional work to pass the 2.0 specification. Module that includes a REST API that will return data on various levels if requesting just specific items.
* How to handle statistics? e.g., what are the counts for objects per creation date.
** Perl script that will lookup the size of the collection, how many objects - on Github
** Google Analytics module in 7

==Relevance Search & Ranking==

==Metadata Harvesting Normalization & Enrichement @ Scale==

* Seeing same tools that were brought forth and then not hearing anything else about them.
* Conversations with folk about normalizing and enriching metadata.
* Lets hear about tools and things they are working on.
* Particular processes.

==VuFind Update==

==Telecommunicating Support Group==

@mjgiarlo

==BIBFRAME==
Notes are based off the Tweets made by the group during the discussion:

'''Questions'''
*What will workflows will look like after Linked Data and BIBFRAME are actually pushed out?
*How to best use controlled vocabularies, including various/local controlled vocabularies, in linked data work?
*Will the protectiveness of quality by catalogers become thing of past?

'''Pros'''
*Good thing about RDF, semantic metadata structure is that is creates a good skeleton that can last through system changes.
*Talked about OpenRefine, Freebase, Linked Data/Semantic Web examples
*Shout out for the Open Metadata Registry - http://metadataregistry.org/
*RDFa allows multiple property values inline- more details than http://schema.org , starts to approach MARC richness

'''Concerns'''
*Wariness of simplicity (particularly of Dublin Core) due to the possibility of overloading elements, thus blocking interoperability with other schemas.
*There is the possible issue of every library creating their own ontologies, thus reinventing the wheel.
*Discussion of how long-term cataloging employees will handle this linked data 'revolution', how to best oversee these changes with catalogers dragging their feet.

==Archivespace==

==User Experience==

''Blame @erinrwhite for cruddy notes.''

Coral facilitates. Her question for the group is, how can we overcome the focus on library experience and focus instead on user experience?

=== what's your problem?===

Introductions. Common problems:

* "Just make a web page!"
* "I can figure this weird arcane and overly complicated thing out. Why can't anyone else?"
* Convincing stakeholders that design isn't print design, doesn't need to be the same for everyone and isn't static.
* Redesign by committee, have mercy!
* Getting ready for a redesign
* Publishing/learning about UX research. Who's going through IRB, who's publishing this stuff?
* Devaluation of UX work in library, funding or mandate
* UX not being built into organizational policies etc.
* How can we scale up UX above and beyond one-project research? Expanding to include more projects beyond the website?
* How can we convince our organizations to not recreate the org chart with the website?
* Trying to create a UX position that is beyond web librarian
* Not just testing sites with librarians (!)
* What about user experience for back-of-house software?
* I'm a web team of one. Help?
* "Put the MARC view back in the catalog!"
* Do we really need to default to advanced search? Battling the exceptions vs the average user?
* Taking a guerrilla approach to UX research
* Not a lot of staff in digital area
* Moving from a culture of complaint to a culture of...fixing

A couple folks here working in organizations that have UX and assessment built into the culture. Thanks in advance for your knowledge, y'all!

=== themes===

We broke into sub-groups:

* Making time
* Changing culture
* Beyond the website

==Worldcat Search API==

Help beta test early release of the new WorldCat Search API

==Spotlight: Exhibits, Curated Collections and Blacklight==

==Tools for Instruction==

LMS Integration, Guide on the side, LibGuides, etc.

Participants:
* Mike Hagedon; interests: [http://code.library.arizona.edu/gots Guide on the Side], LTI, LMS integration, subject/course guides
* Michael Berkowski; interests [http://libdata.sourceforge.net/ LibData library subject/course guide authoring], open source
* Christina Salazar;see Mike Hagedon, plus or minus Guide on the Side (not that there's anything wrong with it, but CSUCI cannot use it)
*
(Horrible) Notes from session:
First: the group and the conversation was very diverse so here tis for what it's worth:
We know we need to automate some of the information literacy tasks
Some of us talked about how their institution was using Guide on the Side
There was also a bit of conversation about *other* types of IL instruction tools (like clickers for voting/in class participation,(board) games, mobile/e-mail app that allows for voting)
And a conversation about how libraries are now pressured to tie in IL (or any instruction) to retention and how we can track those outcomes without losing privacy

==Code4lib Conference Documentation==

We discussed the ways in which the lack of historical data make proposing to host the conference difficult. Code4libbers must convince their employer to take on financial responsibility. This does not mean the host pays. In fact, each conference has had a surplus. But a corporate institution is needed to sign the contracts with the venues and services used by the conference. Employers need convincing that the event will not be a huge cost nor a burden on the business office. To convince the administrators, a historical record of past conferences would be immensely helpful.

We discussed several data points that would be useful. Some of these include
* expected and final budgets
* total attendance
* hotel room reservation block size and % of expected size actually used
* food costs, food expectations and % of food actually consumed
* etc.

We plan to begin storing these kinds of data on the code4lib wiki for future planners to use.

Some other documentation that we also plan to add to the wiki:
* Conference Planning Committee Post-mortem (Raleigh group already started this trend with the "Lessons Learned" post)
* explanation of what it's like to work with a 3rd party event planner (Concentra), such as:
** how money flows between attendees, sponsors, host, awardees, and concentra
** what are the benefits of working with a 3rd party planner?
* examples of MOUs between multiple host institutions

Some action items:
* finish documenting this year's conference (Tim et al.)
* attempt to collect historical budgets if they still exist (Josh & Rosy)
* organize existing data on the wiki (?)

==VuFind Update==
Sorry for the delay

We had a lovely gathering of VuFind veterans with a few new comers stopping by to hear what VuFind is all about. New comer and VuFind developer Chris Hallberg headed the meeting, a strong term for sitting there and listening to all the exciting news from our awesome collaborators.

We started with some spoilers from [http://code4lib.org/conference/2014/bauder Julia Bauder's Visualization Talk], a feature of VuFind in active development. Then we went over the short-term plans for VuFind, looking at our GitHub's pull requests, heard an update from Tom on data normalization.

John Sarnowski of the ResCarta Foundation came by to see how VuFind has change since he looked at it a few years ago as the front of his project. Looking forward to a possible collaboration here. Joe talked about his excitement over console tools and his frustration with licensing, hoping to see these in the VuFind core soon! We heard about the OLE timeline and wrapped with Julia talking about her success with ebsco.

Thanks for coming by! See you all in Portland!

2013 preconference proposals

2013-01-04T21:58:08Z

Christinasalazar: adding e-mail address per JRonallo request

Proposals '''now closed'''.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

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.

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.

Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.

====I plan on attending:====

=====All Day=====
*Margaret Heller

=====Morning=====
* [[User:Kevenj|Keven Jeffery]]

=====Afternoon=====
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)
* Christina Salazar (afternoon only)
* Sarah Dooley (afternoon)
* Josh Wilson, joshwilsonnc at gmail (likely afternoon only)
* Ken Varnum, varnum at umich e-d-u
* Cody Hennesy, chennesy at library berkeley edu

==Half Day Morning==
=== Open space session ===

* Dan Chudnov, dchud at gwu edu

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.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

'''I plan on attending:'''
* Devon Smith
* Esmé Cowles
* Jason Casden
* Ryan Eby
* mark matienzo

=== Delivery services ===
* Ted Lawless, Brown University Library, tlawless at brown edu.
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.

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.

Possible topics/activities include:
* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/heroku-360link Py360 Link].

Resources and background information:
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

'''I plan on attending:'''
* Ken Varnum, varnum at umich e-d-u
* Ayla Stein
* Curtis Thacker
* Rosalyn Metz
* James Van Mil

=== Intro to Blacklight ===
* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)

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.

Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.

'''I plan on attending:'''
* Linda Ballinger
* Terry Brady
* Shawn Kiewel
* Dean Farrell
* Michael North
* Carl Jones
* Laney McGlohon

=== RailsBridge Intro to Ruby on Rails ===
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)
* Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu
* Ross Singer, Talis, rossfsinger@gmail.com
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org
* Anyone else want to come and help folks? Contact Jason.

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.

There will be some pre-preconference preparation needed so that we can effectively use our time. Details to come.

* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby

'''I plan on attending:'''
* First and last name
* John MacGillivray
* Jon Stroop - jstroop at princeton
* Christina Salazar - christina{dot}salazar{at}csuci{dot}edu
* Karen Coombs - coombsk{at}oclc{dot}org
* Becky Yoose
* Jeremy Morse
* Julia Bauder - julia{dot}bauder{at}gmail{dot}com
* Chung Kang
* Karen Miller - k-miller3{at}northwestern{dot}edu
* Betsy Coles - bcoles{at}caltech{dot}edu
* Jay Luker - jay{dot}luker{at}gmail{dot}com
* Santi Thompson
* Sarah Dooley - sarah{at}nclive{dot}org
* Brandon Dudley
* Ken Irwin
* Dennis Ogg
* Ian Walls
* Steven Villereal
* Hillel Arnold
* Josh Wilson - joshwilsonnc at gmail
* Cynthia Ng
* Ian Chan
* Heidi Frank - hf36{at}nyu{dot}edu
* Mark Mounts
* Bill McMillin - wmcmilli{at}pratt {dot}edu
* David Lacy
* Courtney Greene - crgreene at indiana dot edu

===Intro to NoSQL Databases===
* Joshua Gomez, George Washington University, jngomez at gwu edu

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.

'''I plan on attending:'''
* Erin Fahy
* Esha Datta
* Trevor Thornton
* Michael Doran
* Ray Schwartz
* Kevin Clarke
* Andreas Orphanides
* Tommy Ingulfsen
* Harrison Dekker
* Eric James
* Sean Crowe
* Scott Hanrath
* Karen Coyle
* Charles Draper
* David Uspal

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Chris Beer, cabeer at stanford.edu
* Dan Chudnov, dchud at gwu edu

* 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:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

'''I plan on attending:'''
* Devon Smith
* Esha Datta
* Ray Schwartz
* Karen Coombs - coombsk{at}oclc{dot}org
* Julia Bauder
* Jason Stirnaman (jstirnaman at kumc.edu)
* Joshua Gomez
* Ayla Stein
* Harrison Dekker
* Ian Walls
* Scott Hanrath
* [[User:Kevenj|Keven Jeffery]]
* James Van Mil
* Sean Crowe
* Karen coyle
* David Lacy
* mark matienzo
* David Uspal

=== Intro to Hydra ===
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)
* Justin Coyne, Data Curation Experts (justin.coyne at curationexperts.com)
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)

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.

'''I plan on attending:'''
* Jeremy Prevost
* Dennis Ogg
* Linda Ballinger
* Terry Brady
* Betsy Coles
* Brendan Quinn
* Shawn Kiewel
* Steven Villereal
* Ryan Eby
* Dean Farrell
* Ian Chan
* Mark Mounts
* Carl Jones
* Laney McGlohon
* First and last name

=== Intro to Blacklight ===
* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Jason Ronallo, NC State (jronallo at gmail.com)
* Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)

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.

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

'''I plan on attending:'''
* John MacGillivray
* Jon Stroop
* Jeremy Morse
* Karen Miller
* Tommy Ingulfsen
* Chung Kang
* Santi Thompson
* Brandon Dudley
* Ken Irwin
* Brendan Quinn
* Hillel Arnold
* Heidi Frank - hf36{at}nyu{dot}com
* Chris Sharp - csharp{at}georgialibraries{dot}org
* Bill McMillin - wmcmilli{at} pratt{dot} edu

=== DPLA Intro/Hacking ===

* Presenter(s)/Leader(s): TBD
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)

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.

'''I plan on attending:'''
* First and last name

=== Fail4lib ===
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)
* Andreas Orphanides, NCSU Libraries (akorphan at ncsu.edu)

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.

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:

# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.
# 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:
#* Technical failure
#* Failure to effectively address a real user need
#* Overinvestment
#* Outreach/Promotion failure
#* Design/UX failure
#* Project team communication failure
#* Missed opportunities (risk-averse failure)
#* Successes gleaned from failures
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.
# 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.

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.

'''I plan on attending:'''
* Becky Yoose
* Lisa Rabey
* Cynthia Ng

=== Solr 4 In Depth ===
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format. Sounds like this is an evening thing that might happen at a bar somewhere?

'''I plan on attending:'''
* First and last name
* Erin Fahy
* Esmé Cowles
* Jon Stroop
* Adam Constabars
* Kevin Clarke
* Jacob Andresen
* Ted Lawless
* Jay Luker
* Tom Burton-West
* Curtis Thacker
* Eric James
* Bess Sadler
* Michael North
* Charles Draper

[[Category:Code4Lib2013]]

2013 preconference proposals

2012-12-05T20:18:24Z

Christinasalazar: signed up for precon sessions

Proposals '''now closed'''.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

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.

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.

Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.

'''I plan on attending:'''
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)
* Christina Salazar (afternoon only)

==Half Day Morning==
=== Open space session ===

* Dan Chudnov, dchud at gwu edu

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.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

'''I plan on attending:'''
* Devon Smith
* First and last name
* Esmé Cowles

=== Delivery services ===
* Ted Lawless, Brown University Library, tlawless at brown edu.
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.

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.

Possible topics/activities include:
* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* 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].

Resources and background information:
* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

'''I plan on attending:'''
* First and last name

=== Intro to Blacklight ===
* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)

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.

Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.

'''I plan on attending:'''
* First and last name

=== RailsBridge Intro to Ruby on Rails ===
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)
* Shaun Ellis, Princeton University Library, shaune@princeton.edu
* Ross Singer, Talis, rossfsinger@gmail.com
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org
* Anyone else want to come and help folks? Contact Jason.

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.

There will be some pre-preconference preparation needed so that we can effectively use our time. Details to come.

* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby

'''I plan on attending:'''
* First and last name
* Shawn Kiewel
* Jon Stroop
* Christina Salazar

===Intro to NoSQL Databases===
* Joshua Gomez, George Washington University, jngomez at gwu edu

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.

'''I plan on attending:'''
* First and last name
* Esha Datta
* Trevor Thornton
* Michael Doran
* Ray Schwartz

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Chris Beer, cabeer at stanford.edu
* Dan Chudnov, dchud at gwu edu

* 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:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

'''I plan on attending:'''
* First and last name
* Devon Smith
* Esha Datta
* Ray Schwartz

=== Intro to Hydra ===
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)
* Mike Giarlo, Penn State Information Technology Services (michael at psu.edu)
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)

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.

'''I plan on attending:'''
* First and last name
* Jeremy Prevost

=== Intro to Blacklight ===
* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)
* Jason Ronallo, NC State (jronallo at gmail.com)
* Shaun Ellis, Princeton University Library, (shaune@princeton.edu)

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.

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

'''I plan on attending:'''
* First and last name
* Shawn Kiewel
* Jon Stroop

=== DPLA Intro/Hacking ===

* Presenter(s)/Leader(s): TBD
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)

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.

'''I plan on attending:'''
* First and last name

=== Fail4lib ===
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)

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.

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:

# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.
# 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:
#* Technical failure
#* Failure to effectively address a real user need
#* Overinvestment
#* Outreach/Promotion failure
#* Design/UX failure
#* Project team communication failure
#* Missed opportunities (risk-averse failure)
#* Successes gleaned from failures
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.
# 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.

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.

'''I plan on attending:'''
* First and last name

=== Solr 4 In Depth ===
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)

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.

'''I plan on attending:'''
* First and last name
* Esmé Cowles
* Jon Stroop

[[Category:Code4Lib2013]]

2013 committees sign-up page

2012-11-26T19:49:52Z

Christinasalazar: signed up for scholarship committee

= Code4Lib 2013 Committees =

If you are interested in helping out with a particular part of the Code4Lib 2013 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.

[[2013 During the Conference Volunteers | During the Conference Volunteers]]

== Book Give-Away Committee ==
*Kevin S. Clarke, ksclarke@gmail.com
*Anjanette Young

== Sponsorships Committee ==

This committee organizes the sponsorship activities. Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.

* Margaret Heller mheller@dom.edu
* [[User:DataGazetteer|Peter Murray]], peter.murray@lyrasis.org
* Kyle Banerjee banerjek@uoregon.edu
* Bohyun Kim kimb et fiu dot edu
* [http://roytennant.com/ Roy Tennant], roytennant@gmail.com
* [http://twitter.com/TheRealArty Cynthia Ng], cynthia.s.ng at gmail
* [[User:highermath|Cary Gordon]], cgordon@chillco.com

== Keynote Speakers Committee ==

This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community) and work with the speakers to arrange their travel and arrangements.

*Francis Kayiwa kayiwa@ YOU EYE SEE DOT edu
*Anjanette Young
*Kevin Reiss kr2 @ princeton . edu
*Jim Rible rible@sou.edu

== Program Committee ==

This committee plans the structure of the program, arranges the voting on presentations, etc. These folks will also announce speakers, etc.
* [[User:DataGazetteer|Peter Murray]], peter.murray@lyrasis.org
* [http://twitter.com/ranti Ranti Junus], ranti.junus@gmail.com
* Ray Schwartz, schwartzr2@wpunj.edu
* [http://twitter.com/TheRealArty Cynthia Ng], cynthia.s.ng at gmail
* Tom Johnson, thomas.johnson@oregonstate.edu
* Tod Olson, tod at uchicago dot edu

== Scholarships Committee ==

This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.
* [http://jodischneider.com/jodi.html Jodi Schneider]
* [http://ecorrado.us/ Edward M. Corrado]
* Santi Thompson, sathompson3@uh.edu
* Christina Salazar (christina.salazar AT csuci DOT edu)

== T-Shirt Committee ==

This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes.

* akorphan (akorphan AT ncsu DOT edu)
* [[User:Pberry|Pberry]] Patrick Berry (pberry@csuchico.edu)

== Social Activities Committee ==

The committee plans, proposes, and organizes the evening activities.

*Francis Kayiwa kayiwa@ YOU EYE SEE DOT edu
*Ray Schwartz, schwartzr2@wpunj.edu
*Bohyun Kim kimb et fiu dot edu
*Shane Beers, sbeers depaul edu
*[[User:JonGorman|Jon Gorman]], jtgorman @ illinois dot edu
*Becky Yoose, b.yoose cinnamon roll gmail speck com
* [http://twitter.com/danwho Dan "lampshade" Suchy], dansuchy at gmail

== Voting Activities Committee ==

This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.
* [http://twitter.com/jlefager Jim LeFager], jameslefager at gmail

== Whatever Committee ==

This committee does whatever the organizers can't talk anyone else into doing.

* [[User:highermath|Cary Gordon]], cgordon@chillco.com
* [http://twitter.com/jlefager Jim LeFager], jameslefager at gmail
* [[User:Wolf29|Wolf Halton]], wolf.halton@lyrasis.org./dev/null
* [[User:crowesn|Sean Crowe]], sean.crowe@ uc dot edu
* [[User:shawnc12|Shawn Carraway]], carraways@ midlandstech dot edu
* [[User:mackeral|Michael Lindsey]], mackeral at gmail
* [[User:Mnorth|Michael North]], m-north AT northwestern DOT edu

= Documentation =
To help with documention, no need to sign up, just start editing.
* [[How To Plan A Code4LibCon]]

== Documentation Interest Group ==
Promote ongoing documentation efforts.

[[Category: Code4Lib2013]]