<?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=ChristopherHallberg</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=ChristopherHallberg"/>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/Special:Contributions/ChristopherHallberg"/>
		<updated>2026-04-08T16:57:26Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.26.2</generator>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2016_Social_Activities&amp;diff=44018</id>
		<title>2016 Social Activities</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2016_Social_Activities&amp;diff=44018"/>
				<updated>2016-03-09T14:05:22Z</updated>
		
		<summary type="html">&lt;p&gt;ChristopherHallberg: /* Philadelphia Events */&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, March 7th ===&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; &amp;lt;strike&amp;gt;LibGuides alternatives&amp;lt;/strike&amp;gt; spreadsheets.&lt;br /&gt;
&lt;br /&gt;
Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!&lt;br /&gt;
&lt;br /&gt;
''' [https://docs.google.com/document/d/1TYZgZynp0e2q1Mqof_xMH1b-QbqOSmowhI4ms22LA8A/edit#heading=h.qvrpxlt089gj Sign Up Form]'''&lt;br /&gt;
&lt;br /&gt;
'''Plans'''&lt;br /&gt;
* When: Monday, March 7th&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:b.yoose@gmail.com 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;
&lt;br /&gt;
=== Reception at the College of Physicians of Philadelphia / Mütter Museum , Tuesday, March 8th ===&lt;br /&gt;
&lt;br /&gt;
All attendees are invited to join us for a &amp;quot;disturbingly informative&amp;quot; opening reception at the College of Physicians of Philadelphia, home of America’s finest museum of medical history. [http://muttermuseum.org/ The Mütter Museum] displays its beautifully preserved collections of anatomical specimens, models, and medical instruments in a 19th-century “cabinet museum” setting.&lt;br /&gt;
&lt;br /&gt;
The reception includes an open bar and free access to the museum exhibits from 5:45PM through 7:45PM. We will also provide a selection of vegan, vegetarian, and omnivore friendly appetizers featuring: Pennsylvania flatbreads, a locally-sourced variety of sausages, and a Mediterranean spread that includes three different varieties of hummus and other plates.&lt;br /&gt;
&lt;br /&gt;
=== LibTechWomen Meetup, Wednesday, March 9th === &lt;br /&gt;
&lt;br /&gt;
An informal meetup for women and their friends in library technology organized by [http://libtechwomen.org/ #libtechwomen]. No need to RSVP. We'll make sure there's an announcement ahead of time, and some of us will be in the hotel lobby at 5:15 to point people in the right direction. &lt;br /&gt;
&lt;br /&gt;
When: Wednesday, March 9th - 5:30pm - 7pm&lt;br /&gt;
&lt;br /&gt;
Where: [http://www.nationalmechanics.com/ National Mechanics] ([http://nationalmechanics.com/philadelphia-restaurant-menu menu]) at [http://nationalmechanics.com/philadelphia-hours-directions 22 South 3rd St] &lt;br /&gt;
&lt;br /&gt;
Come have a drink (soda is a fine choice!) Eat a snack or a big meal. Stay as long as you want. We just want a good time for the community to connect and chat. &lt;br /&gt;
&lt;br /&gt;
NOTE: There is a small chance we might overcrowd National Mechanics. If we do, there many options within one block. We'll make sure to coordinate such &amp;quot;satellites&amp;quot; if need be.&lt;br /&gt;
&lt;br /&gt;
Questions? Contact  [mailto:deibel@uw.edu Kate]&lt;br /&gt;
&lt;br /&gt;
=== Play and Share in the Conference Hotel, Wednesday, March 9th ===&lt;br /&gt;
A large space in the conference hotel will be available for conference attendees to gather and socialize, play games and share goodies. We will be providing tables and chairs for Board Game Night ([https://docs.google.com/spreadsheets/d/1Y9Iz_tLu6j0gUAeq3iVWQTdSAIDOFaJryzswXF41tgs/edit#gid=0 list of games being brought]), and some attendees are planning to organize an acoustic jam session. You are also welcome to bring stuff to share, from craft sodas and beers to baked goods to local treats ([https://twitter.com/search?f=tweets&amp;amp;vertical=default&amp;amp;q=%23cannoli4lib&amp;amp;src=typd #cannoli4lib]).&lt;br /&gt;
&lt;br /&gt;
== Social Map - Places of Interest==&lt;br /&gt;
&lt;br /&gt;
== Ideas ==&lt;br /&gt;
&lt;br /&gt;
* A trip to [http://barcadephiladelphia.com/food/ Barcade] for vintage arcade games, craft beer, and tacos. Only a ten minute train ride from the conference hotel.&lt;br /&gt;
* #jog4lib - currently being planned on the [https://code4lib.slack.com code4lib Slack channel].&lt;br /&gt;
&lt;br /&gt;
== Local Food ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Restaurants ===&lt;br /&gt;
{|class=&amp;quot;wikitable sortable&amp;quot; style=&amp;quot;text-align: left;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Name &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Variety of Food &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; class=&amp;quot;unsortable&amp;quot; | Address &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Distance from Hotel (miles) &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; class=&amp;quot;unsortable&amp;quot; | Cost &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Take Reservations &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Veg*n Friendly&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.khyberpasspub.com/ Khyber Pass Pub] || Gastropub/Cajun || 56 SW. 2nd Street || 0.1 || $$ || no || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.citytavern.com/ City Tavern] || 18th Century American (historical + founding father's beer recipes) || 138 S. 2nd Street || 0.1 || $$$ || yes || meh&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.zahavrestaurant.com/ Zahav] || Israeli || 237 St. James Place || 0.2 || $$$ || yes || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://handynasty.net/oldcity/hours/ Han Dynasty] || Chinese || 123 Chestnut Street || 0.2 || $$ || meh || vegetarian&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.2ndstorybrewing.com/ 2nd Story Brewing Co] || Brewpub || 117 Chestnut Street || 0.2 || $$ || yes || vegetarian&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.franklinfountain.com/ Franklin Fountain] || Ice Cream || 116 Market Street || 0.2 || $$ || no- cash only || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://philadelphia.amadarestaurant.com/ Amada] || Tapas (Jose Garces) || 217 Chestnut Street || 0.2 || $$$ || yes || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.eulogybar.com/ Eulogy Belgian Tavern] || Belgian || 136 Chestnut Street || 0.2 || $$ || yes || vegetarian&lt;br /&gt;
|-&lt;br /&gt;
| [http://karmaphiladelphia.com Karma Indian Restaurant] || Indian || 114 Chestnut St || 0.2 || $$ || yes || vegetarian&lt;br /&gt;
|-&lt;br /&gt;
| [http://ploughstars.com/ The Plough &amp;amp; the Stars] || Irish Pub || 123 Chestnut Street  || 0.2 || $$ || yes || meh&lt;br /&gt;
|-&lt;br /&gt;
| [http://farmiciarestaurant.com/ FARMiCiA] || Farm to Table || 15 S. 3rd Street || 0.3|| $$-$$$ || yes || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.mybierstube.com/ Bierstube] || German Beer Hall || 206 Market Street || 0.3 || $ || yes || vegetarian&lt;br /&gt;
|-&lt;br /&gt;
| [http://forkrestaurant.com/ Fork] || New American || 306 Market Street || 0.3 || $$$ || yes || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://highstreetonmarket.com/ High Street on Market] || New American || 308 Market Street || 0.3 || $$ || yes || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.capogirogelato.com/ Capofitto Pizza and Gelato] || Neapolitan pizza || 233 Chestnut Street || 0.3 || $$ ||  || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.buddakan.com/ Buddakan] || Asian Fusion || 325 Chestnut Street || 0.3 || $$$ || yes || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://macstavern.com/ Mac's Tavern] || Gastropub/New American || 226 Market Street || 0.3 || $$ || no || vegetarian&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.thegaslightphilly.com/ The Gaslight] || New American || 120 Market Street || 0.3 || $$ || yes || vegetarian&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.nationalmechanics.com/ National Mechanics] || Traditional American || 22 S. 3rd Street || 0.4 || $$ || yes || vegetarian&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.pizzeriastella.net/ Pizzeria Stella] || Pizza/Italian || 215 Lombard Street || 0.5 || $$ || no || vegetarian&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.talulasgarden.com/ Talula's Garden] || New American || 210 W. Washington Sq. || 0.5 || $$$ || yes || vegetarian&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.cooperagephilly.com/ Cooperage] || Gastropub/New American || 123 S. 7th Street || 0.5 || $$ || yes || vegetarian&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.tamarindsouthstreet.com/new/index.php?option=com_frontpage&amp;amp;Itemid=28 Tamarind] || Thai || 117 South St. || 0.5 || $$ || yes || vegetarian&lt;br /&gt;
|-&lt;br /&gt;
| [http://hikaruphilly.com/ Hikaru] || Japanese || 607 S 2nd St  || 0.5 || $$ || yes || vegetarian&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.bridgetfoys.com/ Bridget Foy's] || Traditional American || 200 South Street || 0.6 || $$ || yes || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.famous4thstreetdelicatessen.com/index_flash.html Famous 4th Street Delicatessen] || Sandwiches/Breakfast || 700 S. 4th Street || 0.6 || $$ || no || vegetarian&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.morimotorestaurant.com/ Morimoto] || Japanese (YES Morimoto works the sushi bar some nights) || 723 Chestnut Street || 0.6 || $$$$ || yes || meh&lt;br /&gt;
|-&lt;br /&gt;
| [http://wedgeandfig.com/ Wedge + Fig] || New American/Cheese Bistro || 160 N. 3rd Street || 0.6 || $$$ ||  || &lt;br /&gt;
|-&lt;br /&gt;
| [http://www.jones-restaurant.com/ Jones] || American comfort food (Stephen Starr) || 700 Chestnut St. || 0.6 || $$ || yes || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.blackbirdpizzeria.com/ Blackbird] || Pizza/Vegan || 507 S. 6th Street || 0.7 || $ || no || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.serpicoonsouth.com/ Serpico] || New American || 604 South Street || 0.7 || $$$ || yes || &lt;br /&gt;
|-&lt;br /&gt;
| [http://tattooedmomphilly.com/menu Tattooed Mom] || Pub Grub  || 530 South Street || 0.7 || $ || no || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://bistrotlaminette.com/ Bistrot La Minette] || French || 623 S. 6th Street || 0.8 || $$$ || yes || vegetarian&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.brauhausschmitz.com/ Brauhaus Schmitz] || German || 718 South Street || 0.9 || $$ || yes || vegetarian&lt;br /&gt;
|-&lt;br /&gt;
| [http://catahoulaphilly.com/ Catahoula] || Cajun/Creole || 775 S. Front Street || 0.9 || $$ || no || no&lt;br /&gt;
|-&lt;br /&gt;
| [http://littlefishbyob.com/ Little Fish] || Seafood || 746 S. 6th Street || 0.9 || $$$ || yes || no&lt;br /&gt;
|-&lt;br /&gt;
| [http://strangelovesbeerbar.com/ Strangelove's] || New American / Craft Beer || 216 S. 11th Street || 0.8 || $$ || yes || veg*n friendly &lt;br /&gt;
|-&lt;br /&gt;
| [http://www.readingterminalmarket.org/ Reading Terminal Market] || Market/Grocery || 12th and Arch Street || 0.9 || $$ ||  || &lt;br /&gt;
|-&lt;br /&gt;
| [http://strangelovesbeerbar.com/ Strangelove's] || Gastropub || 216 S. 11th St || 0.9 - 1 || $$ || yes || yes (veg*ns &amp;amp; carnivores welcome)&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.triacafe.com/ Tria Cafe] || Wine &amp;amp; Cheese || 1137 Spruce St. || 1.0 || $$-$$$ || no || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fooderybeer.com/ The Foodery] || Bottleshop/Sandwiches || 10th and Pine Streets || 1 || $-$$$ ||  || &lt;br /&gt;
|-&lt;br /&gt;
| [http://www.capogirogelato.com/ Capogiro Gelato] || Gelato || 119 S. 13th Street || 1 || $$ ||  || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.percystreet.com/ Percy Street Barbecue] || Barbecue || 900 South Street || 1 || $$ || yes || no&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.742vegantree.com/ Vegan Tree] || Vegan || 742 South St. || 1 || $ || no || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.blindpigphilly.com/The_Blind_Pig_Philadelphia-_Northern_Liberties_Restaurant_and_Bar_-_Home.html Blind Pig] || Pub food || 702 N 2nd Street || 1.1 || $$ || no || meh&lt;br /&gt;
|-&lt;br /&gt;
| [http://charliewasasinner.com/ Charlie was a sinner] || Vegan bar || 131 S. 13th St. || 1.1 || $$ || yes || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.silkcityphilly.com/ Silk City Diner] || New American || 435 Spring Garden St || 1.2 || $$ || no || meh&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.suxinghouse.com/index.html Su Xing House] || Chinese || 1509 Sansom Street || 1.3 || $ ||  || vegetarian&lt;br /&gt;
|-&lt;br /&gt;
| [http://news.standardtap.com.s86406.gridserver.com/ The Standard Tap] || Pub Grub  || 901 North 2nd Street || 1.3 || $$ || no || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fooderybeer.com/ The Foodery] || Bottleshop/Sandwiches || 2nd and Poplar Streets || 1.3 || $-$$$ ||  || &lt;br /&gt;
|-&lt;br /&gt;
| [http://www.coeurphilly.com/ Coeur] || Gastropub || 8th St. at Christian St. || 1.3 || $$-$$$ || yes || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://kennettrestaurant.multiscreensite.com/ Kennett] || Gastropub/New American || 848 S. 2nd Street || 1.4 || $$ || yes || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://honeyssitneat.com/ Honey's Sit 'n Eat] || Diner/Homestyle || 800 N. 4th St. || 1.4 || $ || no - CASH ONLY || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.jasminericebyob.com/ Jasmine Rice] || Thai || 306 S. 16th St. || 1.5 || $$ || yes || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.triacafe.com/ Tria Cafe] || Wine &amp;amp; Cheese || 123 S. 18th St. || 1.5 || $$-$$$ || no || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.monkscafe.com/ Monk's Cafe] || Belgian || 264 S 16th St || 1.8 || $$ || no || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://philadelphia.villagewhiskey.com Village Whiskey] || Whiskey pub (Jose Garces) || 118 S 20th St || 2 || $$ || no || vegetarian&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.mamasvegetarian.com/ Mama's Vegetarian] || Kosher || 18 S 20TH STREET || 2.1 || $ || no- cash only || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.thebelgiancafe.com/ The Belgian Cafe] || Belgian/Pub (Great beer list) || 601 North 21st Street || 3.3 || $$ || no || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://garcesgroup.com/restaurants#pennsylvania Jose Garces Restaurants] || various || various || $$-$$$$ || yes || yes&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.starr-restaurant.com/ Stephen Starr Restaurants] || various || various || various || $$-$$$$ || yes || yes&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Donuts ===&lt;br /&gt;
&lt;br /&gt;
[http://www.federaldonuts.com/ Federal Donuts]&lt;br /&gt;
&lt;br /&gt;
=== Desserts ===&lt;br /&gt;
&lt;br /&gt;
* [http://www.franklinfountain.com/ Franklin Fountain] - Old City&lt;br /&gt;
* [http://shanecandies.com/blog/ Shane Confectionery] - Old City&lt;br /&gt;
* [http://www.capogirogelato.com/ Capogiro Gelato] - Center City; South Philly; West Philly&lt;br /&gt;
* [http://bassettsicecream.com/ Bassett's Ice Cream] - in Reading Terminal Market&lt;br /&gt;
* [http://www.flyingmonkeyphilly.com/ Flying Monkey] - in Reading Terminal Market&lt;br /&gt;
* [http://maxbrenner.com/ Max Brenner Chocolate Bar] - Rittenhouse&lt;br /&gt;
* [http://www.bestcannoli.com/ Isgro Pasticceria] - South Philly -- CANNOLI&lt;br /&gt;
* [http://www.iluvmagpie.com/ Magpie Artisan Pie Bakery &amp;amp; Boutique] - South Philly&lt;br /&gt;
* [http://johnswaterice.com/ John's Water Ice] - South Philly -- pronounced &amp;quot;wooder ice&amp;quot;&lt;br /&gt;
* [http://www.termini.com/ Termini Brothers] - Italian Market -- CANNOLI&lt;br /&gt;
* [http://www.varallobrothersbakery.com/store/ Varallo Bros. Bakery] - Italian Market -- CANNOLI&lt;br /&gt;
* [http://brownbettydesserts.com/ Brown Betty Dessert Boutique] - NoLibs (Northern Liberties)&lt;br /&gt;
* [http://www.lilpopshop.com/ Lil' Pop Shop] -- West Philly&lt;br /&gt;
* [http://www.littlebabysicecream.com/ Little Baby's Ice Cream] -- East Kensington and West Philly&lt;br /&gt;
* [http://www.ritasice.com/ Rita's Water Ice] - various -- pronounced &amp;quot;wooder ice&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Coffee ===&lt;br /&gt;
* [http://bodhicoffeephila.com/menu-2/ Bodhi Coffee]&lt;br /&gt;
* [http://greenlinecafe.com/ Green Line Cafe]&lt;br /&gt;
* [https://www.greenstreetcoffee.com/ Greenstreet Coffee Co.]&lt;br /&gt;
* [https://oldcitycoffee.com/ Old City Coffee]&lt;br /&gt;
* [http://www.menageriecoffee.com/ Menagerie Coffee]&lt;br /&gt;
* [http://www.saxbyscoffee.com/index.html Saxby's]&lt;br /&gt;
* [http://www.hubbubcoffee.com/ HubBub Coffee]&lt;br /&gt;
* [http://www.elixrcoffee.com/ Elixr]&lt;br /&gt;
* [http://www.rivalbros.com/ Rival Bros.]&lt;br /&gt;
* [http://cakeandthebeanstalk.com/ Cake and the Beanstalk]&lt;br /&gt;
* [http://www.shottowercoffee.com/ Shot Tower Coffee]&lt;br /&gt;
&lt;br /&gt;
== Local Drinks ==&lt;br /&gt;
&lt;br /&gt;
=== Bars ===&lt;br /&gt;
&lt;br /&gt;
Everywhere.&lt;br /&gt;
&lt;br /&gt;
=== Breweries ===&lt;br /&gt;
&lt;br /&gt;
* [http://yardsbrewing.com/ Yards] -- NoLibs (Northern Liberties)&lt;br /&gt;
* [http://philadelphiabrewing.com/ Philadelphia Brewing] -- Fishtown&lt;br /&gt;
* [https://www.manayunkbrewery.com/ Manayunk Brewery] -- Manayunk (of course)&lt;br /&gt;
* [http://www.2ndstorybrewing.com/ 2nd Story] -- Center City East (Old City/Society Hill)&lt;br /&gt;
* [http://stbenjaminbrewing.com/ Saint Benjamin] -- North Philly&lt;br /&gt;
* [http://www.dockstreetbeer.com/ Dock Street] -- West Philly; also has great pizza! Take the 34 Trolley (&amp;quot;Green Line&amp;quot;) out to Baltimore and 50th St.&lt;br /&gt;
* [http://crimeandpunishmentbrewingco.com/ Crime &amp;amp; Punishment] -- Brewerytown&lt;br /&gt;
* [http://earthbreadbrewery.com/ Earth Bread + Brewery] -- Mt. Airy&lt;br /&gt;
* [http://www.ironhillbrewery.com/chestnuthill/ Iron Hill Brewery] -- Chestnut Hill/Germantown&lt;br /&gt;
* [http://www.victorybeer.com/ Victory] -- Downingtown&lt;br /&gt;
* '''''Honorable mention''''': [http://www.tiredhands.com/cafe/ Tired Hands] -- Ardmore; a little bit of a hike but well worth it!&lt;br /&gt;
* '''''Regional''''': [http://www.slyfoxbeer.com/ Sly Fox]&lt;br /&gt;
* '''''Regional BUT America's Oldest Brewery!''''' [http://www.yuengling.com/ Yuengling]&lt;br /&gt;
* [http://www.ripsneakers.com/nodding/ Nodding Head Brewing] -- status unknown&lt;br /&gt;
&lt;br /&gt;
=== Bottle Shops and Taprooms ===&lt;br /&gt;
&lt;br /&gt;
* [http://www.fooderybeer.com/ The Foodery] || 10th and Pine Streets || 1 mile&lt;br /&gt;
* [https://www.facebook.com/BeerHeavenPhiladelphia/ Beer Heaven] || 1100 S. Columbus Blvd. || 1.1 miles&lt;br /&gt;
* [http://fooderyrittenhouse.com/ The Foodery Rittenhouse] || 1710 Sansom St. || 1.4 miles&lt;br /&gt;
* [http://www.hawthornecafe.com/about/ Hawthorne] || 738 S. 11th St. || 1.3 miles&lt;br /&gt;
* [http://bottleshopbeer.com/ Bottle Shop] || 1616 East Passyunk || 1.8 miles&lt;br /&gt;
* [http://mondemarket.blogspot.com/ Monde Market] || 100 S. 21st St. || 1.8 miles&lt;br /&gt;
* [http://bottlebareast.com/ Bottle Bar East] || 1308 Frankford Ave. || 2 miles&lt;br /&gt;
* [http://brewphiladelphia.com/ Brew, a beer boutique] || 1900 S. 15th St. || 2.3 miles -- shares space with [http://www.ultimocoffee.com/ Ultimo Coffee]&lt;br /&gt;
* [http://local44beerbar.com/bottleshop.htm Local 44 Bottle Shop] || 44th and Spruce Sts., West Philly || 3.6 miles -- SEPTA 42 bus stops right in front!&lt;br /&gt;
&lt;br /&gt;
== Philadelphia Events ==&lt;br /&gt;
&lt;br /&gt;
=== Saturday and Sunday, March 5 &amp;amp; 6 ===&lt;br /&gt;
&lt;br /&gt;
Sunday &lt;br /&gt;
[http://www.barnesfoundation.org/visit/philadelphia/free-first-sundays First Free Sunday at the Barnes Foundation!]&lt;br /&gt;
&lt;br /&gt;
[http://www.songkick.com/concerts/25150589-leon-bridges-at-fillmore-philadelphia Leon Bringes and Son Little] - Killer night of R&amp;amp;B/ Soul including Philly's own [http://sonlittlemusic.net/#sonlittle Son Little]&lt;br /&gt;
&lt;br /&gt;
[http://www.songkick.com/concerts/25331894-blanck-mass-at-johnny-brendas Blanck Mass at Johnny Brendas] - Electronic /Drone show at a great Philadelphia venue&lt;br /&gt;
&lt;br /&gt;
=== Monday, March 7 ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Tuesday, March 8 ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[https://www.fi.edu/event/2016-03-08/science-after-hours Party Like a Rock Star at the Science Museum Started by Ben Franklin] - 7:00pm to 10:00pm&lt;br /&gt;
&lt;br /&gt;
Tune those axes and crank up the volume as Science After Hours travels into a world of lost inhibitions—we’ll take you from Woodstock to Punk Rock celebrating all things rock and roll!&lt;br /&gt;
Learn how instruments are designed to produce different sounds and the science of how those sounds reach your brain. Rock out to the science of pyrotechnics, ... an evening better than a trip to Bonnaroo (or, at least, more scientific). $15  (Purchase Tickets in advance)&lt;br /&gt;
&lt;br /&gt;
[http://www.12stepsdown.com/ SUPER! Karaoke starting @9pm w/ @singyourlifekaraoke] @ 12 Steps Down - 9pm+&lt;br /&gt;
&lt;br /&gt;
A bar + mic + liberal amounts of bathroom graffiti = Tuesdays at 12 Steps Down. Gritty and by all accounts glorious though be warned: A smoking venue.&lt;br /&gt;
&lt;br /&gt;
=== Wednesday, March 9 ===&lt;br /&gt;
&lt;br /&gt;
[http://www.songkick.com/concerts/25664299-french-horn-rebellion-at-milkboy-philly French Horn Rebellion, Mystery Skulls] - No French Horns were harmed in the making of these beats&lt;br /&gt;
&lt;br /&gt;
[http://www.hive76.org/ South Philadelphia Hackerspace Open House 7-9 PM ]  If interested, add name to list  [https://oasis.sandstorm.io/shared/Lo-9k04s0C5En4qBtLKIGVFIbESEkilaD0_yBH5V_c8 Open house @ Hive 76 Ride Share list]&lt;br /&gt;
&lt;br /&gt;
[http://meyerweb.com/eric/thoughts/2016/02/29/design-for-real-life/ &amp;quot;Design for Real Life&amp;quot; Book Release Party]  - 6:00PM - 8:00PM, Frankford Hall, 1210 Frankford Ave., Philadelphia&lt;br /&gt;
&lt;br /&gt;
Sara [Wachter-Boettcher] and [Eric Meyer] will be hosting, with incredibly generous support from A Book Apart and [http://phillychi.acm.org/ PhillyCHI], [https://www.eventbrite.com/e/design-for-real-life-book-release-party-sponsored-by-a-book-apart-tickets-22295452298 a launch party at Frankford Hall] in Philadelphia.&amp;amp;nbsp; We’ll be providing some munchies, some tasty adult beverages, and there will be giveaways of both paper and digital copies of the [https://abookapart.com/products/design-for-real-life book].&amp;amp;nbsp; We’d love to see you there!&amp;amp;nbsp; If you can make it, please do RSVP at that link, so we know how much food to order.&lt;br /&gt;
&lt;br /&gt;
=== Thursday, March 10 ===&lt;br /&gt;
&lt;br /&gt;
[https://www.fi.edu/event/2016-03-09/night-skies-observatory  Sisters of the Stars: Women of Astronomy and Space Science ] 6:00pm to 9:00pm&lt;br /&gt;
&lt;br /&gt;
Though not always in the limelight, throughout history women have shined as groundbreaking scientists and intrepid team members pursuing amazing discoveries and the daring exploration of space. Join us as we highlight the women behind some of the most extraordinary adventures in the universe. $5 &lt;br /&gt;
&lt;br /&gt;
[http://phillydevnight.com Philly Dev Night] - 7pm every Thursday, Philly Dev Night opens the [http://phillygameforge.com/ Philly Game Forge] (right down the street, 239 Chestnut St.) to anyone who wants to make, play, write, draw, or smell games. &amp;quot;It doesn't matter if you're an aspiring game developer, artist, writer, or even just a gamer; Dev Night will have something to offer. We talk games, play games, make games, compete, collaborate, and share. Dev Night is a creative time for creative people in a creative space.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== All days ===&lt;br /&gt;
[http://www.visitphilly.com/events/philadelphia/philadelphia-international-flower-show/ The 2016 Philadelphia Flower Show], March 5 - 13, Pennsylvania Convention Center&lt;br /&gt;
&lt;br /&gt;
[http://www.visitphilly.com/events/philadelphia/picasso-the-great-war-experimentation-and-change-at-the-barnes/ Picasso: The Great War, Experimentation and Change], Barnes Foundation - this museum uses timed tickets; strongly advised to book in advance&lt;br /&gt;
&lt;br /&gt;
[http://www.visitphilly.com/museums-attractions/philadelphia/the-golden-age-of-king-midas-at-the-penn-museum/ The Golden Age of King Midas], Penn Museum&lt;br /&gt;
&lt;br /&gt;
[http://www.visitphilly.com/events/philadelphia/international-pop-at-the-philadelphia-museum-of-art/ International Pop], Philadelphia Museum of Art&lt;br /&gt;
&lt;br /&gt;
[http://www.visitphilly.com/events/philadelphia/headed-to-the-white-house-at-the-national-constitution-center/ Headed to the White House], National Constitution Center&lt;br /&gt;
&lt;br /&gt;
[http://www.visitphilly.com/events/philadelphia/drapetomania-at-the-african-american-museum-in-philadelphia/ Drapetomania], African American Museum&lt;br /&gt;
&lt;br /&gt;
[http://www.visitphilly.com/events/philadelphia/down-the-rabbit-hole-celebrating-alice-in-wonderland-at-the-rosenbach/ Down the Rabbit Hole: Celebrating 150 Years of Alice in Wonderland], The Rosenbach&lt;br /&gt;
&lt;br /&gt;
==Getting Around==&lt;br /&gt;
All info on getting to the hotel is on the conference website: http://2016.code4lib.org/venue.html&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2016]]&lt;/div&gt;</summary>
		<author><name>ChristopherHallberg</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&amp;diff=42113</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=42113"/>
				<updated>2014-11-20T17:00:02Z</updated>
		
		<summary type="html">&lt;p&gt;ChristopherHallberg: /* Linked Data Workshop */&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;
== Pre-conference Proposals ==&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;
#&lt;br /&gt;
#&lt;br /&gt;
#&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;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
===RailsBridge: Intro to programming in Ruby on Rails===&lt;br /&gt;
&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
&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;
''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;
# Mike Price&lt;br /&gt;
# Jean Rainwater&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Margaret Heller&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Replace yourself with a painfully complex bash script...or try Ansible ===&lt;br /&gt;
&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;
# Ray Schwartz&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Kevin S. Clarke&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Andy Mardesich&lt;br /&gt;
# Anna Headley&lt;br /&gt;
# Chelsea Lobdell&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Intro to Docker ===&lt;br /&gt;
&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, University of Maryland Libraries , 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;
#  Jim Hahn&lt;br /&gt;
#  Joshua Gomez&lt;br /&gt;
#  Bobbi Fox&lt;br /&gt;
#  Ray Schwartz&lt;br /&gt;
#  Megan Kudzia&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Cary Gordon (uses Docker in production on AWS)&lt;br /&gt;
# Eric Phetteplace&lt;br /&gt;
# Esther Verreau&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Anna Headley (voting for afternoon, compliments ansible)&lt;br /&gt;
&lt;br /&gt;
=== Code Retreat ===&lt;br /&gt;
&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;
# Mike Giarlo&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Devon Smith&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&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;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Dive into Hydra  ===&lt;br /&gt;
 &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;
# Mike Price&lt;br /&gt;
# Jean Rainwater&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== code4lib/Write The Docs barcamp ===&lt;br /&gt;
&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;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
'''Morning'''&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
# Mita Williams&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
'''Afternoon'''&lt;br /&gt;
# Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon. &lt;br /&gt;
# Kevin S. Clarke&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Linked Data Workshop ===&lt;br /&gt;
&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;
''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;
# Logan Cox&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Chris Hallberg&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Code4Arc ===&lt;br /&gt;
&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;
''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;
# Laney McGlohon - developer&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Fail4Lib 2015 ===&lt;br /&gt;
&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;
# Ray Schwartz&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&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;
'''&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;
''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;
#  Megan Kudzia&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&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;
# Ray Schwartz&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&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;
''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;
# Ray Schwartz&lt;br /&gt;
# Andy Mardesich&lt;br /&gt;
# Chelsea Lobdell&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&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;
# Jeannie Graham&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&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;
# Bobbi Fox&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
# Eric Phetteplace&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Andy Mardesich&lt;br /&gt;
# Tao Zhao&lt;br /&gt;
# Chris Hallberg&lt;br /&gt;
&lt;br /&gt;
=== CollectionSpace: Getting it up and running at your museum ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org&lt;br /&gt;
* TBD&lt;br /&gt;
&lt;br /&gt;
This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org&lt;br /&gt;
&lt;br /&gt;
Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&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;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== DPLA API Workshop: ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Afternoon]''' &lt;br /&gt;
&lt;br /&gt;
* Audrey Altman, DPLA&lt;br /&gt;
* Mark Breedlove, DPLA&lt;br /&gt;
* Mark Matienzo, DPLA&lt;br /&gt;
* Tom Johnson, DPLA&lt;br /&gt;
&lt;br /&gt;
The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.&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;
# Ranti Junus&lt;br /&gt;
# Jean Rainwater&lt;br /&gt;
# Mita Williams&lt;br /&gt;
# Margaret Heller&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]]&lt;/div&gt;</summary>
		<author><name>ChristopherHallberg</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&amp;diff=42112</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=42112"/>
				<updated>2014-11-20T16:58:14Z</updated>
		
		<summary type="html">&lt;p&gt;ChristopherHallberg: /* 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;
== Pre-conference Proposals ==&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;
#&lt;br /&gt;
#&lt;br /&gt;
#&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;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
===RailsBridge: Intro to programming in Ruby on Rails===&lt;br /&gt;
&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
&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;
''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;
# Mike Price&lt;br /&gt;
# Jean Rainwater&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Margaret Heller&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Replace yourself with a painfully complex bash script...or try Ansible ===&lt;br /&gt;
&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;
# Ray Schwartz&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Kevin S. Clarke&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Andy Mardesich&lt;br /&gt;
# Anna Headley&lt;br /&gt;
# Chelsea Lobdell&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Intro to Docker ===&lt;br /&gt;
&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, University of Maryland Libraries , 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;
#  Jim Hahn&lt;br /&gt;
#  Joshua Gomez&lt;br /&gt;
#  Bobbi Fox&lt;br /&gt;
#  Ray Schwartz&lt;br /&gt;
#  Megan Kudzia&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Cary Gordon (uses Docker in production on AWS)&lt;br /&gt;
# Eric Phetteplace&lt;br /&gt;
# Esther Verreau&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Anna Headley (voting for afternoon, compliments ansible)&lt;br /&gt;
&lt;br /&gt;
=== Code Retreat ===&lt;br /&gt;
&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;
# Mike Giarlo&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Devon Smith&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&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;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Dive into Hydra  ===&lt;br /&gt;
 &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;
# Mike Price&lt;br /&gt;
# Jean Rainwater&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== code4lib/Write The Docs barcamp ===&lt;br /&gt;
&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;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
'''Morning'''&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
# Mita Williams&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
'''Afternoon'''&lt;br /&gt;
# Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon. &lt;br /&gt;
# Kevin S. Clarke&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Linked Data Workshop ===&lt;br /&gt;
&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;
''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;
# Logan Cox&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Code4Arc ===&lt;br /&gt;
&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;
''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;
# Laney McGlohon - developer&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Fail4Lib 2015 ===&lt;br /&gt;
&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;
# Ray Schwartz&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&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;
'''&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;
''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;
#  Megan Kudzia&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&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;
# Ray Schwartz&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&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;
''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;
# Ray Schwartz&lt;br /&gt;
# Andy Mardesich&lt;br /&gt;
# Chelsea Lobdell&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&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;
# Jeannie Graham&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&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;
# Bobbi Fox&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
# Eric Phetteplace&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Andy Mardesich&lt;br /&gt;
# Tao Zhao&lt;br /&gt;
# Chris Hallberg&lt;br /&gt;
&lt;br /&gt;
=== CollectionSpace: Getting it up and running at your museum ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org&lt;br /&gt;
* TBD&lt;br /&gt;
&lt;br /&gt;
This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org&lt;br /&gt;
&lt;br /&gt;
Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&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;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== DPLA API Workshop: ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Afternoon]''' &lt;br /&gt;
&lt;br /&gt;
* Audrey Altman, DPLA&lt;br /&gt;
* Mark Breedlove, DPLA&lt;br /&gt;
* Mark Matienzo, DPLA&lt;br /&gt;
* Tom Johnson, DPLA&lt;br /&gt;
&lt;br /&gt;
The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.&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;
# Ranti Junus&lt;br /&gt;
# Jean Rainwater&lt;br /&gt;
# Mita Williams&lt;br /&gt;
# Margaret Heller&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]]&lt;/div&gt;</summary>
		<author><name>ChristopherHallberg</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_Breakout_I_(Tuesday)&amp;diff=41047</id>
		<title>2014 Breakout I (Tuesday)</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_Breakout_I_(Tuesday)&amp;diff=41047"/>
				<updated>2014-03-31T13:35:58Z</updated>
		
		<summary type="html">&lt;p&gt;ChristopherHallberg: /* VuFind Update */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Islandora==&lt;br /&gt;
&lt;br /&gt;
Institutions that are live w/Examples&lt;br /&gt;
*Colorado Alliance of Research Libraries [https://www.coalliance.org/software/digital-repository/members]&lt;br /&gt;
**Hosts Islandora 6 repositories on Drupal 6; migrating to Drupal 7&lt;br /&gt;
*Florida State University ([http://fsu.digital.flvc.org])&lt;br /&gt;
*Grinnell [http://digital.grinnell.edu/drupal/]&lt;br /&gt;
&lt;br /&gt;
Question about new installation:  additional resources aside from documentation&lt;br /&gt;
Additional resources:&lt;br /&gt;
*Islandora Google Group [https://groups.google.com/forum/#!forum/islandora]&lt;br /&gt;
* series of cookbooks with Chef for one-click installation of Islandora [https://github.com/LibraryChef/islandora]&lt;br /&gt;
** Could use Vagrant and virtual box&lt;br /&gt;
* New release of Islandora expected soon &lt;br /&gt;
* Lyrasis is asked to review the documentation and will do sanity checks on the documentation&lt;br /&gt;
* Should see improvements to documentation soon&lt;br /&gt;
&lt;br /&gt;
Hosted solutions available to purchase:&lt;br /&gt;
* Lyrasis [https://www.lyrasis.org/LYRASIS%20Digital/Pages/Repository.aspx]&lt;br /&gt;
* DiscoveryGarden [http://discoverygarden.ca/solutions_ir.php]&lt;br /&gt;
* Cherry Hill Co. (coming soon) [http://chillco.com]&lt;br /&gt;
&lt;br /&gt;
What's the learning curve with Drupal - easier/harder than Hydra?&lt;br /&gt;
* Drupal 7 is easier to learn than Drupal 6&lt;br /&gt;
* Recommend the Using Drupal / O'Reilly Book [http://www.worldcat.org/title/using-drupal/oclc/233931612]&lt;br /&gt;
** Useful to understand theming / design&lt;br /&gt;
* Drupal may be more widely-held skill set than Ruby on Rails (in which Hydra is based)&lt;br /&gt;
* Though at least one school's Islandora developer started with Islandora without a PHP/Drupal background&lt;br /&gt;
* DrupalCon - first week in June, Austin TX in 2014&lt;br /&gt;
* Islandora Camp ([http://islandora.ca/camps])&lt;br /&gt;
&lt;br /&gt;
Setup difficulty?&lt;br /&gt;
* Documentation for setting up Solr / Gsearch - some confusion between v. 6 &amp;amp; 7 documentation&lt;br /&gt;
* Would be better for things to be more grouped together&lt;br /&gt;
&lt;br /&gt;
Using Islandora for Media Streaming&lt;br /&gt;
*Video streaming:  streams in HTML5 / used to use Flash in Islandora 6&lt;br /&gt;
*Every video gets an Mp4; audio files use Mp3&lt;br /&gt;
*How are storing the original videos?  In Fedora.  Note: objects do not have to be stored in Fedora&lt;br /&gt;
*Can still think of Fedora as the repository - include all master files and metadata.  if need to migrate out of Fedora in the future, could simply retain master files and metdata.&lt;br /&gt;
*Media Streaming installed on Drupal server&lt;br /&gt;
**FlowPlayer; jwplayer available for Islandora 7&lt;br /&gt;
*Grinnel contracted with Discovery Garden to create generic content solution pack that allowed the creation of an object that held multiple types of files (pdf images, audio, video).  Traded the ability to stream for the ability to create a compound object.  Now need to do additional work to standardize for Islandora 7.&lt;br /&gt;
*Binary object created by Discovery Garden - for download.&lt;br /&gt;
*Islandora has several solution packs for multiple file types (video, audio, compound, large images, small images).  Colorado use case involved oral history (video, audio, text documents together) which should be possible to use with the compound solution packs.&lt;br /&gt;
&lt;br /&gt;
Versioning problems encountered:&lt;br /&gt;
*For each object - new folder is created?  Can turn off versioning based upon file type; do version the metadata, but not the actual master files themselves.&lt;br /&gt;
*Could also use Fedora as a registry - not store the objects themselves because of versioning and performance/scaling issues.  &lt;br /&gt;
&lt;br /&gt;
How to handle updates to metadata?  &lt;br /&gt;
*Checkbox to version or not.&lt;br /&gt;
*METS-like XML schema as a container (FOXML).  When version -it adds it in to FOXML; Islandora only displays the most recent version&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note about custom modules:&lt;br /&gt;
*Custom modules can be difficult to get community support.  out-of-house development makes it difficult to join back with the larger community and core code.&lt;br /&gt;
&lt;br /&gt;
Long-term preservation:&lt;br /&gt;
*MetaArchive - locked server, dark archive.  May be module available for checksum generator and checksum checker - runs checksum on ingest and periodically check them.&lt;br /&gt;
*DuraCloud - application on top of Amazon storage run by DuraSpace&lt;br /&gt;
*Premise - preservation metadata system that helps record whenever records are touched or changed for audit trail.&lt;br /&gt;
&lt;br /&gt;
What happened to Hylandora?&lt;br /&gt;
* Came down to the content model: Islandora and Hydra were too divergent.  &lt;br /&gt;
&lt;br /&gt;
Reasons to go with Islandora over Hydra:&lt;br /&gt;
* Just depends on the skill set available&lt;br /&gt;
* Both Hydra and Islandora have active communities&lt;br /&gt;
&lt;br /&gt;
Issues:&lt;br /&gt;
* Upgrades can be painful / difficult in both Hydra and Islandora&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
What kinds of content is appropriate for Islandora?&lt;br /&gt;
* Good for special collections and ETDs, images from Athletic departments and ContentDM&lt;br /&gt;
* Crossover with Content Management systems, emphasize a policy on what should be included for long-term preservation&lt;br /&gt;
* Grinnell - small liberal arts college; emphasize promoting a place for faculty and students to store their research (undergraduate papers, faculty white papers/publication, data sets, digital humanities, videos of performances, audio of music performances, preserving websites (difficult with Islandora 6 vs. 7, which has a WARCIVE module)&lt;br /&gt;
** Don't want to necessarily limit to a library-only thing; include instructional designers, academic affairs, art gallery, history, &lt;br /&gt;
* Florida:  modules:  large images, small image, pdf and books.  Books module - good for yearbooks.  Want to use it for ETDs and research. &lt;br /&gt;
** Workflow module - has been useful.  Similar to DSpace workflow for ETDs.  When we ingest objects and they're not ready to be published - can work with metadata, wait to publish and not be visible to the public until they are ready to publish.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Access Controls/Embargoes, Harvesting, and Statistics&lt;br /&gt;
* Access controls for data:  Fedora use XacMole (sp)? to set permissions.  can set embargoes for ETDs.  IP embargo module.  Could extend to the bitstream level.  Pretty easy to do without breaking anything.&lt;br /&gt;
* OAI:PMH module - might not like how the Dublin Core looks out of the box - can use MODS out of the box to do the MODS to DC transform.  Needs additional work to pass the 2.0 specification.  Module that includes a REST API that will return data on various levels if requesting just specific items.  &lt;br /&gt;
* How to handle statistics?  e.g., what are the counts for objects per creation date.  &lt;br /&gt;
** Perl script that will lookup the size of the collection, how many objects - on Github&lt;br /&gt;
** Google Analytics module in 7&lt;br /&gt;
&lt;br /&gt;
==Relevance Search &amp;amp; Ranking==&lt;br /&gt;
&lt;br /&gt;
==Metadata Harvesting Normalization &amp;amp; Enrichement @ Scale==&lt;br /&gt;
&lt;br /&gt;
* Seeing same tools that were brought forth and then not hearing anything else about them.&lt;br /&gt;
* Conversations with folk about normalizing and enriching metadata.&lt;br /&gt;
* Lets hear about tools and things they are working on.&lt;br /&gt;
* Particular processes.&lt;br /&gt;
&lt;br /&gt;
==VuFind Update==&lt;br /&gt;
&lt;br /&gt;
==Telecommunicating Support Group==&lt;br /&gt;
&lt;br /&gt;
@mjgiarlo&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==BIBFRAME==&lt;br /&gt;
Notes are based off the Tweets made by the group during the discussion:&lt;br /&gt;
&lt;br /&gt;
'''Questions''' &lt;br /&gt;
*What will workflows will look like after Linked Data and BIBFRAME are actually pushed out?&lt;br /&gt;
*How to best use controlled vocabularies, including various/local controlled vocabularies, in linked data work?&lt;br /&gt;
*Will the protectiveness of quality by catalogers become thing of past? &lt;br /&gt;
&lt;br /&gt;
'''Pros'''&lt;br /&gt;
*Good thing about RDF, semantic metadata structure is that is creates a good skeleton that can last through system changes.&lt;br /&gt;
*Talked about OpenRefine, Freebase, Linked Data/Semantic Web examples &lt;br /&gt;
*Shout out for the Open Metadata Registry - http://metadataregistry.org/&lt;br /&gt;
*RDFa allows multiple property values inline- more details than http://schema.org , starts to approach MARC richness&lt;br /&gt;
&lt;br /&gt;
'''Concerns'''&lt;br /&gt;
*Wariness of simplicity (particularly of Dublin Core) due to the possibility of overloading elements, thus blocking interoperability with other schemas.&lt;br /&gt;
*There is the possible issue of every library creating their own ontologies, thus reinventing the wheel.&lt;br /&gt;
*Discussion of how long-term cataloging employees will handle this linked data 'revolution', how to best oversee these changes with catalogers dragging their feet.&lt;br /&gt;
&lt;br /&gt;
==Archivespace==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==User Experience==&lt;br /&gt;
&lt;br /&gt;
''Blame @erinrwhite for cruddy notes.''&lt;br /&gt;
&lt;br /&gt;
Coral facilitates. Her question for the group is, how can we overcome the focus on library experience and focus instead on user experience?&lt;br /&gt;
&lt;br /&gt;
=== what's your problem?===&lt;br /&gt;
&lt;br /&gt;
Introductions. Common problems:&lt;br /&gt;
&lt;br /&gt;
* &amp;quot;Just make a web page!&amp;quot;&lt;br /&gt;
* &amp;quot;I can figure this weird arcane and overly complicated thing out. Why can't anyone else?&amp;quot;&lt;br /&gt;
* Convincing stakeholders that design isn't print design, doesn't need to be the same for everyone and isn't static.&lt;br /&gt;
* Redesign by committee, have mercy!&lt;br /&gt;
* Getting ready for a redesign&lt;br /&gt;
* Publishing/learning about UX research. Who's going through IRB, who's publishing this stuff?&lt;br /&gt;
* Devaluation of UX work in library, funding or mandate&lt;br /&gt;
* UX not being built into organizational policies etc.&lt;br /&gt;
* How can we scale up UX above and beyond one-project research? Expanding to include more projects beyond the website?&lt;br /&gt;
* How can we convince our organizations to not recreate the org chart with the website?&lt;br /&gt;
* Trying to create a UX position that is beyond web librarian&lt;br /&gt;
* Not just testing sites with librarians (!)&lt;br /&gt;
* What about user experience for back-of-house software?&lt;br /&gt;
* I'm a web team of one. Help?&lt;br /&gt;
* &amp;quot;Put the MARC view back in the catalog!&amp;quot;&lt;br /&gt;
* Do we really need to default to advanced search? Battling the exceptions vs the average user?&lt;br /&gt;
* Taking a guerrilla approach to UX research&lt;br /&gt;
* Not a lot of staff in digital area&lt;br /&gt;
* Moving from a culture of complaint to a culture of...fixing&lt;br /&gt;
&lt;br /&gt;
A couple folks here working in organizations that have UX and assessment built into the culture. Thanks in advance for your knowledge, y'all!&lt;br /&gt;
&lt;br /&gt;
=== themes===&lt;br /&gt;
&lt;br /&gt;
We broke into sub-groups:&lt;br /&gt;
&lt;br /&gt;
* Making time&lt;br /&gt;
* Changing culture&lt;br /&gt;
* Beyond the website&lt;br /&gt;
&lt;br /&gt;
==Worldcat Search API==&lt;br /&gt;
&lt;br /&gt;
Help beta test early release of the new WorldCat Search API&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Spotlight: Exhibits, Curated Collections and Blacklight==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Tools for Instruction==&lt;br /&gt;
&lt;br /&gt;
LMS Integration, Guide on the side, LibGuides, etc.&lt;br /&gt;
&lt;br /&gt;
Participants:&lt;br /&gt;
* Mike Hagedon; interests: [http://code.library.arizona.edu/gots Guide on the Side], LTI, LMS integration, subject/course guides&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Code4lib Conference Documentation==&lt;br /&gt;
&lt;br /&gt;
We discussed the ways in which the lack of historical data make proposing to host the conference difficult.  Code4libbers must convince their employer to take on financial responsibility. This does not mean the host pays. In fact, each conference has had a surplus. But a corporate institution is needed to sign the contracts with the venues and services used by the conference.  Employers need convincing that the event will not be a huge cost nor a burden on the business office. To convince the administrators, a historical record of past conferences would be immensely helpful.&lt;br /&gt;
&lt;br /&gt;
We discussed several data points that would be useful. Some of these include&lt;br /&gt;
* expected and final budgets&lt;br /&gt;
* total attendance&lt;br /&gt;
* hotel room reservation block size and % of expected size actually used&lt;br /&gt;
* food costs, food expectations and % of food actually consumed&lt;br /&gt;
* etc.&lt;br /&gt;
&lt;br /&gt;
We plan to begin storing these kinds of data on the code4lib wiki for future planners to use.&lt;br /&gt;
&lt;br /&gt;
Some other documentation that we also plan to add to the wiki:&lt;br /&gt;
* Conference Planning Committee Post-mortem (Raleigh group already started this trend with the &amp;quot;Lessons Learned&amp;quot; post)&lt;br /&gt;
* explanation of what it's like to work with a 3rd party event planner (Concentra), such as:&lt;br /&gt;
** how money flows between attendees, sponsors, host, awardees, and concentra&lt;br /&gt;
** what are the benefits of working with a 3rd party planner?&lt;br /&gt;
* examples of MOUs between multiple host institutions&lt;br /&gt;
&lt;br /&gt;
Some action items:&lt;br /&gt;
* finish documenting this year's conference (Tim et al.)&lt;br /&gt;
* attempt to collect historical budgets if they still exist (Josh &amp;amp; Rosy)&lt;br /&gt;
* organize existing data on the wiki (?)&lt;br /&gt;
&lt;br /&gt;
==VuFind Update==&lt;br /&gt;
Sorry for the delay&lt;br /&gt;
&lt;br /&gt;
We had a lovely gathering of VuFind veterans with a few new comers stopping by to hear what VuFind is all about. New comer and VuFind developer Chris Hallberg headed the meeting, a strong term for sitting there and listening to all the exciting news from our awesome collaborators.&lt;br /&gt;
&lt;br /&gt;
We started with some spoilers from [http://code4lib.org/conference/2014/bauder Julia Bauder's Visualization Talk], a feature of VuFind in active development. Then we went over the short-term plans for VuFind, looking at our GitHub's pull requests, heard an update from Tom on data normalization. &lt;br /&gt;
&lt;br /&gt;
John Sarnowski of the ResCarta Foundation came by to see how VuFind has change since he looked at it a few years ago as the front of his project. Looking forward to a possible collaboration here. Joe talked about his excitement over console tools and his frustration with licensing, hoping to see these in the VuFind core soon! We heard about the OLE timeline and wrapped with Julia talking about her success with ebsco.&lt;br /&gt;
&lt;br /&gt;
Thanks for coming by! See you all in Portland!&lt;/div&gt;</summary>
		<author><name>ChristopherHallberg</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_Breakout_I_(Tuesday)&amp;diff=41046</id>
		<title>2014 Breakout I (Tuesday)</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_Breakout_I_(Tuesday)&amp;diff=41046"/>
				<updated>2014-03-31T13:27:03Z</updated>
		
		<summary type="html">&lt;p&gt;ChristopherHallberg: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Islandora==&lt;br /&gt;
&lt;br /&gt;
Institutions that are live w/Examples&lt;br /&gt;
*Colorado Alliance of Research Libraries [https://www.coalliance.org/software/digital-repository/members]&lt;br /&gt;
**Hosts Islandora 6 repositories on Drupal 6; migrating to Drupal 7&lt;br /&gt;
*Florida State University ([http://fsu.digital.flvc.org])&lt;br /&gt;
*Grinnell [http://digital.grinnell.edu/drupal/]&lt;br /&gt;
&lt;br /&gt;
Question about new installation:  additional resources aside from documentation&lt;br /&gt;
Additional resources:&lt;br /&gt;
*Islandora Google Group [https://groups.google.com/forum/#!forum/islandora]&lt;br /&gt;
* series of cookbooks with Chef for one-click installation of Islandora [https://github.com/LibraryChef/islandora]&lt;br /&gt;
** Could use Vagrant and virtual box&lt;br /&gt;
* New release of Islandora expected soon &lt;br /&gt;
* Lyrasis is asked to review the documentation and will do sanity checks on the documentation&lt;br /&gt;
* Should see improvements to documentation soon&lt;br /&gt;
&lt;br /&gt;
Hosted solutions available to purchase:&lt;br /&gt;
* Lyrasis [https://www.lyrasis.org/LYRASIS%20Digital/Pages/Repository.aspx]&lt;br /&gt;
* DiscoveryGarden [http://discoverygarden.ca/solutions_ir.php]&lt;br /&gt;
* Cherry Hill Co. (coming soon) [http://chillco.com]&lt;br /&gt;
&lt;br /&gt;
What's the learning curve with Drupal - easier/harder than Hydra?&lt;br /&gt;
* Drupal 7 is easier to learn than Drupal 6&lt;br /&gt;
* Recommend the Using Drupal / O'Reilly Book [http://www.worldcat.org/title/using-drupal/oclc/233931612]&lt;br /&gt;
** Useful to understand theming / design&lt;br /&gt;
* Drupal may be more widely-held skill set than Ruby on Rails (in which Hydra is based)&lt;br /&gt;
* Though at least one school's Islandora developer started with Islandora without a PHP/Drupal background&lt;br /&gt;
* DrupalCon - first week in June, Austin TX in 2014&lt;br /&gt;
* Islandora Camp ([http://islandora.ca/camps])&lt;br /&gt;
&lt;br /&gt;
Setup difficulty?&lt;br /&gt;
* Documentation for setting up Solr / Gsearch - some confusion between v. 6 &amp;amp; 7 documentation&lt;br /&gt;
* Would be better for things to be more grouped together&lt;br /&gt;
&lt;br /&gt;
Using Islandora for Media Streaming&lt;br /&gt;
*Video streaming:  streams in HTML5 / used to use Flash in Islandora 6&lt;br /&gt;
*Every video gets an Mp4; audio files use Mp3&lt;br /&gt;
*How are storing the original videos?  In Fedora.  Note: objects do not have to be stored in Fedora&lt;br /&gt;
*Can still think of Fedora as the repository - include all master files and metadata.  if need to migrate out of Fedora in the future, could simply retain master files and metdata.&lt;br /&gt;
*Media Streaming installed on Drupal server&lt;br /&gt;
**FlowPlayer; jwplayer available for Islandora 7&lt;br /&gt;
*Grinnel contracted with Discovery Garden to create generic content solution pack that allowed the creation of an object that held multiple types of files (pdf images, audio, video).  Traded the ability to stream for the ability to create a compound object.  Now need to do additional work to standardize for Islandora 7.&lt;br /&gt;
*Binary object created by Discovery Garden - for download.&lt;br /&gt;
*Islandora has several solution packs for multiple file types (video, audio, compound, large images, small images).  Colorado use case involved oral history (video, audio, text documents together) which should be possible to use with the compound solution packs.&lt;br /&gt;
&lt;br /&gt;
Versioning problems encountered:&lt;br /&gt;
*For each object - new folder is created?  Can turn off versioning based upon file type; do version the metadata, but not the actual master files themselves.&lt;br /&gt;
*Could also use Fedora as a registry - not store the objects themselves because of versioning and performance/scaling issues.  &lt;br /&gt;
&lt;br /&gt;
How to handle updates to metadata?  &lt;br /&gt;
*Checkbox to version or not.&lt;br /&gt;
*METS-like XML schema as a container (FOXML).  When version -it adds it in to FOXML; Islandora only displays the most recent version&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note about custom modules:&lt;br /&gt;
*Custom modules can be difficult to get community support.  out-of-house development makes it difficult to join back with the larger community and core code.&lt;br /&gt;
&lt;br /&gt;
Long-term preservation:&lt;br /&gt;
*MetaArchive - locked server, dark archive.  May be module available for checksum generator and checksum checker - runs checksum on ingest and periodically check them.&lt;br /&gt;
*DuraCloud - application on top of Amazon storage run by DuraSpace&lt;br /&gt;
*Premise - preservation metadata system that helps record whenever records are touched or changed for audit trail.&lt;br /&gt;
&lt;br /&gt;
What happened to Hylandora?&lt;br /&gt;
* Came down to the content model: Islandora and Hydra were too divergent.  &lt;br /&gt;
&lt;br /&gt;
Reasons to go with Islandora over Hydra:&lt;br /&gt;
* Just depends on the skill set available&lt;br /&gt;
* Both Hydra and Islandora have active communities&lt;br /&gt;
&lt;br /&gt;
Issues:&lt;br /&gt;
* Upgrades can be painful / difficult in both Hydra and Islandora&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
What kinds of content is appropriate for Islandora?&lt;br /&gt;
* Good for special collections and ETDs, images from Athletic departments and ContentDM&lt;br /&gt;
* Crossover with Content Management systems, emphasize a policy on what should be included for long-term preservation&lt;br /&gt;
* Grinnell - small liberal arts college; emphasize promoting a place for faculty and students to store their research (undergraduate papers, faculty white papers/publication, data sets, digital humanities, videos of performances, audio of music performances, preserving websites (difficult with Islandora 6 vs. 7, which has a WARCIVE module)&lt;br /&gt;
** Don't want to necessarily limit to a library-only thing; include instructional designers, academic affairs, art gallery, history, &lt;br /&gt;
* Florida:  modules:  large images, small image, pdf and books.  Books module - good for yearbooks.  Want to use it for ETDs and research. &lt;br /&gt;
** Workflow module - has been useful.  Similar to DSpace workflow for ETDs.  When we ingest objects and they're not ready to be published - can work with metadata, wait to publish and not be visible to the public until they are ready to publish.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Access Controls/Embargoes, Harvesting, and Statistics&lt;br /&gt;
* Access controls for data:  Fedora use XacMole (sp)? to set permissions.  can set embargoes for ETDs.  IP embargo module.  Could extend to the bitstream level.  Pretty easy to do without breaking anything.&lt;br /&gt;
* OAI:PMH module - might not like how the Dublin Core looks out of the box - can use MODS out of the box to do the MODS to DC transform.  Needs additional work to pass the 2.0 specification.  Module that includes a REST API that will return data on various levels if requesting just specific items.  &lt;br /&gt;
* How to handle statistics?  e.g., what are the counts for objects per creation date.  &lt;br /&gt;
** Perl script that will lookup the size of the collection, how many objects - on Github&lt;br /&gt;
** Google Analytics module in 7&lt;br /&gt;
&lt;br /&gt;
==Relevance Search &amp;amp; Ranking==&lt;br /&gt;
&lt;br /&gt;
==Metadata Harvesting Normalization &amp;amp; Enrichement @ Scale==&lt;br /&gt;
&lt;br /&gt;
* Seeing same tools that were brought forth and then not hearing anything else about them.&lt;br /&gt;
* Conversations with folk about normalizing and enriching metadata.&lt;br /&gt;
* Lets hear about tools and things they are working on.&lt;br /&gt;
* Particular processes.&lt;br /&gt;
&lt;br /&gt;
==VuFind Update==&lt;br /&gt;
&lt;br /&gt;
==Telecommunicating Support Group==&lt;br /&gt;
&lt;br /&gt;
@mjgiarlo&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==BIBFRAME==&lt;br /&gt;
Notes are based off the Tweets made by the group during the discussion:&lt;br /&gt;
&lt;br /&gt;
'''Questions''' &lt;br /&gt;
*What will workflows will look like after Linked Data and BIBFRAME are actually pushed out?&lt;br /&gt;
*How to best use controlled vocabularies, including various/local controlled vocabularies, in linked data work?&lt;br /&gt;
*Will the protectiveness of quality by catalogers become thing of past? &lt;br /&gt;
&lt;br /&gt;
'''Pros'''&lt;br /&gt;
*Good thing about RDF, semantic metadata structure is that is creates a good skeleton that can last through system changes.&lt;br /&gt;
*Talked about OpenRefine, Freebase, Linked Data/Semantic Web examples &lt;br /&gt;
*Shout out for the Open Metadata Registry - http://metadataregistry.org/&lt;br /&gt;
*RDFa allows multiple property values inline- more details than http://schema.org , starts to approach MARC richness&lt;br /&gt;
&lt;br /&gt;
'''Concerns'''&lt;br /&gt;
*Wariness of simplicity (particularly of Dublin Core) due to the possibility of overloading elements, thus blocking interoperability with other schemas.&lt;br /&gt;
*There is the possible issue of every library creating their own ontologies, thus reinventing the wheel.&lt;br /&gt;
*Discussion of how long-term cataloging employees will handle this linked data 'revolution', how to best oversee these changes with catalogers dragging their feet.&lt;br /&gt;
&lt;br /&gt;
==Archivespace==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==User Experience==&lt;br /&gt;
&lt;br /&gt;
''Blame @erinrwhite for cruddy notes.''&lt;br /&gt;
&lt;br /&gt;
Coral facilitates. Her question for the group is, how can we overcome the focus on library experience and focus instead on user experience?&lt;br /&gt;
&lt;br /&gt;
=== what's your problem?===&lt;br /&gt;
&lt;br /&gt;
Introductions. Common problems:&lt;br /&gt;
&lt;br /&gt;
* &amp;quot;Just make a web page!&amp;quot;&lt;br /&gt;
* &amp;quot;I can figure this weird arcane and overly complicated thing out. Why can't anyone else?&amp;quot;&lt;br /&gt;
* Convincing stakeholders that design isn't print design, doesn't need to be the same for everyone and isn't static.&lt;br /&gt;
* Redesign by committee, have mercy!&lt;br /&gt;
* Getting ready for a redesign&lt;br /&gt;
* Publishing/learning about UX research. Who's going through IRB, who's publishing this stuff?&lt;br /&gt;
* Devaluation of UX work in library, funding or mandate&lt;br /&gt;
* UX not being built into organizational policies etc.&lt;br /&gt;
* How can we scale up UX above and beyond one-project research? Expanding to include more projects beyond the website?&lt;br /&gt;
* How can we convince our organizations to not recreate the org chart with the website?&lt;br /&gt;
* Trying to create a UX position that is beyond web librarian&lt;br /&gt;
* Not just testing sites with librarians (!)&lt;br /&gt;
* What about user experience for back-of-house software?&lt;br /&gt;
* I'm a web team of one. Help?&lt;br /&gt;
* &amp;quot;Put the MARC view back in the catalog!&amp;quot;&lt;br /&gt;
* Do we really need to default to advanced search? Battling the exceptions vs the average user?&lt;br /&gt;
* Taking a guerrilla approach to UX research&lt;br /&gt;
* Not a lot of staff in digital area&lt;br /&gt;
* Moving from a culture of complaint to a culture of...fixing&lt;br /&gt;
&lt;br /&gt;
A couple folks here working in organizations that have UX and assessment built into the culture. Thanks in advance for your knowledge, y'all!&lt;br /&gt;
&lt;br /&gt;
=== themes===&lt;br /&gt;
&lt;br /&gt;
We broke into sub-groups:&lt;br /&gt;
&lt;br /&gt;
* Making time&lt;br /&gt;
* Changing culture&lt;br /&gt;
* Beyond the website&lt;br /&gt;
&lt;br /&gt;
==Worldcat Search API==&lt;br /&gt;
&lt;br /&gt;
Help beta test early release of the new WorldCat Search API&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Spotlight: Exhibits, Curated Collections and Blacklight==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Tools for Instruction==&lt;br /&gt;
&lt;br /&gt;
LMS Integration, Guide on the side, LibGuides, etc.&lt;br /&gt;
&lt;br /&gt;
Participants:&lt;br /&gt;
* Mike Hagedon; interests: [http://code.library.arizona.edu/gots Guide on the Side], LTI, LMS integration, subject/course guides&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Code4lib Conference Documentation==&lt;br /&gt;
&lt;br /&gt;
We discussed the ways in which the lack of historical data make proposing to host the conference difficult.  Code4libbers must convince their employer to take on financial responsibility. This does not mean the host pays. In fact, each conference has had a surplus. But a corporate institution is needed to sign the contracts with the venues and services used by the conference.  Employers need convincing that the event will not be a huge cost nor a burden on the business office. To convince the administrators, a historical record of past conferences would be immensely helpful.&lt;br /&gt;
&lt;br /&gt;
We discussed several data points that would be useful. Some of these include&lt;br /&gt;
* expected and final budgets&lt;br /&gt;
* total attendance&lt;br /&gt;
* hotel room reservation block size and % of expected size actually used&lt;br /&gt;
* food costs, food expectations and % of food actually consumed&lt;br /&gt;
* etc.&lt;br /&gt;
&lt;br /&gt;
We plan to begin storing these kinds of data on the code4lib wiki for future planners to use.&lt;br /&gt;
&lt;br /&gt;
Some other documentation that we also plan to add to the wiki:&lt;br /&gt;
* Conference Planning Committee Post-mortem (Raleigh group already started this trend with the &amp;quot;Lessons Learned&amp;quot; post)&lt;br /&gt;
* explanation of what it's like to work with a 3rd party event planner (Concentra), such as:&lt;br /&gt;
** how money flows between attendees, sponsors, host, awardees, and concentra&lt;br /&gt;
** what are the benefits of working with a 3rd party planner?&lt;br /&gt;
* examples of MOUs between multiple host institutions&lt;br /&gt;
&lt;br /&gt;
Some action items:&lt;br /&gt;
* finish documenting this year's conference (Tim et al.)&lt;br /&gt;
* attempt to collect historical budgets if they still exist (Josh &amp;amp; Rosy)&lt;br /&gt;
* organize existing data on the wiki (?)&lt;br /&gt;
&lt;br /&gt;
==VuFind Update==&lt;br /&gt;
Sorry for the delay&lt;/div&gt;</summary>
		<author><name>ChristopherHallberg</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&amp;diff=40758</id>
		<title>2014 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&amp;diff=40758"/>
				<updated>2014-03-20T17:20:36Z</updated>
		
		<summary type="html">&lt;p&gt;ChristopherHallberg: /* RailsBridge: Intro to programming in Ruby on Rails */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= PROPOSALS ARE CLOSED : PLEASE DO NOT ADD NEW PRECONFERENCES TO THIS PAGE =&lt;br /&gt;
&lt;br /&gt;
Proposals were accepted through December 6th, 2013.&lt;br /&gt;
&lt;br /&gt;
It would be really, super duper helpful if folks who think they might want to attend a pre-conference could indicate interest by adding your name to a session below. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Note===&lt;br /&gt;
Attendance at a pre-conference will require a small fee ''due at the time of conference registration&amp;quot;.&lt;br /&gt;
 &lt;br /&gt;
Although this was specified in the email announcements relating to pre-conferences, it was not added to this page until December 2nd.  I (Adam C.) apologize for the omission and I hope this will not cause any &amp;quot;sticker shock.&amp;quot;  Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.&lt;br /&gt;
&lt;br /&gt;
Please put your pre-conference on the list in the following format:&lt;br /&gt;
&lt;br /&gt;
=Code4Lib 2014 Pre-Conference Proposals=&lt;br /&gt;
&lt;br /&gt;
===Drupal4lib Sub-con Barcamp===&lt;br /&gt;
=====Full Day=====&lt;br /&gt;
&lt;br /&gt;
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.&lt;br /&gt;
&lt;br /&gt;
This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).&lt;br /&gt;
&lt;br /&gt;
[[resources to help you learn drupal]]&lt;br /&gt;
&lt;br /&gt;
====Interested in Attending:====&lt;br /&gt;
&lt;br /&gt;
=====All Day=====&lt;br /&gt;
&lt;br /&gt;
* Renna Tuten &lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
&lt;br /&gt;
* Kevin Reiss&lt;br /&gt;
* Charlie Morris (NCSU) - glad to see this again this year!&lt;br /&gt;
* Paula Gray-Overtoom&lt;br /&gt;
* Laurie Lee Moses&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Open Refine Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day[Morning]&amp;quot;'''&lt;br /&gt;
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com&lt;br /&gt;
&lt;br /&gt;
[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control&lt;br /&gt;
&lt;br /&gt;
The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. &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;
&amp;lt;ol&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Adam Constabaris&lt;br /&gt;
&amp;lt;li&amp;gt;Jason Stirnaman&lt;br /&gt;
&amp;lt;li&amp;gt;Joshua Gomez&lt;br /&gt;
&amp;lt;li&amp;gt;Sam Kome&lt;br /&gt;
&amp;lt;li&amp;gt;Mike Beccaria&lt;br /&gt;
&amp;lt;li&amp;gt;Angela Zoss&lt;br /&gt;
&amp;lt;li&amp;gt;A. Soroka&lt;br /&gt;
&amp;lt;li&amp;gt; Matt Zumwalt&lt;br /&gt;
&amp;lt;li&amp;gt;Jim LeFager&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Responsive Design Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day [Afternoon]&amp;quot;''' &lt;br /&gt;
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com&lt;br /&gt;
* Contact David Ward, University of Illinois, dh-ward@illinois.edu&lt;br /&gt;
&lt;br /&gt;
This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. &lt;br /&gt;
&lt;br /&gt;
Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.&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;
=== Intro to Blacklight ===&lt;br /&gt;
'''&amp;quot;Half-Day [Morning]&amp;quot;''' &lt;br /&gt;
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
* TA: Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
This session will be walk-through of the architecture of Blacklight, the community, and an introduction to building a Blacklight-based application. Each participant will have the opportunity to build a simple Blacklight application, and make basic customizations, while using a test-driven approach.&lt;br /&gt;
&lt;br /&gt;
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.&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;
# Megan Kudzia&lt;br /&gt;
# Bret Davidson&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Cory Lown&lt;br /&gt;
# Emily Daly&lt;br /&gt;
# Angela Zoss&lt;br /&gt;
# Sean Aery&lt;br /&gt;
# Francis Kayiwa&lt;br /&gt;
# Heidi Frank&lt;br /&gt;
# Junior Tidal&lt;br /&gt;
# Ian Chan&lt;br /&gt;
# Ted Lawless&lt;br /&gt;
# David Lacy&lt;br /&gt;
# Erik Hatcher&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Blacklight Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day [Afternoon]&amp;quot;''' &lt;br /&gt;
* Contact Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
&lt;br /&gt;
This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.&lt;br /&gt;
&lt;br /&gt;
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).&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;
# Shaun Ellis&lt;br /&gt;
# Kevin Reiss&lt;br /&gt;
# Megan Kudzia&lt;br /&gt;
# Erik Hatcher&lt;br /&gt;
# Emily Daly&lt;br /&gt;
# Laurie Lee Moses&lt;br /&gt;
# Francis Kayiwa&lt;br /&gt;
# Ted Lawless&lt;br /&gt;
# David Lacy&lt;br /&gt;
&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 Justin Coyne, Data Curation Experts, justin@curationexperts.com&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! 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 Blacklight and Hydra.&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;
# Ayla Stein&lt;br /&gt;
# Heidi Dowding&lt;br /&gt;
# Caitlin Christian-Lamb&lt;br /&gt;
# Scott Bacon&lt;br /&gt;
# [[User:RileyChilds | Riley Childs]]&lt;br /&gt;
# Carolina Garcia&lt;br /&gt;
# David Uspal&lt;br /&gt;
# Chris Hallberg&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===&lt;br /&gt;
'''Full-Day'''&lt;br /&gt;
&lt;br /&gt;
Contact: &lt;br /&gt;
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com&lt;br /&gt;
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu&lt;br /&gt;
&lt;br /&gt;
This will be a full day session on project management.  We'll cover&lt;br /&gt;
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment&lt;br /&gt;
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets&lt;br /&gt;
* '''Executing the Project''' -- status meeting, status reports, issue management&lt;br /&gt;
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product&lt;br /&gt;
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.&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;
# Robin Dean&lt;br /&gt;
# Erin White&lt;br /&gt;
# Andrew Darby&lt;br /&gt;
# Sam Kome&lt;br /&gt;
# Ryan Scherle&lt;br /&gt;
# Will Shaw&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
# Cynthia &amp;quot;Arty&amp;quot; Ng&lt;br /&gt;
# Laurie Lee Moses (if I don't do the Hackfest for Blacklight)&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
# Bohyun Kim (Afternoon)&lt;br /&gt;
# Mike Hagedon&lt;br /&gt;
# Chris Hallberg&lt;br /&gt;
#Susan Ivey &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Fail4Lib 2014===&lt;br /&gt;
'''Half Day [TBD, probably afternoon]'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Andreas Orphanides, akorphan (at) ncsu.edu&lt;br /&gt;
* Jason Casden, jmcasden (at) ncsu.edu&lt;br /&gt;
&lt;br /&gt;
The task of design (and the work that we do as library coders) is intimately tied to failure. Failures, both big and small, motivate us to create and improve. Failures are also occasionally the result of our work. Understanding and embracing failure, encouraging enlightened risk-taking, and seeking out opportunities to fail and learn are essential to success in our field. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be feared.&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
&lt;br /&gt;
* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?&lt;br /&gt;
* Confessionals, for those willing to share. Talk about your own experiences with rough starts, labor pains, and doomed projects in your own work: What can we learn from our own (and each others') failures?&lt;br /&gt;
* Group therapy. Let's talk about how to deal with risk management, failed projects, experimental endeavors, and more: How can we make ourselves, our colleagues, and our organizations more fault tolerant? How do we make sure we fail as productively as possible?&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;
#Bret Davidson&lt;br /&gt;
#Mike Graves&lt;br /&gt;
#Jason Stirnaman&lt;br /&gt;
#Julia Bauder&lt;br /&gt;
#Linda Ballinger&lt;br /&gt;
#Scott Hanrath&lt;br /&gt;
#Caitlin Christian-Lamb&lt;br /&gt;
#Ian Walls&lt;br /&gt;
#Scott Bacon &lt;br /&gt;
#mx matienzo&lt;br /&gt;
#Chris Sharp&lt;br /&gt;
#Junior Tidal&lt;br /&gt;
#Julie Rudder&lt;br /&gt;
#David Uspal&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===CLLAM @ code4lib===&lt;br /&gt;
'''(Computational Linguistics for Libraries, Archives and Museums)'''&lt;br /&gt;
&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Douglas W. Oard (primary), oard (at) umd.edu &lt;br /&gt;
* Corey Harper, corey (dot) harper (at) nyu.edu&lt;br /&gt;
* Robert Sanderson, azaroth42 (at) gmail.com &lt;br /&gt;
* Robert Warren, rwarren (at) math.carleton.ca&lt;br /&gt;
&lt;br /&gt;
We will hack at the intersection of diverse content from Libraries, Archives and Museums and bleeding edge tools from computational linguistics for slicing and dicing that content. Did you just acquire the email archives of a startup company? Maybe you can automatically build an org chart. Have you got metadata in a slew of languages? Perhaps you can search it all using one query. Is name authority control for e-resources getting too costly? Let’s see if entity linking techniques can help. These are just a few teasers. &lt;br /&gt;
&lt;br /&gt;
There’ll be plenty of content and tools supplied, but please bring your own [data] too -- you’ll hack with it in new ways throughout the day. We’ll get started with some lightning talks on what we’ve brought,then we’ll break up into groups to experiment and work on the ideas that appeal. Three guaranteed outcomes: you’ll walk away with new ideas, new tools, and new people you’ll have met.&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;
# Devon Smith&lt;br /&gt;
# Kevin S. Clarke&lt;br /&gt;
# Jason Stirnaman&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Carolina Garcia&lt;br /&gt;
# Tom Burton-West&lt;br /&gt;
# Dan Scott&lt;br /&gt;
# Devin Higgins&lt;br /&gt;
# Mark Breedlove&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== GeoHydra: Managing geospatial content ===&lt;br /&gt;
&lt;br /&gt;
'''Half-day [Afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Contact: Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Moderator: Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,&lt;br /&gt;
etc., all of which you want to integrate into your digital repository? In this&lt;br /&gt;
workshop, we will discuss how Hydra can provide discovery, delivery, and&lt;br /&gt;
management services for geospatial assets, as well as solicit questions about&lt;br /&gt;
your own GIS projects. We aim to help answer the following questions you might have about putting geospatial data into your Hydra-based digital library:&lt;br /&gt;
&lt;br /&gt;
* What are the types of geospatial data?&lt;br /&gt;
* How to dive into Hydra?&lt;br /&gt;
* How to model geospatial holdings with Hydra?&lt;br /&gt;
* How to discover and view geospatial data?&lt;br /&gt;
* How to build a geospatial data infrastructure?&lt;br /&gt;
* What are common approaches and problems?&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;
# Esmé Cowles&lt;br /&gt;
# David Drexler&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Technology, Librarianship, and Gender: Moving the conversation forward===&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]&lt;br /&gt;
&lt;br /&gt;
'''Description'''&lt;br /&gt;
&lt;br /&gt;
Librarianship is largely made up of women, yet women are significantly underrepresented in tech positions, on any level, within libraries themselves. Why? What are we doing to encourage women to become more involved in STEM within librarianship? What kind of message are we sending when library technology keynotes remain almost resolutely male? How are we changing the face of technology, not only within libraries, but with the field itself? How are we training our staff and colleagues in the areas of fairness and removal of bias? Our vendors?&lt;br /&gt;
&lt;br /&gt;
Lots of tough questions.&lt;br /&gt;
&lt;br /&gt;
While the conversation has been going on via various blogs and articles within the last few years, it was given a public face at [http://infotoday.com/il2013/day.asp?day=Monday#session_D105 Internet Librarian 2013] where a panel of 7 (four women, three men) gave personal experiences on the above and then opened up the conversation to the audience. As eye opening and enriching the conversation was, a 45 minute panel was not enough. One thing remains clear: We need to keep the conversation moving forward and start making some radical changes in the way we think, act, and how we need to harness this to start making real changes within librarianship itself.&lt;br /&gt;
&lt;br /&gt;
Topics to include:  Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems,  mentoring, ally support, and more&lt;br /&gt;
&lt;br /&gt;
Those attending should expect: Begin with opening up the conversation of experiences and talking about what is most needed, spending remaining time putting together live, usable solutions to start implementing as well as pushing the conversation forward at local levels&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;
=====All Day=====&lt;br /&gt;
1. Kate Kosturski&lt;br /&gt;
&lt;br /&gt;
2. Valerie Aurora&lt;br /&gt;
&lt;br /&gt;
3. Declan Fleming (I'd be good with a half day too)&lt;br /&gt;
&lt;br /&gt;
4. mx matienzo (likewise ok w/ half day)&lt;br /&gt;
&lt;br /&gt;
5. Ginny Boyer (I'd be good with a half day too)&lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
1. Shaun Ellis&lt;br /&gt;
&lt;br /&gt;
2. Jason Casden&lt;br /&gt;
&lt;br /&gt;
3. Bohyun Kim&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
1. Ayla Stein&lt;br /&gt;
&lt;br /&gt;
2. Heidi Dowding&lt;br /&gt;
&lt;br /&gt;
3. Coral Sheldon-Hess&lt;br /&gt;
&lt;br /&gt;
4. Cory Lown&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===FileAnalyzer: Rapid Development of File Manipulation Tasks===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
* Contact Terry Brady, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The FileAnalyzer (http://georgetown-university-libraries.github.io/File-Analyzer/) is an application designed to solve a number of library automation challenges:&lt;br /&gt;
&lt;br /&gt;
* validating digitized and reformatted files&lt;br /&gt;
* validating vendor statistics for counter compliance&lt;br /&gt;
* preparing collections of digital files for archiving and ingest&lt;br /&gt;
* manipulating ILS import and export files&lt;br /&gt;
&lt;br /&gt;
The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census. After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform. Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.&lt;br /&gt;
&lt;br /&gt;
The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules. As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.&lt;br /&gt;
&lt;br /&gt;
The first half of this session will be targeted to potential users and developers.  The second half of the session will be targeted towards developers who are interested in developing custom rules for the application.&lt;br /&gt;
&lt;br /&gt;
''Session Overview''&lt;br /&gt;
* Overview of the application&lt;br /&gt;
* Running sample file tests/transformations through the application&lt;br /&gt;
* Compiling and building the application&lt;br /&gt;
* Coding a custom file processing task&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;
# Michael Doran&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Collecting social media data with Social Feed Manager===&lt;br /&gt;
'''Half-Day [Morning]'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Dan Chudnov, GW Libraries, dchud (at) gwu.edu&lt;br /&gt;
* Dan Kerchner, GW Libraries, kerchner (at) gwu.edu&lt;br /&gt;
* Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu&lt;br /&gt;
&lt;br /&gt;
Social media data is a popular material for research and a new format for building collections.  What does it take to collect meaningfully from Twitter, Tumblr, YouTube, Weibo, Facebook, and other sites?  We will:&lt;br /&gt;
* Introduce options for collections, including both high- and low-end commercial offerings. Discuss what it means to collect these resources, covering boundaries, policies, and workflows required to develop a social media collection program in your institution.&lt;br /&gt;
* Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them&lt;br /&gt;
* Help you get started using the free [http://gwu-libraries.github.io/social-feed-manager Social Feed Manager] (SFM) app we're developing at GW to create your first collections. We’ll demo its use and demo a clean install (those w/environments can follow along)&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;
# Declan Fleming&lt;br /&gt;
# Esmé Cowles&lt;br /&gt;
# Jason Stirnaman&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Intro to Git ===&lt;br /&gt;
'''&amp;quot;Half-Day [tbd - probably afternoon]&amp;quot;''' &lt;br /&gt;
* Contact: Erin Fahy, Stanford University, efahy at stanford.edu&lt;br /&gt;
* TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu&lt;br /&gt;
&lt;br /&gt;
This session will cover the fundamentals of git by discussing/going through (time allowing):&lt;br /&gt;
* what is a distributed version control system&lt;br /&gt;
* what is git and github&lt;br /&gt;
* initializing a repo on a remote server/github&lt;br /&gt;
* cloning an existing repo&lt;br /&gt;
* creating a branch&lt;br /&gt;
* contributing code to a repo&lt;br /&gt;
* how to handle merge conflicts&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;
# Sam Kome&lt;br /&gt;
# Paula Gray-Overtoom&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
# Michael Doran&lt;br /&gt;
# Caitlin Christian-Lamb&lt;br /&gt;
# [[User:RileyChilds|Riley Childs]]&lt;br /&gt;
# Jim LeFager&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Archival discovery and use ===&lt;br /&gt;
'''Full Day''' &lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Tim Shearer, UNC Chapel Hill, tshearer at email.unc.edu, &lt;br /&gt;
* Will Sexton, Duke, will.sexton at duke.edu&lt;br /&gt;
&lt;br /&gt;
This is a full day pre-conference about archival collections and will cover the intersections of archives, workflows, technologies, discovery, and use.&lt;br /&gt;
&lt;br /&gt;
Morning agenda: focused talks around (but not limited to) issues such as:&lt;br /&gt;
* Crowd-sourcing description to enhance collecitons&lt;br /&gt;
* Linked data and authority&lt;br /&gt;
* Mass digitization and sustainable workflows&lt;br /&gt;
* Digitized objects in context (images and other objects in finding aids)&lt;br /&gt;
* Too many cooks in the kitchen: versioning&lt;br /&gt;
* Global-, intra-, and inter- discovery of archival materials via finding aids &lt;br /&gt;
* and more...&lt;br /&gt;
&lt;br /&gt;
Afternoon agenda:  Focused talks around specific tools followed by general discussion, connections, opportunities, aspirations, and planning.&lt;br /&gt;
&lt;br /&gt;
Tool examples:&lt;br /&gt;
* Archivespace&lt;br /&gt;
* STEADy&lt;br /&gt;
* &amp;quot;RAMP&amp;quot; (Remixing Archival Metadata Project)&lt;br /&gt;
* OpenRefine&lt;br /&gt;
* Aeon&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;
Morning:&lt;br /&gt;
* Julia Bauder&lt;br /&gt;
&lt;br /&gt;
Afternoon:&lt;br /&gt;
* your name&lt;br /&gt;
&lt;br /&gt;
All day:&lt;br /&gt;
&lt;br /&gt;
# Josh Wilson&lt;br /&gt;
# Sam Kome&lt;br /&gt;
# Linda Ballinger&lt;br /&gt;
# Caitlin Christian-Lamb&lt;br /&gt;
# Laurie Lee Moses (seriously hard to decide here!)&lt;br /&gt;
# David Bass&lt;br /&gt;
# John Rees&lt;br /&gt;
# Lynn Eaton&lt;br /&gt;
# Hillel Arnold&lt;br /&gt;
# Susan Ivey&lt;br /&gt;
# Kristen Merryman&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===AV Content Slam===&lt;br /&gt;
'''Half-Day [morning]'''&lt;br /&gt;
Contacts:&lt;br /&gt;
* Kara Van Malssen, kara (at) avpreserve.com&lt;br /&gt;
* Lauren Sorenson, laurens (at) bavc.org&lt;br /&gt;
* Steven Villereal , villereal (at) gmail.com&lt;br /&gt;
A morning BarCamp/unconference for practitioners and coders who work with audiovisual content. The agenda will be attendee-driven, with a focus on sharing, synthesizing, and improving workflow strategies and documentation for software-based approaches to wrangling and providing access to audio and video content.&lt;br /&gt;
Possible topics of discussion might include:&lt;br /&gt;
* Use of format id and characterization/metadata extraction tools for AV&lt;br /&gt;
* Creating and using time-based metadata&lt;br /&gt;
* Managing (moving, fixity checking, etc) massive files (like uncompressed video)&lt;br /&gt;
For a better idea of the topics and concerns that have informed some past AV-themed events, check out the event wikis for [http://wiki.curatecamp.org/index.php/CURATEcamp_AVpres_2013 CURATEcamp AVpres 2013] as well as the [http://wiki.curatecamp.org/index.php/Association_of_Moving_Image_Archivists_%26_Digital_Library_Federation_Hack_Day_2013 AMIA/DLF 2013 Hack Day] .&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;
# A. Soroka&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===OCLC Web Services Hackfest===&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Half-Day&amp;quot; [afternoon]&lt;br /&gt;
&lt;br /&gt;
Contact: Shelley Hostetler, Community Manager, Developer Network hostetls[at]oclc.org&lt;br /&gt;
&lt;br /&gt;
This half-day hackfest will explore some of the OCLC Developer Network web services. We will provide an overview of some of the common topics such as the general REST-based architecture for most services and how to use some new authentication clients. The group can then decide to take a deep dive into a particular API and/or write a client library for the community.&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;
===Obey the Testing Goat!: Test Driven Web Development From The Ground Up===&lt;br /&gt;
'''Half-Day [tbd - probably afternoon]'''&lt;br /&gt;
* Contact [[User:Mredar|Mark Redar]], mredar[at]gmail.com&lt;br /&gt;
&lt;br /&gt;
Test driven development is a proven method for producing better quality code. But I've found it hard to follow a strict TDD methodology when starting new web projects. How do you write that first test when there is no code or web pages created yet.&lt;br /&gt;
&lt;br /&gt;
In this session, we will follow the excellent book [http://shop.oreilly.com/product/0636920029533.do &amp;quot;Test-Driven Web Development with Python&amp;quot;] to create a simple web site in Django following TDD from the first character typed. Come ready to code and test. No prior knowledge of python or Django required.&lt;br /&gt;
&lt;br /&gt;
By the end of this session, you should be able to  [http://www.obeythetestinggoat.com/ &amp;quot;Obey the Testing Goat&amp;quot;] from the start to finish for your next project.&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;
# Charlie Morris (NCSU)&lt;br /&gt;
# Jason Stirnaman&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
# Scott Hanrath&lt;br /&gt;
# Mike Beccaria&lt;br /&gt;
# Sean Aery&lt;br /&gt;
# Carolina Garcia&lt;br /&gt;
# Heidi Frank&lt;br /&gt;
# Chung Kang&lt;br /&gt;
# Nabil Kashyap&lt;br /&gt;
# Justin Simpson&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Summon Hackfest ===&lt;br /&gt;
&lt;br /&gt;
Presenter: Eddie Newwirth and presenters from Summon libraries&lt;br /&gt;
Contact: Scott Schuetze (first DOT last @ serialssolutions. com)&lt;br /&gt;
&lt;br /&gt;
The Summon Hackfest (10:30am-12pm) will be a great opportunity for libraries using the Summon service to talk about improving discovery of resources, share their creative customizations and code, and exchange ideas about ways they can leverage the Summon API to better meet the needs of their users.&lt;br /&gt;
 &lt;br /&gt;
The Summon Hackfest is open to all libraries currently using ProQuest discovery and management services (Intota, Summon, Ulrich’s or the 360 suite of services), whether they are attending Code4Lib or are just in the area.&lt;br /&gt;
 &lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
[[:Category:Code4Lib2014]]&lt;/div&gt;</summary>
		<author><name>ChristopherHallberg</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&amp;diff=40757</id>
		<title>2014 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&amp;diff=40757"/>
				<updated>2014-03-20T17:18:30Z</updated>
		
		<summary type="html">&lt;p&gt;ChristopherHallberg: /* RailsBridge: Intro to programming in Ruby on Rails */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= PROPOSALS ARE CLOSED : PLEASE DO NOT ADD NEW PRECONFERENCES TO THIS PAGE =&lt;br /&gt;
&lt;br /&gt;
Proposals were accepted through December 6th, 2013.&lt;br /&gt;
&lt;br /&gt;
It would be really, super duper helpful if folks who think they might want to attend a pre-conference could indicate interest by adding your name to a session below. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Note===&lt;br /&gt;
Attendance at a pre-conference will require a small fee ''due at the time of conference registration&amp;quot;.&lt;br /&gt;
 &lt;br /&gt;
Although this was specified in the email announcements relating to pre-conferences, it was not added to this page until December 2nd.  I (Adam C.) apologize for the omission and I hope this will not cause any &amp;quot;sticker shock.&amp;quot;  Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.&lt;br /&gt;
&lt;br /&gt;
Please put your pre-conference on the list in the following format:&lt;br /&gt;
&lt;br /&gt;
=Code4Lib 2014 Pre-Conference Proposals=&lt;br /&gt;
&lt;br /&gt;
===Drupal4lib Sub-con Barcamp===&lt;br /&gt;
=====Full Day=====&lt;br /&gt;
&lt;br /&gt;
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.&lt;br /&gt;
&lt;br /&gt;
This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).&lt;br /&gt;
&lt;br /&gt;
[[resources to help you learn drupal]]&lt;br /&gt;
&lt;br /&gt;
====Interested in Attending:====&lt;br /&gt;
&lt;br /&gt;
=====All Day=====&lt;br /&gt;
&lt;br /&gt;
* Renna Tuten &lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
&lt;br /&gt;
* Kevin Reiss&lt;br /&gt;
* Charlie Morris (NCSU) - glad to see this again this year!&lt;br /&gt;
* Paula Gray-Overtoom&lt;br /&gt;
* Laurie Lee Moses&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Open Refine Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day[Morning]&amp;quot;'''&lt;br /&gt;
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com&lt;br /&gt;
&lt;br /&gt;
[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control&lt;br /&gt;
&lt;br /&gt;
The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. &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;
&amp;lt;ol&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Adam Constabaris&lt;br /&gt;
&amp;lt;li&amp;gt;Jason Stirnaman&lt;br /&gt;
&amp;lt;li&amp;gt;Joshua Gomez&lt;br /&gt;
&amp;lt;li&amp;gt;Sam Kome&lt;br /&gt;
&amp;lt;li&amp;gt;Mike Beccaria&lt;br /&gt;
&amp;lt;li&amp;gt;Angela Zoss&lt;br /&gt;
&amp;lt;li&amp;gt;A. Soroka&lt;br /&gt;
&amp;lt;li&amp;gt; Matt Zumwalt&lt;br /&gt;
&amp;lt;li&amp;gt;Jim LeFager&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Responsive Design Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day [Afternoon]&amp;quot;''' &lt;br /&gt;
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com&lt;br /&gt;
* Contact David Ward, University of Illinois, dh-ward@illinois.edu&lt;br /&gt;
&lt;br /&gt;
This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. &lt;br /&gt;
&lt;br /&gt;
Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.&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;
=== Intro to Blacklight ===&lt;br /&gt;
'''&amp;quot;Half-Day [Morning]&amp;quot;''' &lt;br /&gt;
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
* TA: Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
This session will be walk-through of the architecture of Blacklight, the community, and an introduction to building a Blacklight-based application. Each participant will have the opportunity to build a simple Blacklight application, and make basic customizations, while using a test-driven approach.&lt;br /&gt;
&lt;br /&gt;
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.&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;
# Megan Kudzia&lt;br /&gt;
# Bret Davidson&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Cory Lown&lt;br /&gt;
# Emily Daly&lt;br /&gt;
# Angela Zoss&lt;br /&gt;
# Sean Aery&lt;br /&gt;
# Francis Kayiwa&lt;br /&gt;
# Heidi Frank&lt;br /&gt;
# Junior Tidal&lt;br /&gt;
# Ian Chan&lt;br /&gt;
# Ted Lawless&lt;br /&gt;
# David Lacy&lt;br /&gt;
# Erik Hatcher&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Blacklight Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day [Afternoon]&amp;quot;''' &lt;br /&gt;
* Contact Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
&lt;br /&gt;
This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.&lt;br /&gt;
&lt;br /&gt;
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).&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;
# Shaun Ellis&lt;br /&gt;
# Kevin Reiss&lt;br /&gt;
# Megan Kudzia&lt;br /&gt;
# Erik Hatcher&lt;br /&gt;
# Emily Daly&lt;br /&gt;
# Laurie Lee Moses&lt;br /&gt;
# Francis Kayiwa&lt;br /&gt;
# Ted Lawless&lt;br /&gt;
# David Lacy&lt;br /&gt;
&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 Justin Coyne, Data Curation Experts, justin@curationexperts.com&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! 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 Blacklight and Hydra.&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;
1. Ayla Stein&lt;br /&gt;
&lt;br /&gt;
2. Heidi Dowding&lt;br /&gt;
&lt;br /&gt;
3. Caitlin Christian-Lamb&lt;br /&gt;
&lt;br /&gt;
4. Scott Bacon&lt;br /&gt;
&lt;br /&gt;
5. [[User:RileyChilds | Riley Childs]]&lt;br /&gt;
&lt;br /&gt;
6. Carolina Garcia&lt;br /&gt;
&lt;br /&gt;
7. David Uspal&lt;br /&gt;
&lt;br /&gt;
8. Chris Hallberg&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===&lt;br /&gt;
'''Full-Day'''&lt;br /&gt;
&lt;br /&gt;
Contact: &lt;br /&gt;
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com&lt;br /&gt;
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu&lt;br /&gt;
&lt;br /&gt;
This will be a full day session on project management.  We'll cover&lt;br /&gt;
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment&lt;br /&gt;
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets&lt;br /&gt;
* '''Executing the Project''' -- status meeting, status reports, issue management&lt;br /&gt;
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product&lt;br /&gt;
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.&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;
# Robin Dean&lt;br /&gt;
# Erin White&lt;br /&gt;
# Andrew Darby&lt;br /&gt;
# Sam Kome&lt;br /&gt;
# Ryan Scherle&lt;br /&gt;
# Will Shaw&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
# Cynthia &amp;quot;Arty&amp;quot; Ng&lt;br /&gt;
# Laurie Lee Moses (if I don't do the Hackfest for Blacklight)&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
# Bohyun Kim (Afternoon)&lt;br /&gt;
# Mike Hagedon&lt;br /&gt;
# Chris Hallberg&lt;br /&gt;
#Susan Ivey &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Fail4Lib 2014===&lt;br /&gt;
'''Half Day [TBD, probably afternoon]'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Andreas Orphanides, akorphan (at) ncsu.edu&lt;br /&gt;
* Jason Casden, jmcasden (at) ncsu.edu&lt;br /&gt;
&lt;br /&gt;
The task of design (and the work that we do as library coders) is intimately tied to failure. Failures, both big and small, motivate us to create and improve. Failures are also occasionally the result of our work. Understanding and embracing failure, encouraging enlightened risk-taking, and seeking out opportunities to fail and learn are essential to success in our field. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be feared.&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
&lt;br /&gt;
* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?&lt;br /&gt;
* Confessionals, for those willing to share. Talk about your own experiences with rough starts, labor pains, and doomed projects in your own work: What can we learn from our own (and each others') failures?&lt;br /&gt;
* Group therapy. Let's talk about how to deal with risk management, failed projects, experimental endeavors, and more: How can we make ourselves, our colleagues, and our organizations more fault tolerant? How do we make sure we fail as productively as possible?&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;
#Bret Davidson&lt;br /&gt;
#Mike Graves&lt;br /&gt;
#Jason Stirnaman&lt;br /&gt;
#Julia Bauder&lt;br /&gt;
#Linda Ballinger&lt;br /&gt;
#Scott Hanrath&lt;br /&gt;
#Caitlin Christian-Lamb&lt;br /&gt;
#Ian Walls&lt;br /&gt;
#Scott Bacon &lt;br /&gt;
#mx matienzo&lt;br /&gt;
#Chris Sharp&lt;br /&gt;
#Junior Tidal&lt;br /&gt;
#Julie Rudder&lt;br /&gt;
#David Uspal&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===CLLAM @ code4lib===&lt;br /&gt;
'''(Computational Linguistics for Libraries, Archives and Museums)'''&lt;br /&gt;
&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Douglas W. Oard (primary), oard (at) umd.edu &lt;br /&gt;
* Corey Harper, corey (dot) harper (at) nyu.edu&lt;br /&gt;
* Robert Sanderson, azaroth42 (at) gmail.com &lt;br /&gt;
* Robert Warren, rwarren (at) math.carleton.ca&lt;br /&gt;
&lt;br /&gt;
We will hack at the intersection of diverse content from Libraries, Archives and Museums and bleeding edge tools from computational linguistics for slicing and dicing that content. Did you just acquire the email archives of a startup company? Maybe you can automatically build an org chart. Have you got metadata in a slew of languages? Perhaps you can search it all using one query. Is name authority control for e-resources getting too costly? Let’s see if entity linking techniques can help. These are just a few teasers. &lt;br /&gt;
&lt;br /&gt;
There’ll be plenty of content and tools supplied, but please bring your own [data] too -- you’ll hack with it in new ways throughout the day. We’ll get started with some lightning talks on what we’ve brought,then we’ll break up into groups to experiment and work on the ideas that appeal. Three guaranteed outcomes: you’ll walk away with new ideas, new tools, and new people you’ll have met.&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;
# Devon Smith&lt;br /&gt;
# Kevin S. Clarke&lt;br /&gt;
# Jason Stirnaman&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Carolina Garcia&lt;br /&gt;
# Tom Burton-West&lt;br /&gt;
# Dan Scott&lt;br /&gt;
# Devin Higgins&lt;br /&gt;
# Mark Breedlove&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== GeoHydra: Managing geospatial content ===&lt;br /&gt;
&lt;br /&gt;
'''Half-day [Afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Contact: Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Moderator: Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,&lt;br /&gt;
etc., all of which you want to integrate into your digital repository? In this&lt;br /&gt;
workshop, we will discuss how Hydra can provide discovery, delivery, and&lt;br /&gt;
management services for geospatial assets, as well as solicit questions about&lt;br /&gt;
your own GIS projects. We aim to help answer the following questions you might have about putting geospatial data into your Hydra-based digital library:&lt;br /&gt;
&lt;br /&gt;
* What are the types of geospatial data?&lt;br /&gt;
* How to dive into Hydra?&lt;br /&gt;
* How to model geospatial holdings with Hydra?&lt;br /&gt;
* How to discover and view geospatial data?&lt;br /&gt;
* How to build a geospatial data infrastructure?&lt;br /&gt;
* What are common approaches and problems?&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;
# Esmé Cowles&lt;br /&gt;
# David Drexler&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Technology, Librarianship, and Gender: Moving the conversation forward===&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]&lt;br /&gt;
&lt;br /&gt;
'''Description'''&lt;br /&gt;
&lt;br /&gt;
Librarianship is largely made up of women, yet women are significantly underrepresented in tech positions, on any level, within libraries themselves. Why? What are we doing to encourage women to become more involved in STEM within librarianship? What kind of message are we sending when library technology keynotes remain almost resolutely male? How are we changing the face of technology, not only within libraries, but with the field itself? How are we training our staff and colleagues in the areas of fairness and removal of bias? Our vendors?&lt;br /&gt;
&lt;br /&gt;
Lots of tough questions.&lt;br /&gt;
&lt;br /&gt;
While the conversation has been going on via various blogs and articles within the last few years, it was given a public face at [http://infotoday.com/il2013/day.asp?day=Monday#session_D105 Internet Librarian 2013] where a panel of 7 (four women, three men) gave personal experiences on the above and then opened up the conversation to the audience. As eye opening and enriching the conversation was, a 45 minute panel was not enough. One thing remains clear: We need to keep the conversation moving forward and start making some radical changes in the way we think, act, and how we need to harness this to start making real changes within librarianship itself.&lt;br /&gt;
&lt;br /&gt;
Topics to include:  Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems,  mentoring, ally support, and more&lt;br /&gt;
&lt;br /&gt;
Those attending should expect: Begin with opening up the conversation of experiences and talking about what is most needed, spending remaining time putting together live, usable solutions to start implementing as well as pushing the conversation forward at local levels&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;
=====All Day=====&lt;br /&gt;
1. Kate Kosturski&lt;br /&gt;
&lt;br /&gt;
2. Valerie Aurora&lt;br /&gt;
&lt;br /&gt;
3. Declan Fleming (I'd be good with a half day too)&lt;br /&gt;
&lt;br /&gt;
4. mx matienzo (likewise ok w/ half day)&lt;br /&gt;
&lt;br /&gt;
5. Ginny Boyer (I'd be good with a half day too)&lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
1. Shaun Ellis&lt;br /&gt;
&lt;br /&gt;
2. Jason Casden&lt;br /&gt;
&lt;br /&gt;
3. Bohyun Kim&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
1. Ayla Stein&lt;br /&gt;
&lt;br /&gt;
2. Heidi Dowding&lt;br /&gt;
&lt;br /&gt;
3. Coral Sheldon-Hess&lt;br /&gt;
&lt;br /&gt;
4. Cory Lown&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===FileAnalyzer: Rapid Development of File Manipulation Tasks===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
* Contact Terry Brady, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The FileAnalyzer (http://georgetown-university-libraries.github.io/File-Analyzer/) is an application designed to solve a number of library automation challenges:&lt;br /&gt;
&lt;br /&gt;
* validating digitized and reformatted files&lt;br /&gt;
* validating vendor statistics for counter compliance&lt;br /&gt;
* preparing collections of digital files for archiving and ingest&lt;br /&gt;
* manipulating ILS import and export files&lt;br /&gt;
&lt;br /&gt;
The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census. After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform. Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.&lt;br /&gt;
&lt;br /&gt;
The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules. As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.&lt;br /&gt;
&lt;br /&gt;
The first half of this session will be targeted to potential users and developers.  The second half of the session will be targeted towards developers who are interested in developing custom rules for the application.&lt;br /&gt;
&lt;br /&gt;
''Session Overview''&lt;br /&gt;
* Overview of the application&lt;br /&gt;
* Running sample file tests/transformations through the application&lt;br /&gt;
* Compiling and building the application&lt;br /&gt;
* Coding a custom file processing task&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;
# Michael Doran&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Collecting social media data with Social Feed Manager===&lt;br /&gt;
'''Half-Day [Morning]'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Dan Chudnov, GW Libraries, dchud (at) gwu.edu&lt;br /&gt;
* Dan Kerchner, GW Libraries, kerchner (at) gwu.edu&lt;br /&gt;
* Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu&lt;br /&gt;
&lt;br /&gt;
Social media data is a popular material for research and a new format for building collections.  What does it take to collect meaningfully from Twitter, Tumblr, YouTube, Weibo, Facebook, and other sites?  We will:&lt;br /&gt;
* Introduce options for collections, including both high- and low-end commercial offerings. Discuss what it means to collect these resources, covering boundaries, policies, and workflows required to develop a social media collection program in your institution.&lt;br /&gt;
* Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them&lt;br /&gt;
* Help you get started using the free [http://gwu-libraries.github.io/social-feed-manager Social Feed Manager] (SFM) app we're developing at GW to create your first collections. We’ll demo its use and demo a clean install (those w/environments can follow along)&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;
# Declan Fleming&lt;br /&gt;
# Esmé Cowles&lt;br /&gt;
# Jason Stirnaman&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Intro to Git ===&lt;br /&gt;
'''&amp;quot;Half-Day [tbd - probably afternoon]&amp;quot;''' &lt;br /&gt;
* Contact: Erin Fahy, Stanford University, efahy at stanford.edu&lt;br /&gt;
* TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu&lt;br /&gt;
&lt;br /&gt;
This session will cover the fundamentals of git by discussing/going through (time allowing):&lt;br /&gt;
* what is a distributed version control system&lt;br /&gt;
* what is git and github&lt;br /&gt;
* initializing a repo on a remote server/github&lt;br /&gt;
* cloning an existing repo&lt;br /&gt;
* creating a branch&lt;br /&gt;
* contributing code to a repo&lt;br /&gt;
* how to handle merge conflicts&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;
# Sam Kome&lt;br /&gt;
# Paula Gray-Overtoom&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
# Michael Doran&lt;br /&gt;
# Caitlin Christian-Lamb&lt;br /&gt;
# [[User:RileyChilds|Riley Childs]]&lt;br /&gt;
# Jim LeFager&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Archival discovery and use ===&lt;br /&gt;
'''Full Day''' &lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Tim Shearer, UNC Chapel Hill, tshearer at email.unc.edu, &lt;br /&gt;
* Will Sexton, Duke, will.sexton at duke.edu&lt;br /&gt;
&lt;br /&gt;
This is a full day pre-conference about archival collections and will cover the intersections of archives, workflows, technologies, discovery, and use.&lt;br /&gt;
&lt;br /&gt;
Morning agenda: focused talks around (but not limited to) issues such as:&lt;br /&gt;
* Crowd-sourcing description to enhance collecitons&lt;br /&gt;
* Linked data and authority&lt;br /&gt;
* Mass digitization and sustainable workflows&lt;br /&gt;
* Digitized objects in context (images and other objects in finding aids)&lt;br /&gt;
* Too many cooks in the kitchen: versioning&lt;br /&gt;
* Global-, intra-, and inter- discovery of archival materials via finding aids &lt;br /&gt;
* and more...&lt;br /&gt;
&lt;br /&gt;
Afternoon agenda:  Focused talks around specific tools followed by general discussion, connections, opportunities, aspirations, and planning.&lt;br /&gt;
&lt;br /&gt;
Tool examples:&lt;br /&gt;
* Archivespace&lt;br /&gt;
* STEADy&lt;br /&gt;
* &amp;quot;RAMP&amp;quot; (Remixing Archival Metadata Project)&lt;br /&gt;
* OpenRefine&lt;br /&gt;
* Aeon&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;
Morning:&lt;br /&gt;
* Julia Bauder&lt;br /&gt;
&lt;br /&gt;
Afternoon:&lt;br /&gt;
* your name&lt;br /&gt;
&lt;br /&gt;
All day:&lt;br /&gt;
&lt;br /&gt;
# Josh Wilson&lt;br /&gt;
# Sam Kome&lt;br /&gt;
# Linda Ballinger&lt;br /&gt;
# Caitlin Christian-Lamb&lt;br /&gt;
# Laurie Lee Moses (seriously hard to decide here!)&lt;br /&gt;
# David Bass&lt;br /&gt;
# John Rees&lt;br /&gt;
# Lynn Eaton&lt;br /&gt;
# Hillel Arnold&lt;br /&gt;
# Susan Ivey&lt;br /&gt;
# Kristen Merryman&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===AV Content Slam===&lt;br /&gt;
'''Half-Day [morning]'''&lt;br /&gt;
Contacts:&lt;br /&gt;
* Kara Van Malssen, kara (at) avpreserve.com&lt;br /&gt;
* Lauren Sorenson, laurens (at) bavc.org&lt;br /&gt;
* Steven Villereal , villereal (at) gmail.com&lt;br /&gt;
A morning BarCamp/unconference for practitioners and coders who work with audiovisual content. The agenda will be attendee-driven, with a focus on sharing, synthesizing, and improving workflow strategies and documentation for software-based approaches to wrangling and providing access to audio and video content.&lt;br /&gt;
Possible topics of discussion might include:&lt;br /&gt;
* Use of format id and characterization/metadata extraction tools for AV&lt;br /&gt;
* Creating and using time-based metadata&lt;br /&gt;
* Managing (moving, fixity checking, etc) massive files (like uncompressed video)&lt;br /&gt;
For a better idea of the topics and concerns that have informed some past AV-themed events, check out the event wikis for [http://wiki.curatecamp.org/index.php/CURATEcamp_AVpres_2013 CURATEcamp AVpres 2013] as well as the [http://wiki.curatecamp.org/index.php/Association_of_Moving_Image_Archivists_%26_Digital_Library_Federation_Hack_Day_2013 AMIA/DLF 2013 Hack Day] .&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;
# A. Soroka&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===OCLC Web Services Hackfest===&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Half-Day&amp;quot; [afternoon]&lt;br /&gt;
&lt;br /&gt;
Contact: Shelley Hostetler, Community Manager, Developer Network hostetls[at]oclc.org&lt;br /&gt;
&lt;br /&gt;
This half-day hackfest will explore some of the OCLC Developer Network web services. We will provide an overview of some of the common topics such as the general REST-based architecture for most services and how to use some new authentication clients. The group can then decide to take a deep dive into a particular API and/or write a client library for the community.&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;
===Obey the Testing Goat!: Test Driven Web Development From The Ground Up===&lt;br /&gt;
'''Half-Day [tbd - probably afternoon]'''&lt;br /&gt;
* Contact [[User:Mredar|Mark Redar]], mredar[at]gmail.com&lt;br /&gt;
&lt;br /&gt;
Test driven development is a proven method for producing better quality code. But I've found it hard to follow a strict TDD methodology when starting new web projects. How do you write that first test when there is no code or web pages created yet.&lt;br /&gt;
&lt;br /&gt;
In this session, we will follow the excellent book [http://shop.oreilly.com/product/0636920029533.do &amp;quot;Test-Driven Web Development with Python&amp;quot;] to create a simple web site in Django following TDD from the first character typed. Come ready to code and test. No prior knowledge of python or Django required.&lt;br /&gt;
&lt;br /&gt;
By the end of this session, you should be able to  [http://www.obeythetestinggoat.com/ &amp;quot;Obey the Testing Goat&amp;quot;] from the start to finish for your next project.&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;
# Charlie Morris (NCSU)&lt;br /&gt;
# Jason Stirnaman&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
# Scott Hanrath&lt;br /&gt;
# Mike Beccaria&lt;br /&gt;
# Sean Aery&lt;br /&gt;
# Carolina Garcia&lt;br /&gt;
# Heidi Frank&lt;br /&gt;
# Chung Kang&lt;br /&gt;
# Nabil Kashyap&lt;br /&gt;
# Justin Simpson&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Summon Hackfest ===&lt;br /&gt;
&lt;br /&gt;
Presenter: Eddie Newwirth and presenters from Summon libraries&lt;br /&gt;
Contact: Scott Schuetze (first DOT last @ serialssolutions. com)&lt;br /&gt;
&lt;br /&gt;
The Summon Hackfest (10:30am-12pm) will be a great opportunity for libraries using the Summon service to talk about improving discovery of resources, share their creative customizations and code, and exchange ideas about ways they can leverage the Summon API to better meet the needs of their users.&lt;br /&gt;
 &lt;br /&gt;
The Summon Hackfest is open to all libraries currently using ProQuest discovery and management services (Intota, Summon, Ulrich’s or the 360 suite of services), whether they are attending Code4Lib or are just in the area.&lt;br /&gt;
 &lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
[[:Category:Code4Lib2014]]&lt;/div&gt;</summary>
		<author><name>ChristopherHallberg</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&amp;diff=40756</id>
		<title>2014 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&amp;diff=40756"/>
				<updated>2014-03-20T17:17:31Z</updated>
		
		<summary type="html">&lt;p&gt;ChristopherHallberg: /* RailsBridge: Intro to programming in Ruby on Rails */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= PROPOSALS ARE CLOSED : PLEASE DO NOT ADD NEW PRECONFERENCES TO THIS PAGE =&lt;br /&gt;
&lt;br /&gt;
Proposals were accepted through December 6th, 2013.&lt;br /&gt;
&lt;br /&gt;
It would be really, super duper helpful if folks who think they might want to attend a pre-conference could indicate interest by adding your name to a session below. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Note===&lt;br /&gt;
Attendance at a pre-conference will require a small fee ''due at the time of conference registration&amp;quot;.&lt;br /&gt;
 &lt;br /&gt;
Although this was specified in the email announcements relating to pre-conferences, it was not added to this page until December 2nd.  I (Adam C.) apologize for the omission and I hope this will not cause any &amp;quot;sticker shock.&amp;quot;  Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.&lt;br /&gt;
&lt;br /&gt;
Please put your pre-conference on the list in the following format:&lt;br /&gt;
&lt;br /&gt;
=Code4Lib 2014 Pre-Conference Proposals=&lt;br /&gt;
&lt;br /&gt;
===Drupal4lib Sub-con Barcamp===&lt;br /&gt;
=====Full Day=====&lt;br /&gt;
&lt;br /&gt;
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.&lt;br /&gt;
&lt;br /&gt;
This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).&lt;br /&gt;
&lt;br /&gt;
[[resources to help you learn drupal]]&lt;br /&gt;
&lt;br /&gt;
====Interested in Attending:====&lt;br /&gt;
&lt;br /&gt;
=====All Day=====&lt;br /&gt;
&lt;br /&gt;
* Renna Tuten &lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
&lt;br /&gt;
* Kevin Reiss&lt;br /&gt;
* Charlie Morris (NCSU) - glad to see this again this year!&lt;br /&gt;
* Paula Gray-Overtoom&lt;br /&gt;
* Laurie Lee Moses&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Open Refine Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day[Morning]&amp;quot;'''&lt;br /&gt;
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com&lt;br /&gt;
&lt;br /&gt;
[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control&lt;br /&gt;
&lt;br /&gt;
The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. &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;
&amp;lt;ol&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Adam Constabaris&lt;br /&gt;
&amp;lt;li&amp;gt;Jason Stirnaman&lt;br /&gt;
&amp;lt;li&amp;gt;Joshua Gomez&lt;br /&gt;
&amp;lt;li&amp;gt;Sam Kome&lt;br /&gt;
&amp;lt;li&amp;gt;Mike Beccaria&lt;br /&gt;
&amp;lt;li&amp;gt;Angela Zoss&lt;br /&gt;
&amp;lt;li&amp;gt;A. Soroka&lt;br /&gt;
&amp;lt;li&amp;gt; Matt Zumwalt&lt;br /&gt;
&amp;lt;li&amp;gt;Jim LeFager&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Responsive Design Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day [Afternoon]&amp;quot;''' &lt;br /&gt;
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com&lt;br /&gt;
* Contact David Ward, University of Illinois, dh-ward@illinois.edu&lt;br /&gt;
&lt;br /&gt;
This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. &lt;br /&gt;
&lt;br /&gt;
Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.&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;
=== Intro to Blacklight ===&lt;br /&gt;
'''&amp;quot;Half-Day [Morning]&amp;quot;''' &lt;br /&gt;
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
* TA: Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
This session will be walk-through of the architecture of Blacklight, the community, and an introduction to building a Blacklight-based application. Each participant will have the opportunity to build a simple Blacklight application, and make basic customizations, while using a test-driven approach.&lt;br /&gt;
&lt;br /&gt;
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.&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;
# Megan Kudzia&lt;br /&gt;
# Bret Davidson&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Cory Lown&lt;br /&gt;
# Emily Daly&lt;br /&gt;
# Angela Zoss&lt;br /&gt;
# Sean Aery&lt;br /&gt;
# Francis Kayiwa&lt;br /&gt;
# Heidi Frank&lt;br /&gt;
# Junior Tidal&lt;br /&gt;
# Ian Chan&lt;br /&gt;
# Ted Lawless&lt;br /&gt;
# David Lacy&lt;br /&gt;
# Erik Hatcher&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Blacklight Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day [Afternoon]&amp;quot;''' &lt;br /&gt;
* Contact Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
&lt;br /&gt;
This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.&lt;br /&gt;
&lt;br /&gt;
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).&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;
# Shaun Ellis&lt;br /&gt;
# Kevin Reiss&lt;br /&gt;
# Megan Kudzia&lt;br /&gt;
# Erik Hatcher&lt;br /&gt;
# Emily Daly&lt;br /&gt;
# Laurie Lee Moses&lt;br /&gt;
# Francis Kayiwa&lt;br /&gt;
# Ted Lawless&lt;br /&gt;
# David Lacy&lt;br /&gt;
&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 Justin Coyne, Data Curation Experts, justin@curationexperts.com&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! 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 Blacklight and Hydra.&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;
1. Ayla Stein&lt;br /&gt;
&lt;br /&gt;
2. Heidi Dowding&lt;br /&gt;
&lt;br /&gt;
3. Caitlin Christian-Lamb&lt;br /&gt;
&lt;br /&gt;
4. Scott Bacon&lt;br /&gt;
&lt;br /&gt;
5. [[User:RileyChilds | Riley Childs]]&lt;br /&gt;
&lt;br /&gt;
6. Carolina Garcia&lt;br /&gt;
&lt;br /&gt;
7. Chris Hallberg&lt;br /&gt;
&lt;br /&gt;
7. David Uspal&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===&lt;br /&gt;
'''Full-Day'''&lt;br /&gt;
&lt;br /&gt;
Contact: &lt;br /&gt;
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com&lt;br /&gt;
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu&lt;br /&gt;
&lt;br /&gt;
This will be a full day session on project management.  We'll cover&lt;br /&gt;
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment&lt;br /&gt;
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets&lt;br /&gt;
* '''Executing the Project''' -- status meeting, status reports, issue management&lt;br /&gt;
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product&lt;br /&gt;
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.&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;
# Robin Dean&lt;br /&gt;
# Erin White&lt;br /&gt;
# Andrew Darby&lt;br /&gt;
# Sam Kome&lt;br /&gt;
# Ryan Scherle&lt;br /&gt;
# Will Shaw&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
# Cynthia &amp;quot;Arty&amp;quot; Ng&lt;br /&gt;
# Laurie Lee Moses (if I don't do the Hackfest for Blacklight)&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
# Bohyun Kim (Afternoon)&lt;br /&gt;
# Mike Hagedon&lt;br /&gt;
# Chris Hallberg&lt;br /&gt;
#Susan Ivey &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Fail4Lib 2014===&lt;br /&gt;
'''Half Day [TBD, probably afternoon]'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Andreas Orphanides, akorphan (at) ncsu.edu&lt;br /&gt;
* Jason Casden, jmcasden (at) ncsu.edu&lt;br /&gt;
&lt;br /&gt;
The task of design (and the work that we do as library coders) is intimately tied to failure. Failures, both big and small, motivate us to create and improve. Failures are also occasionally the result of our work. Understanding and embracing failure, encouraging enlightened risk-taking, and seeking out opportunities to fail and learn are essential to success in our field. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be feared.&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
&lt;br /&gt;
* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?&lt;br /&gt;
* Confessionals, for those willing to share. Talk about your own experiences with rough starts, labor pains, and doomed projects in your own work: What can we learn from our own (and each others') failures?&lt;br /&gt;
* Group therapy. Let's talk about how to deal with risk management, failed projects, experimental endeavors, and more: How can we make ourselves, our colleagues, and our organizations more fault tolerant? How do we make sure we fail as productively as possible?&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;
#Bret Davidson&lt;br /&gt;
#Mike Graves&lt;br /&gt;
#Jason Stirnaman&lt;br /&gt;
#Julia Bauder&lt;br /&gt;
#Linda Ballinger&lt;br /&gt;
#Scott Hanrath&lt;br /&gt;
#Caitlin Christian-Lamb&lt;br /&gt;
#Ian Walls&lt;br /&gt;
#Scott Bacon &lt;br /&gt;
#mx matienzo&lt;br /&gt;
#Chris Sharp&lt;br /&gt;
#Junior Tidal&lt;br /&gt;
#Julie Rudder&lt;br /&gt;
#David Uspal&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===CLLAM @ code4lib===&lt;br /&gt;
'''(Computational Linguistics for Libraries, Archives and Museums)'''&lt;br /&gt;
&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Douglas W. Oard (primary), oard (at) umd.edu &lt;br /&gt;
* Corey Harper, corey (dot) harper (at) nyu.edu&lt;br /&gt;
* Robert Sanderson, azaroth42 (at) gmail.com &lt;br /&gt;
* Robert Warren, rwarren (at) math.carleton.ca&lt;br /&gt;
&lt;br /&gt;
We will hack at the intersection of diverse content from Libraries, Archives and Museums and bleeding edge tools from computational linguistics for slicing and dicing that content. Did you just acquire the email archives of a startup company? Maybe you can automatically build an org chart. Have you got metadata in a slew of languages? Perhaps you can search it all using one query. Is name authority control for e-resources getting too costly? Let’s see if entity linking techniques can help. These are just a few teasers. &lt;br /&gt;
&lt;br /&gt;
There’ll be plenty of content and tools supplied, but please bring your own [data] too -- you’ll hack with it in new ways throughout the day. We’ll get started with some lightning talks on what we’ve brought,then we’ll break up into groups to experiment and work on the ideas that appeal. Three guaranteed outcomes: you’ll walk away with new ideas, new tools, and new people you’ll have met.&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;
# Devon Smith&lt;br /&gt;
# Kevin S. Clarke&lt;br /&gt;
# Jason Stirnaman&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Carolina Garcia&lt;br /&gt;
# Tom Burton-West&lt;br /&gt;
# Dan Scott&lt;br /&gt;
# Devin Higgins&lt;br /&gt;
# Mark Breedlove&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== GeoHydra: Managing geospatial content ===&lt;br /&gt;
&lt;br /&gt;
'''Half-day [Afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Contact: Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Moderator: Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,&lt;br /&gt;
etc., all of which you want to integrate into your digital repository? In this&lt;br /&gt;
workshop, we will discuss how Hydra can provide discovery, delivery, and&lt;br /&gt;
management services for geospatial assets, as well as solicit questions about&lt;br /&gt;
your own GIS projects. We aim to help answer the following questions you might have about putting geospatial data into your Hydra-based digital library:&lt;br /&gt;
&lt;br /&gt;
* What are the types of geospatial data?&lt;br /&gt;
* How to dive into Hydra?&lt;br /&gt;
* How to model geospatial holdings with Hydra?&lt;br /&gt;
* How to discover and view geospatial data?&lt;br /&gt;
* How to build a geospatial data infrastructure?&lt;br /&gt;
* What are common approaches and problems?&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;
# Esmé Cowles&lt;br /&gt;
# David Drexler&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Technology, Librarianship, and Gender: Moving the conversation forward===&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]&lt;br /&gt;
&lt;br /&gt;
'''Description'''&lt;br /&gt;
&lt;br /&gt;
Librarianship is largely made up of women, yet women are significantly underrepresented in tech positions, on any level, within libraries themselves. Why? What are we doing to encourage women to become more involved in STEM within librarianship? What kind of message are we sending when library technology keynotes remain almost resolutely male? How are we changing the face of technology, not only within libraries, but with the field itself? How are we training our staff and colleagues in the areas of fairness and removal of bias? Our vendors?&lt;br /&gt;
&lt;br /&gt;
Lots of tough questions.&lt;br /&gt;
&lt;br /&gt;
While the conversation has been going on via various blogs and articles within the last few years, it was given a public face at [http://infotoday.com/il2013/day.asp?day=Monday#session_D105 Internet Librarian 2013] where a panel of 7 (four women, three men) gave personal experiences on the above and then opened up the conversation to the audience. As eye opening and enriching the conversation was, a 45 minute panel was not enough. One thing remains clear: We need to keep the conversation moving forward and start making some radical changes in the way we think, act, and how we need to harness this to start making real changes within librarianship itself.&lt;br /&gt;
&lt;br /&gt;
Topics to include:  Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems,  mentoring, ally support, and more&lt;br /&gt;
&lt;br /&gt;
Those attending should expect: Begin with opening up the conversation of experiences and talking about what is most needed, spending remaining time putting together live, usable solutions to start implementing as well as pushing the conversation forward at local levels&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;
=====All Day=====&lt;br /&gt;
1. Kate Kosturski&lt;br /&gt;
&lt;br /&gt;
2. Valerie Aurora&lt;br /&gt;
&lt;br /&gt;
3. Declan Fleming (I'd be good with a half day too)&lt;br /&gt;
&lt;br /&gt;
4. mx matienzo (likewise ok w/ half day)&lt;br /&gt;
&lt;br /&gt;
5. Ginny Boyer (I'd be good with a half day too)&lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
1. Shaun Ellis&lt;br /&gt;
&lt;br /&gt;
2. Jason Casden&lt;br /&gt;
&lt;br /&gt;
3. Bohyun Kim&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
1. Ayla Stein&lt;br /&gt;
&lt;br /&gt;
2. Heidi Dowding&lt;br /&gt;
&lt;br /&gt;
3. Coral Sheldon-Hess&lt;br /&gt;
&lt;br /&gt;
4. Cory Lown&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===FileAnalyzer: Rapid Development of File Manipulation Tasks===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
* Contact Terry Brady, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The FileAnalyzer (http://georgetown-university-libraries.github.io/File-Analyzer/) is an application designed to solve a number of library automation challenges:&lt;br /&gt;
&lt;br /&gt;
* validating digitized and reformatted files&lt;br /&gt;
* validating vendor statistics for counter compliance&lt;br /&gt;
* preparing collections of digital files for archiving and ingest&lt;br /&gt;
* manipulating ILS import and export files&lt;br /&gt;
&lt;br /&gt;
The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census. After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform. Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.&lt;br /&gt;
&lt;br /&gt;
The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules. As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.&lt;br /&gt;
&lt;br /&gt;
The first half of this session will be targeted to potential users and developers.  The second half of the session will be targeted towards developers who are interested in developing custom rules for the application.&lt;br /&gt;
&lt;br /&gt;
''Session Overview''&lt;br /&gt;
* Overview of the application&lt;br /&gt;
* Running sample file tests/transformations through the application&lt;br /&gt;
* Compiling and building the application&lt;br /&gt;
* Coding a custom file processing task&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;
# Michael Doran&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Collecting social media data with Social Feed Manager===&lt;br /&gt;
'''Half-Day [Morning]'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Dan Chudnov, GW Libraries, dchud (at) gwu.edu&lt;br /&gt;
* Dan Kerchner, GW Libraries, kerchner (at) gwu.edu&lt;br /&gt;
* Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu&lt;br /&gt;
&lt;br /&gt;
Social media data is a popular material for research and a new format for building collections.  What does it take to collect meaningfully from Twitter, Tumblr, YouTube, Weibo, Facebook, and other sites?  We will:&lt;br /&gt;
* Introduce options for collections, including both high- and low-end commercial offerings. Discuss what it means to collect these resources, covering boundaries, policies, and workflows required to develop a social media collection program in your institution.&lt;br /&gt;
* Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them&lt;br /&gt;
* Help you get started using the free [http://gwu-libraries.github.io/social-feed-manager Social Feed Manager] (SFM) app we're developing at GW to create your first collections. We’ll demo its use and demo a clean install (those w/environments can follow along)&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;
# Declan Fleming&lt;br /&gt;
# Esmé Cowles&lt;br /&gt;
# Jason Stirnaman&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Intro to Git ===&lt;br /&gt;
'''&amp;quot;Half-Day [tbd - probably afternoon]&amp;quot;''' &lt;br /&gt;
* Contact: Erin Fahy, Stanford University, efahy at stanford.edu&lt;br /&gt;
* TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu&lt;br /&gt;
&lt;br /&gt;
This session will cover the fundamentals of git by discussing/going through (time allowing):&lt;br /&gt;
* what is a distributed version control system&lt;br /&gt;
* what is git and github&lt;br /&gt;
* initializing a repo on a remote server/github&lt;br /&gt;
* cloning an existing repo&lt;br /&gt;
* creating a branch&lt;br /&gt;
* contributing code to a repo&lt;br /&gt;
* how to handle merge conflicts&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;
# Sam Kome&lt;br /&gt;
# Paula Gray-Overtoom&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
# Michael Doran&lt;br /&gt;
# Caitlin Christian-Lamb&lt;br /&gt;
# [[User:RileyChilds|Riley Childs]]&lt;br /&gt;
# Jim LeFager&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Archival discovery and use ===&lt;br /&gt;
'''Full Day''' &lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Tim Shearer, UNC Chapel Hill, tshearer at email.unc.edu, &lt;br /&gt;
* Will Sexton, Duke, will.sexton at duke.edu&lt;br /&gt;
&lt;br /&gt;
This is a full day pre-conference about archival collections and will cover the intersections of archives, workflows, technologies, discovery, and use.&lt;br /&gt;
&lt;br /&gt;
Morning agenda: focused talks around (but not limited to) issues such as:&lt;br /&gt;
* Crowd-sourcing description to enhance collecitons&lt;br /&gt;
* Linked data and authority&lt;br /&gt;
* Mass digitization and sustainable workflows&lt;br /&gt;
* Digitized objects in context (images and other objects in finding aids)&lt;br /&gt;
* Too many cooks in the kitchen: versioning&lt;br /&gt;
* Global-, intra-, and inter- discovery of archival materials via finding aids &lt;br /&gt;
* and more...&lt;br /&gt;
&lt;br /&gt;
Afternoon agenda:  Focused talks around specific tools followed by general discussion, connections, opportunities, aspirations, and planning.&lt;br /&gt;
&lt;br /&gt;
Tool examples:&lt;br /&gt;
* Archivespace&lt;br /&gt;
* STEADy&lt;br /&gt;
* &amp;quot;RAMP&amp;quot; (Remixing Archival Metadata Project)&lt;br /&gt;
* OpenRefine&lt;br /&gt;
* Aeon&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;
Morning:&lt;br /&gt;
* Julia Bauder&lt;br /&gt;
&lt;br /&gt;
Afternoon:&lt;br /&gt;
* your name&lt;br /&gt;
&lt;br /&gt;
All day:&lt;br /&gt;
&lt;br /&gt;
# Josh Wilson&lt;br /&gt;
# Sam Kome&lt;br /&gt;
# Linda Ballinger&lt;br /&gt;
# Caitlin Christian-Lamb&lt;br /&gt;
# Laurie Lee Moses (seriously hard to decide here!)&lt;br /&gt;
# David Bass&lt;br /&gt;
# John Rees&lt;br /&gt;
# Lynn Eaton&lt;br /&gt;
# Hillel Arnold&lt;br /&gt;
# Susan Ivey&lt;br /&gt;
# Kristen Merryman&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===AV Content Slam===&lt;br /&gt;
'''Half-Day [morning]'''&lt;br /&gt;
Contacts:&lt;br /&gt;
* Kara Van Malssen, kara (at) avpreserve.com&lt;br /&gt;
* Lauren Sorenson, laurens (at) bavc.org&lt;br /&gt;
* Steven Villereal , villereal (at) gmail.com&lt;br /&gt;
A morning BarCamp/unconference for practitioners and coders who work with audiovisual content. The agenda will be attendee-driven, with a focus on sharing, synthesizing, and improving workflow strategies and documentation for software-based approaches to wrangling and providing access to audio and video content.&lt;br /&gt;
Possible topics of discussion might include:&lt;br /&gt;
* Use of format id and characterization/metadata extraction tools for AV&lt;br /&gt;
* Creating and using time-based metadata&lt;br /&gt;
* Managing (moving, fixity checking, etc) massive files (like uncompressed video)&lt;br /&gt;
For a better idea of the topics and concerns that have informed some past AV-themed events, check out the event wikis for [http://wiki.curatecamp.org/index.php/CURATEcamp_AVpres_2013 CURATEcamp AVpres 2013] as well as the [http://wiki.curatecamp.org/index.php/Association_of_Moving_Image_Archivists_%26_Digital_Library_Federation_Hack_Day_2013 AMIA/DLF 2013 Hack Day] .&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;
# A. Soroka&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===OCLC Web Services Hackfest===&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Half-Day&amp;quot; [afternoon]&lt;br /&gt;
&lt;br /&gt;
Contact: Shelley Hostetler, Community Manager, Developer Network hostetls[at]oclc.org&lt;br /&gt;
&lt;br /&gt;
This half-day hackfest will explore some of the OCLC Developer Network web services. We will provide an overview of some of the common topics such as the general REST-based architecture for most services and how to use some new authentication clients. The group can then decide to take a deep dive into a particular API and/or write a client library for the community.&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;
===Obey the Testing Goat!: Test Driven Web Development From The Ground Up===&lt;br /&gt;
'''Half-Day [tbd - probably afternoon]'''&lt;br /&gt;
* Contact [[User:Mredar|Mark Redar]], mredar[at]gmail.com&lt;br /&gt;
&lt;br /&gt;
Test driven development is a proven method for producing better quality code. But I've found it hard to follow a strict TDD methodology when starting new web projects. How do you write that first test when there is no code or web pages created yet.&lt;br /&gt;
&lt;br /&gt;
In this session, we will follow the excellent book [http://shop.oreilly.com/product/0636920029533.do &amp;quot;Test-Driven Web Development with Python&amp;quot;] to create a simple web site in Django following TDD from the first character typed. Come ready to code and test. No prior knowledge of python or Django required.&lt;br /&gt;
&lt;br /&gt;
By the end of this session, you should be able to  [http://www.obeythetestinggoat.com/ &amp;quot;Obey the Testing Goat&amp;quot;] from the start to finish for your next project.&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;
# Charlie Morris (NCSU)&lt;br /&gt;
# Jason Stirnaman&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
# Scott Hanrath&lt;br /&gt;
# Mike Beccaria&lt;br /&gt;
# Sean Aery&lt;br /&gt;
# Carolina Garcia&lt;br /&gt;
# Heidi Frank&lt;br /&gt;
# Chung Kang&lt;br /&gt;
# Nabil Kashyap&lt;br /&gt;
# Justin Simpson&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Summon Hackfest ===&lt;br /&gt;
&lt;br /&gt;
Presenter: Eddie Newwirth and presenters from Summon libraries&lt;br /&gt;
Contact: Scott Schuetze (first DOT last @ serialssolutions. com)&lt;br /&gt;
&lt;br /&gt;
The Summon Hackfest (10:30am-12pm) will be a great opportunity for libraries using the Summon service to talk about improving discovery of resources, share their creative customizations and code, and exchange ideas about ways they can leverage the Summon API to better meet the needs of their users.&lt;br /&gt;
 &lt;br /&gt;
The Summon Hackfest is open to all libraries currently using ProQuest discovery and management services (Intota, Summon, Ulrich’s or the 360 suite of services), whether they are attending Code4Lib or are just in the area.&lt;br /&gt;
 &lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
[[:Category:Code4Lib2014]]&lt;/div&gt;</summary>
		<author><name>ChristopherHallberg</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&amp;diff=40679</id>
		<title>2014 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&amp;diff=40679"/>
				<updated>2014-03-17T18:39:23Z</updated>
		
		<summary type="html">&lt;p&gt;ChristopherHallberg: /* Managing Projects: Or I'm in charge, now what? (aka PM4Lib) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= PROPOSALS ARE CLOSED : PLEASE DO NOT ADD NEW PRECONFERENCES TO THIS PAGE =&lt;br /&gt;
&lt;br /&gt;
Proposals were accepted through December 6th, 2013.&lt;br /&gt;
&lt;br /&gt;
It would be really, super duper helpful if folks who think they might want to attend a pre-conference could indicate interest by adding your name to a session below. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Note===&lt;br /&gt;
Attendance at a pre-conference will require a small fee ''due at the time of conference registration&amp;quot;.&lt;br /&gt;
 &lt;br /&gt;
Although this was specified in the email announcements relating to pre-conferences, it was not added to this page until December 2nd.  I (Adam C.) apologize for the omission and I hope this will not cause any &amp;quot;sticker shock.&amp;quot;  Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.&lt;br /&gt;
&lt;br /&gt;
Please put your pre-conference on the list in the following format:&lt;br /&gt;
&lt;br /&gt;
=Code4Lib 2014 Pre-Conference Proposals=&lt;br /&gt;
&lt;br /&gt;
===Drupal4lib Sub-con Barcamp===&lt;br /&gt;
=====Full Day=====&lt;br /&gt;
&lt;br /&gt;
* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.&lt;br /&gt;
&lt;br /&gt;
This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).&lt;br /&gt;
&lt;br /&gt;
[[resources to help you learn drupal]]&lt;br /&gt;
&lt;br /&gt;
====Interested in Attending:====&lt;br /&gt;
&lt;br /&gt;
=====All Day=====&lt;br /&gt;
&lt;br /&gt;
* Renna Tuten &lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
&lt;br /&gt;
* Kevin Reiss&lt;br /&gt;
* Charlie Morris (NCSU) - glad to see this again this year!&lt;br /&gt;
* Paula Gray-Overtoom&lt;br /&gt;
* Laurie Lee Moses&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Open Refine Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day[Morning]&amp;quot;'''&lt;br /&gt;
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com&lt;br /&gt;
&lt;br /&gt;
[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control&lt;br /&gt;
&lt;br /&gt;
The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. &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;
&amp;lt;ol&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Adam Constabaris&lt;br /&gt;
&amp;lt;li&amp;gt;Jason Stirnaman&lt;br /&gt;
&amp;lt;li&amp;gt;Joshua Gomez&lt;br /&gt;
&amp;lt;li&amp;gt;Sam Kome&lt;br /&gt;
&amp;lt;li&amp;gt;Mike Beccaria&lt;br /&gt;
&amp;lt;li&amp;gt;Angela Zoss&lt;br /&gt;
&amp;lt;li&amp;gt;A. Soroka&lt;br /&gt;
&amp;lt;li&amp;gt; Matt Zumwalt&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Responsive Design Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day [Afternoon]&amp;quot;''' &lt;br /&gt;
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com&lt;br /&gt;
* Contact David Ward, University of Illinois, dh-ward@illinois.edu&lt;br /&gt;
&lt;br /&gt;
This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. &lt;br /&gt;
&lt;br /&gt;
Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.&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;
=== Intro to Blacklight ===&lt;br /&gt;
'''&amp;quot;Half-Day [Morning]&amp;quot;''' &lt;br /&gt;
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
* TA: Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
This session will be walk-through of the architecture of Blacklight, the community, and an introduction to building a Blacklight-based application. Each participant will have the opportunity to build a simple Blacklight application, and make basic customizations, while using a test-driven approach.&lt;br /&gt;
&lt;br /&gt;
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.&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;
# Megan Kudzia&lt;br /&gt;
# Bret Davidson&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Cory Lown&lt;br /&gt;
# Emily Daly&lt;br /&gt;
# Angela Zoss&lt;br /&gt;
# Sean Aery&lt;br /&gt;
# Francis Kayiwa&lt;br /&gt;
# Heidi Frank&lt;br /&gt;
# Junior Tidal&lt;br /&gt;
# Ian Chan&lt;br /&gt;
# Ted Lawless&lt;br /&gt;
# David Lacy&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Blacklight Hackfest===&lt;br /&gt;
'''&amp;quot;Half-Day [Afternoon]&amp;quot;''' &lt;br /&gt;
* Contact Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
&lt;br /&gt;
This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.&lt;br /&gt;
&lt;br /&gt;
For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).&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;
# Shaun Ellis&lt;br /&gt;
# Kevin Reiss&lt;br /&gt;
# Megan Kudzia&lt;br /&gt;
# Erik Hatcher&lt;br /&gt;
# Emily Daly&lt;br /&gt;
# Laurie Lee Moses&lt;br /&gt;
# Francis Kayiwa&lt;br /&gt;
# Ted Lawless&lt;br /&gt;
# David Lacy&lt;br /&gt;
&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 Justin Coyne, Data Curation Experts, justin@curationexperts.com&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! 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 Blacklight and Hydra.&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;
1. Ayla Stein&lt;br /&gt;
&lt;br /&gt;
2. Heidi Dowding&lt;br /&gt;
&lt;br /&gt;
3. Caitlin Christian-Lamb&lt;br /&gt;
&lt;br /&gt;
4. Scott Bacon&lt;br /&gt;
&lt;br /&gt;
5. [[User:RileyChilds | Riley Childs]]&lt;br /&gt;
&lt;br /&gt;
6. Carolina Garcia&lt;br /&gt;
&lt;br /&gt;
7. David Uspal&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===&lt;br /&gt;
'''Full-Day'''&lt;br /&gt;
&lt;br /&gt;
Contact: &lt;br /&gt;
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com&lt;br /&gt;
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu&lt;br /&gt;
&lt;br /&gt;
This will be a full day session on project management.  We'll cover&lt;br /&gt;
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment&lt;br /&gt;
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets&lt;br /&gt;
* '''Executing the Project''' -- status meeting, status reports, issue management&lt;br /&gt;
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product&lt;br /&gt;
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.&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;
# Robin Dean&lt;br /&gt;
# Erin White&lt;br /&gt;
# Andrew Darby&lt;br /&gt;
# Sam Kome&lt;br /&gt;
# Ryan Scherle&lt;br /&gt;
# Will Shaw&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
# Cynthia &amp;quot;Arty&amp;quot; Ng&lt;br /&gt;
# Laurie Lee Moses (if I don't do the Hackfest for Blacklight)&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
# Bohyun Kim (Afternoon)&lt;br /&gt;
# Mike Hagedon&lt;br /&gt;
# Chris Hallberg&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Fail4Lib 2014===&lt;br /&gt;
'''Half Day [TBD, probably afternoon]'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Andreas Orphanides, akorphan (at) ncsu.edu&lt;br /&gt;
* Jason Casden, jmcasden (at) ncsu.edu&lt;br /&gt;
&lt;br /&gt;
The task of design (and the work that we do as library coders) is intimately tied to failure. Failures, both big and small, motivate us to create and improve. Failures are also occasionally the result of our work. Understanding and embracing failure, encouraging enlightened risk-taking, and seeking out opportunities to fail and learn are essential to success in our field. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be feared.&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
&lt;br /&gt;
* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?&lt;br /&gt;
* Confessionals, for those willing to share. Talk about your own experiences with rough starts, labor pains, and doomed projects in your own work: What can we learn from our own (and each others') failures?&lt;br /&gt;
* Group therapy. Let's talk about how to deal with risk management, failed projects, experimental endeavors, and more: How can we make ourselves, our colleagues, and our organizations more fault tolerant? How do we make sure we fail as productively as possible?&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;
#Bret Davidson&lt;br /&gt;
#Mike Graves&lt;br /&gt;
#Jason Stirnaman&lt;br /&gt;
#Julia Bauder&lt;br /&gt;
#Linda Ballinger&lt;br /&gt;
#Scott Hanrath&lt;br /&gt;
#Caitlin Christian-Lamb&lt;br /&gt;
#Ian Walls&lt;br /&gt;
#Scott Bacon &lt;br /&gt;
#mx matienzo&lt;br /&gt;
#Chris Sharp&lt;br /&gt;
#Junior Tidal&lt;br /&gt;
#Julie Rudder&lt;br /&gt;
#David Uspal&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===CLLAM @ code4lib===&lt;br /&gt;
'''(Computational Linguistics for Libraries, Archives and Museums)'''&lt;br /&gt;
&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Douglas W. Oard (primary), oard (at) umd.edu &lt;br /&gt;
* Corey Harper, corey (dot) harper (at) nyu.edu&lt;br /&gt;
* Robert Sanderson, azaroth42 (at) gmail.com &lt;br /&gt;
* Robert Warren, rwarren (at) math.carleton.ca&lt;br /&gt;
&lt;br /&gt;
We will hack at the intersection of diverse content from Libraries, Archives and Museums and bleeding edge tools from computational linguistics for slicing and dicing that content. Did you just acquire the email archives of a startup company? Maybe you can automatically build an org chart. Have you got metadata in a slew of languages? Perhaps you can search it all using one query. Is name authority control for e-resources getting too costly? Let’s see if entity linking techniques can help. These are just a few teasers. &lt;br /&gt;
&lt;br /&gt;
There’ll be plenty of content and tools supplied, but please bring your own [data] too -- you’ll hack with it in new ways throughout the day. We’ll get started with some lightning talks on what we’ve brought,then we’ll break up into groups to experiment and work on the ideas that appeal. Three guaranteed outcomes: you’ll walk away with new ideas, new tools, and new people you’ll have met.&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;
# Devon Smith&lt;br /&gt;
# Kevin S. Clarke&lt;br /&gt;
# Jason Stirnaman&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Carolina Garcia&lt;br /&gt;
# Tom Burton-West&lt;br /&gt;
# Dan Scott&lt;br /&gt;
# Devin Higgins&lt;br /&gt;
# Mark Breedlove&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== GeoHydra: Managing geospatial content ===&lt;br /&gt;
&lt;br /&gt;
'''Half-day [Afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Contact: Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Moderator: Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,&lt;br /&gt;
etc., all of which you want to integrate into your digital repository? In this&lt;br /&gt;
workshop, we will discuss how Hydra can provide discovery, delivery, and&lt;br /&gt;
management services for geospatial assets, as well as solicit questions about&lt;br /&gt;
your own GIS projects. We aim to help answer the following questions you might have about putting geospatial data into your Hydra-based digital library:&lt;br /&gt;
&lt;br /&gt;
* What are the types of geospatial data?&lt;br /&gt;
* How to dive into Hydra?&lt;br /&gt;
* How to model geospatial holdings with Hydra?&lt;br /&gt;
* How to discover and view geospatial data?&lt;br /&gt;
* How to build a geospatial data infrastructure?&lt;br /&gt;
* What are common approaches and problems?&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;
# Esmé Cowles&lt;br /&gt;
# David Drexler&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Technology, Librarianship, and Gender: Moving the conversation forward===&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]&lt;br /&gt;
&lt;br /&gt;
'''Description'''&lt;br /&gt;
&lt;br /&gt;
Librarianship is largely made up of women, yet women are significantly underrepresented in tech positions, on any level, within libraries themselves. Why? What are we doing to encourage women to become more involved in STEM within librarianship? What kind of message are we sending when library technology keynotes remain almost resolutely male? How are we changing the face of technology, not only within libraries, but with the field itself? How are we training our staff and colleagues in the areas of fairness and removal of bias? Our vendors?&lt;br /&gt;
&lt;br /&gt;
Lots of tough questions.&lt;br /&gt;
&lt;br /&gt;
While the conversation has been going on via various blogs and articles within the last few years, it was given a public face at [http://infotoday.com/il2013/day.asp?day=Monday#session_D105 Internet Librarian 2013] where a panel of 7 (four women, three men) gave personal experiences on the above and then opened up the conversation to the audience. As eye opening and enriching the conversation was, a 45 minute panel was not enough. One thing remains clear: We need to keep the conversation moving forward and start making some radical changes in the way we think, act, and how we need to harness this to start making real changes within librarianship itself.&lt;br /&gt;
&lt;br /&gt;
Topics to include:  Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems,  mentoring, ally support, and more&lt;br /&gt;
&lt;br /&gt;
Those attending should expect: Begin with opening up the conversation of experiences and talking about what is most needed, spending remaining time putting together live, usable solutions to start implementing as well as pushing the conversation forward at local levels&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;
=====All Day=====&lt;br /&gt;
1. Kate Kosturski&lt;br /&gt;
&lt;br /&gt;
2. Valerie Aurora&lt;br /&gt;
&lt;br /&gt;
3. Declan Fleming (I'd be good with a half day too)&lt;br /&gt;
&lt;br /&gt;
4. mx matienzo (likewise ok w/ half day)&lt;br /&gt;
&lt;br /&gt;
5. Ginny Boyer (I'd be good with a half day too)&lt;br /&gt;
&lt;br /&gt;
=====Morning=====&lt;br /&gt;
1. Shaun Ellis&lt;br /&gt;
&lt;br /&gt;
2. Jason Casden&lt;br /&gt;
&lt;br /&gt;
3. Bohyun Kim&lt;br /&gt;
&lt;br /&gt;
=====Afternoon=====&lt;br /&gt;
1. Ayla Stein&lt;br /&gt;
&lt;br /&gt;
2. Heidi Dowding&lt;br /&gt;
&lt;br /&gt;
3. Coral Sheldon-Hess&lt;br /&gt;
&lt;br /&gt;
4. Cory Lown&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===FileAnalyzer: Rapid Development of File Manipulation Tasks===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
* Contact Terry Brady, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The FileAnalyzer (http://georgetown-university-libraries.github.io/File-Analyzer/) is an application designed to solve a number of library automation challenges:&lt;br /&gt;
&lt;br /&gt;
* validating digitized and reformatted files&lt;br /&gt;
* validating vendor statistics for counter compliance&lt;br /&gt;
* preparing collections of digital files for archiving and ingest&lt;br /&gt;
* manipulating ILS import and export files&lt;br /&gt;
&lt;br /&gt;
The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census. After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform. Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.&lt;br /&gt;
&lt;br /&gt;
The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules. As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.&lt;br /&gt;
&lt;br /&gt;
The first half of this session will be targeted to potential users and developers.  The second half of the session will be targeted towards developers who are interested in developing custom rules for the application.&lt;br /&gt;
&lt;br /&gt;
''Session Overview''&lt;br /&gt;
* Overview of the application&lt;br /&gt;
* Running sample file tests/transformations through the application&lt;br /&gt;
* Compiling and building the application&lt;br /&gt;
* Coding a custom file processing task&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;
# Michael Doran&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Collecting social media data with Social Feed Manager===&lt;br /&gt;
'''Half-Day [Morning]'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Dan Chudnov, GW Libraries, dchud (at) gwu.edu&lt;br /&gt;
* Dan Kerchner, GW Libraries, kerchner (at) gwu.edu&lt;br /&gt;
* Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu&lt;br /&gt;
&lt;br /&gt;
Social media data is a popular material for research and a new format for building collections.  What does it take to collect meaningfully from Twitter, Tumblr, YouTube, Weibo, Facebook, and other sites?  We will:&lt;br /&gt;
* Introduce options for collections, including both high- and low-end commercial offerings. Discuss what it means to collect these resources, covering boundaries, policies, and workflows required to develop a social media collection program in your institution.&lt;br /&gt;
* Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them&lt;br /&gt;
* Help you get started using the free [http://gwu-libraries.github.io/social-feed-manager Social Feed Manager] (SFM) app we're developing at GW to create your first collections. We’ll demo its use and demo a clean install (those w/environments can follow along)&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;
# Declan Fleming&lt;br /&gt;
# Esmé Cowles&lt;br /&gt;
# Jason Stirnaman&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Intro to Git ===&lt;br /&gt;
'''&amp;quot;Half-Day [tbd - probably afternoon]&amp;quot;''' &lt;br /&gt;
* Contact: Erin Fahy, Stanford University, efahy at stanford.edu&lt;br /&gt;
* TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu&lt;br /&gt;
&lt;br /&gt;
This session will cover the fundamentals of git by discussing/going through (time allowing):&lt;br /&gt;
* what is a distributed version control system&lt;br /&gt;
* what is git and github&lt;br /&gt;
* initializing a repo on a remote server/github&lt;br /&gt;
* cloning an existing repo&lt;br /&gt;
* creating a branch&lt;br /&gt;
* contributing code to a repo&lt;br /&gt;
* how to handle merge conflicts&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;
# Sam Kome&lt;br /&gt;
# Paula Gray-Overtoom&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
# Michael Doran&lt;br /&gt;
# Caitlin Christian-Lamb&lt;br /&gt;
# [[User:RileyChilds|Riley Childs]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Archival discovery and use ===&lt;br /&gt;
'''Full Day''' &lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Tim Shearer, UNC Chapel Hill, tshearer at email.unc.edu, &lt;br /&gt;
* Will Sexton, Duke, will.sexton at duke.edu&lt;br /&gt;
&lt;br /&gt;
This is a full day pre-conference about archival collections and will cover the intersections of archives, workflows, technologies, discovery, and use.&lt;br /&gt;
&lt;br /&gt;
Morning agenda: focused talks around (but not limited to) issues such as:&lt;br /&gt;
* Crowd-sourcing description to enhance collecitons&lt;br /&gt;
* Linked data and authority&lt;br /&gt;
* Mass digitization and sustainable workflows&lt;br /&gt;
* Digitized objects in context (images and other objects in finding aids)&lt;br /&gt;
* Too many cooks in the kitchen: versioning&lt;br /&gt;
* Global-, intra-, and inter- discovery of archival materials via finding aids &lt;br /&gt;
* and more...&lt;br /&gt;
&lt;br /&gt;
Afternoon agenda:  Focused talks around specific tools followed by general discussion, connections, opportunities, aspirations, and planning.&lt;br /&gt;
&lt;br /&gt;
Tool examples:&lt;br /&gt;
* Archivespace&lt;br /&gt;
* STEADy&lt;br /&gt;
* &amp;quot;RAMP&amp;quot; (Remixing Archival Metadata Project)&lt;br /&gt;
* OpenRefine&lt;br /&gt;
* Aeon&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;
Morning:&lt;br /&gt;
* Julia Bauder&lt;br /&gt;
&lt;br /&gt;
Afternoon:&lt;br /&gt;
* your name&lt;br /&gt;
&lt;br /&gt;
All day:&lt;br /&gt;
&lt;br /&gt;
# Josh Wilson&lt;br /&gt;
# Sam Kome&lt;br /&gt;
# Linda Ballinger&lt;br /&gt;
# Caitlin Christian-Lamb&lt;br /&gt;
# Laurie Lee Moses (seriously hard to decide here!)&lt;br /&gt;
# David Bass&lt;br /&gt;
# John Rees&lt;br /&gt;
# Lynn Eaton&lt;br /&gt;
# Hillel Arnold&lt;br /&gt;
# Susan Ivey&lt;br /&gt;
# Kristen Merryman&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===AV Content Slam===&lt;br /&gt;
'''Half-Day [morning]'''&lt;br /&gt;
Contacts:&lt;br /&gt;
* Kara Van Malssen, kara (at) avpreserve.com&lt;br /&gt;
* Lauren Sorenson, laurens (at) bavc.org&lt;br /&gt;
* Steven Villereal , villereal (at) gmail.com&lt;br /&gt;
A morning BarCamp/unconference for practitioners and coders who work with audiovisual content. The agenda will be attendee-driven, with a focus on sharing, synthesizing, and improving workflow strategies and documentation for software-based approaches to wrangling and providing access to audio and video content.&lt;br /&gt;
Possible topics of discussion might include:&lt;br /&gt;
* Use of format id and characterization/metadata extraction tools for AV&lt;br /&gt;
* Creating and using time-based metadata&lt;br /&gt;
* Managing (moving, fixity checking, etc) massive files (like uncompressed video)&lt;br /&gt;
For a better idea of the topics and concerns that have informed some past AV-themed events, check out the event wikis for [http://wiki.curatecamp.org/index.php/CURATEcamp_AVpres_2013 CURATEcamp AVpres 2013] as well as the [http://wiki.curatecamp.org/index.php/Association_of_Moving_Image_Archivists_%26_Digital_Library_Federation_Hack_Day_2013 AMIA/DLF 2013 Hack Day] .&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;
# A. Soroka&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===OCLC Web Services Hackfest===&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Half-Day&amp;quot; [afternoon]&lt;br /&gt;
&lt;br /&gt;
Contact: Shelley Hostetler, Community Manager, Developer Network hostetls[at]oclc.org&lt;br /&gt;
&lt;br /&gt;
This half-day hackfest will explore some of the OCLC Developer Network web services. We will provide an overview of some of the common topics such as the general REST-based architecture for most services and how to use some new authentication clients. The group can then decide to take a deep dive into a particular API and/or write a client library for the community.&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;
===Obey the Testing Goat!: Test Driven Web Development From The Ground Up===&lt;br /&gt;
'''Half-Day [tbd - probably afternoon]'''&lt;br /&gt;
* Contact [[User:Mredar|Mark Redar]], mredar[at]gmail.com&lt;br /&gt;
&lt;br /&gt;
Test driven development is a proven method for producing better quality code. But I've found it hard to follow a strict TDD methodology when starting new web projects. How do you write that first test when there is no code or web pages created yet.&lt;br /&gt;
&lt;br /&gt;
In this session, we will follow the excellent book [http://shop.oreilly.com/product/0636920029533.do &amp;quot;Test-Driven Web Development with Python&amp;quot;] to create a simple web site in Django following TDD from the first character typed. Come ready to code and test. No prior knowledge of python or Django required.&lt;br /&gt;
&lt;br /&gt;
By the end of this session, you should be able to  [http://www.obeythetestinggoat.com/ &amp;quot;Obey the Testing Goat&amp;quot;] from the start to finish for your next project.&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;
# Charlie Morris (NCSU)&lt;br /&gt;
# Jason Stirnaman&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Liz Milewicz&lt;br /&gt;
# Scott Hanrath&lt;br /&gt;
# Mike Beccaria&lt;br /&gt;
# Sean Aery&lt;br /&gt;
# Carolina Garcia&lt;br /&gt;
# Heidi Frank&lt;br /&gt;
# Chung Kang&lt;br /&gt;
# Nabil Kashyap&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Summon Hackfest ===&lt;br /&gt;
&lt;br /&gt;
Presenter: Eddie Newwirth and presenters from Summon libraries&lt;br /&gt;
Contact: Scott Schuetze (first DOT last @ serialssolutions. com)&lt;br /&gt;
&lt;br /&gt;
The Summon Hackfest (10:30am-12pm) will be a great opportunity for libraries using the Summon service to talk about improving discovery of resources, share their creative customizations and code, and exchange ideas about ways they can leverage the Summon API to better meet the needs of their users.&lt;br /&gt;
 &lt;br /&gt;
The Summon Hackfest is open to all libraries currently using ProQuest discovery and management services (Intota, Summon, Ulrich’s or the 360 suite of services), whether they are attending Code4Lib or are just in the area.&lt;br /&gt;
 &lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
[[:Category:Code4Lib2014]]&lt;/div&gt;</summary>
		<author><name>ChristopherHallberg</name></author>	</entry>

	</feed>