== Instructions ==Thank you for considering proposing a prePre-conference! Here conferences are a few details:NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions.
* We will be taking pre-conference proposals until '''November 7, 2014'''== Preconference Schedule ==* 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 See 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@columbiafurther information on each session.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
{| class=== Proposal formatting guidelines"wikitable sortable"|-! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1: ===30 PM - 4:30 PM)|-| '''Parlor A (30''') || Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable (9: Needs: projector, internet connection, and power strips) || Presentations workshop (1: Needs: projector/screen)|-| '''Parlor B (30)''' || Code Retreat (18: Needs whiteboard, dry-erase markers, projector) || Code Retreat (15: Needs whiteboard, dry-erase markers, projector) |-| '''Parlor C (30)''' || [[code4lib/Write The Docs barcamp]] (8: Needs: projector/screen, flipboard/whiteboard, power sources for laptops) || [[code4lib/Write The Docs barcamp]] (5)|-| '''Broadway I & II (70)''' || Linked Data Workshop (56: Bringing their own projector) || Intro to Git & possibly beyond (40: Needs: projector/screen)|-| '''Broadway III & IV (70)''' || Visualizing Library Data (60: Needs: projector) || Intro to Docker (52)|-| '''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) || CollectionSpace: Getting it up and running at your museum (5: Needs: Projector)|-| '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (25: Needs: internet/wifi, overhead projection) || Fail4Lib 2015 (13: Needs: projector/screen; Requested: Conference table seating - must be in this room - limit 20 attendants)|-| '''Galleria III (35)''' || Replace yourself with a painfully complex bash script...or try Ansible (20: Need projector) || A hands-on introduction to GeoBlacklight (19: Needs: projector, outlets; Requests: list of attendees)|-| '''Studio (35)''' || (Empty) || Dive into Hydra (29: Needs: projector/screen; Requests: classroom style seating)|-| '''Directors (35)''' || Code4Arc (20: Needs: projector) || Code4Arc (18: Needs: projector)|-| '''Council (45)''' || Delivering and Preserving GIS Data (10: Projector, Video connector for MacBook Pro, wifi, power outlets) || DPLA API Workshop (34: Bringing their own projector) |}
<pre>== Pre-conferences =====MORNING:======= Coding Custom Solutions for Every Department in the Library with File Analyzer ====* Terry Brady, Georgetown University Library, twb27@georgetown.edu
=== Preconference TitleThe 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 departmentOne of:* Transferring ILS invoices for the University Account System for the Acquisitions department '''"Full Day"''' * Delivering patron fines to the Bursar’s office for the Access Service department'''"Half Day [Morning]"''' * Summarizing student worker timesheet data for the Finance department'''"Half Day [Afternoon]"''' * Validating counter compliant reports for the Electronic Resources department* Preparing ingest packages for the Digital Services department* Validating checksums for the Preservation department
* Facilitator's name, affiliation, This hands on workshop will step through the components of the application framework and email address* Second facilitator's name, affiliation, email address, if second speakerthe process of customizing the application.
Abstract'''TRAINING OUTLINE'''* https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training-Code4Lib-2015
====Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable:====
* Karen A. Coombs, OCLC, coombsk@oclc.org
''Interested in Attending'' If Have you would be interested in attendingbuilt something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, please indicate by adding we will discuss a set of recommended best practices for how to share your name (but not email address, etccode.) here ###
</pre> == Pre-conference Proposals == Post We’ll start with coding standards and test writing so you can be confident of the quality of your ideas here! === Delivering code. Next we'll discuss inline documentation as a tool for developers and Preserving GIS Data === '''Half Day [Morning]'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.
==== Delivering and Preserving GIS Data ====
* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu
* Eliot Jordan, Princeton University
We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.
''Interested in Attending'[https://stanford.box.com/geohydra-code4lib2015 Slides]''' [http://slides.com/eliotjordan/practical-experience-with-geoserver/ Slides (GeoServer)]
If you would be interested in attending====Linked Data Workshop====* Karen Estlund, please indicate by adding your name (but not email addressUniversity of Oregon, etckestlund@uoregon.) hereedu* Tom Johnson, DPLA, tom@dp.la
# [[User:Ssimpkin|Sarah Simpkin]]# Vicky Steeves# Andrew Battista# Peggy Griesinger# === A handsDeveloper and metadata experts-on introduction to GeoBlacklight === '''Half Day [Afternoon]''' * Darren Hardy, Stanford University, drh@stanford.edu* Jack Reed, Stanford University, pjreed@stanford.edu GeoBlacklight is a discovery solution for geospatial focused linked data that builds on the successful Blacklight platformworkshop. Many libraries have collections of GIS Topics covered will include: linked open data principles, converting existing data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop "Delivering and Preserving GIS Data". ''Interested modeling linked data in Attending'' If you would be interested in attending, please indicate by adding your name (but not email address, etcDAMS.) here
# [[Userhttp:Ssimpkin|Sarah Simpkin]//goo.gl/QrUIYE LD Workshop Materials]# Vicky Steeves# Andrew Battista# Peggy Griesinger#
====RailsBridge: Intro to programming in Ruby on Rails==='''"Half-Day" [morning]'''=
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu
* Laney McGlohon, Stanford University, laneymcg@stanford.edu
* Additional instructors welcome
''HOME WORK: Please do in advance!! http://docs.railsbridge.org/installfest/''
To help the class run smoothly please complete the install fest before attending the class. If you have problems contact us!
Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.
RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].
''Interested in Attending'' If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here # Maura Carbone#Vicky Steeves# Peggy Griesinger# ==== Replace yourself with a painfully complex bash script...or try Ansible ==='''Half Day [Morning]'''=
* Chad Nelson, chad dot nelson @ lyrasis dot org
* Blake Carver, Blake dot carver @lyrasis dot org
Abstract:
[http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.
''Interested in Attending'' If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here### === Intro to Docker =Visualizing Library Data===='''Half Day [Whenever]''' * John FinkMatt Miller, McMaster University, john dot fink at gmail dot com* Francis Kayiwa, Kayiwa Consulting , francis dot kayiwa at gmail dot com Abstract: [http://docker.io Docker] ([http://journal.code4libmatthewmiller@nypl.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 setupNew York Public Library, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end. ''Interested in Attending''NYPL Labs
1Visualizing 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. Jim Hahn
=== Code Retreat FULL DAY:==='''Full Day'''
====Code Retreat====
* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu
* Additional facilitators welcome; Especially if you have CodeRetreat experience.
Abstract:
"Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.
Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time." [http://coderetreat.org/about About Code Retreat]
''Interested in Attending'' === Presentations workshop =Code4Arc == '''"Half Day [Afternoon]"''' (but could be expanded based on interest) * Chris Beer, Stanford University, cabeer@stanford.edu* Additional facilitators welcome. This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc. ''Interested in Attending'' If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here #Vicky Steeves## === Dive into Hydra === One of:'''"Half Day [Afternoon]"''' * Justin Coyne, Data Curation Experts, justin@curationexperts.com* Bess Sadler, Stanford University, bess@stanford.edu Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend "RailsBridge" prior to this workshop. ''Interested in Attending'' If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here # Maura Carbone# Peggy Griesinger# === code4lib/Write The Docs barcamp === One of:'''"Full Day"''', with options for jumping in for half a day * code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu* Write the Docs contacts: TBA Abstract Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breath 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://docs.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'''### '''Afternoon'''### === Linked Data Workshop === One of:'''"Half Day [morning]"''' * Karen Estlund, University of Oregon, kestlund@uoregon.edu* Tom Johnson, DPLA, tom@dp.la Abstract: Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS. If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here # Logan Cox## === Code4Arc === One of:'''"Full Day"''' (with options for half day participation)
* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com
* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org
* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com
Abstract:
What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how?
The schedule may include the following:
* Panel type conversations about the State of Art in Archives
* Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed
When signing up, please indicate if you are an end-user or a developer.
If you would be interested ''Interested in attending, please indicate by adding your name (but not email address, etc.) hereAttending''
# Laney McGlohon - developer
#Shaun Ellis#Ryan Rotter - sysadmin/developer# Matt LaChance# Maureen Callahan - archivist, often-times product owner# Liza Harrell-Edge - end-user# Jessica Venlet - end-user/archivist (can be there in the afternoon)# Andrew Berger - "digital" archivist# Bill Kelm - sysadmin# Jeremy Floyd - end-user (archivist turned metadata librarian)# Sara Amato (morning only) - end-user# Julie Hardesty (afternoon only) - end-user (metadata librarian)
=== Fail4Lib 2015 =[http://wiki.code4lib.org/Code4lib/Write_The_Docs_barcamp code4lib/Write The Docs barcamp]===='''Half Day [TBD* code4lib wrangler: Becky Yoose, probably afternoon]'''yoosebec at grinnell dot edu* Write the Docs contacts: TBA
* Andreas Orphanides, akorphan (at) ncsu'''Event page where you can find the latest information and.edu* Jason Casden, jmcasden .. documentation(at!) ncsuat [http://wiki.code4lib.eduorg/Code4lib/Write_The_Docs_barcamp]'''
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.
Failure. Failure never changes. Since failure is an inescapable part of our professional workRemember, it's important to be familiar with itlike metadata, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as documentation is 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 love note 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 fearfuture.
This year's preconference will include new case studies and an improved discussion formatMore information about Write the Docs at http://conf. Repeat customers are welcome! (Fail early, fail oftenwritethedocs.org/ There will be a nominal fee (t/b/d)for non-Code4LibCon attendees (subject to organizer approval).
The schedule may include the following===AFTERNOON:======= A hands-on introduction to GeoBlacklight ====* Darren Hardy, Stanford University, drh@stanford.edu* Jack Reed, Stanford University, pjreed@stanford.edu
* Case studiesGeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Avoid our own mistakes by bearing witness to the failures Many libraries have collections of othersGIS data that aren’t easily discoverable.* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.* Group therapy. Vent about your own experiences in This will be a judgmenthands-free setting. Explore how we can make our organizations less risk-averse on workshop, focused on installing and more failure-tolerantrunning GeoBlacklight which builds on the morning workshop "Delivering and Preserving GIS Data".
''Interested in attending''==== CollectionSpace: Getting it up and running at your museum ====* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org* Becky Escamilla, Oakland Museum of California, rescamilla@museumca.org
If you would be This workshop is designed for anyone interested in attending, please indicate by adding your name or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (but not email addressmuseum, library, special collection, gallery, etc.) hereFor 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.
=== Coding Custom Solutions If possible, please bring a laptop capable of running the latest version of VirtualBox (www.virtualbox.org). I've prepared a VirtualBox machine for Every Department in the Library workshop that I will share with File Analyzer === One you at the beginning of:'''"Half Day [Morning]"''' the session.
==== Dive into Hydra ====* Terry BradyJustin Coyne, Georgetown University LibraryData Curation Experts, twb27justin@georgetowncurationexperts.educom*
AbstractHydra 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.
The Georgetown University Library has shared an application called the [http==== DPLA API Workshop://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.====* Audrey Altman, DPLA* Mark Breedlove, DPLA* Mark Matienzo, DPLA* Tom Johnson, DPLA
* Analyzing Marc Records for The Digital Public Library of America API workshop guides attendees through the Cataloging department* Transferring ILS invoices for the University Account System for the Acquisitions department * Delivering patron fines process of creating an app based on DPLA's free, public API. The API provides access to the Bursar’s office 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 Access Service department* Summarizing student worker timesheet data for capabilities of the Finance department* Validating counter compliant reports DPLA API, available toolsets, and tips for using records from the Electronic Resources department* Preparing ingest packages for the Digital Services department* Validating checksums for API effectively. Members of DPLA's technology team will be on hand to help the Preservation departmentgroup build their first application, and answer questions about tools and content.
This hands on workshop will step through the components of the application framework'''[http://bit. Workshop participants will install ly/c4l15-dpla-api Slides and develop custom File Analyzer tasks in this session.resources]'''
The workshop agenda will loosely follow the [https://github==== Fail4Lib 2015 ====* Andreas Orphanides, akorphan (at) ncsu.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014]edu* Jason Casden, jmcasden (at) ncsu.edu
'''[https://docs.google.com/presentation/d/1pdatzBjVIs1YDQL3CUhWjvSj_u5Y-9pOLZvb-PAdUaU/edit?usp=sharing SLIDES]'''
Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'Interested ll talk about our own experiences with projects gone wrong, explore some famous design failures in Attendingthe real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.
If you would be interested in attending, please indicate by adding your name This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (but not email addressFail early, etcfail often.) here
#The schedule may include the following:#* Case studies. Avoid our own mistakes by bearing witness to the failures of others.#* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.* Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.
=== Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: === '''Half Day [Whenever]'Readings''
* Karen A'''Case Study 1: The Healthcare. Coombs, OCLC, coombsk@oclc.orggov rollout'''
AbstractHave you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code* [http://www. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for theverge.com/us-world/2013/12/3/5163228/healthcare-gov-obamacare-website-shows-how to share your code.-government-can-do-tech-better Adrianne Jeffries We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as (The Verge): Thanks a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distributionlot, updates and community feedbackhealthcare.gov]
''Interested in Attending''* [http://www.forbes.com/sites/lorenthompson/2013/12/03/healthcare-gov-diagnosis-the-government-broke-every-rule-of-project-management/ Loren Thompson (Forbes): Healthcare.gov diagnosis: the government broke every rule of project management]
If you would be interested in attending* Optional, please indicate by adding your name nice summary: [http://npengage.com/nonprofit-technology/lessons-learned-from-the-healthcare-gov-rollout/ Bo Crader (but not email addressnpEngage): Lessons learned from the healthcare.gov rollout]* Optional, etcvery enterprisey: [http://www.enterprisetech.com/2014/04/04/hyperscale-lessons-healthcare-gov/ Alex Woodie (EnterpriseTech) here: The hyperscale lessons of healthcare.gov]
# Peggy Griesinger##'''Case Study 2: The Challenger disaster'''
* [http://ethics.tamu.edu/Portals/3/Case%20Studies/Shuttle.pdf Engineering Ethics: The Space Shuttle Challenger disaster (case study instructor's guide)]
** 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.
=== UXtravaganza ==='''"Half or Full Day * [Based on Interest?, Morninghttp:/Afternoon Doesn’t Matter/www.nbcnews.com/id/3077541/ns/technology_and_science-space/t/shuttle-report-blames-nasa-culture/ NBC News: Shuttle report blames NASA culture]"'''
* William HicksOptional, University of North Texas, Williamgood technical detail: [http://en.hicks@untwikipedia.eduorg/wiki/Space_Shuttle_Challenger_disaster Wikipedia: Space Shuttle Challenger disaster]* Volunteers?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)]
Abstract==== Intro to Docker ====* John Fink, McMaster University, john dot fink at gmail dot com* Francis Kayiwa, University of Maryland Libraries , fkayiwa at umd dot edu
I’m envisioning a 1[http:/2 of full day for front/docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-end developerslevel virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, content strategy peopleincluding setup, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state importing of current researchcontainers, development workflows and play with each other’s sitesdeploying. A half day seems doableKnowing when Docker is useful and when it isn't will also be covered. Ideally, but if there’s significant enough interest we could push for a full? Here are a few of every attendee will have ample experience creating and running their own Docker instances by the things I think might be interesting to see happen:end.
==== Intro to Git & possibly beyond ====* '''Analytics Share-fest:''' A few volunteers demonstrate data about their websitesErin Fahy, catalogsStanford University, archival/digital collectionsefahy@stanford. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutionsedu* Shaun Trujillo, in certain kinds of systemsMount Holyoke College, etc. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeingstrujill@mtholyoke.edu
* '''UX Best Practices Catch Up:''' This spring I had We can start with the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most basics of Git and discuss ways in which was focused on mobileit can help you version control just about any file, not just code. I could distill down Points we can go over:* What is a lot of Distributed Version Control System?* What's the information into an short presentationdifference between Git and Github. Since this is a constantly moving area of research it would be nice com?* How to see a few people do other similar short presentations initialize new Git projects locally and on some current trendsa remote server/findings relevant Github* Cloning/Forking existing projects and keeping up to librariesdate* The wonderful world of Git branches* Interactive rebasing* Contributing code to existing projects & what pull requests are* How to handle merge conflicts* Overview of workflows and branch best practices* (time allowing) Advanced git: pre/post hooks, searchsubmodules, etc.anything else?
==== Presentations workshop ====* '''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 sizesChris Beer, OSStanford University, OS Versions, + Google Glasscabeer@stanford. 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 servicesedu* Additional facilitators welcome.
* '''The Eye’s Have It.''' The UNT Libraries This is also in the process of acquiring an eye tracker and software a preconference session intended 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-conferencefirst time Code4Lib speakers, we could try to do some live demos on each other’s sites; i.e. You nominate a site/servicehabitual procrastinators, someone in the audience volunteers to wear the deviceexperienced speakers, 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 exercisesthinking about offering lightning talks, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running If you're preparing a usability test, that would be rad. But we need you to step up and steer part of the time talk for most of this year's Code4Lib, this workshop is an opportunity to workrehearse your presentation, so if you are interested in some aspectget feedback from peers, and especially if you want to volunteer to lead a bit of get familiar with the time, contact me. ''Interested in Attending'' If you would be interested in attending, please indicate by adding yourname (but not email addresspresentation technology, etc.) here ###
[[Category:Code4Lib2015]]