<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.code4lib.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=AshleyBlewer</id>
		<title>Code4Lib - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.code4lib.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=AshleyBlewer"/>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/Special:Contributions/AshleyBlewer"/>
		<updated>2026-04-29T11:17:23Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.26.2</generator>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=User:AshleyBlewer&amp;diff=43892</id>
		<title>User:AshleyBlewer</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=User:AshleyBlewer&amp;diff=43892"/>
				<updated>2016-02-08T18:10:06Z</updated>
		
		<summary type="html">&lt;p&gt;AshleyBlewer: becoming a user&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;hello!&lt;/div&gt;</summary>
		<author><name>AshleyBlewer</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2016_Conference_Volunteers&amp;diff=43891</id>
		<title>2016 Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2016_Conference_Volunteers&amp;diff=43891"/>
				<updated>2016-02-08T18:09:16Z</updated>
		
		<summary type="html">&lt;p&gt;AshleyBlewer: adds me to video committee (it's troo!)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Code4Lib 2016 Volunteers sign-up page.  As conference plans evolve, the page will be periodically updated with new opportunities to volunteer.  When you sign up please either include some way to contact you or send your contact information to Kathleen Haley (Chair for Volunteers) at KHaley AT mwa DOT org.&lt;br /&gt;
&lt;br /&gt;
For general questions, or if you identify a volunteer need not covered in the list below, feel free to contact Kathleen or David Uspal (LPC Committee Contact for Volunteers) at david DOT uspal AT villanova DOT edu.&lt;br /&gt;
&lt;br /&gt;
== Welcome Wagon/Concierge ==&lt;br /&gt;
&lt;br /&gt;
Helps with greeting newcomers, directing people to evening activities and local points of interest, etc. and being generally awesome to the community.&lt;br /&gt;
*  Megan Kudzia&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
== Conference Logistics ==&lt;br /&gt;
&lt;br /&gt;
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.&lt;br /&gt;
&lt;br /&gt;
Sunday:&lt;br /&gt;
* Katherine Lynch&lt;br /&gt;
* Lauren Gala&lt;br /&gt;
* Chad Nelson&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Monday:&lt;br /&gt;
* Lauren Gala&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
== Preconference Setup ==&lt;br /&gt;
&lt;br /&gt;
Help manage preconference sessions, setting up projectors, etc.&lt;br /&gt;
&lt;br /&gt;
Sheraton Society Hill (Conference Hotel):&lt;br /&gt;
* Lauren Gala&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Chemical Heritage Foundation:&lt;br /&gt;
* Anna Headley (CHF contact)&lt;br /&gt;
* Michelle DiMeo (CHF contact)&lt;br /&gt;
&lt;br /&gt;
Franklin Hall:&lt;br /&gt;
* Scott Ziegler (venue contact at APS)&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
&lt;br /&gt;
Answering general questions on Twitter and IRC:&lt;br /&gt;
* Christina Harlow&lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ask questions on mic on behalf of community (because of distance, mic aversion, etc)&lt;br /&gt;
&lt;br /&gt;
Tuesday:&lt;br /&gt;
* [[User:Todrobbins|Tod Robbins]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday:&lt;br /&gt;
* Christina Harlow&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thursday:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Livestream ==&lt;br /&gt;
Volunteers for the livestream will assist the livestream technician with conferencee streaming.  Their main duty will be to serve as a backup minder of the equipment in case the technician needs to step aside for a break.&lt;br /&gt;
&lt;br /&gt;
Technician/on-call: &lt;br /&gt;
* [[User:AshleyBlewer|Ashley Blewer!]] (@ablwr)&lt;br /&gt;
&lt;br /&gt;
Tuesday AM:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Tuesday PM:&lt;br /&gt;
* Francis Kayiwa&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday AM:&lt;br /&gt;
* [[User:Todrobbins|Tod Robbins]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday PM:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thursday AM:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
== IRC (Technical) ==&lt;br /&gt;
&lt;br /&gt;
Access:&lt;br /&gt;
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people.&lt;br /&gt;
* Mx Matienzo (anarchivist)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Helper:&lt;br /&gt;
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Registration Desk ==&lt;br /&gt;
Assists with handing out registration materials to attendees.&lt;br /&gt;
&lt;br /&gt;
Monday AM (8:00-9:30):&lt;br /&gt;
* Shaun Ellis&lt;br /&gt;
* Katherine Lynch&lt;br /&gt;
&lt;br /&gt;
Monday PM (12:00-1:30):&lt;br /&gt;
* Megan Kudzia&lt;br /&gt;
* Katherine Lynch&lt;br /&gt;
&lt;br /&gt;
Tuesday AM (7:00-9:30):&lt;br /&gt;
* Lauren Gala&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
Tuesday AM:&lt;br /&gt;
* David Lacy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Tuesday PM:&lt;br /&gt;
* Shaun Ellis&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday AM:&lt;br /&gt;
* Anna Headley&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday PM:&lt;br /&gt;
* Dre&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thursday AM:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
== Session Timers ==&lt;br /&gt;
&lt;br /&gt;
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop or tablet with a stopwatch program).  It's good to have two people in each slot to back each other up in case of machinery failure.&lt;br /&gt;
&lt;br /&gt;
Tuesday AM:&lt;br /&gt;
* Francis Kayiwa&lt;br /&gt;
* Christina Harlow&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Tuesday PM:&lt;br /&gt;
* Lauren Gala&lt;br /&gt;
* Katherine Lynch&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday AM:&lt;br /&gt;
*  Lauren Gala&lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday PM:&lt;br /&gt;
*  Lauren Gala&lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thursday AM:&lt;br /&gt;
*  Lauren Gala&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
== The Whatever Crew ==&lt;br /&gt;
Volunteers who are willing to help with various tasks as needed during the conference. &lt;br /&gt;
* Dre&lt;br /&gt;
* Katherine Lynch&lt;br /&gt;
* [[User:Todrobbins|Tod Robbins]]&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2016]]&lt;/div&gt;</summary>
		<author><name>AshleyBlewer</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2016_Conference_Committees&amp;diff=43767</id>
		<title>2016 Conference Committees</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2016_Conference_Committees&amp;diff=43767"/>
				<updated>2016-01-10T22:17:14Z</updated>
		
		<summary type="html">&lt;p&gt;AshleyBlewer: adds me to video committee (it's troo!)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2016 Committees =&lt;br /&gt;
&lt;br /&gt;
''Many hands make for light work.''&lt;br /&gt;
&lt;br /&gt;
Hosting a conference is incredibly complex, and it cannot be done without the help of the entire community.  If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2016 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact).  Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary).  The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc.  Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.&lt;br /&gt;
&lt;br /&gt;
We will assign a local contact (LPC) to each committee.&lt;br /&gt;
&lt;br /&gt;
== Location and Dates ==&lt;br /&gt;
&lt;br /&gt;
* Location: Old City District of Philadelphia, PA&lt;br /&gt;
* Dates: March 7-10, 2016&lt;br /&gt;
** Pre-conferences - &lt;br /&gt;
** Main meeting - &lt;br /&gt;
** Post conference activities?&lt;br /&gt;
&lt;br /&gt;
== Local Planning Committee ==&lt;br /&gt;
This committee is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.&lt;br /&gt;
&lt;br /&gt;
*  David Lacy (Villanova) - Primary Contact (v)&lt;br /&gt;
*  Chad Nelson - Secondary Contact (v)&lt;br /&gt;
*  Anna Headley (Chemical Heritage Foundation) - Documentarian (v)&lt;br /&gt;
*  [[User:Sdellis|Shaun Ellis]] (Princeton)  (v)&lt;br /&gt;
*  Katherine Lynch (Temple) (v)&lt;br /&gt;
*  Stephen Ng (Temple)&lt;br /&gt;
*  Brett Bonfield (Collingswood Public)&lt;br /&gt;
*  Lauren Gala (UPenn)&lt;br /&gt;
*  David Uspal (Villanova) (v)&lt;br /&gt;
*  Chris Clement (Drexel)&lt;br /&gt;
&lt;br /&gt;
== Website Working Group ==&lt;br /&gt;
This group will focus on content strategy (in collaboration with the Documentation Committee) and feature implementations to improve the overall user experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).  &lt;br /&gt;
&lt;br /&gt;
[[Website Working Group Documents|Website Working Group Documents]]&lt;br /&gt;
&lt;br /&gt;
* Shaun Ellis (Princeton) - Primary Contact&lt;br /&gt;
* [[User:LukeAeschleman| Luke Aeschleman]] (UNC - Chapel Hill | Health Sciences Library) - Secondary Contact&lt;br /&gt;
*  [[User:jtidal|Junior Tidal]] (New York City College of Technology)&lt;br /&gt;
*  [[User:BillMcMillin|Bill McMillin]] (Pratt Institute) - Documentarian&lt;br /&gt;
*  [[User:Sdellis|Shaun Ellis]] (Princeton) - LPC Contact (v)&lt;br /&gt;
* [[User:Phette23|Eric Phetteplace]] (Cal College of the Arts)&lt;br /&gt;
*  [[User:Sarahshealy| Sarah Shealy]] (Greenville (SC) County Public Library)&lt;br /&gt;
*  [[User:JennC| Jennifer Colt]] (Cornell University Library)&lt;br /&gt;
* [[User:LaurenAjamie| Lauren Ajamie]] (University of Notre Dame Library)&lt;br /&gt;
* [[User:MichaelSchofield| Michael Schofield]] ( @schoeyfield )&lt;br /&gt;
* [[User:Wickr|Ryan Wick]]&lt;br /&gt;
* [[User:cbeer|Chris Beer]]&lt;br /&gt;
*  [[User:Cdmo|Charlie Morris]] (Penn State)&lt;br /&gt;
&lt;br /&gt;
== Sponsorship Committee ==&lt;br /&gt;
This group will focus on making sure all who want to support the conference have the opportunity to do so.  Sponsorship Committee work involves working with the LPC to close budget gaps and talking to potential sponsors to find the level that is right for them.  &lt;br /&gt;
&lt;br /&gt;
The Sponsorship committee meets every other Tuesday at 2pm EST (11am PST) via [https://plus.google.com/hangouts/_/gwibrfqhzxe23uto4me3tktbnia Google hangout].  &lt;br /&gt;
&lt;br /&gt;
* [[User:Sdellis|Shaun Ellis]] (Princeton) (v)&lt;br /&gt;
* David Uspal (Villanova) - LPC Contact (v)&lt;br /&gt;
* Chad Nelson&lt;br /&gt;
* Morgan McKeehan&lt;br /&gt;
* Ray Schwartz&lt;br /&gt;
* Sharon Whitfield (Rowan University)&lt;br /&gt;
* Brett Bonfield  (Collingswood Public) (v)&lt;br /&gt;
* Katherine Lynch (Temple University)&lt;br /&gt;
* Rachel Trent (George Washington University)&lt;br /&gt;
&lt;br /&gt;
== Keynote Committee ==&lt;br /&gt;
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.&lt;br /&gt;
&lt;br /&gt;
* Brett Bonfield (Collingswood Public)&lt;br /&gt;
* John Mignault (ESDN/METRO)&lt;br /&gt;
* Emily Morton-Owens&lt;br /&gt;
* [[User:Phette23|Eric Phetteplace]]&lt;br /&gt;
* Whitni Watkins (St. Lawrence University)&lt;br /&gt;
* Beatrice Pulliam (Providence Public)&lt;br /&gt;
&lt;br /&gt;
== Pre-conference Committee ==&lt;br /&gt;
This committee plans the pre-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.&lt;br /&gt;
* Anna Headley - Chemical Heritage Foundation (Local Contact)&lt;br /&gt;
* [[User:ChristinaHarlow|Christina Harlow]] - convener&lt;br /&gt;
* Eric Lease Morgan - Librarian-At-Large&lt;br /&gt;
* Andrea Schurr - Univ. of TN at Chattanooga&lt;br /&gt;
* [[User:AndyWeidner|Andy Weidner]] - Univ. of Houston&lt;br /&gt;
&lt;br /&gt;
[[Preconference2016Workspace]]&lt;br /&gt;
&lt;br /&gt;
== Program Committee == &lt;br /&gt;
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.&lt;br /&gt;
* David Lacy - Villanova (Local Contact)&lt;br /&gt;
* Kevin Beswick - NCSU&lt;br /&gt;
* Peter Murray - Cherry HIll Company&lt;br /&gt;
* Chris Beer - Stanford University Libraries&lt;br /&gt;
* Matt Sherman - University of Bridgeport&lt;br /&gt;
* Whitni Watkins - St. Lawrence University&lt;br /&gt;
* Ben Armintor - Columbia University&lt;br /&gt;
* Ranti Junus - Michigan State University&lt;br /&gt;
* Katherine Lynch - Temple University&lt;br /&gt;
* Tod Olson - University of Chicago&lt;br /&gt;
&lt;br /&gt;
== Scholarship Committee ==&lt;br /&gt;
This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.&lt;br /&gt;
* Chad Nelson (Local Contact)&lt;br /&gt;
*  [[User:jtidal|Junior Tidal]] (New York City College of Technology)&lt;br /&gt;
* Linda Ballinger (Penn State)&lt;br /&gt;
* Mairelys Lemus-Rojas (University of Miami Libraries)&lt;br /&gt;
* Spencer Lamm (Drexel University)&lt;br /&gt;
* Lauren Gala (U Penn)&lt;br /&gt;
* Bohyun Kim (U Maryland, Baltimore)&lt;br /&gt;
* [[User:dkerchner|Dan Kerchner]] (George Washington University)&lt;br /&gt;
&lt;br /&gt;
== Childcare Committee == &lt;br /&gt;
This group assess the need for childcare at the conference, organizes childcare options, determines cost, and liaises with parents and chilcare providers&lt;br /&gt;
* Chad Nelson (Local Contact)&lt;br /&gt;
&lt;br /&gt;
== T-Shirt Committee ==&lt;br /&gt;
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.&lt;br /&gt;
* Lauren Gala (Local Contact)&lt;br /&gt;
* [[User:ChristinaHarlow|Christina Harlow]]&lt;br /&gt;
&lt;br /&gt;
== Onsite Volunteer Committee ==&lt;br /&gt;
This committee wrangles &amp;lt;s&amp;gt;tributes&amp;lt;/s&amp;gt; people to volunteer for the following duties:&lt;br /&gt;
** MC&lt;br /&gt;
** Registration&lt;br /&gt;
** Session Timers&lt;br /&gt;
** Etc.&lt;br /&gt;
&lt;br /&gt;
* (Local Contact)&lt;br /&gt;
* (Documentarian)&lt;br /&gt;
* (Chair)&lt;br /&gt;
&lt;br /&gt;
== Social Activities ==&lt;br /&gt;
This committee works closely with the local programming committee in organizing events outside of conference hours. This committee is in charge of organizing the Newcomer Dinner (traditionally held the night before the first day of the main conference) as well as ensuring that there is a variety of different events to cater to different interests (alcoholic/non-alcoholic, carnivore/vegan, mainstream/niche, and everything in between).&lt;br /&gt;
&lt;br /&gt;
* Becky Yoose (The Seattle Public Library; benevolent dictator for life)&lt;br /&gt;
* (Local Contact)&lt;br /&gt;
* (Documentarian)&lt;br /&gt;
* (Chair)&lt;br /&gt;
&lt;br /&gt;
== Streaming Video Committee ==&lt;br /&gt;
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks (?), and, of course, actually running the camera during the conference.&lt;br /&gt;
&lt;br /&gt;
* (Local Contact)&lt;br /&gt;
* Ashley Blewer&lt;br /&gt;
* (Documentarian)&lt;br /&gt;
* (Chair)&lt;br /&gt;
&lt;br /&gt;
== Code4Lib 2017 Host Voting Committee ==&lt;br /&gt;
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. &lt;br /&gt;
&lt;br /&gt;
* (Local Contact)&lt;br /&gt;
* (Documentarian)&lt;br /&gt;
* (Chair)&lt;br /&gt;
&lt;br /&gt;
== Wifi/Electrical ==&lt;br /&gt;
Arguably the most important committee. Coordinates with the local programming committee and the conference venue to ensure that wifi will be functioning for 450 people x 3 to 4 wifi enabled devices per person... as well as ensuring that there is ample power for folks to plug said devices in at the conference.&lt;br /&gt;
&lt;br /&gt;
* (Local Contact)&lt;br /&gt;
* (Documentarian)&lt;br /&gt;
* (Chair)&lt;br /&gt;
&lt;br /&gt;
== Book Giveaway Committee ==&lt;br /&gt;
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (for example, free private repo from Github or license for oXygen). They also handle the raffle at the conference (with a randomizer to do the drawing of names).&lt;br /&gt;
&lt;br /&gt;
* (Local Contact)&lt;br /&gt;
* (Documentarian)&lt;br /&gt;
* (Chair)&lt;br /&gt;
&lt;br /&gt;
== IRC Committee ==&lt;br /&gt;
Coordinate with freenode to ensure that the #code4lib IRC channel can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.&lt;br /&gt;
&lt;br /&gt;
* (Local Contact)&lt;br /&gt;
* (Documentarian)&lt;br /&gt;
* (Chair)&lt;br /&gt;
&lt;br /&gt;
== Accessibility Committee ==&lt;br /&gt;
A new committee for 2016 - document and address major points of the conference that are not accessible for conference attendees (physical and virtual).&lt;br /&gt;
&lt;br /&gt;
* (Local Contact)&lt;br /&gt;
* (Documentarian)&lt;br /&gt;
* (Chair)&lt;br /&gt;
&lt;br /&gt;
== Whatever Committee ==&lt;br /&gt;
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.&lt;br /&gt;
&lt;br /&gt;
* ...&lt;br /&gt;
* ...&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
== Additional Committees... Coming Soon! ==&lt;br /&gt;
* Reception?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2016]]&lt;/div&gt;</summary>
		<author><name>AshleyBlewer</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Social_Activities&amp;diff=42802</id>
		<title>2015 Social Activities</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Social_Activities&amp;diff=42802"/>
				<updated>2015-02-12T01:14:58Z</updated>
		
		<summary type="html">&lt;p&gt;AshleyBlewer: /* Karaoke, Wednesday February 11 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Social Activities Group is working on several events and social opportunities for after conference hours. We will be adding more events as they come along. Watch this page!&lt;br /&gt;
&lt;br /&gt;
Also, if you find a cool event to go to, and want to share the wealth with others, feel free to add the event to the page. :)&lt;br /&gt;
&lt;br /&gt;
== Planned Events ==&lt;br /&gt;
&lt;br /&gt;
=== Newcomer Dinner, Monday, February 9th ===&lt;br /&gt;
&lt;br /&gt;
First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating &amp;lt;strike&amp;gt;discussions about&amp;lt;/strike&amp;gt; demonstrations of the many uses of &amp;lt;strike&amp;gt;bacon&amp;lt;/strike&amp;gt; &amp;lt;strike&amp;gt;XML&amp;lt;/strike&amp;gt; &amp;lt;strike&amp;gt;EZProxy&amp;lt;/strike&amp;gt; LibGuides alternatives.&lt;br /&gt;
&lt;br /&gt;
Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!&lt;br /&gt;
&lt;br /&gt;
'''Plans'''&lt;br /&gt;
* When: Monday, February 9th&lt;br /&gt;
* Time: 6 PM (ish) or whenever you can get your group together&lt;br /&gt;
* Mastermind (if you have any questions): [mailto:yoosebec@grinnell.edu Becky Yoose]&lt;br /&gt;
&lt;br /&gt;
''Guidelines:''&lt;br /&gt;
*Max of '''6''' per group&lt;br /&gt;
**Please, no waitlisting&lt;br /&gt;
**Some restaurants can hold multiple groups of six. It is up to you to investigate the venue to see if this is possible.&lt;br /&gt;
*ID yourselves so we can get a good mix of new people and veterans in each group&lt;br /&gt;
**New folks - n&lt;br /&gt;
**c4l vets - v&lt;br /&gt;
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group''')&lt;br /&gt;
**Leader duties&lt;br /&gt;
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library tech type folks&lt;br /&gt;
***Herd folks from hotel to restaurant (know where you're going!)&lt;br /&gt;
*See a restaurant that's not listed? Feel free to add one, '''but please make sure that it is open that Monday evening.'''&lt;br /&gt;
&lt;br /&gt;
'''[https://docs.google.com/document/d/1rqfdRYxCZe7UrelaULzk8jpjavGGi2PGHUN1hPX7aNI/edit?usp=sharing Restaurant list and dinner sign ups posted on Google Docs]'''&lt;br /&gt;
&lt;br /&gt;
=== LibTechWomen Meetup, Tuesday February 10th ===&lt;br /&gt;
&lt;br /&gt;
When: Tuesday, February 10th  - 5:30pm - 7pm&lt;br /&gt;
&lt;br /&gt;
Where: The Veggie Grill -- 508 SW Taylor St. (One block from the hotel.) [http://veggiegrill.com/docs/vg-web-menu.pdf Menu is here.]&lt;br /&gt;
&lt;br /&gt;
An informal meetup for women and their friends in library technology. No need to RSVP. I'll try to make sure there's an announcement ahead of time, and will be in the hotel lobby at 5:15 to point people in the right direction.&lt;br /&gt;
&lt;br /&gt;
Questions? [mailto:sarahsimpkin@gmail.com Sarah Simpkin]&lt;br /&gt;
&lt;br /&gt;
=== Craft Brew Drinkup, Tuesday February 10th ===&lt;br /&gt;
&lt;br /&gt;
When:  Tuesday, February 10th  - 7pm - 10pm (ish)&lt;br /&gt;
&lt;br /&gt;
Where:  eBay Offices - 1400 SW 5th Ave, Portland, OR 97201&lt;br /&gt;
&lt;br /&gt;
The Craft Brew Drinkup at Code4lib 2015 is all about sharing and enjoying good beer with fellow conference attendees. The idea is to bring bottles of your favorite beers or non-alcoholic drinks.&lt;br /&gt;
&lt;br /&gt;
While you're not obligated to bring local brews from wherever you're from, participants are definitely encouraged to bring brews that you think is special and might be somewhat hard for others outside your area to find. Homebrew is especially welcome as are non-alcoholic beverages. Hot water will be provided for those who want to bring tea blends.&lt;br /&gt;
&lt;br /&gt;
This year, eBay has agreed to host the Code4Lib Drinkup at their offices in downtown Portland, a 6 block walk from the conference hotel.  Attendees should expect to bring something to share, either drinks or snacks. Cups will be provided by the host.&lt;br /&gt;
&lt;br /&gt;
'''Please Note''': The space must be cleaned up and all folks gone no later than 11pm.  &lt;br /&gt;
&lt;br /&gt;
'''[https://www.eventbrite.com/e/code4lib-2015-tickets-14504558525 Space is limited to the first 200 people who register for the event!]'''&lt;br /&gt;
&lt;br /&gt;
Please sign up on the [[2015 Craft Drinkup|Craft Drinkup wiki page]] to share the brews and bottles you're thinking of bringing along and special requests can be made, but don't expect that your wishes will be granted.&lt;br /&gt;
&lt;br /&gt;
Door volunteers&lt;br /&gt;
7-7:30 | &lt;br /&gt;
7:30-8  Chela | &lt;br /&gt;
8-:8:30 Tara | &lt;br /&gt;
8:30-9  Ranti |&lt;br /&gt;
9-9:30 Beatrice |&lt;br /&gt;
9:30-10&lt;br /&gt;
&lt;br /&gt;
=== Run4Lib, Monday-Wednesday, Feb 9-11th ===&lt;br /&gt;
&lt;br /&gt;
When:  Monday-Wednesday (February 9th, 10th &amp;amp; 11th) '''leaving at 6:30AM'''&lt;br /&gt;
&lt;br /&gt;
Where: Meet in Conf Hotel Lobby, see routes below.&lt;br /&gt;
&lt;br /&gt;
Running Distance: 5k-ish&lt;br /&gt;
&lt;br /&gt;
Run4Lib is about providing an easy opportunity to get your run on with other runners. We decided to alternate between two routes, both similar in distance. &lt;br /&gt;
&lt;br /&gt;
'''Mon/Wed route''':[http://www.mapmyrun.com/routes/view/616875918 MapMyRun Run4Lib Mon/Wed Route] &lt;br /&gt;
&lt;br /&gt;
'''Tues route''':[http://www.mapmyrun.com/routes/view/616883656 MapMyRun Run4Lib Tues Route]&lt;br /&gt;
&lt;br /&gt;
Questions? : [mailto:wwatkins@stlawu.edu Whitni Watkins]&lt;br /&gt;
&lt;br /&gt;
=== OCLC Developer House Meetup, Wednesday February 11th ===&lt;br /&gt;
&lt;br /&gt;
When: Wednesday, Febraury 11th 5:30pm – 7:00pm&lt;br /&gt;
&lt;br /&gt;
Where: Meet in the hotel lobby at 5:30 and figure out where we want to go (or stay?) for a drink, depending on the will of the group and the whim of the weather.&lt;br /&gt;
&lt;br /&gt;
An informal meetup for alumni and anyone interested in OCLC’s Developer House event. No need to RSVP. &lt;br /&gt;
&lt;br /&gt;
Drop me a note if you have any questions: [mailto:hostetls@oclc.org Shelley Hostetler]&lt;br /&gt;
&lt;br /&gt;
=== Game Night, Wednesday February 11 === &lt;br /&gt;
&lt;br /&gt;
Games sign up on the [[2015_Game_Night|Game Night page]]&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
Where: ballroom/meeting room(s) at the Hilton.  &lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
When: February 11, 6pm&lt;br /&gt;
&lt;br /&gt;
=== Karaoke, Wednesday February 11 ===&lt;br /&gt;
&lt;br /&gt;
Interested in singing your face off, and/or enjoying others doing the same?&lt;br /&gt;
&lt;br /&gt;
'''When:''' February 11, 8-11pm&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Where:''' [http://voiceboxpdx.com/ Voicebox PDX], 2112 NW Hoyt, Portland, OR 97210 / 503.303.8220&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Cost:''' About $15 (depending on number of people and how long we stay) plus whatever food &amp;amp; drink you order&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Details:''' '''''Update''''' We've upgraded to the $80/hr room that can hold up to 30 people.&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Song List''': Create an account at [http://vbsongs.com/ VBSongs] if you want to plan/save your playlist in advance! You can also use it to queue songs to sing direct from your mobile device.&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Advice from a PDX local Voicebox regular:''' With a group this size, we might consider setting some ground rules to make sure everyone gets to sing, for example, don't queue more than one song in a row, don't have more than two songs in the queue, etc...&lt;br /&gt;
&lt;br /&gt;
# Michael Klein (@mbklein)&lt;br /&gt;
# Mark Matienzo (@anarchivist)&lt;br /&gt;
# Whitni Watkins (@nimblelibrarian)&lt;br /&gt;
# Julie Hardesty (@jlhardes)&lt;br /&gt;
# Cliff Ingham (c/o @jlhardes)&lt;br /&gt;
# Erin White (@erinrwhite)&lt;br /&gt;
# Catelynne Sahadath (@metacatie)&lt;br /&gt;
# Rebecca Fraimow (@rhfraim)&lt;br /&gt;
# Peggy Griesinger (@peggygriesinger)&lt;br /&gt;
# Casey E. Davis (@caseyedavis1)&lt;br /&gt;
# Linda Newman (@NewmanLindaUC on Twitter, newmanld-AT-ucmail.uc.edu if we fall back to email)&lt;br /&gt;
# Jessica Venlet (@JessVenlet)&lt;br /&gt;
# Chad Nelson (@bibliotechy)&lt;br /&gt;
# Jennifer Lindner (@jenlindner)&lt;br /&gt;
# Marijane White (@marijane)&lt;br /&gt;
# Thom Goodnow (@goodnowlibtech)&lt;br /&gt;
# Bryan Brown (@bryjbrown)&lt;br /&gt;
# Jessie Keck (@jessiekeck)&lt;br /&gt;
# Vanessa Ragains (c/o @jessiekeck)&lt;br /&gt;
&lt;br /&gt;
== Social Map - Places of Interest==&lt;br /&gt;
&lt;br /&gt;
== Ideas ==&lt;br /&gt;
&lt;br /&gt;
''Want to see a specific event? Add your own ideas here...''&lt;br /&gt;
&lt;br /&gt;
== Local Food ==&lt;br /&gt;
* [http://www.foodcartsportland.com/maps/ Portland Food Carts] - Several in Pioneer Courthouse Square (2 blocks away from conference) and a huge pod off SW 10th &amp;amp; Alder. &amp;quot;Pods&amp;quot; are locations with multiple food carts and a good choice for a large group with different dietary needs, preferences, and budgets. Most meals are under $10. [https://www.google.com/maps/d/viewer?msa=0&amp;amp;mid=zBwrQkvFyvi8.k7T1OA_J6anE Pod Map]. It's rare to find a place to sit, so once you've got your meal check your map for the nearest green square in downtown. &lt;br /&gt;
&lt;br /&gt;
=== Restaurants ===&lt;br /&gt;
&lt;br /&gt;
=== Donuts ===&lt;br /&gt;
* [http://www.bluestardonuts.com/ Blue Star Donuts] - Awesome donuts.&lt;br /&gt;
&lt;br /&gt;
=== Desserts ===&lt;br /&gt;
* [http://euphoriachocolate.com/ Euphoria Chocolate] - Sold by many gift shops, including the Made In Oregon at PDX Airport. Local chocolate, good stuff. &lt;br /&gt;
* [http://www.moonstruckchocolate.com/ Moonstruck Chocolate Company] - Local chocolate. Locations off SW 6th &amp;amp; Alder; NW 23rd between Hoyt and Glisan. NW 23rd also has a number of shops, bars, restaurants, and is good for people watching. Accessible by the Portland Streetcar.&lt;br /&gt;
&lt;br /&gt;
=== Coffee ===&lt;br /&gt;
* [http://purringtonscatlounge.com/home/p484/ Purringtons Cat Lounge] - Cat cafe. Reservations required (hour slots, $8/person)&lt;br /&gt;
&lt;br /&gt;
== Local Drinks ==&lt;br /&gt;
&lt;br /&gt;
=== Bars ===&lt;br /&gt;
&lt;br /&gt;
=== Breweries ===&lt;br /&gt;
* [http://basecampbrewingco.com/ Base Camp Brewing Co.]&lt;br /&gt;
* [http://www.bridgeportbrew.com/home Bridgeport Brewing]&lt;br /&gt;
* [http://www.burnsidebrewco.com/ Burnside Brewing Co.]&lt;br /&gt;
* [http://www.cascadebrewingbarrelhouse.com/ Cascade Brewing Barrel House]&lt;br /&gt;
* [http://www.deschutesbrewery.com/locations/portland Deschutes Brewery and Pub]&lt;br /&gt;
* [http://hairofthedog.com/ Hair of the Dog Brewing Co.]&lt;br /&gt;
* [http://www.rockbottom.com/ Rock Bottom Restaurant and Brewery]&lt;br /&gt;
* [http://www.rogue.com/roguemeetinghalls/ Rogue Distillery and Pub]&lt;br /&gt;
* [http://www.d2m.com/Tugwebsite/ Tugboat Brewing Company]&lt;br /&gt;
* [http://widmerbrothers.com/ Widmer Brothers Brewing]&lt;br /&gt;
&lt;br /&gt;
The breweries listed above are a few blocks' walk from [http://trimet.org/index.htm Tri-Met MAX] or the [http://www.portlandstreetcar.org/node/4 Portland Streetcar] lines- which are easily accessible from the host hotel.&lt;br /&gt;
&lt;br /&gt;
=== Bottle Shops and Taprooms ===&lt;br /&gt;
* [http://www.baileystaproom.com/ Bailey's Taproom] (Downtown)&lt;br /&gt;
* [http://www.johnsmarketplace.com/ John's] (SW)&lt;br /&gt;
* [http://www.belmont-station.com/ Belmont Station] (SE)&lt;br /&gt;
* [http://bazipdx.com/ Bazi Bierbrasserie] (SE)&lt;br /&gt;
* [http://thebeermongers.com/ Beer Mongers] (SE)&lt;br /&gt;
* [http://www.apexbar.com/ APEX Bar] (SE)&lt;br /&gt;
* [http://www.saraveza.com/ Saraveza] (N)&lt;br /&gt;
&lt;br /&gt;
== Portland Events ==&lt;br /&gt;
&lt;br /&gt;
=== Saturday and Sunday, February 7 and 8 ===&lt;br /&gt;
&lt;br /&gt;
* [https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;4c26a341.1412 PBCore RDF ontology hackathon]&lt;br /&gt;
* [[PBCore RDF Hackathon]]&lt;br /&gt;
&lt;br /&gt;
=== Monday, February 9 ===&lt;br /&gt;
* [http://tickets.orsymphony.org/single/eventDetail.aspx?p=2523 Carmina Burana], 8:00 pm, Arlene Schnitzer Concert Hall&lt;br /&gt;
* [http://www.powells.com/events/6382 Nick Hornby in Conversation with Cheryl Strayed], 7:00 pm, Powell's Books at Cedar Hills Crossing&lt;br /&gt;
&lt;br /&gt;
=== Tuesday, February 10 ===&lt;br /&gt;
* [http://www.portland5.com/keller-auditorium/events/carmen Carmen], 7:30 pm, Keller Auditorium&lt;br /&gt;
&lt;br /&gt;
=== Wednesday, February 11 ===&lt;br /&gt;
&lt;br /&gt;
* [http://www.portland5.com/arlene-schnitzer-concert-hall/events/nederlands-dans-theater-2 Nederlands Dans Theater at Arlene Schnitzer Concert Hall], 7:30 pm; Already purchased a block of tickets for those who indicated interest early on. Anyone else buying a ticket late in the game and interested in joining us before the show for a bite to eat contact Andy Mardesich &amp;lt;Andy.Mardesich at ucop.edu&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=== Thursday, February 12  ===&lt;br /&gt;
* [http://www.portland5.com/keller-auditorium/events/carmen Carmen], 7:30 pm, Keller Auditorium&lt;br /&gt;
* [http://www.mississippistudios.com/event/724141-catfish-bottlemen-portland/ Catfish and The Bottlemen], 9:00 pm, Mississippi Studios&lt;br /&gt;
* [http://thirdangle.org/2014-15-season/mozart-revisted/ Mozart, Revisited], 7:30 pm, Zoomtopia&lt;br /&gt;
&lt;br /&gt;
=== All days ===&lt;br /&gt;
* [http://www.nwfilm.org/festivals/piff/ Portland International Film Festival]&lt;br /&gt;
* [http://portlandartmuseum.org/exhibitions/masterworks-portland-el-greco/ Masterworks | Portland: El Greco], Portland Art Museum&lt;br /&gt;
&lt;br /&gt;
==Getting Around==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]]&lt;/div&gt;</summary>
		<author><name>AshleyBlewer</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Social_Activities&amp;diff=42791</id>
		<title>2015 Social Activities</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Social_Activities&amp;diff=42791"/>
				<updated>2015-02-11T22:18:03Z</updated>
		
		<summary type="html">&lt;p&gt;AshleyBlewer: /* Karaoke, Wednesday February 11 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Social Activities Group is working on several events and social opportunities for after conference hours. We will be adding more events as they come along. Watch this page!&lt;br /&gt;
&lt;br /&gt;
Also, if you find a cool event to go to, and want to share the wealth with others, feel free to add the event to the page. :)&lt;br /&gt;
&lt;br /&gt;
== Planned Events ==&lt;br /&gt;
&lt;br /&gt;
=== Newcomer Dinner, Monday, February 9th ===&lt;br /&gt;
&lt;br /&gt;
First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating &amp;lt;strike&amp;gt;discussions about&amp;lt;/strike&amp;gt; demonstrations of the many uses of &amp;lt;strike&amp;gt;bacon&amp;lt;/strike&amp;gt; &amp;lt;strike&amp;gt;XML&amp;lt;/strike&amp;gt; &amp;lt;strike&amp;gt;EZProxy&amp;lt;/strike&amp;gt; LibGuides alternatives.&lt;br /&gt;
&lt;br /&gt;
Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!&lt;br /&gt;
&lt;br /&gt;
'''Plans'''&lt;br /&gt;
* When: Monday, February 9th&lt;br /&gt;
* Time: 6 PM (ish) or whenever you can get your group together&lt;br /&gt;
* Mastermind (if you have any questions): [mailto:yoosebec@grinnell.edu Becky Yoose]&lt;br /&gt;
&lt;br /&gt;
''Guidelines:''&lt;br /&gt;
*Max of '''6''' per group&lt;br /&gt;
**Please, no waitlisting&lt;br /&gt;
**Some restaurants can hold multiple groups of six. It is up to you to investigate the venue to see if this is possible.&lt;br /&gt;
*ID yourselves so we can get a good mix of new people and veterans in each group&lt;br /&gt;
**New folks - n&lt;br /&gt;
**c4l vets - v&lt;br /&gt;
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group''')&lt;br /&gt;
**Leader duties&lt;br /&gt;
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library tech type folks&lt;br /&gt;
***Herd folks from hotel to restaurant (know where you're going!)&lt;br /&gt;
*See a restaurant that's not listed? Feel free to add one, '''but please make sure that it is open that Monday evening.'''&lt;br /&gt;
&lt;br /&gt;
'''[https://docs.google.com/document/d/1rqfdRYxCZe7UrelaULzk8jpjavGGi2PGHUN1hPX7aNI/edit?usp=sharing Restaurant list and dinner sign ups posted on Google Docs]'''&lt;br /&gt;
&lt;br /&gt;
=== LibTechWomen Meetup, Tuesday February 10th ===&lt;br /&gt;
&lt;br /&gt;
When: Tuesday, February 10th  - 5:30pm - 7pm&lt;br /&gt;
&lt;br /&gt;
Where: The Veggie Grill -- 508 SW Taylor St. (One block from the hotel.) [http://veggiegrill.com/docs/vg-web-menu.pdf Menu is here.]&lt;br /&gt;
&lt;br /&gt;
An informal meetup for women and their friends in library technology. No need to RSVP. I'll try to make sure there's an announcement ahead of time, and will be in the hotel lobby at 5:15 to point people in the right direction.&lt;br /&gt;
&lt;br /&gt;
Questions? [mailto:sarahsimpkin@gmail.com Sarah Simpkin]&lt;br /&gt;
&lt;br /&gt;
=== Craft Brew Drinkup, Tuesday February 10th ===&lt;br /&gt;
&lt;br /&gt;
When:  Tuesday, February 10th  - 7pm - 10pm (ish)&lt;br /&gt;
&lt;br /&gt;
Where:  eBay Offices - 1400 SW 5th Ave, Portland, OR 97201&lt;br /&gt;
&lt;br /&gt;
The Craft Brew Drinkup at Code4lib 2015 is all about sharing and enjoying good beer with fellow conference attendees. The idea is to bring bottles of your favorite beers or non-alcoholic drinks.&lt;br /&gt;
&lt;br /&gt;
While you're not obligated to bring local brews from wherever you're from, participants are definitely encouraged to bring brews that you think is special and might be somewhat hard for others outside your area to find. Homebrew is especially welcome as are non-alcoholic beverages. Hot water will be provided for those who want to bring tea blends.&lt;br /&gt;
&lt;br /&gt;
This year, eBay has agreed to host the Code4Lib Drinkup at their offices in downtown Portland, a 6 block walk from the conference hotel.  Attendees should expect to bring something to share, either drinks or snacks. Cups will be provided by the host.&lt;br /&gt;
&lt;br /&gt;
'''Please Note''': The space must be cleaned up and all folks gone no later than 11pm.  &lt;br /&gt;
&lt;br /&gt;
'''[https://www.eventbrite.com/e/code4lib-2015-tickets-14504558525 Space is limited to the first 200 people who register for the event!]'''&lt;br /&gt;
&lt;br /&gt;
Please sign up on the [[2015 Craft Drinkup|Craft Drinkup wiki page]] to share the brews and bottles you're thinking of bringing along and special requests can be made, but don't expect that your wishes will be granted.&lt;br /&gt;
&lt;br /&gt;
Door volunteers&lt;br /&gt;
7-7:30 | &lt;br /&gt;
7:30-8  Chela | &lt;br /&gt;
8-:8:30 Tara | &lt;br /&gt;
8:30-9  Ranti |&lt;br /&gt;
9-9:30 Beatrice |&lt;br /&gt;
9:30-10&lt;br /&gt;
&lt;br /&gt;
=== Run4Lib, Monday-Wednesday, Feb 9-11th ===&lt;br /&gt;
&lt;br /&gt;
When:  Monday-Wednesday (February 9th, 10th &amp;amp; 11th) '''leaving at 6:30AM'''&lt;br /&gt;
&lt;br /&gt;
Where: Meet in Conf Hotel Lobby, see routes below.&lt;br /&gt;
&lt;br /&gt;
Running Distance: 5k-ish&lt;br /&gt;
&lt;br /&gt;
Run4Lib is about providing an easy opportunity to get your run on with other runners. We decided to alternate between two routes, both similar in distance. &lt;br /&gt;
&lt;br /&gt;
'''Mon/Wed route''':[http://www.mapmyrun.com/routes/view/616875918 MapMyRun Run4Lib Mon/Wed Route] &lt;br /&gt;
&lt;br /&gt;
'''Tues route''':[http://www.mapmyrun.com/routes/view/616883656 MapMyRun Run4Lib Tues Route]&lt;br /&gt;
&lt;br /&gt;
Questions? : [mailto:wwatkins@stlawu.edu Whitni Watkins]&lt;br /&gt;
&lt;br /&gt;
=== OCLC Developer House Meetup, Wednesday February 11th ===&lt;br /&gt;
&lt;br /&gt;
When: Wednesday, Febraury 11th 5:30pm – 7:00pm&lt;br /&gt;
&lt;br /&gt;
Where: Meet in the hotel lobby at 5:30 and figure out where we want to go (or stay?) for a drink, depending on the will of the group and the whim of the weather.&lt;br /&gt;
&lt;br /&gt;
An informal meetup for alumni and anyone interested in OCLC’s Developer House event. No need to RSVP. &lt;br /&gt;
&lt;br /&gt;
Drop me a note if you have any questions: [mailto:hostetls@oclc.org Shelley Hostetler]&lt;br /&gt;
&lt;br /&gt;
=== Game Night, Wednesday February 11 === &lt;br /&gt;
&lt;br /&gt;
Games sign up on the [[2015_Game_Night|Game Night page]]&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
Where: ballroom/meeting room(s) at the Hilton.  &lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
When: February 11, 6pm&lt;br /&gt;
&lt;br /&gt;
=== Karaoke, Wednesday February 11 ===&lt;br /&gt;
&lt;br /&gt;
Interested in singing your face off, and/or enjoying others doing the same?&lt;br /&gt;
&lt;br /&gt;
'''When:''' February 11, 8-11pm&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Where:''' [http://voiceboxpdx.com/ Voicebox PDX], 2112 NW Hoyt, Portland, OR 97210 / 503.303.8220&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Cost:''' About $15 (depending on number of people and how long we stay) plus whatever food &amp;amp; drink you order&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Details:''' '''''Update''''' We've upgraded to the $80/hr room that can hold up to 30 people.&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Song List''': Create an account at [http://vbsongs.com/ VBSongs] if you want to plan/save your playlist in advance! You can also use it to queue songs to sing direct from your mobile device.&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Advice from a PDX local Voicebox regular:''' With a group this size, we might consider setting some ground rules to make sure everyone gets to sing, for example, don't queue more than one song in a row, don't have more than two songs in the queue, etc...&lt;br /&gt;
&lt;br /&gt;
# Michael Klein (@mbklein)&lt;br /&gt;
# Mark Matienzo (@anarchivist)&lt;br /&gt;
# Whitni Watkins (@nimblelibrarian)&lt;br /&gt;
# Julie Hardesty (@jlhardes)&lt;br /&gt;
# Cliff Ingham (c/o @jlhardes)&lt;br /&gt;
# Erin White (@erinrwhite)&lt;br /&gt;
# Catelynne Sahadath (@metacatie)&lt;br /&gt;
# Rebecca Fraimow (@rhfraim)&lt;br /&gt;
# Peggy Griesinger (@peggygriesinger)&lt;br /&gt;
# Vicky Steeves (@vickysteeves)&lt;br /&gt;
# Casey E. Davis (@caseyedavis1)&lt;br /&gt;
# Linda Newman (@NewmanLindaUC on Twitter, newmanld-AT-ucmail.uc.edu if we fall back to email)&lt;br /&gt;
# Jessica Venlet (@JessVenlet)&lt;br /&gt;
# Chad Nelson (@bibliotechy)&lt;br /&gt;
# Jennifer Lindner (@jenlindner)&lt;br /&gt;
# Marijane White (@marijane)&lt;br /&gt;
# Beatrice Pulliam (@beatricepulliam)&lt;br /&gt;
# Thom Goodnow (@goodnowlibtech)&lt;br /&gt;
# Bryan Brown (@bryjbrown)&lt;br /&gt;
# Jessie Keck (@jessiekeck)&lt;br /&gt;
# Vanessa Ragains (c/o @jessiekeck)&lt;br /&gt;
# Ashley &amp;quot;T-Swift&amp;quot; Blewer (@ablwr)&lt;br /&gt;
&lt;br /&gt;
== Social Map - Places of Interest==&lt;br /&gt;
&lt;br /&gt;
== Ideas ==&lt;br /&gt;
&lt;br /&gt;
''Want to see a specific event? Add your own ideas here...''&lt;br /&gt;
&lt;br /&gt;
== Local Food ==&lt;br /&gt;
* [http://www.foodcartsportland.com/maps/ Portland Food Carts] - Several in Pioneer Courthouse Square (2 blocks away from conference) and a huge pod off SW 10th &amp;amp; Alder. &amp;quot;Pods&amp;quot; are locations with multiple food carts and a good choice for a large group with different dietary needs, preferences, and budgets. Most meals are under $10. [https://www.google.com/maps/d/viewer?msa=0&amp;amp;mid=zBwrQkvFyvi8.k7T1OA_J6anE Pod Map]. It's rare to find a place to sit, so once you've got your meal check your map for the nearest green square in downtown. &lt;br /&gt;
&lt;br /&gt;
=== Restaurants ===&lt;br /&gt;
&lt;br /&gt;
=== Donuts ===&lt;br /&gt;
* [http://www.bluestardonuts.com/ Blue Star Donuts] - Awesome donuts.&lt;br /&gt;
&lt;br /&gt;
=== Desserts ===&lt;br /&gt;
* [http://euphoriachocolate.com/ Euphoria Chocolate] - Sold by many gift shops, including the Made In Oregon at PDX Airport. Local chocolate, good stuff. &lt;br /&gt;
* [http://www.moonstruckchocolate.com/ Moonstruck Chocolate Company] - Local chocolate. Locations off SW 6th &amp;amp; Alder; NW 23rd between Hoyt and Glisan. NW 23rd also has a number of shops, bars, restaurants, and is good for people watching. Accessible by the Portland Streetcar.&lt;br /&gt;
&lt;br /&gt;
=== Coffee ===&lt;br /&gt;
* [http://purringtonscatlounge.com/home/p484/ Purringtons Cat Lounge] - Cat cafe. Reservations required (hour slots, $8/person)&lt;br /&gt;
&lt;br /&gt;
== Local Drinks ==&lt;br /&gt;
&lt;br /&gt;
=== Bars ===&lt;br /&gt;
&lt;br /&gt;
=== Breweries ===&lt;br /&gt;
* [http://basecampbrewingco.com/ Base Camp Brewing Co.]&lt;br /&gt;
* [http://www.bridgeportbrew.com/home Bridgeport Brewing]&lt;br /&gt;
* [http://www.burnsidebrewco.com/ Burnside Brewing Co.]&lt;br /&gt;
* [http://www.cascadebrewingbarrelhouse.com/ Cascade Brewing Barrel House]&lt;br /&gt;
* [http://www.deschutesbrewery.com/locations/portland Deschutes Brewery and Pub]&lt;br /&gt;
* [http://hairofthedog.com/ Hair of the Dog Brewing Co.]&lt;br /&gt;
* [http://www.rockbottom.com/ Rock Bottom Restaurant and Brewery]&lt;br /&gt;
* [http://www.rogue.com/roguemeetinghalls/ Rogue Distillery and Pub]&lt;br /&gt;
* [http://www.d2m.com/Tugwebsite/ Tugboat Brewing Company]&lt;br /&gt;
* [http://widmerbrothers.com/ Widmer Brothers Brewing]&lt;br /&gt;
&lt;br /&gt;
The breweries listed above are a few blocks' walk from [http://trimet.org/index.htm Tri-Met MAX] or the [http://www.portlandstreetcar.org/node/4 Portland Streetcar] lines- which are easily accessible from the host hotel.&lt;br /&gt;
&lt;br /&gt;
=== Bottle Shops and Taprooms ===&lt;br /&gt;
* [http://www.baileystaproom.com/ Bailey's Taproom] (Downtown)&lt;br /&gt;
* [http://www.johnsmarketplace.com/ John's] (SW)&lt;br /&gt;
* [http://www.belmont-station.com/ Belmont Station] (SE)&lt;br /&gt;
* [http://bazipdx.com/ Bazi Bierbrasserie] (SE)&lt;br /&gt;
* [http://thebeermongers.com/ Beer Mongers] (SE)&lt;br /&gt;
* [http://www.apexbar.com/ APEX Bar] (SE)&lt;br /&gt;
* [http://www.saraveza.com/ Saraveza] (N)&lt;br /&gt;
&lt;br /&gt;
== Portland Events ==&lt;br /&gt;
&lt;br /&gt;
=== Saturday and Sunday, February 7 and 8 ===&lt;br /&gt;
&lt;br /&gt;
* [https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;4c26a341.1412 PBCore RDF ontology hackathon]&lt;br /&gt;
* [[PBCore RDF Hackathon]]&lt;br /&gt;
&lt;br /&gt;
=== Monday, February 9 ===&lt;br /&gt;
* [http://tickets.orsymphony.org/single/eventDetail.aspx?p=2523 Carmina Burana], 8:00 pm, Arlene Schnitzer Concert Hall&lt;br /&gt;
* [http://www.powells.com/events/6382 Nick Hornby in Conversation with Cheryl Strayed], 7:00 pm, Powell's Books at Cedar Hills Crossing&lt;br /&gt;
&lt;br /&gt;
=== Tuesday, February 10 ===&lt;br /&gt;
* [http://www.portland5.com/keller-auditorium/events/carmen Carmen], 7:30 pm, Keller Auditorium&lt;br /&gt;
&lt;br /&gt;
=== Wednesday, February 11 ===&lt;br /&gt;
&lt;br /&gt;
* [http://www.portland5.com/arlene-schnitzer-concert-hall/events/nederlands-dans-theater-2 Nederlands Dans Theater at Arlene Schnitzer Concert Hall], 7:30 pm; Already purchased a block of tickets for those who indicated interest early on. Anyone else buying a ticket late in the game and interested in joining us before the show for a bite to eat contact Andy Mardesich &amp;lt;Andy.Mardesich at ucop.edu&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=== Thursday, February 12  ===&lt;br /&gt;
* [http://www.portland5.com/keller-auditorium/events/carmen Carmen], 7:30 pm, Keller Auditorium&lt;br /&gt;
* [http://www.mississippistudios.com/event/724141-catfish-bottlemen-portland/ Catfish and The Bottlemen], 9:00 pm, Mississippi Studios&lt;br /&gt;
* [http://thirdangle.org/2014-15-season/mozart-revisted/ Mozart, Revisited], 7:30 pm, Zoomtopia&lt;br /&gt;
&lt;br /&gt;
=== All days ===&lt;br /&gt;
* [http://www.nwfilm.org/festivals/piff/ Portland International Film Festival]&lt;br /&gt;
* [http://portlandartmuseum.org/exhibitions/masterworks-portland-el-greco/ Masterworks | Portland: El Greco], Portland Art Museum&lt;br /&gt;
&lt;br /&gt;
==Getting Around==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]]&lt;/div&gt;</summary>
		<author><name>AshleyBlewer</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Lightning_Talks&amp;diff=42770</id>
		<title>2015 Lightning Talks</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Lightning_Talks&amp;diff=42770"/>
				<updated>2015-02-11T18:57:56Z</updated>
		
		<summary type="html">&lt;p&gt;AshleyBlewer: /* Wednesday 11:00 AM to 12:00 PM */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
==Lightning Talks==&lt;br /&gt;
&amp;lt;big&amp;gt;'''Lightning talk signup will begin after the opening session, on a (physical) sign up board.  As spots fill, we'll add them here for convenient reference.'''&amp;lt;/big&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Tuesday 14:30 PM to 15:30 PM==&lt;br /&gt;
# Automated Entity Extractions to Relate Library Resources - Kyle Banerjee&lt;br /&gt;
# ResCarta Recap&lt;br /&gt;
# [https://drive.google.com/file/d/0B6S516ceOR1nalpHOGFJdFVnclk/view?usp=sharing Information Design Thoughts] - Dre&lt;br /&gt;
# Vufind &amp;amp; Worldcat Discovery API - Karen Coombs&lt;br /&gt;
# Video Accessibility - Jason Ronallo&lt;br /&gt;
# [https://docs.google.com/presentation/d/11vBKfYbGzp5_gyksPqK1WKLvMVO_aMk03x2PvK1p_u8/view?usp=sharing ILS and Payment Systems] - Josh Weisman&lt;br /&gt;
# Fedora 4 Migration - Adam Wead&lt;br /&gt;
# [[https://gist.github.com/cbeer/4082dd15b62090f94b98 LDPath]] - Chris Beer&lt;br /&gt;
# [[https://drive.google.com/file/d/0B5jVboA5eH6ATHhSRnZCczhvLVE/view?usp=sharing Self-Deposit of Scientific Data]] - Darren Hardy&lt;br /&gt;
# Bread - Mx. Matienzo&lt;br /&gt;
&lt;br /&gt;
==Wednesday 11:00 AM to 12:00 PM==&lt;br /&gt;
# [http://bit.ly/rightspres rights metadata] esmé cowles&lt;br /&gt;
# [https://speakerdeck.com/nabeta/2014-2015-activities-of-code4lib-japan 2014-2015 Activities around code4lib Japan] - Kosuke Tanabe&lt;br /&gt;
# Dominic Bordelon - Maker Spacing + Arduino&lt;br /&gt;
# [http://ablwr.github.io/c4l_preforma/#/ PreForma (Preservation Formats Project)] - Ashley Blewer&lt;br /&gt;
# PBEBUCore - Casey E. Davis&lt;br /&gt;
# RDF for relational database developers - Hector Correa &lt;br /&gt;
# [http://intro2libsys.info/code4lib-2015 Building a BIBFRAME catalog] - Jeremy Nelson&lt;br /&gt;
# Mukustu CMS - Alex Merrill&lt;br /&gt;
# Planning for the data schlep - Adam Constaburis&lt;br /&gt;
# How do we improve as developers? - Trey Terrell&lt;br /&gt;
&lt;br /&gt;
==Thursday 9:30 AM to 10:15 AM ==&lt;br /&gt;
&lt;br /&gt;
# [https://github.com/OpenGeoMetadata/metadatarepository OpenGeoMetadata] : Let's share our geo metadata&lt;br /&gt;
# IIIF Image Drupal module&lt;br /&gt;
# Clustering moving image works - Kelley McGrath&lt;br /&gt;
# Islandora Fedora 4 proof of concept - Danny Lamb&lt;br /&gt;
# Measure the future - Jason Griffey&lt;br /&gt;
# Low hanging fruit of accessibility - Kate Deibel&lt;br /&gt;
# Drupal, git, and sanity - Charlie M.&lt;br /&gt;
# Archiving the silenced - Natasha Nunn&lt;br /&gt;
# The Great Migration: Fedora 4 - Andrew Woods&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]]&lt;/div&gt;</summary>
		<author><name>AshleyBlewer</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_During_the_Conference_Volunteers&amp;diff=42559</id>
		<title>2015 During the Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_During_the_Conference_Volunteers&amp;diff=42559"/>
				<updated>2015-01-31T14:13:35Z</updated>
		
		<summary type="html">&lt;p&gt;AshleyBlewer: /* Video Streaming */ all the streaming so I don't miss a single thing&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;code4lib 2015 During the Conference Volunteers&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--== Hospitality Suite Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee makes arrangements for any hospitality suite amenities (technology, snacks, games, icebreakers...) we may want.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Preconference Setup Help ==&lt;br /&gt;
&lt;br /&gt;
Help manage preconference sessions, setting up projectors, etc.&lt;br /&gt;
&lt;br /&gt;
* John Sarnowski (at ResCarta)&lt;br /&gt;
* Whitni Watkins (at NimbleLibrarian)&lt;br /&gt;
* Christina Harlow (at cm_harlow)&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
== Welcome Wagon Committee ==&lt;br /&gt;
&lt;br /&gt;
Offers conference newcomers an opportunity to self-identify; offers oldtimers an opportunity to meet newcomers. May also want to constitute a year-round variation for #code4lib.&lt;br /&gt;
&lt;br /&gt;
* Becky Yoose (b.yoose at google)&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
Responsible for non-IRC social networking presence.&lt;br /&gt;
&lt;br /&gt;
1-2 person(s) to take questions for sessions (assuming there's time during the session) via Twitter/IRC, and adding resources to lanyrd schedule (slides, notes, resources mentioned, etc.) Make a note if you can only do one or both.&lt;br /&gt;
&lt;br /&gt;
Consider directing people with questions to presenter on twitter/IRC (if applicable) if there is no time for questions.&lt;br /&gt;
&lt;br /&gt;
*Whitni Watkins (at NimbleLibrarian)&lt;br /&gt;
* Christina Harlow (at cm_harlow)&lt;br /&gt;
&lt;br /&gt;
== Beverage Share Setup/Teardown ==&lt;br /&gt;
&lt;br /&gt;
Help set up and clean up after the Tuesday event at the Ebay offices.&lt;br /&gt;
&lt;br /&gt;
* Karen Estlund - setup&lt;br /&gt;
* John Sarnowski - clean up (at ResCarta)&lt;br /&gt;
* Dominic Bordelon - clean up&lt;br /&gt;
* Whitni Watkins - setup (at NimbleLibrarian)&lt;br /&gt;
* Ben Armintor - both/either (barmintor)&lt;br /&gt;
* Bobbi Fox - setup&lt;br /&gt;
&lt;br /&gt;
== IRC Helpers ==&lt;br /&gt;
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.&lt;br /&gt;
&lt;br /&gt;
* Chad Nelson (bibliotechy)&lt;br /&gt;
One of the easiest ways to participate is to [http://webchat.freenode.net/ Go here] with your web browser. Choose a nickname (anything works so long as it is unique; if you want to be anonymous pick appropriately). Enter &amp;quot;code4lib&amp;quot; as the &amp;quot;Channel&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
If you've managed to get into the channel without help, type &amp;quot;@helpers&amp;quot; (without the quotes) to see a list of #code4lib helpers.&lt;br /&gt;
&lt;br /&gt;
== IRC Access ==&lt;br /&gt;
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people&lt;br /&gt;
&lt;br /&gt;
* Mx Matienzo (anarchivist)&lt;br /&gt;
&lt;br /&gt;
==Registration Desk Volunteers==&lt;br /&gt;
&lt;br /&gt;
'''Monday'''&lt;br /&gt;
* John Sarnowski (at ResCarta)&lt;br /&gt;
* Whitni Watkins (at NimbleLibrarian) -- if we only need one desk volunteer, let me know.  &lt;br /&gt;
'''Tuesday'''&lt;br /&gt;
* Christina Harlow (at cm_harlow)&lt;br /&gt;
* Whitni Watkins (at NimbleLibrarian) -- if we only need one desk volunteer, let me know.&lt;br /&gt;
'''Wednesday'''&lt;br /&gt;
* Christina Harlow (at cm_harlow)&lt;br /&gt;
* Bobbi Fox&lt;br /&gt;
&lt;br /&gt;
==Video Streaming==&lt;br /&gt;
We need two volunteers for each session, one at the front near the speaker and one at the rear at the camera/encoder.&lt;br /&gt;
We will have a brief training on Monday Afternoon. If you can't make the training, we will perform magic knowledge transfer.&lt;br /&gt;
This is not a highly technical position, if you can recognize a video camera two times out of three, you're in.&lt;br /&gt;
&lt;br /&gt;
You are welcome to work multiple sessions, or all of them. This will get you really good karma and many free drinks.&lt;br /&gt;
&lt;br /&gt;
'''Tuesday AM'''&lt;br /&gt;
&lt;br /&gt;
Ashley Blewer (at ablwr)&lt;br /&gt;
&lt;br /&gt;
'''Tuesday PM'''&lt;br /&gt;
&lt;br /&gt;
Ashley Blewer (at ablwr)&lt;br /&gt;
&lt;br /&gt;
'''Wednesday AM'''&lt;br /&gt;
&lt;br /&gt;
Ashley Blewer (at ablwr)&lt;br /&gt;
&lt;br /&gt;
'''Wednesday PM'''&lt;br /&gt;
&lt;br /&gt;
Ashley Blewer (at ablwr)&lt;br /&gt;
&lt;br /&gt;
'''Thursday AM'''&lt;br /&gt;
&lt;br /&gt;
Ashley Blewer (at ablwr, go big or go home)&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
'''Tuesday AM'''&lt;br /&gt;
*Terry R., likes to put birds on things&lt;br /&gt;
&lt;br /&gt;
'''Tuesday PM'''&lt;br /&gt;
*Eric, mumbler extraordinaire&lt;br /&gt;
&lt;br /&gt;
'''Wednesday AM'''&lt;br /&gt;
*Becky, destroyer of last names, singer of badly adapted show tunes &lt;br /&gt;
&lt;br /&gt;
'''Wednesday PM'''&lt;br /&gt;
*Cary, taller than Becky, will not sing.&lt;br /&gt;
&lt;br /&gt;
'''Thursday AM'''&lt;br /&gt;
&lt;br /&gt;
== Session Timer Volunteers ==&lt;br /&gt;
&lt;br /&gt;
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop with a stopwatch program).  It's good to have two people in each slot to back each other up in case of machinery failure.&lt;br /&gt;
&lt;br /&gt;
'''Schedule for Session Timers'''&lt;br /&gt;
&lt;br /&gt;
'''Tuesday AM'''&lt;br /&gt;
&lt;br /&gt;
* Francis Kayiwa (Mr. Sweetie Poo https://www.youtube.com/watch?v=xAnVNXaa5oA)&lt;br /&gt;
* Sarah Simpkin (at sarahsimpkin)&lt;br /&gt;
&lt;br /&gt;
'''Tuesday PM'''&lt;br /&gt;
*Maura Carbone&lt;br /&gt;
&lt;br /&gt;
'''Wednesday AM'''&lt;br /&gt;
* John Sarnowski (at ResCarta)&lt;br /&gt;
* Sarah Simpkin (at sarahsimpkin)&lt;br /&gt;
&lt;br /&gt;
'''Wednesday PM'''&lt;br /&gt;
* Dominic Bordelon&lt;br /&gt;
&lt;br /&gt;
'''Thursday AM'''&lt;br /&gt;
* Eric Phetteplace (at phette23)&lt;br /&gt;
&lt;br /&gt;
== Raffles ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Whatever Else Needs to be Done ==&lt;br /&gt;
&lt;br /&gt;
* Sarah Simpkin (at sarahsimpkin)&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2015]]&lt;/div&gt;</summary>
		<author><name>AshleyBlewer</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_During_the_Conference_Volunteers&amp;diff=42547</id>
		<title>2015 During the Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_During_the_Conference_Volunteers&amp;diff=42547"/>
				<updated>2015-01-30T02:56:32Z</updated>
		
		<summary type="html">&lt;p&gt;AshleyBlewer: /* Video Streaming */ Correcting my contact handle!&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;code4lib 2015 During the Conference Volunteers&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--== Hospitality Suite Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee makes arrangements for any hospitality suite amenities (technology, snacks, games, icebreakers...) we may want.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Preconference Setup Help ==&lt;br /&gt;
&lt;br /&gt;
Help manage preconference sessions, setting up projectors, etc.&lt;br /&gt;
&lt;br /&gt;
* John Sarnowski (at ResCarta)&lt;br /&gt;
* Whitni Watkins (at NimbleLibrarian)&lt;br /&gt;
* Christina Harlow (at cm_harlow)&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
== Welcome Wagon Committee ==&lt;br /&gt;
&lt;br /&gt;
Offers conference newcomers an opportunity to self-identify; offers oldtimers an opportunity to meet newcomers. May also want to constitute a year-round variation for #code4lib.&lt;br /&gt;
&lt;br /&gt;
* Becky Yoose (b.yoose at google)&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
Responsible for non-IRC social networking presence.&lt;br /&gt;
&lt;br /&gt;
1-2 person(s) to take questions for sessions (assuming there's time during the session) via Twitter/IRC, and adding resources to lanyrd schedule (slides, notes, resources mentioned, etc.) Make a note if you can only do one or both.&lt;br /&gt;
&lt;br /&gt;
Consider directing people with questions to presenter on twitter/IRC (if applicable) if there is no time for questions.&lt;br /&gt;
&lt;br /&gt;
*Whitni Watkins (at NimbleLibrarian)&lt;br /&gt;
* Christina Harlow (at cm_harlow)&lt;br /&gt;
&lt;br /&gt;
== Beverage Share Setup/Teardown ==&lt;br /&gt;
&lt;br /&gt;
Help set up and clean up after the Tuesday event at the Ebay offices.&lt;br /&gt;
&lt;br /&gt;
* Karen Estlund - setup&lt;br /&gt;
* John Sarnowski - clean up (at ResCarta)&lt;br /&gt;
* Dominic Bordelon - clean up&lt;br /&gt;
* Whitni Watkins - setup (at NimbleLibrarian)&lt;br /&gt;
&lt;br /&gt;
== IRC Helpers ==&lt;br /&gt;
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.&lt;br /&gt;
&lt;br /&gt;
* Chad Nelson (bibliotechy)&lt;br /&gt;
One of the easiest ways to participate is to [http://webchat.freenode.net/ Go here] with your web browser. Choose a nickname (anything works so long as it is unique; if you want to be anonymous pick appropriately). Enter &amp;quot;code4lib&amp;quot; as the &amp;quot;Channel&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
If you've managed to get into the channel without help, type &amp;quot;@helpers&amp;quot; (without the quotes) to see a list of #code4lib helpers.&lt;br /&gt;
&lt;br /&gt;
== IRC Access ==&lt;br /&gt;
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people&lt;br /&gt;
&lt;br /&gt;
* Mx Matienzo (anarchivist)&lt;br /&gt;
&lt;br /&gt;
==Registration Desk Volunteers==&lt;br /&gt;
&lt;br /&gt;
'''Monday'''&lt;br /&gt;
* John Sarnowski (at ResCarta)&lt;br /&gt;
* Whitni Watkins (at NimbleLibrarian) -- if we only need one desk volunteer, let me know.  &lt;br /&gt;
'''Tuesday'''&lt;br /&gt;
* Christina Harlow (at cm_harlow)&lt;br /&gt;
* Whitni Watkins (at NimbleLibrarian) -- if we only need one desk volunteer, let me know.&lt;br /&gt;
'''Wednesday'''&lt;br /&gt;
* Christina Harlow (at cm_harlow)&lt;br /&gt;
&lt;br /&gt;
==Video Streaming==&lt;br /&gt;
We need two volunteers for each session, one at the front near the speaker and one at the rear at the camera/encoder.&lt;br /&gt;
We will have a brief training on Monday Afternoon. If you can't make the training, we will perform magic knowledge transfer.&lt;br /&gt;
This is not a highly technical position, if you can recognize a video camera two times out of three, you're in.&lt;br /&gt;
&lt;br /&gt;
You are welcome to work multiple sessions, or all of them. This will get you really good karma and many free drinks.&lt;br /&gt;
&lt;br /&gt;
'''Tuesday AM'''&lt;br /&gt;
&lt;br /&gt;
Ashley Blewer (at ablwr)&lt;br /&gt;
&lt;br /&gt;
'''Tuesday PM'''&lt;br /&gt;
&lt;br /&gt;
Ashley Blewer (at ablwr)&lt;br /&gt;
&lt;br /&gt;
'''Wednesday AM'''&lt;br /&gt;
&lt;br /&gt;
Ashley Blewer (at ablwr)&lt;br /&gt;
&lt;br /&gt;
'''Wednesday PM'''&lt;br /&gt;
&lt;br /&gt;
Ashley Blewer (at ablwr)&lt;br /&gt;
&lt;br /&gt;
'''Thursday AM'''&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
'''Tuesday AM'''&lt;br /&gt;
&lt;br /&gt;
'''Tuesday PM'''&lt;br /&gt;
&lt;br /&gt;
'''Wednesday AM'''&lt;br /&gt;
*Becky, destroyer of last names, singer of badly adapted show tunes &lt;br /&gt;
&lt;br /&gt;
'''Wednesday PM'''&lt;br /&gt;
*Cary, taller than Becky, will not sing.&lt;br /&gt;
&lt;br /&gt;
'''Thursday AM'''&lt;br /&gt;
&lt;br /&gt;
== Session Timer Volunteers ==&lt;br /&gt;
&lt;br /&gt;
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop with a stopwatch program).  It's good to have two people in each slot to back each other up in case of machinery failure.&lt;br /&gt;
&lt;br /&gt;
'''Schedule for Session Timers'''&lt;br /&gt;
&lt;br /&gt;
'''Tuesday AM'''&lt;br /&gt;
&lt;br /&gt;
* Francis Kayiwa (Mr. Sweetie Poo https://www.youtube.com/watch?v=xAnVNXaa5oA)&lt;br /&gt;
* Sarah Simpkin (at sarahsimpkin)&lt;br /&gt;
&lt;br /&gt;
'''Tuesday PM'''&lt;br /&gt;
*Maura Carbone&lt;br /&gt;
&lt;br /&gt;
'''Wednesday AM'''&lt;br /&gt;
* John Sarnowski (at ResCarta)&lt;br /&gt;
* Sarah Simpkin (at sarahsimpkin)&lt;br /&gt;
&lt;br /&gt;
'''Wednesday PM'''&lt;br /&gt;
* Dominic Bordelon&lt;br /&gt;
&lt;br /&gt;
'''Thursday AM'''&lt;br /&gt;
&lt;br /&gt;
== Raffles ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Whatever Else Needs to be Done ==&lt;br /&gt;
&lt;br /&gt;
* Sarah Simpkin (at sarahsimpkin)&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2015]]&lt;/div&gt;</summary>
		<author><name>AshleyBlewer</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_During_the_Conference_Volunteers&amp;diff=42539</id>
		<title>2015 During the Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_During_the_Conference_Volunteers&amp;diff=42539"/>
				<updated>2015-01-29T23:57:40Z</updated>
		
		<summary type="html">&lt;p&gt;AshleyBlewer: adding myself for video watch&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;code4lib 2015 During the Conference Volunteers&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--== Hospitality Suite Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee makes arrangements for any hospitality suite amenities (technology, snacks, games, icebreakers...) we may want.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Preconference Setup Help ==&lt;br /&gt;
&lt;br /&gt;
Help manage preconference sessions, setting up projectors, etc.&lt;br /&gt;
&lt;br /&gt;
* John Sarnowski (at ResCarta)&lt;br /&gt;
* Whitni Watkins (at NimbleLibrarian)&lt;br /&gt;
* Christina Harlow (at cm_harlow)&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
== Welcome Wagon Committee ==&lt;br /&gt;
&lt;br /&gt;
Offers conference newcomers an opportunity to self-identify; offers oldtimers an opportunity to meet newcomers. May also want to constitute a year-round variation for #code4lib.&lt;br /&gt;
&lt;br /&gt;
* Becky Yoose (b.yoose at google)&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
Responsible for non-IRC social networking presence.&lt;br /&gt;
&lt;br /&gt;
1-2 person(s) to take questions for sessions (assuming there's time during the session) via Twitter/IRC, and adding resources to lanyrd schedule (slides, notes, resources mentioned, etc.) Make a note if you can only do one or both.&lt;br /&gt;
&lt;br /&gt;
Consider directing people with questions to presenter on twitter/IRC (if applicable) if there is no time for questions.&lt;br /&gt;
&lt;br /&gt;
*Whitni Watkins (at NimbleLibrarian)&lt;br /&gt;
* Christina Harlow (at cm_harlow)&lt;br /&gt;
&lt;br /&gt;
== Beverage Share Setup/Teardown ==&lt;br /&gt;
&lt;br /&gt;
Help set up and clean up after the Tuesday event at the Ebay offices.&lt;br /&gt;
&lt;br /&gt;
* Karen Estlund - setup&lt;br /&gt;
* John Sarnowski - clean up (at ResCarta)&lt;br /&gt;
* Dominic Bordelon - clean up&lt;br /&gt;
* Whitni Watkins - setup (at NimbleLibrarian)&lt;br /&gt;
&lt;br /&gt;
== IRC Helpers ==&lt;br /&gt;
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.&lt;br /&gt;
&lt;br /&gt;
* Chad Nelson (bibliotechy)&lt;br /&gt;
One of the easiest ways to participate is to [http://webchat.freenode.net/ Go here] with your web browser. Choose a nickname (anything works so long as it is unique; if you want to be anonymous pick appropriately). Enter &amp;quot;code4lib&amp;quot; as the &amp;quot;Channel&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
If you've managed to get into the channel without help, type &amp;quot;@helpers&amp;quot; (without the quotes) to see a list of #code4lib helpers.&lt;br /&gt;
&lt;br /&gt;
== IRC Access ==&lt;br /&gt;
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people&lt;br /&gt;
&lt;br /&gt;
* Mx Matienzo (anarchivist)&lt;br /&gt;
&lt;br /&gt;
==Registration Desk Volunteers==&lt;br /&gt;
&lt;br /&gt;
'''Monday'''&lt;br /&gt;
* John Sarnowski (at ResCarta)&lt;br /&gt;
* Whitni Watkins (at NimbleLibrarian) -- if we only need one desk volunteer, let me know.  &lt;br /&gt;
'''Tuesday'''&lt;br /&gt;
* Christina Harlow (at cm_harlow)&lt;br /&gt;
* Whitni Watkins (at NimbleLibrarian) -- if we only need one desk volunteer, let me know.&lt;br /&gt;
'''Wednesday'''&lt;br /&gt;
* Christina Harlow (at cm_harlow)&lt;br /&gt;
&lt;br /&gt;
==Video Streaming==&lt;br /&gt;
We need two volunteers for each session, one at the front near the speaker and one at the rear at the camera/encoder.&lt;br /&gt;
We will have a brief training on Monday Afternoon. If you can't make the training, we will perform magic knowledge transfer.&lt;br /&gt;
This is not a highly technical position, if you can recognize a video camera two times out of three, you're in.&lt;br /&gt;
&lt;br /&gt;
You are welcome to work multiple sessions, or all of them. This will get you really good karma and many free drinks.&lt;br /&gt;
&lt;br /&gt;
'''Tuesday AM'''&lt;br /&gt;
&lt;br /&gt;
Ashley Blewer (at ablwr)&lt;br /&gt;
&lt;br /&gt;
'''Tuesday PM'''&lt;br /&gt;
&lt;br /&gt;
Ashley Blewer (at abler)&lt;br /&gt;
&lt;br /&gt;
'''Wednesday AM'''&lt;br /&gt;
&lt;br /&gt;
Ashley Blewer (at abler)&lt;br /&gt;
&lt;br /&gt;
'''Wednesday PM'''&lt;br /&gt;
&lt;br /&gt;
Ashley Blewer (at abler)&lt;br /&gt;
&lt;br /&gt;
'''Thursday AM'''&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
'''Tuesday AM'''&lt;br /&gt;
&lt;br /&gt;
'''Tuesday PM'''&lt;br /&gt;
&lt;br /&gt;
'''Wednesday AM'''&lt;br /&gt;
*Becky, destroyer of last names, singer of badly adapted show tunes &lt;br /&gt;
&lt;br /&gt;
'''Wednesday PM'''&lt;br /&gt;
&lt;br /&gt;
'''Thursday AM'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Session Timer Volunteers ==&lt;br /&gt;
&lt;br /&gt;
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop with a stopwatch program).  It's good to have two people in each slot to back each other up in case of machinery failure.&lt;br /&gt;
&lt;br /&gt;
'''Schedule for Session Timers'''&lt;br /&gt;
&lt;br /&gt;
'''Tuesday AM'''&lt;br /&gt;
&lt;br /&gt;
* Francis Kayiwa (Mr. Sweetie Poo https://www.youtube.com/watch?v=xAnVNXaa5oA)&lt;br /&gt;
&lt;br /&gt;
'''Tuesday PM'''&lt;br /&gt;
*Maura Carbone&lt;br /&gt;
&lt;br /&gt;
'''Wednesday AM'''&lt;br /&gt;
* John Sarnowski (at ResCarta)&lt;br /&gt;
'''Wednesday PM'''&lt;br /&gt;
* Dominic Bordelon&lt;br /&gt;
&lt;br /&gt;
'''Thursday AM'''&lt;br /&gt;
&lt;br /&gt;
== Raffles ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Whatever Else Needs to be Done ==&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2015]]&lt;/div&gt;</summary>
		<author><name>AshleyBlewer</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&amp;diff=42019</id>
		<title>2015 Preconference Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&amp;diff=42019"/>
				<updated>2014-11-07T23:08:22Z</updated>
		
		<summary type="html">&lt;p&gt;AshleyBlewer: /* Visualizing Library Data */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Instructions ==&lt;br /&gt;
Thank you for considering proposing a pre-conference! Here are a few details:&lt;br /&gt;
&lt;br /&gt;
* We will be taking pre-conference proposals until '''November 7, 2014'''&lt;br /&gt;
* 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&lt;br /&gt;
* Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]&lt;br /&gt;
* 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!)&lt;br /&gt;
* 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&lt;br /&gt;
* '''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&lt;br /&gt;
* Please use the template for proposals provided in the pre-formatted block below&lt;br /&gt;
&lt;br /&gt;
=== Proposal formatting guidelines: ===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Preconference Title: ===&lt;br /&gt;
 &lt;br /&gt;
One of:&lt;br /&gt;
'''&amp;quot;Full Day&amp;quot;''' &lt;br /&gt;
'''&amp;quot;Half Day [Morning]&amp;quot;''' &lt;br /&gt;
'''&amp;quot;Half Day [Afternoon]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Facilitator's name, affiliation, and email address&lt;br /&gt;
* Second facilitator's name, affiliation, email address, if second speaker&lt;br /&gt;
&lt;br /&gt;
Abstract&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Pre-conference Proposals ==&lt;br /&gt;
&lt;br /&gt;
Post your ideas here!&lt;br /&gt;
&lt;br /&gt;
=== Delivering and Preserving GIS Data ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Morning]'''&lt;br /&gt;
&lt;br /&gt;
* Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Jack Reed, Stanford University, pjreed@stanford.edu&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# [[User:Ssimpkin|Sarah Simpkin]]&lt;br /&gt;
# Vicky Steeves&lt;br /&gt;
# Andrew Battista&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== A hands-on introduction to GeoBlacklight ===&lt;br /&gt;
&lt;br /&gt;
'''Half Day [Afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Jack Reed, Stanford University, pjreed@stanford.edu&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;Delivering and Preserving GIS Data&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# [[User:Ssimpkin|Sarah Simpkin]]&lt;br /&gt;
# Vicky Steeves&lt;br /&gt;
# Andrew Battista&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
===RailsBridge: Intro to programming in Ruby on Rails===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu&lt;br /&gt;
* Additional instructors welcome&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Maura Carbone&lt;br /&gt;
#Vicky Steeves&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Replace yourself with a painfully complex bash script...or try Ansible ===&lt;br /&gt;
'''Half Day [Morning]'''&lt;br /&gt;
&lt;br /&gt;
* Chad Nelson, chad dot nelson @ lyrasis dot org&lt;br /&gt;
* Blake Carver, Blake dot carver @lyrasis dot org&lt;br /&gt;
&lt;br /&gt;
Abstract: &lt;br /&gt;
&lt;br /&gt;
[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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
 &lt;br /&gt;
=== Intro to Docker ===&lt;br /&gt;
'''Half Day [Whenever]'''&lt;br /&gt;
&lt;br /&gt;
* John Fink, McMaster University, john dot fink at gmail dot com&lt;br /&gt;
* Francis Kayiwa, Kayiwa Consulting , francis dot kayiwa at gmail dot com&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
[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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
1. Jim Hahn&lt;br /&gt;
&lt;br /&gt;
=== Code Retreat ===&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu&lt;br /&gt;
* Additional facilitators welcome; Especially if you have CodeRetreat experience.&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.&lt;br /&gt;
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.&lt;br /&gt;
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.&amp;quot; [http://coderetreat.org/about About Code Retreat]&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
=== Presentations workshop ===&lt;br /&gt;
 &lt;br /&gt;
'''&amp;quot;Half Day [Afternoon]&amp;quot;'''  (but could be expanded based on interest)&lt;br /&gt;
&lt;br /&gt;
* Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
* Additional facilitators welcome.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
 &lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#Vicky Steeves&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Dive into Hydra  ===&lt;br /&gt;
 &lt;br /&gt;
One of:&lt;br /&gt;
'''&amp;quot;Half Day [Afternoon]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Justin Coyne, Data Curation Experts, justin@curationexperts.com&lt;br /&gt;
* Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;RailsBridge&amp;quot; prior to this workshop.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Maura Carbone&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
#&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
=== code4lib/Write The Docs barcamp ===&lt;br /&gt;
 &lt;br /&gt;
One of:&lt;br /&gt;
'''&amp;quot;Full Day&amp;quot;''', with options for jumping in for half a day&lt;br /&gt;
&lt;br /&gt;
* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu&lt;br /&gt;
* Write the Docs contacts: TBA&lt;br /&gt;
&lt;br /&gt;
Abstract&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Remember, like metadata, documentation is a love note to the future.&lt;br /&gt;
&lt;br /&gt;
More information about Write the Docs at http://conf.writethedocs.org/&lt;br /&gt;
&lt;br /&gt;
There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). &lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
'''Full day'''&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
'''Morning'''&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
'''Afternoon'''&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Linked Data Workshop ===&lt;br /&gt;
&lt;br /&gt;
One of:&lt;br /&gt;
'''&amp;quot;Half Day [morning]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Karen Estlund, University of Oregon, kestlund@uoregon.edu&lt;br /&gt;
* Tom Johnson, DPLA, tom@dp.la&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Logan Cox&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Code4Arc ===&lt;br /&gt;
&lt;br /&gt;
One of:&lt;br /&gt;
'''&amp;quot;Full Day&amp;quot;''' (with options for half day participation)&lt;br /&gt;
&lt;br /&gt;
* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com&lt;br /&gt;
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com&lt;br /&gt;
* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org&lt;br /&gt;
* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? &lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
&lt;br /&gt;
* Panel type conversations about the State of Art in Archives &lt;br /&gt;
* Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed &lt;br /&gt;
* Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
When signing up, please indicate if you are an end-user or a developer.&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Laney McGlohon - developer&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Fail4Lib 2015 ===&lt;br /&gt;
'''Half Day [TBD, probably afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Andreas Orphanides, akorphan (at) ncsu.edu&lt;br /&gt;
* Jason Casden, jmcasden (at) ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
&lt;br /&gt;
* Case studies. Avoid our own mistakes by bearing witness to the failures of others.&lt;br /&gt;
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
''Interested in attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Coding Custom Solutions for Every Department in the Library with File Analyzer ===&lt;br /&gt;
 &lt;br /&gt;
One of:&lt;br /&gt;
'''&amp;quot;Half Day [Morning]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Terry Brady, Georgetown University Library, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
Abstract&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Analyzing Marc Records for the Cataloging department&lt;br /&gt;
* Transferring ILS invoices for the University Account System for the Acquisitions department &lt;br /&gt;
* Delivering patron fines to the Bursar’s office for the Access Service department&lt;br /&gt;
* Summarizing student worker timesheet data for the Finance department&lt;br /&gt;
* Validating counter compliant reports for the Electronic Resources department&lt;br /&gt;
* Preparing ingest packages for the Digital Services department&lt;br /&gt;
* Validating checksums for the Preservation department&lt;br /&gt;
&lt;br /&gt;
This hands on workshop will step through the components of the application framework.  Workshop participants will install and develop custom File Analyzer tasks in this session.&lt;br /&gt;
&lt;br /&gt;
The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Whenever]'''&lt;br /&gt;
&lt;br /&gt;
* Karen A. Coombs, OCLC, coombsk@oclc.org&lt;br /&gt;
&lt;br /&gt;
Abstract&lt;br /&gt;
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.&lt;br /&gt;
 &lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== UXtravaganza ===&lt;br /&gt;
'''&amp;quot;Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]&amp;quot;'''&lt;br /&gt;
&lt;br /&gt;
* William Hicks, University of North Texas, William.hicks@unt.edu&lt;br /&gt;
* Volunteers?&lt;br /&gt;
&lt;br /&gt;
Abstract&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
* '''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 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.&lt;br /&gt;
&lt;br /&gt;
* '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation.  Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc.&lt;br /&gt;
&lt;br /&gt;
* '''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.&lt;br /&gt;
&lt;br /&gt;
* '''The Eye’s Have It.''' The UNT Libraries is also 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 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.&lt;br /&gt;
&lt;br /&gt;
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&amp;quot;, 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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your&lt;br /&gt;
name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Intro to Git &amp;amp; possibly beyond ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Whenever]'''&lt;br /&gt;
&lt;br /&gt;
* Erin Fahy, Stanford University, efahy@stanford.edu&lt;br /&gt;
* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
* What is a Distributed Version Control System?&lt;br /&gt;
* What's the difference between Git and Github.com?&lt;br /&gt;
* How to initialize new Git projects locally and on a remote server/Github&lt;br /&gt;
* Cloning/Forking existing projects and keeping up to date&lt;br /&gt;
* The wonderful world of Git branches&lt;br /&gt;
* Interactive rebasing&lt;br /&gt;
* Contributing code to existing projects &amp;amp; what pull requests are&lt;br /&gt;
* How to handle merge conflicts&lt;br /&gt;
* Overview of workflows and branch best practices&lt;br /&gt;
* (time allowing) Advanced git: pre/post hooks, submodules, anything else?&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Visualizing Library Data ===&lt;br /&gt;
 &lt;br /&gt;
'''&amp;quot;Half Day [Morning||Afternoon]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Ashley Blewer!&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]]&lt;/div&gt;</summary>
		<author><name>AshleyBlewer</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&amp;diff=41917</id>
		<title>2015 Prepared Talk Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&amp;diff=41917"/>
				<updated>2014-11-05T14:04:56Z</updated>
		
		<summary type="html">&lt;p&gt;AshleyBlewer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Code4lib 2015 is a loosely-structured conference that provides people working at the intersection of libraries/archives/museums/cultural heritage and technology with a chance to share ideas, be inspired, and forge collaborations. For more information about the Code4lib community, please visit http://code4lib.org/about/. &lt;br /&gt;
The conference will be held at the Portland Hilton &amp;amp; Executive Tower in Portland, Oregon, from February 9-12, 2015.&lt;br /&gt;
&lt;br /&gt;
'''Proposals for Prepared Talks:'''&lt;br /&gt;
&lt;br /&gt;
We encourage everyone to propose a talk.&lt;br /&gt;
 &lt;br /&gt;
Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:&lt;br /&gt;
* Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software&lt;br /&gt;
* Tools and technologies – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)&lt;br /&gt;
* Technical issues - Big issues in library technology that should be addressed or better understood&lt;br /&gt;
* Relevant non-technical issues – Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc.&lt;br /&gt;
&lt;br /&gt;
Proposals can be submitted through Friday, November 7, 2014 at 5pm PST (GMT−8). Voting will start on November 11, 2014 and continue through November 25, 2014. The URL to submit votes will be announced on the Code4Lib website and mailing list and will require an active code4lib.org account to participate. The final list of presentations will be announced in early- to mid-December.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Proposals for Prepared Talks:'''&lt;br /&gt;
&lt;br /&gt;
Log in to the Code4lib wiki and edit this wiki page using the prescribed format. If you are not already registered, follow the instructions to do so.&lt;br /&gt;
Provide a title and brief (500 words or fewer) description of your proposed talk.&lt;br /&gt;
If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist voters in opening the conference to new presenters.&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Talk Title: ==&lt;br /&gt;
 &lt;br /&gt;
* Speaker's name,  email address, and (optional) affiliation&lt;br /&gt;
* Second speaker's name, email address, and affiliation, if second speaker&lt;br /&gt;
&lt;br /&gt;
Abstract of no more than 500 words.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Talk Proposals'''&lt;br /&gt;
==Refinery — An open source locally deployable web platform for the analysis of large document collections==&lt;br /&gt;
 &lt;br /&gt;
* [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com&lt;br /&gt;
&lt;br /&gt;
Refinery is an open source web platform for the analysis of large unstructured document collections. It extracts meaningful semantic themes within documents also known as &amp;quot;topics&amp;quot; which can be thought of as word clouds composed of terms that highly co-occur with one another. Once this semantic index is formed, one can extract relevant documents related to these topics and further refine their contents through a summarization process that allows users to search for phrases that are relevant to them within the corpus. The goal of Refinery is to make this whole process easier and to provide some of the latest scalable versions of these learning algorithms in an intuitive web-based interface. Refinery is also meant to be run locally, thus bypassing the need for securing document collections over the internet. The talk will go through some of the technologies involved and a demo of the app.&lt;br /&gt;
&lt;br /&gt;
For more info check out http://www.docrefinery.org.&lt;br /&gt;
&lt;br /&gt;
==Drupal 8 — Evolution &amp;amp; Revolution==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Drupal 8 is in beta and nearing release. Among its many features, it notably has become more developer friendly through its adoption of the Symfony PHP framework along with Symfony's outstanding set of libraries (like Guzzle) and tools (like Composer). And, in implementing the Twig theming system, it is can begin to escape PHPtemplate. These moves also make it easier to create headless systems that uses Angular.js and other systems for presentation, or even forgo presentation entirely.&lt;br /&gt;
&lt;br /&gt;
From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.&lt;br /&gt;
&lt;br /&gt;
==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==&lt;br /&gt;
 &lt;br /&gt;
* [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]],  stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]&lt;br /&gt;
&lt;br /&gt;
GameSalad is a popular tool for developing mobile and desktop games with little actual programming. In this presentation, Stan Bogdanov breaks down the development process he followed while building [https://github.com/stanrb/mobiLit mobiLit], a mobile app with the goal of being the first open-source gamified information literacy app to be used as part of a college-level information literacy curriculum. He will go through the basics of using GameSalad to create an app that can be easily customized by non-programmers and the instructional principles used to teach the material in a mobile medium. Stan will also go through two qualitative design studies he did on the app and discuss their results and the lessons learned from building mobiLit. The session will conclude with an overview of the next steps for the [https://github.com/stanrb/mobiLit mobiLit project].&lt;br /&gt;
&lt;br /&gt;
==The Impossible Search: Pulling data form unknown sources==&lt;br /&gt;
 &lt;br /&gt;
* Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com &lt;br /&gt;
&lt;br /&gt;
It's easy to search data you know the structure of, but what if you need to pull in data from sources that don't have a standard structure. The ability to search community events along with your standard catalog search results is an example, but often the only way to pull these events is through XML, JSON, (Insert structured format here), or even just raw html. But how do you get that structure? That simple question is what makes this impossible. The process to define and process this structure takes a lot of manual labor, especially if the data you are pulling is just HTML, and then every time you add data to the index you have to run all the data through a script to pull in data in a format Solr or an other index can use. This talk will focus on Solr, but the principles explained will apply to many other indexes.&lt;br /&gt;
&lt;br /&gt;
==What! You're Not Using Docker?==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Boring part: Docker[1] is a container system that provides benefits similar to virtualization with only a fraction of the overhead. Scintillating part: Docker can host between four to six times the number of service instances than systems such as Xen or VMWare on a given piece of hardware. But thats not all! Docker also makes it simple(r) to create transportable instances, so you can spin up development servers on your laptop.&lt;br /&gt;
&lt;br /&gt;
*[1]https://www.docker.com/&lt;br /&gt;
&lt;br /&gt;
== Video Accessibility, WebVTT, and Timed Text Track Tricks ==&lt;br /&gt;
&lt;br /&gt;
* Jason Ronallo, jronallo@gmail.com, NCSU Libraries&lt;br /&gt;
&lt;br /&gt;
Video on the Web presents new challenges and opportunities. How do you make your video more accessible to those with various disabilities and needs? I'll show you how. This presentation will focus on how to write and deliver captions, subtitles, audio descriptions, and timed metadata tracks for Web video using the WebVTT W3C standard. Encoding timed text tracks in this way opens up opportunities for new functionality on your websites beyond accessibility. The presentation will show some examples of the potential for using timed text tracks in creative ways. I'll cover all the HTML and JavaScript you will need to know as well as some of the CSS and other bits you could probably do without but are too fun to pass up.&lt;br /&gt;
&lt;br /&gt;
== Categorizing Records with Random Forests ==&lt;br /&gt;
 &lt;br /&gt;
* Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library&lt;br /&gt;
Academic libraries are increasingly responsible for providing ingest, search, discovery, and analysis for data sets.  Emerging techniques from data science and machine learning can provide librarians and developers with an opportunity to generate new insights and services from these document collections.  This presentation will provide a brief overview of common machine learning classification techniques, then dive into a more detailed example using a random forest to assign keywords to research data sets.  The talk will emphasize the insight that can be gained from machine learning rather than the inner workings of the algorithms.  The overall goal of this presentation is to provide librarians and developers with the context to recognize an opportunity to apply machine learning categorization techniques at their home campuses and organizations.  &lt;br /&gt;
&lt;br /&gt;
== Data Science in Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Devon Smith, smithde@oclc.org, OCLC&lt;br /&gt;
&lt;br /&gt;
Data Science is increasing in buzz and hype. I'll go over what it is, what it isn't, and how it fits in libraries.&lt;br /&gt;
&lt;br /&gt;
== PDF metadata extraction for academic literature == &lt;br /&gt;
&lt;br /&gt;
* Kevin Savage, kevin.savage at mendeley.com, Mendeley&lt;br /&gt;
* Joyce Stack, joyce.stack at mendeley.com, Mendeley&lt;br /&gt;
&lt;br /&gt;
Mendeley recently added a, &amp;quot;document from file,&amp;quot; endpoint to its API which attempts to extract metadata such as title and authors directly from PDF files. This talk will describe at a high level the machine learning methods we used including how we measured and tuned our model. We will then delve more deeply into our stack, the tools we used, some of the things that didn't work and why PDFs are the worst thing ever to compute over.&lt;br /&gt;
&lt;br /&gt;
== Giving Users What They Want: Record Grouping in VuFind ==&lt;br /&gt;
 &lt;br /&gt;
* Mark Noble,  mark@marmot.org, [//www.marmot.org Marmot Library Network]&lt;br /&gt;
&lt;br /&gt;
In 2013, Marmot did extensive usability studies with patrons to determine what was difficult in the catalog.  Many patrons had problems sifting through all of the various formats and editions of a title.  In 2014 we developed a method for [//mercury.marmot.org/Union/Search?lookfor=divergent grouping records] so only a single work is shown in search results and all formats and editions are listed under that work.  We will discuss our definition of a 'work' based on FRBR principles; combining meta data from MARC records with metadata from other sources like OverDrive; the technical details of Record Grouping; the design decisions made during implementation; and the reaction from users and staff.&lt;br /&gt;
&lt;br /&gt;
== Topic Space: a mobile augmented reality recommendation app ==&lt;br /&gt;
&lt;br /&gt;
* Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign&lt;br /&gt;
&lt;br /&gt;
The Topic Space module (http://minrvaproject.org/modules_topicspace.php ) was developed with an IMLS Sparks! Grant to investigate augmented reality technologies for in-library recommendations. The funding allowed for sustained university community collaboration by the University Library, the Graduate School of Library and Information Science, as well as graduate student programmers sourced from the Department of Computer Science. Collaborators designed app functionality and identified relevant open source libraries that could power optical character recognition (OCR) functionality from within the mobile phone.&lt;br /&gt;
&lt;br /&gt;
Topic space allows a user to take a picture of an item's call number in the book stacks. The module will show the user other books that are relevant but that are not shelved nearby. It can also show users books that are normally shelved here but that are currently checked out. Recommendations are based on Library of Congress subject headings and ILS circulation data which indicate recommendation candidates based on total check-outs. &lt;br /&gt;
&lt;br /&gt;
Research questions included development of back end (server-side) pattern matching algorithms for recommendations, and a rapid formative evaluation of interface design that would provide optimal user experience for navigation of the book stacks as a context to recommendations.&lt;br /&gt;
&lt;br /&gt;
Along with the Topic Space native app, grant collaborators prototyped web based recommendations which could serve as a new way of providing readers advisory and “more like this” recommendations from discovery interfaces accessed through desktop browsers. Outcomes of the grant include the availability of the [https://play.google.com/store/apps/details?id=edu.illinois.ugl.minrva Topic Spaces module within Minrva app on the Android Play store] and an experimental [http://backbonejs.org/ Backbone.js] based [http://minrva-dev.library.illinois.edu Topic Space web app].&lt;br /&gt;
&lt;br /&gt;
== Leveling Up Your Git Workflow ==&lt;br /&gt;
&lt;br /&gt;
* Megan Kudzia, moneill@albion.edu, Albion College Library&lt;br /&gt;
* Kate Sears, eks11@albion.edu, Albion College Library&lt;br /&gt;
&lt;br /&gt;
Have you started experimenting with Git on your own, but now you need to include others in your projects? Learn from our mistakes! Transitioning from a one-person git workflow and repo structure, to a structure that includes multiple people (including student workers), is not for the faint of heart. We'll talk about why we decided to work this way, our path to developing a git culture amongst ourselves, conceptual and technical difficulties we've faced, what we learned, and where we are now. Also with pretty pictures (aka workflow drawings).&lt;br /&gt;
&lt;br /&gt;
== Drone Loaning Program: Because Laptops are so last century ==&lt;br /&gt;
&lt;br /&gt;
 * Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries&lt;br /&gt;
 * Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries&lt;br /&gt;
&lt;br /&gt;
At Univ. Maryland we are in the very early stages of looking into allowing our student body get their hands on a drone. Yes that's right we will let students take out a drone for n amount of hours to work on projects of their choosing. The talk will talk about the logistics of getting a program of this sort from concept to &amp;quot;Is the drone available?&amp;quot;. If people sign waivers we will also promise not to crash the drone into code4lib attendees.&lt;br /&gt;
&lt;br /&gt;
== Got Git? Getting More Out of Your GitHub Repositories ==&lt;br /&gt;
&lt;br /&gt;
 * Terry Brady, twb27@georgetown.edu, Georgetown University Library&lt;br /&gt;
&lt;br /&gt;
This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories. &lt;br /&gt;
&lt;br /&gt;
In additional to all of the great benefits of using Git for code management, the GitHub interface provides a powerful set of tools to showcase a project and to keep your users informed of developments to your project.  These tools can assist with marketing and outreach - turning your code repository into a focus of conversation!&lt;br /&gt;
&lt;br /&gt;
* [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]&lt;br /&gt;
* [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]&lt;br /&gt;
* [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]&lt;br /&gt;
* [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]&lt;br /&gt;
* Gists for code sharing&lt;br /&gt;
* Private Repositories and Organizational Groups&lt;br /&gt;
* Pull Request Conversation Tracking&lt;br /&gt;
* Customized Issue management&lt;br /&gt;
&lt;br /&gt;
== Quick Wins for Every Department in the Library - File Analyzer! ==&lt;br /&gt;
&lt;br /&gt;
 * Terry Brady, twb27@georgetown.edu, Georgetown University Library&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.&lt;br /&gt;
* Analyzing Marc Records for the Cataloging department&lt;br /&gt;
* Transferring ILS invoices for the University Account System for the Acquisitions department &lt;br /&gt;
* Delivering patron fines to the Bursar’s office for the Access Service department&lt;br /&gt;
* Summarizing student worker timesheet data for the Finance department&lt;br /&gt;
* Validating COUNTER compliant reports for the Electronic Resources department&lt;br /&gt;
* Generating ingest packages for the Digital Services department&lt;br /&gt;
* Validating checksums for the Preservation department&lt;br /&gt;
&lt;br /&gt;
Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!&lt;br /&gt;
&lt;br /&gt;
==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor&lt;br /&gt;
&lt;br /&gt;
The transition from paper maps to digital ones changed much more than the maps themselves; it changed the very foundation of how we work and how we find each other. Now maps are transforming again.  The Geospatial World is moving from GIS systems that are institutionally-focused, expensive, feature-burdened, and binds data into a complicated and demanding user-hostile interface. From this transition from digital to web-based digital geospatial tools has come growth and development in new forms of map-based investigative journalism, activism, scholarship, and business ventures. This talk will highlight the conditions and strategies that made these changes possible as a means to draw a path by which librarians through our own work may follow, dragons notwithstanding. &lt;br /&gt;
&lt;br /&gt;
== Building Your Own Federated Search ==&lt;br /&gt;
&lt;br /&gt;
* Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco&lt;br /&gt;
&lt;br /&gt;
Advances in modern browsers have created some interesting possibilities for federated search. This presentation will cover common techniques and pitfalls in building a federated search. We will discuss what principles guided our decisions when implementing our own federated search. We will show tools we've built and our findings from building and using experimental prototypes.&lt;br /&gt;
&lt;br /&gt;
Your higher education institution likely offers dozens of online resources for educators, students, researchers, and the public. And each of these online resources likely has its own search tool. But users can't be expected to search in dozens of different interfaces to find what they're looking for. A typical solution for this issue is federated search. &lt;br /&gt;
&lt;br /&gt;
==  Indexing Linked Data with LDPath ==&lt;br /&gt;
&lt;br /&gt;
* Chris Beer, cabeer@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
LDPath [1] is a simple query language for indexing linked open data, with support for caching, content negotiation, and integration with non-RDF endpoints. This talk will demonstrate the features and potential of the language and framework to index a resource with links into id.loc.gov, viaf.org, geonames.org, etc to build an application-ready document.&lt;br /&gt;
&lt;br /&gt;
[1] http://marmotta.apache.org/ldpath/language.html&lt;br /&gt;
&lt;br /&gt;
== Show Me the Money: Integrating an LMS with Payment Providers ==&lt;br /&gt;
 &lt;br /&gt;
* Josh Weisman,  Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group&lt;br /&gt;
&lt;br /&gt;
In order to provide an easy and convenient way for patrons to pay fines, we are exploring ways to integrate the library management system with online payment providers such as PayPal. With many LMS systems being designed and developed for the cloud, we should be able to provide the frictionless user experience our patrons have come to expect from online transactions. In this session we'll discuss strategies for integration and review a sample application which uses REST APIs from a library management system to integrate with PayPal.&lt;br /&gt;
&lt;br /&gt;
== Shibboleth Federated Authentication for Library Applications: ==&lt;br /&gt;
&lt;br /&gt;
* Scott Fisher, scott.fisher@ucop.edu, California Digital Library&lt;br /&gt;
* Ken Weiss, ken.weiss@ucop.edu, California Digital Library&lt;br /&gt;
&lt;br /&gt;
Shibboleth is the most widely-used method to provide single-sign-on authentication to academic applications where users come from many different institutions. Shibboleth, the InCommon education and research trust framework, and the SAML protocol comprise a very powerful - but very complicated - solution to this very complicated problem. Scott and Ken have implemented Shibboleth for multiple library applications. They will share their understanding of the good, the bad, and the underlying spaghetti that makes it all work. Ken will discuss some of the technical aspects of the solution, touching on optimal and non-optimal use cases, administrative challenges, and authorization concerns. Scott will describe the implementation pattern for multi-institution single-sign-on that the California Digital Library has evolved, using the recently released Dash application (http://dash.cdlib.org) as an example.&lt;br /&gt;
&lt;br /&gt;
==Scientific Data: A Needs Assessment Journey==&lt;br /&gt;
 &lt;br /&gt;
*[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History&lt;br /&gt;
&lt;br /&gt;
While surveying digital research and collections data in the research science divisions at the American Museum of Natural History in NYC (as a part of my [http://ndsr.nycdigital.org/ National Digital Stewardship Residency] project), I have come across the big data hogs (genome sequencing and CT scanning) and the little pieces of data (images, publications), all equally important to not only scientific discovery, but as nodes in the history of science. &lt;br /&gt;
&lt;br /&gt;
In this session, I will discuss the development of my needs assessment surveys for scientific datasets and the interview process with Museum curators and researchers as background, seguing into an explanation of the results. I will then combine my findings into preliminary selection criteria to choose tools for digital preservation and management unique to scientific datasets. This will brooke a discussion on emerging standards, tools, and technologies in big data, specific to research science. &lt;br /&gt;
&lt;br /&gt;
I will conclude with preliminary findings on emerging technology that can be used to answer concerns surrounding the management and digital preservation of these data. I am hoping the Q&amp;amp;A session can be used to both answer questions about my project, and function as a way for you (the larger tech-savy library community)  to discuss the tools I’ve touched on in this talk. &lt;br /&gt;
&lt;br /&gt;
== Feminist Human Computer Interaction (HCI) in Library Software ==&lt;br /&gt;
 &lt;br /&gt;
* Bess Sadler,  bess@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
Libraries are not neutral repositories of knowledge. Library classification systems and search technologies tend to reflect the inequalities, biases, ethnocentrism, and power imbalances of the societies in which they are built [1]. How might we better resist these tendencies in the library software we create? This talk will examine some qualities of feminist HCI (pluralism, self-disclosure, participation, ecology, advocacy, and embodiment) [2] through the lens of library software. &lt;br /&gt;
&lt;br /&gt;
[1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.&lt;br /&gt;
&lt;br /&gt;
[2] Bardzell, Shaowen. Feminist HCI: Taking Stock and Outlining an Agenda for Design. CHI 2010: HCI For All. http://dmrussell.net/CHI2010/docs/p1301.pdf&lt;br /&gt;
&lt;br /&gt;
== Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==&lt;br /&gt;
&lt;br /&gt;
* Audrey Altman, audrey at dp.la, Digital Public Library of America&lt;br /&gt;
* Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America&lt;br /&gt;
* Mark Breedlove, mark at dp.la, Digital Public Library of America&lt;br /&gt;
&lt;br /&gt;
The Digital Public Library of America aggregates metadata for over 8 million objects from more than 24 direct partners, or Hubs, using its Metadata Application Profile (MAP), an RDF metadata application profile based on the Europeana Data Model. After working with the initial system for harvesting, mapping and enhancing our Hub’s metadata for a year, we realized that it was inadequate for working with data at this scale. There were architectural issues; it was opaque to non-developer and partner staff; there were inadequate tools for quality assurance and analysis; and the system was unaware that it was working with RDF data. As the network of Hubs expanded and we ingested more metadata, it became harder and harder to know when or why a harvest, a mapping task, or an enrichment went wrong because the tools for quality assurancewere largely inadequate. &lt;br /&gt;
&lt;br /&gt;
The DPLA Content and Technology teams decided to develop a new system from the ground up to address those problems. Development of Heidrun, the internal version of the new system, started in October 2014. Heidrun’s goals are to make it easier for us to harvest and map metadata from various sources and in variety of schemas to the DPLA MAP, to better enrich that metadata using external data sources, and to actively involve our partners in the ingestion process through access to better QA tools. Heidrun and its componentry are built on Ruby on Rails, Blacklight, and ActiveTriples. Our presentation will give some background on our design principles and processes used during development, the architecture of the system, and its functionality. We plan to release a version of Heidrun and its components as a generalized metadata aggregation system for use by DPLA Hubs and others working to aggregate cultural heritage metadata.&lt;br /&gt;
&lt;br /&gt;
== OS or GTFO: Program or Perish ==&lt;br /&gt;
*Tessa Fallon, tessa.fallon@gmail.com&lt;br /&gt;
&lt;br /&gt;
Description TBD&lt;br /&gt;
&lt;br /&gt;
== Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==&lt;br /&gt;
* Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries&lt;br /&gt;
Would your library like to have large digital signage that displays dynamic information such as library hours, weather, room availability, and more? Have you looked into purchasing large digital signage, only to be turned off by the high price tag and lack of customization available with commercial solutions? Our library has developed a cheap and effective alternative to these systems using HTML 5 authoring software, a large TV, and freely-available APIs from Google, Springshare, and others. At this session, you’ll learn about the system that we have in place for displaying dynamic and easily-updatable information on our library’s large digital display, and how you can easily create something similar for your library.&lt;br /&gt;
&lt;br /&gt;
== REPOX: Metadata Blender ==&lt;br /&gt;
 &lt;br /&gt;
* John Mignault, jmignault@metro.org, Empire State Digital Network&lt;br /&gt;
&lt;br /&gt;
With the growth in the number of hubs providing metadata to the Digital Public Library of America, many of them are using REPOX, a tool originally created for the Europeana project. We'll take a look at REPOX and its capabilities and how it can be useful for ingesting and transforming metadata.&lt;br /&gt;
&lt;br /&gt;
== Beyond Open Source ==&lt;br /&gt;
&lt;br /&gt;
* Jason Casden, jmcasden@ncsu.edu, NCSU Libraries&lt;br /&gt;
* Bret Davidson, bddavids@ncsu.edu, NCSU Libraries&lt;br /&gt;
&lt;br /&gt;
The Code4Lib community has produced an increasingly impressive collection of open source software over the last decade, but much of this creative work remains out of reach for large portions of the library community. Do the relatively privileged institutions represented by a majority of Code4Lib participants have a professional responsibility to support the adoption of their innovations?&lt;br /&gt;
&lt;br /&gt;
Drawing from old and new software packaging and distribution approaches (from freeware to Docker), we will propose extending the open source software values of collaboration and transparency to include the wide and affordable distribution of software. We believe this will not only simplify the process of sharing our applications within the Code4Lib community, but also make it possible for less well resourced institutions to actually use our software. We will identify areas of need, present our experiences with the users of our own open source projects, discuss our attempts to go beyond open source, and make an argument for the internal value of supporting and encouraging a vibrant library ecosystem.&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]] &lt;br /&gt;
[[Category:Talk Proposals]]&lt;br /&gt;
&lt;br /&gt;
== Making It Work: Problem Solving Using Open Source at a Small Academic Library ==&lt;br /&gt;
 &lt;br /&gt;
* Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology&lt;br /&gt;
* Max King, mking9@iit.edu, Illinois Institute of Technology&lt;br /&gt;
&lt;br /&gt;
The Illinois Institute of Technology campus was added to the National Register of Historic Places in 2005, and contains a building, Mies van der Rohe's S.R. Crown Hall, that was named a National Historic Landmark in 2001. Creating a digital resource that can adequately showcase the campus and its architecture is challenge enough in and of itself, but doing so as a two-person team of relative newcomers, at a university library without dedicated programmers on staff, ups the ante considerably.&lt;br /&gt;
The challenges of technical know-how, staff time, and funding are nothing new to anyone working on digital projects at a university library, and are amplified when doing so at a smaller institution. This talk covers the conception, development, and design of the campus map site that was built, concentrating on the problem-solving strategies developed to cope with limited technical and financial resources.&lt;br /&gt;
We'll talk about our approach to development with Open Source software, including Omeka, along with the Neatline and Simile Timeline plugins. We'll also discuss the juggling act of designing for mobile mapping functionality without sacrificing desktop design, weighing the costs of increased functionality versus our ability to time-effectively include that functionality, and the challenge of building a site that could be developed iteratively, with an eye towards future enhancement and sustainability. Finally, we’ll provide recommendations for other librarians at smaller institutions for their own efforts at digital development.&lt;br /&gt;
&lt;br /&gt;
== Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==&lt;br /&gt;
 &lt;br /&gt;
* Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art&lt;br /&gt;
&lt;br /&gt;
The Museum of Modern Art has amassed a large collection of audiovisual materials over its many decades of existence. In order to preserve these materials, much of the audiovisual collection has been digitized. This is a complex process involving numerous steps and devices, and the methods used for digitization can have an effect on the quality of the file that is preserved. Therefore, knowing exactly how something was digitized is critical for future stewards of these objects to be able to properly care for and preserve them. However, detailed technical information about the processes involved in the digitization of audiovisual materials is not defined explicitly in most metadata schemas used for audiovisual materials. In order to record process history using existing metadata standards, some level of creativity is required to allow existing standards to express this information.&lt;br /&gt;
&lt;br /&gt;
This talk will detail different metadata standards, including PBCore, PREMIS, and reVTMD, that can be implemented as methods of recording this information. Specifically, the talk will examine efforts to integrate this metadata into the Museum of Modern Art’s new digital repository, the DRMC. This talk will provide background on the DRMC as well as MoMA’s specific institutional needs for process history metadata, then discuss different metadata implementations we have considered to document process history.&lt;br /&gt;
&lt;br /&gt;
== Pig Kisses Elephant: Building Research Data Services for Web Archives ==&lt;br /&gt;
 &lt;br /&gt;
* Jefferson Bailey,  jefferson@archive.org, Internet Archive&lt;br /&gt;
* Vinay Goel, vinay@archive.org, Internet Archive&lt;br /&gt;
&lt;br /&gt;
More and more libraries and archives are creating web archiving programs.  For both new and established programs, these archives can consist of hundreds of thousands, if not millions, of born-digital resources within a single collection; as such, they are ideally suited for large-scale computational study and analysis. Yet current access methods for web archives consist largely of browsing the archived web in the same manner as browsing the live web and the size of these collections and complexity of the WARC format can make aggregate analysis difficult. This talk will describe a project to create new ways for users and researchers to access and study web archives by offering extracted and post-processed datasets derived from web collections. Working with the 325+ institutions and their 2600+ collections within the Archive-It service, the Internet Archive is building methods to deliver a variety of datasets culled from collections of web content, including extracted metadata packaged in JSON, longitudinal link graph data, named entities, and other types of data. The talk will cover the technical details of building dataset production pipelines with Apache Pig, Hadoop, and tools like Stanford NER, the programmatic aspects of building data services for archives and researchers, and ongoing work to create new ways to access and study web archives.&lt;br /&gt;
&lt;br /&gt;
== Awesome Pi, LOL! ==&lt;br /&gt;
&lt;br /&gt;
* Matt Connolly, mconnolly@cornell.edu, Cornell University Library&lt;br /&gt;
* Jennifer Colt, jrc88@cornell.edu, Cornell University Library&lt;br /&gt;
&lt;br /&gt;
Inspired by Harvard Library Lab’s “Awesome Box” project, Cornell’s Library Outside the Library (LOL) group is piloting a more automated approach to letting our users tell us which materials they find particularly stunning. Armed with a Raspberry Pi, a barcode scanner, and some bits of kit that flash and glow, we have ventured into the foreign world of hardware development. This talk will discuss what it’s like for software developers and designers to get their hands dirty, how patrons are reacting to the Awesomizer, and LOL’s not-afraid-to-fail philosophy of experimentation.&lt;br /&gt;
&lt;br /&gt;
== You Gotta Keep 'em Separated: The Case for &amp;quot;Bento Box&amp;quot; Discovery Interfaces ==&lt;br /&gt;
 &lt;br /&gt;
* Jason Thomale,  jason.thomale@unt.edu, University of North Texas Libraries&lt;br /&gt;
&lt;br /&gt;
I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.&lt;br /&gt;
&lt;br /&gt;
The thing is, practically all of us--in academic libraries at least--have a similar set up for discovery, with just a few variations, and so talking about it still seems useful. Stop me if this sounds familiar. You've got a single search box on the library homepage as a starting point for discovery. And it's probably a tabbed affair, with an option for searching the catalog for books, an option for searching a discovery service for articles, an option for searching databases, and maybe a few others. Maybe you have an option to search everything at once--probably the default, if you have it. And, if you're a crazy hepcat, maybe you ''only'' have your one search that searches everything, with no tabs.&lt;br /&gt;
&lt;br /&gt;
Now, the question is, for your &amp;quot;everything&amp;quot; search, are you doing a combined list of results, or are you doing it bento-box style, with a short results list from each category displayed in its own compartment?&lt;br /&gt;
&lt;br /&gt;
At UNT, we've been holding off on implementing an &amp;quot;everything&amp;quot; search, for various reasons. One reason is that the evidence for either style hasn't been very clear. There's this persistent paradox that we just can't reconcile: users tell us, through word and action, that they prefer searching Google, yet, libraries aren't Google, and there are valid design reasons why we shouldn't try to oversimplify our discovery interfaces to be like Google. And there's user data that supports both sides.&lt;br /&gt;
&lt;br /&gt;
Holding off on making this decision has granted us 2 years of data on how people use our tabbed search interface that does ''not'' include an &amp;quot;everything&amp;quot; search. Recently I conducted a thorough analysis of this data--specifically the usage and query data for our catalog and discovery system (Summon). And I think it helps make the case for a bento box style discovery interface. To be clear, it isn't exactly the smoking gun that I was hoping for, but the picture it paints I think is telling. At the very least, it points away from a combined-results approach.&lt;br /&gt;
&lt;br /&gt;
I'm proposing a talk discussing the data we've collected, the trends we've seen, and what I think it all means--plus other reasons that we're jumping on the &amp;quot;bento box&amp;quot; discovery bandwagon and why I think &amp;quot;bento box&amp;quot; is at this point the path that least sells our souls.&lt;br /&gt;
&lt;br /&gt;
== Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift ==&lt;br /&gt;
 &lt;br /&gt;
* Ashley Blewer!, ashley.blewer@gmail.com&lt;br /&gt;
&lt;br /&gt;
Checksum technology is used all over the place, from git commits to authenticating Linux packages. It is most commonly used in the digital preservation field to monitor materials in storage for changes that will occur over time or used in the transmission of files during duplication. But do you even checksum, bro? I want this talk to move checksums from a position of mysterious macho jargon to something everyone can understand and want to use. I think a lot of people have heard of checksum but don’t know where to begin when it comes to actually using it at their institution. And cryptography is hella intimidating! This talk will cover what checksums are, how they can be integrated into a library or archival workflow, protecting collections requiring additional levels of security, algorithms used to verify file fixity and how they are different, and other aspects of cryptographic technology. Oh, and please note that all points in this talk will be emphasized or lightly performed through Taylor Swift lyrics. Seriously, this talk will consist of at least 50% Taylor Swift. Can you, like, even?&lt;/div&gt;</summary>
		<author><name>AshleyBlewer</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_AVGeeks_Signup&amp;diff=40814</id>
		<title>2014 AVGeeks Signup</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_AVGeeks_Signup&amp;diff=40814"/>
				<updated>2014-03-24T01:57:42Z</updated>
		
		<summary type="html">&lt;p&gt;AshleyBlewer: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[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.  &lt;br /&gt;
&lt;br /&gt;
This event, [http://kingsbarcade.com/2014/03/26/av-geeks-present-when-computers-where-young/ When Computers Were Young], will include &amp;quot;Actual 16mm school films that introduce us to the wonderful world of computers and their potential future -- all before Google!&amp;quot;  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.&lt;br /&gt;
&lt;br /&gt;
'''When:''' Doors open at 7:30 PM.&lt;br /&gt;
&lt;br /&gt;
'''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.&lt;br /&gt;
&lt;br /&gt;
'''Cost:''' The event is free with a suggested $5 donation.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''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:'''&lt;br /&gt;
&lt;br /&gt;
* Steve Morris&lt;br /&gt;
* Laurie Lee Moses - this looks really fun!&lt;br /&gt;
* Heather Rayl - old education films AND Indian food??! What more could a girl want?&lt;br /&gt;
* Anna Headley&lt;br /&gt;
* Ian Walls&lt;br /&gt;
* Kevin Clarke&lt;br /&gt;
* Paula Gray-Overtoom&lt;br /&gt;
* Julia Bauder&lt;br /&gt;
* Josh Wilson&lt;br /&gt;
* Kristen Wilson&lt;br /&gt;
* Michael Blake&lt;br /&gt;
* Junior Tidal&lt;br /&gt;
* Michael Levy&lt;br /&gt;
* Declan Fleming&lt;br /&gt;
* Ed Fugikawa&lt;br /&gt;
* Birkin James Diana&lt;br /&gt;
* Riley Childs (Tentative)&lt;br /&gt;
* Bobbi Fox&lt;br /&gt;
* Mark Breedlove&lt;br /&gt;
* David Drexler (tentative)&lt;br /&gt;
* Chris Clement&lt;br /&gt;
* David Cliff (tentative)&lt;br /&gt;
* Kate Hill and guest Chris Dragga (tentative)&lt;br /&gt;
* Ashley Blewer (YESSSSSSSSS)&lt;br /&gt;
* Vanessa Lucas&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2014]]&lt;/div&gt;</summary>
		<author><name>AshleyBlewer</name></author>	</entry>

	</feed>