== Preconference Schedule (draft) ==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.
Session titles in Italics means they have not been confirmed yet by presenters/workshop leaders.== Preconference Schedule == This is a draft, and there may be some room switching when registration opens. Rooms will be confirmed the week before Code4LibSee 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 Presentations workshop (1: 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''' Broadway I & II (32070) ''' || CANCELLEDLinked Data Workshop (56: [UXtravaganza] Bringing their own projector) || Presentations workshop Intro to Git & possibly beyond (40: Needs: projector/screen)
|-
| '''Grand BallroomBroadway III & IV (70)''' II (200) || Visualizing Library Data (60: Needs: projector) || DPLA API Workshop Intro to Docker (Bringing their own projector52)
|-
| '''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 CollectionSpace: Getting it up and running at your museum (5: Needs: projector/screen; Requested: Conference table seating, limit 20 attendantsProjector)
|-
| '''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 Fail4Lib 2015 (13: Needs: Projectorprojector/screen; Requested: Conference table seating - must be in this room - limit 20 attendants)
|-
| '''Galleria III (35)''' || Replace yourself with a painfully complex bash script...or try Ansible (Confirmed with Chad; No given setup needs yet20: Need projector) || Intro A hands-on introduction to DockerGeoBlacklight (19: Needs: projector, outlets; Requests: list of attendees)
|-
| '''Studio (35)''' || Linked Data Workshop (Bringing their own projectorEmpty) || 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 DPLA API Workshop (Needs34: Bringing their own projector, outlets; Requests: list of attendees)
|}
== Instructions ==
Thank you for considering proposing a pre-conference! Here are a few details:
* We will be taking pre-conference proposals until '''November 7, 2014'''
* If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu
* Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]
* If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)
* If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu
* '''NOTE:''' 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
* Please use the template for proposals provided in the pre-formatted block below
== Pre-conferences ==
===MORNING:===
==== Coding Custom Solutions for Every Department in the Library with File Analyzer ====
* 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 and Preserving GIS Data ===patron fines to the Bursar’s office for the Access Service department * Summarizing student worker timesheet data for the Finance department'''Half Day [Morning]'''* Validating counter compliant reports for the Electronic Resources department* Preparing ingest packages for the Digital Services department* Validating checksums for the Preservation department
* Darren Hardy, Stanford University, drh@stanfordThis hands on workshop will step through the components of the application framework and the process of customizing the application.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'''TRAINING OUTLINE'''* https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training-Code4Lib-2015
''Interested in Attending''====Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable:====* Karen A. Coombs, OCLC, coombsk@oclc.org
If Have you would be interested in attendingbuilt 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, please indicate by adding we will discuss a set of recommended best practices for how to share your name (but not email address, etccode.) here # [[User:Ssimpkin|Sarah Simpkin]]# Vicky Steeves# Andrew Battista# Peggy Griesinger# Padraic Stack##### === A handsWe’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-on introduction to GeoBlacklight === '''Half Day [Afternoon]'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.
==== Delivering and Preserving GIS Data ====
* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu
* Eliot Jordan, Princeton University
GeoBlacklight is We will discuss how to set up a discovery solution for geospatial spatial data that builds on the successful Blacklight platform. Many libraries have collections of infrastructure (SDI) to deliver GIS data that aren’t easily discoverable, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. This By the end of the workshop you will be have a hands-on working SDI! This workshop, focused on installing and running GeoBlacklight which builds on is a compliment to the morning GeoBlacklight workshop "Delivering and Preserving GIS Data"in the afternoon.
''Interested in Attending'[https://stanford.box.com/geohydra-code4lib2015 Slides]''' [http://slides.com/eliotjordan/practical-experience-with-geoserver/ Slides (GeoServer)]
If you would be interested in attending====Linked Data Workshop====* Karen Estlund, please indicate by adding your name (but not email addressUniversity of Oregon, etckestlund@uoregon.) hereedu* Tom Johnson, DPLA, tom@dp.la
# [[UserDeveloper and metadata experts-focused linked data workshop. Topics covered will include:Ssimpkin|Sarah Simpkin]]# Vicky Steeves# Andrew Battista# Peggy Griesinger# Padraic Stack#####linked open data principles, converting existing data, and modeling linked data in DAMS.
===RailsBridge: Intro to programming in Ruby on Rails=== '''"Half-Day" [morninghttp://goo.gl/QrUIYE LD Workshop Materials]'''
====RailsBridge: Intro to programming in Ruby on Rails====
* 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'' If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here # Maura Carbone#Vicky Steeves# Peggy Griesinger# Mike Price# Jean Rainwater# Coral Sheldon-Hess# Margaret Heller# Bohyun Kim# Mark Jarrell# Bojana Skarich==== Replace yourself with a painfully complex bash script...or try Ansible === '''Half Day [Morning]'''=
* Chad Nelson, chad dot nelson @ lyrasis dot org
* Blake Carver, Blake dot carver @lyrasis dot org
Abstract:
[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''====Visualizing Library Data====* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs
If you would be interested in attending, please indicate by adding Visualizing your name (but not email addressinstitution’s data can give new insight about your holding’s strengths, etcweaknesses and outliers.) here# Ray Schwartz# Coral SheldonThey 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-Hess# Kevin Sbased 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. Clarke# Joshua Gomez# Charlie Morris# Andy Mardesich# Anna Headley# Chelsea Lobdell# Shaun Ellis# Mark Mounts# Chris Sharp# Heidi Frank
=== Intro to Docker === '''Half Day [Whenever]''' * John Fink, McMaster University, john dot fink at gmail dot com* Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com AbstractFULL DAY: [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 === Code Retreat === '''Full Day'''
====Code Retreat====
* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu
* Additional facilitators welcome; Especially if you have CodeRetreat experience.
Abstract:
"Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.
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## === Presentations workshop =Code4Arc == '''"Half Day [Afternoon]"''' (but could be expanded based on interest) * 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'' If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here #Vicky Steeves######### === Dive into Hydra === '''"Half Day [Afternoon]"''' * 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'' If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here # Maura Carbone# Peggy Griesinger# Mike Price# Jean Rainwater# Sara Amato# David Bass#### === code4lib/Write The Docs barcamp === '''"Full Day"''', with options for jumping in for half a day * code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu* Write the Docs contacts: TBA Abstract 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'' If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here '''Full day'''# Emily Lynema######### '''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. # Kevin S. Clarke# Chris Sharp####### === Linked Data Workshop === '''"Half Day [morning]"''' * Karen Estlund, University of Oregon, kestlund@uoregon.edu* Tom Johnson, DPLA, tom@dp.la Abstract: 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'' If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here # 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 === Code4Arc === '''"Full Day"''' (with options for half day participation)
* 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
Abstract:
What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how?
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
''Interested in Attending''
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
# 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)# Sara Amato (morning only) - end-user# Julie Hardesty (afternoon only) - end-user (metadata librarian)
=== Fail4Lib 2015 =[http://wiki.code4lib.org/Code4lib/Write_The_Docs_barcamp code4lib/Write The Docs barcamp]====* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu* Write the Docs contacts: TBA
'''Half Day Event page where you can find the latest information and... documentation(!) at [TBD, probably afternoonhttp://wiki.code4lib.org/Code4lib/Write_The_Docs_barcamp]'''
* Andreas OrphanidesDocumentation. We all know that we need it for things we develop, akorphan (at) ncsubut most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on.edu* Jason CasdenWe're all guilty! So what's stopping us from doing better docs? Luckily, jmcasden (at) ncsuPortland 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.edu
Abstract:Remember, like metadata, documentation is a love note to the future.
FailureMore information about Write the Docs at http://conf. Failure never changeswritethedocs. Since failure is an inescapable part of our professional work, it's important to org/ There will 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 nominal fee (t/b/d) for non-- rather than something Code4LibCon attendees (subject 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 fearorganizer approval).
This year's preconference will include new case studies and an improved discussion format===AFTERNOON:======= A hands-on introduction to GeoBlacklight ====* Darren Hardy, Stanford University, drh@stanford. Repeat customers are welcome! (Fail earlyedu* Jack Reed, Stanford University, fail oftenpjreed@stanford.)edu
The schedule may include GeoBlacklight is a discovery solution for geospatial data that builds on the following: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".
* Case studies. Avoid our own mistakes by bearing witness to the failures of others.==== CollectionSpace: Getting it up and running at your museum ====* ConfessionalsRichard Millet, for those willing to shareCollectionSpace. Let's learn from our own (and each others') failuresorg, richard.millet@lyrasis.org* 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-tolerantBecky Escamilla, Oakland Museum of California, rescamilla@museumca.org
''Interested This workshop is designed for anyone interested in attending''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
If you would Participants will be interested in attendingwalked 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, please indicate by adding your name (but not email addressset up basic roles and permissions, etcand may then catalog or otherwise document sample objects from their collections.) here
# Ray Schwartz# Charlie Morris# Emily Lynema# Bret Davidson######If possible, please bring a laptop capable of running the latest version of VirtualBox (www.virtualbox.org). I've prepared a VirtualBox machine for the workshop that I will share with you at the beginning of the session.
=== Coding Custom Solutions for Every Department in the Library with File Analyzer = Dive into Hydra ==== * Justin Coyne, Data Curation Experts, justin@curationexperts.com'''"Half Day [Morning]"''' *
* Terry BradyHydra 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, Georgetown University Library, twb27@georgetownenabling 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.edu
Abstract==== DPLA API Workshop: ====* Audrey Altman, DPLA* Mark Breedlove, DPLA* Mark Matienzo, DPLA* Tom Johnson, DPLA
The Georgetown University Digital Public Library has shared an application called 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://georgetown-university-librariescreativecommons.github.ioorg/File-Analyzerpublicdomain/ File Analyzerzero/1.0/ CC0] that has allowed us to build custom solutions for nearly every department 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 librarycapabilities 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.
* 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'''[http://bit.ly/c4l15-dpla-api Slides and resources]'''
This hands on workshop will step through the components of the application framework==== Fail4Lib 2015 ====* Andreas Orphanides, akorphan (at) ncsu. Workshop participants will install and develop custom File Analyzer tasks in this sessionedu* Jason Casden, jmcasden (at) ncsu.edu
The workshop agenda will loosely follow the '''[https://githubdocs.google.com/Georgetown-University-Librariespresentation/File-Analyzerd/wiki/File1pdatzBjVIs1YDQL3CUhWjvSj_u5Y-Analyzer9pOLZvb-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014PAdUaU/edit?usp=sharing SLIDES].'''
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'Interested ll talk about our own experiences with projects gone wrong, explore some famous design failures in Attendingthe 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.
If you would be interested in attending, please indicate by adding your name This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (but not email addressFail early, etcfail often.) here
# Megan KudziaThe 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.
=== Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: === '''Half Day [Whenever]'Readings''
* Karen A'''Case Study 1: The Healthcare. Coombs, OCLC, coombsk@oclc.orggov rollout'''
AbstractHave you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code* [http://www. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for theverge.com/us-world/2013/12/3/5163228/healthcare-gov-obamacare-website-shows-how to share your code.-government-can-do-tech-better Adrianne Jeffries 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 (The Verge): Thanks 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 distributionlot, updates and community feedbackhealthcare.gov]
''Interested in Attending''* [http://www.forbes.com/sites/lorenthompson/2013/12/03/healthcare-gov-diagnosis-the-government-broke-every-rule-of-project-management/ Loren Thompson (Forbes): Healthcare.gov diagnosis: the government broke every rule of project management]
If you would be interested in attending* Optional, please indicate by adding your name nice summary: [http://npengage.com/nonprofit-technology/lessons-learned-from-the-healthcare-gov-rollout/ Bo Crader (but not email addressnpEngage): Lessons learned from the healthcare.gov rollout]* Optional, etcvery enterprisey: [http://www.enterprisetech.com/2014/04/04/hyperscale-lessons-healthcare-gov/ Alex Woodie (EnterpriseTech) here: The hyperscale lessons of healthcare.gov]
# Peggy Griesinger# Ray Schwartz# Josh Wilson#######'''Case Study 2: The Challenger disaster'''
=== CANCELLED* [http: //ethics.tamu.edu/Portals/3/Case%20Studies/Shuttle.pdf Engineering Ethics: The Space Shuttle Challenger disaster (case study instructor''UXtravaganza'' ===s guide)]** This is designed as an instructor'''"Half or Full Day [Based on Interest?s guide, Morning/Afternoon Doesn’t Matter]"''but the summary material beginning on page 3 stands on its own as a case study report. The instructor's materials on the first couple pages are also worth reading.
* William Hicks, University of North Texas, William[http://www.hicks@untnbcnews.edu* Volunteers?com/id/3077541/ns/technology_and_science-space/t/shuttle-report-blames-nasa-culture/ NBC News: Shuttle report blames NASA culture]
Abstract* Optional, good technical detail: [http://en.wikipedia.org/wiki/Space_Shuttle_Challenger_disaster Wikipedia: Space Shuttle Challenger disaster]* Optional: [http://science.ksc.nasa.gov/shuttle/missions/51-l/docs/rogers-commission/Appendix-F.txt Richard Feynman: Appendix F: Personal observations on the reliability of the Shuttle (Rogers Commission excerpt)]
I’m envisioning a 1/2 of full day for front-end developers==== Intro to Docker ====* John Fink, content strategy peopleMcMaster University, and other misfits with an interest in user experiencejohn dot fink at gmail dot com* Francis Kayiwa, where we can talk about our shared problems, use cases, the state University of current researchMaryland Libraries , and play with each other’s sites. A half day seems doable, but if there’s significant enough interest we could push for a full? Here are a few of the things I think might be interesting to see happen:fkayiwa at umd dot edu
* '''Analytics Share-fest[http:''' A few volunteers demonstrate data about their websites, catalogs, archival/digital collections. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etcdocker. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeing. * '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation. Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc. * '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an io Docker] ([http://labupjournal.code4lib.org Open Device Lab/articles/9669 jbfink code4lib journal article]. We have about a dozen devices now of varying sizes, OS, OS Versions, + Google Glass. I’ll bring the devices, you can bring yours, and assuming we can get the wifi up and running we can test our sites/services with our big sausage fingers rather than pretending to do so through emulators and the one or two devices we each usually have on hand. If anyone ) is game they can do a tutorial on Browseran open source Linux operating system-based Inspector Tools, Browser-Cams, or other testing services. * '''The Eye’s Have It.''' The UNT Libraries is also in level virtualization framework that has seen great uptake over the process of acquiring an eye tracker and software for usability and other gaze-based research studiespast year. We’ll This workshop will take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before you through the conference. Assuming we can get our act together learning the device and can get past the technical hurdles basic features of setting it up at the pre-conferenceDocker, we could try to do some live demos on each other’s sites; i.e. You nominate a site/serviceincluding setup, someone in the audience volunteers to wear the deviceimporting of containers, development workflows and we all watch them struggle do the tasks you request on a projectordeploying. Rinse. Lather. Repeat. It would hardly be scientific, but Knowing when Docker is useful and when it sure would isn't will also be funcovered. As a backupIdeally, if we every attendee will have some sites nominated beforehand, I can run a few students at my library through some tasks here ample experience creating and we can show off the results to the crowd. For those of you wanting to attend and help out, I’d really like to see some discussion on typography, writing for the web, “dealing with business/administrative requirements from on-high", maybe do some prototyping exercises, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running a usability test, that would be rad. But we need you to step up and steer part of their own Docker instances by the time for most of this to work, so if you are interested in some aspect, and especially if you want to volunteer to lead a bit of the time, contact meend. ''Interested in Attending'' If you would be interested in attending, please indicate by adding yourname (but not email address, etc.) here # Ray Schwartz# Andy Mardesich# Chelsea Lobdell# Eben English (1/2 day)# Shaun Ellis (as attendee or volunteer)# Whitni Watkins (as attendee or volunteer)#### === Intro to Git & possibly beyond === '''Half Day [Whenever]'''
==== Intro to Git & possibly beyond ====
* 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?
* (time allowing) Advanced git: pre/post hooks, submodules, anything else?
''Interested in Attending''==== Presentations workshop ====* Chris Beer, Stanford University, cabeer@stanford.edu* Additional facilitators welcome.
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here # Jeannie Graham# Derek Merleaux# Laurie Reeves# Bojana Skarich# Heidi Frank# Jason Raitz#### === Visualizing Library Data === '''"Half Day [Morning||Afternoon]"''' * 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 is a preconference 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'' If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here # 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 === CollectionSpace: Getting it up and running at your museum === '''Half Day [Afternoon]''' * Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org* Becky Escamilla, Oakland Museum of California, rescamilla@museumca.org This workshop is designed intended for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museumfirst time Code4Lib speakers, libraryhabitual procrastinators, special collectionexperienced speakers, gallerythose thinking about offering lightning talks, 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''If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here # Terry Brady######### === DPLA API Workshop: === 're preparing a talk for this year''Half Day [Afternoon]''' * Audrey Altmans Code4Lib, DPLA* Mark Breedlove, DPLA* Mark Matienzo, DPLA* Tom Johnson, DPLA The Digital Public Library of America API this workshop guides attendees through the process of creating is an app based on DPLA's freeopportunity to rehearse your presentation, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records get feedback 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 basicspeers, get familiar with the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's presentation 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
[[Category:Code4Lib2015]]
