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

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Libraries_Sharing_Code&amp;diff=43118</id>
		<title>Libraries Sharing Code</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Libraries_Sharing_Code&amp;diff=43118"/>
				<updated>2015-06-11T20:37:23Z</updated>
		
		<summary type="html">&lt;p&gt;Mcritchlow: added UCLA and UCSF&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;A number of libraries have organizational repositories in GitHub.  These can be very valuable and we attempt to collect them here.&lt;br /&gt;
&lt;br /&gt;
==Institutions on GitHub==&lt;br /&gt;
* [https://github.com/aadl Ann Arbor District Library]&lt;br /&gt;
* [https://github.com/BCLibCoop BC Libraries Cooperative]&lt;br /&gt;
* [https://github.com/BCLIbraries Boston College Libraries]&lt;br /&gt;
* [https://github.com/britishlibrary The British Library]&lt;br /&gt;
* [https://github.com/Brown-University-Library Brown University Library]&lt;br /&gt;
* [https://github.com/cca California College of the Arts]&lt;br /&gt;
* [https://github.com/csusm-library CSU San Marcos]&lt;br /&gt;
* [https://github.com/clcdpc Central Library Consortium]&lt;br /&gt;
* [https://github.com/chattlibrary Chattanooga Public Library] (currently empty)&lt;br /&gt;
* [https://github.com/cul Columbia University Libraries]&lt;br /&gt;
* [https://github.com/DarienLibrary Darien (CT) Library]&lt;br /&gt;
* [https://github.com/duke-libraries Duke University Libraries]&lt;br /&gt;
* [https://github.com/gwu-libraries George Washington University Libraries]&lt;br /&gt;
* [https://github.com/Georgetown-University-Libraries Georgetown University Libraries]&lt;br /&gt;
* [https://github.com/subugoe Göttingen State and University Library]&lt;br /&gt;
* [https://github.com/gvsulib Grand Valley State University Libraries]&lt;br /&gt;
* [https://github.com/GrinnellCollegeLibraries Grinnell College Libraries]&lt;br /&gt;
* [https://github.com/harvard-library Harvard University Library Technology Services]&lt;br /&gt;
* [https://github.com/LibraryOfCongress Library of Congress]&lt;br /&gt;
* [https://github.com/LibraryofVA Library of Virginia]&lt;br /&gt;
* [https://github.com/LincolnUniLTL Lincoln University Library Teaching and Learning] (New Zealand)&lt;br /&gt;
* [https://github.com/ndlib University of Notre Dame Hesburgh Libraries] (And [https://github.com/ndlibersa the CORAL stuff])&lt;br /&gt;
* [https://github.com/MontclairState Montclair State]&lt;br /&gt;
* [https://github.com/njstatelibrary New Jersey State Library]&lt;br /&gt;
* [https://github.com/nla National Library of Australia]&lt;br /&gt;
* [https://github.com/nims-library Scientific Information Office, National Institute for Materials Science (NIMS Library)]&lt;br /&gt;
* [https://github.com/NCSU-Libraries NCSU Libraries]&lt;br /&gt;
* [https://github.com/nypl The New York Public Library]&lt;br /&gt;
* [https://github.com/NYULibraries NYU Libraries]&lt;br /&gt;
* [https://github.com/RockefellerArchiveCenter Rockefeller Archive Center]&lt;br /&gt;
* [https://github.com/osulibraries Ohio State University Libraries]&lt;br /&gt;
* [https://github.com/osulp Oregon State University Libraries &amp;amp; Press]&lt;br /&gt;
* [https://github.com/psu-stewardship Penn State Digital Stewardship]&lt;br /&gt;
* [https://github.com/pulibrary Princeton University Library]&lt;br /&gt;
* [https://github.com/ryersonlibrary Ryerson University Library &amp;amp; Archives]&lt;br /&gt;
* [https://github.com/adsabs SAO/NASA Astrophysics Data System]&lt;br /&gt;
* [https://github.com/slub Saxon State and University Library Dresden]&lt;br /&gt;
* [https://github.com/scds Sherman Centre for Digital Scholarship, McMaster University]&lt;br /&gt;
* [https://github.com/sul-dlss Stanford University Digital Library]&lt;br /&gt;
* [https://github.com/UBCLIBSYS UBC Library Systems and IT]&lt;br /&gt;
* [https://github.com/ualbertalib University of Alberta Libraries]&lt;br /&gt;
* [https://github.com/ualibraries The University of Arizona Libraries]&lt;br /&gt;
* [https://github.com/ucalgarylib University of Calgary Libraries &amp;amp; Cultural Resources]&lt;br /&gt;
* [https://github.com/uc-data-services UC Berkeley Library Data &amp;amp; GIS Services]&lt;br /&gt;
* [https://github.com/UCLALibrary UCLA Library]&lt;br /&gt;
* [https://github.com/UCSCLibrary UCSC Library] &lt;br /&gt;
* [https://github.com/ucsdlib UCSD Library]&lt;br /&gt;
* [https://github.com/umd-lib University of Maryland Libraries]&lt;br /&gt;
* [https://github.com/UMNLibraries University of Minnesota Libraries]&lt;br /&gt;
* [https://github.com/UNC-Libraries University of North Carolina at Chapel Hill Libraries]&lt;br /&gt;
* [https://github.com/ui-libraries University of Iowa Libraries]&lt;br /&gt;
* [https://github.com/vculibraries Virginia Commonwealth University Libraries]&lt;br /&gt;
* [https://github.com/wellcomelibrary Wellcome Library]&lt;br /&gt;
* [https://github.com/yalemssa Manuscripts and Archives, Yale University Library]&lt;br /&gt;
* [https://github.com/yorkulibraries York University Libraries]&lt;br /&gt;
&lt;br /&gt;
==Institutions with Non-GitHub open repositories==&lt;br /&gt;
* University of Florida: SobekCM software [http://sourceforge.net/directory/?q=sobekcm Sourceforge], [http://code.google.com/p/sobekcm/ Google code], [http://ufdc.ufl.edu/software UFDC institutional site]&lt;br /&gt;
* [http://eXtensibleCatalog.org eXtensible Catalog] repositories: [http://code.google.com/p/xcmetadataservicestoolkit/ Metadata Services Toolkit], [http://code.google.com/p/xcoaitoolkit/ OAI Toolkit], [http://code.google.com/p/xcncip2toolkit/ NCIP Toolkit] (all these on Google code), [http://drupal.org/project/xc Drupal Toolkit] (on drupal.org)&lt;br /&gt;
* [http://git.sitka.bclibraries.ca BC Libraries Cooperative]&lt;br /&gt;
* [https://bitbucket.org/colglibsys Colgate University Libraries]&lt;br /&gt;
&lt;br /&gt;
==Other Library Organizations on GitHub==&lt;br /&gt;
* [https://github.com/projectblacklight Project Blacklight]&lt;br /&gt;
* [https://github.com/projecthydra Project Hydra]&lt;br /&gt;
* [https://github.com/islandora Islandora]&lt;br /&gt;
* [https://github.com/artefactual Artefactual], along with projects: [https://github.com/artefactual/atom AtoM], and [https://github.com/artefactual/archivematica Archivematica]&lt;br /&gt;
* [https://github.com/duraspace DuraSpace], along with projects: [https://github.com/dspace DSpace], [https://github.com/fcrepo4/ Fedora], and [https://svn.duraspace.org/view/duracloud/ DuraCloud (not yet on GitHub)]&lt;br /&gt;
* [https://github.com/hbz/ North Rhine-Westphalian Library Service Center (hbz)] and its service [https://github.com/lobid/ lobid]&lt;br /&gt;
&lt;br /&gt;
* [https://github.com/pkp Public Knowledge Project], along with projects: [https://github.com/pkp/ojs Open Journal Systems], [https://github.com/pkp/ocs Open Conference Systems], and [https://github.com/pkp/omp Open Monograph Press]&lt;br /&gt;
* [https://github.com/internetarchive Internet Archive]&lt;br /&gt;
* [https://github.com/openlibrary Open Library Team]&lt;br /&gt;
* [https://github.com/scholarslab Scholars' Lab]&lt;br /&gt;
* [https://github.com/next-l Project Next-L]&lt;br /&gt;
* [http://librecat.org/ LibreCat Open Tools for Library and Research Services]&lt;br /&gt;
* [https://github.com/swissbib/ swissbib information services for Swiss university libraries and Swiss National library]&lt;br /&gt;
* [https://github.com/TEIC Text Encoding Initiative Consortium]&lt;br /&gt;
&lt;br /&gt;
==Individuals on GitHub==&lt;br /&gt;
* [https://github.com/jronallo Jason Ronallo] North Carolina State University&lt;br /&gt;
* [https://github.com/cazzerson Jason Casden] North Carolina State University&lt;br /&gt;
* [https://github.com/jbfink John Fink] McMaster University&lt;br /&gt;
* [https://github.com/rgilmour70 Ron Gilmour] Ithaca College&lt;br /&gt;
* [https://github.com/mreidsma Matthew Reidsma] Grand Valley State University&lt;br /&gt;
* [https://github.com/mjsuhonos MJ Suhonos] Ryerson University Library &amp;amp; Archives&lt;br /&gt;
* [https://github.com/mjordan Mark Jordan] Simon Fraser University Library&lt;br /&gt;
* [https://github.com/jneubert Joachim Neubert] ZBW - Leibniz Information Centre for Economics&lt;br /&gt;
* [https://github.com/phette23 Eric Phetteplace] - California College of the Arts&lt;br /&gt;
* [https://github.com/barmintor Ben Armintor] Fedora 3, Blacklight, Hydra Projects&lt;br /&gt;
* [https://github.com/techbrarian Jason Bengtson] Houston Academy of Medicine/Texas Medical Center&lt;/div&gt;</summary>
		<author><name>Mcritchlow</name></author>	</entry>

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

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Craft_Drinkup&amp;diff=42504</id>
		<title>2015 Craft Drinkup</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Craft_Drinkup&amp;diff=42504"/>
				<updated>2015-01-27T17:13:18Z</updated>
		
		<summary type="html">&lt;p&gt;Mcritchlow: Added myself (Matt C) and info to the list&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;When: Tuesday, February 10th - 7pm - 10pm (ish)&lt;br /&gt;
&lt;br /&gt;
Where: eBay Offices - 1400 SW 5th Ave, Portland, OR 97201&lt;br /&gt;
&lt;br /&gt;
The Craft Brew Drinkup at Code4lib 2015 is all about sharing and enjoying good beer, soda, and other drinks with fellow conference attendees. The idea is to bring bottles of your favorite beers or non-alcoholic drinks.&lt;br /&gt;
&lt;br /&gt;
While you're not obligated to bring local brews from wherever you're from, participants are definitely encouraged to bring brews that you think is special and might be somewhat hard for others outside your area to find. Homebrew is especially welcome as are non-alcoholic beverages. There will be hot water available for those who want to bring in their tea blends as well!&lt;br /&gt;
&lt;br /&gt;
This year, eBay has agreed to host the Code4Lib Drinkup at their offices in downtown Portland, a 6 block walk from the conference hotel. Attendees should expect to bring something to share, either drinks or snacks.&lt;br /&gt;
&lt;br /&gt;
Please Note: The space must be cleaned up and all folks gone no later than 11pm.&lt;br /&gt;
&lt;br /&gt;
Space is limited to the first 200 people who register.&lt;br /&gt;
&lt;br /&gt;
== Signup ==&lt;br /&gt;
Please sign up below to share the brews and bottles you're thinking of bringing along and make any special requests (but don't expect that your wishes will be granted).&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Name !! Bringing !! Wanting&lt;br /&gt;
|-&lt;br /&gt;
| Esmé Cowles || Cigar City 110K+OT Batch #7 or Marshal Zhukov, Homebrew Imperial Saison || Any saison or sour!&lt;br /&gt;
|-&lt;br /&gt;
| Francis Kayiwa || (at least the following) Boulevard Quad Bourbon Barrel, Weyebacher Althea || &amp;lt;strike&amp;gt; Scotty Karate &amp;lt;/strike&amp;gt; barleywines and any porters&lt;br /&gt;
|-&lt;br /&gt;
| Becky Yoose || Non-alcoholic options: I have access to craft sodas from Millstream, Sprechers, Stevens Point - '''ping me at b.yoose at gmail if you have a wish list!''' Otherwise, I'll buy whatever's available in PDX and a selection of Finnish teas|| N/A drinks :c) Melon soda (not Ramune) greatly appreciated&lt;br /&gt;
|-&lt;br /&gt;
| Tania Fersenheim || Something from Pretty Things || ...&lt;br /&gt;
|-&lt;br /&gt;
| Ben Armintor || BCS Pappy Van Winkle, Dark Lord 2009, Black Tuesday || ...&lt;br /&gt;
|-&lt;br /&gt;
| Justin Coyne || Surly Darkness? || ...&lt;br /&gt;
|-&lt;br /&gt;
| Whitni Watkins|| Non-alcoholic Ginger beer options: at least Reed's &amp;amp; Saranac Lake. Potentially one other local brewed Ginger beer. If you have a request from Upstate NY HMU whitni.watkins at gmail (alcoholic and N/A) || Ginger Beers &amp;amp; Ales specifically: Fentimans, River City, Bundaberg and Blenheim Red Hot&lt;br /&gt;
|-&lt;br /&gt;
| Sarah Simpkin || Accepting requests for tasty Quebecois beers -- [https://brouehaha.com/en/nos-bieres/ see this list for breweries]. Otherwise will grab a small selection. Contact me at sarahsimpkin at gmail.com :-) || Hefeweizen-y beers appreciated&lt;br /&gt;
|- &lt;br /&gt;
|Coral Sheldon-Hess || Bourbon-barrel aged assam tea (1oz), Whiskey Cinnamon Snap rooibos tea (~1.5 oz), and Brandy Oolong tea (.5 oz), plus 1-2 reusable brewing devices || Ginger ale, anything bourbony, anything imperial and stoutish&lt;br /&gt;
|-&lt;br /&gt;
| mx matienzo || Transmitter Brewing B2, De Molen SSS Triple Stout 2011, perhaps a couple southern Upstate NY ciders, ...? || Saisons, sours and gueuzes, weird ciders, other horseblankety stuff&lt;br /&gt;
|-&lt;br /&gt;
| David Bass || TBT || ...&lt;br /&gt;
|-&lt;br /&gt;
| Christina Harlow || Probably something from Grimm...? Who knows, stuff from Brooklyn &amp;amp; stuff from Eastern Tenn/Western NC (Highland brewery?) || English bitter type stuff or stouts&lt;br /&gt;
|-&lt;br /&gt;
| Tom Johnson || Portland/Willamette Valley things you might not find downtown. Heater Allen, Pfriem, The Commons, Block 15, and/or Crux Fermentation.  Homebrew (Old Ale brewed in October and racked over the winter).|| ...&lt;br /&gt;
|-&lt;br /&gt;
| Ranti Junus || Non-alcoholic something and probably some pu-erh tea. || N/A drinks&lt;br /&gt;
|-&lt;br /&gt;
| Chad Nelson || Weyerbacher Riserva, Dogfish Head Miles Davis Bitches' Brew || miller lite&lt;br /&gt;
|-&lt;br /&gt;
| Maura Carbone || Something from Mass or CT or both, not a beer drinker, so I'll see what I find!  || N/A drinks or a hard cider or two&lt;br /&gt;
|-&lt;br /&gt;
| Sandy Rodriguez || Boulevard Tank 7; perhaps something from [http://mothersbrewing.com/craft-beers/our-beers/ Mother's Brewing]  || scotch ales, brown ales, stouts, saisons&lt;br /&gt;
|-&lt;br /&gt;
| Dominic Bordelon || Louisiana beers besides Abita; probably LA 31 and Covington, maybe a Nola or two || ...&lt;br /&gt;
|-&lt;br /&gt;
| Tara Robertson || Vancouver (BC, Canada) beer || non-alcoholic ginger beer&lt;br /&gt;
|-&lt;br /&gt;
|-&lt;br /&gt;
| Matt Critchlow || I'll try to hunt down some new San Diego offerings (there are many) || homebrew, belgians&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Mcritchlow</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&amp;diff=42265</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=42265"/>
				<updated>2014-12-05T22:26:58Z</updated>
		
		<summary type="html">&lt;p&gt;Mcritchlow: /* Intro to Docker */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Preconference Schedule (draft) ==&lt;br /&gt;
&lt;br /&gt;
Session titles in Italics means they have not been confirmed yet by presenters/workshop leaders.&lt;br /&gt;
&lt;br /&gt;
This is a draft, and there may be some room switching when registration opens. Rooms will be confirmed the week before Code4Lib.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1:30 PM - 4:30 PM)&lt;br /&gt;
|-&lt;br /&gt;
| '''Parlor A (30''') || Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable (Needs: projector, internet connection, and power strips) || Intro to Git &amp;amp; possibly beyond (Needs: projector/screen)&lt;br /&gt;
|-&lt;br /&gt;
| '''Parlor B (30)''' || Code Retreat (Needs whiteboard, dry-erase markers, projector) || Code Retreat (Needs whiteboard, dry-erase markers, projector) &lt;br /&gt;
|-&lt;br /&gt;
| '''Parlor C (30)''' || code4lib/Write The Docs barcamp (Needs: projector/screen, flipboard/whiteboard, power sources for laptops) ||  code4lib/Write The Docs barcamp&lt;br /&gt;
|-&lt;br /&gt;
| '''Grand Ballroom''' I (320) || CANCELLED: [UXtravaganza] || Presentations workshop (Needs: projector/screen)&lt;br /&gt;
|-&lt;br /&gt;
| '''Grand Ballroom''' II (200) || Visualizing Library Data (Needs: projector)  || DPLA API Workshop (Bringing their own projector)&lt;br /&gt;
|-&lt;br /&gt;
| '''Galleria I (35)''' || Coding Custom Solutions for Every Department in the Library with File Analyzer (Needs PC laptop projection, monitor, internet access/wifi, attendees bring laptops) || Fail4Lib 2015 (Needs: projector/screen; Requested: Conference table seating, limit 20 attendants)&lt;br /&gt;
|-&lt;br /&gt;
| '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (Needs: internet/wifi, overhead projection) || CollectionSpace: Getting it up and running at your museum (Needs: Projector)&lt;br /&gt;
|-&lt;br /&gt;
| '''Galleria III (35)''' || ''Replace yourself with a painfully complex bash script...or try Ansible'' || Intro to Docker&lt;br /&gt;
|-&lt;br /&gt;
| '''Studio (35)''' || Linked Data Workshop (Bringing their own projector) || Dive into Hydra (Needs: projector/screen; Requests: classroom style seating)&lt;br /&gt;
|-&lt;br /&gt;
| '''Directors (35)''' || Code4Arc (Needs: projector) || Code4Arc (Needs: projector)&lt;br /&gt;
|-&lt;br /&gt;
| '''Council (45)''' || Delivering and Preserving GIS Data (Projector, Video connector for MacBook Pro, wifi, power outlets) || A hands-on introduction to GeoBlacklight (Needs: projector, outlets; Requests: list of attendees)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&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-conferences ==&lt;br /&gt;
&lt;br /&gt;
===MORNING:===&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;
* Laney McGlohon, Stanford University, laneymcg@stanford.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;
# Bohyun Kim&lt;br /&gt;
# Mark Jarrell&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;
# Shaun Ellis&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Chris Sharp&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 (pleeeeaaase put this in a different slot from Ansible!)&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;
# Shaun Ellis&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Matt Critchlow&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;
# Barbara Hui&lt;br /&gt;
# Carol Bean&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;
# Sara Amato&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;
# Emily Lynema&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;
# Whitni Watkins&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;
# Chris Sharp&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;
# Derek Merleaux&lt;br /&gt;
# Steven Anderson&lt;br /&gt;
# Eben English&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Heather Pitts&lt;br /&gt;
# Andrew Woods&lt;br /&gt;
# Carol Bean&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;
# Shaun Ellis&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;
# Emily Lynema&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;
=== CANCELLED: ''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;
# Eben English (1/2 day)&lt;br /&gt;
# Shaun Ellis (as attendee or volunteer)&lt;br /&gt;
# Whitni Watkins (as attendee or volunteer)&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;
# Derek Merleaux&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;
# Derek Merleaux&lt;br /&gt;
# Bohyun Kim&lt;br /&gt;
# Mark Jarrell&lt;br /&gt;
# Eben English&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Sarah Simpkin&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Kathryn Stine&lt;br /&gt;
# Steve Meyer&lt;br /&gt;
# Matt Critchlow&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;
# Bohyun Kim&lt;br /&gt;
# Steven Anderson&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Sarah Simpkin&lt;br /&gt;
# Mark Jarrell&lt;br /&gt;
# Heather Pitts&lt;br /&gt;
# Kathryn Stine&lt;br /&gt;
# Andrew Woods&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]]&lt;/div&gt;</summary>
		<author><name>Mcritchlow</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&amp;diff=42264</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=42264"/>
				<updated>2014-12-05T22:25:26Z</updated>
		
		<summary type="html">&lt;p&gt;Mcritchlow: /* Visualizing Library Data */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Preconference Schedule (draft) ==&lt;br /&gt;
&lt;br /&gt;
Session titles in Italics means they have not been confirmed yet by presenters/workshop leaders.&lt;br /&gt;
&lt;br /&gt;
This is a draft, and there may be some room switching when registration opens. Rooms will be confirmed the week before Code4Lib.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1:30 PM - 4:30 PM)&lt;br /&gt;
|-&lt;br /&gt;
| '''Parlor A (30''') || Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable (Needs: projector, internet connection, and power strips) || Intro to Git &amp;amp; possibly beyond (Needs: projector/screen)&lt;br /&gt;
|-&lt;br /&gt;
| '''Parlor B (30)''' || Code Retreat (Needs whiteboard, dry-erase markers, projector) || Code Retreat (Needs whiteboard, dry-erase markers, projector) &lt;br /&gt;
|-&lt;br /&gt;
| '''Parlor C (30)''' || code4lib/Write The Docs barcamp (Needs: projector/screen, flipboard/whiteboard, power sources for laptops) ||  code4lib/Write The Docs barcamp&lt;br /&gt;
|-&lt;br /&gt;
| '''Grand Ballroom''' I (320) || CANCELLED: [UXtravaganza] || Presentations workshop (Needs: projector/screen)&lt;br /&gt;
|-&lt;br /&gt;
| '''Grand Ballroom''' II (200) || Visualizing Library Data (Needs: projector)  || DPLA API Workshop (Bringing their own projector)&lt;br /&gt;
|-&lt;br /&gt;
| '''Galleria I (35)''' || Coding Custom Solutions for Every Department in the Library with File Analyzer (Needs PC laptop projection, monitor, internet access/wifi, attendees bring laptops) || Fail4Lib 2015 (Needs: projector/screen; Requested: Conference table seating, limit 20 attendants)&lt;br /&gt;
|-&lt;br /&gt;
| '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (Needs: internet/wifi, overhead projection) || CollectionSpace: Getting it up and running at your museum (Needs: Projector)&lt;br /&gt;
|-&lt;br /&gt;
| '''Galleria III (35)''' || ''Replace yourself with a painfully complex bash script...or try Ansible'' || Intro to Docker&lt;br /&gt;
|-&lt;br /&gt;
| '''Studio (35)''' || Linked Data Workshop (Bringing their own projector) || Dive into Hydra (Needs: projector/screen; Requests: classroom style seating)&lt;br /&gt;
|-&lt;br /&gt;
| '''Directors (35)''' || Code4Arc (Needs: projector) || Code4Arc (Needs: projector)&lt;br /&gt;
|-&lt;br /&gt;
| '''Council (45)''' || Delivering and Preserving GIS Data (Projector, Video connector for MacBook Pro, wifi, power outlets) || A hands-on introduction to GeoBlacklight (Needs: projector, outlets; Requests: list of attendees)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&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-conferences ==&lt;br /&gt;
&lt;br /&gt;
===MORNING:===&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;
* Laney McGlohon, Stanford University, laneymcg@stanford.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;
# Bohyun Kim&lt;br /&gt;
# Mark Jarrell&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;
# Shaun Ellis&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Chris Sharp&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 (pleeeeaaase put this in a different slot from Ansible!)&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;
# Shaun Ellis&lt;br /&gt;
# Mark Mounts&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;
# Barbara Hui&lt;br /&gt;
# Carol Bean&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;
# Sara Amato&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;
# Emily Lynema&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;
# Whitni Watkins&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;
# Chris Sharp&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;
# Derek Merleaux&lt;br /&gt;
# Steven Anderson&lt;br /&gt;
# Eben English&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Heather Pitts&lt;br /&gt;
# Andrew Woods&lt;br /&gt;
# Carol Bean&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;
# Shaun Ellis&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;
# Emily Lynema&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;
=== CANCELLED: ''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;
# Eben English (1/2 day)&lt;br /&gt;
# Shaun Ellis (as attendee or volunteer)&lt;br /&gt;
# Whitni Watkins (as attendee or volunteer)&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;
# Derek Merleaux&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;
# Derek Merleaux&lt;br /&gt;
# Bohyun Kim&lt;br /&gt;
# Mark Jarrell&lt;br /&gt;
# Eben English&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Sarah Simpkin&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Kathryn Stine&lt;br /&gt;
# Steve Meyer&lt;br /&gt;
# Matt Critchlow&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;
# Bohyun Kim&lt;br /&gt;
# Steven Anderson&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Sarah Simpkin&lt;br /&gt;
# Mark Jarrell&lt;br /&gt;
# Heather Pitts&lt;br /&gt;
# Kathryn Stine&lt;br /&gt;
# Andrew Woods&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]]&lt;/div&gt;</summary>
		<author><name>Mcritchlow</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_Twitter_List&amp;diff=36606</id>
		<title>2013 Twitter List</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_Twitter_List&amp;diff=36606"/>
				<updated>2013-02-12T20:00:47Z</updated>
		
		<summary type="html">&lt;p&gt;Mcritchlow: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Put your twitter handle in here, if you're at Code4Lib 2013 Chicago. I'll add you to the [https://twitter.com/code4lib/attendees-2013 Attendees 2013 twitter list] for @code4lib when I get a chance. Thanks! -Sean&lt;br /&gt;
&lt;br /&gt;
# Becky Yoose (@yo_bj)&lt;br /&gt;
# Beatrice Pulliam (@beatricepulliam)&lt;br /&gt;
# Cynthia Ng (@TheRealArty)&lt;br /&gt;
# Nettie Lagace (@abugseye)&lt;br /&gt;
# Erin White (@erinrwhite)&lt;br /&gt;
# Maccabee Levine (@maccabeelevine)&lt;br /&gt;
# Steven Bassett (@bassettsj)&lt;br /&gt;
# Steve Oberg (@techsvcslib)&lt;br /&gt;
# Carmen Mitchell (@carmendarlene)&lt;br /&gt;
# Christie Peterson (@save4use)&lt;br /&gt;
# Jason Casden (@cazzerson)&lt;br /&gt;
# Michael Poltorak (@michaelpoltorak)&lt;br /&gt;
# Ron Gilmour (@gilmour70)&lt;br /&gt;
# James Staub (@jamesstaub)&lt;br /&gt;
# Curtis Thacker (@curtisthacker)&lt;br /&gt;
# Masao Takaku (@tmasao)&lt;br /&gt;
# Colin Watt (@colinmwatt)&lt;br /&gt;
# Dave Green (@icookwithwine)&lt;br /&gt;
# Alan Dyck (@Alan_Dyck)&lt;br /&gt;
# Megan O'Neill Kudzia (@meganoneill)&lt;br /&gt;
# Keith Nickum (@keithnickum)&lt;br /&gt;
# Matt Critchlow (@mattcritchlow)&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2013]]&lt;/div&gt;</summary>
		<author><name>Mcritchlow</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_talks_proposals&amp;diff=28006</id>
		<title>2013 talks proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_talks_proposals&amp;diff=28006"/>
				<updated>2012-11-02T21:11:10Z</updated>
		
		<summary type="html">&lt;p&gt;Mcritchlow: added UCSD proposal&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Deadline has been extended by request due to the hurricane/storm.'''&lt;br /&gt;
&lt;br /&gt;
Deadline for talk submission is ''Friday, November 9'' at 11:59pm ET. We ask that no changes be made after this point, so that every voter reads the same thing. You can update your description again after voting closes.&lt;br /&gt;
&lt;br /&gt;
Prepared talks are 20 minutes (including setup and questions), and focus on one or more of the following areas:&lt;br /&gt;
* tools (some cool new software, software library or integration platform)&lt;br /&gt;
* specs (how to get the most out of some protocols, or proposals for new ones)&lt;br /&gt;
* challenges (one or more big problems we should collectively address)&lt;br /&gt;
&lt;br /&gt;
The community will vote on proposals using the criteria of:&lt;br /&gt;
* usefulness&lt;br /&gt;
* newness&lt;br /&gt;
* geekiness&lt;br /&gt;
* uniqueness&lt;br /&gt;
* awesomeness&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
== Talk Title ==&lt;br /&gt;
 &lt;br /&gt;
* Speaker's name, affiliation, and email address&lt;br /&gt;
* Second speaker's name, affiliation, email address, if applicable&lt;br /&gt;
&lt;br /&gt;
Abstract of no more than 500 words.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== All Teh Metadatas Re-Revisited ==&lt;br /&gt;
 &lt;br /&gt;
* Esme Cowles, UC San Diego Library, escowles AT ucsd DOT edu&lt;br /&gt;
* Matt Critchlow, UC San Diego Library, mcritchlow AT ucsd DOT edu&lt;br /&gt;
* Bradley Westbrook, UC San Diego Library, bdwestbrook AT ucsd DOT edu&lt;br /&gt;
&lt;br /&gt;
Last year Declan Fleming presented ALL TEH METADATAS and reviewed our UC&lt;br /&gt;
San Diego Library Digital Asset Management system and RDF data model. You&lt;br /&gt;
may be shocked to hear that all that metadata wasn't quite enough to&lt;br /&gt;
handle increasingly complex digital library and research data in an&lt;br /&gt;
elegant way. Our ad-hoc, 8-year-old data model has also been added to in&lt;br /&gt;
inconsistent ways and our librarians and developers have not always been&lt;br /&gt;
perfectly in sync in understanding how the data model has evolved over&lt;br /&gt;
time.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
In this presentation we'll review our process of locking a team of&lt;br /&gt;
librarians and developers in a room to figure out a new data model, from&lt;br /&gt;
domain definition through building and testing an OWL ontology. We¹ll also&lt;br /&gt;
cover the challenges we ran into, including the review of existing&lt;br /&gt;
controlled vocabularies and ontologies, or lack thereof, and the decisions&lt;br /&gt;
made to cover the gaps. Finally, we'll discuss how we engaged the digital&lt;br /&gt;
library community for feedback and what we have to do next. We all know&lt;br /&gt;
that Things Fall Apart, this is our attempt at Doing Better This Time.&lt;br /&gt;
&lt;br /&gt;
== Modernizing VuFind with Zend Framework 2 ==&lt;br /&gt;
&lt;br /&gt;
* Demian Katz, Villanova University, demian DOT katz AT villanova DOT edu&lt;br /&gt;
&lt;br /&gt;
When setting goals for a new major release of VuFind, use of an existing web framework was an important decision to encourage standardization and avoid reinvention of the wheel.  Zend Framework 2 was selected as providing the best balance between the cutting-edge (ZF2 was released in 2012) and stability (ZF1 has a long history and many adopters).  This talk will examine some of the architecture and features of the new framework and discuss how it has been used to improve the VuFind project.&lt;br /&gt;
&lt;br /&gt;
== Did You Really Say That Out Loud?  Tools and Techniques for Safe Public WiFi Computing  ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:DataGazetteer|Peter Murray]], LYRASIS, Peter.Murray@lyrasis.org&lt;br /&gt;
&lt;br /&gt;
Public WiFi networks, even those that have passwords, are nothing more that an old-time [https://en.wikipedia.org/wiki/Party_line_(telephony) party line]: what every you say can be easily heard by anyone nearby.  &lt;br /&gt;
Remember [https://en.wikipedia.org/wiki/Firesheep Firesheep]?  &lt;br /&gt;
It was an extension to Firefox that demonstrated how easy it was to snag session cookies and impersonate someone else.&lt;br /&gt;
So what are you sending out over the airwaves, and what techniques are available to prevent eavesdropping?&lt;br /&gt;
This talk will demonstrate tools and techniques for desktop and mobile operating systems that you should be using right now -- right here at Code4Lib -- to protect your data and your network activity.&lt;br /&gt;
&lt;br /&gt;
== Drupal 8 Preview — Symfony and Twig ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Drupal is a great platform for building web applications. Last year, the core developers decided to adopt the Symfony PHP framework, because it would lay the groundwork for the modernization (and de-PHP4ification) of the Drupal codebase. As I write this, the Symfony ClassLoader and HttpFoundation libraries are committed to Drupal core, with more elements likely before Drupal 8 code freeze.&lt;br /&gt;
&lt;br /&gt;
It seems almost certain that the Twig templating engine will supplant PHPtemplate as the core Drupal template engine. Twig is a powerful, secure theme building tool that removes PHP from the templating system, the result being a very concise and powerful theme layer.&lt;br /&gt;
&lt;br /&gt;
Symfony and Twig have a common creator, Fabien Potencier, who's overall goal is to rid the world of the excesses of PHP 4.&lt;br /&gt;
&lt;br /&gt;
== Neat! But How Do We Do It? - The Real-world Problem of Digitizing Complex Corporate Digital Objects ==&lt;br /&gt;
&lt;br /&gt;
* Matthew Mariner, University of Colorado Denver, Auraria Library, matthew.mariner@ucdenver.edu&lt;br /&gt;
&lt;br /&gt;
Isn't it neat when you discover that you are the steward of dozens of Sanborn Fire Instance Maps, hundreds of issues of a city directory, and thousands of photographs of persons in either aforementioned medium? And it's even cooler when you decide, &amp;quot;Let's digitize these together and make them one big awesome project to support public urban history&amp;quot;?  Unfortunately it's a far more difficult process than one imagines at inception and, sadly, doesn't always come to fruition.  My goal here is to discuss the technological (and philosophical) problems librarians and archivists face when trying to create ultra-rich complex corporate digital projects, or, rather, projects consisting of at least three facets interrelated by theme.  I intend to address these problems by suggesting management solutions, web workarounds, and, perhaps, a philosophy that might help in determining whether to even move forward or not.  Expect a few case studies of &amp;quot;grand ideas crushed by technological limitations&amp;quot; and &amp;quot;projects on the right track&amp;quot; to follow.   &lt;br /&gt;
 &lt;br /&gt;
== ResCarta Tools building a standard format for audio archiving, discovery and display ==&lt;br /&gt;
&lt;br /&gt;
* [[User:sarney|John Sarnowski]], The ResCarta Foundation, john.sarnowski@rescarta.org&lt;br /&gt;
&lt;br /&gt;
The free ResCarta Toolkit has been used by libraries and archives around the world to host city directories, newspapers, and historic photographs and by aerospace companies to search and find millions of engineering documents.  Now the ResCarta team has released audio additions to the toolkit. &lt;br /&gt;
&lt;br /&gt;
Create full text searchable oral histories, news stories, interviews. or build an archive of lectures; all done to Library of Congress standards.  The included transcription editor allows for accurate correction of the data conversion tool’s output.  Build true archives of text, photos and audio.  A single audio file carries the embedded Axml metadata, transcription, and word location information. Checks with the FADGI BWF Metaedit.&lt;br /&gt;
&lt;br /&gt;
ResCarta-Web presents your audio to IE, Chome, Firefox, Safari, and Opera browsers with full playback and word search capability. Display format is OGG!! &lt;br /&gt;
&lt;br /&gt;
You have to see this tool in action.  Twenty minutes from an audio file to transcribed, text-searchable website.  Be there or be L seven (Yeah, I’m that old)   &lt;br /&gt;
&lt;br /&gt;
== Format Designation in MARC Records: A Trip Down the Rabbit-Hole ==&lt;br /&gt;
 &lt;br /&gt;
* Michael Doran, University of Texas at Arlington, doran@uta.edu&lt;br /&gt;
&lt;br /&gt;
This presentation will use a seemingly simple data point, the &amp;quot;format&amp;quot; of the item being described, to illustrate some of the complexities and challenges inherent in the parsing of MARC records.  I will talk about abstract vs. concrete forms; format designation in the Leader, 006, 007, and 008 fixed fields as well as the 245 and 300 variable fields; pseudo-formats; what is mandatory vs. optional in respect to format designation in cataloging practice; and the differences between cataloging theory and practice as observed via format-related data mining of a mid-size academic library collection. &lt;br /&gt;
&lt;br /&gt;
I understand that most of us go to code4lib to hear about the latest sexy technologies.  While MARC isn't sexy, many of the new tools being discussed still need to be populated with data gleaned from MARC records.  MARC format designation has ramifications for search and retrieval, limits, and facets, both in the ILS and further downstream in next generation OPACs and web-scale discovery tools.  Even veteran library coders will learn something from this session. &lt;br /&gt;
&lt;br /&gt;
== Touch Kiosk 2: Piezoelectric Boogaloo ==&lt;br /&gt;
&lt;br /&gt;
* Andreas Orphanides, North Carolina State University Libraries, akorphan@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
At the NCSU Libraries, we provide realtime access to information on library spaces and services through an interactive touchscreen kiosk in our Learning Commons. In the summer of 2012, two years after its initial deployment, I redeveloped the kiosk application from the ground up, with an entirely new codebase and a completely redesigned user interface. The changes I implemented were designed to remedy previously identified shortcomings in the code and the interface design [1], and to enhance overall stability and performance of the application.&lt;br /&gt;
&lt;br /&gt;
In this presentation I will outline my revision process, highlighting the lessons I learned and the practices I implemented in the course of redevelopment. I will highlight the key features of the HTML/Javascript codebase that allow for increased stability, flexibility, and ease of maintenance; and identify the changes to the user interface that resulted from the usability findings I uncovered in my previous research. Finally, I will compare the usage patterns of the new interface to the analysis of the previous implementation to examine the practical effect of the implemented changes.&lt;br /&gt;
&lt;br /&gt;
I will also provide access to a genericized version of the interface code for others to build their own implementations of similar kiosk applications.&lt;br /&gt;
&lt;br /&gt;
[1] http://journal.code4lib.org/articles/5832&lt;br /&gt;
&lt;br /&gt;
== Wayfinding in a Cloud: Location Service for libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Petteri Kivimäki, The National Library of Finland, petteri.kivimaki@helsinki.fi&lt;br /&gt;
&lt;br /&gt;
Searching for books in large libraries can be a difficult task for a novice library user. This paper presents The Location Service, software as a service (SaaS) wayfinding application developed and managed by The National Library of Finland, which is targeted for all the libraries. The service provides additional information and map-based guidance to books and collections by showing their location on a map, and it can be integrated with any library management system, as the integration happens by adding a link to the service in the search interface. The service is being developed continuously based on the feedback received from the users.&lt;br /&gt;
&lt;br /&gt;
The service has two user interfaces: One for the customers and one for the library staff for managing the information related to the locations. The UI for the customers is fully customizable by the libraries, and the customization is done via template files by using the following techniques: HTML, CSS, and Javascript/jQuery. The service supports multiple languages, and the libraries have a full control of the languages, which they want to support in their environment.&lt;br /&gt;
&lt;br /&gt;
The service is written in Java and it uses Spring and Hibernate frameworks. The data is stored in PostgreSQL database, which is shared by all the libraries. They do not possess a direct access to the database, but the service offers an interface, which makes it possible to retrieve XML data over HTTP. Modification of the data via admin UI, however, is restricted, and access on the other libraries’ data is blocked.&lt;br /&gt;
&lt;br /&gt;
== Empowering Collection Owners with Automated Bulk Ingest Tools for DSpace ==&lt;br /&gt;
&lt;br /&gt;
* Terry Brady, Georgetown University, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Library has developed a number of applications to expedite the process of ingesting content into DSpace.&lt;br /&gt;
* Automatically inventory a collection of documents or images to be uploaded&lt;br /&gt;
* Generate a spreadsheet for metadata capture based on the inventory&lt;br /&gt;
* Generate item-level ingest folders, contents files and dublin core metadata for the items to be ingested&lt;br /&gt;
* Validate the contents of ingest folders prior to initiating the ingest to DSpace&lt;br /&gt;
* Present users with a simple, web-based form to initiate the batch ingest process&lt;br /&gt;
&lt;br /&gt;
The applications have eliminated a number of error-prone steps from the ingest workflow and have significantly reduced a number of tedious data editing steps.  These applications have empowered content experts to be in charge of their own collections. &lt;br /&gt;
&lt;br /&gt;
In this presentation, I will provide a demonstration of the tools that were built and discuss the development process that was followed.&lt;br /&gt;
&lt;br /&gt;
== Quality Assurance Reports for DSpace Collections ==&lt;br /&gt;
&lt;br /&gt;
* Terry Brady, Georgetown University, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Library has developed a collection of quality assurance reports to improve the consistency of the metadata in our DSpace collections.  The report infrastructure permits the creation of query snippets to test for possible consistency errors within the repository such as items missing thumbnails, items with multiple thumbnails, items missing a creation date, items containing improperly formatted dates, items without duplicated metadata fields, items recently added items across the repository, a community or a collection&lt;br /&gt;
&lt;br /&gt;
These reports have served to prioritize programmatic data cleanup tasks and manual data cleanup tasks.  The reports have served as a progress tracker for data cleanup work and will provide on-going monitoring of the metadata consistency of the repository.&lt;br /&gt;
&lt;br /&gt;
In this presentation, I will provide a demonstration of the tools that were built and discuss the development process that was followed.&lt;br /&gt;
&lt;br /&gt;
== A Hybrid Solution for Improving Single Sign-On to a Proxy Service with Squid and EZproxy through Shibboleth and ExLibris’ Aleph X-Server ==&lt;br /&gt;
&lt;br /&gt;
* Alexander Jerabek, UQAM - Université du Québec à Montréal, jerabek.alexander_j@uqam.ca&lt;br /&gt;
* Minh-Quang Nguyen, UQAM - Université du Québec à Montréal, nguyen.minh-quang@uqam.ca&lt;br /&gt;
&lt;br /&gt;
In this talk, we will describe how we developed and implemented a hybrid solution for improving single sign-on in conjunction with the library’s proxy service. This hybrid solution consists of integrating the disparate elements of EZproxy, the Squid workflow, Shibboleth, and the Aleph X-Server. We will report how this new integrated service improves the user experience. To our knowledge, this new service is unique and has not been implemented anywhere else. We will also present some statistics after approximately one year in production.&lt;br /&gt;
&lt;br /&gt;
See article: http://journal.code4lib.org/articles/7470&lt;br /&gt;
&lt;br /&gt;
== HTML5 Video Now! ==&lt;br /&gt;
&lt;br /&gt;
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Can you use HTML5 video now? Yes.&lt;br /&gt;
&lt;br /&gt;
I'll show you how to get started using HTML5 video, including gotchas, tips, and tricks. Beyond the basics we'll see the power of having video integrated into HTML and the browser. Finally, we'll look at examples that push the limits and show the exciting future of video on the Web.&lt;br /&gt;
&lt;br /&gt;
My experience comes from technical development of an oral history video clips project. I developed the technical aspects of the project, including video processing, server configuration, development of a public site, creation of an administrative interface, and video engagement analytics. Major portions of this work have been open sourced under an MIT license.&lt;br /&gt;
&lt;br /&gt;
== Hybrid Archival Collections Using Blacklight and Hydra ==&lt;br /&gt;
&lt;br /&gt;
* Adam Wead, Rock and Roll Hall of Fame and Museum, awead@rockhall.org&lt;br /&gt;
&lt;br /&gt;
At the Library and Archives of the Rock and Roll Hall of Fame, we use available tools such as Archivists' Toolkit to create EAD finding aids of our collections.  However, managing digital content created from these materials and the born-digital content that is also part of these collections represents a significant challenge.  In my presentation, I will discuss how we solve the problem of our hybrid collections by using Hydra as a digital asset manager and Blacklight as a unified presentation and discovery interface for all our materials.&lt;br /&gt;
&lt;br /&gt;
Our strategy centers around indexing ead xml into Solr as multiple documents: one for each collection, and one for every series, sub-series and item contained within a collection.  For discovery, we use this strategy to leverage item-level searching of archival collections alongside our traditional library content.  For digital collections, we use this same technique to represent a finding aid in Hydra as a set of linked objects using RDF.  New digital items are then linked to these parent objects at the collection and series level.  Once this is done, the items can be exported back out to the Blacklight solr index and the digital content appears along with the rest of the items in the collection.&lt;br /&gt;
&lt;br /&gt;
== Making the Web Accessible through Solid Design ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Cynthia|Cynthia Ng]] from Ryerson University Library &amp;amp; Archives&lt;br /&gt;
&lt;br /&gt;
In libraries, we are always trying our best to be accessible to everyone and we make every effort to do so physically, but what about our websites? Web designers are great at talking about the user experience and how to improve it, but what sometimes gets overlooked is how to make a site more accessible and meet accessibility guidelines. While guidelines are necessary to cover a minimum standard, web accessibility should come from good web design without ‘sacrificing’ features. While it's difficult to make a website fully accessible to everyone, there are easy, practical ways to make a site as accessible as possible.&lt;br /&gt;
&lt;br /&gt;
While the focus will be on websites and meeting the Web Accessibility Guidelines WCAG, the presentation will also touch on how to make custom web interfaces accessible.&lt;br /&gt;
&lt;br /&gt;
== Getting People to What They Need Fast! A Wayfinding Tool to Locate Books &amp;amp; Much More ==&lt;br /&gt;
 &lt;br /&gt;
* Steven Marsden, Ryerson University Library &amp;amp; Archives, steven dot marsden at ryerson dot ca&lt;br /&gt;
* [[User:Cynthia|Cynthia Ng]], Ryerson University Library &amp;amp; Archives&lt;br /&gt;
&lt;br /&gt;
Having a bewildered, lost user in the building or stacks is a common occurrence, but we can help our users find their way through enhanced maps and floor plans.  While not a new concept, these maps are integrated into the user’s flow of information without having to load a special app. The map not only highlights the location, but also provides all the related information with a link back to the detailed item view. During the first stage of the project, it has only be implemented for books (and other physical items), but the 'RULA Finder' is built to help users find just about anything and everything in the library including study rooms, computer labs, and staff. With a simple to use admin interface, it makes it easy for everyone, staff and users. &lt;br /&gt;
&lt;br /&gt;
The application is written in PHP with data stored in a MySQL database. The end-user interface involves jQuery, JSON, and the library's discovery layer (Summon) API.&lt;br /&gt;
&lt;br /&gt;
The presentation will not only cover the technical aspects, but also the implementation and usability findings.&lt;br /&gt;
&lt;br /&gt;
== De-sucking the Library User Experience ==&lt;br /&gt;
 &lt;br /&gt;
* Jeremy Prevost, Northwestern University, j-prevost {AT} northwestern [DOT] edu&lt;br /&gt;
&lt;br /&gt;
Have you ever thought that library vendors purposely create the worst possible user experience they can imagine because they just hate users? Have you ever thought that your own library website feels like it was created by committee rather than for users because, well, it was? I’ll talk about how we used vendor supplied APIs to our ILS and Discovery tool to create an experience for our users that sucks at least a little bit less.&lt;br /&gt;
&lt;br /&gt;
The talk will provide specific examples of how inefficient or confusing vendor supplied solutions are from a user perspective along with our specific streamlined solutions to the same problems. Code examples will be minimal as the focus will be on improving user experience rather than any one code solution of doing that. Examples may include the seemingly simple tasks of renewing a book or requesting an item from another campus library.&lt;br /&gt;
&lt;br /&gt;
== Solr Testing Is Easy with Rspec-Solr Gem ==&lt;br /&gt;
&lt;br /&gt;
* Naomi Dushay, Stanford University, ndushay AT stanford DOT edu&lt;br /&gt;
&lt;br /&gt;
How do you know if &lt;br /&gt;
&lt;br /&gt;
* your idea for &amp;quot;left anchoring&amp;quot; searches actually works?&lt;br /&gt;
* your field analysis for LC call numbers accommodates a suffix between the first and second cutter without breaking the rest of LC call number parsing?&lt;br /&gt;
* tweaking Solr configs to improve, say, Chinese searching, won't break Turkish and Cyrillic?&lt;br /&gt;
* changes to your solrconfig file accomplish what you wanted without breaking anything else?&lt;br /&gt;
&lt;br /&gt;
Avoid the whole app stack when writing Solr acceptance/relevancy/regression tests!  Forget cucumber and capybara.  This gem lets you easily (only 4 short files needed!) write tests like this, passing arbitrary parameters to Solr:&lt;br /&gt;
&lt;br /&gt;
  it &amp;quot;unstemmed author name Zare should precede stemmed variants&amp;quot; do&lt;br /&gt;
    resp = solr_response(author_search_args('Zare').merge({'fl'=&amp;gt;'id,author_person_display', 'facet'=&amp;gt;false}))&lt;br /&gt;
    resp.should include(&amp;quot;author_person_display&amp;quot; =&amp;gt; /\bZare\W/).in_each_of_first(3).documents&lt;br /&gt;
    resp.should_not include(&amp;quot;author_person_display&amp;quot; =&amp;gt; /Zaring/).in_each_of_first(20).documents&lt;br /&gt;
  end&lt;br /&gt;
      &lt;br /&gt;
  it &amp;quot;Cyrillic searching should work:  Восемьсoт семьдесят один день&amp;quot; do&lt;br /&gt;
    resp = solr_resp_doc_ids_only({'q'=&amp;gt;'Восемьсoт семьдесят один день'})&lt;br /&gt;
    resp.should include(&amp;quot;9091779&amp;quot;)&lt;br /&gt;
  end&lt;br /&gt;
   &lt;br /&gt;
  it &amp;quot;q of 'String quartets Parts' and variants should be plausible &amp;quot; do&lt;br /&gt;
    resp = solr_resp_doc_ids_only({'q'=&amp;gt;'String quartets Parts'})&lt;br /&gt;
    resp.should have_at_least(2000).documents&lt;br /&gt;
    resp.should have_the_same_number_of_results_as(solr_resp_doc_ids_only({'q'=&amp;gt;'(String quartets Parts)'}))&lt;br /&gt;
    resp.should have_more_results_than(solr_resp_doc_ids_only({'q'=&amp;gt;'&amp;quot;String quartets Parts&amp;quot;'}))&lt;br /&gt;
  end&lt;br /&gt;
   &lt;br /&gt;
  it &amp;quot;Traditional Chinese chars 三國誌 should get the same results as simplified chars 三国志&amp;quot; do&lt;br /&gt;
    resp = solr_response({'q'=&amp;gt;'三國誌', 'fl'=&amp;gt;'id', 'facet'=&amp;gt;false}) &lt;br /&gt;
    resp.should have_at_least(240).documents&lt;br /&gt;
    resp.should have_the_same_number_of_results_as(solr_resp_doc_ids_only({'q'=&amp;gt;'三国志'})) &lt;br /&gt;
  end&lt;br /&gt;
&lt;br /&gt;
See&lt;br /&gt;
   http://rubydoc.info/github/sul-dlss/rspec-solr/frames&lt;br /&gt;
   https://github.com/sul-dlss/rspec-solr&lt;br /&gt;
&lt;br /&gt;
and our production relevancy/acceptance/regression tests slowly migrating from cucumber to:&lt;br /&gt;
   https://github.com/sul-dlss/sw_index_tests&lt;br /&gt;
&lt;br /&gt;
== Northwestern's Digital Image Library ==&lt;br /&gt;
&lt;br /&gt;
*Mike Stroming, Northwestern University Library, m-stroming AT northwestern DOT edu&lt;br /&gt;
*Edgar Garcia, Northwestern University Library, edgar-garcia AT northwestern DOT edu&lt;br /&gt;
&lt;br /&gt;
At Northwestern University Library, we are about to release a beta version of our Digital Image Library (DIL).  DIL is an implementation of the Hydra technology that provides a Fedora repository solution for discovery of and access to over 100,000 images for staff, students, and scholars. Some important features are:&lt;br /&gt;
&lt;br /&gt;
*Build custom collection of images using drag-and-drop&lt;br /&gt;
*Re-order images within a collection using drag-and-drop&lt;br /&gt;
*Nest collections within other collections&lt;br /&gt;
*Create details/crops of images&lt;br /&gt;
*Zoom, rotate images&lt;br /&gt;
*Upload personal images&lt;br /&gt;
*Retrieve your own uploads and details from a collection&lt;br /&gt;
*Export a collection to a PowerPoint presentation&lt;br /&gt;
*Create a group of users and authorize access to your images&lt;br /&gt;
*Batch edit image metadata&lt;br /&gt;
&lt;br /&gt;
Our presentation will include a demo, explanation of the architecture, and a discussion of the benefits of being a part of the Hydra open-source community.&lt;br /&gt;
&lt;br /&gt;
== Two standards in a software (to say nothing of Normarc) ==&lt;br /&gt;
&lt;br /&gt;
*Zeno Tajoli, CINECA (Italy), z DOT tajoli AT cineca DOT it&lt;br /&gt;
&lt;br /&gt;
With this presentation I want to show how ILS Koha handles the support of three differnt MARC dialects:&lt;br /&gt;
MARC21, Unimarc and Normarc. The main points of the presentation:&lt;br /&gt;
&lt;br /&gt;
*Three MARC at MySQL level&lt;br /&gt;
*Three MARC at API level&lt;br /&gt;
*Three MARC at display&lt;br /&gt;
*Can I add a new format ?&lt;br /&gt;
&lt;br /&gt;
== Future Friendly Web Design for Libraries ==&lt;br /&gt;
&lt;br /&gt;
*[[User:michaelschofield|Michael Schofield]], Alvin Sherman Library, Research, and Information Technology Center, mschofied[dot]nova[dot]edu&lt;br /&gt;
&lt;br /&gt;
Libraries on the web are afterthoughts. Often their design is stymied on one hand by red tape imposed by the larger institution and on the other by an overload of too democratic input from colleagues. Slashed budgets / staff stretched too thin foul-up the R-word (that'd be &amp;quot;redesign&amp;quot;) - but things are getting pretty strange. Notions about the Web (and where it can be accessed) are changing. &lt;br /&gt;
&lt;br /&gt;
So libraries can only avoid refabbing their fixed-width desktop and jQuery Mobile m-dot websites for so long until desktop users evaporate and demand from patrons with web-ready refrigerators becomes deafening. Just when we have largely hopped on the bandwagon and gotten enthusiastic about being online, our users expect a library's site to look and perform great on everything. &lt;br /&gt;
&lt;br /&gt;
Our presence on the web should be built to weather ever-increasing device complexity. To meet users at their point of need, libraries must start thinking Future Friendly.&lt;br /&gt;
&lt;br /&gt;
This overview rehashes the approach and philosophy of library web design, re-orienting it for maximum accessibility and maximum efficiency of design. While just 20 minutes, we'll mull over techniques like mobile-first responsive web design, modular CSS, browser feature detection for progressive enhancement, and lots of nifty tricks.&lt;br /&gt;
&lt;br /&gt;
==BYU's discovery layer service aggregator==&lt;br /&gt;
&lt;br /&gt;
*Curtis	Thacker, Brigham Young University, curtis.thacker AT byu DOT edu&lt;br /&gt;
&lt;br /&gt;
It is clear that libraries will continue to experience rapid change based on the speed of technology. To acknowledge this new reality and to provide rapid response to shifting end user paradigms BYU has developed a custom service aggregator. At first our vendors looked at us a bit funny; however, in the last year they have been astonished with the fluid implementation of new services – here’s the short list:&lt;br /&gt;
&lt;br /&gt;
*filmfinder - a tool for browsing and searching films&lt;br /&gt;
*A custom book recommender service based on checkout data&lt;br /&gt;
*Integrated library services like personell, library hours, study room scheduler and database finder through a custom adwords system.&lt;br /&gt;
*A very geeky and powerful utility used for converting marc XML into primo compliant xml.&lt;br /&gt;
*Embedded floormaps&lt;br /&gt;
*A responsive web design&lt;br /&gt;
*Bing did-you-mean&lt;br /&gt;
*And many more.&lt;br /&gt;
&lt;br /&gt;
I will demo the system, review the archtecture and talk about future plans.&lt;br /&gt;
&lt;br /&gt;
==The Avalon Media System: A Next Generation Hydra Head For Audio and Video Delivery==&lt;br /&gt;
&lt;br /&gt;
* Michael Klein, Senior Software Developer, Northwestern University LIbrary, michael.klein AT northwestern DOT edu&lt;br /&gt;
* Nathan Rogers, Programmer/Analyst, Indiana University, rogersna AT indiana DOT edu&lt;br /&gt;
&lt;br /&gt;
Based on the success of the [http://www.dml.indiana.edu/ Variations] digital music platform, Indiana University and Northwestern University have developed a next generation educational tool for delivering multimedia resources to the classroom. The Avalon Media System (formerly Variations on Video) supports the ingest, media processing, management, and access-controlled delivery of library-managed video and audio collections. To do so, the system draws on several existing, mature, open source technologies:&lt;br /&gt;
&lt;br /&gt;
* The ingest, search, and discovery functionality of the Hydra framework&lt;br /&gt;
* The powerful multimedia workflow management features of Opencast Matterhorn&lt;br /&gt;
* The flexible Engage audio/video player&lt;br /&gt;
* The streaming capabilities of both Red5 Media Server (open source) and Adobe Flash Media Server (proprietary)&lt;br /&gt;
&lt;br /&gt;
Extensive customization options are built into the framework for tailoring the application to the needs of a specific institution.&lt;br /&gt;
&lt;br /&gt;
Our goal is to create an open platform that can be used by other institutions to serve the needs of the academic community. Release 1 is planned for a late February launch with future versions released every couple of months following. For more information visit http://avalonmediasystem.org/ and https://github.com/variations-on-video/hydrant.&lt;br /&gt;
&lt;br /&gt;
== The DH Curation Guide: Building a Community Resource == &lt;br /&gt;
&lt;br /&gt;
*Robin Davis, John Jay College of Criminal Justice, robdavis AT jjay.cuny.edu &lt;br /&gt;
*James Little, University of Illinois Urbana-Champaign, little9 AT illinois.edu  &lt;br /&gt;
&lt;br /&gt;
Data curation for the digital humanities is an emerging area of research and practice. The DH Curation Guide, launched in July 2012, is an educational resource that addresses aspects of humanities data curation in a series of expert-written articles. Each provides a succinct introduction to a topic with annotated lists of useful tools, projects, standards, and good examples of data curation done right. The DH Curation Guide is intended to be a go-to resource for data curation practitioners and learners in libraries, archives, museums, and academic institutions.  &lt;br /&gt;
&lt;br /&gt;
Because it's a growing field, we designed the DH Curation Guide to be a community-driven, living document. We developed a granular commenting system that encourages data curation community members to contribute remarks on articles, article sections, and article paragraphs. Moreover, we built in a way for readers to contribute and annotate resources for other data curation practitioners.  &lt;br /&gt;
&lt;br /&gt;
This talk will address how the DH Curation Guide is currently used and will include a sneak peek at the articles that are in store for the Guide’s future. We will talk about the difficulties and successes of launching a site that encourages community. We are all builders here, so we will also walk through developing the granular commenting/annotation system and the XSLT-powered publication workflow. &lt;br /&gt;
&lt;br /&gt;
== Solr Update == &lt;br /&gt;
&lt;br /&gt;
*Erik Hatcher, LucidWorks, erik.hatcher AT lucidworks.com &lt;br /&gt;
&lt;br /&gt;
Solr is continually improving.  Solr 4 was recently released, bringing dramatic changes in the underlying Lucene library and Solr-level features.  It's tough for us all to keep up with the various versions and capabilities.&lt;br /&gt;
&lt;br /&gt;
This talk will blaze through the highlights of new features and improvements in Solr 4 (and up).  Topics will include: SolrCloud, direct spell checking, surround query parser, and many other features.  We will focus on the features library coders really need to know about.&lt;br /&gt;
&lt;br /&gt;
== Reports for the People == &lt;br /&gt;
&lt;br /&gt;
*Kara Young, Keene State College, NH, kyoung1 at keene.edu&lt;br /&gt;
*Dana Clark, Keene State College, NH, dclark5 at keene.edu&lt;br /&gt;
&lt;br /&gt;
Libraries are increasingly being called upon to provide information on how our programs and services are moving our institutional strategic goals forward.  In support of College and departmental Information Literacy learning outcomes, Mason Library Systems at Keene State College developed an assessment database to record and report assessment activities by Library faculty.  Frustrated by the lack of freely available options for intuitively recording, accounting for, and outputting useful reports on instructional activities, Librarians requested a tool to make capturing and reporting activities (and their lives) easier.  Library Systems was able to respond to this need by working with librarians to identify what information is necessary to capture, where other assessment tools had fallen short, and ultimately by developing an application that supports current reporting imperatives while providing flexibility for future changes.&lt;br /&gt;
&lt;br /&gt;
The result of our efforts was an in-house browser interfaced Assessment Database to improve the process of data collection and analysis.  The application is written in PHP, data stored in a MySQL database, and presented via browser making extensive use of JQuery and JQuery plug-ins for data collection, manipulation, and presentation. &lt;br /&gt;
The presentation will outline the process undertaken to build a successful collaboration with Library faculty from conception to implementation, as well as the technical aspects of our trial-and-error approach. Plus: cool charts and graphs!&lt;br /&gt;
&lt;br /&gt;
==  Network Analyses of Library Catalog Data ==&lt;br /&gt;
 &lt;br /&gt;
* Kirk Hess, University of Illinois at Urbana-Champaign, kirkhess AT illinois.edu&lt;br /&gt;
* Harriett Green, University of Illinois at Urbana-Champaign, green19 AT illinois.edu &lt;br /&gt;
&lt;br /&gt;
Library collections are all too often like icebergs:  The amount exposed on the surface is only a fraction of the actual amount of content, and we’d like to recommend relevant items from deep within the catalog to users. With the assistance of an XSEDE Allocation grant (http://xsede.org), we’ve used R to reconstitute anonymous circulation data from the University of Illinois’s library catalog into separate user transactions. The transaction data is incorporated into subject analyses that use XSEDE supercomputing resources to generate predictive network analyses and visualizations of subject areas searched by library users using Gephi (https://gephi.org/). The test data set for developing the subject analyses consisted of approximately 38,000 items from the Literatures and Languages Library that contained 110,000 headings and 130,620 transactions. We’re currently working on developing a recommender system within VuFind to display the results of these analyses.&lt;br /&gt;
&lt;br /&gt;
== Pitfall! Working with Legacy Born Digital Materials in Special Collections ==&lt;br /&gt;
&lt;br /&gt;
* Donald Mennerich, The New York Public Library, don.mennerich AT gmail.com&lt;br /&gt;
* Mark A. Matienzo, Yale University Library, mark AT matienzo.org&lt;br /&gt;
&lt;br /&gt;
Archives and special collections are being faced with a growing abundance of  born digital material, as well as an abundance of many promising tools for managing them. However, one must consider the potential problems that can arise when approaching a collection containing legacy materials (from roughly the pre-internet era). Many of the tried and true, &amp;quot;best of breed&amp;quot; tools for digital preservation don't always work as they do for more recent materials, requiring a fair amount of ingenuity and use of &amp;quot;word of mouth tradecraft and knowledge exchanged through serendipitous contacts, backchannel conversations, and beer&amp;quot; (Kirschenbaum, &amp;quot;Breaking &amp;lt;code&amp;gt;badflag&amp;lt;/code&amp;gt;&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
Our presentation will focus on some of the strange problems encountered and creative solutions devised by two digital archivists in the course of preserving, processing, and providing access to collections at their institutions. We'll be placing particular particular emphasis of the pitfalls and crocodiles we've learned to swing over safely, while collecting treasure in the process. We'll address working with CP/M disks in collections of authors' papers, reconstructing a multipart hard drive backup spread across floppy disks, and more. &lt;br /&gt;
&lt;br /&gt;
== Project &amp;lt;s&amp;gt;foobar&amp;lt;/s&amp;gt; FUBAR ==&lt;br /&gt;
&lt;br /&gt;
* Becky Yoose, Grinnell College, yoosebec AT grinnell DOT edu&lt;br /&gt;
&lt;br /&gt;
Be it mandated from Those In A Higher Pay Grade Than You or self-inflicted, many of us deal with managing major library-related technology projects [1]. It’s common nowadays to manage multiple technology projects, and generally external and internal issues can be planned for to minimize project timeline shifts and quality of deliverables. Life, however, has other plans for you, and all your major library technology infrastructure projects pile on top of each other at the same time. How do you and your staff survive a train wreck of technology projects and produce deliverables to project stakeholders without having to go into the library IT version of the United States Federal Witness Protection Program?&lt;br /&gt;
&lt;br /&gt;
This session covers my experience with the collision of three major library technology projects - including a new institutional repository and an integrated library system migration - and how we dealt with external and internal factors, implemented damage control, and overall lessening the damage from the epic crash. You might laugh, you might cry, you will probably have flashbacks from previous projects, but you will come out of this session with a set of tools to use when you’re dealing with managing mission-critical projects.&lt;br /&gt;
&lt;br /&gt;
[1] Past code4lib talks have covered specific project management strategies, such as Agile, for application development. I will be focusing on and discussing general project management practices in relation to various library technology projects, many of which these strategies include in their own structures.&lt;br /&gt;
&lt;br /&gt;
== Implementing RFID in an Academic Library == &lt;br /&gt;
&lt;br /&gt;
* Scott Bacon, Coastal Carolina University, sbacon AT coastal DOT edu&lt;br /&gt;
&lt;br /&gt;
Coastal Carolina University’s Kimbel Library recently implemented RFID to increase security, provide better inventory control over library materials and enable do-it-yourself patron services such as self checkout. &lt;br /&gt;
&lt;br /&gt;
I’ll give a quick overview of RFID and the components involved and then will talk about how our library utilized the technology. It takes a lot of research, time, money and not too little resourcefulness to make your library RFID-ready. I’ll show how we developed our project timeline, how we assessed and evaluated vendors and how we navigated the bid process. I’ll also talk about hardware and software installation, configuration and troubleshooting and will discuss our book and media collection encoding process. &lt;br /&gt;
&lt;br /&gt;
We encountered myriad issues with our vendor, the hardware and the software. Would we do it all over again? Should your library consider RFID? Caveats abound...&lt;br /&gt;
&lt;br /&gt;
== Coding an Academic Library Intranet in Drupal: Now We're Getting Organizized... ==&lt;br /&gt;
&lt;br /&gt;
* Scott Bacon, Coastal Carolina University, sbacon AT coastal DOT edu&lt;br /&gt;
&lt;br /&gt;
The Kimbel Library Intranet is coded in Drupal 7, and was created to increase staff communication and store documentation. This presentation will contain an overview of our intranet project, including the modules we used, implementation issues, and possible directions in future development phases. I won’t forget to talk about the slew of tasty development issues we faced, including dealing with our university IT department, user buy-in, site navigation, user roles, project management, training and mobile modules (or the lack thereof). And some other fun (mostly) true anecdotes will surely be shared. &lt;br /&gt;
&lt;br /&gt;
The main functions of Phase I of this project were to increase communication across departments and committees, facilitate project management and revise the library's shared drive. Another important function of this first phase was to host mission-critical documentation such as strategic goals, policies and procedures. Phase II of this project will focus on porting employee tasks into the centralized intranet environment. This development phase, which aims to replicate and automate the bulk of staff workflows within a content management system, will be a huge undertaking. &lt;br /&gt;
&lt;br /&gt;
We chose Drupal as our intranet platform because of its extensibility, flexibility and community support. We are also moving our entire library web presence to Drupal in 2013 and will be soliciting any advice on which modules to use/avoid and which third-party services to wrangle into the Drupal environment. Should we use Drupal as the back-end to our entire Web presence? Why or why not?&lt;br /&gt;
&lt;br /&gt;
== Hands off! Best Practices and Top Ten Lists for Code Handoffs ==&lt;br /&gt;
 &lt;br /&gt;
* Naomi Dushay, Stanford University Library, ndushay@stanford.edu&lt;br /&gt;
* Bess Sadler, Stanford University Library, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Transition points in who is the primary developer on an actively developing code base can be a source of frustration for everyone involved. We've tried to minimize that pain point as much as possible through the use of agile methods like test driven development, continuous integration, and modular design. Has optimizing for developer happiness brought us happiness? What's worked, what hasn't, and what's worth adopting? How do you keep your project in a state where you can easily hand it off? &lt;br /&gt;
&lt;br /&gt;
== How to be an effective evangelist for your open source project ==&lt;br /&gt;
 &lt;br /&gt;
* Bess Sadler, Stanford University Library, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
The difference between an open source software project that gets new adopters and new contributing community members (which is to say, a project that goes on existing for any length of time) and a project that doesn't, often isn't a question of superior design or technology. It's more often a question of whether the advocates for the project can convince institutional leaders AND front line developers that a project is stable and trustworthy. What are successful strategies for attracting development partners? I'll try to answer that and talk about what we could do as a community to make collaboration easier.  &lt;br /&gt;
&lt;br /&gt;
== What does it mean to be a &amp;quot;good&amp;quot; vendor in an open source meritocracy? ==&lt;br /&gt;
&lt;br /&gt;
* Matt Zumwalt, Data Curation Experts / MediaShelf / Hydra Project, matt@curationexperts.com&lt;br /&gt;
&lt;br /&gt;
What is the role of vendors in open source?  What should be the position of vendors in a meritocracy?  What are the avenues for encouraging great vendors who contribute to open source communities in valuable ways?  How you answer these questions has a huge impact on a community, and in order to formulate strong answers, you need to be well informed.  Let’s glimpse at the business practicalities of this situation, beginning with 1) an overview of the viable profit models for open-source software, 2) some of the realities of vendor involvement in open source, and 3) an account of the ins &amp;amp; outs of compensation &amp;amp; equity structures within for-profit corporations.&lt;br /&gt;
&lt;br /&gt;
The topics of power &amp;amp; influence, fairness, community participation, software quality, employment and personal profit are fair game, along with software licensing, sponsorship, closed source software and the role of sales people.&lt;br /&gt;
&lt;br /&gt;
This presentation will draw on personal experience from the past seven years spent bootstrapping and running MediaShelf, a small but prolific for-profit consulting company that focuses entirely on open source digital repository software.  MediaShelf has played an active role in creating the Hydra Framework and continuously contributes to maintenance of Fedora. Those contributions have been funded through consulting contracts for authoring &amp;amp; implementing open source software on behalf of organizations around the world.&lt;br /&gt;
&lt;br /&gt;
==Occam’s Reader: A system that allows the sharing of eBooks via Interlibrary Loan==&lt;br /&gt;
&lt;br /&gt;
*Ryan Litsey, Texas Tech University, Ryan DOT Litsey AT ttu.edu&lt;br /&gt;
*Kenny Ketner, Texas Tech University, Kenny DOT Ketner AT ttu.edu&lt;br /&gt;
&lt;br /&gt;
Occam’s Reader is a software platform that allows the transfer and sharing of electronic books between libraries via existing interlibrary loan software. Occam’s Reader allows libraries to meet the growing need to be able to share our electronic resources. In the ever-increasing digital world, many of our collection development plans now include eBook platforms. The problem with eBooks, however, is that they are resources that are locked into the home library. With Occam’s Reader we can continue the centuries-old tradition of resource sharing and also keep up with the changing digital landscape. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Using Puppet for configuration management when no two servers look alike ==&lt;br /&gt;
* Eugene Vilensky, Senior Systems Administrator, Northwestern University Library, evilensky northwestern edu&lt;br /&gt;
&lt;br /&gt;
Configuration management is hot because it allows one to scale to thousands of machines, all of which look alike, and tightly manage changes across the nodes. Infrastructure as code, implement all changes programmatically, yadda yadda yadda.&lt;br /&gt;
&lt;br /&gt;
Unfortunately, servers which have gone unmanaged for a long time do not look very similar to each other.  Variables come in many forms, usually because of some or all of the following: Who installed the server, where it was installed, where the image was sourced from, when it was installed, where additional packages were sourced, and what kind of software was hosted on it.&lt;br /&gt;
&lt;br /&gt;
Bringing such machines into your configuration management platform is no harder and no easier than some or all of the following options options: 1) blow such machines away and start from scratch, migrate your data. 2) Find the lowest common baseline between the current state and the ideal state and start the work there. 3) implement new features/services on existing unmanaged machines but manage the new features/services.&lt;br /&gt;
&lt;br /&gt;
I will describe our experiences at the library for all three options using the Puppet open-source tool on Enterprise Linux 5 and 6.&lt;br /&gt;
&lt;br /&gt;
== REST &amp;lt;b&amp;gt;IS&amp;lt;/b&amp;gt; Your Mobile Strategy ==&lt;br /&gt;
&lt;br /&gt;
* Richard Wolf, University of Illinois at Chicago, richwolf@uic.edu&lt;br /&gt;
&lt;br /&gt;
Mobile is the new hotness ... and you can't be one of the cool kids unless you've got your own mobile app ... but the road to mobility is daunting.  I'll argue that it's actually easier than it seems ... and that the simplest way to mobility is to bring your data to the party, create a REST API around the data, tell developers about your API, and then let the magic happen.  To make my argument concrete, I'll show (lord help me!) how to go from an interesting REST API to a fun iOS tool for librarians and the general public in twenty minutes.&lt;br /&gt;
&lt;br /&gt;
== ScholarSphere: How We Built a Repository App That Doesn't Feel Like Yet Another Janky Old Repository App ==&lt;br /&gt;
&lt;br /&gt;
* Dan Coughlin, Penn State University, danny@psu.edu&lt;br /&gt;
* Mike Giarlo, Penn State University, michael@psu.edu&lt;br /&gt;
&lt;br /&gt;
ScholarSphere is a web application that allows the Penn State research community to deposit, share, and manage its scholarly works.  It is also, as some of our users and our peers have observed, a repository app that feels much more like Google Docs or GitHub than earlier-generation repository applications.  ScholarSphere is built upon the Hydra framework (Fedora Commons, Solr, Blacklight, Ruby on Rails), MySQL, Redis, Resque, FITS, ImageMagick, jQuery, Bootstrap, and FontAwesome.  We'll talk about techniques we used to:&lt;br /&gt;
&lt;br /&gt;
* eliminate Fedora-isms in the application&lt;br /&gt;
* model and expose RDF metadata in ways that users find unobtrusive&lt;br /&gt;
* manage permissions via a UI widget that doesn't stab you in the face&lt;br /&gt;
* harvest and connect controlled vocabularies (such as LCSH) to forms&lt;br /&gt;
* make URIs cool&lt;br /&gt;
* keep the app snappy without venturing into the architectural labyrinth of YAGNI&lt;br /&gt;
* build and queue background jobs&lt;br /&gt;
* expose social features and populate activity streams&lt;br /&gt;
* tie checksum verification, characterization, and version control to the UI&lt;br /&gt;
* let users upload and edit multiple files at once&lt;br /&gt;
&lt;br /&gt;
The application will be demonstrated; code will be shown; and we solemnly commit to showing ABSOLUTELY NO XML.&lt;br /&gt;
&lt;br /&gt;
==Coding with Mittens==&lt;br /&gt;
&lt;br /&gt;
*Jim LeFager, DePaul University Library jlefager@depaul.edu&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Working in an environment where developers have restricted access to servers and development areas, or where you are primarily working in multiple hosted systems with limited access, can be a challenge when you are attempting to incorporate any new functionality or improve an existing one.  Hosted web services present a benefit so that staff time is not dedicated to server maintenance and development, but customization can be difficult and at times impossible.  In many cases, incorporating any current API functionality requires additional work besides the original development work which can be frustrating and inefficient.  The result can be a Frankenstein monster of web services that is confusing to the user and difficult to navigate.  &lt;br /&gt;
&lt;br /&gt;
This talk will focus on some effective best practices, and maybe not so great but necessary practices that we have adopted to develop and improve our user’s experience using javascript/jQuery and CSS to manipulate our hosted environments.  This will include a review of available tools that allow collaborative development in the cloud, as well as examples of jQuery methods that have allowed us to take additional control of these hosted environments as well as track them using Google Analytics.  Included will be examples from Springshare Campus Guides, CONTENTdm and other hosted web spaces that have been ‘hacked’ to improve the UI.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Hacking the DPLA ==&lt;br /&gt;
* Nate Hill, Chattanooga Public Library,  nathanielhill AT gmail.com&lt;br /&gt;
* Sam Klein, Wikipedia, metasj AT gmail.com&lt;br /&gt;
&lt;br /&gt;
The Digital Public Library of America is a growing open-source platform to support digital libraries and archives of all kinds.  DPLA-alpha is available for testing, with data from six initial Hubs.  New APIs and data feeds are in development, with the next release scheduled for April.   &lt;br /&gt;
&lt;br /&gt;
Come learn what we are doing, how to contribute or hack the DPLA roadmap, and how you (or your favorite institution) can draw from and publish through it.  Larger institutions can join as a (content or service) hub, helping to aggregate and share metadata and services from across their {region, field, archive-type}.   We will discuss current challenges and possibilities (UI and API suggestions wanted!), apps being built on the platform, and related digitization efforts.&lt;br /&gt;
&lt;br /&gt;
DPLA has a transparent community and planning process; new participants are always welcome.  Half the time will be for suggestions and discussion.   Please bring proposals, problems, partnerships and possible paradoxes to discuss.&lt;br /&gt;
&lt;br /&gt;
== Introduction to SilverStripe 3.0 ==&lt;br /&gt;
 &lt;br /&gt;
* Ian Walls, University of Massachusetts Amherst, iwalls AT library DOT umass DOT edu&lt;br /&gt;
&lt;br /&gt;
SilverStripe is an open source Content Management System/development framework out of New Zealand, written in PHP, with a solid MVC structure.  This presentation will cover everything you need to know to get started with SilverStripe, including&lt;br /&gt;
* Features (and why you should consider SilverStripe)&lt;br /&gt;
* Requirements &amp;amp; Installation&lt;br /&gt;
* Model-View-Controller&lt;br /&gt;
* Key data types &amp;amp; configuration settings&lt;br /&gt;
* Modules&lt;br /&gt;
* Where to start with customization&lt;br /&gt;
* Community support and participation&lt;br /&gt;
&lt;br /&gt;
== Citation search in SOLR and second-order operators ==&lt;br /&gt;
 &lt;br /&gt;
* Roman Chyla, Astrophysics Data System, roman.chyla AT (cfa.harvad.edu|gmail.com)&lt;br /&gt;
&lt;br /&gt;
Citation search is basically about connections (Is the paper read by a friend of mine more important than others? Get me a paper read by somebody who cites many papers/is cited by many papers?), but the implementation of the citation search is surprisingly useful in many other areas.&lt;br /&gt;
&lt;br /&gt;
I will show 'guts' of the new citation search for astrophysics, it is generic and can be applied recursively to any Lucene query. Some people would call it a second-order operation because it works with the results of the previous (search) function. The talk will see technical details of the special query class, its collectors, how to add a new search operator and how to influence relevance scores. Then you can type with me: friends_of(friends_of(cited_for(keyword:&amp;quot;black holes&amp;quot;) AND keyword:&amp;quot;red dwarf&amp;quot;))&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Managing Segmented Images and Hierarchical Collections with Fedora-Commons and Solr ==&lt;br /&gt;
&lt;br /&gt;
* David Lacy, Villanova University, david DOT lacy AT villanova.edu&lt;br /&gt;
&lt;br /&gt;
Many of the resources within our digital library are split into parts -- newspapers, scrapbooks and journals being examples of collections of individual scanned pages.  In some cases, groups of pages within a collection, or segments within a particular page, may also represent chapters or articles.&lt;br /&gt;
&lt;br /&gt;
We recently devised a procedure to extract these &amp;quot;segmented resources&amp;quot; into their own objects within our repository, and index them individually in our Discovery Layer.&lt;br /&gt;
&lt;br /&gt;
In this talk I will explain how we dissected and organized these newly created resources with an extension to our Fedora Model, and how we make them discoverable through Solr configurations that facilitate browsable hierarchical relationships and field-collapsed results that group items within relevant resources.&lt;br /&gt;
&lt;br /&gt;
== Google Analytics, Event Tracking and Discovery Tools==&lt;br /&gt;
 &lt;br /&gt;
* Emily Lynema, North Carolina State University Libraries. ejlynema AT ncsu DOT edu&lt;br /&gt;
* Adam Constabaris, North Carolina State University Libraries, ajconsta AT ncsu DOT edu&lt;br /&gt;
&lt;br /&gt;
The NCSU Libraries is using Google Analytics increasingly across its website as a replacement for usage tracking via Urchin. More recently, we have also begun to use the event tracking features in Google Analytics. This has allowed us to gather usage statistics for activities that don’t initiate new requests to the server, such as clicks that hide and show already-loaded content (as in many tabbed interfaces).  Aggregating these events together with pageview tracking in Google Analytics presents a more unified picture of patron activity and can help improve design of tools like the library catalog.  While assuming a basic understanding of the use of Google Analytics pageview tracking, this presentation will start with an introduction to the event tracking capabilities that may be less widely known. &lt;br /&gt;
&lt;br /&gt;
We’ll share library catalog usage data pulled from Google Analytics, including information about  features that are common across the newest wave of catalog interfaces, such as tabbed content, Google Preview, and shelf browse. We will also cover the approach taken for the technical implementation of this data-intensive JavaScript event tracking.&lt;br /&gt;
&lt;br /&gt;
As a counterpart, we can demonstrate how we have begun to use Google Analytics event tracking in a proprietary vendor discovery tool (Serials Solutions Summon). While the same technical ideas govern this implementation, we can highlight the differences (read, challenges) inherent in utilizing this type of event tracking in vendor-owned application vs. a locally developed application.&lt;br /&gt;
&lt;br /&gt;
Along the way, hopefully you’ll learn a little about why you might (or might not) want to use Google Analytics event tracking yourself and see some interesting catalog usage stats.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2013]]&lt;/div&gt;</summary>
		<author><name>Mcritchlow</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_c4l2012_social_activities&amp;diff=11260</id>
		<title>2012 c4l2012 social activities</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_c4l2012_social_activities&amp;diff=11260"/>
				<updated>2012-02-08T00:26:24Z</updated>
		
		<summary type="html">&lt;p&gt;Mcritchlow: /* Wednesday afternoon tour */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Ideas==&lt;br /&gt;
* Woodinville distillery tour&lt;br /&gt;
** +1&lt;br /&gt;
* Seattle distillery tour&lt;br /&gt;
* Favorite local breweries&lt;br /&gt;
* Favorite local tea houses&lt;br /&gt;
* Favorite local used bookstores&lt;br /&gt;
* Visit hackerspace&lt;br /&gt;
** +1&lt;br /&gt;
&lt;br /&gt;
==Planned events==&lt;br /&gt;
&lt;br /&gt;
===Pre-Newcomer + Veterans dinner /drink-up Monday===&lt;br /&gt;
Early in town for pre-conference? &lt;br /&gt;
First time at code4lib? &lt;br /&gt;
Don't know anyone at code4lib?&lt;br /&gt;
Join fellow c4l newbies + 2nd + 3rd timers + veterans. &lt;br /&gt;
You will gain a bunch of new/veteran code4libbers in one night!&lt;br /&gt;
Sign up below (NO CAP). You can show up only for dinner or drinks or both! &lt;br /&gt;
&lt;br /&gt;
But put your name so that we have a rough idea about the number of ppl who will show up =)&lt;br /&gt;
&lt;br /&gt;
'''Plans'''&lt;br /&gt;
* When: Monday evening (2/6) &lt;br /&gt;
* For Dinner: Meet at 6PM (ish)at the hotel lobby&lt;br /&gt;
* For Drinks: show up at Hideout between 8 -10 PM for local art, fancy cocktails, or Belgian beer&lt;br /&gt;
* For Hospitality suite intro chat/hangout: show up at 10 PM - midnight? at hospitality suite&lt;br /&gt;
&lt;br /&gt;
Dinner: [http://www.yelp.com/biz/kastoori-grill-seattle Kastoori Grill -Indian &amp;amp; Himalayan/Nepalese/Tibetan (vegetarian-friendly)]&lt;br /&gt;
0.8 miles 15 min. walk&lt;br /&gt;
* Bohyun Kim - n/v (2nd-timer) (leader)&lt;br /&gt;
* Jason Clark - n/v leader&lt;br /&gt;
* Margaret Heller&lt;br /&gt;
* Sarah Johnston - n&lt;br /&gt;
* Andrea Schurr - n/v (2nd-timer)&lt;br /&gt;
* Jason Ronallo&lt;br /&gt;
* Karen Coombs - v&lt;br /&gt;
* Eric James&lt;br /&gt;
* Misty De Meo - n&lt;br /&gt;
* Keri Thompson - n&lt;br /&gt;
* Andreas Orphanides - v&lt;br /&gt;
* Tom Burton-West -v&lt;br /&gt;
* Keith Folsom - n&lt;br /&gt;
* Sam Meister - n&lt;br /&gt;
* Jen Weintraub - n&lt;br /&gt;
* Reservation made for 15. Bring cash if you can! =)&lt;br /&gt;
&lt;br /&gt;
Drinks: [http://www.yelp.com/biz/the-hideout-seattle Hideout Lounge] for local art, fancy cocktails, and Belgian beer&lt;br /&gt;
0.3 miles 8 min. walk&lt;br /&gt;
* Bohyun Kim - n/v (2nd-timer) (leader)&lt;br /&gt;
* Jason Clark - n/v leader&lt;br /&gt;
* Lisa Kurt - n&lt;br /&gt;
* Margaret Heller&lt;br /&gt;
* Andrea Schurr - n/v (2nd-timer)&lt;br /&gt;
* Anoop Atre (Would love to if back from MS visit)&lt;br /&gt;
* Heather Pitts (maybe) - n&lt;br /&gt;
* Evviva Weinraub - Hope to join up if back from MS visit)&lt;br /&gt;
* Megan Banasek -n&lt;br /&gt;
* Misty De Meo (maybe) - n&lt;br /&gt;
* Keri Thompson (definitely)&lt;br /&gt;
* David Drexler (likely) - n&lt;br /&gt;
* Andreas Orphanides - v&lt;br /&gt;
* Rebecca Jones - n&lt;br /&gt;
* Chick Markley - v&lt;br /&gt;
* Ray Henry - n&lt;br /&gt;
* Jonathan Green (likely) - n&lt;br /&gt;
* Aaron Collier - n&lt;br /&gt;
* Tim Lepczyk - n&lt;br /&gt;
&lt;br /&gt;
Hospitality suite intro chat/ hangout: just show up at the hospitality suite - no sign up required.&lt;br /&gt;
&lt;br /&gt;
===Morning Run Tuesday===&lt;br /&gt;
I (Ray Schwartz) am organizing a morning run for anyone that would like to join me.  It will be around 5 to 6 miles.  I usually run a 10 minute per mile pace. And I would like to start around 7am.  Select which days Tuesday or Wednesday or both mornings.  Choose the date you wish via this Doodle link http://www.doodle.com/3tbigutqvkda5ib8&lt;br /&gt;
&lt;br /&gt;
Link to the course map is at http://www.runningmap.com/?id=351428.&lt;br /&gt;
&lt;br /&gt;
So far 4 have signed up for both Tuesday and Wednesday.  Let's meet in the Lobby at 7am on Tuesday, and we will decide how to do Wednesday.&lt;br /&gt;
&lt;br /&gt;
===Newcomer dinner Tuesday===&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;dongles&amp;lt;/strike&amp;gt; XML.&lt;br /&gt;
&lt;br /&gt;
Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!&lt;br /&gt;
&lt;br /&gt;
'''Plans'''&lt;br /&gt;
* When: Tuesday evening (2/7) '''Note that this year's dinner is on Tuesday'''&lt;br /&gt;
* Time: 6 PM (ish) or whenever you can get your group together&lt;br /&gt;
* Mastermind (if you have any questions): [mailto:yoosebec@grinnell.edu Becky Yoose]&lt;br /&gt;
&lt;br /&gt;
''Guidelines:''&lt;br /&gt;
*Max of '''6''' per group&lt;br /&gt;
**Please, no waitlisting :(&lt;br /&gt;
*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 coders &lt;br /&gt;
***Herd folks from hotel to restaurant (know where you're going!)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Restaurants'''&lt;br /&gt;
&lt;br /&gt;
'''Restaurants within .25 miles of the hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://www.sazeracrestaurant.com/index.php Sazerac] (AWESOME happy hour menu that runs until 8)&lt;br /&gt;
* Martin Haye - n (2nd timer but it's been a ''long'' time)&lt;br /&gt;
&amp;lt;strike&amp;gt;* William Gunn - n&amp;lt;/strike&amp;gt; - Sorry I must beg out, someone may want to take my spot.&lt;br /&gt;
* Rebecca Jones - n&lt;br /&gt;
* Chick Markley - v - leader?&lt;br /&gt;
* Keri Thompson - n&lt;br /&gt;
* Andy Jackson - n&lt;br /&gt;
* Tom Burton-West -v&lt;br /&gt;
*'''capped at 6''' ''(So, who's the fearless leader of this group? ~yo_bj)''&lt;br /&gt;
&lt;br /&gt;
[http://oasiankitchen.com/ O'Asian Kitchen and Lounge]  (Asian) &lt;br /&gt;
&lt;br /&gt;
'''Restaurants between .25 miles and .5 miles of the hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://www.pikebrewing.com/index_html.shtml Pike Brewing] (local brewery, pub food)&lt;br /&gt;
We are meeting in the lobby of the hotel at 6pm.&lt;br /&gt;
* Ken Varnum - n&lt;br /&gt;
* Chad Nelson - n&lt;br /&gt;
* Ed Summers - v&lt;br /&gt;
* Tommy Ingulfsen - n&lt;br /&gt;
* Adam Wead - v or .5n&lt;br /&gt;
* Dan Coughlin - n&lt;br /&gt;
*'''capped at 6''' ''(So, who's the fearless leader of this group? ~yo_bj)''&lt;br /&gt;
&lt;br /&gt;
[http://www.rockbottom.com/ The Rock Bottom Restaurant &amp;amp; Brewery] (American)&lt;br /&gt;
It seemed like all the others were full so I thought it start this in case anyone else is as crazy unprepared as I am.&lt;br /&gt;
* Jonathan Green (jonathan at discoverygarden dot ca) - n&lt;br /&gt;
* Ed Fugikawa ( ed AT coalliance DOT org ) - n&lt;br /&gt;
* Zinthia Briceno - n (@zbriceno) &lt;br /&gt;
* David Talley - n ( dwtalley AT uw DOT edu ) -- Where to meet? Hotel main entrance, 6pm?&lt;br /&gt;
* Patrick Berry - v (@pberry) -- Lobby at 6pm sounds perfect.  I'm the short blonde guy.  I guess I will &amp;quot;lead&amp;quot; our merry band of famished folk.&lt;br /&gt;
* Al Cornish - v&lt;br /&gt;
* Tom Keays - v&lt;br /&gt;
* Andrew Pasterfield - n ( deesnutz AT gmail punto com )&lt;br /&gt;
* '''Not Taking Reservations -- Come with us at your own risk'''&lt;br /&gt;
&lt;br /&gt;
[http://www.wildginger.net/ Wild Ginger] (Asian, a bit overpriced) &amp;quot;Reservations made under Jason Clark at 6pm for 6 people. Meeting in hotel lobby around 5:45pm.&amp;quot;&lt;br /&gt;
* Jason Clark - n/v leader&lt;br /&gt;
* Tamar Sadeh - n&lt;br /&gt;
* Kevin Clarke - v&lt;br /&gt;
* Gary Thompson - n&lt;br /&gt;
* Keith Folsom - n&lt;br /&gt;
* Sarah Park - n (my Seattle friend recommended this place!)&lt;br /&gt;
&lt;br /&gt;
[http://www.thepurplecafe.com/index.html Purple Cafe] (American, Wine Bar) ''reservation made under Calvin Mah for 6:30pm for the 6 of us.  I'll be meeting in the hotel lobby at 6pm with some sort of sign.  See you then!''&lt;br /&gt;
* Calvin Mah - (leader) - v&lt;br /&gt;
* David Isaak - n&lt;br /&gt;
* Aaron Collier - n&lt;br /&gt;
* Sean Hannan - v&lt;br /&gt;
* Joshua Gomez - v&lt;br /&gt;
* Charlie Morris - n&lt;br /&gt;
* '''capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.cafepaloma.com/ Cafe Paloma] (Mediterranean) Reservation for 6:15 -- Meet in hotel lobby at 6 -- I have short white hair and will be wearing a purple jacket.&lt;br /&gt;
* Jean Rainwater (leader) - v&lt;br /&gt;
* Kelley McGrath - n&lt;br /&gt;
* Lori Robare - n&lt;br /&gt;
* Emily Lynema - v&lt;br /&gt;
* Sarah Johnston - n&lt;br /&gt;
* Sam Meister - n&lt;br /&gt;
* '''capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.thecollinspub.com/ Collins Pub] (Pub Food, great beer selection) ''Meet in the lobby at 6:15pm''&lt;br /&gt;
* Francis Kayiwa - (leader) &amp;quot;(get hold of me at first dot last name at goog as the date gets closer with your mobile)&amp;quot; v&lt;br /&gt;
* Michael Lindsey - v&lt;br /&gt;
* Dan Suchy - v&lt;br /&gt;
* David Drexler - n&lt;br /&gt;
* Laura Smart - n&lt;br /&gt;
* Heather Pitts - n&lt;br /&gt;
*'''capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.mcmenamins.com/311-six-arms-home Six Arms - McMenamins] (Pub Food &amp;amp; they brew their own beer) ''Meet in the Lobby at 6pm. I've also emailed you. --Joel''&lt;br /&gt;
* Joel Richard (richardjm AT si.edu) (leader) - v&lt;br /&gt;
* Margaret Heller - v&lt;br /&gt;
* Sibyl Schaefer (sschaefer AT rockarch . org) - v&lt;br /&gt;
* Tim Lepczyk (timlepczyk AT gmail.com) - n&lt;br /&gt;
* Ray Schwartz (schwartzr2@wpunj.edu) - v&lt;br /&gt;
* Andrea Schurr (andrea-schurr AT utc DOT edu) - v(2nd-timer)&lt;br /&gt;
* '''capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.611supreme.com/ 611 Supreme] (Crepes and Full Bar) ''Reservation for 6 at 6:30. Meet in the conference hotel lobby at 6pm. Look for the short woman in a trench coat and wide brim hat ~Becky''&lt;br /&gt;
&lt;br /&gt;
*Becky Yoose (leader) - v &lt;br /&gt;
*Cynthia Ng - n&lt;br /&gt;
*Zoe Chao - v&lt;br /&gt;
*Stephanie Collett - n (2nd-timer)&lt;br /&gt;
*Bethany Nowviskie - n&lt;br /&gt;
* Ben Shum - n&lt;br /&gt;
*'''capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.panafricamarket.com/wp/ Pan Africa Restaurant &amp;amp; Bar] (Pan African) &lt;br /&gt;
CLOSED TUESDAYS!!!!!!!!!!!!!!!!!!&lt;br /&gt;
Sorry for the confusion. I have moved everyone to Long Provincial, so that you'll have a place held in case you want it. If Long Provincial doesn't suit you, please remove your name in case someone else wants the spot. Again, I'm sorry. --Jason&lt;br /&gt;
&lt;br /&gt;
[http://longprovincial.com/ Long Provincial] Vietnamese (.7 miles from hotel; 15 minute walk)&lt;br /&gt;
&lt;br /&gt;
Reservation for 6 for 6:30 (and I have a confirmation number!). Meet in the hotel lobby at 6 to allow for a strolling pace to walk over there.&lt;br /&gt;
&lt;br /&gt;
Has a jellyfish tank.&lt;br /&gt;
&lt;br /&gt;
*Jason Ronallo (leader?) - v?&lt;br /&gt;
*Nettie Lagace - n&lt;br /&gt;
*Bohyun Kim - n/v (2nd-timer)&lt;br /&gt;
*Wendy Robertson - n&lt;br /&gt;
*Jennifer Bowen - n/v (3rd timer)&lt;br /&gt;
*James Stuart - n&lt;br /&gt;
*'''capped at six'''&lt;br /&gt;
&lt;br /&gt;
'''Restaurants between .5 and 1 mile from hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://momijiseattle.com/ Momiji] New Japanese restaurant in Seattle - [http://www.concierge.com/tools/blogs/unpacked/2011/10/momiji-seattle.html Reviewed in Concierge.com]&lt;br /&gt;
&lt;br /&gt;
* Andrew Nagy (leader) - v&lt;br /&gt;
* Cory Lown - v&lt;br /&gt;
* Tod Robbins - n&lt;br /&gt;
* Dennis Schafroth - n&lt;br /&gt;
* Tammy Allgood Wolf - n*&lt;br /&gt;
* Tim Shearer - v&lt;br /&gt;
*'''capped at six''' &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
[http://tomdouglas.com/index.php?page=palace-kitchen-dinner Palace Kitchen] (another Tom Douglas restaurant, w/ a focus on meat).  ''I have made a reservation for 6 at 8pm. Let's meet in the conference lobby at 6:30pm and make our way slowly over; we will find things to do in the interim. Look for Mike Giarlo, a man who may be holding a sign that says &amp;quot;HI I'M MIKE GIARLO&amp;quot; or otherwise shouting his name or looking confused.''&lt;br /&gt;
&lt;br /&gt;
* Mike Giarlo (leader) - v&lt;br /&gt;
* Carmen Mitchell - n&lt;br /&gt;
* Daniel Lovins - v&lt;br /&gt;
* Cary Gordon - v &lt;br /&gt;
* Declan Fleming - v&lt;br /&gt;
* Amy Unger - n&lt;br /&gt;
* (CAPPED AT SIX!)&lt;br /&gt;
&lt;br /&gt;
[http://sitkaandspruce.com/ Sitka and Spruce] (Eclectic, super-local and super-seasonal.) ''We have a reservation for 6 at 8:15pm. We'll meet in the conference lobby at 6:30 pm and head over - the owners also run [http://www.ferdinandthebar.com/home/ Bar Ferd'nand], a wine shop/bar in the same building, and we can kill time there before we eat. Look for Mark Matienzo or Hillel Arnold.''&lt;br /&gt;
&lt;br /&gt;
* Mark Matienzo (leader) - v&lt;br /&gt;
* Hillel Arnold - sophomore&lt;br /&gt;
* Devon Smith - v&lt;br /&gt;
* Derek Merleaux - sophmore&lt;br /&gt;
* Jennifer Weintraub - n&lt;br /&gt;
* Peter Green - n (2nd)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://www.yelp.com/biz/japonessa-seattle Japonessa Restaurant] (Japanese + full bar)&lt;br /&gt;
&lt;br /&gt;
''Reservations for 6 at 7:00pm - Meet in lobby at 6:15''&lt;br /&gt;
&lt;br /&gt;
* Ryan Wick (leader) - v&lt;br /&gt;
* Kate Zwaard - n&lt;br /&gt;
* Joe Atzberger - v&lt;br /&gt;
* Scott Fisher - n (2nd-timer)&lt;br /&gt;
* Anoop Atre - n&lt;br /&gt;
* Lisa Kurt - n&lt;br /&gt;
* '''capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://tomdouglas.com/index.php?page=serious-pie Serious Pie] (Tom Douglas restaurant, inventive pizzas, good local beer list). &lt;br /&gt;
&lt;br /&gt;
''No reservations for parties at Serious Pie...So, let's meet in the lobby at 6:30.  Look for a guy wearing an 'Alma' t-shirt (me).  Others out there...come and crash the 'capped at six' crowd heading to Serious Pie.'' &lt;br /&gt;
&lt;br /&gt;
* Christopher Spalding (leader) - v&lt;br /&gt;
* Robin Schaaf - n&lt;br /&gt;
* Jason Stirnaman - v&lt;br /&gt;
* Christina Morris - n&lt;br /&gt;
* Ray Henry - n&lt;br /&gt;
* Sean Purcell - n&lt;br /&gt;
* '''capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.allmenus.com/wa/seattle/204592-ballet-restaurant/menu/ Ballet] (Vietnamese)&lt;br /&gt;
&lt;br /&gt;
[http://www.kokebrestaurant.com/ Kokeb Ethiopian Restaurant] (Ethiopian) ''Let's say meet at the lobby at 6pm like everyone else. Woohoo!''&lt;br /&gt;
&lt;br /&gt;
''We have reservations for 6 at 6:45.''&lt;br /&gt;
&lt;br /&gt;
* Andreas Orphanides (leader) - v&lt;br /&gt;
* Mark Mounts - v&lt;br /&gt;
* Joe Montibello - n&lt;br /&gt;
* Justin Littman - n&lt;br /&gt;
* Ron Peterson&lt;br /&gt;
* Bobbi Fox - sophmore&lt;br /&gt;
* (CAPPED AT SIX!)&lt;br /&gt;
Crashing the [http://www.seattlerb.org/ Seattle Ruby] meetup, which meets on Capital Hill at 7:00 on Tuesdays. Eat at [http://www.yelp.com/biz/poppy-seattle Poppy] before.  Reservations for 6:15. Leaving from the hotel lobby at 5:45.  ''If you dig Ruby, come to this.  Seattle ruby produced Nokogiri, Vlad, Rubygems.org ....''&lt;br /&gt;
* Matt Zumwalt (leader) - v&lt;br /&gt;
* *Justin Coyne - n&lt;br /&gt;
* Misty De Meo - n&lt;br /&gt;
* Fumihiro Kato - n (2nd timer)&lt;br /&gt;
* Dan Brubaker Horst - n (3nd timer)&lt;br /&gt;
* Willy Mene - sophomore&lt;br /&gt;
* (CAPPED AT SIX)&lt;br /&gt;
&lt;br /&gt;
[http://tomdouglas.com/index.php?page=dahlia-lounge Dahlia Lounge] (Pacific Northwest cuisine, $$$)&lt;br /&gt;
&lt;br /&gt;
[http://www.mattsinthemarket.com/ Matt's in the Market] (Northwest Cuisine, $$$)&lt;br /&gt;
&lt;br /&gt;
[http://www.placepigalle-seattle.com/ Place Pigalle] (French)&lt;br /&gt;
&lt;br /&gt;
[http://www.chezshea.com/ Chez Shea] (French)&lt;br /&gt;
&lt;br /&gt;
[http://www.elysianbrewing.com/elysian.html Elysian Breweries and Pubs] (Pub Food)&lt;br /&gt;
&lt;br /&gt;
[http://www.mezaseattle.com/index.html Meza] (Latin Fare)&lt;br /&gt;
Have reservations for 6.45. It's about a mile from hotel. 10min bus, 30 min walk. Meet in lobby @ 6 and we'll work out bus/walk/cab. -corey&lt;br /&gt;
* Tara Robertson - n&lt;br /&gt;
* Shawn Averkamp - sophomore&lt;br /&gt;
* Corey Harper - v (leader)&lt;br /&gt;
* Shaun Ellis - sophomore&lt;br /&gt;
* Jon Stroop - fifth year senior&lt;br /&gt;
* Birkin James Diana - v (hi Jon!; hey newcomers, I'm taking the 6th slot, but, if you're stuck for a signup, plz do feel free to bump/overwrite me - seriously!)&lt;br /&gt;
* '''capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://inthebowlbistro.com/index.php In the Bowl] (Veg*n, Asian)&lt;br /&gt;
&lt;br /&gt;
[http://www.plumbistro.com/ Plumb Bistro] (Veg*n)&lt;br /&gt;
&lt;br /&gt;
[http://highlineseattle.com/ Highline] (Veg*n, bar)&lt;br /&gt;
* Jacob Reed - n&lt;br /&gt;
* Brian McBride - n&lt;br /&gt;
&lt;br /&gt;
'''Restaurants more than 1 miles from the hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://bravehorsetavern.com/ Brave Horse Tavern] (another Tom Douglas, good regional beer list, yummy food. Near South Lake Union. Would require a ride on the South Lake Union Trolley (SLUT), but it's easy to get to/use from downtown. &lt;br /&gt;
&lt;br /&gt;
[http://www.temperodobrasil.net/ Tempero do Brasil] I was excited to see Ipanema Grill 6 blocks from the hotel, unfortunately it seems to be closed for good.  So this restaurant which is a 10 minute ($15) cab ride away and which also serves Brazilian cuisine (including the ever-tasty feijoada) will have to do.  Reservation at 6:45, meet in lobby at 6:15 with a plan of getting in the taxis at about 6:30.  I'll be wearing a red and white Hawaiian shirt. &lt;br /&gt;
&lt;br /&gt;
* Robert Haschart - leader - v third year&lt;br /&gt;
* Molly Pickral - n&lt;br /&gt;
* Erik Hetzner - 2nd c4l&lt;br /&gt;
* Paul Deschner -n (where should we meet?)&lt;br /&gt;
&lt;br /&gt;
[http://flyingfishrestaurant.com/ Flying Fish] (Seafood)&lt;br /&gt;
&lt;br /&gt;
[http://www.allmenus.com/wa/seattle/3437-cafe-flora/menu/dinner/ Cafe Flora] (FANTASTIC Veg*n restaurant. Use Metro bus #11 to get there)&lt;br /&gt;
&lt;br /&gt;
[http://www.teapotvegetarianhouse.com/index.htm Teapot Vegetarian House] (Veg*n, Asian)&lt;br /&gt;
&lt;br /&gt;
[http://spaceneedle.com/restaurant/ Space Needle] (American, Pricy; but what the heck, listed it anyway for those who want the experience)&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Get Lamp&amp;quot; viewing Tuesday (9 PM) ===&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Tuesday, February 7, 9 PM or shortly after -Courtyard Ballroom&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Adam Wead and Michael Klein are organizing a viewing of [http://www.getlamp.com/ Get Lamp: The Text Adventure Documentary]&lt;br /&gt;
&lt;br /&gt;
It's not about Linux, Apache, MySQL or PHP, but if you don't have a one, you might get eaten by a grue.&lt;br /&gt;
&lt;br /&gt;
If there is additional interest, there may be another viewing this week.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Morning Run Wednesday===&lt;br /&gt;
I (Ray Schwartz) will not be running on Wednesday.  Though several others have said that they will meet at 7am in the Hotel Lobby.  I would recommend to walk straight down west to the water front and turn right-heading north, following the pedestrian path.  It goes on or some miles, so it is a good choice.&lt;br /&gt;
&lt;br /&gt;
===Veg*n Dinner Wednesday===&lt;br /&gt;
&lt;br /&gt;
We'll pick a place with lots of veg*n options to go eat Wednesday for dinner. Vegetarians and non-vegetarians welcome.&lt;br /&gt;
&lt;br /&gt;
*[http://lovinghut.us/seattle/index.html Loving Hut] Modest price. 1 mile from hotel. Will do bill splitting if we let them know up front. &lt;br /&gt;
&lt;br /&gt;
Talked with Loving Hut and made a reservation for 15 for 6:30. Meet in the hotel lobby at 6.&lt;br /&gt;
&lt;br /&gt;
*Jason Ronallo (jronallo AT gmail.com)&lt;br /&gt;
*Sean Hannan&lt;br /&gt;
*Ed Summers&lt;br /&gt;
*James Stuart&lt;br /&gt;
*Bohyun Kim&lt;br /&gt;
*Bethany Nowviskie&lt;br /&gt;
*Margaret Heller&lt;br /&gt;
*Laura Smart&lt;br /&gt;
*Sibyl Schaefer&lt;br /&gt;
*Cynthia Ng&lt;br /&gt;
*Andrea Shurr&lt;br /&gt;
*Eric James&lt;br /&gt;
*Birkin James Diana&lt;br /&gt;
*Sheree F&lt;br /&gt;
*Misty De Meo&lt;br /&gt;
*Reservation is for 15.&lt;br /&gt;
&lt;br /&gt;
===Meat-Up Dinner Wednesday===&lt;br /&gt;
&lt;br /&gt;
RIP Meat-Up. Going to Amazon for hurricanes.&lt;br /&gt;
&lt;br /&gt;
(if you do not find a suitable burger joint, there are also some top-notch steakhouses in Seattle. Both the Metropolitan Grill and El Gaucho are delightful if folks are OK with $50 steaks. Just FYI, not trying to hijack your meat-up, Cary!. -mjgiarlo)&lt;br /&gt;
&lt;br /&gt;
===Evergreen/Koha and friends dinner Wednesday===&lt;br /&gt;
Put your name and any food limitations, or suggestions of places to go. We'll figure where we're going later. For now, let's assume we're meeting in the hotel lobby at 6pm.&lt;br /&gt;
&lt;br /&gt;
Since I don't see any seafood restaurant for dinners I'm (Anoop) suggesting this place and can make reservations:&lt;br /&gt;
 &lt;br /&gt;
Six Seven Restaurant &amp;amp; Lounge [http://www.opentable.com/six-seven-restaurant-and-lounge?scpref=170  | OpenTable entry]&lt;br /&gt;
2411 Alaskan Way, Pier 67&lt;br /&gt;
Seattle, WA 98121&lt;br /&gt;
&lt;br /&gt;
* Tara Robertson&lt;br /&gt;
* Chris Sharp&lt;br /&gt;
* Tod Robbins - n&lt;br /&gt;
* Ben Shum&lt;br /&gt;
* Anoop Atre - n&lt;br /&gt;
* Matt Carlson - n&lt;br /&gt;
* Luis Baquera - n&lt;br /&gt;
* Larry Baerveldt (someplace with beer, natch)&lt;br /&gt;
* David Drexler -n (if there's space)&lt;br /&gt;
&lt;br /&gt;
===[[2012 Craft Brew Drinkup|Craft Brew Drinkup]], Wednesday (9 PM)===&lt;br /&gt;
&lt;br /&gt;
'''Wednesday, February 8, 9 PM-ish -Hospitality Suite'''&lt;br /&gt;
&lt;br /&gt;
Like good beer? Bring some in your luggage! Some of us are planning to bring some of our favorite local, special, or homebrewed beers to share. Interested? Sign up on the [[2012 Craft Brew Drinkup]] page!&lt;br /&gt;
&lt;br /&gt;
'''PLEASE POST WILLING TO HOST ON THE [[2012 Craft Brew Drinkup|DRINKUP PAGE]]''' :)&lt;br /&gt;
&lt;br /&gt;
===Dim Sum Lunch Thursday===&lt;br /&gt;
&lt;br /&gt;
For those of you staying in town after the last session on Thursday, [http://oasiankitchen.com/ O'Asian Kitchen] has dim sum service during the weekdays. Meet up around 12:35, meeting location tba. Bring cash for easier bill splitting.&lt;br /&gt;
&lt;br /&gt;
*Becky Yoose&lt;br /&gt;
* Declan Fleming - love me some Dim Sum!&lt;br /&gt;
* Adam Wead&lt;br /&gt;
* Heather Pitts&lt;br /&gt;
* Sibyl Schaefer&lt;br /&gt;
* Anoop Atre&lt;br /&gt;
* Dan Suchy&lt;br /&gt;
* Carmen Mitchell&lt;br /&gt;
* Tara Robertson&lt;br /&gt;
* Ray Schwartz&lt;br /&gt;
* Cynthia Ng&lt;br /&gt;
* Corey Harper&lt;br /&gt;
* Joshua Gomez&lt;br /&gt;
* Cary Gordon&lt;br /&gt;
* Mike Giarlo&lt;br /&gt;
* Joe Atzberger&lt;br /&gt;
* Dileshni Jayasinghe&lt;br /&gt;
* Ryan Wick&lt;br /&gt;
* Dennis Schafroth&lt;br /&gt;
* Mike Durbin&lt;br /&gt;
* Ben Shum&lt;br /&gt;
* Dan Chudnov&lt;br /&gt;
&lt;br /&gt;
==Social Map - places of interest==&lt;br /&gt;
[http://g.co/maps/4m5pk Code4lib 2012 - Seattle - social events, hangouts, and places to see]&lt;br /&gt;
&lt;br /&gt;
==Seattle Events Feb 5-9==&lt;br /&gt;
===Saturday, February 4, 2012===&lt;br /&gt;
In case you are showing up really early.&lt;br /&gt;
* Belgianfest: http://www.washingtonbeer.com/belgianfest/&lt;br /&gt;
===Sunday, February 5, 2012===&lt;br /&gt;
* Clinton Fearon &amp;amp; The Boogie Brown Band/Live Wyya/Adrian Xavier/Selecta Raiford/DJ Courtland, Neumos: http://neumos.com/neumos.php&lt;br /&gt;
* Michael The Blind/The Els, Skylark: http://www.skylarkcafe.com/&lt;br /&gt;
* Addaura/Alda/Hallow, Comet&lt;br /&gt;
* &amp;quot;I Am My Own Wife&amp;quot; 7:30pm at Seattle Repertory Theatre (Seattle Center) http://www.seattlerep.org/Plays/1112/IM/&lt;br /&gt;
* Science Fiction + Fantasy short film festival, Encore screening. http://www.empmuseum.org/programs/index.asp?categoryID=216&lt;br /&gt;
&lt;br /&gt;
===Monday, February 6, 2012===&lt;br /&gt;
* Silent Movie Mondays:  Last Command 1928, http://stgpresents.org/artists/?artist=1829#, Show at 7:00pm, The Paramount Theatre $10&lt;br /&gt;
This all-classic film series, First Oscars, is accompanied by live music from the historic Mighty Wurlitzer organ, one of the last three remaining organs of its kind to reside in its original environment, played by critically acclaimed organist Jim Riggs.&lt;br /&gt;
&lt;br /&gt;
===Tuesday, February 7, 2012===&lt;br /&gt;
* Lionize/Maylene &amp;amp; The Sons Of Disaster, El Corazon: http://elcorazonseattle.com/&lt;br /&gt;
* The Pulltab Playboys/Rachel Lyn Harrington &amp;amp; The Knock Outs/The James Low Western Front, Sunset: http://sunsettavern.com/&lt;br /&gt;
* Twin Sister, Vera: http://theveraproject.org/shows/&lt;br /&gt;
* The Features, Chop Suey: http://www.chopsuey.com/&lt;br /&gt;
* Wilco/White Denim, Paramount Theatre: http://stgpresents.org/&lt;br /&gt;
* &amp;quot;I Am My Own Wife&amp;quot; 7:30pm at Seattle Repertory Theatre (Seattle Center) http://www.seattlerep.org/Plays/1112/IM/&lt;br /&gt;
* Intro to Arduino Workshop, 7pm at Metrix Create Space http://metrixcreatespace.com/&lt;br /&gt;
&lt;br /&gt;
===Wednesday, February 8, 2012===&lt;br /&gt;
* The Golden Blondes/The Jet Age/Mr. Drinx &amp;amp; The Pot Heads, Sunset: http://sunsettavern.com/&lt;br /&gt;
* Pipsisewah/The Chasers/The Magic Mirrors, Tractor: http://www.tractortavern.com/ &lt;br /&gt;
* Dengue Fever vs Secret Chiefs 3, Moe Bar http://bit.ly/yJtfXv  (how could you pass the opportunity to see someone play this thing :http://bit.ly/wB5AgZ&lt;br /&gt;
* Amazon Tech in Seattle is having an open house next Wednesday at 5:30 PM with Werner Vogels and David Friedberg of the Climate Corporation. https://aws.amazon.com/amazon-open-house-february-2012/ ([http://g.co/maps/adpnt map])&lt;br /&gt;
&lt;br /&gt;
===Thursday, February 9, 2012===&lt;br /&gt;
* SAM Opening - Gauguin and Polynesia: An Elusive Paradise: http://www.seattleartmuseum.org/gauguin&lt;br /&gt;
* The Jayhawks, Neptune Theater: http://stgpresents.org/&lt;br /&gt;
* Digital Leather, Comet &lt;br /&gt;
* Savani World Quintet/Super Sones, Columbia City Theater: http://www.columbiacitytheater.com/&lt;br /&gt;
* Blvd Park {album release}/Nettle Honey/Creeping Time, Tractor: http://www.tractortavern.com/&lt;br /&gt;
* Eleanor Friedberger, Crocodile: http://thecrocodile.com/index.html&lt;br /&gt;
&lt;br /&gt;
===Ongoing Events===&lt;br /&gt;
* Seattle Art Museum: Tours are every Saturday &amp;amp; Sunday at noon, and the First Thursday of every month at 10:30, 11:30 am, 12:30 &amp;amp; 1:30 pm.&lt;br /&gt;
* EMP:  Exhibits on display include: Battlestar Galactica, Nirvana, Avatar, and Can’t Look Away: The Lure of Horror Film&lt;br /&gt;
* Teatro ZinZanni: ¡Caliente! http://dreams.zinzanni.org/&lt;br /&gt;
* Pacific NW Ballet: performing Don Quixote at McCaw Hall http://www.pnb.org/&lt;br /&gt;
* Oklahoma!, Sunday matinee and nightly: 5th Avenue Theatre, 1308 Fifth Avenue http://www.5thavenue.org/show/oklahoma&lt;br /&gt;
&lt;br /&gt;
==Local events/places==&lt;br /&gt;
* Metrix Create Space&lt;br /&gt;
* Ada's Technical Books&lt;br /&gt;
* Northwest Outdoor Center&lt;br /&gt;
* Center for Wooden Boats&lt;br /&gt;
* Empty Sea Studios acoustic music&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Local Beer Places==&lt;br /&gt;
* Map of [http://beermapping.com/maps/citymaps.php?m=seattle#lat=47.66723703450515&amp;amp;lng=-122.28263854980469&amp;amp;z=5 beer venues] maintained at Beermapping.com.&lt;br /&gt;
* List of [http://www.washingtonbeer.com/breweries/seattle-king-co/ local breweries] ([http://maps.google.com/maps/ms?hl=en&amp;amp;ie=UTF8&amp;amp;msa=0&amp;amp;msid=201783184139227541123.0004813e64758434cb054&amp;amp;source=embed&amp;amp;ll=47.558921,-122.106171&amp;amp;spn=0.442982,1.234589&amp;amp;z=10&amp;amp;source=embed map]) maintained by the Washington Beer Commission&lt;br /&gt;
* Map of [http://www.ratebeer.com/Places/RegionMap.asp?rid=7600 beer venues] maintained by Ratebeer.com.&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
[http://orbiscascade.org/index/c4l-things-to-do-in-seattle Things to do in Seattle, from the hosts]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Tour of the Seattle Public Library==&lt;br /&gt;
&lt;br /&gt;
===Tuesday breakout session 3-4pm - max 20 ppl===&lt;br /&gt;
&lt;br /&gt;
Meet by the coffee urns, leaving at 2:55pm (10% off at the gift shop if you mention that you are attending code4lib)&lt;br /&gt;
&lt;br /&gt;
* Tara Robertson&lt;br /&gt;
* Bohyun Kim&lt;br /&gt;
* Shirley Lew&lt;br /&gt;
* Margaret Heller&lt;br /&gt;
* Ben Shum&lt;br /&gt;
* Chris Sharp&lt;br /&gt;
* Cynthia Ng&lt;br /&gt;
* Megan Banasek&lt;br /&gt;
* Chris Beer&lt;br /&gt;
* Peter Murray&lt;br /&gt;
* Bobbi Fox&lt;br /&gt;
* Joe Montibello&lt;br /&gt;
* Tim Lepczyk&lt;br /&gt;
* Mark Mounts&lt;br /&gt;
* Robin Dean&lt;br /&gt;
* Robert Haschart&lt;br /&gt;
* Zoe Chao&lt;br /&gt;
* Shawn Averkamp&lt;br /&gt;
&lt;br /&gt;
More tour may come later. Stay tuned! &lt;br /&gt;
&lt;br /&gt;
Jeff Christensen 206-387-4659&lt;br /&gt;
&lt;br /&gt;
centaltours@spl.org&lt;br /&gt;
&lt;br /&gt;
===Wednesday afternoon tour===&lt;br /&gt;
Tour on Tuesday was nice, but less of a &amp;quot;behind the scenes&amp;quot; experience than I'd hoped. The tour guide talked a bit about the building, architecture and some of the design aspects that worked (and didn't). Unfortunately the Wed tour will not include the automatic materials sorting room. Sign up, if there's enough interest the Wed tour will go ahead. Again, max 20 people.&lt;br /&gt;
&lt;br /&gt;
Also, Wednesday needs a group wrangler. &lt;br /&gt;
&lt;br /&gt;
* Anoop Atre&lt;br /&gt;
* Sean Chen&lt;br /&gt;
* Andrew Pasterfield&lt;br /&gt;
* Ed Fugikawa&lt;br /&gt;
* Jacob Reed&lt;br /&gt;
* Brian McBride&lt;br /&gt;
* Calvin Mah&lt;br /&gt;
* Duncan Barth&lt;br /&gt;
* Molly Pickral&lt;br /&gt;
* Jean Rainwater&lt;br /&gt;
* Matt Critchlow&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Mcritchlow</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=During_the_Conference_Volunteers&amp;diff=10416</id>
		<title>During the Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=During_the_Conference_Volunteers&amp;diff=10416"/>
				<updated>2012-01-25T23:57:03Z</updated>
		
		<summary type="html">&lt;p&gt;Mcritchlow: /* Registration Desk Schedule */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;code4lib 2012 Volunteers&lt;br /&gt;
&lt;br /&gt;
== Hospitality Suite Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee makes arrangements for any hospitality suite amenities (technology, snacks, games, icebreakers...) we may want&lt;br /&gt;
&lt;br /&gt;
* Mike Giarlo -- Penn State [Glad to be a keyholder, room-sitter, and general tidier-upper]&lt;br /&gt;
* Tom Johnson -- Oregon State University&lt;br /&gt;
* Lisa Kurt [lkurt at unr dot edu]-- University of Nevada, Reno&lt;br /&gt;
* Carmen Mitchell -- California State University San Marcos&lt;br /&gt;
* Declan Fleming -- UCSD&lt;br /&gt;
* Becky Yoose -- Grinnell College&lt;br /&gt;
* Devon Smith &lt;br /&gt;
&lt;br /&gt;
== Welcome Wagon Committee ==&lt;br /&gt;
&lt;br /&gt;
Offers conference newcomers an opportunity to self-identify; offers oldtimers an opportunity to meet newcomers. May also want to constitute a year-round variation for #code4lib.&lt;br /&gt;
&lt;br /&gt;
* Becky Yoose(b.yoose at gmail dot com) -- Grinnell College&lt;br /&gt;
* Bohyun Kim(kimb at fiu dot edu) -- Florida International University&lt;br /&gt;
* Jason Clark (jaclark at montana dot edu) Montana State University&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
Responsible for non-IRC social networking presence.&lt;br /&gt;
&lt;br /&gt;
*Rowena McKernan (rmckernan at whatcom dot ctc dot edu) ~ Whatcom Community College&lt;br /&gt;
&lt;br /&gt;
== IRC Evangelists ==&lt;br /&gt;
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.&lt;br /&gt;
&lt;br /&gt;
* Sam Kome (skome) Claremont Colleges&lt;br /&gt;
* Gabriel Farrell (gsf) (gsf747@gmail.com) Drexel University&lt;br /&gt;
* Michael Klein (mbklein) (mbklein@gmail.com) Stanford University&lt;br /&gt;
* Jon Gorman University of Illinois&lt;br /&gt;
&lt;br /&gt;
== IRC Access ==&lt;br /&gt;
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful.&lt;br /&gt;
&lt;br /&gt;
* Michael B. Klein -- emailed Freenode with IP block for conference.&lt;br /&gt;
* Cary Gordon (highermath) (cgordon at chillco.com) -- The Cherry Hill Company&lt;br /&gt;
&lt;br /&gt;
== Video Committee ==&lt;br /&gt;
Video archiving and video streaming possibilities.&lt;br /&gt;
&lt;br /&gt;
* Corey Harper corey dot harper gmail&lt;br /&gt;
* Shaun Ellis shaune@princeton.edu&lt;br /&gt;
* Cary Gordon (cgordon at chillco.com) -- The Cherry Hill Company&lt;br /&gt;
&lt;br /&gt;
==Registration Desk Volunteers==&lt;br /&gt;
We need 1-2 volunteers to hang out at the registration desk for 2-hour shifts.  Also on Monday and Tuesday, an additional volunteer with wireless access knowledge would be helpful on the Registration Desk to answer tech questions.&lt;br /&gt;
&lt;br /&gt;
* Dan Suchy (dansuchy at gmail) -- UC San Diego&lt;br /&gt;
* Doris Munson (dmunson at ewu.edu) -- Eastern Washington University&lt;br /&gt;
* Tod Robbins (todd.d.robbins at gmail) -- University of Washington&lt;br /&gt;
&lt;br /&gt;
===Registration Desk Schedule===&lt;br /&gt;
Monday&lt;br /&gt;
7-8 am&lt;br /&gt;
* Bobbi Fox&lt;br /&gt;
*&lt;br /&gt;
* (wireless expert)&lt;br /&gt;
Monday 8-9 am&lt;br /&gt;
* Bobbi Fox&lt;br /&gt;
*&lt;br /&gt;
* (wireless expert)&lt;br /&gt;
&lt;br /&gt;
Monday 9-10 am&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
Tuesday&lt;br /&gt;
7-8 am&lt;br /&gt;
* Dan Suchy (bring him coffee)&lt;br /&gt;
* Matt Critchlow&lt;br /&gt;
* (wireless expert)&lt;br /&gt;
Tuesday 8-9 am&lt;br /&gt;
* Dan Suchy (bring him coffee)&lt;br /&gt;
* Matt Critchlow&lt;br /&gt;
* (wireless expert)&lt;br /&gt;
Tuesday 9-10 am&lt;br /&gt;
* &lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
Tuesday AM&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
Tuesday PM&lt;br /&gt;
* Peter Murray&lt;br /&gt;
&lt;br /&gt;
Wednesday AM&lt;br /&gt;
* Becky Yoose&lt;br /&gt;
&lt;br /&gt;
Wednesday PM&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
Thursday AM&lt;br /&gt;
* Cynthia Ng&lt;br /&gt;
&lt;br /&gt;
== Microphone Runners==&lt;br /&gt;
&lt;br /&gt;
Run wireless handheld microphones to audience members asking questions.&lt;br /&gt;
Ask Anything Session: Wed. 11:15-12&lt;br /&gt;
*Jeanne Kliewer (jkliewer at emporia dot edu) Emporia State University&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
== Session Timer Volunteers ==&lt;br /&gt;
&lt;br /&gt;
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop with a stopwatch program).&lt;br /&gt;
&lt;br /&gt;
* Ann Gleason (amwhit24 at uw dot edu) - University of Washington -- Not registered.&lt;br /&gt;
* Carmen Mitchell (carmenmitchell at gmail dot com) - California State University San Marcos&lt;br /&gt;
* Tod Robbins (todd.d.robbins at gmail) - University of Washington -- Not registered.&lt;br /&gt;
&lt;br /&gt;
'''Schedule for Session Timers'''&lt;br /&gt;
&lt;br /&gt;
Tuesday AM&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
Tuesday PM&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
Wednesday AM&lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
Wednesday PM&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
Thursday AM&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
== Raffles ==&lt;br /&gt;
* Kyle Banerjee (calling awardees)&lt;br /&gt;
* (backup)&lt;br /&gt;
* Michael B. Klein, Stanford University (mbklein@gmail.com) (program)&lt;/div&gt;</summary>
		<author><name>Mcritchlow</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_preconference_proposals&amp;diff=10234</id>
		<title>2012 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_preconference_proposals&amp;diff=10234"/>
				<updated>2012-01-12T23:19:40Z</updated>
		
		<summary type="html">&lt;p&gt;Mcritchlow: /* Microsoft Campus Visit */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Proposals for 2012 Code4LibCon Preconferences=&lt;br /&gt;
Proposals closed Sunday, November 20, 2011, so we can finalize the list and add them to registration! (The deadline for preconference proposals has passed.)&lt;br /&gt;
&lt;br /&gt;
Spaces available: main meeting room (max 275) + 5 breakout rooms (max 30-50). &lt;br /&gt;
&lt;br /&gt;
'''Please include a &amp;quot;Contact/Responsible Individual&amp;quot; name and email address so we know who is willing to put on the proposed precon.&lt;br /&gt;
'''&lt;br /&gt;
==Full Day==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Hacking Content ===&lt;br /&gt;
&lt;br /&gt;
What is the future of getting library information and resources into users’ hands at the right time and with appropriate context and relevancy.  Learning management systems, library guides, Web-scale discovery systems-plenty of tools to choose from and still we see lots of opportunities for improvement. Let’s pick them apart and brainstorm ideas for projects that could address weaknesses in one or all of these systems. If you’re interested in these issues, challenges and conundrums join us for a day of thinking, dreaming and scheming. All skill sets and backgrounds needed. &lt;br /&gt;
&lt;br /&gt;
Speakers/Facilitators will be:&lt;br /&gt;
 - Thom Cox - Manager of Library Information Technology Services - Tufts University&lt;br /&gt;
 - Ken Varnum – Web Systems Manager - University of Michigan Libraries&lt;br /&gt;
 - Evviva Weinraub – Director, Emerging Technologies and Services - Oregon State University Libraries &lt;br /&gt;
&lt;br /&gt;
Contact:  Margaret Mellinger - margaret dot mellinger at oregonstate dot edu&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
*David Uspal (david DOT uspal AT villanova DOT edu)&lt;br /&gt;
*Tammy Allgood Wolf&lt;br /&gt;
&lt;br /&gt;
=== Developing applications using REST web services ===&lt;br /&gt;
&lt;br /&gt;
Been hearing about web services but don’t know where to start to build something? Have you built applications that use read services but are stumped by OAuth, Content Negotiation and HTTP Headers? Come dig in and learn how to build applications that interact with both read and write REST services. We’ll cover the basic principles and practices of REST services and discuss the Atom Publishing Protocol as a REST service and its extensibility. The group will examine and test the CouchDB HTTP API by building a simple list creation tool. You’ll learn how OCLC’s platform web services leverage Atom to expose the data and business processes from OCLC’s library systems. By the end of the session, you’ll know the basic principles of REST services, be able to perform Create, Read, Update and Delete operations via REST and be able to authenticate to REST services via API keys and OAuth.&lt;br /&gt;
&lt;br /&gt;
Come ready to learn and code!&lt;br /&gt;
&lt;br /&gt;
Presenter: Karen Coombs - coombsk at oclc dot org&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
*Sam Kome&lt;br /&gt;
*Ray Schwartz&lt;br /&gt;
*Jim Robinson&lt;br /&gt;
*David Bucknum&lt;br /&gt;
*Jean Rainwater&lt;br /&gt;
*Laney McGlohon&lt;br /&gt;
*Joshua Gomez&lt;br /&gt;
*Wayne Schneider&lt;br /&gt;
*Andy Kohler&lt;br /&gt;
&lt;br /&gt;
==Half Day Morning==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Linkfest ===&lt;br /&gt;
&lt;br /&gt;
We've had talks and sessions galore about Linked Data at code4lib in past years.  Let's focus on linking.  Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web.  At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there.  May a kajillion links bloom!&lt;br /&gt;
&lt;br /&gt;
If you need an &amp;quot;intro to linked data&amp;quot; we can prep a good list of readings/talks to review before you come.  But please come ready to link!&lt;br /&gt;
&lt;br /&gt;
Organizer type person:  Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
*Becky Yoose&lt;br /&gt;
*Tom Johnson&lt;br /&gt;
*Ed Summers&lt;br /&gt;
* bernardo gomez ( bgomez at emory dot edu )&lt;br /&gt;
* William Gunn&lt;br /&gt;
* Jason Ronallo&lt;br /&gt;
* Keri Thompson&lt;br /&gt;
* David Lacy&lt;br /&gt;
* Corey A Harper&lt;br /&gt;
* Matt Phillips (mphillips@law.harvard.edu)&lt;br /&gt;
* Declan Fleming&lt;br /&gt;
&lt;br /&gt;
=== What's New in Solr ===&lt;br /&gt;
&lt;br /&gt;
This session will bring folks up to speed on the latest developments in Lucene and Solr.  There's always a lot of new capabilities as well as tips and tricks on using Solr in clever and powerful ways.  &lt;br /&gt;
&lt;br /&gt;
Presenter: Erik Hatcher - erik . hatcher @ lucidimagination dot com&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
* &amp;quot;Gabriel Farrell&amp;quot; &amp;lt;gsf24@drexel.edu&amp;gt;&lt;br /&gt;
* &amp;quot;Erik Hetzner&amp;quot; &amp;lt;erik.hetzner AT ucop BORK edu&amp;gt;&lt;br /&gt;
* &amp;quot;Kevin S. Clarke&amp;quot; &amp;lt;ksclarke@gmail&amp;gt;&lt;br /&gt;
* &amp;quot;Michael B. Klein&amp;quot; &amp;lt;mbklein@gmail&amp;gt;&lt;br /&gt;
* Demian Katz (demian DOT katz AT villanova DOT edu)&lt;br /&gt;
* &amp;quot;Mark Mounts&amp;quot; &amp;lt;mark.mounts@dartmouth.edu&amp;gt;&lt;br /&gt;
* Anoop Atre ~ anoop.atre AT mnsu . edu&lt;br /&gt;
* David Isaak &amp;lt;david.isaak@kpchr.org&amp;gt;&lt;br /&gt;
* John Pillans &amp;lt;jpillan@indiana.edu&amp;gt;&lt;br /&gt;
* John Wynstra (john.wynstra@uni.edu)&lt;br /&gt;
&lt;br /&gt;
==Half Day Afternoon==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Git -r done === &lt;br /&gt;
&lt;br /&gt;
A session to cover all things Git, everyone's favorite distributed version control system.  This session should cover a little bit of the history of Git, how it works, and how it's different than other version controls systems like SVN.  Practical application should also be covered, including how to clone existing repos and contribute code back to them, how to host your own repository, and best practices for setting up a distributed network.&lt;br /&gt;
&lt;br /&gt;
Looking for attendees with real-life Git experience to share it, so we can all broaden our understanding of possible use-cases and nifty advanced features.&lt;br /&gt;
&lt;br /&gt;
Coordinator:  Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com&lt;br /&gt;
&lt;br /&gt;
Helper: Cary Gordon, Cherry Hill Company, @highermath / cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
* Patrick Berry (pberry@csuchico.edu)&lt;br /&gt;
* Chris Sharp (csharp@georgialibraries.org)&lt;br /&gt;
* Matt Critchlow (mcritchlow@ucsd.edu)&lt;br /&gt;
* Peter Murray (Peter.Murray@lyrasis.org)&lt;br /&gt;
* Margaret Heller (mheller@dom.edu)&lt;br /&gt;
* Kevin S. Clarke (ksclarke@gmail)&lt;br /&gt;
* Michael B. Klein (mbklein@gmail)&lt;br /&gt;
* Demian Katz (demian DOT katz AT villanova DOT edu)&lt;br /&gt;
* Benjamin Shum (bshum@biblio.org)&lt;br /&gt;
* Sibyl Schaefer (sschaefer@rockarch.org)&lt;br /&gt;
* Tammy Allgood Wolf (tammy.allgood@asu.edu)&lt;br /&gt;
* Chad Nelson (cnelson17 AT gsu DOT edu)&lt;br /&gt;
* Lisa Kurt (lkurt@unr.edu)&lt;br /&gt;
* Matt Phillips (mphillips@law.harvard.edu)&lt;br /&gt;
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)&lt;br /&gt;
* John Wynstra (john.wynstra@uni.edu)&lt;br /&gt;
* Declan Fleming&lt;br /&gt;
&lt;br /&gt;
=== Blacklight ===&lt;br /&gt;
&lt;br /&gt;
This session will be walk-through of the architecture of Blacklight and what we have been improving since the rails 3 upgrade.  In addition to the architecture of the software, we will also briefly discuss the architecture of the Blacklight community and what has made it successful so far.&lt;br /&gt;
&lt;br /&gt;
For part of the session we will install Blacklight live and get it up and running.  This install demo will include a How-To on basic customizations in Blacklight using a test-driven approach (one of the cornerstones of the Blacklight community).&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;
Presenters: Jessie Keck, Stanford University - jkeck at stanford dot edu | Molly Pickral, University of Virginia - mpc3c at virginia dot edu&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
* bernardo gomez ( bgomez at emory dot edu )&lt;br /&gt;
* Mark Mounts &amp;lt;mark.mounts@dartmouth.edu&amp;gt;&lt;br /&gt;
* Sibyl Schaefer (sschaefer@rockarch.org)&lt;br /&gt;
* John Pillans (jpillan@indiana.edu)&lt;br /&gt;
* Mang Sun (mang.dot sun at rice dot edu)&lt;br /&gt;
&lt;br /&gt;
=== DACS and EAD Overview ===&lt;br /&gt;
&lt;br /&gt;
This session will look at what DACS (Describing Archives: a Content Standard) is and describe the ten required elements.  Then there will be an overview of what EAD is, how it works, and the required elements.  The final part will be a practice session on taking a paper finding aid and coding it using DACS and EAD.&lt;br /&gt;
&lt;br /&gt;
Presenter:  Doris Munson, Eastern Washington University, dmunson at ewu dot edu&lt;br /&gt;
(please feel free to contact me if you are interested in being a co-presenter)&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
* Francis Kayiwa ( kayiwa@ YouEyeSee dot edu )&lt;br /&gt;
* Carmen Mitchell (carmenmitchell at gmail dot com)&lt;br /&gt;
&lt;br /&gt;
=== [[Digging into metadata: context, code, and collaboration]] ===&lt;br /&gt;
&lt;br /&gt;
Working with library/archival metadata is difficult. This preconference will tackle pressing questions and will show some of the intricacies of metadata (including AACR2/MARC) with exercises to demonstrate why inconsistencies exist in the data. What steps can the cataloging &amp;amp; metadata community take to help improve the quality of this data?  What tools &amp;amp; techniques could help?  Rules have evolved over time leaving dirty legacy data.  Systems have impacted--and will continue to impact--data structure &amp;amp; design.  How can this data be aggregated and refined for use in a new emerging data environments?  What assumptions can safely be made and when do you need to inquire about local practice?  We will end with a hack-fest where you can ask questions of experienced catalogers and get help with your metadata related problems.  Bring your laptops and data.   &lt;br /&gt;
&lt;br /&gt;
Person Herder: Becky Yoose, Grinnell College, yoosebec at grinnell dot edu&lt;br /&gt;
&lt;br /&gt;
Collaborators/Facilitators: Corey Harper, New York University - corey dot harper at nyu dot edu | Shana L. McDanold, University of Pennsylvania - 	&lt;br /&gt;
mcdanold at pobox dot upenn dot edu  | Laura Smart, Caltech - laura at library dot caltech dot edu&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
* Jen Weintraub (jweintraub@library.ucla.edu)&lt;br /&gt;
* Peter Green (pmgreen@princeton.edu)&lt;br /&gt;
* David Isaak (david.isaak@kpchr.org)&lt;br /&gt;
* Alex Rolfe (arolfe@georgefox.edu)&lt;br /&gt;
&lt;br /&gt;
=== &amp;quot;Geo&amp;quot; ===&lt;br /&gt;
This session will explore, we hope collaboratively, the presentation of objects on maps.  There will be a section on workflow, a section on discovering objects via &amp;quot;geobrowse,&amp;quot; a section discovery of objects via &amp;quot;geosearch,&amp;quot; and an exploration of the discovery and presentation of geo-referenced images (e.g. historic maps). There will be open discussion on other approaches to map-based discovery.  Emphasis will be placed on simplicity of workflow and implementation.  Technologies include: Atom, Django, Solr, and OpenLayers.  &lt;br /&gt;
&lt;br /&gt;
Presenters:  Mike Graves, UNC Chapel Hill, gravm at email dot unc dot edu; Tim Shearer, UNC Chapel Hill, tshearer at email dot unc dot edu&lt;br /&gt;
(please feel free to contact Tim if you are interested in being a co-presenter)&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
* &amp;quot;Gabriel Farrell&amp;quot; &amp;lt;gsf24@drexel.edu&amp;gt;&lt;br /&gt;
* Anoop Atre ~ anoop.atre AT mnsu . edu&lt;br /&gt;
* Chad Nelson (cnelson17 AT gsu DOT edu)&lt;br /&gt;
* Jason Casden (jmcasden AT ncsu DOT edu&lt;br /&gt;
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)&lt;br /&gt;
&lt;br /&gt;
== Half-day Evening ==&lt;br /&gt;
&lt;br /&gt;
=== Microsoft Campus Visit ===&lt;br /&gt;
Join us for a trip across Lake Washington to Microsoft Headquarters.  Bus will depart from the conference hotel at 4:15pm on Monday. We will visit the Microsoft Home and the Envisioning Lab.  The we'll head over to Microsoft Research for drinks and appetizers, and you'll see some great demos of some cool new (and free!) technologies coming out of MSR.  Bus will get back to hotel by 9:00pm, plenty of time to hit a pub.  You'll learn about:&lt;br /&gt;
&lt;br /&gt;
1. Layerscape -[http://communities.worldwidetelescope.org/]&lt;br /&gt;
&lt;br /&gt;
2. ChronoZoom - [http://research.microsoft.com/chronozoom/]&lt;br /&gt;
&lt;br /&gt;
3. F# - [http://www.tryfsharp.org]&lt;br /&gt;
&lt;br /&gt;
4. Microsoft Academic Search - [http://academic.research.microsoft.com]&lt;br /&gt;
&lt;br /&gt;
Space is limited, so reserve your seat today  Email Alex at the address below.    &lt;br /&gt;
&lt;br /&gt;
Coordinator: Alex Wade, Microsoft Research, awade at microsoft dot com &lt;br /&gt;
&lt;br /&gt;
Presenters: Rob Fatland; Christophe Poulain; Michael Zyskowski &lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
* Declan Fleming&lt;br /&gt;
* Matt Critchlow&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Mcritchlow</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_preconference_proposals&amp;diff=10160</id>
		<title>2012 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_preconference_proposals&amp;diff=10160"/>
				<updated>2012-01-12T01:29:55Z</updated>
		
		<summary type="html">&lt;p&gt;Mcritchlow: /* Interest in Attending */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Proposals for 2012 Code4LibCon Preconferences=&lt;br /&gt;
Proposals closed Sunday, November 20, 2011, so we can finalize the list and add them to registration! (The deadline for preconference proposals has passed.)&lt;br /&gt;
&lt;br /&gt;
Spaces available: main meeting room (max 275) + 5 breakout rooms (max 30-50). &lt;br /&gt;
&lt;br /&gt;
'''Please include a &amp;quot;Contact/Responsible Individual&amp;quot; name and email address so we know who is willing to put on the proposed precon.&lt;br /&gt;
'''&lt;br /&gt;
==Full Day==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Hacking Content ===&lt;br /&gt;
&lt;br /&gt;
What is the future of getting library information and resources into users’ hands at the right time and with appropriate context and relevancy.  Learning management systems, library guides, Web-scale discovery systems-plenty of tools to choose from and still we see lots of opportunities for improvement. Let’s pick them apart and brainstorm ideas for projects that could address weaknesses in one or all of these systems. If you’re interested in these issues, challenges and conundrums join us for a day of thinking, dreaming and scheming. All skill sets and backgrounds needed. &lt;br /&gt;
&lt;br /&gt;
Speakers/Facilitators will be:&lt;br /&gt;
 - Thom Cox - Manager of Library Information Technology Services - Tufts University&lt;br /&gt;
 - Ken Varnum – Web Systems Manager - University of Michigan Libraries&lt;br /&gt;
 - Evviva Weinraub – Director, Emerging Technologies and Services - Oregon State University Libraries &lt;br /&gt;
&lt;br /&gt;
Contact:  Margaret Mellinger - margaret dot mellinger at oregonstate dot edu&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
=== Developing applications using REST web services ===&lt;br /&gt;
&lt;br /&gt;
Been hearing about web services but don’t know where to start to build something? Have you built applications that use read services but are stumped by OAuth, Content Negotiation and HTTP Headers? Come dig in and learn how to build applications that interact with both read and write REST services. We’ll cover the basic principles and practices of REST services and discuss the Atom Publishing Protocol as a REST service and its extensibility. The group will examine and test the CouchDB HTTP API by building a simple list creation tool. You’ll learn how OCLC’s platform web services leverage Atom to expose the data and business processes from OCLC’s library systems. By the end of the session, you’ll know the basic principles of REST services, be able to perform Create, Read, Update and Delete operations via REST and be able to authenticate to REST services via API keys and OAuth.&lt;br /&gt;
&lt;br /&gt;
Come ready to learn and code!&lt;br /&gt;
&lt;br /&gt;
Presenter: Karen Coombs - coombsk at oclc dot org&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
*Sam Kome&lt;br /&gt;
*Ray Schwartz&lt;br /&gt;
*Jim Robinson&lt;br /&gt;
&lt;br /&gt;
==Half Day Morning==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Linkfest ===&lt;br /&gt;
&lt;br /&gt;
We've had talks and sessions galore about Linked Data at code4lib in past years.  Let's focus on linking.  Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web.  At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there.  May a kajillion links bloom!&lt;br /&gt;
&lt;br /&gt;
If you need an &amp;quot;intro to linked data&amp;quot; we can prep a good list of readings/talks to review before you come.  But please come ready to link!&lt;br /&gt;
&lt;br /&gt;
Organizer type person:  Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
*Becky Yoose&lt;br /&gt;
*Tom Johnson&lt;br /&gt;
*Ed Summers&lt;br /&gt;
&lt;br /&gt;
=== What's New in Solr ===&lt;br /&gt;
&lt;br /&gt;
This session will bring folks up to speed on the latest developments in Lucene and Solr.  There's always a lot of new capabilities as well as tips and tricks on using Solr in clever and powerful ways.  &lt;br /&gt;
&lt;br /&gt;
Presenter: Erik Hatcher - erik . hatcher @ lucidimagination dot com&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
==Half Day Afternoon==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Git -r done === &lt;br /&gt;
&lt;br /&gt;
A session to cover all things Git, everyone's favorite distributed version control system.  This session should cover a little bit of the history of Git, how it works, and how it's different than other version controls systems like SVN.  Practical application should also be covered, including how to clone existing repos and contribute code back to them, how to host your own repository, and best practices for setting up a distributed network.&lt;br /&gt;
&lt;br /&gt;
Looking for attendees with real-life Git experience to share it, so we can all broaden our understanding of possible use-cases and nifty advanced features.&lt;br /&gt;
&lt;br /&gt;
Coordinator:  Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com&lt;br /&gt;
&lt;br /&gt;
Helper: Cary Gordon, Cherry Hill Company, @highermath / cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
* Patrick Berry (pberry@csuchico.edu)&lt;br /&gt;
* Chris Sharp (csharp@georgialibraries.org)&lt;br /&gt;
* Matt Critchlow (mcritchlow@ucsd.edu)&lt;br /&gt;
&lt;br /&gt;
=== Blacklight ===&lt;br /&gt;
&lt;br /&gt;
This session will be walk-through of the architecture of Blacklight and what we have been improving since the rails 3 upgrade.  In addition to the architecture of the software, we will also briefly discuss the architecture of the Blacklight community and what has made it successful so far.&lt;br /&gt;
&lt;br /&gt;
For part of the session we will install Blacklight live and get it up and running.  This install demo will include a How-To on basic customizations in Blacklight using a test-driven approach (one of the cornerstones of the Blacklight community).&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;
Presenters: Jessie Keck, Stanford University - jkeck at stanford dot edu | Molly Pickral, University of Virginia - mpc3c at virginia dot edu&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
=== DACS and EAD Overview ===&lt;br /&gt;
&lt;br /&gt;
This session will look at what DACS (Describing Archives: a Content Standard) is and describe the ten required elements.  Then there will be an overview of what EAD is, how it works, and the required elements.  The final part will be a practice session on taking a paper finding aid and coding it using DACS and EAD.&lt;br /&gt;
&lt;br /&gt;
Presenter:  Doris Munson, Eastern Washington University, dmunson at ewu dot edu&lt;br /&gt;
(please feel free to contact me if you are interested in being a co-presenter)&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
=== [[Digging into metadata: context, code, and collaboration]] ===&lt;br /&gt;
&lt;br /&gt;
Working with library/archival metadata is difficult. This preconference will tackle pressing questions and will show some of the intricacies of metadata (including AACR2/MARC) with exercises to demonstrate why inconsistencies exist in the data. What steps can the cataloging &amp;amp; metadata community take to help improve the quality of this data?  What tools &amp;amp; techniques could help?  Rules have evolved over time leaving dirty legacy data.  Systems have impacted--and will continue to impact--data structure &amp;amp; design.  How can this data be aggregated and refined for use in a new emerging data environments?  What assumptions can safely be made and when do you need to inquire about local practice?  We will end with a hack-fest where you can ask questions of experienced catalogers and get help with your metadata related problems.  Bring your laptops and data.   &lt;br /&gt;
&lt;br /&gt;
Person Herder: Becky Yoose, Grinnell College, yoosebec at grinnell dot edu&lt;br /&gt;
&lt;br /&gt;
Collaborators/Facilitators: Corey Harper, New York University - corey dot harper at nyu dot edu | Shana L. McDanold, University of Pennsylvania - 	&lt;br /&gt;
mcdanold at pobox dot upenn dot edu  | Laura Smart, Caltech - laura at library dot caltech dot edu&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
=== &amp;quot;Geo&amp;quot; ===&lt;br /&gt;
This session will explore, we hope collaboratively, the presentation of objects on maps.  There will be a section on workflow, a section on discovering objects via &amp;quot;geobrowse,&amp;quot; a section discovery of objects via &amp;quot;geosearch,&amp;quot; and an exploration of the discovery and presentation of geo-referenced images (e.g. historic maps). There will be open discussion on other approaches to map-based discovery.  Emphasis will be placed on simplicity of workflow and implementation.  Technologies include: Atom, Django, Solr, and OpenLayers.  &lt;br /&gt;
&lt;br /&gt;
Presenters:  Mike Graves, UNC Chapel Hill, gravm at email dot unc dot edu; Tim Shearer, UNC Chapel Hill, tshearer at email dot unc dot edu&lt;br /&gt;
(please feel free to contact Tim if you are interested in being a co-presenter)&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Mcritchlow</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2012_preconference_proposals&amp;diff=10159</id>
		<title>2012 preconference proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2012_preconference_proposals&amp;diff=10159"/>
				<updated>2012-01-12T01:25:43Z</updated>
		
		<summary type="html">&lt;p&gt;Mcritchlow: /* Git -r done */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Proposals for 2012 Code4LibCon Preconferences=&lt;br /&gt;
Proposals closed Sunday, November 20, 2011, so we can finalize the list and add them to registration! (The deadline for preconference proposals has passed.)&lt;br /&gt;
&lt;br /&gt;
Spaces available: main meeting room (max 275) + 5 breakout rooms (max 30-50). &lt;br /&gt;
&lt;br /&gt;
'''Please include a &amp;quot;Contact/Responsible Individual&amp;quot; name and email address so we know who is willing to put on the proposed precon.&lt;br /&gt;
'''&lt;br /&gt;
==Full Day==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Hacking Content ===&lt;br /&gt;
&lt;br /&gt;
What is the future of getting library information and resources into users’ hands at the right time and with appropriate context and relevancy.  Learning management systems, library guides, Web-scale discovery systems-plenty of tools to choose from and still we see lots of opportunities for improvement. Let’s pick them apart and brainstorm ideas for projects that could address weaknesses in one or all of these systems. If you’re interested in these issues, challenges and conundrums join us for a day of thinking, dreaming and scheming. All skill sets and backgrounds needed. &lt;br /&gt;
&lt;br /&gt;
Speakers/Facilitators will be:&lt;br /&gt;
 - Thom Cox - Manager of Library Information Technology Services - Tufts University&lt;br /&gt;
 - Ken Varnum – Web Systems Manager - University of Michigan Libraries&lt;br /&gt;
 - Evviva Weinraub – Director, Emerging Technologies and Services - Oregon State University Libraries &lt;br /&gt;
&lt;br /&gt;
Contact:  Margaret Mellinger - margaret dot mellinger at oregonstate dot edu&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
=== Developing applications using REST web services ===&lt;br /&gt;
&lt;br /&gt;
Been hearing about web services but don’t know where to start to build something? Have you built applications that use read services but are stumped by OAuth, Content Negotiation and HTTP Headers? Come dig in and learn how to build applications that interact with both read and write REST services. We’ll cover the basic principles and practices of REST services and discuss the Atom Publishing Protocol as a REST service and its extensibility. The group will examine and test the CouchDB HTTP API by building a simple list creation tool. You’ll learn how OCLC’s platform web services leverage Atom to expose the data and business processes from OCLC’s library systems. By the end of the session, you’ll know the basic principles of REST services, be able to perform Create, Read, Update and Delete operations via REST and be able to authenticate to REST services via API keys and OAuth.&lt;br /&gt;
&lt;br /&gt;
Come ready to learn and code!&lt;br /&gt;
&lt;br /&gt;
Presenter: Karen Coombs - coombsk at oclc dot org&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
*Sam Kome&lt;br /&gt;
*Ray Schwartz&lt;br /&gt;
*Jim Robinson&lt;br /&gt;
&lt;br /&gt;
==Half Day Morning==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Linkfest ===&lt;br /&gt;
&lt;br /&gt;
We've had talks and sessions galore about Linked Data at code4lib in past years.  Let's focus on linking.  Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web.  At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there.  May a kajillion links bloom!&lt;br /&gt;
&lt;br /&gt;
If you need an &amp;quot;intro to linked data&amp;quot; we can prep a good list of readings/talks to review before you come.  But please come ready to link!&lt;br /&gt;
&lt;br /&gt;
Organizer type person:  Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
*Becky Yoose&lt;br /&gt;
*Tom Johnson&lt;br /&gt;
*Ed Summers&lt;br /&gt;
&lt;br /&gt;
=== What's New in Solr ===&lt;br /&gt;
&lt;br /&gt;
This session will bring folks up to speed on the latest developments in Lucene and Solr.  There's always a lot of new capabilities as well as tips and tricks on using Solr in clever and powerful ways.  &lt;br /&gt;
&lt;br /&gt;
Presenter: Erik Hatcher - erik . hatcher @ lucidimagination dot com&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
==Half Day Afternoon==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Git -r done === &lt;br /&gt;
&lt;br /&gt;
A session to cover all things Git, everyone's favorite distributed version control system.  This session should cover a little bit of the history of Git, how it works, and how it's different than other version controls systems like SVN.  Practical application should also be covered, including how to clone existing repos and contribute code back to them, how to host your own repository, and best practices for setting up a distributed network.&lt;br /&gt;
&lt;br /&gt;
Looking for attendees with real-life Git experience to share it, so we can all broaden our understanding of possible use-cases and nifty advanced features.&lt;br /&gt;
&lt;br /&gt;
Coordinator:  Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com&lt;br /&gt;
&lt;br /&gt;
Helper: Cary Gordon, Cherry Hill Company, @highermath / cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
* Matt Critchlow (mcritchlow@ucsd.edu)&lt;br /&gt;
* Patrick Berry (pberry@csuchico.edu)&lt;br /&gt;
* Chris Sharp (csharp@georgialibraries.org)&lt;br /&gt;
&lt;br /&gt;
=== Blacklight ===&lt;br /&gt;
&lt;br /&gt;
This session will be walk-through of the architecture of Blacklight and what we have been improving since the rails 3 upgrade.  In addition to the architecture of the software, we will also briefly discuss the architecture of the Blacklight community and what has made it successful so far.&lt;br /&gt;
&lt;br /&gt;
For part of the session we will install Blacklight live and get it up and running.  This install demo will include a How-To on basic customizations in Blacklight using a test-driven approach (one of the cornerstones of the Blacklight community).&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;
Presenters: Jessie Keck, Stanford University - jkeck at stanford dot edu | Molly Pickral, University of Virginia - mpc3c at virginia dot edu&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
=== DACS and EAD Overview ===&lt;br /&gt;
&lt;br /&gt;
This session will look at what DACS (Describing Archives: a Content Standard) is and describe the ten required elements.  Then there will be an overview of what EAD is, how it works, and the required elements.  The final part will be a practice session on taking a paper finding aid and coding it using DACS and EAD.&lt;br /&gt;
&lt;br /&gt;
Presenter:  Doris Munson, Eastern Washington University, dmunson at ewu dot edu&lt;br /&gt;
(please feel free to contact me if you are interested in being a co-presenter)&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
=== [[Digging into metadata: context, code, and collaboration]] ===&lt;br /&gt;
&lt;br /&gt;
Working with library/archival metadata is difficult. This preconference will tackle pressing questions and will show some of the intricacies of metadata (including AACR2/MARC) with exercises to demonstrate why inconsistencies exist in the data. What steps can the cataloging &amp;amp; metadata community take to help improve the quality of this data?  What tools &amp;amp; techniques could help?  Rules have evolved over time leaving dirty legacy data.  Systems have impacted--and will continue to impact--data structure &amp;amp; design.  How can this data be aggregated and refined for use in a new emerging data environments?  What assumptions can safely be made and when do you need to inquire about local practice?  We will end with a hack-fest where you can ask questions of experienced catalogers and get help with your metadata related problems.  Bring your laptops and data.   &lt;br /&gt;
&lt;br /&gt;
Person Herder: Becky Yoose, Grinnell College, yoosebec at grinnell dot edu&lt;br /&gt;
&lt;br /&gt;
Collaborators/Facilitators: Corey Harper, New York University - corey dot harper at nyu dot edu | Shana L. McDanold, University of Pennsylvania - 	&lt;br /&gt;
mcdanold at pobox dot upenn dot edu  | Laura Smart, Caltech - laura at library dot caltech dot edu&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
=== &amp;quot;Geo&amp;quot; ===&lt;br /&gt;
This session will explore, we hope collaboratively, the presentation of objects on maps.  There will be a section on workflow, a section on discovering objects via &amp;quot;geobrowse,&amp;quot; a section discovery of objects via &amp;quot;geosearch,&amp;quot; and an exploration of the discovery and presentation of geo-referenced images (e.g. historic maps). There will be open discussion on other approaches to map-based discovery.  Emphasis will be placed on simplicity of workflow and implementation.  Technologies include: Atom, Django, Solr, and OpenLayers.  &lt;br /&gt;
&lt;br /&gt;
Presenters:  Mike Graves, UNC Chapel Hill, gravm at email dot unc dot edu; Tim Shearer, UNC Chapel Hill, tshearer at email dot unc dot edu&lt;br /&gt;
(please feel free to contact Tim if you are interested in being a co-presenter)&lt;br /&gt;
&lt;br /&gt;
==== Interest in Attending ====&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2012]]&lt;/div&gt;</summary>
		<author><name>Mcritchlow</name></author>	</entry>

	</feed>