Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions.
== Preconference Schedule (draft) ==
Session titles in Italics means they have not been confirmed yet by presenters/workshop leaders. This is a draft, and there There may be some room switching when registration opens. Rooms will be confirmed the week before Code4Lib. See below for further information on each session.
{| class="wikitable sortable"
| '''Council (45)''' || Delivering and Preserving GIS Data (Projector, Video connector for MacBook Pro, wifi, power outlets) || A hands-on introduction to GeoBlacklight (Needs: 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 ====
Morning, Galleria I
* Terry Brady, Georgetown University Library, twb27@georgetown.edu
=== The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.* Analyzing Marc Records for the Cataloging department* Transferring ILS invoices for the University Account System for the Acquisitions department * Delivering 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.edu* Jack Reed, Stanford University, pjreed@stanford Workshop participants will install and develop custom File Analyzer tasks in this session.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 The workshop you agenda will have a working SDI! This workshop is a compliment to loosely follow the GeoBlacklight workshop in the afternoon[https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].
''Interested in Attending''
# Megan Kudzia
If you would be interested in attending, please indicate by adding your name ====Confessions of the (but not email addressAccidental) Code Hoarder: How to make your Code Sharable:====Morning, etcParlor A* Karen A.) hereCoombs, OCLC, coombsk@oclc.org
# [[User:Ssimpkin|Sarah Simpkin]]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.# Vicky Steeves # Andrew BattistaWe’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback. ''Interested in Attending''
# Peggy Griesinger
# Ray Schwartz##### === A hands-on introduction to GeoBlacklight === '''Half Day [Afternoon]'''Josh Wilson
==== Delivering and Preserving GIS Data ====
Morning, Council
* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu
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''
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
# [[User:Ssimpkin|Sarah Simpkin]]
# Vicky Steeves
# Andrew Battista
# Peggy Griesinger
#
#
#
#
#
#
===RailsBridge: Intro to programming in Ruby on Rails=Linked Data Workshop====Morning, Studio* Karen Estlund, University of Oregon, kestlund@uoregon.edu* Tom Johnson, DPLA, tom@dp.la
'''"HalfDeveloper and metadata experts-Day" [morning]'''focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.
''Interested in Attending''
# Logan Cox
# Ray Schwartz
# Chris Hallberg
# Derek Merleaux
# Steven Anderson
# Eben English
# Mark Mounts
# Heather Pitts
# Andrew Woods
# Carol Bean
# Naomi Dushay (probably)
# David Lacy
# David Uspal
# David Bass
# Brendan Quinn
# Chrissy Rissmeyer
# Sharon Clapp
# Anjanette Young
====RailsBridge: Intro to programming in Ruby on Rails====
Morning, Galleria II
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu
* Laney McGlohon, Stanford University, laneymcg@stanford.edu
''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
# Mark Jarrell
# Bojana Skarich
=== Replace yourself with a painfully complex bash script...or try Ansible ===
'''Half Day [Morning]'''
====Replace yourself with a painfully complex bash script...or try Ansible====
Morning, Galleria III
* Chad Nelson, chad dot nelson @ lyrasis dot org
* Blake Carver, Blake dot carver @lyrasis dot org
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''
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
# Ray Schwartz
# Coral Sheldon-Hess
# Anjanette Young
=== Intro to Docker =Visualizing Library Data====Morning, Grand Ballroom II* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs
'''Half Day [Whenever]''' * John FinkVisualizing your institution’s data can give new insight about your holding’s strengths, McMaster University, john dot fink at gmail dot com* Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com Abstract: [http://dockerweaknesses and outliers.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 yearThey can also provide potential new avenues for discovery and access. This workshop half day session will take you through the basic features of Docker, including setup, importing of containers, development workflows and deployingfocus on programmatically visualizing library metadata. Knowing when Docker is useful and when it isn't Emphasis will also be coveredon creating web-based visualizations utilizing libraries such as d3. Ideally, every attendee js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have ample experience creating template, sample code and running methodologies enabling them to start producing visualization with their own Docker instances by the enddata.
''Interested in Attending''
# Jim HahnAshley Blewer!# 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)Ranti Junus
# Eric Phetteplace
# Esther VerreauJoshua Gomez
# Charlie Morris
# Anna Headley (voting for afternoon, compliments ansible)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
# Sara Amato
# David Lacy
# David Uspal
# Matt Bernhardt
# Brendan Quinn# Anjanette YoungGreg Bem (Morning only)
=== Code Retreat FULL DAY:=== '''Full Day'''
====Code Retreat====
Full Day, Parlor B
* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu
* Additional facilitators welcome; Especially if you have CodeRetreat experience.
Abstract:
"Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.
''Interested in Attending''
# Mike Giarlo
# Charlie Morris
# James Van Mil
# Glen Horton
#
#
=== Presentations workshop =Code4Arc ==== '''"Half Full Day [Afternoon]"''' (but could be expanded based on interest), Directors* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com
* Chris BeerWhat does it mean to Code for Archives? Is it different than coding for libraries, Stanford Universityand if so, cabeer@stanford.edu* Additional facilitators welcome.how?
This Code4Lib is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If wonderful and successful model (youmust agree or you wouldn're preparing a talk for this year's Code4Lib, t be reading this ). This workshop is an opportunity attempt to rehearse your presentationcreate a space to replicate the model in an Archival context. A space to talk about development for archives, get feedback from peers, get familiar with and the presentation technologyparticular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, etcand between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems. ''Interested in Attending''
If you would be interested The schedule may include the following:* Panel type conversations about the State of Art in attendingArchives * Case Studies - discussion of workflows at specific institutions, please indicate by adding your name including gaps in tools and how those are being addressed or could be addressed * Tool Demos - access to demos of some of the open source tools used in an Archival Context (but not email addressexamples include ArchivesSpace, Archivematica, BitCurator, etc.AtoM) here
#Vicky Steeves#########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.
=== Dive into Hydra === '''"Half Day [Afternoon]"''' * Justin CoyneWhen signing up, 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 openplease indicate if you are an end-source software. Dive into Hydra is user or 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 workshopdeveloper.
''Interested in Attending''
# Laney McGlohon - developer
# Shaun Ellis
# Ryan Rotter
# Matt LaChance
# Maureen Callahan - archivist, often-times product owner
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# Scott Fisher# Brian E. Davis## ==== code4lib/Write The Docs barcamp ==== '''"Full Day"'''day, with options for jumping in for half a dayParlor C
* 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'''
#
#
#
#
#
#
#
#
#
#
'''Morning'''
# Whitni Watkins
# Jason Raitz
#
#
#
#
#
#
'''Afternoon'''
# Kevin S. Clarke
# Chris Sharp
#
#
#
#
#
#
#
=== Linked Data Workshop AFTERNOON:======= A hands-on introduction to GeoBlacklight ====Afternoon, Council* Darren Hardy, Stanford University, drh@stanford.edu* Jack Reed, Stanford University, pjreed@stanford.edu
'''"Half Day [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"''' .
* Karen Estlund, University of Oregon, kestlund@uoregon.edu''Interested in Attending''* Tom Johnson, DPLA, tom@dp.la# [[User:Ssimpkin|Sarah Simpkin]]# Vicky Steeves# Andrew Battista# Peggy Griesinger
Abstract==== CollectionSpace:Getting it up and running at your museum ====Afternoon, Galleria II* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org* Becky Escamilla, Oakland Museum of California, rescamilla@museumca.org
Developer This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org Participants will be walked through the process of installing the software and metadata expertsperforming basic configuration work on a stand-focused linked data workshopalone instance of CollectionSpace. Topics covered Participants will include: linked open data principleslearn how to create user accounts, converting existing dataset up basic roles and permissions, and modeling linked data in DAMSmay 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 # Logan Cox# Ray Schwartz# Chris Hallberg# Derek Merleaux# Steven Anderson# Eben English# Mark Mounts# Heather Pitts# Andrew Woods# Carol Bean# Naomi Dushay (probably)# David Lacy# David Uspal# David Bass# Brendan Quinn# Chrissy RissmeyerTerry Brady
# Sharon Clapp
# Anjanette Young
=== Code4Arc =Dive into Hydra ====Afternoon, Studio* Justin Coyne, Data Curation Experts, justin@curationexperts.com* Bess Sadler, Stanford University, bess@stanford.edu
Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend "Full DayRailsBridge"''' (with options for half day participation)prior to this workshop.
* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com''Interested in Attending''* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com# Maura Carbone* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org# Peggy Griesinger# Mike Price# Jean Rainwater# Sara Amato# David Bass# Scott Fisher* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail# Brian E.comDavis
Abstract==== DPLA API Workshop:====Afternoon, Grand Ballroom II* Audrey Altman, DPLA* Mark Breedlove, DPLA* Mark Matienzo, DPLA* Tom Johnson, DPLA
What does it mean 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 Code for Archives? Is it different than coding for over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and if so, how? Code4Lib is museums in a wonderful and successful model (you must agree or you wouldn't be reading this)common metadata format. This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development designed for archivespeople of all technical skill levels and will cover API basics, and the particular challenges capabilities of developing archival systems. Topics to discuss include Integration between different Archival software toolsthe DPLA API, and between Archival tools/workflows and larger institutional tools like institutional repositoriesavailable toolsets, discovery and access systemstips for using records from the API effectively. The schedule may include the following: * Panel type conversations about the State Members of Art in Archives * Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could DPLA's technology team will be addressed * Tool Demos - access on hand to demos of some of help the open source tools used in an Archival Context (examples include ArchivesSpacegroup build their first application, Archivematica, BitCurator, AtoM) Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of answer questions about tools available to touch and play withcontent. When signing up, please indicate if you are an end-user or a developer. ''Interested in Attending''
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# Laney McGlohon - developerSteven Anderson
# Shaun Ellis
# Ryan RotterSarah Simpkin# Matt LaChanceMark Jarrell# Maureen Callahan - archivist, often-times product ownerHeather Pitts#Kathryn Stine#Andrew Woods### === Fail4Lib 2015 === '''Half Day [TBD, probably afternoon]'''Greg Bem
==== Fail4Lib 2015 ====
Afternoon, Galleria I
* Andreas Orphanides, akorphan (at) ncsu.edu
* Jason Casden, jmcasden (at) ncsu.edu
Abstract:
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.
The schedule may include the following:
* Case studies. Avoid our own mistakes by bearing witness to the failures of others.
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.
''Interested in attending''
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
# Ray Schwartz
# Charlie Morris
# Bret Davidson
# Hannah Sommers
#
#
#
#
#
=== Coding Custom Solutions for Every Department in the Library with File Analyzer =Intro to Docker ====Afternoon, Galleria III * John Fink, McMaster University, john dot fink at gmail dot com'''"Half Day [Morning]"''' * Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com
* Terry Brady, Georgetown University Library, twb27@georgetown[http://docker.edu Abstract The Georgetown University Library has shared an application called the io Docker] ([http://georgetown-university-librariesjournal.githubcode4lib.ioorg/File-Analyzerarticles/ File Analyzer9669 jbfink code4lib journal article] ) is an open source Linux operating system-level virtualization framework that has allowed us to build custom solutions for nearly every department in seen great uptake over the librarypast year. * Analyzing Marc Records for the Cataloging department* Transferring ILS invoices for the University Account System for the Acquisitions department * Delivering patron fines to the Bursar’s office for the Access Service department* Summarizing student worker timesheet data for the Finance department* Validating counter compliant reports for the Electronic Resources department* Preparing ingest packages for the Digital Services department* Validating checksums for the Preservation department This hands on workshop will step take you through the components basic features of the application frameworkDocker, including setup, importing of containers, development workflows and deploying. Workshop participants will install Knowing when Docker is useful and develop custom File Analyzer tasks in this sessionwhen it isn't will also be covered. The workshop agenda Ideally, every attendee will loosely follow have ample experience creating and running their own Docker instances by the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014]end.
''Interested in Attending''
# Jim HahnIf you would be interested in attending, please indicate by adding your name (but not email address, etc.) here# Joshua Gomez# Bobbi Fox# Ray Schwartz
# Megan Kudzia
######### === Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: === '''Half Day [Whenever]''' * Karen A. Coombs, OCLC, coombsk@oclc.org 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. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code. We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how autoCoral Sheldon-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback. ''Interested in Attending'' If you would be interested in attending, please indicate by adding your name Hess (but not email address, etc.) here # Peggy Griesinger# Ray Schwartz# Josh Wilson####### === CANCELLED: ''UXtravaganza'' ==='''"Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]"''' * William Hicks, University of North Texas, William.hicks@unt.edu* Volunteers? Abstract I’m envisioning a 1/2 of full day for front-end developers, content strategy people, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state of current research, 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: * '''Analytics Share-fest:''' 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 pleeeeaaase put this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etc. 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 different slot 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.Ansible!) * '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an [http://labup.org Open Device Lab]. 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 Browser-based Inspector Tools, Browser-Cams, or other testing services. * '''The Eye’s Have It.''' The UNT Libraries is also # Cary Gordon (uses Docker in the process of acquiring an eye tracker and software for usability and other gaze-based research studies. We’ll take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before the conference. Assuming we can get our act together learning the device and can get past the technical hurdles of setting it up at the pre-conference, we could try to do some live demos production on each other’s sites; i.e. You nominate a site/service, someone in the audience volunteers to wear the device, and we all watch them struggle do the tasks you request on a projector. Rinse. Lather. Repeat. It would hardly be scientific, but it sure would be fun. As a backup, if we have some sites nominated beforehand, I can run a few students at my library through some tasks here 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 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 me. ''Interested in Attending'' If you would be interested in attending, please indicate by adding yourname (but not email address, etc.AWS) here # Ray SchwartzEric Phetteplace# Andy MardesichEsther Verreau# Chelsea LobdellCharlie Morris# Eben English Anna Headley (1/2 dayvoting for afternoon, compliments ansible)# Shaun Ellis (as attendee or volunteer)# Whitni Watkins (as attendee or volunteer)Mark Mounts#Matt Critchlow#Ray Henry#Eric Frierson#Sara Amato# David Lacy=== Intro to Git & possibly beyond ===# David Uspal # Matt Bernhardt'''Half Day [Whenever]'''# Brendan Quinn# Anjanette Young
==== Intro to Git & possibly beyond ====
Afternoon, Parlor A
* Erin Fahy, Stanford University, efahy@stanford.edu
* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu
We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:
* What is a Distributed Version Control System?
* What's the difference between Git and Github.com?
''Interested in Attending''
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
# Jeannie Graham
# Derek Merleaux
# Emily Lynema
# Brian E. Davis
#
#
=== Visualizing Library Data = Presentations workshop ==== '''"Half Day [Morning||Afternoon]"''' , Grand Ballroom I* Chris Beer, Stanford University, cabeer@stanford.edu* Additional facilitators welcome.
* Matt MillerThis is a preconference session intended for first time Code4Lib speakers, matthewmiller@nypl.orghabitual procrastinators, New York Public Libraryexperienced speakers, NYPL Labs Visualizing your institution’s data can give new insight those thinking about your holding’s strengthsoffering lightning talks, weaknesses and outliersetc. They can also provide potential new avenues If you're preparing a talk 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 templatethis year's Code4Lib, sample code and methodologies enabling them this workshop is an opportunity to start producing visualization rehearse your presentation, get feedback from peers, get familiar with their own data. ''Interested in Attending'' If you would be interested in attending, please indicate by adding your name (but not email addressthe presentation technology, 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# Greg Bem (Morning only) === 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 for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org
Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.
''Interested in Attending''
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here # Terry Brady# Sharon Clapp######## === DPLA API Workshop: === '''Half Day [Afternoon]''' * Audrey Altman, DPLA* Mark Breedlove, DPLA* Mark Matienzo, DPLA* Tom Johnson, DPLA The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content. If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here # Ranti Junus# Jean Rainwater# Mita Williams# Margaret Heller# Bohyun Kim# Steven Anderson# Shaun Ellis# Sarah Simpkin# Mark Jarrell# Heather Pitts# Kathryn Stine# Andrew Woods# Greg BemVicky Steeves
[[Category:Code4Lib2015]]