https://wiki.code4lib.org/api.php?action=feedcontributions&user=MarkBreedlove&feedformat=atomCode4Lib - User contributions [en]2024-03-28T12:53:56ZUser contributionsMediaWiki 1.26.2https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&diff=426302015 Preconference Proposals2015-02-04T19:57:44Z<p>MarkBreedlove: added Mark Breedlove</p>
<hr />
<div>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. <br />
<br />
== Preconference Schedule (draft) ==<br />
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.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1:30 PM - 4:30 PM)<br />
|-<br />
| '''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)<br />
|-<br />
| '''Parlor B (30)''' || Code Retreat (18: Needs whiteboard, dry-erase markers, projector) || Code Retreat (15: Needs whiteboard, dry-erase markers, projector) <br />
|-<br />
| '''Parlor C (30)''' || [[code4lib/Write The Docs barcamp]] (8: Needs: projector/screen, flipboard/whiteboard, power sources for laptops) || [[code4lib/Write The Docs barcamp]] (5)<br />
|-<br />
| '''Grand Ballroom''' I (320) || '''CANCELLED''': [UXtravaganza] || Presentations workshop (1: Needs: projector/screen)<br />
|-<br />
| '''Grand Ballroom''' II (200) || Visualizing Library Data (60: Needs: projector) || DPLA API Workshop (34: Bringing their own projector)<br />
|-<br />
| '''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)<br />
|-<br />
| '''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)<br />
|-<br />
| '''Galleria III (35)''' || Replace yourself with a painfully complex bash script...or try Ansible (20: Need projector) || Intro to Docker (52)<br />
|-<br />
| '''Studio (35)''' || Linked Data Workshop (56: Bringing their own projector) || Dive into Hydra (29: Needs: projector/screen; Requests: classroom style seating)<br />
|-<br />
| '''Directors (35)''' || Code4Arc (20: Needs: projector) || Code4Arc (18: Needs: projector)<br />
|-<br />
| '''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)<br />
|}<br />
<br />
== Pre-conferences ==<br />
===MORNING:===<br />
==== Coding Custom Solutions for Every Department in the Library with File Analyzer ====<br />
Morning, Galleria I<br />
* Terry Brady, Georgetown University Library, twb27@georgetown.edu<br />
<br />
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.<br />
* Analyzing Marc Records for the Cataloging department<br />
* Transferring ILS invoices for the University Account System for the Acquisitions department <br />
* Delivering patron fines to the Bursar’s office for the Access Service department<br />
* Summarizing student worker timesheet data for the Finance department<br />
* Validating counter compliant reports for the Electronic Resources department<br />
* Preparing ingest packages for the Digital Services department<br />
* Validating checksums for the Preservation department<br />
<br />
This hands on workshop will step through the components of the application framework and the process of customizing the application.<br />
<br />
TRAINING OUTLINE<br />
* https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training-Code4Lib-2015<br />
<br />
''Interested in Attending''<br />
# Megan Kudzia<br />
# Julie Swierczek<br />
<br />
====Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable:====<br />
Morning, Parlor A<br />
* Karen A. Coombs, OCLC, coombsk@oclc.org<br />
<br />
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.<br />
<br />
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.<br />
<br />
''Interested in Attending''<br />
# Peggy Griesinger<br />
# Ray Schwartz<br />
# Josh Wilson<br />
<br />
==== Delivering and Preserving GIS Data ====<br />
Morning, Council<br />
* Darren Hardy, Stanford University, drh@stanford.edu<br />
* Jack Reed, Stanford University, pjreed@stanford.edu<br />
<br />
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.<br />
<br />
''Interested in Attending''<br />
# [[User:Ssimpkin|Sarah Simpkin]]<br />
# Vicky Steeves<br />
# Andrew Battista<br />
# Peggy Griesinger<br />
<br />
====Linked Data Workshop====<br />
Morning, Studio<br />
* Karen Estlund, University of Oregon, kestlund@uoregon.edu<br />
* Tom Johnson, DPLA, tom@dp.la<br />
<br />
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.<br />
<br />
''Interested in Attending''<br />
# Logan Cox<br />
# Ray Schwartz<br />
# Chris Hallberg<br />
# Derek Merleaux<br />
# Steven Anderson<br />
# Eben English<br />
# Mark Mounts<br />
# Heather Pitts<br />
# Andrew Woods<br />
# Carol Bean<br />
# Naomi Dushay (probably)<br />
# David Lacy<br />
# David Uspal<br />
# David Bass<br />
# Brendan Quinn<br />
# Chrissy Rissmeyer<br />
# Sharon Clapp<br />
# Anjanette Young<br />
# Brooke Sansosti<br />
# Richard Tan<br />
# Catelynne Sahadath<br />
# Mark Breedlove<br />
<br />
====RailsBridge: Intro to programming in Ruby on Rails====<br />
Morning, Galleria II<br />
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu<br />
* Laney McGlohon, Stanford University, laneymcg@stanford.edu<br />
* Additional instructors welcome<br />
<br />
''HOME WORK: Please do in advance!! http://docs.railsbridge.org/installfest/''<br />
To help the class run smoothly please complete the install fest before attending the class. If you have problems contact us!<br />
<br />
Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.<br />
<br />
RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].<br />
<br />
''Interested in Attending''<br />
# Maura Carbone<br />
#Vicky Steeves<br />
# Peggy Griesinger<br />
# Mike Price<br />
# Jean Rainwater<br />
# Coral Sheldon-Hess<br />
# Margaret Heller<br />
# Bohyun Kim<br />
# Mark Jarrell<br />
# Bojana Skarich<br />
# Sarah Bavier<br />
# Christina Salazar<br />
<br />
====Replace yourself with a painfully complex bash script...or try Ansible====<br />
Morning, Galleria III<br />
* Chad Nelson, chad dot nelson @ lyrasis dot org<br />
* Blake Carver, Blake dot carver @lyrasis dot org<br />
<br />
[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.<br />
<br />
''Interested in Attending''<br />
# Ray Schwartz<br />
# Coral Sheldon-Hess<br />
# Kevin S. Clarke<br />
# Joshua Gomez<br />
# Charlie Morris<br />
# Andy Mardesich<br />
# Anna Headley<br />
# Chelsea Lobdell<br />
# Shaun Ellis<br />
# Mark Mounts<br />
# Chris Sharp<br />
# Heidi Frank<br />
# Anjanette Young<br />
<br />
====Visualizing Library Data====<br />
Morning, Grand Ballroom II<br />
* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs<br />
<br />
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.<br />
<br />
''Interested in Attending''<br />
# Ashley Blewer!<br />
# Bobbi Fox<br />
# Ray Schwartz<br />
# Ranti Junus<br />
# Eric Phetteplace<br />
# Joshua Gomez<br />
# Charlie Morris<br />
# Andy Mardesich<br />
# Tao Zhao<br />
# Chris Hallberg<br />
# Derek Merleaux<br />
# Bohyun Kim<br />
# Mark Jarrell<br />
# Eben English<br />
# Shaun Ellis<br />
# Sarah Simpkin<br />
# Mark Mounts<br />
# Kathryn Stine<br />
# Steve Meyer<br />
# Matt Critchlow<br />
# Andrew Pasterfield<br />
# Ray Henry<br />
# Bret Davidson<br />
# Naomi Dushay (maybe)<br />
# Eric Frierson<br />
# Matt Bernhardt<br />
# Greg Bem (Morning only)<br />
# Dominic Bordelon<br />
# Jim LeFager<br />
# Sarah Park<br />
<br />
===FULL DAY:===<br />
<br />
====Code Retreat====<br />
Full Day, Parlor B<br />
* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu<br />
* Additional facilitators welcome; Especially if you have CodeRetreat experience.<br />
<br />
"Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.<br />
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.<br />
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]<br />
<br />
''Interested in Attending''<br />
# Mike Giarlo<br />
# Charlie Morris<br />
# Devon Smith<br />
# Barbara Hui<br />
# Carol Bean<br />
# Matt Connolly<br />
# James Van Mil<br />
# Glen Horton<br />
# Jon Earley<br />
<br />
====Code4Arc ====<br />
Full Day, Directors<br />
* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com<br />
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com<br />
* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org<br />
* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com<br />
<br />
What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? <br />
<br />
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.<br />
<br />
The schedule may include the following:<br />
* Panel type conversations about the State of Art in Archives <br />
* Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed <br />
* Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)<br />
<br />
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. <br />
<br />
When signing up, please indicate if you are an end-user or a developer.<br />
<br />
''Interested in Attending''<br />
# Laney McGlohon - developer<br />
# Shaun Ellis<br />
# Ryan Rotter - sysadmin/developer<br />
# Matt LaChance<br />
# Maureen Callahan - archivist, often-times product owner<br />
# Liza Harrell-Edge - end-user<br />
# Jessica Venlet - end-user/archivist (can be there in the afternoon)<br />
# Andrew Berger - "digital" archivist<br />
# Bill Kelm - sysadmin<br />
# Jeremy Floyd - end-user (archivist turned metadata librarian)<br />
# Sara Amato (morning only) - end-user<br />
<br />
====[http://wiki.code4lib.org/Code4lib/Write_The_Docs_barcamp code4lib/Write The Docs barcamp]====<br />
Full day, Parlor C<br />
* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu<br />
* Write the Docs contacts: TBA<br />
<br />
'''Event page where you can find the latest information and... documentation(!) at [http://wiki.code4lib.org/Code4lib/Write_The_Docs_barcamp]'''<br />
<br />
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. <br />
<br />
Remember, like metadata, documentation is a love note to the future.<br />
<br />
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). <br />
<br />
''Interested in Attending''<br />
'''Full day'''<br />
# <br />
<br />
'''Morning'''<br />
# Ranti Junus<br />
# Mita Williams<br />
# Whitni Watkins<br />
# Jason Raitz<br />
<br />
'''Afternoon'''<br />
# Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon. <br />
# Chris Sharp<br />
# Julie Swierczek<br />
<br />
===AFTERNOON:===<br />
==== A hands-on introduction to GeoBlacklight ====<br />
Afternoon, Council<br />
* Darren Hardy, Stanford University, drh@stanford.edu<br />
* Jack Reed, Stanford University, pjreed@stanford.edu<br />
<br />
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".<br />
<br />
''Interested in Attending''<br />
# [[User:Ssimpkin|Sarah Simpkin]]<br />
# Vicky Steeves<br />
# Andrew Battista<br />
# Peggy Griesinger<br />
<br />
==== CollectionSpace: Getting it up and running at your museum ====<br />
Afternoon, Galleria II<br />
* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org<br />
* Becky Escamilla, Oakland Museum of California, rescamilla@museumca.org<br />
<br />
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<br />
<br />
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.<br />
<br />
''Interested in Attending''<br />
# Terry Brady<br />
# Sharon Clapp<br />
<br />
==== Dive into Hydra ====<br />
Afternoon, Studio<br />
* Justin Coyne, Data Curation Experts, justin@curationexperts.com<br />
* Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
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.<br />
<br />
''Interested in Attending''<br />
# Maura Carbone<br />
# Peggy Griesinger<br />
# Mike Price<br />
# Jean Rainwater<br />
# Sara Amato<br />
# David Bass<br />
# Scott Fisher<br />
# Brian E. Davis<br />
# Sarah Bavier<br />
# Christina Salazar<br />
# Sarah Park<br />
<br />
==== DPLA API Workshop: ====<br />
Afternoon, Grand Ballroom II<br />
* Audrey Altman, DPLA<br />
* Mark Breedlove, DPLA<br />
* Mark Matienzo, DPLA<br />
* Tom Johnson, DPLA<br />
<br />
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.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
# Ranti Junus<br />
# Jean Rainwater<br />
# Mita Williams<br />
# Margaret Heller<br />
# Bohyun Kim<br />
# Steven Anderson<br />
# Shaun Ellis<br />
# Sarah Simpkin<br />
# Mark Jarrell<br />
# Heather Pitts<br />
# Kathryn Stine<br />
# Andrew Woods<br />
# Greg Bem<br />
# Brooke Sansosti<br />
# Jim LeFager<br />
# Scott Chamberlain<br />
<br />
==== Fail4Lib 2015 ====<br />
Afternoon, Galleria I<br />
* Andreas Orphanides, akorphan (at) ncsu.edu<br />
* Jason Casden, jmcasden (at) ncsu.edu<br />
<br />
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.<br />
<br />
This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)<br />
<br />
The schedule may include the following:<br />
* Case studies. Avoid our own mistakes by bearing witness to the failures of others.<br />
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.<br />
* 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.<br />
<br />
''Readings''<br />
<br />
'''Case Study 1: The Healthcare.gov rollout'''<br />
<br />
* [http://www.theverge.com/us-world/2013/12/3/5163228/healthcare-gov-obamacare-website-shows-how-government-can-do-tech-better Adrianne Jeffries (The Verge): Thanks a lot, healthcare.gov]<br />
<br />
* [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]<br />
<br />
* Optional, nice summary: [http://npengage.com/nonprofit-technology/lessons-learned-from-the-healthcare-gov-rollout/ Bo Crader (npEngage): Lessons learned from the healthcare.gov rollout]<br />
* Optional, very enterprisey: [http://www.enterprisetech.com/2014/04/04/hyperscale-lessons-healthcare-gov/ Alex Woodie (EnterpriseTech): The hyperscale lessons of healthcare.gov]<br />
<br />
'''Case Study 2: The Challenger disaster'''<br />
<br />
* [http://ethics.tamu.edu/Portals/3/Case%20Studies/Shuttle.pdf Engineering Ethics: The Space Shuttle Challenger disaster (case study instructor's guide)]<br />
** This is designed as an instructor's guide, 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.<br />
<br />
* [http://www.nbcnews.com/id/3077541/ns/technology_and_science-space/t/shuttle-report-blames-nasa-culture/ NBC News: Shuttle report blames NASA culture]<br />
<br />
* Optional, good technical detail: [http://en.wikipedia.org/wiki/Space_Shuttle_Challenger_disaster Wikipedia: Space Shuttle Challenger disaster]<br />
* 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)]<br />
<br />
''Interested in attending''<br />
# Ray Schwartz<br />
# Charlie Morris<br />
# Emily Lynema<br />
# Bret Davidson<br />
# Hannah Sommers<br />
<br />
==== Intro to Docker ====<br />
Afternoon, Galleria III<br />
* John Fink, McMaster University, john dot fink at gmail dot com<br />
* Francis Kayiwa, University of Maryland Libraries , fkayiwa at umd dot edu<br />
<br />
[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.<br />
<br />
''Interested in Attending''<br />
# Jim Hahn<br />
# Joshua Gomez<br />
# Bobbi Fox<br />
# Ray Schwartz<br />
# Megan Kudzia<br />
# Coral Sheldon-Hess (pleeeeaaase put this in a different slot from Ansible!)<br />
# Cary Gordon (uses Docker in production on AWS)<br />
# Eric Phetteplace<br />
# Esther Verreau<br />
# Charlie Morris<br />
# Anna Headley (voting for afternoon, compliments ansible)<br />
# Shaun Ellis<br />
# Mark Mounts<br />
# Matt Critchlow<br />
# Ray Henry<br />
# Eric Frierson<br />
# David Lacy<br />
# David Uspal<br />
# Matt Bernhardt<br />
# Brendan Quinn<br />
# Anjanette Young<br />
# Kevin S. Clarke<br />
<br />
==== Intro to Git & possibly beyond ====<br />
Afternoon, Parlor A<br />
* Erin Fahy, Stanford University, efahy@stanford.edu<br />
* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu<br />
<br />
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:<br />
* What is a Distributed Version Control System?<br />
* What's the difference between Git and Github.com?<br />
* How to initialize new Git projects locally and on a remote server/Github<br />
* Cloning/Forking existing projects and keeping up to date<br />
* The wonderful world of Git branches<br />
* Interactive rebasing<br />
* Contributing code to existing projects & what pull requests are<br />
* How to handle merge conflicts<br />
* Overview of workflows and branch best practices<br />
* (time allowing) Advanced git: pre/post hooks, submodules, anything else?<br />
<br />
''Interested in Attending''<br />
# Jeannie Graham<br />
# Derek Merleaux<br />
# Laurie Reeves<br />
# Bojana Skarich<br />
# Heidi Frank<br />
# Jason Raitz<br />
# Emily Lynema<br />
# Brian E. Davis<br />
# Dominic Bordelon<br />
# Richard Tan<br />
# Catelynne Sahadath<br />
<br />
==== Presentations workshop ====<br />
Afternoon, Grand Ballroom I<br />
* Chris Beer, Stanford University, cabeer@stanford.edu<br />
* Additional facilitators welcome.<br />
<br />
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.<br />
<br />
''Interested in Attending''<br />
#Vicky Steeves<br />
<br />
[[Category:Code4Lib2015]]</div>MarkBreedlovehttps://wiki.code4lib.org/index.php?title=2014_AVGeeks_Signup&diff=407802014 AVGeeks Signup2014-03-22T00:53:52Z<p>MarkBreedlove: </p>
<hr />
<div>[http://www.avgeeks.com/wp2/ A/V Geeks] maintains a collection of over 23,000 old 16mm educational films from various decades of the 20th century, including such classics as [http://www.avgeeks.com/wp2/library-story-the-1952/ The Library Story (1952)], many obtained from school and government auctions. Media archaeologist [http://www.indyweek.com/indyweek/skip-elsheimer/Content?oid=1183990 Skip Elsheimer] holds themed showings of selected films at events around the Triangle and in other states. <br />
<br />
This event, [http://kingsbarcade.com/2014/03/26/av-geeks-present-when-computers-where-young/ When Computers Were Young], will include "Actual 16mm school films that introduce us to the wonderful world of computers and their potential future -- all before Google!" Films will include Disney's Ethics in the Computer Age and more. This showing is an all ages, public event that is part of a series of monthly shows held at [http://kingsbarcade.com/ Kings Barcade], but the event has been scheduled and themed with the Code4Lib crowd in mind.<br />
<br />
'''When:''' Doors open at 7:30 PM.<br />
<br />
'''Where:''' Located two blocks from the Sheraton, Kings is a 250-capacity live music venue with a full bar and several local beers on tap. Kings is directly connected with the [http://neptunesparlour.com/ Neptunes Parlour], a cocktail lounge with classic arcade games, pinball, and nightly DJ's. The new [http://garlandraleigh.com/ Garland] Indian restaurant, operated by the same owners, is also downstairs.<br />
<br />
'''Cost:''' The event is free with a suggested $5 donation. <br />
<br />
<br />
'''Please add your name to the list below if you are interested in attending so that we can inform the organizers about the level of interest:'''<br />
<br />
* Steve Morris<br />
* Laurie Lee Moses - this looks really fun!<br />
* Heather Rayl - old education films AND Indian food??! What more could a girl want?<br />
* Anna Headley<br />
* Ian Walls<br />
* Kevin Clarke<br />
* Paula Gray-Overtoom<br />
* Julia Bauder<br />
* Josh Wilson<br />
* Kristen Wilson<br />
* Michael Blake<br />
* Junior Tidal<br />
* Michael Levy<br />
* Declan Fleming<br />
* Ed Fugikawa<br />
* Birkin James Diana<br />
* Riley Childs (Tentative)<br />
* Bobbi Fox<br />
* Mark Breedlove<br />
<br />
<br />
[[Category:Code4Lib2014]]</div>MarkBreedlovehttps://wiki.code4lib.org/index.php?title=2014_preconference_proposals&diff=403642014 preconference proposals2014-02-10T14:03:37Z<p>MarkBreedlove: /* CLLAM @ code4lib */</p>
<hr />
<div>= PROPOSALS ARE CLOSED : PLEASE DO NOT ADD NEW PRECONFERENCES TO THIS PAGE =<br />
<br />
Proposals were accepted through December 6th, 2013.<br />
<br />
It would be really, super duper helpful if folks who think they might want to attend a pre-conference could indicate interest by adding your name to a session below. <br />
<br />
<br />
===Note===<br />
Attendance at a pre-conference will require a small fee ''due at the time of conference registration".<br />
<br />
Although this was specified in the email announcements relating to pre-conferences, it was not added to this page until December 2nd. I (Adam C.) apologize for the omission and I hope this will not cause any "sticker shock." Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.<br />
<br />
Please put your pre-conference on the list in the following format:<br />
<br />
=Code4Lib 2014 Pre-Conference Proposals=<br />
<br />
===Drupal4lib Sub-con Barcamp===<br />
=====Full Day=====<br />
<br />
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com<br />
<br />
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.<br />
<br />
This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).<br />
<br />
[[resources to help you learn drupal]]<br />
<br />
====Interested in Attending:====<br />
<br />
=====All Day=====<br />
<br />
* Renna Tuten <br />
<br />
=====Morning=====<br />
<br />
* Kevin Reiss<br />
* Charlie Morris (NCSU) - glad to see this again this year!<br />
* Paula Gray-Overtoom<br />
* Laurie Lee Moses<br />
<br />
=====Afternoon=====<br />
<br />
&nbsp;<br />
<br />
----<br />
<br />
===Open Refine Hackfest===<br />
'''"Half-Day"'''<br />
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com<br />
<br />
[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control<br />
<br />
The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. <br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<ol><br />
<li>Adam Constabaris<br />
<li>Ray Schwartz<br />
<li>Jason Stirnaman<br />
<li>Joshua Gomez<br />
<li>Sam Kome<br />
<li>Mike Beccaria<br />
<li>Angela Zoss<br />
<li>A. Soroka<br />
<li> Matt Zumwalt<br />
</ol><br />
----<br />
<br />
===Responsive Design Hackfest===<br />
'''"Half-Day [Afternoon]"''' <br />
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com<br />
* Contact David Ward, University of Illinois, dh-ward@illinois.edu<br />
<br />
This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. <br />
<br />
Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
----<br />
<br />
=== Intro to Blacklight ===<br />
'''"Half-Day [Morning]"''' <br />
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu<br />
* TA: Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
This session will be walk-through of the architecture of Blacklight, the community, and an introduction to building a Blacklight-based application. Each participant will have the opportunity to build a simple Blacklight application, and make basic customizations, while using a test-driven approach.<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Megan Kudzia<br />
# Bret Davidson<br />
# Coral Sheldon-Hess<br />
# Cory Lown<br />
# Emily Daly<br />
# Angela Zoss<br />
# Sean Aery<br />
# Francis Kayiwa<br />
# Heidi Frank<br />
# Junior Tidal<br />
# Ian Chan<br />
----<br />
<br />
===Blacklight Hackfest===<br />
'''"Half-Day [Afternoon]"''' <br />
* Contact Chris Beer, Stanford University, cabeer@stanford.edu<br />
<br />
This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.<br />
<br />
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Shaun Ellis<br />
# Kevin Reiss<br />
# Megan Kudzia<br />
# Erik Hatcher<br />
# Emily Daly<br />
# Laurie Lee Moses<br />
# Francis Kayiwa<br />
<br />
----<br />
<br />
===RailsBridge: Intro to programming in Ruby on Rails===<br />
'''"Half-Day" [morning]'''<br />
* Contact Justin Coyne, Data Curation Experts, justin@curationexperts.com<br />
<br />
Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! RailsBridge is a friendly place to get together and learn how to write some code.<br />
<br />
RailsBridge is a great workshop that opens the doors to projects like Blacklight and Hydra.<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
1. Ayla Stein<br />
<br />
2. Heidi Dowding<br />
<br />
3. Caitlin Christian-Lamb<br />
<br />
4. Scott Bacon<br />
<br />
5. [[User:RileyChilds | Riley Childs]]<br />
<br />
6. Carolina Garcia<br />
<br />
----<br />
<br />
===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===<br />
'''Full-Day'''<br />
<br />
Contact: <br />
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com<br />
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu<br />
<br />
This will be a full day session on project management. We'll cover<br />
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment<br />
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets<br />
* '''Executing the Project''' -- status meeting, status reports, issue management<br />
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product<br />
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Robin Dean<br />
# Erin White<br />
# Andrew Darby<br />
# Sam Kome<br />
# Ryan Scherle<br />
# Will Shaw<br />
# Liz Milewicz<br />
# Cynthia "Arty" Ng<br />
# Laurie Lee Moses (if I don't do the Hackfest for Blacklight)<br />
# Ranti Junus<br />
# Bohyun Kim (Afternoon)<br />
<br />
----<br />
<br />
===Fail4Lib 2014===<br />
'''Half Day [TBD, probably afternoon]'''<br />
<br />
Contacts: <br />
* Andreas Orphanides, akorphan (at) ncsu.edu<br />
* Jason Casden, jmcasden (at) ncsu.edu<br />
<br />
The task of design (and the work that we do as library coders) is intimately tied to failure. Failures, both big and small, motivate us to create and improve. Failures are also occasionally the result of our work. Understanding and embracing failure, encouraging enlightened risk-taking, and seeking out opportunities to fail and learn are essential to success in our field. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be feared.<br />
<br />
The schedule may include the following:<br />
<br />
* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?<br />
* Confessionals, for those willing to share. Talk about your own experiences with rough starts, labor pains, and doomed projects in your own work: What can we learn from our own (and each others') failures?<br />
* Group therapy. Let's talk about how to deal with risk management, failed projects, experimental endeavors, and more: How can we make ourselves, our colleagues, and our organizations more fault tolerant? How do we make sure we fail as productively as possible?<br />
<br />
''Interested in attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#Bret Davidson<br />
#Mike Graves<br />
#Ray Schwartz<br />
#Jason Stirnaman<br />
#Julia Bauder<br />
#Linda Ballinger<br />
#Scott Hanrath<br />
#Caitlin Christian-Lamb<br />
#Ian Walls<br />
#Scott Bacon <br />
#mx matienzo<br />
#Chris Sharp<br />
#Junior Tidal<br />
----<br />
<br />
===CLLAM @ code4lib===<br />
'''(Computational Linguistics for Libraries, Archives and Museums)'''<br />
<br />
'''Full Day'''<br />
<br />
Contacts: <br />
* Douglas W. Oard (primary), oard (at) umd.edu <br />
* Corey Harper, corey (dot) harper (at) nyu.edu<br />
* Robert Sanderson, azaroth42 (at) gmail.com <br />
* Robert Warren, rwarren (at) math.carleton.ca<br />
<br />
We will hack at the intersection of diverse content from Libraries, Archives and Museums and bleeding edge tools from computational linguistics for slicing and dicing that content. Did you just acquire the email archives of a startup company? Maybe you can automatically build an org chart. Have you got metadata in a slew of languages? Perhaps you can search it all using one query. Is name authority control for e-resources getting too costly? Let’s see if entity linking techniques can help. These are just a few teasers. <br />
<br />
There’ll be plenty of content and tools supplied, but please bring your own [data] too -- you’ll hack with it in new ways throughout the day. We’ll get started with some lightning talks on what we’ve brought,then we’ll break up into groups to experiment and work on the ideas that appeal. Three guaranteed outcomes: you’ll walk away with new ideas, new tools, and new people you’ll have met.<br />
<br />
''Interested in attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Devon Smith<br />
# Kevin S. Clarke<br />
# Jason Stirnaman<br />
# Joshua Gomez<br />
# Carolina Garcia<br />
# Tom Burton-West<br />
# Dan Scott<br />
# Devin Higgins<br />
# Mark Breedlove<br />
----<br />
<br />
=== GeoHydra: Managing geospatial content ===<br />
<br />
'''Half-day [Afternoon]'''<br />
<br />
* Contact: Darren Hardy, Stanford University, drh@stanford.edu<br />
* Moderator: Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,<br />
etc., all of which you want to integrate into your digital repository? In this<br />
workshop, we will discuss how Hydra can provide discovery, delivery, and<br />
management services for geospatial assets, as well as solicit questions about<br />
your own GIS projects. We aim to help answer the following questions you might have about putting geospatial data into your Hydra-based digital library:<br />
<br />
* What are the types of geospatial data?<br />
* How to dive into Hydra?<br />
* How to model geospatial holdings with Hydra?<br />
* How to discover and view geospatial data?<br />
* How to build a geospatial data infrastructure?<br />
* What are common approaches and problems?<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Esmé Cowles<br />
----<br />
<br />
===Technology, Librarianship, and Gender: Moving the conversation forward===<br />
'''Full Day'''<br />
<br />
Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]<br />
<br />
'''Description'''<br />
<br />
Librarianship is largely made up of women, yet women are significantly underrepresented in tech positions, on any level, within libraries themselves. Why? What are we doing to encourage women to become more involved in STEM within librarianship? What kind of message are we sending when library technology keynotes remain almost resolutely male? How are we changing the face of technology, not only within libraries, but with the field itself? How are we training our staff and colleagues in the areas of fairness and removal of bias? Our vendors?<br />
<br />
Lots of tough questions.<br />
<br />
While the conversation has been going on via various blogs and articles within the last few years, it was given a public face at [http://infotoday.com/il2013/day.asp?day=Monday#session_D105 Internet Librarian 2013] where a panel of 7 (four women, three men) gave personal experiences on the above and then opened up the conversation to the audience. As eye opening and enriching the conversation was, a 45 minute panel was not enough. One thing remains clear: We need to keep the conversation moving forward and start making some radical changes in the way we think, act, and how we need to harness this to start making real changes within librarianship itself.<br />
<br />
Topics to include: Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems, mentoring, ally support, and more<br />
<br />
Those attending should expect: Begin with opening up the conversation of experiences and talking about what is most needed, spending remaining time putting together live, usable solutions to start implementing as well as pushing the conversation forward at local levels<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
=====All Day=====<br />
1. Kate Kosturski<br />
<br />
2. Valerie Aurora<br />
<br />
3. Declan Fleming (I'd be good with a half day too)<br />
<br />
4. mx matienzo (likewise ok w/ half day)<br />
<br />
=====Morning=====<br />
1. Shaun Ellis<br />
<br />
2. Jason Casden<br />
<br />
3. Bohyun Kim<br />
<br />
=====Afternoon=====<br />
1. Ayla Stein<br />
<br />
2. Heidi Dowding<br />
<br />
3. Coral Sheldon-Hess<br />
<br />
4. Cory Lown<br />
----<br />
<br />
===FileAnalyzer: Rapid Development of File Manipulation Tasks===<br />
'''"Half-Day" [morning]'''<br />
* Contact Terry Brady, twb27@georgetown.edu<br />
<br />
The FileAnalyzer (http://georgetown-university-libraries.github.io/File-Analyzer/) is an application designed to solve a number of library automation challenges:<br />
<br />
* validating digitized and reformatted files<br />
* validating vendor statistics for counter compliance<br />
* preparing collections of digital files for archiving and ingest<br />
* manipulating ILS import and export files<br />
<br />
The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census. After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform. Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.<br />
<br />
The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules. As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.<br />
<br />
The first half of this session will be targeted to potential users and developers. The second half of the session will be targeted towards developers who are interested in developing custom rules for the application.<br />
<br />
''Session Overview''<br />
* Overview of the application<br />
* Running sample file tests/transformations through the application<br />
* Compiling and building the application<br />
* Coding a custom file processing task<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
#Ray Schwartz<br />
# Michael Doran<br />
----<br />
<br />
===Collecting social media data with Social Feed Manager===<br />
'''Half-Day [Morning]'''<br />
<br />
Contacts: <br />
* Dan Chudnov, GW Libraries, dchud (at) gwu.edu<br />
* Dan Kerchner, GW Libraries, kerchner (at) gwu.edu<br />
* Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu<br />
<br />
Social media data is a popular material for research and a new format for building collections. What does it take to collect meaningfully from Twitter, Tumblr, YouTube, Weibo, Facebook, and other sites? We will:<br />
* Introduce options for collections, including both high- and low-end commercial offerings. Discuss what it means to collect these resources, covering boundaries, policies, and workflows required to develop a social media collection program in your institution.<br />
* Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them<br />
* Help you get started using the free [http://gwu-libraries.github.io/social-feed-manager Social Feed Manager] (SFM) app we're developing at GW to create your first collections. We’ll demo its use and demo a clean install (those w/environments can follow along)<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Declan Fleming<br />
# Esmé Cowles<br />
# Jason Stirnaman<br />
# Ray Schwartz<br />
# Liz Milewicz<br />
# Ranti Junus<br />
<br />
----<br />
<br />
=== Intro to Git ===<br />
'''"Half-Day [tbd - probably afternoon]"''' <br />
* Contact: Erin Fahy, Stanford University, efahy at stanford.edu<br />
* TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu<br />
<br />
This session will cover the fundamentals of git by discussing/going through (time allowing):<br />
* what is a distributed version control system<br />
* what is git and github<br />
* initializing a repo on a remote server/github<br />
* cloning an existing repo<br />
* creating a branch<br />
* contributing code to a repo<br />
* how to handle merge conflicts<br />
<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
# Ray Schwartz<br />
# Sam Kome<br />
# Paula Gray-Overtoom<br />
# Liz Milewicz<br />
# Michael Doran<br />
# Caitlin Christian-Lamb<br />
# [[User:RileyChilds|Riley Childs]]<br />
----<br />
<br />
=== Archival discovery and use ===<br />
'''Full Day''' <br />
<br />
Contacts: <br />
* Tim Shearer, UNC Chapel Hill, tshearer at email.unc.edu, <br />
* Will Sexton, Duke, will.sexton at duke.edu<br />
<br />
This is a full day pre-conference about archival collections and will cover the intersections of archives, workflows, technologies, discovery, and use.<br />
<br />
Morning agenda: focused talks around (but not limited to) issues such as:<br />
* Crowd-sourcing description to enhance collecitons<br />
* Linked data and authority<br />
* Mass digitization and sustainable workflows<br />
* Digitized objects in context (images and other objects in finding aids)<br />
* Too many cooks in the kitchen: versioning<br />
* Global-, intra-, and inter- discovery of archival materials via finding aids <br />
* and more...<br />
<br />
Afternoon agenda: Focused talks around specific tools followed by general discussion, connections, opportunities, aspirations, and planning.<br />
<br />
Tool examples:<br />
* Archivespace<br />
* STEADy<br />
* "RAMP" (Remixing Archival Metadata Project)<br />
* OpenRefine<br />
* Aeon<br />
<br />
''Interested in Attending''<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
<br />
Morning:<br />
* Julia Bauder<br />
<br />
Afternoon:<br />
* your name<br />
<br />
All day:<br />
<br />
# Josh Wilson<br />
# Sam Kome<br />
# Linda Ballinger<br />
# Caitlin Christian-Lamb<br />
# Laurie Lee Moses (seriously hard to decide here!)<br />
# David Bass<br />
# John Rees<br />
# Lynn Eaton<br />
# Hillel Arnold<br />
# Susan Ivey<br />
----<br />
<br />
===AV Content Slam===<br />
'''Half-Day [morning]'''<br />
Contacts:<br />
* Kara Van Malssen, kara (at) avpreserve.com<br />
* Lauren Sorenson, laurens (at) bavc.org<br />
* Steven Villereal , villereal (at) gmail.com<br />
A morning BarCamp/unconference for practitioners and coders who work with audiovisual content. The agenda will be attendee-driven, with a focus on sharing, synthesizing, and improving workflow strategies and documentation for software-based approaches to wrangling and providing access to audio and video content.<br />
Possible topics of discussion might include:<br />
* Use of format id and characterization/metadata extraction tools for AV<br />
* Creating and using time-based metadata<br />
* Managing (moving, fixity checking, etc) massive files (like uncompressed video)<br />
For a better idea of the topics and concerns that have informed some past AV-themed events, check out the event wikis for [http://wiki.curatecamp.org/index.php/CURATEcamp_AVpres_2013 CURATEcamp AVpres 2013] as well as the [http://wiki.curatecamp.org/index.php/Association_of_Moving_Image_Archivists_%26_Digital_Library_Federation_Hack_Day_2013 AMIA/DLF 2013 Hack Day] .<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:<br />
<br />
# A. Soroka<br />
<br />
----<br />
<br />
===OCLC Web Services Hackfest===<br />
<br />
"Half-Day" [afternoon]<br />
<br />
Contact: Shelley Hostetler, Community Manager, Developer Network hostetls[at]oclc.org<br />
<br />
This half-day hackfest will explore some of the OCLC Developer Network web services. We will provide an overview of some of the common topics such as the general REST-based architecture for most services and how to use some new authentication clients. The group can then decide to take a deep dive into a particular API and/or write a client library for the community.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:<br />
<br />
<br />
----<br />
<br />
<br />
===Obey the Testing Goat!: Test Driven Web Development From The Ground Up===<br />
'''Half-Day [tbd - probably afternoon]'''<br />
* Contact [[User:Mredar|Mark Redar]], mredar[at]gmail.com<br />
<br />
Test driven development is a proven method for producing better quality code. But I've found it hard to follow a strict TDD methodology when starting new web projects. How do you write that first test when there is no code or web pages created yet.<br />
<br />
In this session, we will follow the excellent book [http://shop.oreilly.com/product/0636920029533.do "Test-Driven Web Development with Python"] to create a simple web site in Django following TDD from the first character typed. Come ready to code and test. No prior knowledge of python or Django required.<br />
<br />
By the end of this session, you should be able to [http://www.obeythetestinggoat.com/ "Obey the Testing Goat"] from the start to finish for your next project.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:<br />
<br />
# Charlie Morris (NCSU)<br />
# Jason Stirnaman<br />
# Joshua Gomez<br />
# Liz Milewicz<br />
# Scott Hanrath<br />
# Mike Beccaria<br />
# Sean Aery<br />
# Carolina Garcia<br />
# Heidi Frank<br />
----<br />
<br />
===Summon Hackfest and ProQuest Discovery & Management Technologies Users Group ===<br />
<br />
Presenter: Eddie Newwirth and presenters from Summon libraries<br />
Contact: Scott Schuetze (first DOT last @ serialssolutions. com)<br />
<br />
The morning hackfest (10:30am-12pm) will be a great opportunity for libraries using the Summon service to share their creative customizations and code and exchange ideas about ways they can leverage the Summon API to better meet the needs of their users.<br />
<br />
The ProQuest Discovery & Management Technologies User Group (1pm-4pm) will feature updates from product managers, presentations by several libraries sharing different aspects of their experiences with ProQuest discovery and management services, and an interactive session designed to let you share your stories and discuss ideas.<br />
<br />
The Summon Hackfest and User Group are open to all libraries currently using ProQuest discovery and management services (Intota, Summon, Ulrich’s or the 360 suite of services), whether they are attending Code4Lib or are just in the area.<br />
<br />
----<br />
<br />
[[:Category:Code4Lib2014]]</div>MarkBreedlove