<?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=Afred</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=Afred"/>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/Special:Contributions/Afred"/>
		<updated>2026-04-09T22:14:50Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.26.2</generator>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Craft_Drinkup&amp;diff=42608</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=42608"/>
				<updated>2015-02-03T21:12:28Z</updated>
		
		<summary type="html">&lt;p&gt;Afred: &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 || [http://www.sprecherbrewery.com/store/details.php?prodId=164&amp;amp;category=7 N/A Soda from Sprecher Brewery], [http://www.sprecherbrewery.com/store/cw2/assets/product_huge/F_Popcorn_RB-Large.jpg Sprecher Root beer float flavored popcorn], 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 || Stuff from NY that Matienzo &amp;amp; Harlow don't bring || Farmhouse beers, tasty low-ABV beers&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, Allagash FOUR, Neshaminator || 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;
| Jeremy Nelson || Left Hand's Wake Up the Dead Imperial Stout or other Colorado Stout/Porter || stouts and porters&lt;br /&gt;
|-&lt;br /&gt;
|Heather Pitts||Mid-Willamette Valley stuff in growlers/growlettes (depends on what's on tap), some bottles too||sours, stouts, porters, ginger ciders or meads&lt;br /&gt;
|-&lt;br /&gt;
|Jeremy Floyd||A selection from [http://www.greatbasinbrewingco.com/site/brews/in-bottles/ Great Basin Brewing Co.] in Northern Nevada||saisons, sours, anything unique&lt;br /&gt;
|-&lt;br /&gt;
|Misty De Meo||A bottle from Vancouver's [http://artisansakemaker.com/ Artisan SakeMaker]||stouts, porters, any dark beers really&lt;br /&gt;
|-&lt;br /&gt;
|Jon Earley || From Michigan, [http://foundersbrewing.com/our-beer/dirty-bastard/ Founders Dirty Bastard] and [http://www.greenbushbrewing.com/gb_splash.php?r=http://www.greenbushbrewing.com/beers/anger.htm Greenbush Anger] || ginger ale, anything unique&lt;br /&gt;
|-&lt;br /&gt;
|Eric Frierson||Austin's own [http://www.beeradvocate.com/beer/profile/383/1062/ Live Oak HefeWeizen] if I can find a way to bottle it; if not, then [http://www.beeradvocate.com/beer/profile/458/23720/ Devil's Backbone] tripel||scottish ales would be nice.&lt;br /&gt;
|-&lt;br /&gt;
|Andrew Myers||[http://spencerbrewery.com/beer/ Spencer trappist ale], and maybe something from [http://www.aeronautbrewing.com/ the new place down the street]||hops&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Afred</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Craft_Drinkup&amp;diff=42607</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=42607"/>
				<updated>2015-02-03T21:11:12Z</updated>
		
		<summary type="html">&lt;p&gt;Afred: Andrew Myers attending craft brew drink-up&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 || [http://www.sprecherbrewery.com/store/details.php?prodId=164&amp;amp;category=7 N/A Soda from Sprecher Brewery], [http://www.sprecherbrewery.com/store/cw2/assets/product_huge/F_Popcorn_RB-Large.jpg Sprecher Root beer float flavored popcorn], 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 || Stuff from NY that Matienzo &amp;amp; Harlow don't bring || Farmhouse beers, tasty low-ABV beers&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, Allagash FOUR, Neshaminator || 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;
| Jeremy Nelson || Left Hand's Wake Up the Dead Imperial Stout or other Colorado Stout/Porter || stouts and porters&lt;br /&gt;
|-&lt;br /&gt;
|Heather Pitts||Mid-Willamette Valley stuff in growlers/growlettes (depends on what's on tap), some bottles too||sours, stouts, porters, ginger ciders or meads&lt;br /&gt;
|-&lt;br /&gt;
|Jeremy Floyd||A selection from [http://www.greatbasinbrewingco.com/site/brews/in-bottles/ Great Basin Brewing Co.] in Northern Nevada||saisons, sours, anything unique&lt;br /&gt;
|-&lt;br /&gt;
|Misty De Meo||A bottle from Vancouver's [http://artisansakemaker.com/ Artisan SakeMaker]||stouts, porters, any dark beers really&lt;br /&gt;
|-&lt;br /&gt;
|Jon Earley || From Michigan, [http://foundersbrewing.com/our-beer/dirty-bastard/ Founders Dirty Bastard] and [http://www.greenbushbrewing.com/gb_splash.php?r=http://www.greenbushbrewing.com/beers/anger.htm Greenbush Anger] || ginger ale, anything unique&lt;br /&gt;
|-&lt;br /&gt;
|Eric Frierson||Austin's own [http://www.beeradvocate.com/beer/profile/383/1062/ Live Oak HefeWeizen] if I can find a way to bottle it; if not, then [http://www.beeradvocate.com/beer/profile/458/23720/ Devil's Backbone] tripel||scottish ales would be nice.&lt;br /&gt;
|-&lt;br /&gt;
|Andrew Myers||[http://spencerbrewery.com/beer/ Spencer trappist ale], and maybe something from [http://www.aeronautbrewing.com/ the new place down the street]||trappist ale, and some other beer maybe&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Afred</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&amp;diff=41998</id>
		<title>2015 Prepared Talk Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&amp;diff=41998"/>
				<updated>2014-11-07T20:24:01Z</updated>
		
		<summary type="html">&lt;p&gt;Afred: /* PBCore in Action: Three Words, Not Two! */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Code4lib 2015 is a loosely-structured conference that provides people working at the intersection of libraries/archives/museums/cultural heritage and technology with a chance to share ideas, be inspired, and forge collaborations. For more information about the Code4lib community, please visit http://code4lib.org/about/. &lt;br /&gt;
The conference will be held at the Portland Hilton &amp;amp; Executive Tower in Portland, Oregon, from February 9-12, 2015.&lt;br /&gt;
&lt;br /&gt;
'''Proposals for Prepared Talks:'''&lt;br /&gt;
&lt;br /&gt;
We encourage everyone to propose a talk.&lt;br /&gt;
 &lt;br /&gt;
Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:&lt;br /&gt;
* Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software&lt;br /&gt;
* Tools and technologies – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)&lt;br /&gt;
* Technical issues - Big issues in library technology that should be addressed or better understood&lt;br /&gt;
* Relevant non-technical issues – Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc.&lt;br /&gt;
&lt;br /&gt;
Proposals can be submitted through Friday, November 7, 2014 at 5pm PST (GMT−8). Voting will start on November 11, 2014 and continue through November 25, 2014. The URL to submit votes will be announced on the Code4Lib website and mailing list and will require an active code4lib.org account to participate. The final list of presentations will be announced in early- to mid-December.&lt;br /&gt;
&lt;br /&gt;
'''Proposals for Prepared Talks:'''&lt;br /&gt;
&lt;br /&gt;
Log in to the Code4lib wiki and edit this wiki page using the prescribed format. If you are not already registered, follow the instructions to do so.&lt;br /&gt;
Provide a title and brief (500 words or fewer) description of your proposed talk.&lt;br /&gt;
If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist voters in opening the conference to new presenters.&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Talk Title: ==&lt;br /&gt;
 &lt;br /&gt;
* Speaker's name,  email address, and (optional) affiliation&lt;br /&gt;
* Second speaker's name, email address, and affiliation, if second speaker&lt;br /&gt;
&lt;br /&gt;
Abstract of no more than 500 words.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Talk Proposals'''&lt;br /&gt;
== Zines + Gamification = Awesomest Metadata Literacy Outreach Event Ever! ==&lt;br /&gt;
 &lt;br /&gt;
* [http://www.JenniferHecker.info Jennifer Hecker], jenniferraehecker@gmail.com, [http://www.lib.utexas.edu/subject/zines University of Texas Libraries] &amp;amp; [http://www.AustinFanzineProject.org Austin Fanzine Project]&lt;br /&gt;
* [http://anomalily.net/ Lillian Karabaic], librarian@iprc.org, [http://www.iprc.org/ Independent Publishing Resource Center] (Portland)&lt;br /&gt;
 &lt;br /&gt;
In academic libraries, and elsewhere, the popularity of zine (a magazine produced for love, not profit) collections is on the rise. At the same time, metadata literacy is becoming an increasingly important skill, helping people navigate and understand digital environments and interactions. We have found a way to teach metadata literacy to the general public that isn’t super-boring – in fact, we’ve made it downright fun!&lt;br /&gt;
&lt;br /&gt;
First, volunteer zine librarian Lillian Karabaic of Portland’s Independent Publishing Resource Center facilitated the creation of a gamified cataloging interface for the IPRC’s annual Raiders of the Lost Archives backlog-busting 24-hour volunteer cataloging event.&lt;br /&gt;
&lt;br /&gt;
Then, archivist Jennifer Hecker facilitated the adaptation of the IPRC’s game for use in a similar, but also very different context – promoting UT Libraries newly-acquired zine collections. The main goal of the academic-library-based event was increasing excitement around the collections, but with the side goal of building metadata literacy, and introducing an understanding of library cataloging issues.&lt;br /&gt;
&lt;br /&gt;
The Texas modification also conforms to the xZINECOREx metadata schema developed by the national [http://zinelibraries.info/ Zine Librarians Interest Group], and triggered interesting conversations with the Libraries’s cataloging department about evolving metadata standards and how to incorporate the products of crowd-sourcing projects into existing workflows.&lt;br /&gt;
&lt;br /&gt;
Both games will be demoed.&lt;br /&gt;
&lt;br /&gt;
We have never presented at Code4lib.&lt;br /&gt;
&lt;br /&gt;
== Do the Semantic FRBRoo ==&lt;br /&gt;
* Rosie Le Faive, rlefaive@upei.ca, University of Prince Edward Island&lt;br /&gt;
&lt;br /&gt;
[http://www.islandora.ca Islandora] is great for creating repositories of any data type, but how can you model meaningful relationships between digital objects and use them to tell a story?&lt;br /&gt;
&lt;br /&gt;
At UPEI, I’m assembling an ethnography of Prince Edward Island’s traditional fiddle music that includes musical clips, video clips, oral histories, musical notation, images, and ethnographic commentaries. In order to present an exhibition-style site, I’m tying these digital objects together via the people, places, events, tunes and topics that they share or describe. &lt;br /&gt;
&lt;br /&gt;
To describe the relationships, I’m extending Islandora to use [http://www.cidoc-crm.org/frbr_inro.html FRBRoo], a vocabulary that combines the FRBR model with CIDOC-CRM, the the object-oriented museum documentation ontology. These modules being developed will allow other researchers to create a structured, navigable digital repository of diverse object types, that uses Islandora as an exhibition platform. &lt;br /&gt;
&lt;br /&gt;
== Our $50,000 Problem: Why Library School? ==&lt;br /&gt;
* Jennie Rose Halperin, jhalperin@mozilla.com, Mozilla Corporation&lt;br /&gt;
&lt;br /&gt;
57 library schools in the United States are churning out approximately 100 graduates per year, many with debt upwards of $50,000.  According to ONet, [http://www.inthelibrarywiththeleadpipe.org/2011/is-the-united-states-training-too-many-librarians-or-too-few-part-1/ 84% of library jobs in the US require an MLS.] The library profession is [http://dpeaflcio.org/programs-publications/issue-fact-sheets/library-workers-facts-figures/) 92% white and 82% female and entry-level librarians can expect to make $32,500 per year.]&lt;br /&gt;
&lt;br /&gt;
Contrasted with developers, who are almost [http://www.ncwit.org/blog/did-you-know-demographics-technical-women 90% male] and can expect to make [http://www.forbes.com/sites/jennagoudreau/2011/06/01/best-entry-level-jobs/ $70,000 in an entry-level position,] these numbers are dismal.&lt;br /&gt;
&lt;br /&gt;
According to a recent survey, the top skill that outgoing library students want to know is “programming” and yet many MLS programs still consider Microsoft Word an essential technology skill.&lt;br /&gt;
&lt;br /&gt;
What is going on here? Why do we accept this fate, where mostly female debt-burdened professionals continue to be thrown onto the work force without the education their expensive degrees promised?&lt;br /&gt;
&lt;br /&gt;
As a community we need to come together to stop this cycle. We need to provide better support and mentorship to diversify and keep the profession relevant and help librarianship move into the future it deserves.&lt;br /&gt;
&lt;br /&gt;
This talk will walk through the challenges of navigating a hostile employment environment as well as present models for better development and future state imagining.&lt;br /&gt;
&lt;br /&gt;
== No cataloging software? Need more than Dublin Core? No problem!: Experiences with CollectiveAccess ==&lt;br /&gt;
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University&lt;br /&gt;
* Rachel Wittmann, rwittma@clemson.edu, Clemson University&lt;br /&gt;
&lt;br /&gt;
Clemson University Libraries has implemented the open-source software CollectiveAccess for customized digital collection needs. CollectiveAccess is an open-source project with the goal of providing a flexible way to manage and publish museum and archival collections. There are several applications associated with the projects; most used are: Providence (for cataloging and entering metadata) and Pawtucket (for displaying objects in a collection for the public). It has many profiles readily available for installing with existing library standards, such as Dublin Core, and there is a robust syntax for creating your own profiles to fit custom tailored metadata schemas. Plus, the user interface allows you to modify the metadata profile quickly and easily.&lt;br /&gt;
&lt;br /&gt;
In this talk, we will discuss:&lt;br /&gt;
* Our experiences with installing Providence and creating an installation profile that satisfies the needs of many of the Clemson Libraries digital archiving processes. &lt;br /&gt;
* The stumbling blocks experienced in that process and how they were resolved.&lt;br /&gt;
* The available plugins sourcing widely used authorities, such as Library of Congress thesauri and GeoNames.org, and how they have been used by our projects. &lt;br /&gt;
* A brief overview of the export and import functions and also current workflow practices within Providence.&lt;br /&gt;
* Future plans &amp;amp; the role of CollectiveAccess at Clemson University Libraries&lt;br /&gt;
&lt;br /&gt;
== Getting ContentDM and Wordpress to Play Together ==&lt;br /&gt;
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University&lt;br /&gt;
&lt;br /&gt;
Clemson University Libraries has a very strong program for digitizing and archiving photographs, and the Digital Imaging team processes many hundreds of photographs every month. These images are managed using different methods, including ContentDM, a digital collection manager.&lt;br /&gt;
&lt;br /&gt;
ContentDM provides various methods for searching and displaying photographs, along with their metadata. However, recent initiatives have resulted in the need to leverage those collections into exhibits displayed on other library-related websites, such as our Special Collections unit. The Clemson Libraries has invested heavily in Wordpress as our content management system of choice, and it seemed most efficient not to have to export and import images into our Wordpress sites in order to provide exhibited images.&lt;br /&gt;
&lt;br /&gt;
Fortunately, ContentDM has provided an API to many of their functions, allowing the extraction of metadata and even rescaled images through URLs. This project has been developing a plugin for Wordpress that integrates with ContentDM through shortcodes that Wordpress editors can easily include in their content. These shortcodes allow editors to choose how many images, which images from which collections, thumbnail sizes, etc. to display in different gallery styles. Plans are for it to allow integration with different plugins such as Fancybox and Masonry.&lt;br /&gt;
&lt;br /&gt;
In this presentation, I will demonstrate the current state of the plugin and discuss future plans. &lt;br /&gt;
&lt;br /&gt;
==Refinery — An open source locally deployable web platform for the analysis of large document collections==&lt;br /&gt;
 &lt;br /&gt;
* [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com&lt;br /&gt;
&lt;br /&gt;
Refinery is an open source web platform for the analysis of large unstructured document collections. It extracts meaningful semantic themes within documents also known as &amp;quot;topics&amp;quot; which can be thought of as word clouds composed of terms that highly co-occur with one another. Once this semantic index is formed, one can extract relevant documents related to these topics and further refine their contents through a summarization process that allows users to search for phrases that are relevant to them within the corpus. The goal of Refinery is to make this whole process easier and to provide some of the latest scalable versions of these learning algorithms in an intuitive web-based interface. Refinery is also meant to be run locally, thus bypassing the need for securing document collections over the internet. The talk will go through some of the technologies involved and a demo of the app.&lt;br /&gt;
&lt;br /&gt;
For more info check out http://www.docrefinery.org.&lt;br /&gt;
&lt;br /&gt;
==Drupal 8 — Evolution &amp;amp; Revolution==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Drupal 8 is in beta and nearing release. Among its many features, it notably has become more developer friendly through its adoption of the Symfony PHP framework along with Symfony's outstanding set of libraries (like Guzzle) and tools (like Composer). And, in implementing the Twig theming system, it is can begin to escape PHPtemplate. These moves also make it easier to create headless systems that uses Angular.js and other systems for presentation, or even forgo presentation entirely.&lt;br /&gt;
&lt;br /&gt;
From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.&lt;br /&gt;
&lt;br /&gt;
==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==&lt;br /&gt;
 &lt;br /&gt;
* [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]],  stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]&lt;br /&gt;
&lt;br /&gt;
GameSalad is a popular tool for developing mobile and desktop games with little actual programming. In this presentation, Stan Bogdanov breaks down the development process he followed while building [https://github.com/stanrb/mobiLit mobiLit], a mobile app with the goal of being the first open-source gamified information literacy app to be used as part of a college-level information literacy curriculum. He will go through the basics of using GameSalad to create an app that can be easily customized by non-programmers and the instructional principles used to teach the material in a mobile medium. Stan will also go through two qualitative design studies he did on the app and discuss their results and the lessons learned from building mobiLit. The session will conclude with an overview of the next steps for the [https://github.com/stanrb/mobiLit mobiLit project].&lt;br /&gt;
&lt;br /&gt;
==The Impossible Search: Pulling data from multiple unknown sources==&lt;br /&gt;
 &lt;br /&gt;
* Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com &lt;br /&gt;
&lt;br /&gt;
It's easy to search data you know the structure of, but what if you need to pull in data from sources that don't have a standard structure. The ability to search community events along with your standard catalog search results is an example, but often the only way to pull these events is through XML, JSON, (Insert structured format here), or even just raw html. But how do you get that structure? That simple question is what makes this impossible. The process to define and process this structure takes a lot of manual labor, especially if the data you are pulling is just HTML, and then every time you add data to the index you have to run all the data through a script to pull in data in a format Solr or an other index can use. This talk will focus on Solr, but the principles explained will apply to many other indexes.&lt;br /&gt;
&lt;br /&gt;
==What! You're Not Using Docker?==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Boring part: Docker[1] is a container system that provides benefits similar to virtualization with only a fraction of the overhead. Scintillating part: Docker can host between four to six times the number of service instances than systems such as Xen or VMWare on a given piece of hardware. But thats not all! Docker also makes it simple(r) to create transportable instances, so you can spin up development servers on your laptop.&lt;br /&gt;
&lt;br /&gt;
*[1]https://www.docker.com/&lt;br /&gt;
&lt;br /&gt;
== Video Accessibility, WebVTT, and Timed Text Track Tricks ==&lt;br /&gt;
&lt;br /&gt;
* Jason Ronallo, jronallo@gmail.com, NCSU Libraries&lt;br /&gt;
&lt;br /&gt;
Video on the Web presents new challenges and opportunities. How do you make your video more accessible to those with various disabilities and needs? I'll show you how. This presentation will focus on how to write and deliver captions, subtitles, audio descriptions, and timed metadata tracks for Web video using the WebVTT W3C standard. Encoding timed text tracks in this way opens up opportunities for new functionality on your websites beyond accessibility. The presentation will show some examples of the potential for using timed text tracks in creative ways. I'll cover all the HTML and JavaScript you will need to know as well as some of the CSS and other bits you could probably do without but are too fun to pass up.&lt;br /&gt;
&lt;br /&gt;
== Categorizing Records with Random Forests ==&lt;br /&gt;
 &lt;br /&gt;
* Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library&lt;br /&gt;
Academic libraries are increasingly responsible for providing ingest, search, discovery, and analysis for data sets.  Emerging techniques from data science and machine learning can provide librarians and developers with an opportunity to generate new insights and services from these document collections.  This presentation will provide a brief overview of common machine learning classification techniques, then dive into a more detailed example using a random forest to assign keywords to research data sets.  The talk will emphasize the insight that can be gained from machine learning rather than the inner workings of the algorithms.  The overall goal of this presentation is to provide librarians and developers with the context to recognize an opportunity to apply machine learning categorization techniques at their home campuses and organizations.  &lt;br /&gt;
&lt;br /&gt;
== Data Science in Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Devon Smith, smithde@oclc.org, OCLC&lt;br /&gt;
&lt;br /&gt;
Data Science is increasing in buzz and hype. I'll go over what it is, what it isn't, and how it fits in libraries.&lt;br /&gt;
&lt;br /&gt;
== PDF metadata extraction for academic literature == &lt;br /&gt;
&lt;br /&gt;
* Kevin Savage, kevin.savage at mendeley.com, Mendeley&lt;br /&gt;
* Joyce Stack, joyce.stack at mendeley.com, Mendeley&lt;br /&gt;
&lt;br /&gt;
Mendeley recently added a, &amp;quot;document from file,&amp;quot; endpoint to its API which attempts to extract metadata such as title and authors directly from PDF files. This talk will describe at a high level the machine learning methods we used including how we measured and tuned our model. We will then delve more deeply into our stack, the tools we used, some of the things that didn't work and why PDFs are the worst thing ever to compute over.&lt;br /&gt;
&lt;br /&gt;
== Giving Users What They Want: Record Grouping in VuFind ==&lt;br /&gt;
 &lt;br /&gt;
* Mark Noble,  mark@marmot.org, [//www.marmot.org Marmot Library Network]&lt;br /&gt;
&lt;br /&gt;
In 2013, Marmot did extensive usability studies with patrons to determine what was difficult in the catalog.  Many patrons had problems sifting through all of the various formats and editions of a title.  In 2014 we developed a method for [//mercury.marmot.org/Union/Search?lookfor=divergent grouping records] so only a single work is shown in search results and all formats and editions are listed under that work.  We will discuss our definition of a 'work' based on FRBR principles; combining meta data from MARC records with metadata from other sources like OverDrive; the technical details of Record Grouping; the design decisions made during implementation; and the reaction from users and staff.&lt;br /&gt;
&lt;br /&gt;
== Topic Space: a mobile augmented reality recommendation app ==&lt;br /&gt;
&lt;br /&gt;
* Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign&lt;br /&gt;
&lt;br /&gt;
The Topic Space module (http://minrvaproject.org/modules_topicspace.php ) was developed with an IMLS Sparks! Grant to investigate augmented reality technologies for in-library recommendations. The funding allowed for sustained university community collaboration by the University Library, the Graduate School of Library and Information Science, as well as graduate student programmers sourced from the Department of Computer Science. Collaborators designed app functionality and identified relevant open source libraries that could power optical character recognition (OCR) functionality from within the mobile phone.&lt;br /&gt;
&lt;br /&gt;
Topic space allows a user to take a picture of an item's call number in the book stacks. The module will show the user other books that are relevant but that are not shelved nearby. It can also show users books that are normally shelved here but that are currently checked out. Recommendations are based on Library of Congress subject headings and ILS circulation data which indicate recommendation candidates based on total check-outs. &lt;br /&gt;
&lt;br /&gt;
Research questions included development of back end (server-side) pattern matching algorithms for recommendations, and a rapid formative evaluation of interface design that would provide optimal user experience for navigation of the book stacks as a context to recommendations.&lt;br /&gt;
&lt;br /&gt;
Along with the Topic Space native app, grant collaborators prototyped web based recommendations which could serve as a new way of providing readers advisory and “more like this” recommendations from discovery interfaces accessed through desktop browsers. Outcomes of the grant include the availability of the [https://play.google.com/store/apps/details?id=edu.illinois.ugl.minrva Topic Spaces module within Minrva app on the Android Play store] and an experimental [http://backbonejs.org/ Backbone.js] based [http://minrva-dev.library.illinois.edu Topic Space web app].&lt;br /&gt;
&lt;br /&gt;
== Leveling Up Your Git Workflow ==&lt;br /&gt;
&lt;br /&gt;
* Megan Kudzia, moneill@albion.edu, Albion College Library&lt;br /&gt;
* Kate Sears, eks11@albion.edu, Albion College Library&lt;br /&gt;
&lt;br /&gt;
Have you started experimenting with Git on your own, but now you need to include others in your projects? Learn from our mistakes! Transitioning from a one-person git workflow and repo structure, to a structure that includes multiple people (including student workers), is not for the faint of heart. We'll talk about why we decided to work this way, our path to developing a git culture amongst ourselves, conceptual and technical difficulties we've faced, what we learned, and where we are now. Also with pretty pictures (aka workflow drawings).&lt;br /&gt;
&lt;br /&gt;
== Drone Loaning Program: Because Laptops are so last century ==&lt;br /&gt;
&lt;br /&gt;
 * Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries&lt;br /&gt;
 * Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries&lt;br /&gt;
&lt;br /&gt;
At Univ. Maryland we are in the very early stages of looking into allowing our student body get their hands on a drone. Yes that's right we will let students take out a drone for n amount of hours to work on projects of their choosing. The talk will talk about the logistics of getting a program of this sort from concept to &amp;quot;Is the drone available?&amp;quot;. If people sign waivers we will also promise not to crash the drone into code4lib attendees.&lt;br /&gt;
&lt;br /&gt;
== Got Git? Getting More Out of Your GitHub Repositories ==&lt;br /&gt;
&lt;br /&gt;
 * Terry Brady, twb27@georgetown.edu, Georgetown University Library&lt;br /&gt;
&lt;br /&gt;
This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories. &lt;br /&gt;
&lt;br /&gt;
In additional to all of the great benefits of using Git for code management, the GitHub interface provides a powerful set of tools to showcase a project and to keep your users informed of developments to your project.  These tools can assist with marketing and outreach - turning your code repository into a focus of conversation!&lt;br /&gt;
&lt;br /&gt;
* [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]&lt;br /&gt;
* [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]&lt;br /&gt;
* [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]&lt;br /&gt;
* [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]&lt;br /&gt;
* Gists for code sharing&lt;br /&gt;
* Private Repositories and Organizational Groups&lt;br /&gt;
* Pull Request Conversation Tracking&lt;br /&gt;
* Customized Issue management&lt;br /&gt;
&lt;br /&gt;
== Quick Wins for Every Department in the Library - File Analyzer! ==&lt;br /&gt;
&lt;br /&gt;
 * Terry Brady, twb27@georgetown.edu, Georgetown University Library&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.&lt;br /&gt;
* Analyzing Marc Records for the Cataloging department&lt;br /&gt;
* Transferring ILS invoices for the University Account System for the Acquisitions department &lt;br /&gt;
* Delivering patron fines to the Bursar’s office for the Access Service department&lt;br /&gt;
* Summarizing student worker timesheet data for the Finance department&lt;br /&gt;
* Validating COUNTER compliant reports for the Electronic Resources department&lt;br /&gt;
* Generating ingest packages for the Digital Services department&lt;br /&gt;
* Validating checksums for the Preservation department&lt;br /&gt;
&lt;br /&gt;
Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!&lt;br /&gt;
&lt;br /&gt;
==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor&lt;br /&gt;
&lt;br /&gt;
The transition from paper maps to digital ones changed much more than the maps themselves; it changed the very foundation of how we work and how we find each other. Now maps are transforming again.  The Geospatial World is moving from GIS systems that are institutionally-focused, expensive, feature-burdened, and binds data into a complicated and demanding user-hostile interface. From this transition from digital to web-based digital geospatial tools has come growth and development in new forms of map-based investigative journalism, activism, scholarship, and business ventures. This talk will highlight the conditions and strategies that made these changes possible as a means to draw a path by which librarians through our own work may follow, dragons notwithstanding. &lt;br /&gt;
&lt;br /&gt;
== Building Your Own Federated Search ==&lt;br /&gt;
&lt;br /&gt;
* Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco&lt;br /&gt;
&lt;br /&gt;
Advances in modern browsers have created some interesting possibilities for federated search. This presentation will cover common techniques and pitfalls in building a federated search. We will discuss what principles guided our decisions when implementing our own federated search. We will show tools we've built and our findings from building and using experimental prototypes.&lt;br /&gt;
&lt;br /&gt;
Your higher education institution likely offers dozens of online resources for educators, students, researchers, and the public. And each of these online resources likely has its own search tool. But users can't be expected to search in dozens of different interfaces to find what they're looking for. A typical solution for this issue is federated search. &lt;br /&gt;
&lt;br /&gt;
==  Indexing Linked Data with LDPath ==&lt;br /&gt;
&lt;br /&gt;
* Chris Beer, cabeer@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
LDPath [1] is a simple query language for indexing linked open data, with support for caching, content negotiation, and integration with non-RDF endpoints. This talk will demonstrate the features and potential of the language and framework to index a resource with links into id.loc.gov, viaf.org, geonames.org, etc to build an application-ready document.&lt;br /&gt;
&lt;br /&gt;
[1] http://marmotta.apache.org/ldpath/language.html&lt;br /&gt;
&lt;br /&gt;
== Show Me the Money: Integrating an LMS with Payment Providers ==&lt;br /&gt;
 &lt;br /&gt;
* Josh Weisman,  Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group&lt;br /&gt;
&lt;br /&gt;
In order to provide an easy and convenient way for patrons to pay fines, we are exploring ways to integrate the library management system with online payment providers such as PayPal. With many LMS systems being designed and developed for the cloud, we should be able to provide the frictionless user experience our patrons have come to expect from online transactions. In this session we'll discuss strategies for integration and review a sample application which uses REST APIs from a library management system to integrate with PayPal.&lt;br /&gt;
&lt;br /&gt;
== Shibboleth Federated Authentication for Library Applications: ==&lt;br /&gt;
&lt;br /&gt;
* Scott Fisher, scott.fisher@ucop.edu, California Digital Library&lt;br /&gt;
* Ken Weiss, ken.weiss@ucop.edu, California Digital Library&lt;br /&gt;
&lt;br /&gt;
Shibboleth is the most widely-used method to provide single-sign-on authentication to academic applications where users come from many different institutions. Shibboleth, the InCommon education and research trust framework, and the SAML protocol comprise a very powerful - but very complicated - solution to this very complicated problem. Scott and Ken have implemented Shibboleth for multiple library applications. They will share their understanding of the good, the bad, and the underlying spaghetti that makes it all work. Ken will discuss some of the technical aspects of the solution, touching on optimal and non-optimal use cases, administrative challenges, and authorization concerns. Scott will describe the implementation pattern for multi-institution single-sign-on that the California Digital Library has evolved, using the recently released Dash application (http://dash.cdlib.org) as an example.&lt;br /&gt;
&lt;br /&gt;
==Scientific Data: A Needs Assessment Journey==&lt;br /&gt;
 &lt;br /&gt;
*[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History&lt;br /&gt;
&lt;br /&gt;
While surveying digital research and collections data in the research science divisions at the American Museum of Natural History in NYC (as a part of my [http://ndsr.nycdigital.org/ National Digital Stewardship Residency] project), I have come across the big data hogs (genome sequencing and CT scanning) and the little pieces of data (images, publications), all equally important to not only scientific discovery, but as nodes in the history of science. &lt;br /&gt;
&lt;br /&gt;
In this session, I will discuss the development of my needs assessment surveys for scientific datasets and the interview process with Museum curators and researchers as background, seguing into an explanation of the results. I will then combine my findings into preliminary selection criteria to choose tools for digital preservation and management unique to scientific datasets. This will brooke a discussion on emerging standards, tools, and technologies in big data, specific to research science. &lt;br /&gt;
&lt;br /&gt;
I will conclude with preliminary findings on emerging technology that can be used to answer concerns surrounding the management and digital preservation of these data. I am hoping the Q&amp;amp;A session can be used to both answer questions about my project, and function as a way for you (the larger tech-savy library community)  to discuss the tools I’ve touched on in this talk. &lt;br /&gt;
&lt;br /&gt;
== Feminist Human Computer Interaction (HCI) in Library Software ==&lt;br /&gt;
 &lt;br /&gt;
* Bess Sadler,  bess@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
Libraries are not neutral repositories of knowledge. Library classification systems and search technologies tend to reflect the inequalities, biases, ethnocentrism, and power imbalances of the societies in which they are built [1]. How might we better resist these tendencies in the library software we create? This talk will examine some qualities of feminist HCI (pluralism, self-disclosure, participation, ecology, advocacy, and embodiment) [2] through the lens of library software. &lt;br /&gt;
&lt;br /&gt;
[1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.&lt;br /&gt;
&lt;br /&gt;
[2] Bardzell, Shaowen. Feminist HCI: Taking Stock and Outlining an Agenda for Design. CHI 2010: HCI For All. http://dmrussell.net/CHI2010/docs/p1301.pdf&lt;br /&gt;
&lt;br /&gt;
== Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==&lt;br /&gt;
&lt;br /&gt;
* Audrey Altman, audrey at dp.la, Digital Public Library of America&lt;br /&gt;
* Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America&lt;br /&gt;
* Mark Breedlove, mb at dp.la, Digital Public Library of America&lt;br /&gt;
&lt;br /&gt;
The Digital Public Library of America aggregates metadata for over 8 million objects from more than 24 direct partners, or Hubs, using its Metadata Application Profile (MAP), an RDF metadata application profile based on the Europeana Data Model. After working with the initial system for harvesting, mapping and enhancing our Hub’s metadata for a year, we realized that it was inadequate for working with data at this scale. There were architectural issues; it was opaque to non-developer and partner staff; there were inadequate tools for quality assurance and analysis; and the system was unaware that it was working with RDF data. As the network of Hubs expanded and we ingested more metadata, it became harder and harder to know when or why a harvest, a mapping task, or an enrichment went wrong because the tools for quality assurance were largely inadequate. &lt;br /&gt;
&lt;br /&gt;
The DPLA Content and Technology teams decided to develop a new system from the ground up to address those problems. Development of Heidrun, the internal version of the new system, started in October 2014. Heidrun’s goals are to make it easier for us to harvest and map metadata from various sources and in variety of schemas to the DPLA MAP, to better enrich that metadata using external data sources, and to actively involve our partners in the ingestion process through access to better QA tools. Heidrun and its componentry are built on Ruby on Rails, Blacklight, and ActiveTriples. Our presentation will give some background on our design principles and processes used during development, the architecture of the system, and its functionality. We plan to release a version of Heidrun and its components as a generalized metadata aggregation system for use by DPLA Hubs and others working to aggregate cultural heritage metadata.&lt;br /&gt;
&lt;br /&gt;
== OS or GTFO: Program or Perish ==&lt;br /&gt;
*Tessa Fallon, tessa.fallon@gmail.com&lt;br /&gt;
&lt;br /&gt;
Description TBD&lt;br /&gt;
&lt;br /&gt;
== Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==&lt;br /&gt;
* Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries&lt;br /&gt;
Would your library like to have large digital signage that displays dynamic information such as library hours, weather, room availability, and more? Have you looked into purchasing large digital signage, only to be turned off by the high price tag and lack of customization available with commercial solutions? Our library has developed a cheap and effective alternative to these systems using HTML 5 authoring software, a large TV, and freely-available APIs from Google, Springshare, and others. At this session, you’ll learn about the system that we have in place for displaying dynamic and easily-updatable information on our library’s large digital display, and how you can easily create something similar for your library.&lt;br /&gt;
&lt;br /&gt;
== REPOX: Metadata Blender ==&lt;br /&gt;
 &lt;br /&gt;
* John Mignault, jmignault@metro.org, Empire State Digital Network&lt;br /&gt;
&lt;br /&gt;
With the growth in the number of hubs providing metadata to the Digital Public Library of America, many of them are using REPOX, a tool originally created for the Europeana project, to aggregate disparate metadata feeds and transform them into formats suitable for ingest into DPLA. The Empire State Digital Network, the forthcoming DPLA service hub for NY state, is using it to prepare for our first ingest into DPLA in early 2015.  We'll take a look at REPOX and its capabilities and how it can be useful for ingesting and transforming metadata, and also discuss some things we've learned in massaging widely varied metadata feeds.&lt;br /&gt;
&lt;br /&gt;
== Beyond Open Source ==&lt;br /&gt;
&lt;br /&gt;
* Jason Casden, jmcasden@ncsu.edu, NCSU Libraries&lt;br /&gt;
* Bret Davidson, bddavids@ncsu.edu, NCSU Libraries&lt;br /&gt;
&lt;br /&gt;
The Code4Lib community has produced an increasingly impressive collection of open source software over the last decade, but much of this creative work remains out of reach for large portions of the library community. Do the relatively privileged institutions represented by a majority of Code4Lib participants have a professional responsibility to support the adoption of their innovations?&lt;br /&gt;
&lt;br /&gt;
Drawing from old and new software packaging and distribution approaches (from freeware to Docker), we will propose extending the open source software values of collaboration and transparency to include the wide and affordable distribution of software. We believe this will not only simplify the process of sharing our applications within the Code4Lib community, but also make it possible for less well resourced institutions to actually use our software. We will identify areas of need, present our experiences with the users of our own open source projects, discuss our attempts to go beyond open source, and make an argument for the internal value of supporting and encouraging a vibrant library ecosystem.&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]] &lt;br /&gt;
[[Category:Talk Proposals]]&lt;br /&gt;
&lt;br /&gt;
== Making It Work: Problem Solving Using Open Source at a Small Academic Library ==&lt;br /&gt;
 &lt;br /&gt;
* Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology&lt;br /&gt;
* Max King, mking9@iit.edu, Illinois Institute of Technology&lt;br /&gt;
&lt;br /&gt;
The Illinois Institute of Technology campus was added to the National Register of Historic Places in 2005, and contains a building, Mies van der Rohe's S.R. Crown Hall, that was named a National Historic Landmark in 2001. Creating a digital resource that can adequately showcase the campus and its architecture is challenge enough in and of itself, but doing so as a two-person team of relative newcomers, at a university library without dedicated programmers on staff, ups the ante considerably.&lt;br /&gt;
The challenges of technical know-how, staff time, and funding are nothing new to anyone working on digital projects at a university library, and are amplified when doing so at a smaller institution. This talk covers the conception, development, and design of the campus map site that was built, concentrating on the problem-solving strategies developed to cope with limited technical and financial resources.&lt;br /&gt;
We'll talk about our approach to development with Open Source software, including Omeka, along with the Neatline and Simile Timeline plugins. We'll also discuss the juggling act of designing for mobile mapping functionality without sacrificing desktop design, weighing the costs of increased functionality versus our ability to time-effectively include that functionality, and the challenge of building a site that could be developed iteratively, with an eye towards future enhancement and sustainability. Finally, we’ll provide recommendations for other librarians at smaller institutions for their own efforts at digital development.&lt;br /&gt;
&lt;br /&gt;
== Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==&lt;br /&gt;
 &lt;br /&gt;
* Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art&lt;br /&gt;
&lt;br /&gt;
The Museum of Modern Art has amassed a large collection of audiovisual materials over its many decades of existence. In order to preserve these materials, much of the audiovisual collection has been digitized. This is a complex process involving numerous steps and devices, and the methods used for digitization can have an effect on the quality of the file that is preserved. Therefore, knowing exactly how something was digitized is critical for future stewards of these objects to be able to properly care for and preserve them. However, detailed technical information about the processes involved in the digitization of audiovisual materials is not defined explicitly in most metadata schemas used for audiovisual materials. In order to record process history using existing metadata standards, some level of creativity is required to allow existing standards to express this information.&lt;br /&gt;
&lt;br /&gt;
This talk will detail different metadata standards, including PBCore, PREMIS, and reVTMD, that can be implemented as methods of recording this information. Specifically, the talk will examine efforts to integrate this metadata into the Museum of Modern Art’s new digital repository, the DRMC. This talk will provide background on the DRMC as well as MoMA’s specific institutional needs for process history metadata, then discuss different metadata implementations we have considered to document process history.&lt;br /&gt;
&lt;br /&gt;
== Pig Kisses Elephant: Building Research Data Services for Web Archives ==&lt;br /&gt;
 &lt;br /&gt;
* Jefferson Bailey,  jefferson@archive.org, Internet Archive&lt;br /&gt;
* Vinay Goel, vinay@archive.org, Internet Archive&lt;br /&gt;
&lt;br /&gt;
More and more libraries and archives are creating web archiving programs.  For both new and established programs, these archives can consist of hundreds of thousands, if not millions, of born-digital resources within a single collection; as such, they are ideally suited for large-scale computational study and analysis. Yet current access methods for web archives consist largely of browsing the archived web in the same manner as browsing the live web and the size of these collections and complexity of the WARC format can make aggregate analysis difficult. This talk will describe a project to create new ways for users and researchers to access and study web archives by offering extracted and post-processed datasets derived from web collections. Working with the 325+ institutions and their 2600+ collections within the Archive-It service, the Internet Archive is building methods to deliver a variety of datasets culled from collections of web content, including extracted metadata packaged in JSON, longitudinal link graph data, named entities, and other types of data. The talk will cover the technical details of building dataset production pipelines with Apache Pig, Hadoop, and tools like Stanford NER, the programmatic aspects of building data services for archives and researchers, and ongoing work to create new ways to access and study web archives.&lt;br /&gt;
&lt;br /&gt;
== Awesome Pi, LOL! ==&lt;br /&gt;
&lt;br /&gt;
* Matt Connolly, mconnolly@cornell.edu, Cornell University Library&lt;br /&gt;
* Jennifer Colt, jrc88@cornell.edu, Cornell University Library&lt;br /&gt;
&lt;br /&gt;
Inspired by Harvard Library Lab’s “Awesome Box” project, Cornell’s Library Outside the Library (LOL) group is piloting a more automated approach to letting our users tell us which materials they find particularly stunning. Armed with a Raspberry Pi, a barcode scanner, and some bits of kit that flash and glow, we have ventured into the foreign world of hardware development. This talk will discuss what it’s like for software developers and designers to get their hands dirty, how patrons are reacting to the Awesomizer, and LOL’s not-afraid-to-fail philosophy of experimentation.&lt;br /&gt;
&lt;br /&gt;
== You Gotta Keep 'em Separated: The Case for &amp;quot;Bento Box&amp;quot; Discovery Interfaces ==&lt;br /&gt;
 &lt;br /&gt;
* Jason Thomale,  jason.thomale@unt.edu, University of North Texas Libraries&lt;br /&gt;
&lt;br /&gt;
I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.&lt;br /&gt;
&lt;br /&gt;
The thing is, practically all of us--in academic libraries at least--have a similar set up for discovery, with just a few variations, and so talking about it still seems useful. Stop me if this sounds familiar. You've got a single search box on the library homepage as a starting point for discovery. And it's probably a tabbed affair, with an option for searching the catalog for books, an option for searching a discovery service for articles, an option for searching databases, and maybe a few others. Maybe you have an option to search everything at once--probably the default, if you have it. And, if you're a crazy hepcat, maybe you ''only'' have your one search that searches everything, with no tabs.&lt;br /&gt;
&lt;br /&gt;
Now, the question is, for your &amp;quot;everything&amp;quot; search, are you doing a combined list of results, or are you doing it bento-box style, with a short results list from each category displayed in its own compartment?&lt;br /&gt;
&lt;br /&gt;
At UNT, we've been holding off on implementing an &amp;quot;everything&amp;quot; search, for various reasons. One reason is that the evidence for either style hasn't been very clear. There's this persistent paradox that we just can't reconcile: users tell us, through word and action, that they prefer searching Google, yet, libraries aren't Google, and there are valid design reasons why we shouldn't try to oversimplify our discovery interfaces to be like Google. And there's user data that supports both sides.&lt;br /&gt;
&lt;br /&gt;
Holding off on making this decision has granted us 2 years of data on how people use our tabbed search interface that does ''not'' include an &amp;quot;everything&amp;quot; search. Recently I conducted a thorough analysis of this data--specifically the usage and query data for our catalog and discovery system (Summon). And I think it helps make the case for a bento box style discovery interface. To be clear, it isn't exactly the smoking gun that I was hoping for, but the picture it paints I think is telling. At the very least, it points away from a combined-results approach.&lt;br /&gt;
&lt;br /&gt;
I'm proposing a talk discussing the data we've collected, the trends we've seen, and what I think it all means--plus other reasons that we're jumping on the &amp;quot;bento box&amp;quot; discovery bandwagon and why I think &amp;quot;bento box&amp;quot; is at this point the path that least sells our souls.&lt;br /&gt;
&lt;br /&gt;
== Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift ==&lt;br /&gt;
 &lt;br /&gt;
* Ashley Blewer!, ashley.blewer@gmail.com&lt;br /&gt;
&lt;br /&gt;
Checksum technology is used all over the place, from git commits to authenticating Linux packages. It is most commonly used in the digital preservation field to monitor materials in storage for changes that will occur over time or used in the transmission of files during duplication. But do you even checksum, bro? I want this talk to move checksums from a position of mysterious macho jargon to something everyone can understand and want to use. I think a lot of people have heard of checksum but don’t know where to begin when it comes to actually using it at their institution. And cryptography is hella intimidating! This talk will cover what checksums are, how they can be integrated into a library or archival workflow, protecting collections requiring additional levels of security, algorithms used to verify file fixity and how they are different, and other aspects of cryptographic technology. Oh, and please note that all points in this talk will be emphasized or lightly performed through Taylor Swift lyrics. Seriously, this talk will consist of at least 50% Taylor Swift. Can you, like, even?&lt;br /&gt;
&lt;br /&gt;
== Level Up Your Coding with Code Club (yes, you can talk about it) ==&lt;br /&gt;
&lt;br /&gt;
* Coral Sheldon-Hess, coral@sheldon-hess.org&lt;br /&gt;
&lt;br /&gt;
Reading code is a necessary part of becoming a better developer. It gives you more experience and more insight into How Things Are (or Aren't) Done; it builds your intuition about how to solve problems with code; and it increases your confidence that you, too, can tackle whatever technological problems you're facing.&lt;br /&gt;
&lt;br /&gt;
But you don't have to read code alone! (Which is good. It's really not fun to read code alone.) &lt;br /&gt;
&lt;br /&gt;
In late 2014, a group of librarians formed two Code Clubs, inspired by [http://bloggytoons.com/code-club/ this talk by Saron] (of Bloggytoons fame). I'd like to tell you about how we've structured our Code Clubs, what has gone well, what we've learned, and what you need to do to form your own Code Club. I'll share a list of the codebases we've looked at, too, to help you get your own Code Club off the ground! &lt;br /&gt;
&lt;br /&gt;
== The Growth of a Programmer ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:jgo | Joshua Gomez]], Getty Research Institute, jgomez@getty.edu&lt;br /&gt;
&lt;br /&gt;
Just like other creative endeavors, software developers can experience periods of great productivity or find themselves in a rut. After contemplating the alternating periods in my own career I've noticed several factors that have effected my own professional growth and happiness, including: mentorship, structure, community, teamwork, environment, formal education, etc. Not all of the factors need to be present at all times; but some mixture of them is critical for continued growth. In this talk, I will articulate these factors, discuss how they can effect a developer's career, and how they can be sought out when missing. This talk is aimed at both new developers looking to strike their own path as well as the veterans that lead or mentor them.&lt;br /&gt;
&lt;br /&gt;
== Developing a Fedora 4.0 Content Model for Disk Images ==&lt;br /&gt;
&lt;br /&gt;
* Matthew Farrell, matthew.j.farrell@duke.edu, Duke University Libraries&lt;br /&gt;
* Alexandra Chassanoff, achass@email.unc.edu, BitCurator Access Project Manager&lt;br /&gt;
&lt;br /&gt;
As the acquisition of born-digital materials grows, institutions are seeking methods to facilitate easy ingest into their repositories and provide access to disk images and files derived or extracted from disk images. In this session, we describe our development of a Fedora 4.0 Content model for disk images, including acceptable image file formats and the rationale behind those choices.  We will also discuss efforts to integrate the disk image content model into the BitCurator Access environment. Unlike generalized, format-agnostic content models which might treat the disk image as a generic bitstream, a content model designed for disk images enables expression of relationships among associated content in the collection such as files extracted from images and other born-digital and digitized material associated with the same creator.  It also enables capture of file-system attributes such as file paths, timestamps, whether files are allocated/deleted, etc.  Further, a disk image content model suggests further steps repositories can take in order to transform and re-use associated metadata generated during the creation and forensic analysis of the disk image.&lt;br /&gt;
&lt;br /&gt;
== Data acquisition and publishing tools in R ==&lt;br /&gt;
&lt;br /&gt;
* Scott Chamberlain,  scott@ropensci.org, rOpenSci/UC Berkeley - first-time presenter&lt;br /&gt;
&lt;br /&gt;
R is an open source programming environment that is widely used among researchers in many fields. R is powerful because it's free, increasingly robust, and facilitates reproducible research, an increasingly sought after goal in academia. Although tools for data manipulation/visualization/analysis are well developed in R, data acquisition and publishing tools are not. rOpenSci is a collaborative effort to create the tools necessary to complete the reproducible research workflow. This presentation discusses the need for these tools, including examples, including interacting with the repositories Mendeley, Dryad, DataONE, and Figshare. In addition, we are building tools for searching scholarly metadata and acuiring full text of open access articles in a standarized way across metadata providers (e.g., Crossref, DataCite, DPLA) and publishers (e.g., PLOS, PeerJ, BMC, Pubmed). Last, we are building out tools for data reading and writing in Ecologial Metadata Language (EML).&lt;br /&gt;
&lt;br /&gt;
== SPLUNK: Log File Analysis ==&lt;br /&gt;
&lt;br /&gt;
* Jim LeFager, jlefager@depaul.edu, DePaul University Library&lt;br /&gt;
DePaul University Library recently took over monitoring and maintaining of the library EZproxy servers this past year and using Splunk, a machine data analysis tool, we are able to gather information and statistics on our electronic resource usage in addition to monitoring the servers. Splunk is a tool that can collect, analyze, and visualize log files and other machine data in real time and this has allowed for gathering realtime usage statistics for our electronic resources allowing us to filter by multiple facets including IP Range, Group Membership (student, faculty), so that we can see who is accessing our resources and from where. Splunk allows our library to query our data and create rich custom dashboards as well as create alerts that can be triggered when certain conditions are met, such as error codes, which can send an email alert to a group of users. We will be leveraging Splunk to monitor all library web applications going forward. This talk will review setting up Splunk and best practices in using the available features and customizations available including creating queries, alerts, and custom dashboards.  &lt;br /&gt;
&lt;br /&gt;
== Your code does not exist in a vacuum ==&lt;br /&gt;
* Becky Yoose, yoosebec at grinnell dot edu, Grinnell College (Done a lightning talk, MC duties, but have not presented a prepared talk)&lt;br /&gt;
&lt;br /&gt;
“If you have something to say, then say it in code…” - Sebastian Hammer, code4lib 2009&lt;br /&gt;
&lt;br /&gt;
In its 10 year run, code4lib has covered the spectrum of libtech development, from search to repositories to interfaces. However, during this time there has been little discussion about this one little fact about development - code does not exist in a vacuum. &lt;br /&gt;
&lt;br /&gt;
Like the comment above, code has something to say. A person’s or organization’s culture and beliefs influences code in all steps of the development cycle. What development method you use, tools, programming languages, licenses - everything is interconnected with and influenced by the philosophies, economics, social structures, and cultural beliefs of the developer and their organization/community.&lt;br /&gt;
&lt;br /&gt;
This talk will discuss these interconnections and influences when one develops code for libraries, focusing on several development practices (such as “Fail Fast, Fail Often” and Agile)   and licensing choices (such as open source) that libtech has either tried to model or incorporate into mainstream libtech practices. It’ll only scratch the surface of the many influences present in libtech development, but it will give folks a starting point to further investigate these connections at their own organizations and as a community as a whole.&lt;br /&gt;
&lt;br /&gt;
tl;dr - this will be a messy theoretical talk about technology and libraries. No shiny code slides, no live demos. You might come out of this talk feeling uncomfortable. Your code does not exist in a vacuum. Then again, you don’t exist in a vacuum either.&lt;br /&gt;
&lt;br /&gt;
== The Metadata Hopper: Mapping and Merging Metadata Standards for Simple, User-Friendly Access ==&lt;br /&gt;
&lt;br /&gt;
* Tracy Seneca, tjseneca@uic.edu, University of Illinois at Chicago&lt;br /&gt;
* Esther Verreau: verreau1@uic.edu, University of Illinois at Chicago&lt;br /&gt;
&lt;br /&gt;
The Chicago Collections Consortium: 15 institutions and growing!  8 distinct EAD standards! At least 3 permutations of MARC, and we lost count of the varieties of custom CONTENTdm image collections.  Not to mention the 14,730 unique subject terms, nearly all of which lead our poor end-users to exactly one organization's content. &lt;br /&gt;
&lt;br /&gt;
All large content aggregation projects have faced this challenge, and there are a few emerging tools to help us wrangle disparate metadata into new contexts.  The Metadata Hopper is one such tool. The Metadata Hopper enables archivists to map their local metadata standards to standardized deposit records, and tags those materials using a shared vocabulary, integrating them into a user-friendly portal without disrupting local practices. In last year's Code4Lib lightning talk we described the challenges that the Chicago Collections Consortium faces in creating shared, in-depth access to archival and digital collections about Chicago history and culture across CCC member organizations. This year, thanks to the Andrew W. Mellon Foundation, we have a working Django application to demonstrate.  In this talk we'll discuss the design that enables multiple layers of flexibility, from the ability to accept a variety of metadata standards to designing for an open source audience.&lt;br /&gt;
&lt;br /&gt;
http://chicagocollectionsconsortium.org&lt;br /&gt;
&lt;br /&gt;
== Programmers are not projects: lessons learned from managing humans ==&lt;br /&gt;
&lt;br /&gt;
* Erin White, erwhite@vcu.edu, Virginia Commonwealth University - first-time presenter&lt;br /&gt;
&lt;br /&gt;
Managing projects is one thing, but managing people is another. Whether we’re hired as managers or grow “organically” into management roles, sometimes technical people end up leading technical teams (gasp!). I’ll talk about lessons I’ve learned about hiring, retaining, and working long-term and day-to-day with highly tech-competent humans. I’ll also talk about navigating the politics of libraryland, juggling different types of projects, and working with constrained budgets to make good things and keep talented people engaged.&lt;br /&gt;
&lt;br /&gt;
== Practical Strategies for Picking Low-Hanging Fruits to Improve Your Library's Web Usability and UX ==&lt;br /&gt;
&lt;br /&gt;
* Bohyun Kim, bkim@hshsl.umaryland.edu, University of Maryland, Baltimore&lt;br /&gt;
&lt;br /&gt;
Have you ever tried to fix an obvious (to you at least!) problem in Web usability or UX (user experience) only to face strong resistance from the library staff? Are you a strong advocate for making library resources, systems, services, and space as usable as possible, but do you often find yourself struggling to get the point across and/or obtain the crucial buy-in from colleagues and administrators? &lt;br /&gt;
&lt;br /&gt;
There is no shortage of Web usability and UX guidelines. But applying them to a library and implementing desired changes often involve a long and slow process. To tackle this issue, this talk will focus on how to utilize the 'expert review' process (aka 'heuristic evaluation') as a preliminary or even preparatory step before embarking on more time-and-labor-intensive usability testing and user research. Several examples from  simple fixes to more nuanced usability and UX issues in libraries will be discussed to your heart's content. The goal of this talk is to provide practical strategies for picking as many low-hanging fruits as possible to make a real (albeit small) difference to your library's Web usability and UX effectively and efficiently.&lt;br /&gt;
&lt;br /&gt;
== A Semantic Makeover for CMS Data ==&lt;br /&gt;
&lt;br /&gt;
* Bill Levay, wjlevay@gmail.com, Linked Jazz Project&lt;br /&gt;
&lt;br /&gt;
How can we take semi-structured but messy metadata from a repository like CONTENTdm and transform it into rich linked data? Working with metadata from Tulane’s Hogan Jazz Archive Photography Collection, the Linked Jazz Project used Open Refine and Python scripts to tease out proper names, match them with name authority URIs, and specify FOAF relationships between musicians who appear together in photographs. Additional RDF triples were created for any dates associated with the photos, and for those images with place information we employed GeoNames URIs. Historical images and data that were siloed can now interact with other datasets, like Linked Jazz’s rich set of names and personal relationships, and can be visualized [link to come] or otherwise presented on the web in any number of ways. I have not previously presented at a Code4Lib conference.&lt;br /&gt;
&lt;br /&gt;
== Taking User Experience (UX) to new heights ==&lt;br /&gt;
 &lt;br /&gt;
* Kayne Richens, kayne.richens@deakin.edu.au, Deakin University&lt;br /&gt;
&lt;br /&gt;
User Experience, or &amp;quot;UX&amp;quot;, is for more than just websites. At Deakin University Library we're exploring ways to improve the user experience inside our campus library spaces, by putting new technologies front and centre in the overall experience for our students. How are we doing this? We’re collaborating with the University's IT department and exploring the following Library-changing opportunities:&lt;br /&gt;
&lt;br /&gt;
- Augmented Reality for Way-finding: We’re tackling that infamous thing that all Libraries can't get right – way-finding. We're enhancing library tour information and way-finding experiences by introducing augmented reality solutions.&lt;br /&gt;
 &lt;br /&gt;
- Heat mapping the library with wi-fi: We’re using our existing wi-fi infrastructure to present &amp;quot;heat maps&amp;quot; of library space utilisation, allowing our users to easily locate the space that best suits their needs, whether it be busy spaces to collaborate, or quiet spaces to study. And by overlaying computer usage and group study room bookings, users can quickly locate the space they need.&lt;br /&gt;
 &lt;br /&gt;
- Video chat library service: We’re piloting video-conferencing facilities in our group study rooms and spaces, connecting users and librarians and other professionals.&lt;br /&gt;
         &lt;br /&gt;
This talk will look at how these different technologies will be brought together to provide improved user experiences, as well some of the evidence and reasons that helped us to identify our needs, so you can too.&lt;br /&gt;
&lt;br /&gt;
==How to Hack it as a Working Parent: or, Should Your Face be Bathed in the Blue Glow of a Phone at 2 AM?==&lt;br /&gt;
&lt;br /&gt;
*Margaret Heller, Loyola University Chicago, mheller1@luc.edu&lt;br /&gt;
*Christina Salazar, California State University Channel Islands, christina.salazar@csuci.edu&lt;br /&gt;
*May Yan, Ryerson University, may.yan@ryerson.ca&lt;br /&gt;
&lt;br /&gt;
Modern technology has made it easier than ever for parents employed in technical environments to keep up with work at all hours and in all locations. This makes it possible to work a flexible schedule, but also may lead to problems with work/life balance and furthering unreasonable expectations about working hours. Add to that shifting gender roles and limited paid parental leave in the United States and you have potential for burnout and a certainty for anxiety. It raises the additioal question of whether the “always connected” mindset puts up a barrier to some populations who otherwise might be better represented in open source and library technology communities. &lt;br /&gt;
&lt;br /&gt;
This presentation will address tools that are useful for working parents in technical library positions, and share some lessons learned about using these tools while maintaining a reasonable work/life balance. We will consider a question that Karen Coyle raised back in 1996: &lt;br /&gt;
“What if the thousands of hours of graveyard shift amateur hacking wasn't really the best way to get the job done? That would be unthinkable.” &lt;br /&gt;
&lt;br /&gt;
For those who are able to take an extended parental leave, we will present strategies for minimizing the impact to your career and your employer. For those (particularly in the United States) who are only able to take a short leave will require different strategies. Despite different levels of preparation, all are useful exercises in succession planning and making a stronger workplace and future ability to work a flexible schedule through reviewing workloads, cross-training personnel, hiring contract replacements, and creative divisions of labor. Such preparation makes work better for everyone, kids or no kids or caretakers of any kind.&lt;br /&gt;
&lt;br /&gt;
==Making your digital objects embeddable around the web==&lt;br /&gt;
 &lt;br /&gt;
* Jessie Keck, jkeck@stanford.edu, Stanford University Libraries&lt;br /&gt;
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
With more and more content from our digital repositories making their way into our discovery environments we quickly realize that we’re repeatedly re-inventing the wheel when it comes to creating “Viewers” for these digital objects.  With various different types of viewers necessary (books, images, audio, video, geospatial data, etc) the burden of getting these viewers into various environments (topic guides, blogs, catalogs, etc) becomes exponential.&lt;br /&gt;
&lt;br /&gt;
In this talk we’ll discuss how Stanford University Libraries implemented an oEmbed service to create an extensible viewer framework for all of its digital content. Using this service we’ve been able to easily integrate viewers into various discovery applications as well as make it easy for end users who discover our objects to easily embed customized versions into their own websites and blogs.&lt;br /&gt;
&lt;br /&gt;
==So you want to make your geospatial data discoverable==&lt;br /&gt;
 &lt;br /&gt;
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
Finding data for research or coursework can be one of the most time intensive tasks for a scholar or student. We introduce GeoBlacklight, an open source, multi-institutional software project focused on solving these common challenges at institutions across the world. GeoBlacklight prioritizes user experience, integrates with many GIS tools, and streamlines the use and organization of geospatial data. This talk will provide an introduction to the software, demonstrate current functionality, and provide a road map for future work.&lt;br /&gt;
&lt;br /&gt;
== Clueless-Driven Development: How I learned to migrate to Fedora 4 ==&lt;br /&gt;
&lt;br /&gt;
* Adam Wead, awead@psu.edu, Penn State University&lt;br /&gt;
&lt;br /&gt;
Recently I was tasked with migrating the content from our Fedora3 repository to the new Fedora4 repository architecture.&lt;br /&gt;
Despite a wealth of community support, I had no idea how to approach, or even begin to solve this problem. I knew I&lt;br /&gt;
wanted to follow best practices and use test-driven  development to build my solution, but had no idea where to start.&lt;br /&gt;
Despite this initial setback, I was able to start writing tests with only a  vague understanding of the problem. As my&lt;br /&gt;
tests exposed where my understanding of the problem was flawed, my code evolved, and within a week I had arrived  at a&lt;br /&gt;
working solution that exhibited all the hallmarks of good testing and software design.&lt;br /&gt;
&lt;br /&gt;
This talk recounts the process I went through from starting with practically nothing, to arriving at a working solution.&lt;br /&gt;
You can follow the rules of  test-driven development, but you can write tests in an expressive way to describe the&lt;br /&gt;
problem instead of just describing what the code should do. It was also essential to begin testing from an integration&lt;br /&gt;
viewpoint as opposed to a unit one, because at the outset the units were unknown and were later realized through further&lt;br /&gt;
development. For the presentation, I will be demonstrating using RSpec and Ruby. All the code examples will be related&lt;br /&gt;
to the Hydra software stack; however, I hope to show  that the processes at work will be applicable in any context.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Designing and Leading a Kick A** Tech Team ==&lt;br /&gt;
 &lt;br /&gt;
* Sibyl Schaefer,  sschaefer@rockarch.org, Rockefeller Archive Center&lt;br /&gt;
&lt;br /&gt;
New managers are often promoted without receiving management training, yet management is not something you just figure out. The experience of being expected to know how to manage, yet not being trained to do so often results in new managers feeling isolated and unsure how to move from making to managing. In this talk I’ll focus on my own managerial experience of designing and leading an archival tech team in a small independent archives. Topics covered will include hiring, delegating, creating a team culture, and leading people whose specialized knowledge exceeds your own. The talk take-aways should be applicable to managers and employees at large and small institutions alike.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==American (Archives) Horror Story: LTO Failure and Data Loss ==&lt;br /&gt;
 &lt;br /&gt;
* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH&lt;br /&gt;
* Casey Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH&lt;br /&gt;
&lt;br /&gt;
Here’s a story to send shivers down archival spines: when transferring video files off LTO for the American Archive project, WGBH got an initial failure rate of 57%.   After repeat tries, the rates improved; still, an unnervingly large percentage of files were never able to be transferred successfully.   Even more unnerving, going public with our horror story got a big response from other archives using LTO -- it seems like many institutions are having similarly scary results.   What are the real risks with LTO tape?  Are there steps that archives should be taking to better circumvent those risks?  This presentation will share information about LTO storage failures across archives world and discuss the process of investigating the problem at WGBH by testing different methods of data retrieval from LTO (direct and networked downloads, individual file retrieval and bulk data dump, use of LTO 4 and LTO 6 decks) and using checksum comparisons and file analysis and characterization tools such as ffprobe, mediainfo and exiftool to analyze failed files.  We'll also present whatever results we’ve managed to turn up by the time of Code4Lib!&lt;br /&gt;
&lt;br /&gt;
== PBCore in Action: Three Words, Not Two! ==&lt;br /&gt;
 &lt;br /&gt;
* Casey E. Davis,  casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH&lt;br /&gt;
* Andrew (Drew) Myers, andrew_myers@wgbh.org, Supervising Developer, WGBH&lt;br /&gt;
&lt;br /&gt;
In 2001, public media representatives developed the PBCore XML schema to establish a common language for managing metadata about their analog and digital audio and video. Since then, PBCore has been adopted by a number of organizations and archivists in the moving image archival community. The schema has also undergone a few revisions, but on more than one occasion it was left orphaned and with little to no support.&lt;br /&gt;
 &lt;br /&gt;
Times have changed. You may have heard the news that PBCore is back in action as part of the American Archive of Public Broadcasting initiative and via the Association of Moving Image Archivists (AMIA) PBCore Advisory Subcommittee. A group of archivists, public media stakeholders, and engaged users have come together to provide necessary, sustaining support for the standard and to see to its further development. &lt;br /&gt;
 &lt;br /&gt;
At this session, we'll discuss the scope and uses of PBCore in digital preservation and access, report on the progress and goals of the PBCore Advisory Subcommittee, and share how the group (by the time of the conference) will have transformed the XML schema into an RDF ontology, bringing PBCore into the second decade of the 21st century. #PBHardcore&lt;br /&gt;
&lt;br /&gt;
==Collaborating to Avert the Digital Graveyard==&lt;br /&gt;
&lt;br /&gt;
* Harish Nayak, hnayak@library.rochester.edu, University of Rochester Libraries &lt;br /&gt;
* Sean Morris, smorris@library.rochester.edu, University of Rochester Libraries &lt;br /&gt;
&lt;br /&gt;
In 1995, the Robbins Library at the University of Rochester created a digital collection of Arthurian texts, images, and bibliographies. Together with medieval scholars, we recently completed the redesign and development of an interface for this collection. Using FRBR concepts, we re-conceptualized organization and editing workflow from the ground up in a mobile-first Drupal-based project. &lt;br /&gt;
&lt;br /&gt;
In this talk we will describe the project as well as how we utilized the techniques of work practice study and user centered design to maintain engagement with reluctant stakeholders, nontechnical scholars, and VERY meticulous graduate students.  Neither of us have previously presented at a Code4Lib conference.&lt;br /&gt;
&lt;br /&gt;
==Docker? VMs? EC2? Yes! With Packer.io==&lt;br /&gt;
&lt;br /&gt;
* Kevin S. Clarke, ksclarke@gmail.com, Digital Library Programmer, UCLA&lt;br /&gt;
&lt;br /&gt;
There are a lot of exciting ways to deploy a software stack nowadays. Many of our library systems are fully virtualized. Docker is a compelling alternative, and there are also cloud options like Amazon's EC2. This talk will introduce Packer.io, a tool for creating identical machine images for multiple platforms (e.g., Docker, VMWare, VirtualBox, EC2, GCE, OpenStack, et al.) all from a single source configuration.  It works well with Ansible, Chef, Puppet, Salt, and plain old Bash scripts. And, it's designed to be scriptable so that builds can be automated. This presentation will show how easy it is to use Packer.io to bring up a set of related services like Fedora 4, Grinder (for stress testing), and Graphite (for charting metrics). As an added value, all the buzzwords in this proposal will be defined and explained!&lt;br /&gt;
&lt;br /&gt;
== Technology on your Wrist: Cross-platform Smartwatch Development for Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:sanderson|Steven Carl Anderson]], sanderson@bpl.org, Boston Public Library (no previously accepted prepared talks but have done lightning talks in the past)&lt;br /&gt;
&lt;br /&gt;
I'll be the first to admit: smartwatches are unlikely to completely revolutionize how a library provides online services. But I believe they still represent an opportunity to further enhance existing library services and resources in a unique way.&lt;br /&gt;
&lt;br /&gt;
At the Boston Public Library (BPL), we're in the initial phases of designing a modest smartwatch app to provide notifications for circulation availability and checked-out-material due-date alerts by the end of current year. We're starting small, but we plan to evolve the concept over time as we see what (if any) traction such an application gets with potential users. For example, we plan to explore the possibility of adding &amp;quot;nearest branch to my current location&amp;quot; functionality to this app.&lt;br /&gt;
&lt;br /&gt;
Despite the &amp;quot;development phase&amp;quot; of this application as of this writing, this talk is not being given by a novice. As a technology enthusiast, I've released [http://www.phdgaming.com/smartwatch_projects/ five smartwatch applications] and have had two of those be finalists in a [http://www.phdgaming.com/samsung_challenge/ Samsung sponsored development challenge]. This experience not only will allow for the BPL to avoid many beginner mistakes in its smartwatch app development but also gives a much more complete understanding of the smartwatch development ecosystem.&lt;br /&gt;
&lt;br /&gt;
This talk will explore the following questions:&lt;br /&gt;
&lt;br /&gt;
* What kinds of online library services could potentially be transformed or translated into the smartwatch/wearable domain? What kinds of services are better left alone? These questions are currently being explored and I'll talk about our plans and experiences. Included will be any statistical information from our application launch along with statistics from my personal development.&lt;br /&gt;
&lt;br /&gt;
* How to support all the different operating systems these devices run without painful modifications to your codebase. (There's Tizen that is used by Samsung's Gear 2 and Gear S, Android Wear that is used by most other non-Apple manufacturers, then there is Apple's upcoming smartwatch itself, etc.)&lt;br /&gt;
&lt;br /&gt;
* How to support different screen resolutions on such a small device. From round to rectangular to perfectly square, smartwatches come in all different shapes these days.&lt;br /&gt;
&lt;br /&gt;
* What are the app stores like on these platforms? As I support multiple applications through different distribution networks, a guide to navigating how to distribute one's app is included and I'll reveal how these systems work “behind the curtain.”&lt;br /&gt;
&lt;br /&gt;
* What are common issues and pitfalls to avoid when doing development? Tips on broken APIs and how to cope or optimizing your code will be included.&lt;br /&gt;
&lt;br /&gt;
==Seeing the Forest From the Trees: The Art of Creating Workflows for Digital Projects ==&lt;br /&gt;
 &lt;br /&gt;
* Jen LaBarbera, j.labarbera@neu.edu, NDSR Resident, Northeastern University&lt;br /&gt;
* Joey Heinen, joseph_heinen@harvard.edu, NDSR Resident, Harvard University&lt;br /&gt;
* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH&lt;br /&gt;
* Tricia Patterson, triciap@mit.edu, NDSR Resident, MIT&lt;br /&gt;
&lt;br /&gt;
We have to &amp;quot;turn projects into programs&amp;quot; in order to create a solid and sustainable digital preservation initiative...but what the heck does that even mean? What does that look like?&lt;br /&gt;
&lt;br /&gt;
In this talk, members of the inaugural Boston cohort of the National Digital Stewardship Residency will discuss one piece of our digital preservation test kitchen: our stabs at creating digital workflows that will (hopefully) help our institutions turn digital preservation projects into programs. Specifically, we will talk about how difficult it is to create a general and overarching workflow for digital preservation tasks (e.g. ingest into repositories, format migrations, etc.) that incorporates various technical tools while also taking into account the myriad and unending list of possible exceptions or special scenarios. Turning these complicated, specific processes into a simplified and generalized workflow is an art. We haven't necessarily perfected that art yet, but in this talk, we'll share what has worked for us -- and what hasn't. We’ll also touch on the importance of documentation, and achieving that delicate balance of adequately thorough documentation that doesn’t pose the risk of information avalanche. These processes often create more questions than answers, but we'll share the answers that we (and our mentors) have found along the way!&lt;br /&gt;
&lt;br /&gt;
== Annotations as Linked Data with Fedora4 and Triannon (a Real Use Case for RDF!) ==&lt;br /&gt;
&lt;br /&gt;
* Rob Sanderson, azaroth@stanford.edu,  Stanford University Libraries&lt;br /&gt;
* Naomi Dushay, ndushay@stanford.edu,  Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
Annotations on content resources allow users to contribute knowledge within the digital repository space.  W3C Open Annotation provides a comprehensive model for web annotation on all types of content, using Linked Data as a fundamental framework.  Annotation clients generate instances of this model, typically using a JSON serialization, but need to store that data somewhere using a standard interaction pattern so that best of breed clients, servers, and data can be mixed and matched.&lt;br /&gt;
&lt;br /&gt;
Stanford is using Fedora4 for managing Open Annotations, via a middleware component called Triannon.  Triannon receives the JSON data from the annotation client, and uses the Linked Data Platform API implementation in Fedora4 to create, retrieve, update and delete the constituent resources.  Triannon could be easily modified to use other LDP implementations, or could be modified to work with linked data other than annotations.&lt;br /&gt;
&lt;br /&gt;
== Helping Google (and scholars, researchers, educators, &amp;amp; the public) find archival audio ==&lt;br /&gt;
&lt;br /&gt;
* Anne Wootton, anne@popuparchive.org, Pop Up Archive (www.popuparchive.org)&lt;br /&gt;
&lt;br /&gt;
Culturally significant digital audio collections are hard to discover on the web. There are major barriers keeping this valuable media from scholars, researchers, and the general public:&lt;br /&gt;
&lt;br /&gt;
Audio is opaque: you can’t picture sound, or skim the words in a recording. &lt;br /&gt;
Audio is hard to share: there’s no text to interact with. &lt;br /&gt;
Audio is not text: but since text is the medium of the web, there’s no path for audiences to find content-rich audio.&lt;br /&gt;
Audio metadata is inconsistent and incomplete.&lt;br /&gt;
&lt;br /&gt;
At Pop Up Archive, we're helping solve this problem making the spoken word searchable. We began as a UC-Berkeley School of Information Master's thesis to provide better access to recorded sound for audio producers, journalists, and historians. Today, Pop Up Archive processes thousands of hours of sound from all over the web to create automatic, timestamped transcripts and keywords, working with media companies and institutions like NPR, KQED, HuffPost Live, Princeton, and Stanford. We're building collections of sound from journalists, media organizations, and oral history archives from around the world. Pop Up Archive is supported by the John S. and James L. Knight Foundation, the National Endowment for the Humanities, and 500 Startups.&lt;br /&gt;
&lt;br /&gt;
== Digital Content Integrated with ILS Data for User Discovery:  Lessons Learned ==&lt;br /&gt;
&lt;br /&gt;
* Naomi Dushay, ndushay@stanford.edu,  Stanford University Libraries&lt;br /&gt;
* Laney McGlohon, laneymcg@stanford.edu,  Stanford University Libraries (first-time presenter)&lt;br /&gt;
&lt;br /&gt;
So you want to expose your digital content in your discovery interface, integrated with the data from your ILS?  How do you make the best information user searchable?  How do you present complete, up to date search results with a minimum of duplicate entries?&lt;br /&gt;
&lt;br /&gt;
At Stanford, we have these cases and more:&lt;br /&gt;
* digital content with no metadata in ILS&lt;br /&gt;
* digital content for metadata in ILS&lt;br /&gt;
* digital content with its own metadata derived from ILS metadata.&lt;br /&gt;
&lt;br /&gt;
We will describe our efforts to accommodate multiple updatable metadata sources for materials in the ILS and our Digital Object Repository while presenting users with reduced duplication in SearchWorks.  Included will be some failures, some successes, and an honest assessment of where we are now.&lt;br /&gt;
&lt;br /&gt;
== Show All the Things: Kanban for Libraries == &lt;br /&gt;
&lt;br /&gt;
* Mike Hagedon, mhagedon@email.arizona.edu, University of Arizona Libraries (first-time presenter)&lt;br /&gt;
&lt;br /&gt;
The web developers at the University of Arizona Libraries had a problem: we were working on a major website rebuild project with no clear way to prioritize it against our other work. We knew we wanted to follow Agile principles and initially chose Scrum to organize and communicate about our work. But we found that certain core pieces of Scrum did not work for our team. Then we discovered Kanban, an Agile meta-process for organizing work (team or individual) that treats the work more as a flow than as a series of fixed time boxes. I’ll be talking about our journey toward finding a process that works for our team and how we’ve applied the principles of Kanban to better get our work done. Specifically, I'll discuss principles like how to visualize all your work, how to limit how much you’re doing (to get more done!), and how to optimize the flow of your work.&lt;/div&gt;</summary>
		<author><name>Afred</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&amp;diff=41994</id>
		<title>2015 Prepared Talk Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&amp;diff=41994"/>
				<updated>2014-11-07T20:00:47Z</updated>
		
		<summary type="html">&lt;p&gt;Afred: /* PBCore in Action: Three Words, Not Two! */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Code4lib 2015 is a loosely-structured conference that provides people working at the intersection of libraries/archives/museums/cultural heritage and technology with a chance to share ideas, be inspired, and forge collaborations. For more information about the Code4lib community, please visit http://code4lib.org/about/. &lt;br /&gt;
The conference will be held at the Portland Hilton &amp;amp; Executive Tower in Portland, Oregon, from February 9-12, 2015.&lt;br /&gt;
&lt;br /&gt;
'''Proposals for Prepared Talks:'''&lt;br /&gt;
&lt;br /&gt;
We encourage everyone to propose a talk.&lt;br /&gt;
 &lt;br /&gt;
Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:&lt;br /&gt;
* Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software&lt;br /&gt;
* Tools and technologies – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)&lt;br /&gt;
* Technical issues - Big issues in library technology that should be addressed or better understood&lt;br /&gt;
* Relevant non-technical issues – Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc.&lt;br /&gt;
&lt;br /&gt;
Proposals can be submitted through Friday, November 7, 2014 at 5pm PST (GMT−8). Voting will start on November 11, 2014 and continue through November 25, 2014. The URL to submit votes will be announced on the Code4Lib website and mailing list and will require an active code4lib.org account to participate. The final list of presentations will be announced in early- to mid-December.&lt;br /&gt;
&lt;br /&gt;
'''Proposals for Prepared Talks:'''&lt;br /&gt;
&lt;br /&gt;
Log in to the Code4lib wiki and edit this wiki page using the prescribed format. If you are not already registered, follow the instructions to do so.&lt;br /&gt;
Provide a title and brief (500 words or fewer) description of your proposed talk.&lt;br /&gt;
If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist voters in opening the conference to new presenters.&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Talk Title: ==&lt;br /&gt;
 &lt;br /&gt;
* Speaker's name,  email address, and (optional) affiliation&lt;br /&gt;
* Second speaker's name, email address, and affiliation, if second speaker&lt;br /&gt;
&lt;br /&gt;
Abstract of no more than 500 words.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Talk Proposals'''&lt;br /&gt;
== Zines + Gamification = Awesomest Metadata Literacy Outreach Event Ever! ==&lt;br /&gt;
 &lt;br /&gt;
* [http://www.JenniferHecker.info Jennifer Hecker], jenniferraehecker@gmail.com, [http://www.lib.utexas.edu/subject/zines University of Texas Libraries] &amp;amp; [http://www.AustinFanzineProject.org Austin Fanzine Project]&lt;br /&gt;
* [http://anomalily.net/ Lillian Karabaic], librarian@iprc.org, [http://www.iprc.org/ Independent Publishing Resource Center] (Portland)&lt;br /&gt;
 &lt;br /&gt;
In academic libraries, and elsewhere, the popularity of zine (a magazine produced for love, not profit) collections is on the rise. At the same time, metadata literacy is becoming an increasingly important skill, helping people navigate and understand digital environments and interactions. We have found a way to teach metadata literacy to the general public that isn’t super-boring – in fact, we’ve made it downright fun!&lt;br /&gt;
&lt;br /&gt;
First, volunteer zine librarian Lillian Karabaic of Portland’s Independent Publishing Resource Center facilitated the creation of a gamified cataloging interface for the IPRC’s annual Raiders of the Lost Archives backlog-busting 24-hour volunteer cataloging event.&lt;br /&gt;
&lt;br /&gt;
Then, archivist Jennifer Hecker facilitated the adaptation of the IPRC’s game for use in a similar, but also very different context – promoting UT Libraries newly-acquired zine collections. The main goal of the academic-library-based event was increasing excitement around the collections, but with the side goal of building metadata literacy, and introducing an understanding of library cataloging issues.&lt;br /&gt;
&lt;br /&gt;
The Texas modification also conforms to the xZINECOREx metadata schema developed by the national [http://zinelibraries.info/ Zine Librarians Interest Group], and triggered interesting conversations with the Libraries’s cataloging department about evolving metadata standards and how to incorporate the products of crowd-sourcing projects into existing workflows.&lt;br /&gt;
&lt;br /&gt;
Both games will be demoed.&lt;br /&gt;
&lt;br /&gt;
We have never presented at Code4lib.&lt;br /&gt;
&lt;br /&gt;
== Do the Semantic FRBRoo ==&lt;br /&gt;
* Rosie Le Faive, rlefaive@upei.ca, University of Prince Edward Island&lt;br /&gt;
&lt;br /&gt;
[http://www.islandora.ca Islandora] is great for creating repositories of any data type, but how can you model meaningful relationships between digital objects and use them to tell a story?&lt;br /&gt;
&lt;br /&gt;
At UPEI, I’m assembling an ethnography of Prince Edward Island’s traditional fiddle music that includes musical clips, video clips, oral histories, musical notation, images, and ethnographic commentaries. In order to present an exhibition-style site, I’m tying these digital objects together via the people, places, events, tunes and topics that they share or describe. &lt;br /&gt;
&lt;br /&gt;
To describe the relationships, I’m extending Islandora to use [http://www.cidoc-crm.org/frbr_inro.html FRBRoo], a vocabulary that combines the FRBR model with CIDOC-CRM, the the object-oriented museum documentation ontology. These modules being developed will allow other researchers to create a structured, navigable digital repository of diverse object types, that uses Islandora as an exhibition platform. &lt;br /&gt;
&lt;br /&gt;
== Our $50,000 Problem: Why Library School? ==&lt;br /&gt;
* Jennie Rose Halperin, jhalperin@mozilla.com, Mozilla Corporation&lt;br /&gt;
&lt;br /&gt;
57 library schools in the United States are churning out approximately 100 graduates per year, many with debt upwards of $50,000.  According to ONet, [http://www.inthelibrarywiththeleadpipe.org/2011/is-the-united-states-training-too-many-librarians-or-too-few-part-1/ 84% of library jobs in the US require an MLS.] The library profession is [http://dpeaflcio.org/programs-publications/issue-fact-sheets/library-workers-facts-figures/) 92% white and 82% female and entry-level librarians can expect to make $32,500 per year.]&lt;br /&gt;
&lt;br /&gt;
Contrasted with developers, who are almost [http://www.ncwit.org/blog/did-you-know-demographics-technical-women 90% male] and can expect to make [http://www.forbes.com/sites/jennagoudreau/2011/06/01/best-entry-level-jobs/ $70,000 in an entry-level position,] these numbers are dismal.&lt;br /&gt;
&lt;br /&gt;
According to a recent survey, the top skill that outgoing library students want to know is “programming” and yet many MLS programs still consider Microsoft Word an essential technology skill.&lt;br /&gt;
&lt;br /&gt;
What is going on here? Why do we accept this fate, where mostly female debt-burdened professionals continue to be thrown onto the work force without the education their expensive degrees promised?&lt;br /&gt;
&lt;br /&gt;
As a community we need to come together to stop this cycle. We need to provide better support and mentorship to diversify and keep the profession relevant and help librarianship move into the future it deserves.&lt;br /&gt;
&lt;br /&gt;
This talk will walk through the challenges of navigating a hostile employment environment as well as present models for better development and future state imagining.&lt;br /&gt;
&lt;br /&gt;
== No cataloging software? Need more than Dublin Core? No problem!: Experiences with CollectiveAccess ==&lt;br /&gt;
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University&lt;br /&gt;
* Rachel Wittmann, rwittma@clemson.edu, Clemson University&lt;br /&gt;
&lt;br /&gt;
Clemson University Libraries has implemented the open-source software CollectiveAccess for customized digital collection needs. CollectiveAccess is an open-source project with the goal of providing a flexible way to manage and publish museum and archival collections. There are several applications associated with the projects; most used are: Providence (for cataloging and entering metadata) and Pawtucket (for displaying objects in a collection for the public). It has many profiles readily available for installing with existing library standards, such as Dublin Core, and there is a robust syntax for creating your own profiles to fit custom tailored metadata schemas. Plus, the user interface allows you to modify the metadata profile quickly and easily.&lt;br /&gt;
&lt;br /&gt;
In this talk, we will discuss:&lt;br /&gt;
* Our experiences with installing Providence and creating an installation profile that satisfies the needs of many of the Clemson Libraries digital archiving processes. &lt;br /&gt;
* The stumbling blocks experienced in that process and how they were resolved.&lt;br /&gt;
* The available plugins sourcing widely used authorities, such as Library of Congress thesauri and GeoNames.org, and how they have been used by our projects. &lt;br /&gt;
* A brief overview of the export and import functions and also current workflow practices within Providence.&lt;br /&gt;
* Future plans &amp;amp; the role of CollectiveAccess at Clemson University Libraries&lt;br /&gt;
&lt;br /&gt;
== Getting ContentDM and Wordpress to Play Together ==&lt;br /&gt;
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University&lt;br /&gt;
&lt;br /&gt;
Clemson University Libraries has a very strong program for digitizing and archiving photographs, and the Digital Imaging team processes many hundreds of photographs every month. These images are managed using different methods, including ContentDM, a digital collection manager.&lt;br /&gt;
&lt;br /&gt;
ContentDM provides various methods for searching and displaying photographs, along with their metadata. However, recent initiatives have resulted in the need to leverage those collections into exhibits displayed on other library-related websites, such as our Special Collections unit. The Clemson Libraries has invested heavily in Wordpress as our content management system of choice, and it seemed most efficient not to have to export and import images into our Wordpress sites in order to provide exhibited images.&lt;br /&gt;
&lt;br /&gt;
Fortunately, ContentDM has provided an API to many of their functions, allowing the extraction of metadata and even rescaled images through URLs. This project has been developing a plugin for Wordpress that integrates with ContentDM through shortcodes that Wordpress editors can easily include in their content. These shortcodes allow editors to choose how many images, which images from which collections, thumbnail sizes, etc. to display in different gallery styles. Plans are for it to allow integration with different plugins such as Fancybox and Masonry.&lt;br /&gt;
&lt;br /&gt;
In this presentation, I will demonstrate the current state of the plugin and discuss future plans. &lt;br /&gt;
&lt;br /&gt;
==Refinery — An open source locally deployable web platform for the analysis of large document collections==&lt;br /&gt;
 &lt;br /&gt;
* [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com&lt;br /&gt;
&lt;br /&gt;
Refinery is an open source web platform for the analysis of large unstructured document collections. It extracts meaningful semantic themes within documents also known as &amp;quot;topics&amp;quot; which can be thought of as word clouds composed of terms that highly co-occur with one another. Once this semantic index is formed, one can extract relevant documents related to these topics and further refine their contents through a summarization process that allows users to search for phrases that are relevant to them within the corpus. The goal of Refinery is to make this whole process easier and to provide some of the latest scalable versions of these learning algorithms in an intuitive web-based interface. Refinery is also meant to be run locally, thus bypassing the need for securing document collections over the internet. The talk will go through some of the technologies involved and a demo of the app.&lt;br /&gt;
&lt;br /&gt;
For more info check out http://www.docrefinery.org.&lt;br /&gt;
&lt;br /&gt;
==Drupal 8 — Evolution &amp;amp; Revolution==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Drupal 8 is in beta and nearing release. Among its many features, it notably has become more developer friendly through its adoption of the Symfony PHP framework along with Symfony's outstanding set of libraries (like Guzzle) and tools (like Composer). And, in implementing the Twig theming system, it is can begin to escape PHPtemplate. These moves also make it easier to create headless systems that uses Angular.js and other systems for presentation, or even forgo presentation entirely.&lt;br /&gt;
&lt;br /&gt;
From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.&lt;br /&gt;
&lt;br /&gt;
==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==&lt;br /&gt;
 &lt;br /&gt;
* [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]],  stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]&lt;br /&gt;
&lt;br /&gt;
GameSalad is a popular tool for developing mobile and desktop games with little actual programming. In this presentation, Stan Bogdanov breaks down the development process he followed while building [https://github.com/stanrb/mobiLit mobiLit], a mobile app with the goal of being the first open-source gamified information literacy app to be used as part of a college-level information literacy curriculum. He will go through the basics of using GameSalad to create an app that can be easily customized by non-programmers and the instructional principles used to teach the material in a mobile medium. Stan will also go through two qualitative design studies he did on the app and discuss their results and the lessons learned from building mobiLit. The session will conclude with an overview of the next steps for the [https://github.com/stanrb/mobiLit mobiLit project].&lt;br /&gt;
&lt;br /&gt;
==The Impossible Search: Pulling data from multiple unknown sources==&lt;br /&gt;
 &lt;br /&gt;
* Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com &lt;br /&gt;
&lt;br /&gt;
It's easy to search data you know the structure of, but what if you need to pull in data from sources that don't have a standard structure. The ability to search community events along with your standard catalog search results is an example, but often the only way to pull these events is through XML, JSON, (Insert structured format here), or even just raw html. But how do you get that structure? That simple question is what makes this impossible. The process to define and process this structure takes a lot of manual labor, especially if the data you are pulling is just HTML, and then every time you add data to the index you have to run all the data through a script to pull in data in a format Solr or an other index can use. This talk will focus on Solr, but the principles explained will apply to many other indexes.&lt;br /&gt;
&lt;br /&gt;
==What! You're Not Using Docker?==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Boring part: Docker[1] is a container system that provides benefits similar to virtualization with only a fraction of the overhead. Scintillating part: Docker can host between four to six times the number of service instances than systems such as Xen or VMWare on a given piece of hardware. But thats not all! Docker also makes it simple(r) to create transportable instances, so you can spin up development servers on your laptop.&lt;br /&gt;
&lt;br /&gt;
*[1]https://www.docker.com/&lt;br /&gt;
&lt;br /&gt;
== Video Accessibility, WebVTT, and Timed Text Track Tricks ==&lt;br /&gt;
&lt;br /&gt;
* Jason Ronallo, jronallo@gmail.com, NCSU Libraries&lt;br /&gt;
&lt;br /&gt;
Video on the Web presents new challenges and opportunities. How do you make your video more accessible to those with various disabilities and needs? I'll show you how. This presentation will focus on how to write and deliver captions, subtitles, audio descriptions, and timed metadata tracks for Web video using the WebVTT W3C standard. Encoding timed text tracks in this way opens up opportunities for new functionality on your websites beyond accessibility. The presentation will show some examples of the potential for using timed text tracks in creative ways. I'll cover all the HTML and JavaScript you will need to know as well as some of the CSS and other bits you could probably do without but are too fun to pass up.&lt;br /&gt;
&lt;br /&gt;
== Categorizing Records with Random Forests ==&lt;br /&gt;
 &lt;br /&gt;
* Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library&lt;br /&gt;
Academic libraries are increasingly responsible for providing ingest, search, discovery, and analysis for data sets.  Emerging techniques from data science and machine learning can provide librarians and developers with an opportunity to generate new insights and services from these document collections.  This presentation will provide a brief overview of common machine learning classification techniques, then dive into a more detailed example using a random forest to assign keywords to research data sets.  The talk will emphasize the insight that can be gained from machine learning rather than the inner workings of the algorithms.  The overall goal of this presentation is to provide librarians and developers with the context to recognize an opportunity to apply machine learning categorization techniques at their home campuses and organizations.  &lt;br /&gt;
&lt;br /&gt;
== Data Science in Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Devon Smith, smithde@oclc.org, OCLC&lt;br /&gt;
&lt;br /&gt;
Data Science is increasing in buzz and hype. I'll go over what it is, what it isn't, and how it fits in libraries.&lt;br /&gt;
&lt;br /&gt;
== PDF metadata extraction for academic literature == &lt;br /&gt;
&lt;br /&gt;
* Kevin Savage, kevin.savage at mendeley.com, Mendeley&lt;br /&gt;
* Joyce Stack, joyce.stack at mendeley.com, Mendeley&lt;br /&gt;
&lt;br /&gt;
Mendeley recently added a, &amp;quot;document from file,&amp;quot; endpoint to its API which attempts to extract metadata such as title and authors directly from PDF files. This talk will describe at a high level the machine learning methods we used including how we measured and tuned our model. We will then delve more deeply into our stack, the tools we used, some of the things that didn't work and why PDFs are the worst thing ever to compute over.&lt;br /&gt;
&lt;br /&gt;
== Giving Users What They Want: Record Grouping in VuFind ==&lt;br /&gt;
 &lt;br /&gt;
* Mark Noble,  mark@marmot.org, [//www.marmot.org Marmot Library Network]&lt;br /&gt;
&lt;br /&gt;
In 2013, Marmot did extensive usability studies with patrons to determine what was difficult in the catalog.  Many patrons had problems sifting through all of the various formats and editions of a title.  In 2014 we developed a method for [//mercury.marmot.org/Union/Search?lookfor=divergent grouping records] so only a single work is shown in search results and all formats and editions are listed under that work.  We will discuss our definition of a 'work' based on FRBR principles; combining meta data from MARC records with metadata from other sources like OverDrive; the technical details of Record Grouping; the design decisions made during implementation; and the reaction from users and staff.&lt;br /&gt;
&lt;br /&gt;
== Topic Space: a mobile augmented reality recommendation app ==&lt;br /&gt;
&lt;br /&gt;
* Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign&lt;br /&gt;
&lt;br /&gt;
The Topic Space module (http://minrvaproject.org/modules_topicspace.php ) was developed with an IMLS Sparks! Grant to investigate augmented reality technologies for in-library recommendations. The funding allowed for sustained university community collaboration by the University Library, the Graduate School of Library and Information Science, as well as graduate student programmers sourced from the Department of Computer Science. Collaborators designed app functionality and identified relevant open source libraries that could power optical character recognition (OCR) functionality from within the mobile phone.&lt;br /&gt;
&lt;br /&gt;
Topic space allows a user to take a picture of an item's call number in the book stacks. The module will show the user other books that are relevant but that are not shelved nearby. It can also show users books that are normally shelved here but that are currently checked out. Recommendations are based on Library of Congress subject headings and ILS circulation data which indicate recommendation candidates based on total check-outs. &lt;br /&gt;
&lt;br /&gt;
Research questions included development of back end (server-side) pattern matching algorithms for recommendations, and a rapid formative evaluation of interface design that would provide optimal user experience for navigation of the book stacks as a context to recommendations.&lt;br /&gt;
&lt;br /&gt;
Along with the Topic Space native app, grant collaborators prototyped web based recommendations which could serve as a new way of providing readers advisory and “more like this” recommendations from discovery interfaces accessed through desktop browsers. Outcomes of the grant include the availability of the [https://play.google.com/store/apps/details?id=edu.illinois.ugl.minrva Topic Spaces module within Minrva app on the Android Play store] and an experimental [http://backbonejs.org/ Backbone.js] based [http://minrva-dev.library.illinois.edu Topic Space web app].&lt;br /&gt;
&lt;br /&gt;
== Leveling Up Your Git Workflow ==&lt;br /&gt;
&lt;br /&gt;
* Megan Kudzia, moneill@albion.edu, Albion College Library&lt;br /&gt;
* Kate Sears, eks11@albion.edu, Albion College Library&lt;br /&gt;
&lt;br /&gt;
Have you started experimenting with Git on your own, but now you need to include others in your projects? Learn from our mistakes! Transitioning from a one-person git workflow and repo structure, to a structure that includes multiple people (including student workers), is not for the faint of heart. We'll talk about why we decided to work this way, our path to developing a git culture amongst ourselves, conceptual and technical difficulties we've faced, what we learned, and where we are now. Also with pretty pictures (aka workflow drawings).&lt;br /&gt;
&lt;br /&gt;
== Drone Loaning Program: Because Laptops are so last century ==&lt;br /&gt;
&lt;br /&gt;
 * Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries&lt;br /&gt;
 * Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries&lt;br /&gt;
&lt;br /&gt;
At Univ. Maryland we are in the very early stages of looking into allowing our student body get their hands on a drone. Yes that's right we will let students take out a drone for n amount of hours to work on projects of their choosing. The talk will talk about the logistics of getting a program of this sort from concept to &amp;quot;Is the drone available?&amp;quot;. If people sign waivers we will also promise not to crash the drone into code4lib attendees.&lt;br /&gt;
&lt;br /&gt;
== Got Git? Getting More Out of Your GitHub Repositories ==&lt;br /&gt;
&lt;br /&gt;
 * Terry Brady, twb27@georgetown.edu, Georgetown University Library&lt;br /&gt;
&lt;br /&gt;
This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories. &lt;br /&gt;
&lt;br /&gt;
In additional to all of the great benefits of using Git for code management, the GitHub interface provides a powerful set of tools to showcase a project and to keep your users informed of developments to your project.  These tools can assist with marketing and outreach - turning your code repository into a focus of conversation!&lt;br /&gt;
&lt;br /&gt;
* [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]&lt;br /&gt;
* [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]&lt;br /&gt;
* [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]&lt;br /&gt;
* [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]&lt;br /&gt;
* Gists for code sharing&lt;br /&gt;
* Private Repositories and Organizational Groups&lt;br /&gt;
* Pull Request Conversation Tracking&lt;br /&gt;
* Customized Issue management&lt;br /&gt;
&lt;br /&gt;
== Quick Wins for Every Department in the Library - File Analyzer! ==&lt;br /&gt;
&lt;br /&gt;
 * Terry Brady, twb27@georgetown.edu, Georgetown University Library&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.&lt;br /&gt;
* Analyzing Marc Records for the Cataloging department&lt;br /&gt;
* Transferring ILS invoices for the University Account System for the Acquisitions department &lt;br /&gt;
* Delivering patron fines to the Bursar’s office for the Access Service department&lt;br /&gt;
* Summarizing student worker timesheet data for the Finance department&lt;br /&gt;
* Validating COUNTER compliant reports for the Electronic Resources department&lt;br /&gt;
* Generating ingest packages for the Digital Services department&lt;br /&gt;
* Validating checksums for the Preservation department&lt;br /&gt;
&lt;br /&gt;
Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!&lt;br /&gt;
&lt;br /&gt;
==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor&lt;br /&gt;
&lt;br /&gt;
The transition from paper maps to digital ones changed much more than the maps themselves; it changed the very foundation of how we work and how we find each other. Now maps are transforming again.  The Geospatial World is moving from GIS systems that are institutionally-focused, expensive, feature-burdened, and binds data into a complicated and demanding user-hostile interface. From this transition from digital to web-based digital geospatial tools has come growth and development in new forms of map-based investigative journalism, activism, scholarship, and business ventures. This talk will highlight the conditions and strategies that made these changes possible as a means to draw a path by which librarians through our own work may follow, dragons notwithstanding. &lt;br /&gt;
&lt;br /&gt;
== Building Your Own Federated Search ==&lt;br /&gt;
&lt;br /&gt;
* Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco&lt;br /&gt;
&lt;br /&gt;
Advances in modern browsers have created some interesting possibilities for federated search. This presentation will cover common techniques and pitfalls in building a federated search. We will discuss what principles guided our decisions when implementing our own federated search. We will show tools we've built and our findings from building and using experimental prototypes.&lt;br /&gt;
&lt;br /&gt;
Your higher education institution likely offers dozens of online resources for educators, students, researchers, and the public. And each of these online resources likely has its own search tool. But users can't be expected to search in dozens of different interfaces to find what they're looking for. A typical solution for this issue is federated search. &lt;br /&gt;
&lt;br /&gt;
==  Indexing Linked Data with LDPath ==&lt;br /&gt;
&lt;br /&gt;
* Chris Beer, cabeer@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
LDPath [1] is a simple query language for indexing linked open data, with support for caching, content negotiation, and integration with non-RDF endpoints. This talk will demonstrate the features and potential of the language and framework to index a resource with links into id.loc.gov, viaf.org, geonames.org, etc to build an application-ready document.&lt;br /&gt;
&lt;br /&gt;
[1] http://marmotta.apache.org/ldpath/language.html&lt;br /&gt;
&lt;br /&gt;
== Show Me the Money: Integrating an LMS with Payment Providers ==&lt;br /&gt;
 &lt;br /&gt;
* Josh Weisman,  Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group&lt;br /&gt;
&lt;br /&gt;
In order to provide an easy and convenient way for patrons to pay fines, we are exploring ways to integrate the library management system with online payment providers such as PayPal. With many LMS systems being designed and developed for the cloud, we should be able to provide the frictionless user experience our patrons have come to expect from online transactions. In this session we'll discuss strategies for integration and review a sample application which uses REST APIs from a library management system to integrate with PayPal.&lt;br /&gt;
&lt;br /&gt;
== Shibboleth Federated Authentication for Library Applications: ==&lt;br /&gt;
&lt;br /&gt;
* Scott Fisher, scott.fisher@ucop.edu, California Digital Library&lt;br /&gt;
* Ken Weiss, ken.weiss@ucop.edu, California Digital Library&lt;br /&gt;
&lt;br /&gt;
Shibboleth is the most widely-used method to provide single-sign-on authentication to academic applications where users come from many different institutions. Shibboleth, the InCommon education and research trust framework, and the SAML protocol comprise a very powerful - but very complicated - solution to this very complicated problem. Scott and Ken have implemented Shibboleth for multiple library applications. They will share their understanding of the good, the bad, and the underlying spaghetti that makes it all work. Ken will discuss some of the technical aspects of the solution, touching on optimal and non-optimal use cases, administrative challenges, and authorization concerns. Scott will describe the implementation pattern for multi-institution single-sign-on that the California Digital Library has evolved, using the recently released Dash application (http://dash.cdlib.org) as an example.&lt;br /&gt;
&lt;br /&gt;
==Scientific Data: A Needs Assessment Journey==&lt;br /&gt;
 &lt;br /&gt;
*[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History&lt;br /&gt;
&lt;br /&gt;
While surveying digital research and collections data in the research science divisions at the American Museum of Natural History in NYC (as a part of my [http://ndsr.nycdigital.org/ National Digital Stewardship Residency] project), I have come across the big data hogs (genome sequencing and CT scanning) and the little pieces of data (images, publications), all equally important to not only scientific discovery, but as nodes in the history of science. &lt;br /&gt;
&lt;br /&gt;
In this session, I will discuss the development of my needs assessment surveys for scientific datasets and the interview process with Museum curators and researchers as background, seguing into an explanation of the results. I will then combine my findings into preliminary selection criteria to choose tools for digital preservation and management unique to scientific datasets. This will brooke a discussion on emerging standards, tools, and technologies in big data, specific to research science. &lt;br /&gt;
&lt;br /&gt;
I will conclude with preliminary findings on emerging technology that can be used to answer concerns surrounding the management and digital preservation of these data. I am hoping the Q&amp;amp;A session can be used to both answer questions about my project, and function as a way for you (the larger tech-savy library community)  to discuss the tools I’ve touched on in this talk. &lt;br /&gt;
&lt;br /&gt;
== Feminist Human Computer Interaction (HCI) in Library Software ==&lt;br /&gt;
 &lt;br /&gt;
* Bess Sadler,  bess@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
Libraries are not neutral repositories of knowledge. Library classification systems and search technologies tend to reflect the inequalities, biases, ethnocentrism, and power imbalances of the societies in which they are built [1]. How might we better resist these tendencies in the library software we create? This talk will examine some qualities of feminist HCI (pluralism, self-disclosure, participation, ecology, advocacy, and embodiment) [2] through the lens of library software. &lt;br /&gt;
&lt;br /&gt;
[1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.&lt;br /&gt;
&lt;br /&gt;
[2] Bardzell, Shaowen. Feminist HCI: Taking Stock and Outlining an Agenda for Design. CHI 2010: HCI For All. http://dmrussell.net/CHI2010/docs/p1301.pdf&lt;br /&gt;
&lt;br /&gt;
== Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==&lt;br /&gt;
&lt;br /&gt;
* Audrey Altman, audrey at dp.la, Digital Public Library of America&lt;br /&gt;
* Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America&lt;br /&gt;
* Mark Breedlove, mb at dp.la, Digital Public Library of America&lt;br /&gt;
&lt;br /&gt;
The Digital Public Library of America aggregates metadata for over 8 million objects from more than 24 direct partners, or Hubs, using its Metadata Application Profile (MAP), an RDF metadata application profile based on the Europeana Data Model. After working with the initial system for harvesting, mapping and enhancing our Hub’s metadata for a year, we realized that it was inadequate for working with data at this scale. There were architectural issues; it was opaque to non-developer and partner staff; there were inadequate tools for quality assurance and analysis; and the system was unaware that it was working with RDF data. As the network of Hubs expanded and we ingested more metadata, it became harder and harder to know when or why a harvest, a mapping task, or an enrichment went wrong because the tools for quality assurance were largely inadequate. &lt;br /&gt;
&lt;br /&gt;
The DPLA Content and Technology teams decided to develop a new system from the ground up to address those problems. Development of Heidrun, the internal version of the new system, started in October 2014. Heidrun’s goals are to make it easier for us to harvest and map metadata from various sources and in variety of schemas to the DPLA MAP, to better enrich that metadata using external data sources, and to actively involve our partners in the ingestion process through access to better QA tools. Heidrun and its componentry are built on Ruby on Rails, Blacklight, and ActiveTriples. Our presentation will give some background on our design principles and processes used during development, the architecture of the system, and its functionality. We plan to release a version of Heidrun and its components as a generalized metadata aggregation system for use by DPLA Hubs and others working to aggregate cultural heritage metadata.&lt;br /&gt;
&lt;br /&gt;
== OS or GTFO: Program or Perish ==&lt;br /&gt;
*Tessa Fallon, tessa.fallon@gmail.com&lt;br /&gt;
&lt;br /&gt;
Description TBD&lt;br /&gt;
&lt;br /&gt;
== Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==&lt;br /&gt;
* Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries&lt;br /&gt;
Would your library like to have large digital signage that displays dynamic information such as library hours, weather, room availability, and more? Have you looked into purchasing large digital signage, only to be turned off by the high price tag and lack of customization available with commercial solutions? Our library has developed a cheap and effective alternative to these systems using HTML 5 authoring software, a large TV, and freely-available APIs from Google, Springshare, and others. At this session, you’ll learn about the system that we have in place for displaying dynamic and easily-updatable information on our library’s large digital display, and how you can easily create something similar for your library.&lt;br /&gt;
&lt;br /&gt;
== REPOX: Metadata Blender ==&lt;br /&gt;
 &lt;br /&gt;
* John Mignault, jmignault@metro.org, Empire State Digital Network&lt;br /&gt;
&lt;br /&gt;
With the growth in the number of hubs providing metadata to the Digital Public Library of America, many of them are using REPOX, a tool originally created for the Europeana project, to aggregate disparate metadata feeds and transform them into formats suitable for ingest into DPLA. The Empire State Digital Network, the forthcoming DPLA service hub for NY state, is using it to prepare for our first ingest into DPLA in early 2015.  We'll take a look at REPOX and its capabilities and how it can be useful for ingesting and transforming metadata, and also discuss some things we've learned in massaging widely varied metadata feeds.&lt;br /&gt;
&lt;br /&gt;
== Beyond Open Source ==&lt;br /&gt;
&lt;br /&gt;
* Jason Casden, jmcasden@ncsu.edu, NCSU Libraries&lt;br /&gt;
* Bret Davidson, bddavids@ncsu.edu, NCSU Libraries&lt;br /&gt;
&lt;br /&gt;
The Code4Lib community has produced an increasingly impressive collection of open source software over the last decade, but much of this creative work remains out of reach for large portions of the library community. Do the relatively privileged institutions represented by a majority of Code4Lib participants have a professional responsibility to support the adoption of their innovations?&lt;br /&gt;
&lt;br /&gt;
Drawing from old and new software packaging and distribution approaches (from freeware to Docker), we will propose extending the open source software values of collaboration and transparency to include the wide and affordable distribution of software. We believe this will not only simplify the process of sharing our applications within the Code4Lib community, but also make it possible for less well resourced institutions to actually use our software. We will identify areas of need, present our experiences with the users of our own open source projects, discuss our attempts to go beyond open source, and make an argument for the internal value of supporting and encouraging a vibrant library ecosystem.&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]] &lt;br /&gt;
[[Category:Talk Proposals]]&lt;br /&gt;
&lt;br /&gt;
== Making It Work: Problem Solving Using Open Source at a Small Academic Library ==&lt;br /&gt;
 &lt;br /&gt;
* Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology&lt;br /&gt;
* Max King, mking9@iit.edu, Illinois Institute of Technology&lt;br /&gt;
&lt;br /&gt;
The Illinois Institute of Technology campus was added to the National Register of Historic Places in 2005, and contains a building, Mies van der Rohe's S.R. Crown Hall, that was named a National Historic Landmark in 2001. Creating a digital resource that can adequately showcase the campus and its architecture is challenge enough in and of itself, but doing so as a two-person team of relative newcomers, at a university library without dedicated programmers on staff, ups the ante considerably.&lt;br /&gt;
The challenges of technical know-how, staff time, and funding are nothing new to anyone working on digital projects at a university library, and are amplified when doing so at a smaller institution. This talk covers the conception, development, and design of the campus map site that was built, concentrating on the problem-solving strategies developed to cope with limited technical and financial resources.&lt;br /&gt;
We'll talk about our approach to development with Open Source software, including Omeka, along with the Neatline and Simile Timeline plugins. We'll also discuss the juggling act of designing for mobile mapping functionality without sacrificing desktop design, weighing the costs of increased functionality versus our ability to time-effectively include that functionality, and the challenge of building a site that could be developed iteratively, with an eye towards future enhancement and sustainability. Finally, we’ll provide recommendations for other librarians at smaller institutions for their own efforts at digital development.&lt;br /&gt;
&lt;br /&gt;
== Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==&lt;br /&gt;
 &lt;br /&gt;
* Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art&lt;br /&gt;
&lt;br /&gt;
The Museum of Modern Art has amassed a large collection of audiovisual materials over its many decades of existence. In order to preserve these materials, much of the audiovisual collection has been digitized. This is a complex process involving numerous steps and devices, and the methods used for digitization can have an effect on the quality of the file that is preserved. Therefore, knowing exactly how something was digitized is critical for future stewards of these objects to be able to properly care for and preserve them. However, detailed technical information about the processes involved in the digitization of audiovisual materials is not defined explicitly in most metadata schemas used for audiovisual materials. In order to record process history using existing metadata standards, some level of creativity is required to allow existing standards to express this information.&lt;br /&gt;
&lt;br /&gt;
This talk will detail different metadata standards, including PBCore, PREMIS, and reVTMD, that can be implemented as methods of recording this information. Specifically, the talk will examine efforts to integrate this metadata into the Museum of Modern Art’s new digital repository, the DRMC. This talk will provide background on the DRMC as well as MoMA’s specific institutional needs for process history metadata, then discuss different metadata implementations we have considered to document process history.&lt;br /&gt;
&lt;br /&gt;
== Pig Kisses Elephant: Building Research Data Services for Web Archives ==&lt;br /&gt;
 &lt;br /&gt;
* Jefferson Bailey,  jefferson@archive.org, Internet Archive&lt;br /&gt;
* Vinay Goel, vinay@archive.org, Internet Archive&lt;br /&gt;
&lt;br /&gt;
More and more libraries and archives are creating web archiving programs.  For both new and established programs, these archives can consist of hundreds of thousands, if not millions, of born-digital resources within a single collection; as such, they are ideally suited for large-scale computational study and analysis. Yet current access methods for web archives consist largely of browsing the archived web in the same manner as browsing the live web and the size of these collections and complexity of the WARC format can make aggregate analysis difficult. This talk will describe a project to create new ways for users and researchers to access and study web archives by offering extracted and post-processed datasets derived from web collections. Working with the 325+ institutions and their 2600+ collections within the Archive-It service, the Internet Archive is building methods to deliver a variety of datasets culled from collections of web content, including extracted metadata packaged in JSON, longitudinal link graph data, named entities, and other types of data. The talk will cover the technical details of building dataset production pipelines with Apache Pig, Hadoop, and tools like Stanford NER, the programmatic aspects of building data services for archives and researchers, and ongoing work to create new ways to access and study web archives.&lt;br /&gt;
&lt;br /&gt;
== Awesome Pi, LOL! ==&lt;br /&gt;
&lt;br /&gt;
* Matt Connolly, mconnolly@cornell.edu, Cornell University Library&lt;br /&gt;
* Jennifer Colt, jrc88@cornell.edu, Cornell University Library&lt;br /&gt;
&lt;br /&gt;
Inspired by Harvard Library Lab’s “Awesome Box” project, Cornell’s Library Outside the Library (LOL) group is piloting a more automated approach to letting our users tell us which materials they find particularly stunning. Armed with a Raspberry Pi, a barcode scanner, and some bits of kit that flash and glow, we have ventured into the foreign world of hardware development. This talk will discuss what it’s like for software developers and designers to get their hands dirty, how patrons are reacting to the Awesomizer, and LOL’s not-afraid-to-fail philosophy of experimentation.&lt;br /&gt;
&lt;br /&gt;
== You Gotta Keep 'em Separated: The Case for &amp;quot;Bento Box&amp;quot; Discovery Interfaces ==&lt;br /&gt;
 &lt;br /&gt;
* Jason Thomale,  jason.thomale@unt.edu, University of North Texas Libraries&lt;br /&gt;
&lt;br /&gt;
I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.&lt;br /&gt;
&lt;br /&gt;
The thing is, practically all of us--in academic libraries at least--have a similar set up for discovery, with just a few variations, and so talking about it still seems useful. Stop me if this sounds familiar. You've got a single search box on the library homepage as a starting point for discovery. And it's probably a tabbed affair, with an option for searching the catalog for books, an option for searching a discovery service for articles, an option for searching databases, and maybe a few others. Maybe you have an option to search everything at once--probably the default, if you have it. And, if you're a crazy hepcat, maybe you ''only'' have your one search that searches everything, with no tabs.&lt;br /&gt;
&lt;br /&gt;
Now, the question is, for your &amp;quot;everything&amp;quot; search, are you doing a combined list of results, or are you doing it bento-box style, with a short results list from each category displayed in its own compartment?&lt;br /&gt;
&lt;br /&gt;
At UNT, we've been holding off on implementing an &amp;quot;everything&amp;quot; search, for various reasons. One reason is that the evidence for either style hasn't been very clear. There's this persistent paradox that we just can't reconcile: users tell us, through word and action, that they prefer searching Google, yet, libraries aren't Google, and there are valid design reasons why we shouldn't try to oversimplify our discovery interfaces to be like Google. And there's user data that supports both sides.&lt;br /&gt;
&lt;br /&gt;
Holding off on making this decision has granted us 2 years of data on how people use our tabbed search interface that does ''not'' include an &amp;quot;everything&amp;quot; search. Recently I conducted a thorough analysis of this data--specifically the usage and query data for our catalog and discovery system (Summon). And I think it helps make the case for a bento box style discovery interface. To be clear, it isn't exactly the smoking gun that I was hoping for, but the picture it paints I think is telling. At the very least, it points away from a combined-results approach.&lt;br /&gt;
&lt;br /&gt;
I'm proposing a talk discussing the data we've collected, the trends we've seen, and what I think it all means--plus other reasons that we're jumping on the &amp;quot;bento box&amp;quot; discovery bandwagon and why I think &amp;quot;bento box&amp;quot; is at this point the path that least sells our souls.&lt;br /&gt;
&lt;br /&gt;
== Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift ==&lt;br /&gt;
 &lt;br /&gt;
* Ashley Blewer!, ashley.blewer@gmail.com&lt;br /&gt;
&lt;br /&gt;
Checksum technology is used all over the place, from git commits to authenticating Linux packages. It is most commonly used in the digital preservation field to monitor materials in storage for changes that will occur over time or used in the transmission of files during duplication. But do you even checksum, bro? I want this talk to move checksums from a position of mysterious macho jargon to something everyone can understand and want to use. I think a lot of people have heard of checksum but don’t know where to begin when it comes to actually using it at their institution. And cryptography is hella intimidating! This talk will cover what checksums are, how they can be integrated into a library or archival workflow, protecting collections requiring additional levels of security, algorithms used to verify file fixity and how they are different, and other aspects of cryptographic technology. Oh, and please note that all points in this talk will be emphasized or lightly performed through Taylor Swift lyrics. Seriously, this talk will consist of at least 50% Taylor Swift. Can you, like, even?&lt;br /&gt;
&lt;br /&gt;
== Level Up Your Coding with Code Club (yes, you can talk about it) ==&lt;br /&gt;
&lt;br /&gt;
* Coral Sheldon-Hess, coral@sheldon-hess.org&lt;br /&gt;
&lt;br /&gt;
Reading code is a necessary part of becoming a better developer. It gives you more experience and more insight into How Things Are (or Aren't) Done; it builds your intuition about how to solve problems with code; and it increases your confidence that you, too, can tackle whatever technological problems you're facing.&lt;br /&gt;
&lt;br /&gt;
But you don't have to read code alone! (Which is good. It's really not fun to read code alone.) &lt;br /&gt;
&lt;br /&gt;
In late 2014, a group of librarians formed two Code Clubs, inspired by [http://bloggytoons.com/code-club/ this talk by Saron] (of Bloggytoons fame). I'd like to tell you about how we've structured our Code Clubs, what has gone well, what we've learned, and what you need to do to form your own Code Club. I'll share a list of the codebases we've looked at, too, to help you get your own Code Club off the ground! &lt;br /&gt;
&lt;br /&gt;
== The Growth of a Programmer ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:jgo | Joshua Gomez]], Getty Research Institute, jgomez@getty.edu&lt;br /&gt;
&lt;br /&gt;
Just like other creative endeavors, software developers can experience periods of great productivity or find themselves in a rut. After contemplating the alternating periods in my own career I've noticed several factors that have effected my own professional growth and happiness, including: mentorship, structure, community, teamwork, environment, formal education, etc. Not all of the factors need to be present at all times; but some mixture of them is critical for continued growth. In this talk, I will articulate these factors, discuss how they can effect a developer's career, and how they can be sought out when missing. This talk is aimed at both new developers looking to strike their own path as well as the veterans that lead or mentor them.&lt;br /&gt;
&lt;br /&gt;
== Developing a Fedora 4.0 Content Model for Disk Images ==&lt;br /&gt;
&lt;br /&gt;
* Matthew Farrell, matthew.j.farrell@duke.edu, Duke University Libraries&lt;br /&gt;
* Alexandra Chassanoff, achass@email.unc.edu, BitCurator Access Project Manager&lt;br /&gt;
&lt;br /&gt;
As the acquisition of born-digital materials grows, institutions are seeking methods to facilitate easy ingest into their repositories and provide access to disk images and files derived or extracted from disk images. In this session, we describe our development of a Fedora 4.0 Content model for disk images, including acceptable image file formats and the rationale behind those choices.  We will also discuss efforts to integrate the disk image content model into the BitCurator Access environment. Unlike generalized, format-agnostic content models which might treat the disk image as a generic bitstream, a content model designed for disk images enables expression of relationships among associated content in the collection such as files extracted from images and other born-digital and digitized material associated with the same creator.  It also enables capture of file-system attributes such as file paths, timestamps, whether files are allocated/deleted, etc.  Further, a disk image content model suggests further steps repositories can take in order to transform and re-use associated metadata generated during the creation and forensic analysis of the disk image.&lt;br /&gt;
&lt;br /&gt;
== Data acquisition and publishing tools in R ==&lt;br /&gt;
&lt;br /&gt;
* Scott Chamberlain,  scott@ropensci.org, rOpenSci/UC Berkeley - first-time presenter&lt;br /&gt;
&lt;br /&gt;
R is an open source programming environment that is widely used among researchers in many fields. R is powerful because it's free, increasingly robust, and facilitates reproducible research, an increasingly sought after goal in academia. Although tools for data manipulation/visualization/analysis are well developed in R, data acquisition and publishing tools are not. rOpenSci is a collaborative effort to create the tools necessary to complete the reproducible research workflow. This presentation discusses the need for these tools, including examples, including interacting with the repositories Mendeley, Dryad, DataONE, and Figshare. In addition, we are building tools for searching scholarly metadata and acuiring full text of open access articles in a standarized way across metadata providers (e.g., Crossref, DataCite, DPLA) and publishers (e.g., PLOS, PeerJ, BMC, Pubmed). Last, we are building out tools for data reading and writing in Ecologial Metadata Language (EML).&lt;br /&gt;
&lt;br /&gt;
== SPLUNK: Log File Analysis ==&lt;br /&gt;
&lt;br /&gt;
* Jim LeFager, jlefager@depaul.edu, DePaul University Library&lt;br /&gt;
DePaul University Library recently took over monitoring and maintaining of the library EZproxy servers this past year and using Splunk, a machine data analysis tool, we are able to gather information and statistics on our electronic resource usage in addition to monitoring the servers. Splunk is a tool that can collect, analyze, and visualize log files and other machine data in real time and this has allowed for gathering realtime usage statistics for our electronic resources allowing us to filter by multiple facets including IP Range, Group Membership (student, faculty), so that we can see who is accessing our resources and from where. Splunk allows our library to query our data and create rich custom dashboards as well as create alerts that can be triggered when certain conditions are met, such as error codes, which can send an email alert to a group of users. We will be leveraging Splunk to monitor all library web applications going forward. This talk will review setting up Splunk and best practices in using the available features and customizations available including creating queries, alerts, and custom dashboards.  &lt;br /&gt;
&lt;br /&gt;
== Your code does not exist in a vacuum ==&lt;br /&gt;
* Becky Yoose, yoosebec at grinnell dot edu, Grinnell College (Done a lightning talk, MC duties, but have not presented a prepared talk)&lt;br /&gt;
&lt;br /&gt;
“If you have something to say, then say it in code…” - Sebastian Hammer, code4lib 2009&lt;br /&gt;
&lt;br /&gt;
In its 10 year run, code4lib has covered the spectrum of libtech development, from search to repositories to interfaces. However, during this time there has been little discussion about this one little fact about development - code does not exist in a vacuum. &lt;br /&gt;
&lt;br /&gt;
Like the comment above, code has something to say. A person’s or organization’s culture and beliefs influences code in all steps of the development cycle. What development method you use, tools, programming languages, licenses - everything is interconnected with and influenced by the philosophies, economics, social structures, and cultural beliefs of the developer and their organization/community.&lt;br /&gt;
&lt;br /&gt;
This talk will discuss these interconnections and influences when one develops code for libraries, focusing on several development practices (such as “Fail Fast, Fail Often” and Agile)   and licensing choices (such as open source) that libtech has either tried to model or incorporate into mainstream libtech practices. It’ll only scratch the surface of the many influences present in libtech development, but it will give folks a starting point to further investigate these connections at their own organizations and as a community as a whole.&lt;br /&gt;
&lt;br /&gt;
tl;dr - this will be a messy theoretical talk about technology and libraries. No shiny code slides, no live demos. You might come out of this talk feeling uncomfortable. Your code does not exist in a vacuum. Then again, you don’t exist in a vacuum either.&lt;br /&gt;
&lt;br /&gt;
== The Metadata Hopper: Mapping and Merging Metadata Standards for Simple, User-Friendly Access ==&lt;br /&gt;
&lt;br /&gt;
* Tracy Seneca, tjseneca@uic.edu, University of Illinois at Chicago&lt;br /&gt;
* Esther Verreau: verreau1@uic.edu, University of Illinois at Chicago&lt;br /&gt;
&lt;br /&gt;
The Chicago Collections Consortium: 15 institutions and growing!  8 distinct EAD standards! At least 3 permutations of MARC, and we lost count of the varieties of custom CONTENTdm image collections.  Not to mention the 14,730 unique subject terms, nearly all of which lead our poor end-users to exactly one organization's content. &lt;br /&gt;
&lt;br /&gt;
All large content aggregation projects have faced this challenge, and there are a few emerging tools to help us wrangle disparate metadata into new contexts.  The Metadata Hopper is one such tool. The Metadata Hopper enables archivists to map their local metadata standards to standardized deposit records, and tags those materials using a shared vocabulary, integrating them into a user-friendly portal without disrupting local practices. In last year's Code4Lib lightning talk we described the challenges that the Chicago Collections Consortium faces in creating shared, in-depth access to archival and digital collections about Chicago history and culture across CCC member organizations. This year, thanks to the Andrew W. Mellon Foundation, we have a working Django application to demonstrate.  In this talk we'll discuss the design that enables multiple layers of flexibility, from the ability to accept a variety of metadata standards to designing for an open source audience.&lt;br /&gt;
&lt;br /&gt;
http://chicagocollectionsconsortium.org&lt;br /&gt;
&lt;br /&gt;
== Programmers are not projects: lessons learned from managing humans ==&lt;br /&gt;
&lt;br /&gt;
* Erin White, erwhite@vcu.edu, Virginia Commonwealth University - first-time presenter&lt;br /&gt;
&lt;br /&gt;
Managing projects is one thing, but managing people is another. Whether we’re hired as managers or grow “organically” into management roles, sometimes technical people end up leading technical teams (gasp!). I’ll talk about lessons I’ve learned about hiring, retaining, and working long-term and day-to-day with highly tech-competent humans. I’ll also talk about navigating the politics of libraryland, juggling different types of projects, and working with constrained budgets to make good things and keep talented people engaged.&lt;br /&gt;
&lt;br /&gt;
== Practical Strategies for Picking Low-Hanging Fruits to Improve Your Library's Web Usability and UX ==&lt;br /&gt;
&lt;br /&gt;
* Bohyun Kim, bkim@hshsl.umaryland.edu, University of Maryland, Baltimore&lt;br /&gt;
&lt;br /&gt;
Have you ever tried to fix an obvious (to you at least!) problem in Web usability or UX (user experience) only to face strong resistance from the library staff? Are you a strong advocate for making library resources, systems, services, and space as usable as possible, but do you often find yourself struggling to get the point across and/or obtain the crucial buy-in from colleagues and administrators? &lt;br /&gt;
&lt;br /&gt;
There is no shortage of Web usability and UX guidelines. But applying them to a library and implementing desired changes often involve a long and slow process. To tackle this issue, this talk will focus on how to utilize the 'expert review' process (aka 'heuristic evaluation') as a preliminary or even preparatory step before embarking on more time-and-labor-intensive usability testing and user research. Several examples from  simple fixes to more nuanced usability and UX issues in libraries will be discussed to your heart's content. The goal of this talk is to provide practical strategies for picking as many low-hanging fruits as possible to make a real (albeit small) difference to your library's Web usability and UX effectively and efficiently.&lt;br /&gt;
&lt;br /&gt;
== A Semantic Makeover for CMS Data ==&lt;br /&gt;
&lt;br /&gt;
* Bill Levay, wjlevay@gmail.com, Linked Jazz Project&lt;br /&gt;
&lt;br /&gt;
How can we take semi-structured but messy metadata from a repository like CONTENTdm and transform it into rich linked data? Working with metadata from Tulane’s Hogan Jazz Archive Photography Collection, the Linked Jazz Project used Open Refine and Python scripts to tease out proper names, match them with name authority URIs, and specify FOAF relationships between musicians who appear together in photographs. Additional RDF triples were created for any dates associated with the photos, and for those images with place information we employed GeoNames URIs. Historical images and data that were siloed can now interact with other datasets, like Linked Jazz’s rich set of names and personal relationships, and can be visualized [link to come] or otherwise presented on the web in any number of ways. I have not previously presented at a Code4Lib conference.&lt;br /&gt;
&lt;br /&gt;
== Taking User Experience (UX) to new heights ==&lt;br /&gt;
 &lt;br /&gt;
* Kayne Richens, kayne.richens@deakin.edu.au, Deakin University&lt;br /&gt;
&lt;br /&gt;
User Experience, or &amp;quot;UX&amp;quot;, is for more than just websites. At Deakin University Library we're exploring ways to improve the user experience inside our campus library spaces, by putting new technologies front and centre in the overall experience for our students. How are we doing this? We’re collaborating with the University's IT department and exploring the following Library-changing opportunities:&lt;br /&gt;
&lt;br /&gt;
- Augmented Reality for Way-finding: We’re tackling that infamous thing that all Libraries can't get right – way-finding. We're enhancing library tour information and way-finding experiences by introducing augmented reality solutions.&lt;br /&gt;
 &lt;br /&gt;
- Heat mapping the library with wi-fi: We’re using our existing wi-fi infrastructure to present &amp;quot;heat maps&amp;quot; of library space utilisation, allowing our users to easily locate the space that best suits their needs, whether it be busy spaces to collaborate, or quiet spaces to study. And by overlaying computer usage and group study room bookings, users can quickly locate the space they need.&lt;br /&gt;
 &lt;br /&gt;
- Video chat library service: We’re piloting video-conferencing facilities in our group study rooms and spaces, connecting users and librarians and other professionals.&lt;br /&gt;
         &lt;br /&gt;
This talk will look at how these different technologies will be brought together to provide improved user experiences, as well some of the evidence and reasons that helped us to identify our needs, so you can too.&lt;br /&gt;
&lt;br /&gt;
==How to Hack it as a Working Parent: or, Should Your Face be Bathed in the Blue Glow of a Phone at 2 AM?==&lt;br /&gt;
&lt;br /&gt;
*Margaret Heller, Loyola University Chicago, mheller1@luc.edu&lt;br /&gt;
*Christina Salazar, California State University Channel Islands, christina.salazar@csuci.edu&lt;br /&gt;
*May Yan, Ryerson University, may.yan@ryerson.ca&lt;br /&gt;
&lt;br /&gt;
Modern technology has made it easier than ever for parents employed in technical environments to keep up with work at all hours and in all locations. This makes it possible to work a flexible schedule, but also may lead to problems with work/life balance and furthering unreasonable expectations about working hours. Add to that shifting gender roles and limited paid parental leave in the United States and you have potential for burnout and a certainty for anxiety. It raises the additioal question of whether the “always connected” mindset puts up a barrier to some populations who otherwise might be better represented in open source and library technology communities. &lt;br /&gt;
&lt;br /&gt;
This presentation will address tools that are useful for working parents in technical library positions, and share some lessons learned about using these tools while maintaining a reasonable work/life balance. We will consider a question that Karen Coyle raised back in 1996: &lt;br /&gt;
“What if the thousands of hours of graveyard shift amateur hacking wasn't really the best way to get the job done? That would be unthinkable.” &lt;br /&gt;
&lt;br /&gt;
For those who are able to take an extended parental leave, we will present strategies for minimizing the impact to your career and your employer. For those (particularly in the United States) who are only able to take a short leave will require different strategies. Despite different levels of preparation, all are useful exercises in succession planning and making a stronger workplace and future ability to work a flexible schedule through reviewing workloads, cross-training personnel, hiring contract replacements, and creative divisions of labor. Such preparation makes work better for everyone, kids or no kids or caretakers of any kind.&lt;br /&gt;
&lt;br /&gt;
==Making your digital objects embeddable around the web==&lt;br /&gt;
 &lt;br /&gt;
* Jessie Keck, jkeck@stanford.edu, Stanford University Libraries&lt;br /&gt;
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
With more and more content from our digital repositories making their way into our discovery environments we quickly realize that we’re repeatedly re-inventing the wheel when it comes to creating “Viewers” for these digital objects.  With various different types of viewers necessary (books, images, audio, video, geospatial data, etc) the burden of getting these viewers into various environments (topic guides, blogs, catalogs, etc) becomes exponential.&lt;br /&gt;
&lt;br /&gt;
In this talk we’ll discuss how Stanford University Libraries implemented an oEmbed service to create an extensible viewer framework for all of its digital content. Using this service we’ve been able to easily integrate viewers into various discovery applications as well as make it easy for end users who discover our objects to easily embed customized versions into their own websites and blogs.&lt;br /&gt;
&lt;br /&gt;
==So you want to make your geospatial data discoverable==&lt;br /&gt;
 &lt;br /&gt;
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
Finding data for research or coursework can be one of the most time intensive tasks for a scholar or student. We introduce GeoBlacklight, an open source, multi-institutional software project focused on solving these common challenges at institutions across the world. GeoBlacklight prioritizes user experience, integrates with many GIS tools, and streamlines the use and organization of geospatial data. This talk will provide an introduction to the software, demonstrate current functionality, and provide a road map for future work.&lt;br /&gt;
&lt;br /&gt;
== Clueless-Driven Development: How I learned to migrate to Fedora 4 ==&lt;br /&gt;
&lt;br /&gt;
* Adam Wead, awead@psu.edu, Penn State University&lt;br /&gt;
&lt;br /&gt;
Recently I was tasked with migrating the content from our Fedora3 repository to the new Fedora4 repository architecture.&lt;br /&gt;
Despite a wealth of community support, I had no idea how to approach, or even begin to solve this problem. I knew I&lt;br /&gt;
wanted to follow best practices and use test-driven  development to build my solution, but had no idea where to start.&lt;br /&gt;
Despite this initial setback, I was able to start writing tests with only a  vague understanding of the problem. As my&lt;br /&gt;
tests exposed where my understanding of the problem was flawed, my code evolved, and within a week I had arrived  at a&lt;br /&gt;
working solution that exhibited all the hallmarks of good testing and software design.&lt;br /&gt;
&lt;br /&gt;
This talk recounts the process I went through from starting with practically nothing, to arriving at a working solution.&lt;br /&gt;
You can follow the rules of  test-driven development, but you can write tests in an expressive way to describe the&lt;br /&gt;
problem instead of just describing what the code should do. It was also essential to begin testing from an integration&lt;br /&gt;
viewpoint as opposed to a unit one, because at the outset the units were unknown and were later realized through further&lt;br /&gt;
development. For the presentation, I will be demonstrating using RSpec and Ruby. All the code examples will be related&lt;br /&gt;
to the Hydra software stack; however, I hope to show  that the processes at work will be applicable in any context.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Designing and Leading a Kick A** Tech Team ==&lt;br /&gt;
 &lt;br /&gt;
* Sibyl Schaefer,  sschaefer@rockarch.org, Rockefeller Archive Center&lt;br /&gt;
&lt;br /&gt;
New managers are often promoted without receiving management training, yet management is not something you just figure out. The experience of being expected to know how to manage, yet not being trained to do so often results in new managers feeling isolated and unsure how to move from making to managing. In this talk I’ll focus on my own managerial experience of designing and leading an archival tech team in a small independent archives. Topics covered will include hiring, delegating, creating a team culture, and leading people whose specialized knowledge exceeds your own. The talk take-aways should be applicable to managers and employees at large and small institutions alike.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==American (Archives) Horror Story: LTO Failure and Data Loss ==&lt;br /&gt;
 &lt;br /&gt;
* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH&lt;br /&gt;
* Casey Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH&lt;br /&gt;
&lt;br /&gt;
Here’s a story to send shivers down archival spines: when transferring video files off LTO for the American Archive project, WGBH got an initial failure rate of 57%.   After repeat tries, the rates improved; still, an unnervingly large percentage of files were never able to be transferred successfully.   Even more unnerving, going public with our horror story got a big response from other archives using LTO -- it seems like many institutions are having similarly scary results.   What are the real risks with LTO tape?  Are there steps that archives should be taking to better circumvent those risks?  This presentation will share information about LTO storage failures across archives world and discuss the process of investigating the problem at WGBH by testing different methods of data retrieval from LTO (direct and networked downloads, individual file retrieval and bulk data dump, use of LTO 4 and LTO 6 decks) and using checksum comparisons and file analysis and characterization tools such as ffprobe, mediainfo and exiftool to analyze failed files.  We'll also present whatever results we’ve managed to turn up by the time of Code4Lib!&lt;br /&gt;
&lt;br /&gt;
== PBCore in Action: Three Words, Not Two! ==&lt;br /&gt;
 &lt;br /&gt;
* Casey E. Davis,  casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH&lt;br /&gt;
* Andrew (Drew) Myers, andrew_myers@wgbh.org, Supervising Developer, WGBH&lt;br /&gt;
&lt;br /&gt;
In 2001, public media representatives developed the PBCore XML schema to establish a common language for managing metadata about their analog and digital audio and video. Since then, PBCore has been adopted by a number of organizations and archivists in the moving image archival community. The schema has also undergone a few revisions, but on more than one occasion it was left orphaned and with little to no support.&lt;br /&gt;
 &lt;br /&gt;
Times have changed. You may have heard the news that PBCore is back in action as part of the American Archive of Public Broadcasting initiative and via the Association of Moving Image Archivists (AMIA) PBCore Advisory Subcommittee. A group of archivists, public media stakeholders, and engaged users have come together to provide necessary support for the standard and to see to its further development. &lt;br /&gt;
 &lt;br /&gt;
At this session, we'll discuss the scope and uses of PBCore in digital preservation and access, report on the progress and goals of the PBCore Advisory Subcommittee, and share how the group (by the time of the conference) will have transformed the XML schema into an RDF ontology, bringing PBCore into the second decade of the 21st century. #PBHardcore&lt;br /&gt;
&lt;br /&gt;
==Collaborating to Avert the Digital Graveyard==&lt;br /&gt;
&lt;br /&gt;
* Harish Nayak, hnayak@library.rochester.edu, University of Rochester Libraries &lt;br /&gt;
* Sean Morris, smorris@library.rochester.edu, University of Rochester Libraries &lt;br /&gt;
&lt;br /&gt;
In 1995, the Robbins Library at the University of Rochester created a digital collection of Arthurian texts, images, and bibliographies. Together with medieval scholars, we recently completed the redesign and development of an interface for this collection. Using FRBR concepts, we re-conceptualized organization and editing workflow from the ground up in a mobile-first Drupal-based project. &lt;br /&gt;
&lt;br /&gt;
In this talk we will describe the project as well as how we utilized the techniques of work practice study and user centered design to maintain engagement with reluctant stakeholders, nontechnical scholars, and VERY meticulous graduate students.  Neither of us have previously presented at a Code4Lib conference.&lt;br /&gt;
&lt;br /&gt;
==Docker? VMs? EC2? Yes! With Packer.io==&lt;br /&gt;
&lt;br /&gt;
* Kevin S. Clarke, ksclarke@gmail.com, Digital Library Programmer, UCLA&lt;br /&gt;
&lt;br /&gt;
There are a lot of exciting ways to deploy a software stack nowadays. Many of our library systems are fully virtualized. Docker is a compelling alternative, and there are also cloud options like Amazon's EC2. This talk will introduce Packer.io, a tool for creating identical machine images for multiple platforms (e.g., Docker, VMWare, VirtualBox, EC2, GCE, OpenStack, et al.) all from a single source configuration.  It works well with Ansible, Chef, Puppet, Salt, and plain old Bash scripts. And, it's designed to be scriptable so that builds can be automated. This presentation will show how easy it is to use Packer.io to bring up a set of related services like Fedora 4, Grinder (for stress testing), and Graphite (for charting metrics). As an added value, all the buzzwords in this proposal will be defined and explained!&lt;br /&gt;
&lt;br /&gt;
== Technology on your Wrist: Cross-platform Smartwatch Development for Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:sanderson|Steven Carl Anderson]], sanderson@bpl.org, Boston Public Library (no previously accepted prepared talks but have done lightning talks in the past)&lt;br /&gt;
&lt;br /&gt;
I'll be the first to admit: smartwatches are unlikely to completely revolutionize how a library provides online services. But I believe they still represent an opportunity to further enhance existing library services and resources in a unique way.&lt;br /&gt;
&lt;br /&gt;
At the Boston Public Library (BPL), we're in the initial phases of designing a modest smartwatch app to provide notifications for circulation availability and checked-out-material due-date alerts by the end of current year. We're starting small, but we plan to evolve the concept over time as we see what (if any) traction such an application gets with potential users. For example, we plan to explore the possibility of adding &amp;quot;nearest branch to my current location&amp;quot; functionality to this app.&lt;br /&gt;
&lt;br /&gt;
Despite the &amp;quot;development phase&amp;quot; of this application as of this writing, this talk is not being given by a novice. As a technology enthusiast, I've released [http://www.phdgaming.com/smartwatch_projects/ five smartwatch applications] and have had two of those be finalists in a [http://www.phdgaming.com/samsung_challenge/ Samsung sponsored development challenge]. This experience not only will allow for the BPL to avoid many beginner mistakes in its smartwatch app development but also gives a much more complete understanding of the smartwatch development ecosystem.&lt;br /&gt;
&lt;br /&gt;
This talk will explore the following questions:&lt;br /&gt;
&lt;br /&gt;
* What kinds of online library services could potentially be transformed or translated into the smartwatch/wearable domain? What kinds of services are better left alone? These questions are currently being explored and I'll talk about our plans and experiences. Included will be any statistical information from our application launch along with statistics from my personal development.&lt;br /&gt;
&lt;br /&gt;
* How to support all the different operating systems these devices run without painful modifications to your codebase. (There's Tizen that is used by Samsung's Gear 2 and Gear S, Android Wear that is used by most other non-Apple manufacturers, then there is Apple's upcoming smartwatch itself, etc.)&lt;br /&gt;
&lt;br /&gt;
* How to support different screen resolutions on such a small device. From round to rectangular to perfectly square, smartwatches come in all different shapes these days.&lt;br /&gt;
&lt;br /&gt;
* What are the app stores like on these platforms? As I support multiple applications through different distribution networks, a guide to navigating how to distribute one's app is included and I'll reveal how these systems work “behind the curtain.”&lt;br /&gt;
&lt;br /&gt;
* What are common issues and pitfalls to avoid when doing development? Tips on broken APIs and how to cope or optimizing your code will be included.&lt;br /&gt;
&lt;br /&gt;
==Seeing the Forest From the Trees: The Art of Creating Workflows for Digital Projects ==&lt;br /&gt;
 &lt;br /&gt;
* Jen LaBarbera, j.labarbera@neu.edu, NDSR Resident, Northeastern University&lt;br /&gt;
* Joey Heinen, joseph_heinen@harvard.edu, NDSR Resident, Harvard University&lt;br /&gt;
* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH&lt;br /&gt;
* Tricia Patterson, triciap@mit.edu, NDSR Resident, MIT&lt;br /&gt;
&lt;br /&gt;
We have to &amp;quot;turn projects into programs&amp;quot; in order to create a solid and sustainable digital preservation initiative...but what the heck does that even mean? What does that look like?&lt;br /&gt;
&lt;br /&gt;
In this talk, members of the inaugural Boston cohort of the National Digital Stewardship Residency will discuss one piece of our digital preservation test kitchen: our stabs at creating digital workflows that will (hopefully) help our institutions turn digital preservation projects into programs. Specifically, we will talk about how difficult it is to create a general and overarching workflow for digital preservation tasks (e.g. ingest into repositories, format migrations, etc.) that incorporates various technical tools while also taking into account the myriad and unending list of possible exceptions or special scenarios. Turning these complicated, specific processes into a simplified and generalized workflow is an art. We haven't necessarily perfected that art yet, but in this talk, we'll share what has worked for us -- and what hasn't. We’ll also touch on the importance of documentation, and achieving that delicate balance of adequately thorough documentation that doesn’t pose the risk of information avalanche. These processes often create more questions than answers, but we'll share the answers that we (and our mentors) have found along the way!&lt;br /&gt;
&lt;br /&gt;
== Annotations as Linked Data with Fedora4 and Triannon (a Real Use Case for RDF!) ==&lt;br /&gt;
&lt;br /&gt;
* Rob Sanderson, azaroth@stanford.edu,  Stanford University Libraries&lt;br /&gt;
* Naomi Dushay, ndushay@stanford.edu,  Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
Annotations on content resources allow users to contribute knowledge within the digital repository space.  W3C Open Annotation provides a comprehensive model for web annotation on all types of content, using Linked Data as a fundamental framework.  Annotation clients generate instances of this model, typically using a JSON serialization, but need to store that data somewhere using a standard interaction pattern so that best of breed clients, servers, and data can be mixed and matched.&lt;br /&gt;
&lt;br /&gt;
Stanford is using Fedora4 for managing Open Annotations, via a middleware component called Triannon.  Triannon receives the JSON data from the annotation client, and uses the Linked Data Platform API implementation in Fedora4 to create, retrieve, update and delete the constituent resources.  Triannon could be easily modified to use other LDP implementations, or could be modified to work with linked data other than annotations.&lt;br /&gt;
&lt;br /&gt;
== Helping Google (and scholars, researchers, educators, &amp;amp; the public) find archival audio ==&lt;br /&gt;
&lt;br /&gt;
* Anne Wootton, anne@popuparchive.org, Pop Up Archive (www.popuparchive.org)&lt;br /&gt;
&lt;br /&gt;
Culturally significant digital audio collections are hard to discover on the web. There are major barriers keeping this valuable media from scholars, researchers, and the general public:&lt;br /&gt;
&lt;br /&gt;
Audio is opaque: you can’t picture sound, or skim the words in a recording. &lt;br /&gt;
Audio is hard to share: there’s no text to interact with. &lt;br /&gt;
Audio is not text: but since text is the medium of the web, there’s no path for audiences to find content-rich audio.&lt;br /&gt;
Audio metadata is inconsistent and incomplete.&lt;br /&gt;
&lt;br /&gt;
At Pop Up Archive, we're helping solve this problem making the spoken word searchable. We began as a UC-Berkeley School of Information Master's thesis to provide better access to recorded sound for audio producers, journalists, and historians. Today, Pop Up Archive processes thousands of hours of sound from all over the web to create automatic, timestamped transcripts and keywords, working with media companies and institutions like NPR, KQED, HuffPost Live, Princeton, and Stanford. We're building collections of sound from journalists, media organizations, and oral history archives from around the world. Pop Up Archive is supported by the John S. and James L. Knight Foundation, the National Endowment for the Humanities, and 500 Startups.&lt;br /&gt;
&lt;br /&gt;
== Digital Content Integrated with ILS Data for User Discovery:  Lessons Learned ==&lt;br /&gt;
&lt;br /&gt;
* Naomi Dushay, ndushay@stanford.edu,  Stanford University Libraries&lt;br /&gt;
* Laney McGlohon, laneymcg@stanford.edu,  Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
So you want to expose your digital content in your discovery interface, integrated with the data from your ILS?  How do you make the best information user searchable?  How do you present complete, up to date search results with a minimum of duplicate entries?&lt;br /&gt;
&lt;br /&gt;
At Stanford, we have these cases and more:&lt;br /&gt;
* digital content with no metadata in ILS&lt;br /&gt;
* digital content for metadata in ILS&lt;br /&gt;
* digital content with its own metadata derived from ILS metadata.&lt;br /&gt;
&lt;br /&gt;
We will describe our efforts to accommodate multiple updatable metadata sources for materials in the ILS and our Digital Object Repository while presenting users with reduced duplication in SearchWorks.  Included will be some failures, some successes, and an honest assessment of where we are now.&lt;br /&gt;
&lt;br /&gt;
== Show All the Things: Kanban for Libraries == &lt;br /&gt;
&lt;br /&gt;
* Mike Hagedon, mhagedon@email.arizona.edu, University of Arizona Libraries&lt;br /&gt;
&lt;br /&gt;
The web developers at the University of Arizona Libraries had a problem: we were working on a major website rebuild project with no clear way to prioritize it against our other work. We knew we wanted to follow Agile principles and initially chose Scrum to organize and communicate about our work. But we found that certain core pieces of Scrum did not work for our team. Then we discovered Kanban, an Agile meta-process for organizing work (team or individual) that treats the work more as a flow than as a series of fixed time boxes. I’ll be talking about our journey toward finding a process that works for our team and how we’ve applied the principles of Kanban to better get our work done. Specifically, we talk about principles like how to visualize all your work, how to limit how much you’re doing (to get more done!), and how to optimize the flow of your work.&lt;/div&gt;</summary>
		<author><name>Afred</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&amp;diff=41993</id>
		<title>2015 Prepared Talk Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&amp;diff=41993"/>
				<updated>2014-11-07T19:59:36Z</updated>
		
		<summary type="html">&lt;p&gt;Afred: /* PBCore in Action: Three Words, Not Two! */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Code4lib 2015 is a loosely-structured conference that provides people working at the intersection of libraries/archives/museums/cultural heritage and technology with a chance to share ideas, be inspired, and forge collaborations. For more information about the Code4lib community, please visit http://code4lib.org/about/. &lt;br /&gt;
The conference will be held at the Portland Hilton &amp;amp; Executive Tower in Portland, Oregon, from February 9-12, 2015.&lt;br /&gt;
&lt;br /&gt;
'''Proposals for Prepared Talks:'''&lt;br /&gt;
&lt;br /&gt;
We encourage everyone to propose a talk.&lt;br /&gt;
 &lt;br /&gt;
Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:&lt;br /&gt;
* Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software&lt;br /&gt;
* Tools and technologies – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)&lt;br /&gt;
* Technical issues - Big issues in library technology that should be addressed or better understood&lt;br /&gt;
* Relevant non-technical issues – Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc.&lt;br /&gt;
&lt;br /&gt;
Proposals can be submitted through Friday, November 7, 2014 at 5pm PST (GMT−8). Voting will start on November 11, 2014 and continue through November 25, 2014. The URL to submit votes will be announced on the Code4Lib website and mailing list and will require an active code4lib.org account to participate. The final list of presentations will be announced in early- to mid-December.&lt;br /&gt;
&lt;br /&gt;
'''Proposals for Prepared Talks:'''&lt;br /&gt;
&lt;br /&gt;
Log in to the Code4lib wiki and edit this wiki page using the prescribed format. If you are not already registered, follow the instructions to do so.&lt;br /&gt;
Provide a title and brief (500 words or fewer) description of your proposed talk.&lt;br /&gt;
If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist voters in opening the conference to new presenters.&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Talk Title: ==&lt;br /&gt;
 &lt;br /&gt;
* Speaker's name,  email address, and (optional) affiliation&lt;br /&gt;
* Second speaker's name, email address, and affiliation, if second speaker&lt;br /&gt;
&lt;br /&gt;
Abstract of no more than 500 words.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Talk Proposals'''&lt;br /&gt;
== Zines + Gamification = Awesomest Metadata Literacy Outreach Event Ever! ==&lt;br /&gt;
 &lt;br /&gt;
* [http://www.JenniferHecker.info Jennifer Hecker], jenniferraehecker@gmail.com, [http://www.lib.utexas.edu/subject/zines University of Texas Libraries] &amp;amp; [http://www.AustinFanzineProject.org Austin Fanzine Project]&lt;br /&gt;
* [http://anomalily.net/ Lillian Karabaic], librarian@iprc.org, [http://www.iprc.org/ Independent Publishing Resource Center] (Portland)&lt;br /&gt;
 &lt;br /&gt;
In academic libraries, and elsewhere, the popularity of zine (a magazine produced for love, not profit) collections is on the rise. At the same time, metadata literacy is becoming an increasingly important skill, helping people navigate and understand digital environments and interactions. We have found a way to teach metadata literacy to the general public that isn’t super-boring – in fact, we’ve made it downright fun!&lt;br /&gt;
&lt;br /&gt;
First, volunteer zine librarian Lillian Karabaic of Portland’s Independent Publishing Resource Center facilitated the creation of a gamified cataloging interface for the IPRC’s annual Raiders of the Lost Archives backlog-busting 24-hour volunteer cataloging event.&lt;br /&gt;
&lt;br /&gt;
Then, archivist Jennifer Hecker facilitated the adaptation of the IPRC’s game for use in a similar, but also very different context – promoting UT Libraries newly-acquired zine collections. The main goal of the academic-library-based event was increasing excitement around the collections, but with the side goal of building metadata literacy, and introducing an understanding of library cataloging issues.&lt;br /&gt;
&lt;br /&gt;
The Texas modification also conforms to the xZINECOREx metadata schema developed by the national [http://zinelibraries.info/ Zine Librarians Interest Group], and triggered interesting conversations with the Libraries’s cataloging department about evolving metadata standards and how to incorporate the products of crowd-sourcing projects into existing workflows.&lt;br /&gt;
&lt;br /&gt;
Both games will be demoed.&lt;br /&gt;
&lt;br /&gt;
We have never presented at Code4lib.&lt;br /&gt;
&lt;br /&gt;
== Do the Semantic FRBRoo ==&lt;br /&gt;
* Rosie Le Faive, rlefaive@upei.ca, University of Prince Edward Island&lt;br /&gt;
&lt;br /&gt;
[http://www.islandora.ca Islandora] is great for creating repositories of any data type, but how can you model meaningful relationships between digital objects and use them to tell a story?&lt;br /&gt;
&lt;br /&gt;
At UPEI, I’m assembling an ethnography of Prince Edward Island’s traditional fiddle music that includes musical clips, video clips, oral histories, musical notation, images, and ethnographic commentaries. In order to present an exhibition-style site, I’m tying these digital objects together via the people, places, events, tunes and topics that they share or describe. &lt;br /&gt;
&lt;br /&gt;
To describe the relationships, I’m extending Islandora to use [http://www.cidoc-crm.org/frbr_inro.html FRBRoo], a vocabulary that combines the FRBR model with CIDOC-CRM, the the object-oriented museum documentation ontology. These modules being developed will allow other researchers to create a structured, navigable digital repository of diverse object types, that uses Islandora as an exhibition platform. &lt;br /&gt;
&lt;br /&gt;
== Our $50,000 Problem: Why Library School? ==&lt;br /&gt;
* Jennie Rose Halperin, jhalperin@mozilla.com, Mozilla Corporation&lt;br /&gt;
&lt;br /&gt;
57 library schools in the United States are churning out approximately 100 graduates per year, many with debt upwards of $50,000.  According to ONet, [http://www.inthelibrarywiththeleadpipe.org/2011/is-the-united-states-training-too-many-librarians-or-too-few-part-1/ 84% of library jobs in the US require an MLS.] The library profession is [http://dpeaflcio.org/programs-publications/issue-fact-sheets/library-workers-facts-figures/) 92% white and 82% female and entry-level librarians can expect to make $32,500 per year.]&lt;br /&gt;
&lt;br /&gt;
Contrasted with developers, who are almost [http://www.ncwit.org/blog/did-you-know-demographics-technical-women 90% male] and can expect to make [http://www.forbes.com/sites/jennagoudreau/2011/06/01/best-entry-level-jobs/ $70,000 in an entry-level position,] these numbers are dismal.&lt;br /&gt;
&lt;br /&gt;
According to a recent survey, the top skill that outgoing library students want to know is “programming” and yet many MLS programs still consider Microsoft Word an essential technology skill.&lt;br /&gt;
&lt;br /&gt;
What is going on here? Why do we accept this fate, where mostly female debt-burdened professionals continue to be thrown onto the work force without the education their expensive degrees promised?&lt;br /&gt;
&lt;br /&gt;
As a community we need to come together to stop this cycle. We need to provide better support and mentorship to diversify and keep the profession relevant and help librarianship move into the future it deserves.&lt;br /&gt;
&lt;br /&gt;
This talk will walk through the challenges of navigating a hostile employment environment as well as present models for better development and future state imagining.&lt;br /&gt;
&lt;br /&gt;
== No cataloging software? Need more than Dublin Core? No problem!: Experiences with CollectiveAccess ==&lt;br /&gt;
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University&lt;br /&gt;
* Rachel Wittmann, rwittma@clemson.edu, Clemson University&lt;br /&gt;
&lt;br /&gt;
Clemson University Libraries has implemented the open-source software CollectiveAccess for customized digital collection needs. CollectiveAccess is an open-source project with the goal of providing a flexible way to manage and publish museum and archival collections. There are several applications associated with the projects; most used are: Providence (for cataloging and entering metadata) and Pawtucket (for displaying objects in a collection for the public). It has many profiles readily available for installing with existing library standards, such as Dublin Core, and there is a robust syntax for creating your own profiles to fit custom tailored metadata schemas. Plus, the user interface allows you to modify the metadata profile quickly and easily.&lt;br /&gt;
&lt;br /&gt;
In this talk, we will discuss:&lt;br /&gt;
* Our experiences with installing Providence and creating an installation profile that satisfies the needs of many of the Clemson Libraries digital archiving processes. &lt;br /&gt;
* The stumbling blocks experienced in that process and how they were resolved.&lt;br /&gt;
* The available plugins sourcing widely used authorities, such as Library of Congress thesauri and GeoNames.org, and how they have been used by our projects. &lt;br /&gt;
* A brief overview of the export and import functions and also current workflow practices within Providence.&lt;br /&gt;
* Future plans &amp;amp; the role of CollectiveAccess at Clemson University Libraries&lt;br /&gt;
&lt;br /&gt;
== Getting ContentDM and Wordpress to Play Together ==&lt;br /&gt;
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University&lt;br /&gt;
&lt;br /&gt;
Clemson University Libraries has a very strong program for digitizing and archiving photographs, and the Digital Imaging team processes many hundreds of photographs every month. These images are managed using different methods, including ContentDM, a digital collection manager.&lt;br /&gt;
&lt;br /&gt;
ContentDM provides various methods for searching and displaying photographs, along with their metadata. However, recent initiatives have resulted in the need to leverage those collections into exhibits displayed on other library-related websites, such as our Special Collections unit. The Clemson Libraries has invested heavily in Wordpress as our content management system of choice, and it seemed most efficient not to have to export and import images into our Wordpress sites in order to provide exhibited images.&lt;br /&gt;
&lt;br /&gt;
Fortunately, ContentDM has provided an API to many of their functions, allowing the extraction of metadata and even rescaled images through URLs. This project has been developing a plugin for Wordpress that integrates with ContentDM through shortcodes that Wordpress editors can easily include in their content. These shortcodes allow editors to choose how many images, which images from which collections, thumbnail sizes, etc. to display in different gallery styles. Plans are for it to allow integration with different plugins such as Fancybox and Masonry.&lt;br /&gt;
&lt;br /&gt;
In this presentation, I will demonstrate the current state of the plugin and discuss future plans. &lt;br /&gt;
&lt;br /&gt;
==Refinery — An open source locally deployable web platform for the analysis of large document collections==&lt;br /&gt;
 &lt;br /&gt;
* [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com&lt;br /&gt;
&lt;br /&gt;
Refinery is an open source web platform for the analysis of large unstructured document collections. It extracts meaningful semantic themes within documents also known as &amp;quot;topics&amp;quot; which can be thought of as word clouds composed of terms that highly co-occur with one another. Once this semantic index is formed, one can extract relevant documents related to these topics and further refine their contents through a summarization process that allows users to search for phrases that are relevant to them within the corpus. The goal of Refinery is to make this whole process easier and to provide some of the latest scalable versions of these learning algorithms in an intuitive web-based interface. Refinery is also meant to be run locally, thus bypassing the need for securing document collections over the internet. The talk will go through some of the technologies involved and a demo of the app.&lt;br /&gt;
&lt;br /&gt;
For more info check out http://www.docrefinery.org.&lt;br /&gt;
&lt;br /&gt;
==Drupal 8 — Evolution &amp;amp; Revolution==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Drupal 8 is in beta and nearing release. Among its many features, it notably has become more developer friendly through its adoption of the Symfony PHP framework along with Symfony's outstanding set of libraries (like Guzzle) and tools (like Composer). And, in implementing the Twig theming system, it is can begin to escape PHPtemplate. These moves also make it easier to create headless systems that uses Angular.js and other systems for presentation, or even forgo presentation entirely.&lt;br /&gt;
&lt;br /&gt;
From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.&lt;br /&gt;
&lt;br /&gt;
==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==&lt;br /&gt;
 &lt;br /&gt;
* [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]],  stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]&lt;br /&gt;
&lt;br /&gt;
GameSalad is a popular tool for developing mobile and desktop games with little actual programming. In this presentation, Stan Bogdanov breaks down the development process he followed while building [https://github.com/stanrb/mobiLit mobiLit], a mobile app with the goal of being the first open-source gamified information literacy app to be used as part of a college-level information literacy curriculum. He will go through the basics of using GameSalad to create an app that can be easily customized by non-programmers and the instructional principles used to teach the material in a mobile medium. Stan will also go through two qualitative design studies he did on the app and discuss their results and the lessons learned from building mobiLit. The session will conclude with an overview of the next steps for the [https://github.com/stanrb/mobiLit mobiLit project].&lt;br /&gt;
&lt;br /&gt;
==The Impossible Search: Pulling data from multiple unknown sources==&lt;br /&gt;
 &lt;br /&gt;
* Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com &lt;br /&gt;
&lt;br /&gt;
It's easy to search data you know the structure of, but what if you need to pull in data from sources that don't have a standard structure. The ability to search community events along with your standard catalog search results is an example, but often the only way to pull these events is through XML, JSON, (Insert structured format here), or even just raw html. But how do you get that structure? That simple question is what makes this impossible. The process to define and process this structure takes a lot of manual labor, especially if the data you are pulling is just HTML, and then every time you add data to the index you have to run all the data through a script to pull in data in a format Solr or an other index can use. This talk will focus on Solr, but the principles explained will apply to many other indexes.&lt;br /&gt;
&lt;br /&gt;
==What! You're Not Using Docker?==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Boring part: Docker[1] is a container system that provides benefits similar to virtualization with only a fraction of the overhead. Scintillating part: Docker can host between four to six times the number of service instances than systems such as Xen or VMWare on a given piece of hardware. But thats not all! Docker also makes it simple(r) to create transportable instances, so you can spin up development servers on your laptop.&lt;br /&gt;
&lt;br /&gt;
*[1]https://www.docker.com/&lt;br /&gt;
&lt;br /&gt;
== Video Accessibility, WebVTT, and Timed Text Track Tricks ==&lt;br /&gt;
&lt;br /&gt;
* Jason Ronallo, jronallo@gmail.com, NCSU Libraries&lt;br /&gt;
&lt;br /&gt;
Video on the Web presents new challenges and opportunities. How do you make your video more accessible to those with various disabilities and needs? I'll show you how. This presentation will focus on how to write and deliver captions, subtitles, audio descriptions, and timed metadata tracks for Web video using the WebVTT W3C standard. Encoding timed text tracks in this way opens up opportunities for new functionality on your websites beyond accessibility. The presentation will show some examples of the potential for using timed text tracks in creative ways. I'll cover all the HTML and JavaScript you will need to know as well as some of the CSS and other bits you could probably do without but are too fun to pass up.&lt;br /&gt;
&lt;br /&gt;
== Categorizing Records with Random Forests ==&lt;br /&gt;
 &lt;br /&gt;
* Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library&lt;br /&gt;
Academic libraries are increasingly responsible for providing ingest, search, discovery, and analysis for data sets.  Emerging techniques from data science and machine learning can provide librarians and developers with an opportunity to generate new insights and services from these document collections.  This presentation will provide a brief overview of common machine learning classification techniques, then dive into a more detailed example using a random forest to assign keywords to research data sets.  The talk will emphasize the insight that can be gained from machine learning rather than the inner workings of the algorithms.  The overall goal of this presentation is to provide librarians and developers with the context to recognize an opportunity to apply machine learning categorization techniques at their home campuses and organizations.  &lt;br /&gt;
&lt;br /&gt;
== Data Science in Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Devon Smith, smithde@oclc.org, OCLC&lt;br /&gt;
&lt;br /&gt;
Data Science is increasing in buzz and hype. I'll go over what it is, what it isn't, and how it fits in libraries.&lt;br /&gt;
&lt;br /&gt;
== PDF metadata extraction for academic literature == &lt;br /&gt;
&lt;br /&gt;
* Kevin Savage, kevin.savage at mendeley.com, Mendeley&lt;br /&gt;
* Joyce Stack, joyce.stack at mendeley.com, Mendeley&lt;br /&gt;
&lt;br /&gt;
Mendeley recently added a, &amp;quot;document from file,&amp;quot; endpoint to its API which attempts to extract metadata such as title and authors directly from PDF files. This talk will describe at a high level the machine learning methods we used including how we measured and tuned our model. We will then delve more deeply into our stack, the tools we used, some of the things that didn't work and why PDFs are the worst thing ever to compute over.&lt;br /&gt;
&lt;br /&gt;
== Giving Users What They Want: Record Grouping in VuFind ==&lt;br /&gt;
 &lt;br /&gt;
* Mark Noble,  mark@marmot.org, [//www.marmot.org Marmot Library Network]&lt;br /&gt;
&lt;br /&gt;
In 2013, Marmot did extensive usability studies with patrons to determine what was difficult in the catalog.  Many patrons had problems sifting through all of the various formats and editions of a title.  In 2014 we developed a method for [//mercury.marmot.org/Union/Search?lookfor=divergent grouping records] so only a single work is shown in search results and all formats and editions are listed under that work.  We will discuss our definition of a 'work' based on FRBR principles; combining meta data from MARC records with metadata from other sources like OverDrive; the technical details of Record Grouping; the design decisions made during implementation; and the reaction from users and staff.&lt;br /&gt;
&lt;br /&gt;
== Topic Space: a mobile augmented reality recommendation app ==&lt;br /&gt;
&lt;br /&gt;
* Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign&lt;br /&gt;
&lt;br /&gt;
The Topic Space module (http://minrvaproject.org/modules_topicspace.php ) was developed with an IMLS Sparks! Grant to investigate augmented reality technologies for in-library recommendations. The funding allowed for sustained university community collaboration by the University Library, the Graduate School of Library and Information Science, as well as graduate student programmers sourced from the Department of Computer Science. Collaborators designed app functionality and identified relevant open source libraries that could power optical character recognition (OCR) functionality from within the mobile phone.&lt;br /&gt;
&lt;br /&gt;
Topic space allows a user to take a picture of an item's call number in the book stacks. The module will show the user other books that are relevant but that are not shelved nearby. It can also show users books that are normally shelved here but that are currently checked out. Recommendations are based on Library of Congress subject headings and ILS circulation data which indicate recommendation candidates based on total check-outs. &lt;br /&gt;
&lt;br /&gt;
Research questions included development of back end (server-side) pattern matching algorithms for recommendations, and a rapid formative evaluation of interface design that would provide optimal user experience for navigation of the book stacks as a context to recommendations.&lt;br /&gt;
&lt;br /&gt;
Along with the Topic Space native app, grant collaborators prototyped web based recommendations which could serve as a new way of providing readers advisory and “more like this” recommendations from discovery interfaces accessed through desktop browsers. Outcomes of the grant include the availability of the [https://play.google.com/store/apps/details?id=edu.illinois.ugl.minrva Topic Spaces module within Minrva app on the Android Play store] and an experimental [http://backbonejs.org/ Backbone.js] based [http://minrva-dev.library.illinois.edu Topic Space web app].&lt;br /&gt;
&lt;br /&gt;
== Leveling Up Your Git Workflow ==&lt;br /&gt;
&lt;br /&gt;
* Megan Kudzia, moneill@albion.edu, Albion College Library&lt;br /&gt;
* Kate Sears, eks11@albion.edu, Albion College Library&lt;br /&gt;
&lt;br /&gt;
Have you started experimenting with Git on your own, but now you need to include others in your projects? Learn from our mistakes! Transitioning from a one-person git workflow and repo structure, to a structure that includes multiple people (including student workers), is not for the faint of heart. We'll talk about why we decided to work this way, our path to developing a git culture amongst ourselves, conceptual and technical difficulties we've faced, what we learned, and where we are now. Also with pretty pictures (aka workflow drawings).&lt;br /&gt;
&lt;br /&gt;
== Drone Loaning Program: Because Laptops are so last century ==&lt;br /&gt;
&lt;br /&gt;
 * Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries&lt;br /&gt;
 * Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries&lt;br /&gt;
&lt;br /&gt;
At Univ. Maryland we are in the very early stages of looking into allowing our student body get their hands on a drone. Yes that's right we will let students take out a drone for n amount of hours to work on projects of their choosing. The talk will talk about the logistics of getting a program of this sort from concept to &amp;quot;Is the drone available?&amp;quot;. If people sign waivers we will also promise not to crash the drone into code4lib attendees.&lt;br /&gt;
&lt;br /&gt;
== Got Git? Getting More Out of Your GitHub Repositories ==&lt;br /&gt;
&lt;br /&gt;
 * Terry Brady, twb27@georgetown.edu, Georgetown University Library&lt;br /&gt;
&lt;br /&gt;
This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories. &lt;br /&gt;
&lt;br /&gt;
In additional to all of the great benefits of using Git for code management, the GitHub interface provides a powerful set of tools to showcase a project and to keep your users informed of developments to your project.  These tools can assist with marketing and outreach - turning your code repository into a focus of conversation!&lt;br /&gt;
&lt;br /&gt;
* [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]&lt;br /&gt;
* [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]&lt;br /&gt;
* [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]&lt;br /&gt;
* [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]&lt;br /&gt;
* Gists for code sharing&lt;br /&gt;
* Private Repositories and Organizational Groups&lt;br /&gt;
* Pull Request Conversation Tracking&lt;br /&gt;
* Customized Issue management&lt;br /&gt;
&lt;br /&gt;
== Quick Wins for Every Department in the Library - File Analyzer! ==&lt;br /&gt;
&lt;br /&gt;
 * Terry Brady, twb27@georgetown.edu, Georgetown University Library&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.&lt;br /&gt;
* Analyzing Marc Records for the Cataloging department&lt;br /&gt;
* Transferring ILS invoices for the University Account System for the Acquisitions department &lt;br /&gt;
* Delivering patron fines to the Bursar’s office for the Access Service department&lt;br /&gt;
* Summarizing student worker timesheet data for the Finance department&lt;br /&gt;
* Validating COUNTER compliant reports for the Electronic Resources department&lt;br /&gt;
* Generating ingest packages for the Digital Services department&lt;br /&gt;
* Validating checksums for the Preservation department&lt;br /&gt;
&lt;br /&gt;
Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!&lt;br /&gt;
&lt;br /&gt;
==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor&lt;br /&gt;
&lt;br /&gt;
The transition from paper maps to digital ones changed much more than the maps themselves; it changed the very foundation of how we work and how we find each other. Now maps are transforming again.  The Geospatial World is moving from GIS systems that are institutionally-focused, expensive, feature-burdened, and binds data into a complicated and demanding user-hostile interface. From this transition from digital to web-based digital geospatial tools has come growth and development in new forms of map-based investigative journalism, activism, scholarship, and business ventures. This talk will highlight the conditions and strategies that made these changes possible as a means to draw a path by which librarians through our own work may follow, dragons notwithstanding. &lt;br /&gt;
&lt;br /&gt;
== Building Your Own Federated Search ==&lt;br /&gt;
&lt;br /&gt;
* Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco&lt;br /&gt;
&lt;br /&gt;
Advances in modern browsers have created some interesting possibilities for federated search. This presentation will cover common techniques and pitfalls in building a federated search. We will discuss what principles guided our decisions when implementing our own federated search. We will show tools we've built and our findings from building and using experimental prototypes.&lt;br /&gt;
&lt;br /&gt;
Your higher education institution likely offers dozens of online resources for educators, students, researchers, and the public. And each of these online resources likely has its own search tool. But users can't be expected to search in dozens of different interfaces to find what they're looking for. A typical solution for this issue is federated search. &lt;br /&gt;
&lt;br /&gt;
==  Indexing Linked Data with LDPath ==&lt;br /&gt;
&lt;br /&gt;
* Chris Beer, cabeer@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
LDPath [1] is a simple query language for indexing linked open data, with support for caching, content negotiation, and integration with non-RDF endpoints. This talk will demonstrate the features and potential of the language and framework to index a resource with links into id.loc.gov, viaf.org, geonames.org, etc to build an application-ready document.&lt;br /&gt;
&lt;br /&gt;
[1] http://marmotta.apache.org/ldpath/language.html&lt;br /&gt;
&lt;br /&gt;
== Show Me the Money: Integrating an LMS with Payment Providers ==&lt;br /&gt;
 &lt;br /&gt;
* Josh Weisman,  Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group&lt;br /&gt;
&lt;br /&gt;
In order to provide an easy and convenient way for patrons to pay fines, we are exploring ways to integrate the library management system with online payment providers such as PayPal. With many LMS systems being designed and developed for the cloud, we should be able to provide the frictionless user experience our patrons have come to expect from online transactions. In this session we'll discuss strategies for integration and review a sample application which uses REST APIs from a library management system to integrate with PayPal.&lt;br /&gt;
&lt;br /&gt;
== Shibboleth Federated Authentication for Library Applications: ==&lt;br /&gt;
&lt;br /&gt;
* Scott Fisher, scott.fisher@ucop.edu, California Digital Library&lt;br /&gt;
* Ken Weiss, ken.weiss@ucop.edu, California Digital Library&lt;br /&gt;
&lt;br /&gt;
Shibboleth is the most widely-used method to provide single-sign-on authentication to academic applications where users come from many different institutions. Shibboleth, the InCommon education and research trust framework, and the SAML protocol comprise a very powerful - but very complicated - solution to this very complicated problem. Scott and Ken have implemented Shibboleth for multiple library applications. They will share their understanding of the good, the bad, and the underlying spaghetti that makes it all work. Ken will discuss some of the technical aspects of the solution, touching on optimal and non-optimal use cases, administrative challenges, and authorization concerns. Scott will describe the implementation pattern for multi-institution single-sign-on that the California Digital Library has evolved, using the recently released Dash application (http://dash.cdlib.org) as an example.&lt;br /&gt;
&lt;br /&gt;
==Scientific Data: A Needs Assessment Journey==&lt;br /&gt;
 &lt;br /&gt;
*[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History&lt;br /&gt;
&lt;br /&gt;
While surveying digital research and collections data in the research science divisions at the American Museum of Natural History in NYC (as a part of my [http://ndsr.nycdigital.org/ National Digital Stewardship Residency] project), I have come across the big data hogs (genome sequencing and CT scanning) and the little pieces of data (images, publications), all equally important to not only scientific discovery, but as nodes in the history of science. &lt;br /&gt;
&lt;br /&gt;
In this session, I will discuss the development of my needs assessment surveys for scientific datasets and the interview process with Museum curators and researchers as background, seguing into an explanation of the results. I will then combine my findings into preliminary selection criteria to choose tools for digital preservation and management unique to scientific datasets. This will brooke a discussion on emerging standards, tools, and technologies in big data, specific to research science. &lt;br /&gt;
&lt;br /&gt;
I will conclude with preliminary findings on emerging technology that can be used to answer concerns surrounding the management and digital preservation of these data. I am hoping the Q&amp;amp;A session can be used to both answer questions about my project, and function as a way for you (the larger tech-savy library community)  to discuss the tools I’ve touched on in this talk. &lt;br /&gt;
&lt;br /&gt;
== Feminist Human Computer Interaction (HCI) in Library Software ==&lt;br /&gt;
 &lt;br /&gt;
* Bess Sadler,  bess@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
Libraries are not neutral repositories of knowledge. Library classification systems and search technologies tend to reflect the inequalities, biases, ethnocentrism, and power imbalances of the societies in which they are built [1]. How might we better resist these tendencies in the library software we create? This talk will examine some qualities of feminist HCI (pluralism, self-disclosure, participation, ecology, advocacy, and embodiment) [2] through the lens of library software. &lt;br /&gt;
&lt;br /&gt;
[1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.&lt;br /&gt;
&lt;br /&gt;
[2] Bardzell, Shaowen. Feminist HCI: Taking Stock and Outlining an Agenda for Design. CHI 2010: HCI For All. http://dmrussell.net/CHI2010/docs/p1301.pdf&lt;br /&gt;
&lt;br /&gt;
== Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==&lt;br /&gt;
&lt;br /&gt;
* Audrey Altman, audrey at dp.la, Digital Public Library of America&lt;br /&gt;
* Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America&lt;br /&gt;
* Mark Breedlove, mb at dp.la, Digital Public Library of America&lt;br /&gt;
&lt;br /&gt;
The Digital Public Library of America aggregates metadata for over 8 million objects from more than 24 direct partners, or Hubs, using its Metadata Application Profile (MAP), an RDF metadata application profile based on the Europeana Data Model. After working with the initial system for harvesting, mapping and enhancing our Hub’s metadata for a year, we realized that it was inadequate for working with data at this scale. There were architectural issues; it was opaque to non-developer and partner staff; there were inadequate tools for quality assurance and analysis; and the system was unaware that it was working with RDF data. As the network of Hubs expanded and we ingested more metadata, it became harder and harder to know when or why a harvest, a mapping task, or an enrichment went wrong because the tools for quality assurance were largely inadequate. &lt;br /&gt;
&lt;br /&gt;
The DPLA Content and Technology teams decided to develop a new system from the ground up to address those problems. Development of Heidrun, the internal version of the new system, started in October 2014. Heidrun’s goals are to make it easier for us to harvest and map metadata from various sources and in variety of schemas to the DPLA MAP, to better enrich that metadata using external data sources, and to actively involve our partners in the ingestion process through access to better QA tools. Heidrun and its componentry are built on Ruby on Rails, Blacklight, and ActiveTriples. Our presentation will give some background on our design principles and processes used during development, the architecture of the system, and its functionality. We plan to release a version of Heidrun and its components as a generalized metadata aggregation system for use by DPLA Hubs and others working to aggregate cultural heritage metadata.&lt;br /&gt;
&lt;br /&gt;
== OS or GTFO: Program or Perish ==&lt;br /&gt;
*Tessa Fallon, tessa.fallon@gmail.com&lt;br /&gt;
&lt;br /&gt;
Description TBD&lt;br /&gt;
&lt;br /&gt;
== Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==&lt;br /&gt;
* Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries&lt;br /&gt;
Would your library like to have large digital signage that displays dynamic information such as library hours, weather, room availability, and more? Have you looked into purchasing large digital signage, only to be turned off by the high price tag and lack of customization available with commercial solutions? Our library has developed a cheap and effective alternative to these systems using HTML 5 authoring software, a large TV, and freely-available APIs from Google, Springshare, and others. At this session, you’ll learn about the system that we have in place for displaying dynamic and easily-updatable information on our library’s large digital display, and how you can easily create something similar for your library.&lt;br /&gt;
&lt;br /&gt;
== REPOX: Metadata Blender ==&lt;br /&gt;
 &lt;br /&gt;
* John Mignault, jmignault@metro.org, Empire State Digital Network&lt;br /&gt;
&lt;br /&gt;
With the growth in the number of hubs providing metadata to the Digital Public Library of America, many of them are using REPOX, a tool originally created for the Europeana project, to aggregate disparate metadata feeds and transform them into formats suitable for ingest into DPLA. The Empire State Digital Network, the forthcoming DPLA service hub for NY state, is using it to prepare for our first ingest into DPLA in early 2015.  We'll take a look at REPOX and its capabilities and how it can be useful for ingesting and transforming metadata, and also discuss some things we've learned in massaging widely varied metadata feeds.&lt;br /&gt;
&lt;br /&gt;
== Beyond Open Source ==&lt;br /&gt;
&lt;br /&gt;
* Jason Casden, jmcasden@ncsu.edu, NCSU Libraries&lt;br /&gt;
* Bret Davidson, bddavids@ncsu.edu, NCSU Libraries&lt;br /&gt;
&lt;br /&gt;
The Code4Lib community has produced an increasingly impressive collection of open source software over the last decade, but much of this creative work remains out of reach for large portions of the library community. Do the relatively privileged institutions represented by a majority of Code4Lib participants have a professional responsibility to support the adoption of their innovations?&lt;br /&gt;
&lt;br /&gt;
Drawing from old and new software packaging and distribution approaches (from freeware to Docker), we will propose extending the open source software values of collaboration and transparency to include the wide and affordable distribution of software. We believe this will not only simplify the process of sharing our applications within the Code4Lib community, but also make it possible for less well resourced institutions to actually use our software. We will identify areas of need, present our experiences with the users of our own open source projects, discuss our attempts to go beyond open source, and make an argument for the internal value of supporting and encouraging a vibrant library ecosystem.&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]] &lt;br /&gt;
[[Category:Talk Proposals]]&lt;br /&gt;
&lt;br /&gt;
== Making It Work: Problem Solving Using Open Source at a Small Academic Library ==&lt;br /&gt;
 &lt;br /&gt;
* Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology&lt;br /&gt;
* Max King, mking9@iit.edu, Illinois Institute of Technology&lt;br /&gt;
&lt;br /&gt;
The Illinois Institute of Technology campus was added to the National Register of Historic Places in 2005, and contains a building, Mies van der Rohe's S.R. Crown Hall, that was named a National Historic Landmark in 2001. Creating a digital resource that can adequately showcase the campus and its architecture is challenge enough in and of itself, but doing so as a two-person team of relative newcomers, at a university library without dedicated programmers on staff, ups the ante considerably.&lt;br /&gt;
The challenges of technical know-how, staff time, and funding are nothing new to anyone working on digital projects at a university library, and are amplified when doing so at a smaller institution. This talk covers the conception, development, and design of the campus map site that was built, concentrating on the problem-solving strategies developed to cope with limited technical and financial resources.&lt;br /&gt;
We'll talk about our approach to development with Open Source software, including Omeka, along with the Neatline and Simile Timeline plugins. We'll also discuss the juggling act of designing for mobile mapping functionality without sacrificing desktop design, weighing the costs of increased functionality versus our ability to time-effectively include that functionality, and the challenge of building a site that could be developed iteratively, with an eye towards future enhancement and sustainability. Finally, we’ll provide recommendations for other librarians at smaller institutions for their own efforts at digital development.&lt;br /&gt;
&lt;br /&gt;
== Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==&lt;br /&gt;
 &lt;br /&gt;
* Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art&lt;br /&gt;
&lt;br /&gt;
The Museum of Modern Art has amassed a large collection of audiovisual materials over its many decades of existence. In order to preserve these materials, much of the audiovisual collection has been digitized. This is a complex process involving numerous steps and devices, and the methods used for digitization can have an effect on the quality of the file that is preserved. Therefore, knowing exactly how something was digitized is critical for future stewards of these objects to be able to properly care for and preserve them. However, detailed technical information about the processes involved in the digitization of audiovisual materials is not defined explicitly in most metadata schemas used for audiovisual materials. In order to record process history using existing metadata standards, some level of creativity is required to allow existing standards to express this information.&lt;br /&gt;
&lt;br /&gt;
This talk will detail different metadata standards, including PBCore, PREMIS, and reVTMD, that can be implemented as methods of recording this information. Specifically, the talk will examine efforts to integrate this metadata into the Museum of Modern Art’s new digital repository, the DRMC. This talk will provide background on the DRMC as well as MoMA’s specific institutional needs for process history metadata, then discuss different metadata implementations we have considered to document process history.&lt;br /&gt;
&lt;br /&gt;
== Pig Kisses Elephant: Building Research Data Services for Web Archives ==&lt;br /&gt;
 &lt;br /&gt;
* Jefferson Bailey,  jefferson@archive.org, Internet Archive&lt;br /&gt;
* Vinay Goel, vinay@archive.org, Internet Archive&lt;br /&gt;
&lt;br /&gt;
More and more libraries and archives are creating web archiving programs.  For both new and established programs, these archives can consist of hundreds of thousands, if not millions, of born-digital resources within a single collection; as such, they are ideally suited for large-scale computational study and analysis. Yet current access methods for web archives consist largely of browsing the archived web in the same manner as browsing the live web and the size of these collections and complexity of the WARC format can make aggregate analysis difficult. This talk will describe a project to create new ways for users and researchers to access and study web archives by offering extracted and post-processed datasets derived from web collections. Working with the 325+ institutions and their 2600+ collections within the Archive-It service, the Internet Archive is building methods to deliver a variety of datasets culled from collections of web content, including extracted metadata packaged in JSON, longitudinal link graph data, named entities, and other types of data. The talk will cover the technical details of building dataset production pipelines with Apache Pig, Hadoop, and tools like Stanford NER, the programmatic aspects of building data services for archives and researchers, and ongoing work to create new ways to access and study web archives.&lt;br /&gt;
&lt;br /&gt;
== Awesome Pi, LOL! ==&lt;br /&gt;
&lt;br /&gt;
* Matt Connolly, mconnolly@cornell.edu, Cornell University Library&lt;br /&gt;
* Jennifer Colt, jrc88@cornell.edu, Cornell University Library&lt;br /&gt;
&lt;br /&gt;
Inspired by Harvard Library Lab’s “Awesome Box” project, Cornell’s Library Outside the Library (LOL) group is piloting a more automated approach to letting our users tell us which materials they find particularly stunning. Armed with a Raspberry Pi, a barcode scanner, and some bits of kit that flash and glow, we have ventured into the foreign world of hardware development. This talk will discuss what it’s like for software developers and designers to get their hands dirty, how patrons are reacting to the Awesomizer, and LOL’s not-afraid-to-fail philosophy of experimentation.&lt;br /&gt;
&lt;br /&gt;
== You Gotta Keep 'em Separated: The Case for &amp;quot;Bento Box&amp;quot; Discovery Interfaces ==&lt;br /&gt;
 &lt;br /&gt;
* Jason Thomale,  jason.thomale@unt.edu, University of North Texas Libraries&lt;br /&gt;
&lt;br /&gt;
I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.&lt;br /&gt;
&lt;br /&gt;
The thing is, practically all of us--in academic libraries at least--have a similar set up for discovery, with just a few variations, and so talking about it still seems useful. Stop me if this sounds familiar. You've got a single search box on the library homepage as a starting point for discovery. And it's probably a tabbed affair, with an option for searching the catalog for books, an option for searching a discovery service for articles, an option for searching databases, and maybe a few others. Maybe you have an option to search everything at once--probably the default, if you have it. And, if you're a crazy hepcat, maybe you ''only'' have your one search that searches everything, with no tabs.&lt;br /&gt;
&lt;br /&gt;
Now, the question is, for your &amp;quot;everything&amp;quot; search, are you doing a combined list of results, or are you doing it bento-box style, with a short results list from each category displayed in its own compartment?&lt;br /&gt;
&lt;br /&gt;
At UNT, we've been holding off on implementing an &amp;quot;everything&amp;quot; search, for various reasons. One reason is that the evidence for either style hasn't been very clear. There's this persistent paradox that we just can't reconcile: users tell us, through word and action, that they prefer searching Google, yet, libraries aren't Google, and there are valid design reasons why we shouldn't try to oversimplify our discovery interfaces to be like Google. And there's user data that supports both sides.&lt;br /&gt;
&lt;br /&gt;
Holding off on making this decision has granted us 2 years of data on how people use our tabbed search interface that does ''not'' include an &amp;quot;everything&amp;quot; search. Recently I conducted a thorough analysis of this data--specifically the usage and query data for our catalog and discovery system (Summon). And I think it helps make the case for a bento box style discovery interface. To be clear, it isn't exactly the smoking gun that I was hoping for, but the picture it paints I think is telling. At the very least, it points away from a combined-results approach.&lt;br /&gt;
&lt;br /&gt;
I'm proposing a talk discussing the data we've collected, the trends we've seen, and what I think it all means--plus other reasons that we're jumping on the &amp;quot;bento box&amp;quot; discovery bandwagon and why I think &amp;quot;bento box&amp;quot; is at this point the path that least sells our souls.&lt;br /&gt;
&lt;br /&gt;
== Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift ==&lt;br /&gt;
 &lt;br /&gt;
* Ashley Blewer!, ashley.blewer@gmail.com&lt;br /&gt;
&lt;br /&gt;
Checksum technology is used all over the place, from git commits to authenticating Linux packages. It is most commonly used in the digital preservation field to monitor materials in storage for changes that will occur over time or used in the transmission of files during duplication. But do you even checksum, bro? I want this talk to move checksums from a position of mysterious macho jargon to something everyone can understand and want to use. I think a lot of people have heard of checksum but don’t know where to begin when it comes to actually using it at their institution. And cryptography is hella intimidating! This talk will cover what checksums are, how they can be integrated into a library or archival workflow, protecting collections requiring additional levels of security, algorithms used to verify file fixity and how they are different, and other aspects of cryptographic technology. Oh, and please note that all points in this talk will be emphasized or lightly performed through Taylor Swift lyrics. Seriously, this talk will consist of at least 50% Taylor Swift. Can you, like, even?&lt;br /&gt;
&lt;br /&gt;
== Level Up Your Coding with Code Club (yes, you can talk about it) ==&lt;br /&gt;
&lt;br /&gt;
* Coral Sheldon-Hess, coral@sheldon-hess.org&lt;br /&gt;
&lt;br /&gt;
Reading code is a necessary part of becoming a better developer. It gives you more experience and more insight into How Things Are (or Aren't) Done; it builds your intuition about how to solve problems with code; and it increases your confidence that you, too, can tackle whatever technological problems you're facing.&lt;br /&gt;
&lt;br /&gt;
But you don't have to read code alone! (Which is good. It's really not fun to read code alone.) &lt;br /&gt;
&lt;br /&gt;
In late 2014, a group of librarians formed two Code Clubs, inspired by [http://bloggytoons.com/code-club/ this talk by Saron] (of Bloggytoons fame). I'd like to tell you about how we've structured our Code Clubs, what has gone well, what we've learned, and what you need to do to form your own Code Club. I'll share a list of the codebases we've looked at, too, to help you get your own Code Club off the ground! &lt;br /&gt;
&lt;br /&gt;
== The Growth of a Programmer ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:jgo | Joshua Gomez]], Getty Research Institute, jgomez@getty.edu&lt;br /&gt;
&lt;br /&gt;
Just like other creative endeavors, software developers can experience periods of great productivity or find themselves in a rut. After contemplating the alternating periods in my own career I've noticed several factors that have effected my own professional growth and happiness, including: mentorship, structure, community, teamwork, environment, formal education, etc. Not all of the factors need to be present at all times; but some mixture of them is critical for continued growth. In this talk, I will articulate these factors, discuss how they can effect a developer's career, and how they can be sought out when missing. This talk is aimed at both new developers looking to strike their own path as well as the veterans that lead or mentor them.&lt;br /&gt;
&lt;br /&gt;
== Developing a Fedora 4.0 Content Model for Disk Images ==&lt;br /&gt;
&lt;br /&gt;
* Matthew Farrell, matthew.j.farrell@duke.edu, Duke University Libraries&lt;br /&gt;
* Alexandra Chassanoff, achass@email.unc.edu, BitCurator Access Project Manager&lt;br /&gt;
&lt;br /&gt;
As the acquisition of born-digital materials grows, institutions are seeking methods to facilitate easy ingest into their repositories and provide access to disk images and files derived or extracted from disk images. In this session, we describe our development of a Fedora 4.0 Content model for disk images, including acceptable image file formats and the rationale behind those choices.  We will also discuss efforts to integrate the disk image content model into the BitCurator Access environment. Unlike generalized, format-agnostic content models which might treat the disk image as a generic bitstream, a content model designed for disk images enables expression of relationships among associated content in the collection such as files extracted from images and other born-digital and digitized material associated with the same creator.  It also enables capture of file-system attributes such as file paths, timestamps, whether files are allocated/deleted, etc.  Further, a disk image content model suggests further steps repositories can take in order to transform and re-use associated metadata generated during the creation and forensic analysis of the disk image.&lt;br /&gt;
&lt;br /&gt;
== Data acquisition and publishing tools in R ==&lt;br /&gt;
&lt;br /&gt;
* Scott Chamberlain,  scott@ropensci.org, rOpenSci/UC Berkeley - first-time presenter&lt;br /&gt;
&lt;br /&gt;
R is an open source programming environment that is widely used among researchers in many fields. R is powerful because it's free, increasingly robust, and facilitates reproducible research, an increasingly sought after goal in academia. Although tools for data manipulation/visualization/analysis are well developed in R, data acquisition and publishing tools are not. rOpenSci is a collaborative effort to create the tools necessary to complete the reproducible research workflow. This presentation discusses the need for these tools, including examples, including interacting with the repositories Mendeley, Dryad, DataONE, and Figshare. In addition, we are building tools for searching scholarly metadata and acuiring full text of open access articles in a standarized way across metadata providers (e.g., Crossref, DataCite, DPLA) and publishers (e.g., PLOS, PeerJ, BMC, Pubmed). Last, we are building out tools for data reading and writing in Ecologial Metadata Language (EML).&lt;br /&gt;
&lt;br /&gt;
== SPLUNK: Log File Analysis ==&lt;br /&gt;
&lt;br /&gt;
* Jim LeFager, jlefager@depaul.edu, DePaul University Library&lt;br /&gt;
DePaul University Library recently took over monitoring and maintaining of the library EZproxy servers this past year and using Splunk, a machine data analysis tool, we are able to gather information and statistics on our electronic resource usage in addition to monitoring the servers. Splunk is a tool that can collect, analyze, and visualize log files and other machine data in real time and this has allowed for gathering realtime usage statistics for our electronic resources allowing us to filter by multiple facets including IP Range, Group Membership (student, faculty), so that we can see who is accessing our resources and from where. Splunk allows our library to query our data and create rich custom dashboards as well as create alerts that can be triggered when certain conditions are met, such as error codes, which can send an email alert to a group of users. We will be leveraging Splunk to monitor all library web applications going forward. This talk will review setting up Splunk and best practices in using the available features and customizations available including creating queries, alerts, and custom dashboards.  &lt;br /&gt;
&lt;br /&gt;
== Your code does not exist in a vacuum ==&lt;br /&gt;
* Becky Yoose, yoosebec at grinnell dot edu, Grinnell College (Done a lightning talk, MC duties, but have not presented a prepared talk)&lt;br /&gt;
&lt;br /&gt;
“If you have something to say, then say it in code…” - Sebastian Hammer, code4lib 2009&lt;br /&gt;
&lt;br /&gt;
In its 10 year run, code4lib has covered the spectrum of libtech development, from search to repositories to interfaces. However, during this time there has been little discussion about this one little fact about development - code does not exist in a vacuum. &lt;br /&gt;
&lt;br /&gt;
Like the comment above, code has something to say. A person’s or organization’s culture and beliefs influences code in all steps of the development cycle. What development method you use, tools, programming languages, licenses - everything is interconnected with and influenced by the philosophies, economics, social structures, and cultural beliefs of the developer and their organization/community.&lt;br /&gt;
&lt;br /&gt;
This talk will discuss these interconnections and influences when one develops code for libraries, focusing on several development practices (such as “Fail Fast, Fail Often” and Agile)   and licensing choices (such as open source) that libtech has either tried to model or incorporate into mainstream libtech practices. It’ll only scratch the surface of the many influences present in libtech development, but it will give folks a starting point to further investigate these connections at their own organizations and as a community as a whole.&lt;br /&gt;
&lt;br /&gt;
tl;dr - this will be a messy theoretical talk about technology and libraries. No shiny code slides, no live demos. You might come out of this talk feeling uncomfortable. Your code does not exist in a vacuum. Then again, you don’t exist in a vacuum either.&lt;br /&gt;
&lt;br /&gt;
== The Metadata Hopper: Mapping and Merging Metadata Standards for Simple, User-Friendly Access ==&lt;br /&gt;
&lt;br /&gt;
* Tracy Seneca, tjseneca@uic.edu, University of Illinois at Chicago&lt;br /&gt;
* Esther Verreau: verreau1@uic.edu, University of Illinois at Chicago&lt;br /&gt;
&lt;br /&gt;
The Chicago Collections Consortium: 15 institutions and growing!  8 distinct EAD standards! At least 3 permutations of MARC, and we lost count of the varieties of custom CONTENTdm image collections.  Not to mention the 14,730 unique subject terms, nearly all of which lead our poor end-users to exactly one organization's content. &lt;br /&gt;
&lt;br /&gt;
All large content aggregation projects have faced this challenge, and there are a few emerging tools to help us wrangle disparate metadata into new contexts.  The Metadata Hopper is one such tool. The Metadata Hopper enables archivists to map their local metadata standards to standardized deposit records, and tags those materials using a shared vocabulary, integrating them into a user-friendly portal without disrupting local practices. In last year's Code4Lib lightning talk we described the challenges that the Chicago Collections Consortium faces in creating shared, in-depth access to archival and digital collections about Chicago history and culture across CCC member organizations. This year, thanks to the Andrew W. Mellon Foundation, we have a working Django application to demonstrate.  In this talk we'll discuss the design that enables multiple layers of flexibility, from the ability to accept a variety of metadata standards to designing for an open source audience.&lt;br /&gt;
&lt;br /&gt;
http://chicagocollectionsconsortium.org&lt;br /&gt;
&lt;br /&gt;
== Programmers are not projects: lessons learned from managing humans ==&lt;br /&gt;
&lt;br /&gt;
* Erin White, erwhite@vcu.edu, Virginia Commonwealth University - first-time presenter&lt;br /&gt;
&lt;br /&gt;
Managing projects is one thing, but managing people is another. Whether we’re hired as managers or grow “organically” into management roles, sometimes technical people end up leading technical teams (gasp!). I’ll talk about lessons I’ve learned about hiring, retaining, and working long-term and day-to-day with highly tech-competent humans. I’ll also talk about navigating the politics of libraryland, juggling different types of projects, and working with constrained budgets to make good things and keep talented people engaged.&lt;br /&gt;
&lt;br /&gt;
== Practical Strategies for Picking Low-Hanging Fruits to Improve Your Library's Web Usability and UX ==&lt;br /&gt;
&lt;br /&gt;
* Bohyun Kim, bkim@hshsl.umaryland.edu, University of Maryland, Baltimore&lt;br /&gt;
&lt;br /&gt;
Have you ever tried to fix an obvious (to you at least!) problem in Web usability or UX (user experience) only to face strong resistance from the library staff? Are you a strong advocate for making library resources, systems, services, and space as usable as possible, but do you often find yourself struggling to get the point across and/or obtain the crucial buy-in from colleagues and administrators? &lt;br /&gt;
&lt;br /&gt;
There is no shortage of Web usability and UX guidelines. But applying them to a library and implementing desired changes often involve a long and slow process. To tackle this issue, this talk will focus on how to utilize the 'expert review' process (aka 'heuristic evaluation') as a preliminary or even preparatory step before embarking on more time-and-labor-intensive usability testing and user research. Several examples from  simple fixes to more nuanced usability and UX issues in libraries will be discussed to your heart's content. The goal of this talk is to provide practical strategies for picking as many low-hanging fruits as possible to make a real (albeit small) difference to your library's Web usability and UX effectively and efficiently.&lt;br /&gt;
&lt;br /&gt;
== A Semantic Makeover for CMS Data ==&lt;br /&gt;
&lt;br /&gt;
* Bill Levay, wjlevay@gmail.com, Linked Jazz Project&lt;br /&gt;
&lt;br /&gt;
How can we take semi-structured but messy metadata from a repository like CONTENTdm and transform it into rich linked data? Working with metadata from Tulane’s Hogan Jazz Archive Photography Collection, the Linked Jazz Project used Open Refine and Python scripts to tease out proper names, match them with name authority URIs, and specify FOAF relationships between musicians who appear together in photographs. Additional RDF triples were created for any dates associated with the photos, and for those images with place information we employed GeoNames URIs. Historical images and data that were siloed can now interact with other datasets, like Linked Jazz’s rich set of names and personal relationships, and can be visualized [link to come] or otherwise presented on the web in any number of ways. I have not previously presented at a Code4Lib conference.&lt;br /&gt;
&lt;br /&gt;
== Taking User Experience (UX) to new heights ==&lt;br /&gt;
 &lt;br /&gt;
* Kayne Richens, kayne.richens@deakin.edu.au, Deakin University&lt;br /&gt;
&lt;br /&gt;
User Experience, or &amp;quot;UX&amp;quot;, is for more than just websites. At Deakin University Library we're exploring ways to improve the user experience inside our campus library spaces, by putting new technologies front and centre in the overall experience for our students. How are we doing this? We’re collaborating with the University's IT department and exploring the following Library-changing opportunities:&lt;br /&gt;
&lt;br /&gt;
- Augmented Reality for Way-finding: We’re tackling that infamous thing that all Libraries can't get right – way-finding. We're enhancing library tour information and way-finding experiences by introducing augmented reality solutions.&lt;br /&gt;
 &lt;br /&gt;
- Heat mapping the library with wi-fi: We’re using our existing wi-fi infrastructure to present &amp;quot;heat maps&amp;quot; of library space utilisation, allowing our users to easily locate the space that best suits their needs, whether it be busy spaces to collaborate, or quiet spaces to study. And by overlaying computer usage and group study room bookings, users can quickly locate the space they need.&lt;br /&gt;
 &lt;br /&gt;
- Video chat library service: We’re piloting video-conferencing facilities in our group study rooms and spaces, connecting users and librarians and other professionals.&lt;br /&gt;
         &lt;br /&gt;
This talk will look at how these different technologies will be brought together to provide improved user experiences, as well some of the evidence and reasons that helped us to identify our needs, so you can too.&lt;br /&gt;
&lt;br /&gt;
==How to Hack it as a Working Parent: or, Should Your Face be Bathed in the Blue Glow of a Phone at 2 AM?==&lt;br /&gt;
&lt;br /&gt;
*Margaret Heller, Loyola University Chicago, mheller1@luc.edu&lt;br /&gt;
*Christina Salazar, California State University Channel Islands, christina.salazar@csuci.edu&lt;br /&gt;
*May Yan, Ryerson University, may.yan@ryerson.ca&lt;br /&gt;
&lt;br /&gt;
Modern technology has made it easier than ever for parents employed in technical environments to keep up with work at all hours and in all locations. This makes it possible to work a flexible schedule, but also may lead to problems with work/life balance and furthering unreasonable expectations about working hours. Add to that shifting gender roles and limited paid parental leave in the United States and you have potential for burnout and a certainty for anxiety. It raises the additioal question of whether the “always connected” mindset puts up a barrier to some populations who otherwise might be better represented in open source and library technology communities. &lt;br /&gt;
&lt;br /&gt;
This presentation will address tools that are useful for working parents in technical library positions, and share some lessons learned about using these tools while maintaining a reasonable work/life balance. We will consider a question that Karen Coyle raised back in 1996: &lt;br /&gt;
“What if the thousands of hours of graveyard shift amateur hacking wasn't really the best way to get the job done? That would be unthinkable.” &lt;br /&gt;
&lt;br /&gt;
For those who are able to take an extended parental leave, we will present strategies for minimizing the impact to your career and your employer. For those (particularly in the United States) who are only able to take a short leave will require different strategies. Despite different levels of preparation, all are useful exercises in succession planning and making a stronger workplace and future ability to work a flexible schedule through reviewing workloads, cross-training personnel, hiring contract replacements, and creative divisions of labor. Such preparation makes work better for everyone, kids or no kids or caretakers of any kind.&lt;br /&gt;
&lt;br /&gt;
==Making your digital objects embeddable around the web==&lt;br /&gt;
 &lt;br /&gt;
* Jessie Keck, jkeck@stanford.edu, Stanford University Libraries&lt;br /&gt;
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
With more and more content from our digital repositories making their way into our discovery environments we quickly realize that we’re repeatedly re-inventing the wheel when it comes to creating “Viewers” for these digital objects.  With various different types of viewers necessary (books, images, audio, video, geospatial data, etc) the burden of getting these viewers into various environments (topic guides, blogs, catalogs, etc) becomes exponential.&lt;br /&gt;
&lt;br /&gt;
In this talk we’ll discuss how Stanford University Libraries implemented an oEmbed service to create an extensible viewer framework for all of its digital content. Using this service we’ve been able to easily integrate viewers into various discovery applications as well as make it easy for end users who discover our objects to easily embed customized versions into their own websites and blogs.&lt;br /&gt;
&lt;br /&gt;
==So you want to make your geospatial data discoverable==&lt;br /&gt;
 &lt;br /&gt;
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
Finding data for research or coursework can be one of the most time intensive tasks for a scholar or student. We introduce GeoBlacklight, an open source, multi-institutional software project focused on solving these common challenges at institutions across the world. GeoBlacklight prioritizes user experience, integrates with many GIS tools, and streamlines the use and organization of geospatial data. This talk will provide an introduction to the software, demonstrate current functionality, and provide a road map for future work.&lt;br /&gt;
&lt;br /&gt;
== Clueless-Driven Development: How I learned to migrate to Fedora 4 ==&lt;br /&gt;
&lt;br /&gt;
* Adam Wead, awead@psu.edu, Penn State University&lt;br /&gt;
&lt;br /&gt;
Recently I was tasked with migrating the content from our Fedora3 repository to the new Fedora4 repository architecture.&lt;br /&gt;
Despite a wealth of community support, I had no idea how to approach, or even begin to solve this problem. I knew I&lt;br /&gt;
wanted to follow best practices and use test-driven  development to build my solution, but had no idea where to start.&lt;br /&gt;
Despite this initial setback, I was able to start writing tests with only a  vague understanding of the problem. As my&lt;br /&gt;
tests exposed where my understanding of the problem was flawed, my code evolved, and within a week I had arrived  at a&lt;br /&gt;
working solution that exhibited all the hallmarks of good testing and software design.&lt;br /&gt;
&lt;br /&gt;
This talk recounts the process I went through from starting with practically nothing, to arriving at a working solution.&lt;br /&gt;
You can follow the rules of  test-driven development, but you can write tests in an expressive way to describe the&lt;br /&gt;
problem instead of just describing what the code should do. It was also essential to begin testing from an integration&lt;br /&gt;
viewpoint as opposed to a unit one, because at the outset the units were unknown and were later realized through further&lt;br /&gt;
development. For the presentation, I will be demonstrating using RSpec and Ruby. All the code examples will be related&lt;br /&gt;
to the Hydra software stack; however, I hope to show  that the processes at work will be applicable in any context.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Designing and Leading a Kick A** Tech Team ==&lt;br /&gt;
 &lt;br /&gt;
* Sibyl Schaefer,  sschaefer@rockarch.org, Rockefeller Archive Center&lt;br /&gt;
&lt;br /&gt;
New managers are often promoted without receiving management training, yet management is not something you just figure out. The experience of being expected to know how to manage, yet not being trained to do so often results in new managers feeling isolated and unsure how to move from making to managing. In this talk I’ll focus on my own managerial experience of designing and leading an archival tech team in a small independent archives. Topics covered will include hiring, delegating, creating a team culture, and leading people whose specialized knowledge exceeds your own. The talk take-aways should be applicable to managers and employees at large and small institutions alike.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==American (Archives) Horror Story: LTO Failure and Data Loss ==&lt;br /&gt;
 &lt;br /&gt;
* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH&lt;br /&gt;
* Casey Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH&lt;br /&gt;
&lt;br /&gt;
Here’s a story to send shivers down archival spines: when transferring video files off LTO for the American Archive project, WGBH got an initial failure rate of 57%.   After repeat tries, the rates improved; still, an unnervingly large percentage of files were never able to be transferred successfully.   Even more unnerving, going public with our horror story got a big response from other archives using LTO -- it seems like many institutions are having similarly scary results.   What are the real risks with LTO tape?  Are there steps that archives should be taking to better circumvent those risks?  This presentation will share information about LTO storage failures across archives world and discuss the process of investigating the problem at WGBH by testing different methods of data retrieval from LTO (direct and networked downloads, individual file retrieval and bulk data dump, use of LTO 4 and LTO 6 decks) and using checksum comparisons and file analysis and characterization tools such as ffprobe, mediainfo and exiftool to analyze failed files.  We'll also present whatever results we’ve managed to turn up by the time of Code4Lib!&lt;br /&gt;
&lt;br /&gt;
== PBCore in Action: Three Words, Not Two! ==&lt;br /&gt;
 &lt;br /&gt;
* Casey E. Davis,  casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH&lt;br /&gt;
* Andrew (Drew) Myers, andrew_myers@wgbh.org, Supervising Developer, WGBH&lt;br /&gt;
&lt;br /&gt;
In 2001, public media representatives developed the PBCore XML schema to establish a common language for managing metadata about their analog and digital audio and video. Since then, PBCore has been adopted by a number of organizations and archivists in the moving image archival community. The schema has also undergone a few revisions, but on more than one occasion it was left orphaned and with little to no support.&lt;br /&gt;
 &lt;br /&gt;
Times have changed. You may have heard the news that PBCore is back in action as part of the American Archive of Public Broadcasting initiative and via the Association of Moving Image Archivists (AMIA) PBCore Advisory Subcommittee. A group of archivists, public media stakeholders, and engaged users have come together to provide necessary support for the standard and to see to its further development. It's really exciting to see that archivists are finally starting to deal with their audiovisual collections, and we are confident that PBCore will have a place in those efforts.&lt;br /&gt;
 &lt;br /&gt;
At this session, we'll discuss the scope and uses of PBCore in digital preservation and access, report on the progress and goals of the PBCore Advisory Subcommittee, and share how the group (by the time of the conference) will have transformed the XML schema into an RDF ontology, bringing PBCore into the second decade of the 21st century. #PBHardcore&lt;br /&gt;
&lt;br /&gt;
==Collaborating to Avert the Digital Graveyard==&lt;br /&gt;
&lt;br /&gt;
* Harish Nayak, hnayak@library.rochester.edu, University of Rochester Libraries &lt;br /&gt;
* Sean Morris, smorris@library.rochester.edu, University of Rochester Libraries &lt;br /&gt;
&lt;br /&gt;
In 1995, the Robbins Library at the University of Rochester created a digital collection of Arthurian texts, images, and bibliographies. Together with medieval scholars, we recently completed the redesign and development of an interface for this collection. Using FRBR concepts, we re-conceptualized organization and editing workflow from the ground up in a mobile-first Drupal-based project. &lt;br /&gt;
&lt;br /&gt;
In this talk we will describe the project as well as how we utilized the techniques of work practice study and user centered design to maintain engagement with reluctant stakeholders, nontechnical scholars, and VERY meticulous graduate students.  Neither of us have previously presented at a Code4Lib conference.&lt;br /&gt;
&lt;br /&gt;
==Docker? VMs? EC2? Yes! With Packer.io==&lt;br /&gt;
&lt;br /&gt;
* Kevin S. Clarke, ksclarke@gmail.com, Digital Library Programmer, UCLA&lt;br /&gt;
&lt;br /&gt;
There are a lot of exciting ways to deploy a software stack nowadays. Many of our library systems are fully virtualized. Docker is a compelling alternative, and there are also cloud options like Amazon's EC2. This talk will introduce Packer.io, a tool for creating identical machine images for multiple platforms (e.g., Docker, VMWare, VirtualBox, EC2, GCE, OpenStack, et al.) all from a single source configuration.  It works well with Ansible, Chef, Puppet, Salt, and plain old Bash scripts. And, it's designed to be scriptable so that builds can be automated. This presentation will show how easy it is to use Packer.io to bring up a set of related services like Fedora 4, Grinder (for stress testing), and Graphite (for charting metrics). As an added value, all the buzzwords in this proposal will be defined and explained!&lt;br /&gt;
&lt;br /&gt;
== Technology on your Wrist: Cross-platform Smartwatch Development for Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:sanderson|Steven Carl Anderson]], sanderson@bpl.org, Boston Public Library (no previously accepted prepared talks but have done lightning talks in the past)&lt;br /&gt;
&lt;br /&gt;
I'll be the first to admit: smartwatches are unlikely to completely revolutionize how a library provides online services. But I believe they still represent an opportunity to further enhance existing library services and resources in a unique way.&lt;br /&gt;
&lt;br /&gt;
At the Boston Public Library (BPL), we're in the initial phases of designing a modest smartwatch app to provide notifications for circulation availability and checked-out-material due-date alerts by the end of current year. We're starting small, but we plan to evolve the concept over time as we see what (if any) traction such an application gets with potential users. For example, we plan to explore the possibility of adding &amp;quot;nearest branch to my current location&amp;quot; functionality to this app.&lt;br /&gt;
&lt;br /&gt;
Despite the &amp;quot;development phase&amp;quot; of this application as of this writing, this talk is not being given by a novice. As a technology enthusiast, I've released [http://www.phdgaming.com/smartwatch_projects/ five smartwatch applications] and have had two of those be finalists in a [http://www.phdgaming.com/samsung_challenge/ Samsung sponsored development challenge]. This experience not only will allow for the BPL to avoid many beginner mistakes in its smartwatch app development but also gives a much more complete understanding of the smartwatch development ecosystem.&lt;br /&gt;
&lt;br /&gt;
This talk will explore the following questions:&lt;br /&gt;
&lt;br /&gt;
* What kinds of online library services could potentially be transformed or translated into the smartwatch/wearable domain? What kinds of services are better left alone? These questions are currently being explored and I'll talk about our plans and experiences. Included will be any statistical information from our application launch along with statistics from my personal development.&lt;br /&gt;
&lt;br /&gt;
* How to support all the different operating systems these devices run without painful modifications to your codebase. (There's Tizen that is used by Samsung's Gear 2 and Gear S, Android Wear that is used by most other non-Apple manufacturers, then there is Apple's upcoming smartwatch itself, etc.)&lt;br /&gt;
&lt;br /&gt;
* How to support different screen resolutions on such a small device. From round to rectangular to perfectly square, smartwatches come in all different shapes these days.&lt;br /&gt;
&lt;br /&gt;
* What are the app stores like on these platforms? As I support multiple applications through different distribution networks, a guide to navigating how to distribute one's app is included and I'll reveal how these systems work “behind the curtain.”&lt;br /&gt;
&lt;br /&gt;
* What are common issues and pitfalls to avoid when doing development? Tips on broken APIs and how to cope or optimizing your code will be included.&lt;br /&gt;
&lt;br /&gt;
==Seeing the Forest From the Trees: The Art of Creating Workflows for Digital Projects ==&lt;br /&gt;
 &lt;br /&gt;
* Jen LaBarbera, j.labarbera@neu.edu, NDSR Resident, Northeastern University&lt;br /&gt;
* Joey Heinen, joseph_heinen@harvard.edu, NDSR Resident, Harvard University&lt;br /&gt;
* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH&lt;br /&gt;
* Tricia Patterson, triciap@mit.edu, NDSR Resident, MIT&lt;br /&gt;
&lt;br /&gt;
We have to &amp;quot;turn projects into programs&amp;quot; in order to create a solid and sustainable digital preservation initiative...but what the heck does that even mean? What does that look like?&lt;br /&gt;
&lt;br /&gt;
In this talk, members of the inaugural Boston cohort of the National Digital Stewardship Residency will discuss one piece of our digital preservation test kitchen: our stabs at creating digital workflows that will (hopefully) help our institutions turn digital preservation projects into programs. Specifically, we will talk about how difficult it is to create a general and overarching workflow for digital preservation tasks (e.g. ingest into repositories, format migrations, etc.) that incorporates various technical tools while also taking into account the myriad and unending list of possible exceptions or special scenarios. Turning these complicated, specific processes into a simplified and generalized workflow is an art. We haven't necessarily perfected that art yet, but in this talk, we'll share what has worked for us -- and what hasn't. We’ll also touch on the importance of documentation, and achieving that delicate balance of adequately thorough documentation that doesn’t pose the risk of information avalanche. These processes often create more questions than answers, but we'll share the answers that we (and our mentors) have found along the way!&lt;br /&gt;
&lt;br /&gt;
== Annotations as Linked Data with Fedora4 and Triannon (a Real Use Case for RDF!) ==&lt;br /&gt;
&lt;br /&gt;
* Rob Sanderson, azaroth@stanford.edu,  Stanford University Libraries&lt;br /&gt;
* Naomi Dushay, ndushay@stanford.edu,  Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
Annotations on content resources allow users to contribute knowledge within the digital repository space.  W3C Open Annotation provides a comprehensive model for web annotation on all types of content, using Linked Data as a fundamental framework.  Annotation clients generate instances of this model, typically using a JSON serialization, but need to store that data somewhere using a standard interaction pattern so that best of breed clients, servers, and data can be mixed and matched.&lt;br /&gt;
&lt;br /&gt;
Stanford is using Fedora4 for managing Open Annotations, via a middleware component called Triannon.  Triannon receives the JSON data from the annotation client, and uses the Linked Data Platform API implementation in Fedora4 to create, retrieve, update and delete the constituent resources.  Triannon could be easily modified to use other LDP implementations, or could be modified to work with linked data other than annotations.&lt;br /&gt;
&lt;br /&gt;
== Helping Google (and scholars, researchers, educators, &amp;amp; the public) find archival audio ==&lt;br /&gt;
&lt;br /&gt;
* Anne Wootton, anne@popuparchive.org, Pop Up Archive (www.popuparchive.org)&lt;br /&gt;
&lt;br /&gt;
Culturally significant digital audio collections are hard to discover on the web. There are major barriers keeping this valuable media from scholars, researchers, and the general public:&lt;br /&gt;
&lt;br /&gt;
Audio is opaque: you can’t picture sound, or skim the words in a recording. &lt;br /&gt;
Audio is hard to share: there’s no text to interact with. &lt;br /&gt;
Audio is not text: but since text is the medium of the web, there’s no path for audiences to find content-rich audio.&lt;br /&gt;
Audio metadata is inconsistent and incomplete.&lt;br /&gt;
&lt;br /&gt;
At Pop Up Archive, we're helping solve this problem making the spoken word searchable. We began as a UC-Berkeley School of Information Master's thesis to provide better access to recorded sound for audio producers, journalists, and historians. Today, Pop Up Archive processes thousands of hours of sound from all over the web to create automatic, timestamped transcripts and keywords, working with media companies and institutions like NPR, KQED, HuffPost Live, Princeton, and Stanford. We're building collections of sound from journalists, media organizations, and oral history archives from around the world. Pop Up Archive is supported by the John S. and James L. Knight Foundation, the National Endowment for the Humanities, and 500 Startups.&lt;br /&gt;
&lt;br /&gt;
== Digital Content Integrated with ILS Data for User Discovery:  Lessons Learned ==&lt;br /&gt;
&lt;br /&gt;
* Naomi Dushay, ndushay@stanford.edu,  Stanford University Libraries&lt;br /&gt;
* Laney McGlohon, laneymcg@stanford.edu,  Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
So you want to expose your digital content in your discovery interface, integrated with the data from your ILS?  How do you make the best information user searchable?  How do you present complete, up to date search results with a minimum of duplicate entries?&lt;br /&gt;
&lt;br /&gt;
At Stanford, we have these cases and more:&lt;br /&gt;
* digital content with no metadata in ILS&lt;br /&gt;
* digital content for metadata in ILS&lt;br /&gt;
* digital content with its own metadata derived from ILS metadata.&lt;br /&gt;
&lt;br /&gt;
We will describe our efforts to accommodate multiple updatable metadata sources for materials in the ILS and our Digital Object Repository while presenting users with reduced duplication in SearchWorks.  Included will be some failures, some successes, and an honest assessment of where we are now.&lt;br /&gt;
&lt;br /&gt;
== Show All the Things: Kanban for Libraries == &lt;br /&gt;
&lt;br /&gt;
* Mike Hagedon, mhagedon@email.arizona.edu, University of Arizona Libraries&lt;br /&gt;
&lt;br /&gt;
The web developers at the University of Arizona Libraries had a problem: we were working on a major website rebuild project with no clear way to prioritize it against our other work. We knew we wanted to follow Agile principles and initially chose Scrum to organize and communicate about our work. But we found that certain core pieces of Scrum did not work for our team. Then we discovered Kanban, an Agile meta-process for organizing work (team or individual) that treats the work more as a flow than as a series of fixed time boxes. I’ll be talking about our journey toward finding a process that works for our team and how we’ve applied the principles of Kanban to better get our work done. Specifically, we talk about principles like how to visualize all your work, how to limit how much you’re doing (to get more done!), and how to optimize the flow of your work.&lt;/div&gt;</summary>
		<author><name>Afred</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&amp;diff=41981</id>
		<title>2015 Prepared Talk Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&amp;diff=41981"/>
				<updated>2014-11-07T18:53:51Z</updated>
		
		<summary type="html">&lt;p&gt;Afred: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Code4lib 2015 is a loosely-structured conference that provides people working at the intersection of libraries/archives/museums/cultural heritage and technology with a chance to share ideas, be inspired, and forge collaborations. For more information about the Code4lib community, please visit http://code4lib.org/about/. &lt;br /&gt;
The conference will be held at the Portland Hilton &amp;amp; Executive Tower in Portland, Oregon, from February 9-12, 2015.&lt;br /&gt;
&lt;br /&gt;
'''Proposals for Prepared Talks:'''&lt;br /&gt;
&lt;br /&gt;
We encourage everyone to propose a talk.&lt;br /&gt;
 &lt;br /&gt;
Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:&lt;br /&gt;
* Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software&lt;br /&gt;
* Tools and technologies – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)&lt;br /&gt;
* Technical issues - Big issues in library technology that should be addressed or better understood&lt;br /&gt;
* Relevant non-technical issues – Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc.&lt;br /&gt;
&lt;br /&gt;
Proposals can be submitted through Friday, November 7, 2014 at 5pm PST (GMT−8). Voting will start on November 11, 2014 and continue through November 25, 2014. The URL to submit votes will be announced on the Code4Lib website and mailing list and will require an active code4lib.org account to participate. The final list of presentations will be announced in early- to mid-December.&lt;br /&gt;
&lt;br /&gt;
'''Proposals for Prepared Talks:'''&lt;br /&gt;
&lt;br /&gt;
Log in to the Code4lib wiki and edit this wiki page using the prescribed format. If you are not already registered, follow the instructions to do so.&lt;br /&gt;
Provide a title and brief (500 words or fewer) description of your proposed talk.&lt;br /&gt;
If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist voters in opening the conference to new presenters.&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Talk Title: ==&lt;br /&gt;
 &lt;br /&gt;
* Speaker's name,  email address, and (optional) affiliation&lt;br /&gt;
* Second speaker's name, email address, and affiliation, if second speaker&lt;br /&gt;
&lt;br /&gt;
Abstract of no more than 500 words.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Talk Proposals'''&lt;br /&gt;
== Zines + Gamification = Awesomest Metadata Literacy Outreach Event Ever! ==&lt;br /&gt;
 &lt;br /&gt;
* [http://www.JenniferHecker.info Jennifer Hecker], jenniferraehecker@gmail.com, [http://www.lib.utexas.edu/subject/zines University of Texas Libraries] &amp;amp; [http://www.AustinFanzineProject.org Austin Fanzine Project]&lt;br /&gt;
* [http://anomalily.net/ Lillian Karabaic], librarian@iprc.org, [http://www.iprc.org/ Independent Publishing Resource Center] (Portland)&lt;br /&gt;
 &lt;br /&gt;
In academic libraries, and elsewhere, the popularity of zine (a magazine produced for love, not profit) collections is on the rise. At the same time, metadata literacy is becoming an increasingly important skill, helping people navigate and understand digital environments and interactions. We have found a way to teach metadata literacy to the general public that isn’t super-boring – in fact, we’ve made it downright fun!&lt;br /&gt;
&lt;br /&gt;
First, volunteer zine librarian Lillian Karabaic of Portland’s Independent Publishing Resource Center facilitated the creation of a gamified cataloging interface for the IPRC’s annual Raiders of the Lost Archives backlog-busting 24-hour volunteer cataloging event.&lt;br /&gt;
&lt;br /&gt;
Then, archivist Jennifer Hecker facilitated the adaptation of the IPRC’s game for use in a similar, but also very different context – promoting UT Libraries newly-acquired zine collections. The main goal of the academic-library-based event was increasing excitement around the collections, but with the side goal of building metadata literacy, and introducing an understanding of library cataloging issues.&lt;br /&gt;
&lt;br /&gt;
The Texas modification also conforms to the xZINECOREx metadata schema developed by the national [http://zinelibraries.info/ Zine Librarians Interest Group], and triggered interesting conversations with the Libraries’s cataloging department about evolving metadata standards and how to incorporate the products of crowd-sourcing projects into existing workflows.&lt;br /&gt;
&lt;br /&gt;
Both games will be demoed.&lt;br /&gt;
&lt;br /&gt;
We have never presented at Code4lib.&lt;br /&gt;
&lt;br /&gt;
== Do the Semantic FRBRoo ==&lt;br /&gt;
* Rosie Le Faive, rlefaive@upei.ca, University of Prince Edward Island&lt;br /&gt;
&lt;br /&gt;
[http://www.islandora.ca Islandora] is great for creating repositories of any data type, but how can you model meaningful relationships between digital objects and use them to tell a story?&lt;br /&gt;
&lt;br /&gt;
At UPEI, I’m assembling an ethnography of Prince Edward Island’s traditional fiddle music that includes musical clips, video clips, oral histories, musical notation, images, and ethnographic commentaries. In order to present an exhibition-style site, I’m tying these digital objects together via the people, places, events, tunes and topics that they share or describe. &lt;br /&gt;
&lt;br /&gt;
To describe the relationships, I’m extending Islandora to use [http://www.cidoc-crm.org/frbr_inro.html FRBRoo], a vocabulary that combines the FRBR model with CIDOC-CRM, the the object-oriented museum documentation ontology. These modules being developed will allow other researchers to create a structured, navigable digital repository of diverse object types, that uses Islandora as an exhibition platform. &lt;br /&gt;
&lt;br /&gt;
== Our $50,000 Problem: Why Library School? ==&lt;br /&gt;
* Jennie Rose Halperin, jhalperin@mozilla.com, Mozilla Corporation&lt;br /&gt;
&lt;br /&gt;
57 library schools in the United States are churning out approximately 100 graduates per year, many with debt upwards of $50,000.  According to ONet, [http://www.inthelibrarywiththeleadpipe.org/2011/is-the-united-states-training-too-many-librarians-or-too-few-part-1/ 84% of library jobs in the US require an MLS.] The library profession is [http://dpeaflcio.org/programs-publications/issue-fact-sheets/library-workers-facts-figures/) 92% white and 82% female and entry-level librarians can expect to make $32,500 per year.]&lt;br /&gt;
&lt;br /&gt;
Contrasted with developers, who are almost [http://www.ncwit.org/blog/did-you-know-demographics-technical-women 90% male] and can expect to make [http://www.forbes.com/sites/jennagoudreau/2011/06/01/best-entry-level-jobs/ $70,000 in an entry-level position,] these numbers are dismal.&lt;br /&gt;
&lt;br /&gt;
According to a recent survey, the top skill that outgoing library students want to know is “programming” and yet many MLS programs still consider Microsoft Word an essential technology skill.&lt;br /&gt;
&lt;br /&gt;
What is going on here? Why do we accept this fate, where mostly female debt-burdened professionals continue to be thrown onto the work force without the education their expensive degrees promised?&lt;br /&gt;
&lt;br /&gt;
As a community we need to come together to stop this cycle. We need to provide better support and mentorship to diversify and keep the profession relevant and help librarianship move into the future it deserves.&lt;br /&gt;
&lt;br /&gt;
This talk will walk through the challenges of navigating a hostile employment environment as well as present models for better development and future state imagining.&lt;br /&gt;
&lt;br /&gt;
== No cataloging software? Need more than Dublin Core? No problem!: Experiences with CollectiveAccess ==&lt;br /&gt;
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University&lt;br /&gt;
* Rachel Wittmann, rwittma@clemson.edu, Clemson University&lt;br /&gt;
&lt;br /&gt;
Clemson University Libraries has implemented the open-source software CollectiveAccess for customized digital collection needs. CollectiveAccess is an open-source project with the goal of providing a flexible way to manage and publish museum and archival collections. There are several applications associated with the projects; most used are: Providence (for cataloging and entering metadata) and Pawtucket (for displaying objects in a collection for the public). It has many profiles readily available for installing with existing library standards, such as Dublin Core, and there is a robust syntax for creating your own profiles to fit custom tailored metadata schemas. Plus, the user interface allows you to modify the metadata profile quickly and easily.&lt;br /&gt;
&lt;br /&gt;
In this talk, we will discuss:&lt;br /&gt;
* Our experiences with installing Providence and creating an installation profile that satisfies the needs of many of the Clemson Libraries digital archiving processes. &lt;br /&gt;
* The stumbling blocks experienced in that process and how they were resolved.&lt;br /&gt;
* The available plugins sourcing widely used authorities, such as Library of Congress thesauri and GeoNames.org, and how they have been used by our projects. &lt;br /&gt;
* A brief overview of the export and import functions and also current workflow practices within Providence.&lt;br /&gt;
* Future plans &amp;amp; the role of CollectiveAccess at Clemson University Libraries&lt;br /&gt;
&lt;br /&gt;
== Getting ContentDM and Wordpress to Play Together ==&lt;br /&gt;
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University&lt;br /&gt;
&lt;br /&gt;
Clemson University Libraries has a very strong program for digitizing and archiving photographs, and the Digital Imaging team processes many hundreds of photographs every month. These images are managed using different methods, including ContentDM, a digital collection manager.&lt;br /&gt;
&lt;br /&gt;
ContentDM provides various methods for searching and displaying photographs, along with their metadata. However, recent initiatives have resulted in the need to leverage those collections into exhibits displayed on other library-related websites, such as our Special Collections unit. The Clemson Libraries has invested heavily in Wordpress as our content management system of choice, and it seemed most efficient not to have to export and import images into our Wordpress sites in order to provide exhibited images.&lt;br /&gt;
&lt;br /&gt;
Fortunately, ContentDM has provided an API to many of their functions, allowing the extraction of metadata and even rescaled images through URLs. This project has been developing a plugin for Wordpress that integrates with ContentDM through shortcodes that Wordpress editors can easily include in their content. These shortcodes allow editors to choose how many images, which images from which collections, thumbnail sizes, etc. to display in different gallery styles. Plans are for it to allow integration with different plugins such as Fancybox and Masonry.&lt;br /&gt;
&lt;br /&gt;
In this presentation, I will demonstrate the current state of the plugin and discuss future plans. &lt;br /&gt;
&lt;br /&gt;
==Refinery — An open source locally deployable web platform for the analysis of large document collections==&lt;br /&gt;
 &lt;br /&gt;
* [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com&lt;br /&gt;
&lt;br /&gt;
Refinery is an open source web platform for the analysis of large unstructured document collections. It extracts meaningful semantic themes within documents also known as &amp;quot;topics&amp;quot; which can be thought of as word clouds composed of terms that highly co-occur with one another. Once this semantic index is formed, one can extract relevant documents related to these topics and further refine their contents through a summarization process that allows users to search for phrases that are relevant to them within the corpus. The goal of Refinery is to make this whole process easier and to provide some of the latest scalable versions of these learning algorithms in an intuitive web-based interface. Refinery is also meant to be run locally, thus bypassing the need for securing document collections over the internet. The talk will go through some of the technologies involved and a demo of the app.&lt;br /&gt;
&lt;br /&gt;
For more info check out http://www.docrefinery.org.&lt;br /&gt;
&lt;br /&gt;
==Drupal 8 — Evolution &amp;amp; Revolution==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Drupal 8 is in beta and nearing release. Among its many features, it notably has become more developer friendly through its adoption of the Symfony PHP framework along with Symfony's outstanding set of libraries (like Guzzle) and tools (like Composer). And, in implementing the Twig theming system, it is can begin to escape PHPtemplate. These moves also make it easier to create headless systems that uses Angular.js and other systems for presentation, or even forgo presentation entirely.&lt;br /&gt;
&lt;br /&gt;
From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.&lt;br /&gt;
&lt;br /&gt;
==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==&lt;br /&gt;
 &lt;br /&gt;
* [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]],  stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]&lt;br /&gt;
&lt;br /&gt;
GameSalad is a popular tool for developing mobile and desktop games with little actual programming. In this presentation, Stan Bogdanov breaks down the development process he followed while building [https://github.com/stanrb/mobiLit mobiLit], a mobile app with the goal of being the first open-source gamified information literacy app to be used as part of a college-level information literacy curriculum. He will go through the basics of using GameSalad to create an app that can be easily customized by non-programmers and the instructional principles used to teach the material in a mobile medium. Stan will also go through two qualitative design studies he did on the app and discuss their results and the lessons learned from building mobiLit. The session will conclude with an overview of the next steps for the [https://github.com/stanrb/mobiLit mobiLit project].&lt;br /&gt;
&lt;br /&gt;
==The Impossible Search: Pulling data from multiple unknown sources==&lt;br /&gt;
 &lt;br /&gt;
* Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com &lt;br /&gt;
&lt;br /&gt;
It's easy to search data you know the structure of, but what if you need to pull in data from sources that don't have a standard structure. The ability to search community events along with your standard catalog search results is an example, but often the only way to pull these events is through XML, JSON, (Insert structured format here), or even just raw html. But how do you get that structure? That simple question is what makes this impossible. The process to define and process this structure takes a lot of manual labor, especially if the data you are pulling is just HTML, and then every time you add data to the index you have to run all the data through a script to pull in data in a format Solr or an other index can use. This talk will focus on Solr, but the principles explained will apply to many other indexes.&lt;br /&gt;
&lt;br /&gt;
==What! You're Not Using Docker?==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Boring part: Docker[1] is a container system that provides benefits similar to virtualization with only a fraction of the overhead. Scintillating part: Docker can host between four to six times the number of service instances than systems such as Xen or VMWare on a given piece of hardware. But thats not all! Docker also makes it simple(r) to create transportable instances, so you can spin up development servers on your laptop.&lt;br /&gt;
&lt;br /&gt;
*[1]https://www.docker.com/&lt;br /&gt;
&lt;br /&gt;
== Video Accessibility, WebVTT, and Timed Text Track Tricks ==&lt;br /&gt;
&lt;br /&gt;
* Jason Ronallo, jronallo@gmail.com, NCSU Libraries&lt;br /&gt;
&lt;br /&gt;
Video on the Web presents new challenges and opportunities. How do you make your video more accessible to those with various disabilities and needs? I'll show you how. This presentation will focus on how to write and deliver captions, subtitles, audio descriptions, and timed metadata tracks for Web video using the WebVTT W3C standard. Encoding timed text tracks in this way opens up opportunities for new functionality on your websites beyond accessibility. The presentation will show some examples of the potential for using timed text tracks in creative ways. I'll cover all the HTML and JavaScript you will need to know as well as some of the CSS and other bits you could probably do without but are too fun to pass up.&lt;br /&gt;
&lt;br /&gt;
== Categorizing Records with Random Forests ==&lt;br /&gt;
 &lt;br /&gt;
* Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library&lt;br /&gt;
Academic libraries are increasingly responsible for providing ingest, search, discovery, and analysis for data sets.  Emerging techniques from data science and machine learning can provide librarians and developers with an opportunity to generate new insights and services from these document collections.  This presentation will provide a brief overview of common machine learning classification techniques, then dive into a more detailed example using a random forest to assign keywords to research data sets.  The talk will emphasize the insight that can be gained from machine learning rather than the inner workings of the algorithms.  The overall goal of this presentation is to provide librarians and developers with the context to recognize an opportunity to apply machine learning categorization techniques at their home campuses and organizations.  &lt;br /&gt;
&lt;br /&gt;
== Data Science in Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Devon Smith, smithde@oclc.org, OCLC&lt;br /&gt;
&lt;br /&gt;
Data Science is increasing in buzz and hype. I'll go over what it is, what it isn't, and how it fits in libraries.&lt;br /&gt;
&lt;br /&gt;
== PDF metadata extraction for academic literature == &lt;br /&gt;
&lt;br /&gt;
* Kevin Savage, kevin.savage at mendeley.com, Mendeley&lt;br /&gt;
* Joyce Stack, joyce.stack at mendeley.com, Mendeley&lt;br /&gt;
&lt;br /&gt;
Mendeley recently added a, &amp;quot;document from file,&amp;quot; endpoint to its API which attempts to extract metadata such as title and authors directly from PDF files. This talk will describe at a high level the machine learning methods we used including how we measured and tuned our model. We will then delve more deeply into our stack, the tools we used, some of the things that didn't work and why PDFs are the worst thing ever to compute over.&lt;br /&gt;
&lt;br /&gt;
== Giving Users What They Want: Record Grouping in VuFind ==&lt;br /&gt;
 &lt;br /&gt;
* Mark Noble,  mark@marmot.org, [//www.marmot.org Marmot Library Network]&lt;br /&gt;
&lt;br /&gt;
In 2013, Marmot did extensive usability studies with patrons to determine what was difficult in the catalog.  Many patrons had problems sifting through all of the various formats and editions of a title.  In 2014 we developed a method for [//mercury.marmot.org/Union/Search?lookfor=divergent grouping records] so only a single work is shown in search results and all formats and editions are listed under that work.  We will discuss our definition of a 'work' based on FRBR principles; combining meta data from MARC records with metadata from other sources like OverDrive; the technical details of Record Grouping; the design decisions made during implementation; and the reaction from users and staff.&lt;br /&gt;
&lt;br /&gt;
== Topic Space: a mobile augmented reality recommendation app ==&lt;br /&gt;
&lt;br /&gt;
* Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign&lt;br /&gt;
&lt;br /&gt;
The Topic Space module (http://minrvaproject.org/modules_topicspace.php ) was developed with an IMLS Sparks! Grant to investigate augmented reality technologies for in-library recommendations. The funding allowed for sustained university community collaboration by the University Library, the Graduate School of Library and Information Science, as well as graduate student programmers sourced from the Department of Computer Science. Collaborators designed app functionality and identified relevant open source libraries that could power optical character recognition (OCR) functionality from within the mobile phone.&lt;br /&gt;
&lt;br /&gt;
Topic space allows a user to take a picture of an item's call number in the book stacks. The module will show the user other books that are relevant but that are not shelved nearby. It can also show users books that are normally shelved here but that are currently checked out. Recommendations are based on Library of Congress subject headings and ILS circulation data which indicate recommendation candidates based on total check-outs. &lt;br /&gt;
&lt;br /&gt;
Research questions included development of back end (server-side) pattern matching algorithms for recommendations, and a rapid formative evaluation of interface design that would provide optimal user experience for navigation of the book stacks as a context to recommendations.&lt;br /&gt;
&lt;br /&gt;
Along with the Topic Space native app, grant collaborators prototyped web based recommendations which could serve as a new way of providing readers advisory and “more like this” recommendations from discovery interfaces accessed through desktop browsers. Outcomes of the grant include the availability of the [https://play.google.com/store/apps/details?id=edu.illinois.ugl.minrva Topic Spaces module within Minrva app on the Android Play store] and an experimental [http://backbonejs.org/ Backbone.js] based [http://minrva-dev.library.illinois.edu Topic Space web app].&lt;br /&gt;
&lt;br /&gt;
== Leveling Up Your Git Workflow ==&lt;br /&gt;
&lt;br /&gt;
* Megan Kudzia, moneill@albion.edu, Albion College Library&lt;br /&gt;
* Kate Sears, eks11@albion.edu, Albion College Library&lt;br /&gt;
&lt;br /&gt;
Have you started experimenting with Git on your own, but now you need to include others in your projects? Learn from our mistakes! Transitioning from a one-person git workflow and repo structure, to a structure that includes multiple people (including student workers), is not for the faint of heart. We'll talk about why we decided to work this way, our path to developing a git culture amongst ourselves, conceptual and technical difficulties we've faced, what we learned, and where we are now. Also with pretty pictures (aka workflow drawings).&lt;br /&gt;
&lt;br /&gt;
== Drone Loaning Program: Because Laptops are so last century ==&lt;br /&gt;
&lt;br /&gt;
 * Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries&lt;br /&gt;
 * Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries&lt;br /&gt;
&lt;br /&gt;
At Univ. Maryland we are in the very early stages of looking into allowing our student body get their hands on a drone. Yes that's right we will let students take out a drone for n amount of hours to work on projects of their choosing. The talk will talk about the logistics of getting a program of this sort from concept to &amp;quot;Is the drone available?&amp;quot;. If people sign waivers we will also promise not to crash the drone into code4lib attendees.&lt;br /&gt;
&lt;br /&gt;
== Got Git? Getting More Out of Your GitHub Repositories ==&lt;br /&gt;
&lt;br /&gt;
 * Terry Brady, twb27@georgetown.edu, Georgetown University Library&lt;br /&gt;
&lt;br /&gt;
This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories. &lt;br /&gt;
&lt;br /&gt;
In additional to all of the great benefits of using Git for code management, the GitHub interface provides a powerful set of tools to showcase a project and to keep your users informed of developments to your project.  These tools can assist with marketing and outreach - turning your code repository into a focus of conversation!&lt;br /&gt;
&lt;br /&gt;
* [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]&lt;br /&gt;
* [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]&lt;br /&gt;
* [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]&lt;br /&gt;
* [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]&lt;br /&gt;
* Gists for code sharing&lt;br /&gt;
* Private Repositories and Organizational Groups&lt;br /&gt;
* Pull Request Conversation Tracking&lt;br /&gt;
* Customized Issue management&lt;br /&gt;
&lt;br /&gt;
== Quick Wins for Every Department in the Library - File Analyzer! ==&lt;br /&gt;
&lt;br /&gt;
 * Terry Brady, twb27@georgetown.edu, Georgetown University Library&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.&lt;br /&gt;
* Analyzing Marc Records for the Cataloging department&lt;br /&gt;
* Transferring ILS invoices for the University Account System for the Acquisitions department &lt;br /&gt;
* Delivering patron fines to the Bursar’s office for the Access Service department&lt;br /&gt;
* Summarizing student worker timesheet data for the Finance department&lt;br /&gt;
* Validating COUNTER compliant reports for the Electronic Resources department&lt;br /&gt;
* Generating ingest packages for the Digital Services department&lt;br /&gt;
* Validating checksums for the Preservation department&lt;br /&gt;
&lt;br /&gt;
Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!&lt;br /&gt;
&lt;br /&gt;
==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor&lt;br /&gt;
&lt;br /&gt;
The transition from paper maps to digital ones changed much more than the maps themselves; it changed the very foundation of how we work and how we find each other. Now maps are transforming again.  The Geospatial World is moving from GIS systems that are institutionally-focused, expensive, feature-burdened, and binds data into a complicated and demanding user-hostile interface. From this transition from digital to web-based digital geospatial tools has come growth and development in new forms of map-based investigative journalism, activism, scholarship, and business ventures. This talk will highlight the conditions and strategies that made these changes possible as a means to draw a path by which librarians through our own work may follow, dragons notwithstanding. &lt;br /&gt;
&lt;br /&gt;
== Building Your Own Federated Search ==&lt;br /&gt;
&lt;br /&gt;
* Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco&lt;br /&gt;
&lt;br /&gt;
Advances in modern browsers have created some interesting possibilities for federated search. This presentation will cover common techniques and pitfalls in building a federated search. We will discuss what principles guided our decisions when implementing our own federated search. We will show tools we've built and our findings from building and using experimental prototypes.&lt;br /&gt;
&lt;br /&gt;
Your higher education institution likely offers dozens of online resources for educators, students, researchers, and the public. And each of these online resources likely has its own search tool. But users can't be expected to search in dozens of different interfaces to find what they're looking for. A typical solution for this issue is federated search. &lt;br /&gt;
&lt;br /&gt;
==  Indexing Linked Data with LDPath ==&lt;br /&gt;
&lt;br /&gt;
* Chris Beer, cabeer@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
LDPath [1] is a simple query language for indexing linked open data, with support for caching, content negotiation, and integration with non-RDF endpoints. This talk will demonstrate the features and potential of the language and framework to index a resource with links into id.loc.gov, viaf.org, geonames.org, etc to build an application-ready document.&lt;br /&gt;
&lt;br /&gt;
[1] http://marmotta.apache.org/ldpath/language.html&lt;br /&gt;
&lt;br /&gt;
== Show Me the Money: Integrating an LMS with Payment Providers ==&lt;br /&gt;
 &lt;br /&gt;
* Josh Weisman,  Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group&lt;br /&gt;
&lt;br /&gt;
In order to provide an easy and convenient way for patrons to pay fines, we are exploring ways to integrate the library management system with online payment providers such as PayPal. With many LMS systems being designed and developed for the cloud, we should be able to provide the frictionless user experience our patrons have come to expect from online transactions. In this session we'll discuss strategies for integration and review a sample application which uses REST APIs from a library management system to integrate with PayPal.&lt;br /&gt;
&lt;br /&gt;
== Shibboleth Federated Authentication for Library Applications: ==&lt;br /&gt;
&lt;br /&gt;
* Scott Fisher, scott.fisher@ucop.edu, California Digital Library&lt;br /&gt;
* Ken Weiss, ken.weiss@ucop.edu, California Digital Library&lt;br /&gt;
&lt;br /&gt;
Shibboleth is the most widely-used method to provide single-sign-on authentication to academic applications where users come from many different institutions. Shibboleth, the InCommon education and research trust framework, and the SAML protocol comprise a very powerful - but very complicated - solution to this very complicated problem. Scott and Ken have implemented Shibboleth for multiple library applications. They will share their understanding of the good, the bad, and the underlying spaghetti that makes it all work. Ken will discuss some of the technical aspects of the solution, touching on optimal and non-optimal use cases, administrative challenges, and authorization concerns. Scott will describe the implementation pattern for multi-institution single-sign-on that the California Digital Library has evolved, using the recently released Dash application (http://dash.cdlib.org) as an example.&lt;br /&gt;
&lt;br /&gt;
==Scientific Data: A Needs Assessment Journey==&lt;br /&gt;
 &lt;br /&gt;
*[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History&lt;br /&gt;
&lt;br /&gt;
While surveying digital research and collections data in the research science divisions at the American Museum of Natural History in NYC (as a part of my [http://ndsr.nycdigital.org/ National Digital Stewardship Residency] project), I have come across the big data hogs (genome sequencing and CT scanning) and the little pieces of data (images, publications), all equally important to not only scientific discovery, but as nodes in the history of science. &lt;br /&gt;
&lt;br /&gt;
In this session, I will discuss the development of my needs assessment surveys for scientific datasets and the interview process with Museum curators and researchers as background, seguing into an explanation of the results. I will then combine my findings into preliminary selection criteria to choose tools for digital preservation and management unique to scientific datasets. This will brooke a discussion on emerging standards, tools, and technologies in big data, specific to research science. &lt;br /&gt;
&lt;br /&gt;
I will conclude with preliminary findings on emerging technology that can be used to answer concerns surrounding the management and digital preservation of these data. I am hoping the Q&amp;amp;A session can be used to both answer questions about my project, and function as a way for you (the larger tech-savy library community)  to discuss the tools I’ve touched on in this talk. &lt;br /&gt;
&lt;br /&gt;
== Feminist Human Computer Interaction (HCI) in Library Software ==&lt;br /&gt;
 &lt;br /&gt;
* Bess Sadler,  bess@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
Libraries are not neutral repositories of knowledge. Library classification systems and search technologies tend to reflect the inequalities, biases, ethnocentrism, and power imbalances of the societies in which they are built [1]. How might we better resist these tendencies in the library software we create? This talk will examine some qualities of feminist HCI (pluralism, self-disclosure, participation, ecology, advocacy, and embodiment) [2] through the lens of library software. &lt;br /&gt;
&lt;br /&gt;
[1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.&lt;br /&gt;
&lt;br /&gt;
[2] Bardzell, Shaowen. Feminist HCI: Taking Stock and Outlining an Agenda for Design. CHI 2010: HCI For All. http://dmrussell.net/CHI2010/docs/p1301.pdf&lt;br /&gt;
&lt;br /&gt;
== Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==&lt;br /&gt;
&lt;br /&gt;
* Audrey Altman, audrey at dp.la, Digital Public Library of America&lt;br /&gt;
* Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America&lt;br /&gt;
* Mark Breedlove, mb at dp.la, Digital Public Library of America&lt;br /&gt;
&lt;br /&gt;
The Digital Public Library of America aggregates metadata for over 8 million objects from more than 24 direct partners, or Hubs, using its Metadata Application Profile (MAP), an RDF metadata application profile based on the Europeana Data Model. After working with the initial system for harvesting, mapping and enhancing our Hub’s metadata for a year, we realized that it was inadequate for working with data at this scale. There were architectural issues; it was opaque to non-developer and partner staff; there were inadequate tools for quality assurance and analysis; and the system was unaware that it was working with RDF data. As the network of Hubs expanded and we ingested more metadata, it became harder and harder to know when or why a harvest, a mapping task, or an enrichment went wrong because the tools for quality assurance were largely inadequate. &lt;br /&gt;
&lt;br /&gt;
The DPLA Content and Technology teams decided to develop a new system from the ground up to address those problems. Development of Heidrun, the internal version of the new system, started in October 2014. Heidrun’s goals are to make it easier for us to harvest and map metadata from various sources and in variety of schemas to the DPLA MAP, to better enrich that metadata using external data sources, and to actively involve our partners in the ingestion process through access to better QA tools. Heidrun and its componentry are built on Ruby on Rails, Blacklight, and ActiveTriples. Our presentation will give some background on our design principles and processes used during development, the architecture of the system, and its functionality. We plan to release a version of Heidrun and its components as a generalized metadata aggregation system for use by DPLA Hubs and others working to aggregate cultural heritage metadata.&lt;br /&gt;
&lt;br /&gt;
== OS or GTFO: Program or Perish ==&lt;br /&gt;
*Tessa Fallon, tessa.fallon@gmail.com&lt;br /&gt;
&lt;br /&gt;
Description TBD&lt;br /&gt;
&lt;br /&gt;
== Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==&lt;br /&gt;
* Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries&lt;br /&gt;
Would your library like to have large digital signage that displays dynamic information such as library hours, weather, room availability, and more? Have you looked into purchasing large digital signage, only to be turned off by the high price tag and lack of customization available with commercial solutions? Our library has developed a cheap and effective alternative to these systems using HTML 5 authoring software, a large TV, and freely-available APIs from Google, Springshare, and others. At this session, you’ll learn about the system that we have in place for displaying dynamic and easily-updatable information on our library’s large digital display, and how you can easily create something similar for your library.&lt;br /&gt;
&lt;br /&gt;
== REPOX: Metadata Blender ==&lt;br /&gt;
 &lt;br /&gt;
* John Mignault, jmignault@metro.org, Empire State Digital Network&lt;br /&gt;
&lt;br /&gt;
With the growth in the number of hubs providing metadata to the Digital Public Library of America, many of them are using REPOX, a tool originally created for the Europeana project, to aggregate disparate metadata feeds and transform them into formats suitable for ingest into DPLA. The Empire State Digital Network, the forthcoming DPLA service hub for NY state, is using it to prepare for our first ingest into DPLA in early 2015.  We'll take a look at REPOX and its capabilities and how it can be useful for ingesting and transforming metadata, and also discuss some things we've learned in massaging widely varied metadata feeds.&lt;br /&gt;
&lt;br /&gt;
== Beyond Open Source ==&lt;br /&gt;
&lt;br /&gt;
* Jason Casden, jmcasden@ncsu.edu, NCSU Libraries&lt;br /&gt;
* Bret Davidson, bddavids@ncsu.edu, NCSU Libraries&lt;br /&gt;
&lt;br /&gt;
The Code4Lib community has produced an increasingly impressive collection of open source software over the last decade, but much of this creative work remains out of reach for large portions of the library community. Do the relatively privileged institutions represented by a majority of Code4Lib participants have a professional responsibility to support the adoption of their innovations?&lt;br /&gt;
&lt;br /&gt;
Drawing from old and new software packaging and distribution approaches (from freeware to Docker), we will propose extending the open source software values of collaboration and transparency to include the wide and affordable distribution of software. We believe this will not only simplify the process of sharing our applications within the Code4Lib community, but also make it possible for less well resourced institutions to actually use our software. We will identify areas of need, present our experiences with the users of our own open source projects, discuss our attempts to go beyond open source, and make an argument for the internal value of supporting and encouraging a vibrant library ecosystem.&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]] &lt;br /&gt;
[[Category:Talk Proposals]]&lt;br /&gt;
&lt;br /&gt;
== Making It Work: Problem Solving Using Open Source at a Small Academic Library ==&lt;br /&gt;
 &lt;br /&gt;
* Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology&lt;br /&gt;
* Max King, mking9@iit.edu, Illinois Institute of Technology&lt;br /&gt;
&lt;br /&gt;
The Illinois Institute of Technology campus was added to the National Register of Historic Places in 2005, and contains a building, Mies van der Rohe's S.R. Crown Hall, that was named a National Historic Landmark in 2001. Creating a digital resource that can adequately showcase the campus and its architecture is challenge enough in and of itself, but doing so as a two-person team of relative newcomers, at a university library without dedicated programmers on staff, ups the ante considerably.&lt;br /&gt;
The challenges of technical know-how, staff time, and funding are nothing new to anyone working on digital projects at a university library, and are amplified when doing so at a smaller institution. This talk covers the conception, development, and design of the campus map site that was built, concentrating on the problem-solving strategies developed to cope with limited technical and financial resources.&lt;br /&gt;
We'll talk about our approach to development with Open Source software, including Omeka, along with the Neatline and Simile Timeline plugins. We'll also discuss the juggling act of designing for mobile mapping functionality without sacrificing desktop design, weighing the costs of increased functionality versus our ability to time-effectively include that functionality, and the challenge of building a site that could be developed iteratively, with an eye towards future enhancement and sustainability. Finally, we’ll provide recommendations for other librarians at smaller institutions for their own efforts at digital development.&lt;br /&gt;
&lt;br /&gt;
== Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==&lt;br /&gt;
 &lt;br /&gt;
* Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art&lt;br /&gt;
&lt;br /&gt;
The Museum of Modern Art has amassed a large collection of audiovisual materials over its many decades of existence. In order to preserve these materials, much of the audiovisual collection has been digitized. This is a complex process involving numerous steps and devices, and the methods used for digitization can have an effect on the quality of the file that is preserved. Therefore, knowing exactly how something was digitized is critical for future stewards of these objects to be able to properly care for and preserve them. However, detailed technical information about the processes involved in the digitization of audiovisual materials is not defined explicitly in most metadata schemas used for audiovisual materials. In order to record process history using existing metadata standards, some level of creativity is required to allow existing standards to express this information.&lt;br /&gt;
&lt;br /&gt;
This talk will detail different metadata standards, including PBCore, PREMIS, and reVTMD, that can be implemented as methods of recording this information. Specifically, the talk will examine efforts to integrate this metadata into the Museum of Modern Art’s new digital repository, the DRMC. This talk will provide background on the DRMC as well as MoMA’s specific institutional needs for process history metadata, then discuss different metadata implementations we have considered to document process history.&lt;br /&gt;
&lt;br /&gt;
== Pig Kisses Elephant: Building Research Data Services for Web Archives ==&lt;br /&gt;
 &lt;br /&gt;
* Jefferson Bailey,  jefferson@archive.org, Internet Archive&lt;br /&gt;
* Vinay Goel, vinay@archive.org, Internet Archive&lt;br /&gt;
&lt;br /&gt;
More and more libraries and archives are creating web archiving programs.  For both new and established programs, these archives can consist of hundreds of thousands, if not millions, of born-digital resources within a single collection; as such, they are ideally suited for large-scale computational study and analysis. Yet current access methods for web archives consist largely of browsing the archived web in the same manner as browsing the live web and the size of these collections and complexity of the WARC format can make aggregate analysis difficult. This talk will describe a project to create new ways for users and researchers to access and study web archives by offering extracted and post-processed datasets derived from web collections. Working with the 325+ institutions and their 2600+ collections within the Archive-It service, the Internet Archive is building methods to deliver a variety of datasets culled from collections of web content, including extracted metadata packaged in JSON, longitudinal link graph data, named entities, and other types of data. The talk will cover the technical details of building dataset production pipelines with Apache Pig, Hadoop, and tools like Stanford NER, the programmatic aspects of building data services for archives and researchers, and ongoing work to create new ways to access and study web archives.&lt;br /&gt;
&lt;br /&gt;
== Awesome Pi, LOL! ==&lt;br /&gt;
&lt;br /&gt;
* Matt Connolly, mconnolly@cornell.edu, Cornell University Library&lt;br /&gt;
* Jennifer Colt, jrc88@cornell.edu, Cornell University Library&lt;br /&gt;
&lt;br /&gt;
Inspired by Harvard Library Lab’s “Awesome Box” project, Cornell’s Library Outside the Library (LOL) group is piloting a more automated approach to letting our users tell us which materials they find particularly stunning. Armed with a Raspberry Pi, a barcode scanner, and some bits of kit that flash and glow, we have ventured into the foreign world of hardware development. This talk will discuss what it’s like for software developers and designers to get their hands dirty, how patrons are reacting to the Awesomizer, and LOL’s not-afraid-to-fail philosophy of experimentation.&lt;br /&gt;
&lt;br /&gt;
== You Gotta Keep 'em Separated: The Case for &amp;quot;Bento Box&amp;quot; Discovery Interfaces ==&lt;br /&gt;
 &lt;br /&gt;
* Jason Thomale,  jason.thomale@unt.edu, University of North Texas Libraries&lt;br /&gt;
&lt;br /&gt;
I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.&lt;br /&gt;
&lt;br /&gt;
The thing is, practically all of us--in academic libraries at least--have a similar set up for discovery, with just a few variations, and so talking about it still seems useful. Stop me if this sounds familiar. You've got a single search box on the library homepage as a starting point for discovery. And it's probably a tabbed affair, with an option for searching the catalog for books, an option for searching a discovery service for articles, an option for searching databases, and maybe a few others. Maybe you have an option to search everything at once--probably the default, if you have it. And, if you're a crazy hepcat, maybe you ''only'' have your one search that searches everything, with no tabs.&lt;br /&gt;
&lt;br /&gt;
Now, the question is, for your &amp;quot;everything&amp;quot; search, are you doing a combined list of results, or are you doing it bento-box style, with a short results list from each category displayed in its own compartment?&lt;br /&gt;
&lt;br /&gt;
At UNT, we've been holding off on implementing an &amp;quot;everything&amp;quot; search, for various reasons. One reason is that the evidence for either style hasn't been very clear. There's this persistent paradox that we just can't reconcile: users tell us, through word and action, that they prefer searching Google, yet, libraries aren't Google, and there are valid design reasons why we shouldn't try to oversimplify our discovery interfaces to be like Google. And there's user data that supports both sides.&lt;br /&gt;
&lt;br /&gt;
Holding off on making this decision has granted us 2 years of data on how people use our tabbed search interface that does ''not'' include an &amp;quot;everything&amp;quot; search. Recently I conducted a thorough analysis of this data--specifically the usage and query data for our catalog and discovery system (Summon). And I think it helps make the case for a bento box style discovery interface. To be clear, it isn't exactly the smoking gun that I was hoping for, but the picture it paints I think is telling. At the very least, it points away from a combined-results approach.&lt;br /&gt;
&lt;br /&gt;
I'm proposing a talk discussing the data we've collected, the trends we've seen, and what I think it all means--plus other reasons that we're jumping on the &amp;quot;bento box&amp;quot; discovery bandwagon and why I think &amp;quot;bento box&amp;quot; is at this point the path that least sells our souls.&lt;br /&gt;
&lt;br /&gt;
== Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift ==&lt;br /&gt;
 &lt;br /&gt;
* Ashley Blewer!, ashley.blewer@gmail.com&lt;br /&gt;
&lt;br /&gt;
Checksum technology is used all over the place, from git commits to authenticating Linux packages. It is most commonly used in the digital preservation field to monitor materials in storage for changes that will occur over time or used in the transmission of files during duplication. But do you even checksum, bro? I want this talk to move checksums from a position of mysterious macho jargon to something everyone can understand and want to use. I think a lot of people have heard of checksum but don’t know where to begin when it comes to actually using it at their institution. And cryptography is hella intimidating! This talk will cover what checksums are, how they can be integrated into a library or archival workflow, protecting collections requiring additional levels of security, algorithms used to verify file fixity and how they are different, and other aspects of cryptographic technology. Oh, and please note that all points in this talk will be emphasized or lightly performed through Taylor Swift lyrics. Seriously, this talk will consist of at least 50% Taylor Swift. Can you, like, even?&lt;br /&gt;
&lt;br /&gt;
== Level Up Your Coding with Code Club (yes, you can talk about it) ==&lt;br /&gt;
&lt;br /&gt;
* Coral Sheldon-Hess, coral@sheldon-hess.org&lt;br /&gt;
&lt;br /&gt;
Reading code is a necessary part of becoming a better developer. It gives you more experience and more insight into How Things Are (or Aren't) Done; it builds your intuition about how to solve problems with code; and it increases your confidence that you, too, can tackle whatever technological problems you're facing.&lt;br /&gt;
&lt;br /&gt;
But you don't have to read code alone! (Which is good. It's really not fun to read code alone.) &lt;br /&gt;
&lt;br /&gt;
In late 2014, a group of librarians formed two Code Clubs, inspired by [http://bloggytoons.com/code-club/ this talk by Saron] (of Bloggytoons fame). I'd like to tell you about how we've structured our Code Clubs, what has gone well, what we've learned, and what you need to do to form your own Code Club. I'll share a list of the codebases we've looked at, too, to help you get your own Code Club off the ground! &lt;br /&gt;
&lt;br /&gt;
== The Growth of a Programmer ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:jgo | Joshua Gomez]], Getty Research Institute, jgomez@getty.edu&lt;br /&gt;
&lt;br /&gt;
Just like other creative endeavors, software developers can experience periods of great productivity or find themselves in a rut. After contemplating the alternating periods in my own career I've noticed several factors that have effected my own professional growth and happiness, including: mentorship, structure, community, teamwork, environment, formal education, etc. Not all of the factors need to be present at all times; but some mixture of them is critical for continued growth. In this talk, I will articulate these factors, discuss how they can effect a developer's career, and how they can be sought out when missing. This talk is aimed at both new developers looking to strike their own path as well as the veterans that lead or mentor them.&lt;br /&gt;
&lt;br /&gt;
== Developing a Fedora 4.0 Content Model for Disk Images ==&lt;br /&gt;
&lt;br /&gt;
* Matthew Farrell, matthew.j.farrell@duke.edu, Duke University Libraries&lt;br /&gt;
* Alexandra Chassanoff, achass@email.unc.edu, BitCurator Access Project Manager&lt;br /&gt;
&lt;br /&gt;
As the acquisition of born-digital materials grows, institutions are seeking methods to facilitate easy ingest into their repositories and provide access to disk images and files derived or extracted from disk images. In this session, we describe our development of a Fedora 4.0 Content model for disk images, including acceptable image file formats and the rationale behind those choices.  We will also discuss efforts to integrate the disk image content model into the BitCurator Access environment. Unlike generalized, format-agnostic content models which might treat the disk image as a generic bitstream, a content model designed for disk images enables expression of relationships among associated content in the collection such as files extracted from images and other born-digital and digitized material associated with the same creator.  It also enables capture of file-system attributes such as file paths, timestamps, whether files are allocated/deleted, etc.  Further, a disk image content model suggests further steps repositories can take in order to transform and re-use associated metadata generated during the creation and forensic analysis of the disk image.&lt;br /&gt;
&lt;br /&gt;
== Data acquisition and publishing tools in R ==&lt;br /&gt;
&lt;br /&gt;
* Scott Chamberlain,  scott@ropensci.org, rOpenSci/UC Berkeley - first-time presenter&lt;br /&gt;
&lt;br /&gt;
R is an open source programming environment that is widely used among researchers in many fields. R is powerful because it's free, increasingly robust, and facilitates reproducible research, an increasingly sought after goal in academia. Although tools for data manipulation/visualization/analysis are well developed in R, data acquisition and publishing tools are not. rOpenSci is a collaborative effort to create the tools necessary to complete the reproducible research workflow. This presentation discusses the need for these tools, including examples, including interacting with the repositories Mendeley, Dryad, DataONE, and Figshare. In addition, we are building tools for searching scholarly metadata and acuiring full text of open access articles in a standarized way across metadata providers (e.g., Crossref, DataCite, DPLA) and publishers (e.g., PLOS, PeerJ, BMC, Pubmed). Last, we are building out tools for data reading and writing in Ecologial Metadata Language (EML).&lt;br /&gt;
&lt;br /&gt;
== SPLUNK: Log File Analysis ==&lt;br /&gt;
&lt;br /&gt;
* Jim LeFager, jlefager@depaul.edu, DePaul University Library&lt;br /&gt;
DePaul University Library recently took over monitoring and maintaining of the library EZproxy servers this past year and using Splunk, a machine data analysis tool, we are able to gather information and statistics on our electronic resource usage in addition to monitoring the servers. Splunk is a tool that can collect, analyze, and visualize log files and other machine data in real time and this has allowed for gathering realtime usage statistics for our electronic resources allowing us to filter by multiple facets including IP Range, Group Membership (student, faculty), so that we can see who is accessing our resources and from where. Splunk allows our library to query our data and create rich custom dashboards as well as create alerts that can be triggered when certain conditions are met, such as error codes, which can send an email alert to a group of users. We will be leveraging Splunk to monitor all library web applications going forward. This talk will review setting up Splunk and best practices in using the available features and customizations available including creating queries, alerts, and custom dashboards.  &lt;br /&gt;
&lt;br /&gt;
== Your code does not exist in a vacuum ==&lt;br /&gt;
* Becky Yoose, yoosebec at grinnell dot edu, Grinnell College (Done a lightning talk, MC duties, but have not presented a prepared talk)&lt;br /&gt;
&lt;br /&gt;
“If you have something to say, then say it in code…” - Sebastian Hammer, code4lib 2009&lt;br /&gt;
&lt;br /&gt;
In its 10 year run, code4lib has covered the spectrum of libtech development, from search to repositories to interfaces. However, during this time there has been little discussion about this one little fact about development - code does not exist in a vacuum. &lt;br /&gt;
&lt;br /&gt;
Like the comment above, code has something to say. A person’s or organization’s culture and beliefs influences code in all steps of the development cycle. What development method you use, tools, programming languages, licenses - everything is interconnected with and influenced by the philosophies, economics, social structures, and cultural beliefs of the developer and their organization/community.&lt;br /&gt;
&lt;br /&gt;
This talk will discuss these interconnections and influences when one develops code for libraries, focusing on several development practices (such as “Fail Fast, Fail Often” and Agile)   and licensing choices (such as open source) that libtech has either tried to model or incorporate into mainstream libtech practices. It’ll only scratch the surface of the many influences present in libtech development, but it will give folks a starting point to further investigate these connections at their own organizations and as a community as a whole.&lt;br /&gt;
&lt;br /&gt;
tl;dr - this will be a messy theoretical talk about technology and libraries. No shiny code slides, no live demos. You might come out of this talk feeling uncomfortable. Your code does not exist in a vacuum. Then again, you don’t exist in a vacuum either.&lt;br /&gt;
&lt;br /&gt;
== The Metadata Hopper: Mapping and Merging Metadata Standards for Simple, User-Friendly Access ==&lt;br /&gt;
&lt;br /&gt;
* Tracy Seneca, tjseneca@uic.edu, University of Illinois at Chicago&lt;br /&gt;
* Esther Verreau: verreau1@uic.edu, University of Illinois at Chicago&lt;br /&gt;
&lt;br /&gt;
The Chicago Collections Consortium: 15 institutions and growing!  8 distinct EAD standards! At least 3 permutations of MARC, and we lost count of the varieties of custom CONTENTdm image collections.  Not to mention the 14,730 unique subject terms, nearly all of which lead our poor end-users to exactly one organization's content. &lt;br /&gt;
&lt;br /&gt;
All large content aggregation projects have faced this challenge, and there are a few emerging tools to help us wrangle disparate metadata into new contexts.  The Metadata Hopper is one such tool. The Metadata Hopper enables archivists to map their local metadata standards to standardized deposit records, and tags those materials using a shared vocabulary, integrating them into a user-friendly portal without disrupting local practices. In last year's Code4Lib lightning talk we described the challenges that the Chicago Collections Consortium faces in creating shared, in-depth access to archival and digital collections about Chicago history and culture across CCC member organizations. This year, thanks to the Andrew W. Mellon Foundation, we have a working Django application to demonstrate.  In this talk we'll discuss the design that enables multiple layers of flexibility, from the ability to accept a variety of metadata standards to designing for an open source audience.&lt;br /&gt;
&lt;br /&gt;
http://chicagocollectionsconsortium.org&lt;br /&gt;
&lt;br /&gt;
== Programmers are not projects: lessons learned from managing humans ==&lt;br /&gt;
&lt;br /&gt;
* Erin White, erwhite@vcu.edu, Virginia Commonwealth University - first-time presenter&lt;br /&gt;
&lt;br /&gt;
Managing projects is one thing, but managing people is another. Whether we’re hired as managers or grow “organically” into management roles, sometimes technical people end up leading technical teams (gasp!). I’ll talk about lessons I’ve learned about hiring, retaining, and working long-term and day-to-day with highly tech-competent humans. I’ll also talk about navigating the politics of libraryland, juggling different types of projects, and working with constrained budgets to make good things and keep talented people engaged.&lt;br /&gt;
&lt;br /&gt;
== Practical Strategies for Picking Low-Hanging Fruits to Improve Your Library's Web Usability and UX ==&lt;br /&gt;
&lt;br /&gt;
* Bohyun Kim, bkim@hshsl.umaryland.edu, University of Maryland, Baltimore&lt;br /&gt;
&lt;br /&gt;
Have you ever tried to fix an obvious (to you at least!) problem in Web usability or UX (user experience) only to face strong resistance from the library staff? Are you a strong advocate for making library resources, systems, services, and space as usable as possible, but do you often find yourself struggling to get the point across and/or obtain the crucial buy-in from colleagues and administrators? &lt;br /&gt;
&lt;br /&gt;
There is no shortage of Web usability and UX guidelines. But applying them to a library and implementing desired changes often involve a long and slow process. To tackle this issue, this talk will focus on how to utilize the 'expert review' process (aka 'heuristic evaluation') as a preliminary or even preparatory step before embarking on more time-and-labor-intensive usability testing and user research. Several examples from  simple fixes to more nuanced usability and UX issues in libraries will be discussed to your heart's content. The goal of this talk is to provide practical strategies for picking as many low-hanging fruits as possible to make a real (albeit small) difference to your library's Web usability and UX effectively and efficiently.&lt;br /&gt;
&lt;br /&gt;
== A Semantic Makeover for CMS Data ==&lt;br /&gt;
&lt;br /&gt;
* Bill Levay, wjlevay@gmail.com, Linked Jazz Project&lt;br /&gt;
&lt;br /&gt;
How can we take semi-structured but messy metadata from a repository like CONTENTdm and transform it into rich linked data? Working with metadata from Tulane’s Hogan Jazz Archive Photography Collection, the Linked Jazz Project used Open Refine and Python scripts to tease out proper names, match them with name authority URIs, and specify FOAF relationships between musicians who appear together in photographs. Additional RDF triples were created for any dates associated with the photos, and for those images with place information we employed GeoNames URIs. Historical images and data that were siloed can now interact with other datasets, like Linked Jazz’s rich set of names and personal relationships, and can be visualized [link to come] or otherwise presented on the web in any number of ways. I have not previously presented at a Code4Lib conference.&lt;br /&gt;
&lt;br /&gt;
== Taking User Experience (UX) to new heights ==&lt;br /&gt;
 &lt;br /&gt;
* Kayne Richens, kayne.richens@deakin.edu.au, Deakin University&lt;br /&gt;
&lt;br /&gt;
User Experience, or &amp;quot;UX&amp;quot;, is for more than just websites. At Deakin University Library we're exploring ways to improve the user experience inside our campus library spaces, by putting new technologies front and centre in the overall experience for our students. How are we doing this? We’re collaborating with the University's IT department and exploring the following Library-changing opportunities:&lt;br /&gt;
&lt;br /&gt;
- Augmented Reality for Way-finding: We’re tackling that infamous thing that all Libraries can't get right – way-finding. We're enhancing library tour information and way-finding experiences by introducing augmented reality solutions.&lt;br /&gt;
 &lt;br /&gt;
- Heat mapping the library with wi-fi: We’re using our existing wi-fi infrastructure to present &amp;quot;heat maps&amp;quot; of library space utilisation, allowing our users to easily locate the space that best suits their needs, whether it be busy spaces to collaborate, or quiet spaces to study. And by overlaying computer usage and group study room bookings, users can quickly locate the space they need.&lt;br /&gt;
 &lt;br /&gt;
- Video chat library service: We’re piloting video-conferencing facilities in our group study rooms and spaces, connecting users and librarians and other professionals.&lt;br /&gt;
         &lt;br /&gt;
This talk will look at how these different technologies will be brought together to provide improved user experiences, as well some of the evidence and reasons that helped us to identify our needs, so you can too.&lt;br /&gt;
&lt;br /&gt;
==How to Hack it as a Working Parent: or, Should Your Face be Bathed in the Blue Glow of a Phone at 2 AM?==&lt;br /&gt;
&lt;br /&gt;
*Margaret Heller, Loyola University Chicago, mheller1@luc.edu&lt;br /&gt;
*Christina Salazar, California State University Channel Islands, christina.salazar@csuci.edu&lt;br /&gt;
*May Yan, Ryerson University, may.yan@ryerson.ca&lt;br /&gt;
&lt;br /&gt;
Modern technology has made it easier than ever for parents employed in technical environments to keep up with work at all hours and in all locations. This makes it possible to work a flexible schedule, but also may lead to problems with work/life balance and furthering unreasonable expectations about working hours. Add to that shifting gender roles and limited paid parental leave in the United States and you have potential for burnout and a certainty for anxiety. It raises the additioal question of whether the “always connected” mindset puts up a barrier to some populations who otherwise might be better represented in open source and library technology communities. &lt;br /&gt;
&lt;br /&gt;
This presentation will address tools that are useful for working parents in technical library positions, and share some lessons learned about using these tools while maintaining a reasonable work/life balance. We will consider a question that Karen Coyle raised back in 1996: &lt;br /&gt;
“What if the thousands of hours of graveyard shift amateur hacking wasn't really the best way to get the job done? That would be unthinkable.” &lt;br /&gt;
&lt;br /&gt;
For those who are able to take an extended parental leave, we will present strategies for minimizing the impact to your career and your employer. For those (particularly in the United States) who are only able to take a short leave will require different strategies. Despite different levels of preparation, all are useful exercises in succession planning and making a stronger workplace and future ability to work a flexible schedule through reviewing workloads, cross-training personnel, hiring contract replacements, and creative divisions of labor. Such preparation makes work better for everyone, kids or no kids.&lt;br /&gt;
&lt;br /&gt;
==Making your digital objects embeddable around the web==&lt;br /&gt;
 &lt;br /&gt;
* Jessie Keck, jkeck@stanford.edu, Stanford University Libraries&lt;br /&gt;
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
With more and more content from our digital repositories making their way into our discovery environments we quickly realize that we’re repeatedly re-inventing the wheel when it comes to creating “Viewers” for these digital objects.  With various different types of viewers necessary (books, images, audio, video, geospatial data, etc) the burden of getting these viewers into various environments (topic guides, blogs, catalogs, etc) becomes exponential.&lt;br /&gt;
&lt;br /&gt;
In this talk we’ll discuss how Stanford University Libraries implemented an oEmbed service to create an extensible viewer framework for all of its digital content. Using this service we’ve been able to easily integrate viewers into various discovery applications as well as make it easy for end users who discover our objects to easily embed customized versions into their own websites and blogs.&lt;br /&gt;
&lt;br /&gt;
==So you want to make your geospatial data discoverable==&lt;br /&gt;
 &lt;br /&gt;
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
Finding data for research or coursework can be one of the most time intensive tasks for a scholar or student. We introduce GeoBlacklight, an open source, multi-institutional software project focused on solving these common challenges at institutions across the world. GeoBlacklight prioritizes user experience, integrates with many GIS tools, and streamlines the use and organization of geospatial data. This talk will provide an introduction to the software, demonstrate current functionality, and provide a road map for future work.&lt;br /&gt;
&lt;br /&gt;
== Clueless-Driven Development: How I learned to migrate to Fedora 4 ==&lt;br /&gt;
&lt;br /&gt;
* Adam Wead, awead@psu.edu, Penn State University&lt;br /&gt;
&lt;br /&gt;
Recently I was tasked with migrating the content from our Fedora3 repository to the new Fedora4 repository architecture.&lt;br /&gt;
Despite a wealth of community support, I had no idea how to approach, or even begin to solve this problem. I knew I&lt;br /&gt;
wanted to follow best practices and use test-driven  development to build my solution, but had no idea where to start.&lt;br /&gt;
Despite this initial setback, I was able to start writing tests with only a  vague understanding of the problem. As my&lt;br /&gt;
tests exposed where my understanding of the problem was flawed, my code evolved, and within a week I had arrived  at a&lt;br /&gt;
working solution that exhibited all the hallmarks of good testing and software design.&lt;br /&gt;
&lt;br /&gt;
This talk recounts the process I went through from starting with practically nothing, to arriving at a working solution.&lt;br /&gt;
You can follow the rules of  test-driven development, but you can write tests in an expressive way to describe the&lt;br /&gt;
problem instead of just describing what the code should do. It was also essential to begin testing from an integration&lt;br /&gt;
viewpoint as opposed to a unit one, because at the outset the units were unknown and were later realized through further&lt;br /&gt;
development. For the presentation, I will be demonstrating using RSpec and Ruby. All the code examples will be related&lt;br /&gt;
to the Hydra software stack; however, I hope to show  that the processes at work will be applicable in any context.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Designing and Leading a Kick A** Tech Team ==&lt;br /&gt;
 &lt;br /&gt;
* Sibyl Schaefer,  sschaefer@rockarch.org, Rockefeller Archive Center&lt;br /&gt;
&lt;br /&gt;
New managers are often promoted without receiving management training, yet management is not something you just figure out. The experience of being expected to know how to manage, yet not being trained to do so often results in new managers feeling isolated and unsure how to move from making to managing. In this talk I’ll focus on my own managerial experience of designing and leading an archival tech team in a small independent archives. Topics covered will include hiring, delegating, creating a team culture, and leading people whose specialized knowledge exceeds your own. The talk take-aways should be applicable to managers and employees at large and small institutions alike.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==American (Archives) Horror Story: LTO Failure and Data Loss ==&lt;br /&gt;
 &lt;br /&gt;
* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH&lt;br /&gt;
* Casey Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH&lt;br /&gt;
&lt;br /&gt;
Here’s a story to send shivers down archival spines: when transferring video files off LTO for the American Archive project, WGBH got an initial failure rate of 57%.   After repeat tries, the rates improved; still, an unnervingly large percentage of files were never able to be transferred successfully.   Even more unnerving, going public with our horror story got a big response from other archives using LTO -- it seems like many institutions are having similarly scary results.   What are the real risks with LTO tape?  Are there steps that archives should be taking to better circumvent those risks?  This presentation will share information about LTO storage failures across archives world and discuss the process of investigating the problem at WGBH by testing different methods of data retrieval from LTO (direct and networked downloads, individual file retrieval and bulk data dump, use of LTO 4 and LTO 6 decks) and using checksum comparisons and file analysis and characterization tools such as ffprobe, mediainfo and exiftool to analyze failed files.  We'll also present whatever results we’ve managed to turn up by the time of Code4Lib!&lt;br /&gt;
&lt;br /&gt;
== PBCore in Action: Three Words, Not Two! ==&lt;br /&gt;
 &lt;br /&gt;
* Casey E. Davis,  casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH&lt;br /&gt;
* Andrew (Drew) Myers, andrew_myers@wgbh.org, Supervising Developer, WGBH&lt;br /&gt;
&lt;br /&gt;
In 2001, public media representatives developed the PBCore XML schema to establish a common language for managing metadata about their analog and digital audio and video. Since then, PBCore has been adopted by a number of organizations and archivists in the moving image archival community. The schema has also undergone a few revisions, but on more than one occasion it was left orphaned and with little to no support.&lt;br /&gt;
 &lt;br /&gt;
Times have changed. You may have heard the news that PBCore is back in action as part of the American Archive of Public Broadcasting initiative and via the Association of Moving Image Archivists (AMIA) PBCore Advisory Subcommittee. A group of archivists, public media stakeholders, and engaged users have come together to provide necessary support for the standard and to see to its further development.&lt;br /&gt;
 &lt;br /&gt;
At this session, we'll discuss the scope and uses of PBCore in digital preservation and access, report on the progress and goals of the PBCore Advisory Subcommittee, and share how the group (by the time of the conference) will have transformed the XML schema into an RDF ontology, bringing PBCore into the second decade of the 21st century. #PBHardcore&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Collaborating to Avert the Digital Graveyard==&lt;br /&gt;
&lt;br /&gt;
* Harish Nayak, hnayak@library.rochester.edu, University of Rochester Libraries &lt;br /&gt;
* Sean Morris, smorris@library.rochester.edu, University of Rochester Libraries &lt;br /&gt;
&lt;br /&gt;
In 1995, the Robbins Library at the University of Rochester created a digital collection of Arthurian texts, images, and bibliographies. Together with medieval scholars, we recently completed the redesign and development of an interface for this collection. Using FRBR concepts, we re-conceptualized organization and editing workflow from the ground up in a mobile-first Drupal-based project. &lt;br /&gt;
&lt;br /&gt;
In this talk we will describe the project as well as how we utilized the techniques of work practice study and user centered design to maintain engagement with reluctant stakeholders, nontechnical scholars, and VERY meticulous graduate students.  Neither of us have previously presented at a Code4Lib conference.&lt;br /&gt;
&lt;br /&gt;
==Docker? VMs? EC2? Yes! With Packer.io==&lt;br /&gt;
&lt;br /&gt;
* Kevin S. Clarke, ksclarke@gmail.com, Digital Library Programmer, UCLA&lt;br /&gt;
&lt;br /&gt;
There are a lot of exciting ways to deploy a software stack nowadays. Many of our library systems are fully virtualized. Docker is a compelling alternative, and there are also cloud options like Amazon's EC2. This talk will introduce Packer.io, a tool for creating identical machine images for multiple platforms (e.g., Docker, VMWare, VirtualBox, EC2, GCE, OpenStack, et al.) all from a single source configuration.  It works well with Ansible, Chef, Puppet, Salt, and plain old Bash scripts. And, it's designed to be scriptable so that builds can be automated. This presentation will show how easy it is to use Packer.io to bring up a set of related services like Fedora 4, Grinder (for stress testing), and Graphite (for charting metrics). As an added value, all the buzzwords in this proposal will be defined and explained!&lt;br /&gt;
&lt;br /&gt;
== Technology on your Wrist: Cross-platform Smartwatch Development for Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:sanderson|Steven Carl Anderson]], sanderson@bpl.org, Boston Public Library (no previously accepted prepared talks but have done lightning talks in the past)&lt;br /&gt;
&lt;br /&gt;
I'll be the first to admit: smartwatches are unlikely to completely revolutionize how a library provides online services. But I believe they still represent an opportunity to further enhance existing library services and resources in a unique way.&lt;br /&gt;
&lt;br /&gt;
At the Boston Public Library (BPL), we're in the initial phases of designing a modest smartwatch app to provide notifications for circulation availability and checked-out-material due-date alerts by the end of current year. We're starting small, but we plan to evolve the concept over time as we see what (if any) traction such an application gets with potential users. For example, we plan to explore the possibility of adding &amp;quot;nearest branch to my current location&amp;quot; functionality to this app.&lt;br /&gt;
&lt;br /&gt;
Despite the &amp;quot;development phase&amp;quot; of this application as of this writing, this talk is not being given by a novice. As a technology enthusiast, I've released [http://www.phdgaming.com/smartwatch_projects/ five smartwatch applications] and have had two of those be finalists in a [http://www.phdgaming.com/samsung_challenge/ Samsung sponsored development challenge]. This experience not only will allow for the BPL to avoid many beginner mistakes in its smartwatch app development but also gives a much more complete understanding of the smartwatch development ecosystem.&lt;br /&gt;
&lt;br /&gt;
This talk will explore the following questions:&lt;br /&gt;
&lt;br /&gt;
* What kinds of online library services could potentially be transformed or translated into the smartwatch/wearable domain? What kinds of services are better left alone? These questions are currently being explored and I'll talk about our plans and experiences. Included will be any statistical information from our application launch along with statistics from my personal development.&lt;br /&gt;
&lt;br /&gt;
* How to support all the different operating systems these devices run without painful modifications to your codebase. (There's Tizen that is used by Samsung's Gear 2 and Gear S, Android Wear that is used by most other non-Apple manufacturers, then there is Apple's upcoming smartwatch itself, etc.)&lt;br /&gt;
&lt;br /&gt;
* How to support different screen resolutions on such a small device. From round to rectangular to perfectly square, smartwatches come in all different shapes these days.&lt;br /&gt;
&lt;br /&gt;
* What are the app stores like on these platforms? As I support multiple applications through different distribution networks, a guide to navigating how to distribute one's app is included and I'll reveal how these systems work “behind the curtain.”&lt;br /&gt;
&lt;br /&gt;
* What are common issues and pitfalls to avoid when doing development? Tips on broken APIs and how to cope or optimizing your code will be included.&lt;br /&gt;
&lt;br /&gt;
==Seeing the Forest From the Trees: The Art of Creating Workflows for Digital Projects ==&lt;br /&gt;
 &lt;br /&gt;
* Jen LaBarbera, j.labarbera@neu.edu, NDSR Resident, Northeastern University&lt;br /&gt;
* Joey Heinen, joseph_heinen@harvard.edu, NDSR Resident, Harvard University&lt;br /&gt;
* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH&lt;br /&gt;
* Tricia Patterson, triciap@mit.edu, NDSR Resident, MIT&lt;br /&gt;
&lt;br /&gt;
We have to &amp;quot;turn projects into programs&amp;quot; in order to create a solid and sustainable digital preservation initiative...but what the heck does that even mean? What does that look like?&lt;br /&gt;
&lt;br /&gt;
In this talk, members of the inaugural Boston cohort of the National Digital Stewardship Residency will discuss one piece of our digital preservation test kitchen: our stabs at creating digital workflows that will (hopefully) help our institutions turn digital preservation projects into programs. Specifically, we will talk about how difficult it is to create a general and overarching workflow for digital preservation tasks (e.g. ingest into repositories, format migrations, etc.) that incorporates various technical tools while also taking into account the myriad and unending list of possible exceptions or special scenarios. Turning these complicated, specific processes into a simplified and generalized workflow is an art. We haven't necessarily perfected that art yet, but in this talk, we'll share what has worked for us -- and what hasn't. We’ll also touch on the importance of documentation, and achieving that delicate balance of adequately thorough documentation that doesn’t pose the risk of information avalanche. These processes often create more questions than answers, but we'll share the answers that we (and our mentors) have found along the way!&lt;/div&gt;</summary>
		<author><name>Afred</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&amp;diff=41971</id>
		<title>2015 Prepared Talk Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&amp;diff=41971"/>
				<updated>2014-11-07T17:44:25Z</updated>
		
		<summary type="html">&lt;p&gt;Afred: /* PBCore in Action: Three Words, Not Two! */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Code4lib 2015 is a loosely-structured conference that provides people working at the intersection of libraries/archives/museums/cultural heritage and technology with a chance to share ideas, be inspired, and forge collaborations. For more information about the Code4lib community, please visit http://code4lib.org/about/. &lt;br /&gt;
The conference will be held at the Portland Hilton &amp;amp; Executive Tower in Portland, Oregon, from February 9-12, 2015.&lt;br /&gt;
&lt;br /&gt;
'''Proposals for Prepared Talks:'''&lt;br /&gt;
&lt;br /&gt;
We encourage everyone to propose a talk.&lt;br /&gt;
 &lt;br /&gt;
Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:&lt;br /&gt;
* Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software&lt;br /&gt;
* Tools and technologies – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)&lt;br /&gt;
* Technical issues - Big issues in library technology that should be addressed or better understood&lt;br /&gt;
* Relevant non-technical issues – Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc.&lt;br /&gt;
&lt;br /&gt;
Proposals can be submitted through Friday, November 7, 2014 at 5pm PST (GMT−8). Voting will start on November 11, 2014 and continue through November 25, 2014. The URL to submit votes will be announced on the Code4Lib website and mailing list and will require an active code4lib.org account to participate. The final list of presentations will be announced in early- to mid-December.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Proposals for Prepared Talks:'''&lt;br /&gt;
&lt;br /&gt;
Log in to the Code4lib wiki and edit this wiki page using the prescribed format. If you are not already registered, follow the instructions to do so.&lt;br /&gt;
Provide a title and brief (500 words or fewer) description of your proposed talk.&lt;br /&gt;
If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist voters in opening the conference to new presenters.&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Talk Title: ==&lt;br /&gt;
 &lt;br /&gt;
* Speaker's name,  email address, and (optional) affiliation&lt;br /&gt;
* Second speaker's name, email address, and affiliation, if second speaker&lt;br /&gt;
&lt;br /&gt;
Abstract of no more than 500 words.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Talk Proposals'''&lt;br /&gt;
== Zines + Gamification = Awesomest Metadata Literacy Outreach Event Ever! ==&lt;br /&gt;
 &lt;br /&gt;
* [http://www.JenniferHecker.info Jennifer Hecker], jenniferraehecker@gmail.com, [http://www.lib.utexas.edu/subject/zines University of Texas Libraries] &amp;amp; [http://www.AustinFanzineProject.org Austin Fanzine Project]&lt;br /&gt;
* [http://anomalily.net/ Lillian Karabaic], librarian@iprc.org, [http://www.iprc.org/ Independent Publishing Resource Center] (Portland)&lt;br /&gt;
 &lt;br /&gt;
In academic libraries, and elsewhere, the popularity of zine (a magazine produced for love, not profit) collections is on the rise. At the same time, metadata literacy is becoming an increasingly important skill, helping people navigate and understand digital environments and interactions. We have found a way to teach metadata literacy to the general public that isn’t super-boring – in fact, we’ve made it downright fun!&lt;br /&gt;
&lt;br /&gt;
First, volunteer zine librarian Lillian Karabaic of Portland’s Independent Publishing Resource Center facilitated the creation of a gamified cataloging interface for the IPRC’s annual Raiders of the Lost Archives backlog-busting 24-hour volunteer cataloging event.&lt;br /&gt;
&lt;br /&gt;
Then, archivist Jennifer Hecker facilitated the adaptation of the IPRC’s game for use in a similar, but also very different context – promoting UT Libraries newly-acquired zine collections. The main goal of the academic-library-based event was increasing excitement around the collections, but with the side goal of building metadata literacy, and introducing an understanding of library cataloging issues.&lt;br /&gt;
&lt;br /&gt;
The Texas modification also conforms to the xZINECOREx metadata schema developed by the national [http://zinelibraries.info/ Zine Librarians Interest Group], and triggered interesting conversations with the Libraries’s cataloging department about evolving metadata standards and how to incorporate the products of crowd-sourcing projects into existing workflows.&lt;br /&gt;
&lt;br /&gt;
Both games will be demoed.&lt;br /&gt;
&lt;br /&gt;
== Do the Semantic FRBRoo ==&lt;br /&gt;
* Rosie Le Faive, rlefaive@upei.ca, University of Prince Edward Island&lt;br /&gt;
&lt;br /&gt;
[http://www.islandora.ca Islandora] is great for creating repositories of any data type, but how can you model meaningful relationships between digital objects and use them to tell a story?&lt;br /&gt;
&lt;br /&gt;
At UPEI, I’m assembling an ethnography of Prince Edward Island’s traditional fiddle music that includes musical clips, video clips, oral histories, musical notation, images, and ethnographic commentaries. In order to present an exhibition-style site, I’m tying these digital objects together via the people, places, events, tunes and topics that they share or describe. &lt;br /&gt;
&lt;br /&gt;
To describe the relationships, I’m extending Islandora to use [http://www.cidoc-crm.org/frbr_inro.html FRBRoo], a vocabulary that combines the FRBR model with CIDOC-CRM, the the object-oriented museum documentation ontology. These modules being developed will allow other researchers to create a structured, navigable digital repository of diverse object types, that uses Islandora as an exhibition platform. &lt;br /&gt;
&lt;br /&gt;
== Our $50,000 Problem: Why Library School? ==&lt;br /&gt;
* Jennie Rose Halperin, jhalperin@mozilla.com, Mozilla Corporation&lt;br /&gt;
&lt;br /&gt;
57 library schools in the United States are churning out approximately 100 graduates per year, many with debt upwards of $50,000.  According to ONet, [http://www.inthelibrarywiththeleadpipe.org/2011/is-the-united-states-training-too-many-librarians-or-too-few-part-1/ 84% of library jobs in the US require an MLS.] The library profession is [http://dpeaflcio.org/programs-publications/issue-fact-sheets/library-workers-facts-figures/) 92% white and 82% female and entry-level librarians can expect to make $32,500 per year.]&lt;br /&gt;
&lt;br /&gt;
Contrasted with developers, who are almost [http://www.ncwit.org/blog/did-you-know-demographics-technical-women 90% male] and can expect to make [http://www.forbes.com/sites/jennagoudreau/2011/06/01/best-entry-level-jobs/ $70,000 in an entry-level position,] these numbers are dismal.&lt;br /&gt;
&lt;br /&gt;
According to a recent survey, the top skill that outgoing library students want to know is “programming” and yet many MLS programs still consider Microsoft Word an essential technology skill.&lt;br /&gt;
&lt;br /&gt;
What is going on here? Why do we accept this fate, where mostly female debt-burdened professionals continue to be thrown onto the work force without the education their expensive degrees promised?&lt;br /&gt;
&lt;br /&gt;
As a community we need to come together to stop this cycle. We need to provide better support and mentorship to diversify and keep the profession relevant and help librarianship move into the future it deserves.&lt;br /&gt;
&lt;br /&gt;
This talk will walk through the challenges of navigating a hostile employment environment as well as present models for better development and future state imagining.&lt;br /&gt;
&lt;br /&gt;
== No cataloging software? Need more than Dublin Core? No problem!: Experiences with CollectiveAccess ==&lt;br /&gt;
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University&lt;br /&gt;
* Rachel Wittmann, rwittma@clemson.edu, Clemson University&lt;br /&gt;
&lt;br /&gt;
Clemson University Libraries has implemented the open-source software CollectiveAccess for customized digital collection needs. CollectiveAccess is an open-source project with the goal of providing a flexible way to manage and publish museum and archival collections. There are several applications associated with the projects; most used are: Providence (for cataloging and entering metadata) and Pawtucket (for displaying objects in a collection for the public). It has many profiles readily available for installing with existing library standards, such as Dublin Core, and there is a robust syntax for creating your own profiles to fit custom tailored metadata schemas. Plus, the user interface allows you to modify the metadata profile quickly and easily.&lt;br /&gt;
&lt;br /&gt;
In this talk, we will discuss:&lt;br /&gt;
* Our experiences with installing Providence and creating an installation profile that satisfies the needs of many of the Clemson Libraries digital archiving processes. &lt;br /&gt;
* The stumbling blocks experienced in that process and how they were resolved.&lt;br /&gt;
* The available plugins sourcing widely used authorities, such as Library of Congress thesauri and GeoNames.org, and how they have been used by our projects. &lt;br /&gt;
* A brief overview of the export and import functions and also current workflow practices within Providence.&lt;br /&gt;
* Future plans &amp;amp; the role of CollectiveAccess at Clemson University Libraries&lt;br /&gt;
&lt;br /&gt;
== Getting ContentDM and Wordpress to Play Together ==&lt;br /&gt;
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University&lt;br /&gt;
&lt;br /&gt;
Clemson University Libraries has a very strong program for digitizing and archiving photographs, and the Digital Imaging team processes many hundreds of photographs every month. These images are managed using different methods, including ContentDM, a digital collection manager.&lt;br /&gt;
&lt;br /&gt;
ContentDM provides various methods for searching and displaying photographs, along with their metadata. However, recent initiatives have resulted in the need to leverage those collections into exhibits displayed on other library-related websites, such as our Special Collections unit. The Clemson Libraries has invested heavily in Wordpress as our content management system of choice, and it seemed most efficient not to have to export and import images into our Wordpress sites in order to provide exhibited images.&lt;br /&gt;
&lt;br /&gt;
Fortunately, ContentDM has provided an API to many of their functions, allowing the extraction of metadata and even rescaled images through URLs. This project has been developing a plugin for Wordpress that integrates with ContentDM through shortcodes that Wordpress editors can easily include in their content. These shortcodes allow editors to choose how many images, which images from which collections, thumbnail sizes, etc. to display in different gallery styles. Plans are for it to allow integration with different plugins such as Fancybox and Masonry.&lt;br /&gt;
&lt;br /&gt;
In this presentation, I will demonstrate the current state of the plugin and discuss future plans. &lt;br /&gt;
&lt;br /&gt;
==Refinery — An open source locally deployable web platform for the analysis of large document collections==&lt;br /&gt;
 &lt;br /&gt;
* [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com&lt;br /&gt;
&lt;br /&gt;
Refinery is an open source web platform for the analysis of large unstructured document collections. It extracts meaningful semantic themes within documents also known as &amp;quot;topics&amp;quot; which can be thought of as word clouds composed of terms that highly co-occur with one another. Once this semantic index is formed, one can extract relevant documents related to these topics and further refine their contents through a summarization process that allows users to search for phrases that are relevant to them within the corpus. The goal of Refinery is to make this whole process easier and to provide some of the latest scalable versions of these learning algorithms in an intuitive web-based interface. Refinery is also meant to be run locally, thus bypassing the need for securing document collections over the internet. The talk will go through some of the technologies involved and a demo of the app.&lt;br /&gt;
&lt;br /&gt;
For more info check out http://www.docrefinery.org.&lt;br /&gt;
&lt;br /&gt;
==Drupal 8 — Evolution &amp;amp; Revolution==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Drupal 8 is in beta and nearing release. Among its many features, it notably has become more developer friendly through its adoption of the Symfony PHP framework along with Symfony's outstanding set of libraries (like Guzzle) and tools (like Composer). And, in implementing the Twig theming system, it is can begin to escape PHPtemplate. These moves also make it easier to create headless systems that uses Angular.js and other systems for presentation, or even forgo presentation entirely.&lt;br /&gt;
&lt;br /&gt;
From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.&lt;br /&gt;
&lt;br /&gt;
==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==&lt;br /&gt;
 &lt;br /&gt;
* [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]],  stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]&lt;br /&gt;
&lt;br /&gt;
GameSalad is a popular tool for developing mobile and desktop games with little actual programming. In this presentation, Stan Bogdanov breaks down the development process he followed while building [https://github.com/stanrb/mobiLit mobiLit], a mobile app with the goal of being the first open-source gamified information literacy app to be used as part of a college-level information literacy curriculum. He will go through the basics of using GameSalad to create an app that can be easily customized by non-programmers and the instructional principles used to teach the material in a mobile medium. Stan will also go through two qualitative design studies he did on the app and discuss their results and the lessons learned from building mobiLit. The session will conclude with an overview of the next steps for the [https://github.com/stanrb/mobiLit mobiLit project].&lt;br /&gt;
&lt;br /&gt;
==The Impossible Search: Pulling data from multiple unknown sources==&lt;br /&gt;
 &lt;br /&gt;
* Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com &lt;br /&gt;
&lt;br /&gt;
It's easy to search data you know the structure of, but what if you need to pull in data from sources that don't have a standard structure. The ability to search community events along with your standard catalog search results is an example, but often the only way to pull these events is through XML, JSON, (Insert structured format here), or even just raw html. But how do you get that structure? That simple question is what makes this impossible. The process to define and process this structure takes a lot of manual labor, especially if the data you are pulling is just HTML, and then every time you add data to the index you have to run all the data through a script to pull in data in a format Solr or an other index can use. This talk will focus on Solr, but the principles explained will apply to many other indexes.&lt;br /&gt;
&lt;br /&gt;
==What! You're Not Using Docker?==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Boring part: Docker[1] is a container system that provides benefits similar to virtualization with only a fraction of the overhead. Scintillating part: Docker can host between four to six times the number of service instances than systems such as Xen or VMWare on a given piece of hardware. But thats not all! Docker also makes it simple(r) to create transportable instances, so you can spin up development servers on your laptop.&lt;br /&gt;
&lt;br /&gt;
*[1]https://www.docker.com/&lt;br /&gt;
&lt;br /&gt;
== Video Accessibility, WebVTT, and Timed Text Track Tricks ==&lt;br /&gt;
&lt;br /&gt;
* Jason Ronallo, jronallo@gmail.com, NCSU Libraries&lt;br /&gt;
&lt;br /&gt;
Video on the Web presents new challenges and opportunities. How do you make your video more accessible to those with various disabilities and needs? I'll show you how. This presentation will focus on how to write and deliver captions, subtitles, audio descriptions, and timed metadata tracks for Web video using the WebVTT W3C standard. Encoding timed text tracks in this way opens up opportunities for new functionality on your websites beyond accessibility. The presentation will show some examples of the potential for using timed text tracks in creative ways. I'll cover all the HTML and JavaScript you will need to know as well as some of the CSS and other bits you could probably do without but are too fun to pass up.&lt;br /&gt;
&lt;br /&gt;
== Categorizing Records with Random Forests ==&lt;br /&gt;
 &lt;br /&gt;
* Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library&lt;br /&gt;
Academic libraries are increasingly responsible for providing ingest, search, discovery, and analysis for data sets.  Emerging techniques from data science and machine learning can provide librarians and developers with an opportunity to generate new insights and services from these document collections.  This presentation will provide a brief overview of common machine learning classification techniques, then dive into a more detailed example using a random forest to assign keywords to research data sets.  The talk will emphasize the insight that can be gained from machine learning rather than the inner workings of the algorithms.  The overall goal of this presentation is to provide librarians and developers with the context to recognize an opportunity to apply machine learning categorization techniques at their home campuses and organizations.  &lt;br /&gt;
&lt;br /&gt;
== Data Science in Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Devon Smith, smithde@oclc.org, OCLC&lt;br /&gt;
&lt;br /&gt;
Data Science is increasing in buzz and hype. I'll go over what it is, what it isn't, and how it fits in libraries.&lt;br /&gt;
&lt;br /&gt;
== PDF metadata extraction for academic literature == &lt;br /&gt;
&lt;br /&gt;
* Kevin Savage, kevin.savage at mendeley.com, Mendeley&lt;br /&gt;
* Joyce Stack, joyce.stack at mendeley.com, Mendeley&lt;br /&gt;
&lt;br /&gt;
Mendeley recently added a, &amp;quot;document from file,&amp;quot; endpoint to its API which attempts to extract metadata such as title and authors directly from PDF files. This talk will describe at a high level the machine learning methods we used including how we measured and tuned our model. We will then delve more deeply into our stack, the tools we used, some of the things that didn't work and why PDFs are the worst thing ever to compute over.&lt;br /&gt;
&lt;br /&gt;
== Giving Users What They Want: Record Grouping in VuFind ==&lt;br /&gt;
 &lt;br /&gt;
* Mark Noble,  mark@marmot.org, [//www.marmot.org Marmot Library Network]&lt;br /&gt;
&lt;br /&gt;
In 2013, Marmot did extensive usability studies with patrons to determine what was difficult in the catalog.  Many patrons had problems sifting through all of the various formats and editions of a title.  In 2014 we developed a method for [//mercury.marmot.org/Union/Search?lookfor=divergent grouping records] so only a single work is shown in search results and all formats and editions are listed under that work.  We will discuss our definition of a 'work' based on FRBR principles; combining meta data from MARC records with metadata from other sources like OverDrive; the technical details of Record Grouping; the design decisions made during implementation; and the reaction from users and staff.&lt;br /&gt;
&lt;br /&gt;
== Topic Space: a mobile augmented reality recommendation app ==&lt;br /&gt;
&lt;br /&gt;
* Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign&lt;br /&gt;
&lt;br /&gt;
The Topic Space module (http://minrvaproject.org/modules_topicspace.php ) was developed with an IMLS Sparks! Grant to investigate augmented reality technologies for in-library recommendations. The funding allowed for sustained university community collaboration by the University Library, the Graduate School of Library and Information Science, as well as graduate student programmers sourced from the Department of Computer Science. Collaborators designed app functionality and identified relevant open source libraries that could power optical character recognition (OCR) functionality from within the mobile phone.&lt;br /&gt;
&lt;br /&gt;
Topic space allows a user to take a picture of an item's call number in the book stacks. The module will show the user other books that are relevant but that are not shelved nearby. It can also show users books that are normally shelved here but that are currently checked out. Recommendations are based on Library of Congress subject headings and ILS circulation data which indicate recommendation candidates based on total check-outs. &lt;br /&gt;
&lt;br /&gt;
Research questions included development of back end (server-side) pattern matching algorithms for recommendations, and a rapid formative evaluation of interface design that would provide optimal user experience for navigation of the book stacks as a context to recommendations.&lt;br /&gt;
&lt;br /&gt;
Along with the Topic Space native app, grant collaborators prototyped web based recommendations which could serve as a new way of providing readers advisory and “more like this” recommendations from discovery interfaces accessed through desktop browsers. Outcomes of the grant include the availability of the [https://play.google.com/store/apps/details?id=edu.illinois.ugl.minrva Topic Spaces module within Minrva app on the Android Play store] and an experimental [http://backbonejs.org/ Backbone.js] based [http://minrva-dev.library.illinois.edu Topic Space web app].&lt;br /&gt;
&lt;br /&gt;
== Leveling Up Your Git Workflow ==&lt;br /&gt;
&lt;br /&gt;
* Megan Kudzia, moneill@albion.edu, Albion College Library&lt;br /&gt;
* Kate Sears, eks11@albion.edu, Albion College Library&lt;br /&gt;
&lt;br /&gt;
Have you started experimenting with Git on your own, but now you need to include others in your projects? Learn from our mistakes! Transitioning from a one-person git workflow and repo structure, to a structure that includes multiple people (including student workers), is not for the faint of heart. We'll talk about why we decided to work this way, our path to developing a git culture amongst ourselves, conceptual and technical difficulties we've faced, what we learned, and where we are now. Also with pretty pictures (aka workflow drawings).&lt;br /&gt;
&lt;br /&gt;
== Drone Loaning Program: Because Laptops are so last century ==&lt;br /&gt;
&lt;br /&gt;
 * Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries&lt;br /&gt;
 * Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries&lt;br /&gt;
&lt;br /&gt;
At Univ. Maryland we are in the very early stages of looking into allowing our student body get their hands on a drone. Yes that's right we will let students take out a drone for n amount of hours to work on projects of their choosing. The talk will talk about the logistics of getting a program of this sort from concept to &amp;quot;Is the drone available?&amp;quot;. If people sign waivers we will also promise not to crash the drone into code4lib attendees.&lt;br /&gt;
&lt;br /&gt;
== Got Git? Getting More Out of Your GitHub Repositories ==&lt;br /&gt;
&lt;br /&gt;
 * Terry Brady, twb27@georgetown.edu, Georgetown University Library&lt;br /&gt;
&lt;br /&gt;
This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories. &lt;br /&gt;
&lt;br /&gt;
In additional to all of the great benefits of using Git for code management, the GitHub interface provides a powerful set of tools to showcase a project and to keep your users informed of developments to your project.  These tools can assist with marketing and outreach - turning your code repository into a focus of conversation!&lt;br /&gt;
&lt;br /&gt;
* [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]&lt;br /&gt;
* [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]&lt;br /&gt;
* [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]&lt;br /&gt;
* [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]&lt;br /&gt;
* Gists for code sharing&lt;br /&gt;
* Private Repositories and Organizational Groups&lt;br /&gt;
* Pull Request Conversation Tracking&lt;br /&gt;
* Customized Issue management&lt;br /&gt;
&lt;br /&gt;
== Quick Wins for Every Department in the Library - File Analyzer! ==&lt;br /&gt;
&lt;br /&gt;
 * Terry Brady, twb27@georgetown.edu, Georgetown University Library&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.&lt;br /&gt;
* Analyzing Marc Records for the Cataloging department&lt;br /&gt;
* Transferring ILS invoices for the University Account System for the Acquisitions department &lt;br /&gt;
* Delivering patron fines to the Bursar’s office for the Access Service department&lt;br /&gt;
* Summarizing student worker timesheet data for the Finance department&lt;br /&gt;
* Validating COUNTER compliant reports for the Electronic Resources department&lt;br /&gt;
* Generating ingest packages for the Digital Services department&lt;br /&gt;
* Validating checksums for the Preservation department&lt;br /&gt;
&lt;br /&gt;
Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!&lt;br /&gt;
&lt;br /&gt;
==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor&lt;br /&gt;
&lt;br /&gt;
The transition from paper maps to digital ones changed much more than the maps themselves; it changed the very foundation of how we work and how we find each other. Now maps are transforming again.  The Geospatial World is moving from GIS systems that are institutionally-focused, expensive, feature-burdened, and binds data into a complicated and demanding user-hostile interface. From this transition from digital to web-based digital geospatial tools has come growth and development in new forms of map-based investigative journalism, activism, scholarship, and business ventures. This talk will highlight the conditions and strategies that made these changes possible as a means to draw a path by which librarians through our own work may follow, dragons notwithstanding. &lt;br /&gt;
&lt;br /&gt;
== Building Your Own Federated Search ==&lt;br /&gt;
&lt;br /&gt;
* Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco&lt;br /&gt;
&lt;br /&gt;
Advances in modern browsers have created some interesting possibilities for federated search. This presentation will cover common techniques and pitfalls in building a federated search. We will discuss what principles guided our decisions when implementing our own federated search. We will show tools we've built and our findings from building and using experimental prototypes.&lt;br /&gt;
&lt;br /&gt;
Your higher education institution likely offers dozens of online resources for educators, students, researchers, and the public. And each of these online resources likely has its own search tool. But users can't be expected to search in dozens of different interfaces to find what they're looking for. A typical solution for this issue is federated search. &lt;br /&gt;
&lt;br /&gt;
==  Indexing Linked Data with LDPath ==&lt;br /&gt;
&lt;br /&gt;
* Chris Beer, cabeer@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
LDPath [1] is a simple query language for indexing linked open data, with support for caching, content negotiation, and integration with non-RDF endpoints. This talk will demonstrate the features and potential of the language and framework to index a resource with links into id.loc.gov, viaf.org, geonames.org, etc to build an application-ready document.&lt;br /&gt;
&lt;br /&gt;
[1] http://marmotta.apache.org/ldpath/language.html&lt;br /&gt;
&lt;br /&gt;
== Show Me the Money: Integrating an LMS with Payment Providers ==&lt;br /&gt;
 &lt;br /&gt;
* Josh Weisman,  Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group&lt;br /&gt;
&lt;br /&gt;
In order to provide an easy and convenient way for patrons to pay fines, we are exploring ways to integrate the library management system with online payment providers such as PayPal. With many LMS systems being designed and developed for the cloud, we should be able to provide the frictionless user experience our patrons have come to expect from online transactions. In this session we'll discuss strategies for integration and review a sample application which uses REST APIs from a library management system to integrate with PayPal.&lt;br /&gt;
&lt;br /&gt;
== Shibboleth Federated Authentication for Library Applications: ==&lt;br /&gt;
&lt;br /&gt;
* Scott Fisher, scott.fisher@ucop.edu, California Digital Library&lt;br /&gt;
* Ken Weiss, ken.weiss@ucop.edu, California Digital Library&lt;br /&gt;
&lt;br /&gt;
Shibboleth is the most widely-used method to provide single-sign-on authentication to academic applications where users come from many different institutions. Shibboleth, the InCommon education and research trust framework, and the SAML protocol comprise a very powerful - but very complicated - solution to this very complicated problem. Scott and Ken have implemented Shibboleth for multiple library applications. They will share their understanding of the good, the bad, and the underlying spaghetti that makes it all work. Ken will discuss some of the technical aspects of the solution, touching on optimal and non-optimal use cases, administrative challenges, and authorization concerns. Scott will describe the implementation pattern for multi-institution single-sign-on that the California Digital Library has evolved, using the recently released Dash application (http://dash.cdlib.org) as an example.&lt;br /&gt;
&lt;br /&gt;
==Scientific Data: A Needs Assessment Journey==&lt;br /&gt;
 &lt;br /&gt;
*[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History&lt;br /&gt;
&lt;br /&gt;
While surveying digital research and collections data in the research science divisions at the American Museum of Natural History in NYC (as a part of my [http://ndsr.nycdigital.org/ National Digital Stewardship Residency] project), I have come across the big data hogs (genome sequencing and CT scanning) and the little pieces of data (images, publications), all equally important to not only scientific discovery, but as nodes in the history of science. &lt;br /&gt;
&lt;br /&gt;
In this session, I will discuss the development of my needs assessment surveys for scientific datasets and the interview process with Museum curators and researchers as background, seguing into an explanation of the results. I will then combine my findings into preliminary selection criteria to choose tools for digital preservation and management unique to scientific datasets. This will brooke a discussion on emerging standards, tools, and technologies in big data, specific to research science. &lt;br /&gt;
&lt;br /&gt;
I will conclude with preliminary findings on emerging technology that can be used to answer concerns surrounding the management and digital preservation of these data. I am hoping the Q&amp;amp;A session can be used to both answer questions about my project, and function as a way for you (the larger tech-savy library community)  to discuss the tools I’ve touched on in this talk. &lt;br /&gt;
&lt;br /&gt;
== Feminist Human Computer Interaction (HCI) in Library Software ==&lt;br /&gt;
 &lt;br /&gt;
* Bess Sadler,  bess@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
Libraries are not neutral repositories of knowledge. Library classification systems and search technologies tend to reflect the inequalities, biases, ethnocentrism, and power imbalances of the societies in which they are built [1]. How might we better resist these tendencies in the library software we create? This talk will examine some qualities of feminist HCI (pluralism, self-disclosure, participation, ecology, advocacy, and embodiment) [2] through the lens of library software. &lt;br /&gt;
&lt;br /&gt;
[1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.&lt;br /&gt;
&lt;br /&gt;
[2] Bardzell, Shaowen. Feminist HCI: Taking Stock and Outlining an Agenda for Design. CHI 2010: HCI For All. http://dmrussell.net/CHI2010/docs/p1301.pdf&lt;br /&gt;
&lt;br /&gt;
== Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==&lt;br /&gt;
&lt;br /&gt;
* Audrey Altman, audrey at dp.la, Digital Public Library of America&lt;br /&gt;
* Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America&lt;br /&gt;
* Mark Breedlove, mb at dp.la, Digital Public Library of America&lt;br /&gt;
&lt;br /&gt;
The Digital Public Library of America aggregates metadata for over 8 million objects from more than 24 direct partners, or Hubs, using its Metadata Application Profile (MAP), an RDF metadata application profile based on the Europeana Data Model. After working with the initial system for harvesting, mapping and enhancing our Hub’s metadata for a year, we realized that it was inadequate for working with data at this scale. There were architectural issues; it was opaque to non-developer and partner staff; there were inadequate tools for quality assurance and analysis; and the system was unaware that it was working with RDF data. As the network of Hubs expanded and we ingested more metadata, it became harder and harder to know when or why a harvest, a mapping task, or an enrichment went wrong because the tools for quality assurance were largely inadequate. &lt;br /&gt;
&lt;br /&gt;
The DPLA Content and Technology teams decided to develop a new system from the ground up to address those problems. Development of Heidrun, the internal version of the new system, started in October 2014. Heidrun’s goals are to make it easier for us to harvest and map metadata from various sources and in variety of schemas to the DPLA MAP, to better enrich that metadata using external data sources, and to actively involve our partners in the ingestion process through access to better QA tools. Heidrun and its componentry are built on Ruby on Rails, Blacklight, and ActiveTriples. Our presentation will give some background on our design principles and processes used during development, the architecture of the system, and its functionality. We plan to release a version of Heidrun and its components as a generalized metadata aggregation system for use by DPLA Hubs and others working to aggregate cultural heritage metadata.&lt;br /&gt;
&lt;br /&gt;
== OS or GTFO: Program or Perish ==&lt;br /&gt;
*Tessa Fallon, tessa.fallon@gmail.com&lt;br /&gt;
&lt;br /&gt;
Description TBD&lt;br /&gt;
&lt;br /&gt;
== Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==&lt;br /&gt;
* Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries&lt;br /&gt;
Would your library like to have large digital signage that displays dynamic information such as library hours, weather, room availability, and more? Have you looked into purchasing large digital signage, only to be turned off by the high price tag and lack of customization available with commercial solutions? Our library has developed a cheap and effective alternative to these systems using HTML 5 authoring software, a large TV, and freely-available APIs from Google, Springshare, and others. At this session, you’ll learn about the system that we have in place for displaying dynamic and easily-updatable information on our library’s large digital display, and how you can easily create something similar for your library.&lt;br /&gt;
&lt;br /&gt;
== REPOX: Metadata Blender ==&lt;br /&gt;
 &lt;br /&gt;
* John Mignault, jmignault@metro.org, Empire State Digital Network&lt;br /&gt;
&lt;br /&gt;
With the growth in the number of hubs providing metadata to the Digital Public Library of America, many of them are using REPOX, a tool originally created for the Europeana project, to aggregate disparate metadata feeds and transform them into formats suitable for ingest into DPLA. The Empire State Digital Network, the forthcoming DPLA service hub for NY state, is using it to prepare for our first ingest into DPLA in early 2015.  We'll take a look at REPOX and its capabilities and how it can be useful for ingesting and transforming metadata, and also discuss some things we've learned in massaging widely varied metadata feeds.&lt;br /&gt;
&lt;br /&gt;
== Beyond Open Source ==&lt;br /&gt;
&lt;br /&gt;
* Jason Casden, jmcasden@ncsu.edu, NCSU Libraries&lt;br /&gt;
* Bret Davidson, bddavids@ncsu.edu, NCSU Libraries&lt;br /&gt;
&lt;br /&gt;
The Code4Lib community has produced an increasingly impressive collection of open source software over the last decade, but much of this creative work remains out of reach for large portions of the library community. Do the relatively privileged institutions represented by a majority of Code4Lib participants have a professional responsibility to support the adoption of their innovations?&lt;br /&gt;
&lt;br /&gt;
Drawing from old and new software packaging and distribution approaches (from freeware to Docker), we will propose extending the open source software values of collaboration and transparency to include the wide and affordable distribution of software. We believe this will not only simplify the process of sharing our applications within the Code4Lib community, but also make it possible for less well resourced institutions to actually use our software. We will identify areas of need, present our experiences with the users of our own open source projects, discuss our attempts to go beyond open source, and make an argument for the internal value of supporting and encouraging a vibrant library ecosystem.&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]] &lt;br /&gt;
[[Category:Talk Proposals]]&lt;br /&gt;
&lt;br /&gt;
== Making It Work: Problem Solving Using Open Source at a Small Academic Library ==&lt;br /&gt;
 &lt;br /&gt;
* Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology&lt;br /&gt;
* Max King, mking9@iit.edu, Illinois Institute of Technology&lt;br /&gt;
&lt;br /&gt;
The Illinois Institute of Technology campus was added to the National Register of Historic Places in 2005, and contains a building, Mies van der Rohe's S.R. Crown Hall, that was named a National Historic Landmark in 2001. Creating a digital resource that can adequately showcase the campus and its architecture is challenge enough in and of itself, but doing so as a two-person team of relative newcomers, at a university library without dedicated programmers on staff, ups the ante considerably.&lt;br /&gt;
The challenges of technical know-how, staff time, and funding are nothing new to anyone working on digital projects at a university library, and are amplified when doing so at a smaller institution. This talk covers the conception, development, and design of the campus map site that was built, concentrating on the problem-solving strategies developed to cope with limited technical and financial resources.&lt;br /&gt;
We'll talk about our approach to development with Open Source software, including Omeka, along with the Neatline and Simile Timeline plugins. We'll also discuss the juggling act of designing for mobile mapping functionality without sacrificing desktop design, weighing the costs of increased functionality versus our ability to time-effectively include that functionality, and the challenge of building a site that could be developed iteratively, with an eye towards future enhancement and sustainability. Finally, we’ll provide recommendations for other librarians at smaller institutions for their own efforts at digital development.&lt;br /&gt;
&lt;br /&gt;
== Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==&lt;br /&gt;
 &lt;br /&gt;
* Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art&lt;br /&gt;
&lt;br /&gt;
The Museum of Modern Art has amassed a large collection of audiovisual materials over its many decades of existence. In order to preserve these materials, much of the audiovisual collection has been digitized. This is a complex process involving numerous steps and devices, and the methods used for digitization can have an effect on the quality of the file that is preserved. Therefore, knowing exactly how something was digitized is critical for future stewards of these objects to be able to properly care for and preserve them. However, detailed technical information about the processes involved in the digitization of audiovisual materials is not defined explicitly in most metadata schemas used for audiovisual materials. In order to record process history using existing metadata standards, some level of creativity is required to allow existing standards to express this information.&lt;br /&gt;
&lt;br /&gt;
This talk will detail different metadata standards, including PBCore, PREMIS, and reVTMD, that can be implemented as methods of recording this information. Specifically, the talk will examine efforts to integrate this metadata into the Museum of Modern Art’s new digital repository, the DRMC. This talk will provide background on the DRMC as well as MoMA’s specific institutional needs for process history metadata, then discuss different metadata implementations we have considered to document process history.&lt;br /&gt;
&lt;br /&gt;
== Pig Kisses Elephant: Building Research Data Services for Web Archives ==&lt;br /&gt;
 &lt;br /&gt;
* Jefferson Bailey,  jefferson@archive.org, Internet Archive&lt;br /&gt;
* Vinay Goel, vinay@archive.org, Internet Archive&lt;br /&gt;
&lt;br /&gt;
More and more libraries and archives are creating web archiving programs.  For both new and established programs, these archives can consist of hundreds of thousands, if not millions, of born-digital resources within a single collection; as such, they are ideally suited for large-scale computational study and analysis. Yet current access methods for web archives consist largely of browsing the archived web in the same manner as browsing the live web and the size of these collections and complexity of the WARC format can make aggregate analysis difficult. This talk will describe a project to create new ways for users and researchers to access and study web archives by offering extracted and post-processed datasets derived from web collections. Working with the 325+ institutions and their 2600+ collections within the Archive-It service, the Internet Archive is building methods to deliver a variety of datasets culled from collections of web content, including extracted metadata packaged in JSON, longitudinal link graph data, named entities, and other types of data. The talk will cover the technical details of building dataset production pipelines with Apache Pig, Hadoop, and tools like Stanford NER, the programmatic aspects of building data services for archives and researchers, and ongoing work to create new ways to access and study web archives.&lt;br /&gt;
&lt;br /&gt;
== Awesome Pi, LOL! ==&lt;br /&gt;
&lt;br /&gt;
* Matt Connolly, mconnolly@cornell.edu, Cornell University Library&lt;br /&gt;
* Jennifer Colt, jrc88@cornell.edu, Cornell University Library&lt;br /&gt;
&lt;br /&gt;
Inspired by Harvard Library Lab’s “Awesome Box” project, Cornell’s Library Outside the Library (LOL) group is piloting a more automated approach to letting our users tell us which materials they find particularly stunning. Armed with a Raspberry Pi, a barcode scanner, and some bits of kit that flash and glow, we have ventured into the foreign world of hardware development. This talk will discuss what it’s like for software developers and designers to get their hands dirty, how patrons are reacting to the Awesomizer, and LOL’s not-afraid-to-fail philosophy of experimentation.&lt;br /&gt;
&lt;br /&gt;
== You Gotta Keep 'em Separated: The Case for &amp;quot;Bento Box&amp;quot; Discovery Interfaces ==&lt;br /&gt;
 &lt;br /&gt;
* Jason Thomale,  jason.thomale@unt.edu, University of North Texas Libraries&lt;br /&gt;
&lt;br /&gt;
I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.&lt;br /&gt;
&lt;br /&gt;
The thing is, practically all of us--in academic libraries at least--have a similar set up for discovery, with just a few variations, and so talking about it still seems useful. Stop me if this sounds familiar. You've got a single search box on the library homepage as a starting point for discovery. And it's probably a tabbed affair, with an option for searching the catalog for books, an option for searching a discovery service for articles, an option for searching databases, and maybe a few others. Maybe you have an option to search everything at once--probably the default, if you have it. And, if you're a crazy hepcat, maybe you ''only'' have your one search that searches everything, with no tabs.&lt;br /&gt;
&lt;br /&gt;
Now, the question is, for your &amp;quot;everything&amp;quot; search, are you doing a combined list of results, or are you doing it bento-box style, with a short results list from each category displayed in its own compartment?&lt;br /&gt;
&lt;br /&gt;
At UNT, we've been holding off on implementing an &amp;quot;everything&amp;quot; search, for various reasons. One reason is that the evidence for either style hasn't been very clear. There's this persistent paradox that we just can't reconcile: users tell us, through word and action, that they prefer searching Google, yet, libraries aren't Google, and there are valid design reasons why we shouldn't try to oversimplify our discovery interfaces to be like Google. And there's user data that supports both sides.&lt;br /&gt;
&lt;br /&gt;
Holding off on making this decision has granted us 2 years of data on how people use our tabbed search interface that does ''not'' include an &amp;quot;everything&amp;quot; search. Recently I conducted a thorough analysis of this data--specifically the usage and query data for our catalog and discovery system (Summon). And I think it helps make the case for a bento box style discovery interface. To be clear, it isn't exactly the smoking gun that I was hoping for, but the picture it paints I think is telling. At the very least, it points away from a combined-results approach.&lt;br /&gt;
&lt;br /&gt;
I'm proposing a talk discussing the data we've collected, the trends we've seen, and what I think it all means--plus other reasons that we're jumping on the &amp;quot;bento box&amp;quot; discovery bandwagon and why I think &amp;quot;bento box&amp;quot; is at this point the path that least sells our souls.&lt;br /&gt;
&lt;br /&gt;
== Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift ==&lt;br /&gt;
 &lt;br /&gt;
* Ashley Blewer!, ashley.blewer@gmail.com&lt;br /&gt;
&lt;br /&gt;
Checksum technology is used all over the place, from git commits to authenticating Linux packages. It is most commonly used in the digital preservation field to monitor materials in storage for changes that will occur over time or used in the transmission of files during duplication. But do you even checksum, bro? I want this talk to move checksums from a position of mysterious macho jargon to something everyone can understand and want to use. I think a lot of people have heard of checksum but don’t know where to begin when it comes to actually using it at their institution. And cryptography is hella intimidating! This talk will cover what checksums are, how they can be integrated into a library or archival workflow, protecting collections requiring additional levels of security, algorithms used to verify file fixity and how they are different, and other aspects of cryptographic technology. Oh, and please note that all points in this talk will be emphasized or lightly performed through Taylor Swift lyrics. Seriously, this talk will consist of at least 50% Taylor Swift. Can you, like, even?&lt;br /&gt;
&lt;br /&gt;
== Level Up Your Coding with Code Club (yes, you can talk about it) ==&lt;br /&gt;
&lt;br /&gt;
* Coral Sheldon-Hess, coral@sheldon-hess.org&lt;br /&gt;
&lt;br /&gt;
Reading code is a necessary part of becoming a better developer. It gives you more experience and more insight into How Things Are (or Aren't) Done; it builds your intuition about how to solve problems with code; and it increases your confidence that you, too, can tackle whatever technological problems you're facing.&lt;br /&gt;
&lt;br /&gt;
But you don't have to read code alone! (Which is good. It's really not fun to read code alone.) &lt;br /&gt;
&lt;br /&gt;
In late 2014, a group of librarians formed two Code Clubs, inspired by [http://bloggytoons.com/code-club/ this talk by Saron] (of Bloggytoons fame). I'd like to tell you about how we've structured our Code Clubs, what has gone well, what we've learned, and what you need to do to form your own Code Club. I'll share a list of the codebases we've looked at, too, to help you get your own Code Club off the ground! &lt;br /&gt;
&lt;br /&gt;
== The Growth of a Programmer ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:jgo | Joshua Gomez]], Getty Research Institute, jgomez@getty.edu&lt;br /&gt;
&lt;br /&gt;
Just like other creative endeavors, software developers can experience periods of great productivity or find themselves in a rut. After contemplating the alternating periods in my own career I've noticed several factors that have effected my own professional growth and happiness, including: mentorship, structure, community, teamwork, environment, formal education, etc. Not all of the factors need to be present at all times; but some mixture of them is critical for continued growth. In this talk, I will articulate these factors, discuss how they can effect a developer's career, and how they can be sought out when missing. This talk is aimed at both new developers looking to strike their own path as well as the veterans that lead or mentor them.&lt;br /&gt;
&lt;br /&gt;
== Developing a Fedora 4.0 Content Model for Disk Images ==&lt;br /&gt;
&lt;br /&gt;
* Matthew Farrell, matthew.j.farrell@duke.edu, Duke University Libraries&lt;br /&gt;
* Alexandra Chassanoff, achass@email.unc.edu, BitCurator Access Project Manager&lt;br /&gt;
&lt;br /&gt;
As the acquisition of born-digital materials grows, institutions are seeking methods to facilitate easy ingest into their repositories and provide access to disk images and files derived or extracted from disk images. In this session, we describe our development of a Fedora 4.0 Content model for disk images, including acceptable image file formats and the rationale behind those choices.  We will also discuss efforts to integrate the disk image content model into the BitCurator Access environment. Unlike generalized, format-agnostic content models which might treat the disk image as a generic bitstream, a content model designed for disk images enables expression of relationships among associated content in the collection such as files extracted from images and other born-digital and digitized material associated with the same creator.  It also enables capture of file-system attributes such as file paths, timestamps, whether files are allocated/deleted, etc.  Further, a disk image content model suggests further steps repositories can take in order to transform and re-use associated metadata generated during the creation and forensic analysis of the disk image.&lt;br /&gt;
&lt;br /&gt;
== Data acquisition and publishing tools in R ==&lt;br /&gt;
&lt;br /&gt;
* Scott Chamberlain,  scott@ropensci.org, rOpenSci/UC Berkeley - first-time presenter&lt;br /&gt;
&lt;br /&gt;
R is an open source programming environment that is widely used among researchers in many fields. R is powerful because it's free, increasingly robust, and facilitates reproducible research, an increasingly sought after goal in academia. Although tools for data manipulation/visualization/analysis are well developed in R, data acquisition and publishing tools are not. rOpenSci is a collaborative effort to create the tools necessary to complete the reproducible research workflow. This presentation discusses the need for these tools, including examples, including interacting with the repositories Mendeley, Dryad, DataONE, and Figshare. In addition, we are building tools for searching scholarly metadata and acuiring full text of open access articles in a standarized way across metadata providers (e.g., Crossref, DataCite, DPLA) and publishers (e.g., PLOS, PeerJ, BMC, Pubmed). Last, we are building out tools for data reading and writing in Ecologial Metadata Language (EML).&lt;br /&gt;
&lt;br /&gt;
== SPLUNK: Log File Analysis ==&lt;br /&gt;
&lt;br /&gt;
* Jim LeFager, jlefager@depaul.edu, DePaul University Library&lt;br /&gt;
DePaul University Library recently took over monitoring and maintaining of the library EZproxy servers this past year and using Splunk, a machine data analysis tool, we are able to gather information and statistics on our electronic resource usage in addition to monitoring the servers. Splunk is a tool that can collect, analyze, and visualize log files and other machine data in real time and this has allowed for gathering realtime usage statistics for our electronic resources allowing us to filter by multiple facets including IP Range, Group Membership (student, faculty), so that we can see who is accessing our resources and from where. Splunk allows our library to query our data and create rich custom dashboards as well as create alerts that can be triggered when certain conditions are met, such as error codes, which can send an email alert to a group of users. We will be leveraging Splunk to monitor all library web applications going forward. This talk will review setting up Splunk and best practices in using the available features and customizations available including creating queries, alerts, and custom dashboards.  &lt;br /&gt;
&lt;br /&gt;
== Your code does not exist in a vacuum ==&lt;br /&gt;
* Becky Yoose, yoosebec at grinnell dot edu, Grinnell College (Done a lightning talk, MC duties, but have not presented a prepared talk)&lt;br /&gt;
&lt;br /&gt;
“If you have something to say, then say it in code…” - Sebastian Hammer, code4lib 2009&lt;br /&gt;
&lt;br /&gt;
In its 10 year run, code4lib has covered the spectrum of libtech development, from search to repositories to interfaces. However, during this time there has been little discussion about this one little fact about development - code does not exist in a vacuum. &lt;br /&gt;
&lt;br /&gt;
Like the comment above, code has something to say. A person’s or organization’s culture and beliefs influences code in all steps of the development cycle. What development method you use, tools, programming languages, licenses - everything is interconnected with and influenced by the philosophies, economics, social structures, and cultural beliefs of the developer and their organization/community.&lt;br /&gt;
&lt;br /&gt;
This talk will discuss these interconnections and influences when one develops code for libraries, focusing on several development practices (such as “Fail Fast, Fail Often” and Agile)   and licensing choices (such as open source) that libtech has either tried to model or incorporate into mainstream libtech practices. It’ll only scratch the surface of the many influences present in libtech development, but it will give folks a starting point to further investigate these connections at their own organizations and as a community as a whole.&lt;br /&gt;
&lt;br /&gt;
tl;dr - this will be a messy theoretical talk about technology and libraries. No shiny code slides, no live demos. You might come out of this talk feeling uncomfortable. Your code does not exist in a vacuum. Then again, you don’t exist in a vacuum either.&lt;br /&gt;
&lt;br /&gt;
== The Metadata Hopper: Mapping and Merging Metadata Standards for Simple, User-Friendly Access ==&lt;br /&gt;
&lt;br /&gt;
* Tracy Seneca, tjseneca@uic.edu, University of Illinois at Chicago&lt;br /&gt;
* Esther Verreau: verreau1@uic.edu, University of Illinois at Chicago&lt;br /&gt;
&lt;br /&gt;
The Chicago Collections Consortium: 15 institutions and growing!  8 distinct EAD standards! At least 3 permutations of MARC, and we lost count of the varieties of custom CONTENTdm image collections.  Not to mention the 14,730 unique subject terms, nearly all of which lead our poor end-users to exactly one organization's content. &lt;br /&gt;
&lt;br /&gt;
All large content aggregation projects have faced this challenge, and there are a few emerging tools to help us wrangle disparate metadata into new contexts.  The Metadata Hopper is one such tool. The Metadata Hopper enables archivists to map their local metadata standards to standardized deposit records, and tags those materials using a shared vocabulary, integrating them into a user-friendly portal without disrupting local practices. In last year's Code4Lib lightning talk we described the challenges that the Chicago Collections Consortium faces in creating shared, in-depth access to archival and digital collections about Chicago history and culture across CCC member organizations. This year, thanks to the Andrew W. Mellon Foundation, we have a working Django application to demonstrate.  In this talk we'll discuss the design that enables multiple layers of flexibility, from the ability to accept a variety of metadata standards to designing for an open source audience.&lt;br /&gt;
&lt;br /&gt;
http://chicagocollectionsconsortium.org&lt;br /&gt;
&lt;br /&gt;
== Programmers are not projects: lessons learned from managing humans ==&lt;br /&gt;
&lt;br /&gt;
* Erin White, erwhite@vcu.edu, Virginia Commonwealth University - first-time presenter&lt;br /&gt;
&lt;br /&gt;
Managing projects is one thing, but managing people is another. Whether we’re hired as managers or grow “organically” into management roles, sometimes technical people end up leading technical teams (gasp!). I’ll talk about lessons I’ve learned about hiring, retaining, and working long-term and day-to-day with highly tech-competent humans. I’ll also talk about navigating the politics of libraryland, juggling different types of projects, and working with constrained budgets to make good things and keep talented people engaged.&lt;br /&gt;
&lt;br /&gt;
== Practical Strategies for Picking Low-Hanging Fruits to Improve Your Library's Web Usability and UX ==&lt;br /&gt;
&lt;br /&gt;
* Bohyun Kim, bkim@hshsl.umaryland.edu, University of Maryland, Baltimore&lt;br /&gt;
&lt;br /&gt;
Have you ever tried to fix an obvious (to you at least!) problem in Web usability or UX (user experience) only to face strong resistance from the library staff? Are you a strong advocate for making library resources, systems, services, and space as usable as possible, but do you often find yourself struggling to get the point across and/or obtain the crucial buy-in from colleagues and administrators? &lt;br /&gt;
&lt;br /&gt;
There is no shortage of Web usability and UX guidelines. But applying them to a library and implementing desired changes often involve a long and slow process. To tackle this issue, this talk will focus on how to utilize the 'expert review' process (aka 'heuristic evaluation') as a preliminary or even preparatory step before embarking on more time-and-labor-intensive usability testing and user research. Several examples from  simple fixes to more nuanced usability and UX issues in libraries will be discussed to your heart's content. The goal of this talk is to provide practical strategies for picking as many low-hanging fruits as possible to make a real (albeit small) difference to your library's Web usability and UX effectively and efficiently.&lt;br /&gt;
&lt;br /&gt;
== A Semantic Makeover for CMS Data ==&lt;br /&gt;
&lt;br /&gt;
* Bill Levay, wjlevay@gmail.com, Linked Jazz Project&lt;br /&gt;
&lt;br /&gt;
How can we take semi-structured but messy metadata from a repository like CONTENTdm and transform it into rich linked data? Working with metadata from Tulane’s Hogan Jazz Archive Photography Collection, the Linked Jazz Project used Open Refine and Python scripts to tease out proper names, match them with name authority URIs, and specify FOAF relationships between musicians who appear together in photographs. Additional RDF triples were created for any dates associated with the photos, and for those images with place information we employed GeoNames URIs. Historical images and data that were siloed can now interact with other datasets, like Linked Jazz’s rich set of names and personal relationships, and can be visualized [link to come] or otherwise presented on the web in any number of ways. I have not previously presented at a Code4Lib conference.&lt;br /&gt;
&lt;br /&gt;
== Taking User Experience (UX) to new heights ==&lt;br /&gt;
 &lt;br /&gt;
* Kayne Richens, kayne.richens@deakin.edu.au, Deakin University&lt;br /&gt;
&lt;br /&gt;
User Experience, or &amp;quot;UX&amp;quot;, is for more than just websites. At Deakin University Library we're exploring ways to improve the user experience inside our campus library spaces, by putting new technologies front and centre in the overall experience for our students. How are we doing this? We’re collaborating with the University's IT department and exploring the following Library-changing opportunities:&lt;br /&gt;
&lt;br /&gt;
- Augmented Reality for Way-finding: We’re tackling that infamous thing that all Libraries can't get right – way-finding. We're enhancing library tour information and way-finding experiences by introducing augmented reality solutions.&lt;br /&gt;
 &lt;br /&gt;
- Heat mapping the library with wi-fi: We’re using our existing wi-fi infrastructure to present &amp;quot;heat maps&amp;quot; of library space utilisation, allowing our users to easily locate the space that best suits their needs, whether it be busy spaces to collaborate, or quiet spaces to study. And by overlaying computer usage and group study room bookings, users can quickly locate the space they need.&lt;br /&gt;
 &lt;br /&gt;
- Video chat library service: We’re piloting video-conferencing facilities in our group study rooms and spaces, connecting users and librarians and other professionals.&lt;br /&gt;
         &lt;br /&gt;
This talk will look at how these different technologies will be brought together to provide improved user experiences, as well some of the evidence and reasons that helped us to identify our needs, so you can too.&lt;br /&gt;
&lt;br /&gt;
==How to Hack it as a Working Parent: or, Should Your Face be Bathed in the Blue Glow of a Phone at 2 AM?==&lt;br /&gt;
&lt;br /&gt;
*Margaret Heller, Loyola University Chicago, mheller1@luc.edu&lt;br /&gt;
*Christina Salazar, California State University Channel Islands, christina.salazar@csuci.edu&lt;br /&gt;
*May Yan, Ryerson University, may.yan@ryerson.ca&lt;br /&gt;
&lt;br /&gt;
Modern technology has made it easier than ever for parents employed in technical environments to keep up with work at all hours and in all locations. This makes it possible to work a flexible schedule, but also may lead to problems with work/life balance and furthering unreasonable expectations about working hours. Add to that shifting gender roles and limited paid parental leave in the United States and you have potential for burnout and a certainty for anxiety. It raises the additioal question of whether the “always connected” mindset puts up a barrier to some populations who otherwise might be better represented in open source and library technology communities. &lt;br /&gt;
&lt;br /&gt;
This presentation will address tools that are useful for working parents in technical library positions, and share some lessons learned about using these tools while maintaining a reasonable work/life balance. We will consider a question that Karen Coyle raised back in 1996: &lt;br /&gt;
“What if the thousands of hours of graveyard shift amateur hacking wasn't really the best way to get the job done? That would be unthinkable.” &lt;br /&gt;
&lt;br /&gt;
For those who are able to take an extended parental leave, we will present strategies for minimizing the impact to your career and your employer. For those (particularly in the United States) who are only able to take a short leave will require different strategies. Despite different levels of preparation, all are useful exercises in succession planning and making a stronger workplace and future ability to work a flexible schedule through reviewing workloads, cross-training personnel, hiring contract replacements, and creative divisions of labor. Such preparation makes work better for everyone, kids or no kids.&lt;br /&gt;
&lt;br /&gt;
==Making your digital objects embeddable around the web==&lt;br /&gt;
 &lt;br /&gt;
* Jessie Keck, jkeck@stanford.edu, Stanford University Libraries&lt;br /&gt;
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
With more and more content from our digital repositories making their way into our discovery environments we quickly realize that we’re repeatedly re-inventing the wheel when it comes to creating “Viewers” for these digital objects.  With various different types of viewers necessary (books, images, audio, video, geospatial data, etc) the burden of getting these viewers into various environments (topic guides, blogs, catalogs, etc) becomes exponential.&lt;br /&gt;
&lt;br /&gt;
In this talk we’ll discuss how Stanford University Libraries implemented an oEmbed service to create an extensible viewer framework for all of its digital content. Using this service we’ve been able to easily integrate viewers into various discovery applications as well as make it easy for end users who discover our objects to easily embed customized versions into their own websites and blogs.&lt;br /&gt;
&lt;br /&gt;
==So you want to make your geospatial data discoverable==&lt;br /&gt;
 &lt;br /&gt;
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
Finding data for research or coursework can be one of the most time intensive tasks for a scholar or student. We introduce GeoBlacklight, an open source, multi-institutional software project focused on solving these common challenges at institutions across the world. GeoBlacklight prioritizes user experience, integrates with many GIS tools, and streamlines the use and organization of geospatial data. This talk will provide an introduction to the software, demonstrate current functionality, and provide a road map for future work.&lt;br /&gt;
&lt;br /&gt;
== Clueless-Driven Development: How I learned to migrate to Fedora 4 ==&lt;br /&gt;
&lt;br /&gt;
* Adam Wead, awead@psu.edu, Penn State University&lt;br /&gt;
&lt;br /&gt;
Recently I was tasked with migrating the content from our Fedora3 repository to the new Fedora4 repository architecture.&lt;br /&gt;
Despite a wealth of community support, I had no idea how to approach, or even begin to solve this problem. I knew I&lt;br /&gt;
wanted to follow best practices and use test-driven  development to build my solution, but had no idea where to start.&lt;br /&gt;
Despite this initial setback, I was able to start writing tests with only a  vague understanding of the problem. As my&lt;br /&gt;
tests exposed where my understanding of the problem was flawed, my code evolved, and within a week I had arrived  at a&lt;br /&gt;
working solution that exhibited all the hallmarks of good testing and software design.&lt;br /&gt;
&lt;br /&gt;
This talk recounts the process I went through from starting with practically nothing, to arriving at a working solution.&lt;br /&gt;
You can follow the rules of  test-driven development, but you can write tests in an expressive way to describe the&lt;br /&gt;
problem instead of just describing what the code should do. It was also essential to begin testing from an integration&lt;br /&gt;
viewpoint as opposed to a unit one, because at the outset the units were unknown and were later realized through further&lt;br /&gt;
development. For the presentation, I will be demonstrating using RSpec and Ruby. All the code examples will be related&lt;br /&gt;
to the Hydra software stack; however, I hope to show  that the processes at work will be applicable in any context.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Designing and Leading a Kick A** Tech Team ==&lt;br /&gt;
 &lt;br /&gt;
* Sibyl Schaefer,  sschaefer@rockarch.org, Rockefeller Archive Center&lt;br /&gt;
&lt;br /&gt;
New managers are often promoted without receiving management training, yet management is not something you just figure out. The experience of being expected to know how to manage, yet not being trained to do so often results in new managers feeling isolated and unsure how to move from making to managing. In this talk I’ll focus on my own managerial experience of designing and leading an archival tech team in a small independent archives. Topics covered will include hiring, delegating, creating a team culture, and leading people whose specialized knowledge exceeds your own. The talk take-aways should be applicable to managers and employees at large and small institutions alike.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==American (Archives) Horror Story: LTO Failure and Data Loss ==&lt;br /&gt;
 &lt;br /&gt;
* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH&lt;br /&gt;
* Casey Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH&lt;br /&gt;
&lt;br /&gt;
Here’s a story to send shivers down archival spines: when transferring video files off LTO for the American Archive project, WGBH got an initial failure rate of 57%.   After repeat tries, the rates improved; still, an unnervingly large percentage of files were never able to be transferred successfully.   Even more unnerving, going public with our horror story got a big response from other archives using LTO -- it seems like many institutions are having similarly scary results.   What are the real risks with LTO tape?  Are there steps that archives should be taking to better circumvent those risks?  This presentation will share information about LTO storage failures across archives world and discuss the process of investigating the problem at WGBH by testing different methods of data retrieval from LTO (direct and networked downloads, individual file retrieval and bulk data dump, use of LTO 4 and LTO 6 decks) and using checksum comparisons and file analysis and characterization tools such as ffprobe, mediainfo and exiftool to analyze failed files.  We'll also present whatever results we’ve managed to turn up by the time of Code4Lib!&lt;br /&gt;
&lt;br /&gt;
== PBCore in Action: Three Words, Not Two! ==&lt;br /&gt;
 &lt;br /&gt;
* Casey E. Davis,  casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH&lt;br /&gt;
* Andrew (Drew) Myers, andrew_myers@wgbh.org, Supervising Developer, WGBH&lt;br /&gt;
&lt;br /&gt;
In 2001, public media representatives developed the PBCore XML schema to establish a common language for managing metadata about their analog and digital audio and video. Since then, PBCore has been adopted by a number of organizations and archivists in the moving image archival community. The schema has also undergone a few revisions, but on more than one occasion it was left orphaned and with little to no support.&lt;br /&gt;
 &lt;br /&gt;
Times have changed. You may have heard the news that PBCore is back in action as part of the American Archive of Public Broadcasting initiative and via the Association of Moving Image Archivists (AMIA) PBCore Advisory Subcommittee. A group of archivists, public media stakeholders, and engaged users have come together to provide necessary support for the standard and to see to its further development.&lt;br /&gt;
 &lt;br /&gt;
At this session, we'll discuss the scope and uses of PBCore in digital preservation and access, report on the progress and goals of the PBCore Advisory Subcommittee, and share how the group (by the time of the conference) will have transformed the XML schema into an RDF ontology, bringing PBCore into the second decade of the 21st century. #PBHardcore&lt;br /&gt;
&lt;br /&gt;
==Docker? VMs? EC2? Yes! With Packer.io==&lt;br /&gt;
&lt;br /&gt;
* Kevin S. Clarke, ksclarke@gmail.com, Digital Library Programmer, UCLA&lt;br /&gt;
&lt;br /&gt;
There are a lot of exciting ways to deploy a stack nowadays. Many of your systems are fully virtualized. Docker is a compelling alternative, and there are also cloud options like Amazon's EC2. This talk will introduce Packer.io, a tool for creating identical machine images for multiple platforms (e.g., Docker, VMWare, VirtualBox, EC2, GCE, OpenStack, et al.) from a single source configuration.  It works well with Ansible, Chef, Puppet, Salt, and plain old Bash scripts. And, it's designed to be scriptable so that builds can be automated. This presentation will show how easy it is to use Packer.io to bring up a set of related services like Fedora 4, Grinder, and Graphite. And, as an added value, all the buzzwords in this proposal will be defined and explained!&lt;/div&gt;</summary>
		<author><name>Afred</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&amp;diff=41969</id>
		<title>2015 Prepared Talk Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&amp;diff=41969"/>
				<updated>2014-11-07T17:28:05Z</updated>
		
		<summary type="html">&lt;p&gt;Afred: Added Proposed Talk #56 &amp;quot;PBCore In Action...&amp;quot; to the wiki&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Code4lib 2015 is a loosely-structured conference that provides people working at the intersection of libraries/archives/museums/cultural heritage and technology with a chance to share ideas, be inspired, and forge collaborations. For more information about the Code4lib community, please visit http://code4lib.org/about/. &lt;br /&gt;
The conference will be held at the Portland Hilton &amp;amp; Executive Tower in Portland, Oregon, from February 9-12, 2015.&lt;br /&gt;
&lt;br /&gt;
'''Proposals for Prepared Talks:'''&lt;br /&gt;
&lt;br /&gt;
We encourage everyone to propose a talk.&lt;br /&gt;
 &lt;br /&gt;
Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:&lt;br /&gt;
* Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software&lt;br /&gt;
* Tools and technologies – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)&lt;br /&gt;
* Technical issues - Big issues in library technology that should be addressed or better understood&lt;br /&gt;
* Relevant non-technical issues – Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc.&lt;br /&gt;
&lt;br /&gt;
Proposals can be submitted through Friday, November 7, 2014 at 5pm PST (GMT−8). Voting will start on November 11, 2014 and continue through November 25, 2014. The URL to submit votes will be announced on the Code4Lib website and mailing list and will require an active code4lib.org account to participate. The final list of presentations will be announced in early- to mid-December.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Proposals for Prepared Talks:'''&lt;br /&gt;
&lt;br /&gt;
Log in to the Code4lib wiki and edit this wiki page using the prescribed format. If you are not already registered, follow the instructions to do so.&lt;br /&gt;
Provide a title and brief (500 words or fewer) description of your proposed talk.&lt;br /&gt;
If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist voters in opening the conference to new presenters.&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Talk Title: ==&lt;br /&gt;
 &lt;br /&gt;
* Speaker's name,  email address, and (optional) affiliation&lt;br /&gt;
* Second speaker's name, email address, and affiliation, if second speaker&lt;br /&gt;
&lt;br /&gt;
Abstract of no more than 500 words.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Talk Proposals'''&lt;br /&gt;
== Zines + Gamification = Awesomest Metadata Literacy Outreach Event Ever! ==&lt;br /&gt;
 &lt;br /&gt;
* [http://www.JenniferHecker.info Jennifer Hecker], jenniferraehecker@gmail.com, [http://www.lib.utexas.edu/subject/zines University of Texas Libraries] &amp;amp; [http://www.AustinFanzineProject.org Austin Fanzine Project]&lt;br /&gt;
* [http://anomalily.net/ Lillian Karabaic], librarian@iprc.org, [http://www.iprc.org/ Independent Publishing Resource Center] (Portland)&lt;br /&gt;
 &lt;br /&gt;
In academic libraries, and elsewhere, the popularity of zine (a magazine produced for love, not profit) collections is on the rise. At the same time, metadata literacy is becoming an increasingly important skill, helping people navigate and understand digital environments and interactions. We have found a way to teach metadata literacy to the general public that isn’t super-boring – in fact, we’ve made it downright fun!&lt;br /&gt;
&lt;br /&gt;
First, volunteer zine librarian Lillian Karabaic of Portland’s Independent Publishing Resource Center facilitated the creation of a gamified cataloging interface for the IPRC’s annual Raiders of the Lost Archives backlog-busting 24-hour volunteer cataloging event.&lt;br /&gt;
&lt;br /&gt;
Then, archivist Jennifer Hecker facilitated the adaptation of the IPRC’s game for use in a similar, but also very different context – promoting UT Libraries newly-acquired zine collections. The main goal of the academic-library-based event was increasing excitement around the collections, but with the side goal of building metadata literacy, and introducing an understanding of library cataloging issues.&lt;br /&gt;
&lt;br /&gt;
The Texas modification also conforms to the xZINECOREx metadata schema developed by the national [http://zinelibraries.info/ Zine Librarians Interest Group], and triggered interesting conversations with the Libraries’s cataloging department about evolving metadata standards and how to incorporate the products of crowd-sourcing projects into existing workflows.&lt;br /&gt;
&lt;br /&gt;
Both games will be demoed.&lt;br /&gt;
&lt;br /&gt;
== Do the Semantic FRBRoo ==&lt;br /&gt;
* Rosie Le Faive, rlefaive@upei.ca, University of Prince Edward Island&lt;br /&gt;
&lt;br /&gt;
[http://www.islandora.ca Islandora] is great for creating repositories of any data type, but how can you model meaningful relationships between digital objects and use them to tell a story?&lt;br /&gt;
&lt;br /&gt;
At UPEI, I’m assembling an ethnography of Prince Edward Island’s traditional fiddle music that includes musical clips, video clips, oral histories, musical notation, images, and ethnographic commentaries. In order to present an exhibition-style site, I’m tying these digital objects together via the people, places, events, tunes and topics that they share or describe. &lt;br /&gt;
&lt;br /&gt;
To describe the relationships, I’m extending Islandora to use [http://www.cidoc-crm.org/frbr_inro.html FRBRoo], a vocabulary that combines the FRBR model with CIDOC-CRM, the the object-oriented museum documentation ontology. These modules being developed will allow other researchers to create a structured, navigable digital repository of diverse object types, that uses Islandora as an exhibition platform. &lt;br /&gt;
&lt;br /&gt;
== Our $50,000 Problem: Why Library School? ==&lt;br /&gt;
* Jennie Rose Halperin, jhalperin@mozilla.com, Mozilla Corporation&lt;br /&gt;
&lt;br /&gt;
57 library schools in the United States are churning out approximately 100 graduates per year, many with debt upwards of $50,000.  According to ONet, [http://www.inthelibrarywiththeleadpipe.org/2011/is-the-united-states-training-too-many-librarians-or-too-few-part-1/ 84% of library jobs in the US require an MLS.] The library profession is [http://dpeaflcio.org/programs-publications/issue-fact-sheets/library-workers-facts-figures/) 92% white and 82% female and entry-level librarians can expect to make $32,500 per year.]&lt;br /&gt;
&lt;br /&gt;
Contrasted with developers, who are almost [http://www.ncwit.org/blog/did-you-know-demographics-technical-women 90% male] and can expect to make [http://www.forbes.com/sites/jennagoudreau/2011/06/01/best-entry-level-jobs/ $70,000 in an entry-level position,] these numbers are dismal.&lt;br /&gt;
&lt;br /&gt;
According to a recent survey, the top skill that outgoing library students want to know is “programming” and yet many MLS programs still consider Microsoft Word an essential technology skill.&lt;br /&gt;
&lt;br /&gt;
What is going on here? Why do we accept this fate, where mostly female debt-burdened professionals continue to be thrown onto the work force without the education their expensive degrees promised?&lt;br /&gt;
&lt;br /&gt;
As a community we need to come together to stop this cycle. We need to provide better support and mentorship to diversify and keep the profession relevant and help librarianship move into the future it deserves.&lt;br /&gt;
&lt;br /&gt;
This talk will walk through the challenges of navigating a hostile employment environment as well as present models for better development and future state imagining.&lt;br /&gt;
&lt;br /&gt;
== No cataloging software? Need more than Dublin Core? No problem!: Experiences with CollectiveAccess ==&lt;br /&gt;
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University&lt;br /&gt;
* Rachel Wittmann, rwittma@clemson.edu, Clemson University&lt;br /&gt;
&lt;br /&gt;
Clemson University Libraries has implemented the open-source software CollectiveAccess for customized digital collection needs. CollectiveAccess is an open-source project with the goal of providing a flexible way to manage and publish museum and archival collections. There are several applications associated with the projects; most used are: Providence (for cataloging and entering metadata) and Pawtucket (for displaying objects in a collection for the public). It has many profiles readily available for installing with existing library standards, such as Dublin Core, and there is a robust syntax for creating your own profiles to fit custom tailored metadata schemas. Plus, the user interface allows you to modify the metadata profile quickly and easily.&lt;br /&gt;
&lt;br /&gt;
In this talk, we will discuss:&lt;br /&gt;
* Our experiences with installing Providence and creating an installation profile that satisfies the needs of many of the Clemson Libraries digital archiving processes. &lt;br /&gt;
* The stumbling blocks experienced in that process and how they were resolved.&lt;br /&gt;
* The available plugins sourcing widely used authorities, such as Library of Congress thesauri and GeoNames.org, and how they have been used by our projects. &lt;br /&gt;
* A brief overview of the export and import functions and also current workflow practices within Providence.&lt;br /&gt;
* Future plans &amp;amp; the role of CollectiveAccess at Clemson University Libraries&lt;br /&gt;
&lt;br /&gt;
== Getting ContentDM and Wordpress to Play Together ==&lt;br /&gt;
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University&lt;br /&gt;
&lt;br /&gt;
Clemson University Libraries has a very strong program for digitizing and archiving photographs, and the Digital Imaging team processes many hundreds of photographs every month. These images are managed using different methods, including ContentDM, a digital collection manager.&lt;br /&gt;
&lt;br /&gt;
ContentDM provides various methods for searching and displaying photographs, along with their metadata. However, recent initiatives have resulted in the need to leverage those collections into exhibits displayed on other library-related websites, such as our Special Collections unit. The Clemson Libraries has invested heavily in Wordpress as our content management system of choice, and it seemed most efficient not to have to export and import images into our Wordpress sites in order to provide exhibited images.&lt;br /&gt;
&lt;br /&gt;
Fortunately, ContentDM has provided an API to many of their functions, allowing the extraction of metadata and even rescaled images through URLs. This project has been developing a plugin for Wordpress that integrates with ContentDM through shortcodes that Wordpress editors can easily include in their content. These shortcodes allow editors to choose how many images, which images from which collections, thumbnail sizes, etc. to display in different gallery styles. Plans are for it to allow integration with different plugins such as Fancybox and Masonry.&lt;br /&gt;
&lt;br /&gt;
In this presentation, I will demonstrate the current state of the plugin and discuss future plans. &lt;br /&gt;
&lt;br /&gt;
==Refinery — An open source locally deployable web platform for the analysis of large document collections==&lt;br /&gt;
 &lt;br /&gt;
* [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com&lt;br /&gt;
&lt;br /&gt;
Refinery is an open source web platform for the analysis of large unstructured document collections. It extracts meaningful semantic themes within documents also known as &amp;quot;topics&amp;quot; which can be thought of as word clouds composed of terms that highly co-occur with one another. Once this semantic index is formed, one can extract relevant documents related to these topics and further refine their contents through a summarization process that allows users to search for phrases that are relevant to them within the corpus. The goal of Refinery is to make this whole process easier and to provide some of the latest scalable versions of these learning algorithms in an intuitive web-based interface. Refinery is also meant to be run locally, thus bypassing the need for securing document collections over the internet. The talk will go through some of the technologies involved and a demo of the app.&lt;br /&gt;
&lt;br /&gt;
For more info check out http://www.docrefinery.org.&lt;br /&gt;
&lt;br /&gt;
==Drupal 8 — Evolution &amp;amp; Revolution==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Drupal 8 is in beta and nearing release. Among its many features, it notably has become more developer friendly through its adoption of the Symfony PHP framework along with Symfony's outstanding set of libraries (like Guzzle) and tools (like Composer). And, in implementing the Twig theming system, it is can begin to escape PHPtemplate. These moves also make it easier to create headless systems that uses Angular.js and other systems for presentation, or even forgo presentation entirely.&lt;br /&gt;
&lt;br /&gt;
From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.&lt;br /&gt;
&lt;br /&gt;
==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==&lt;br /&gt;
 &lt;br /&gt;
* [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]],  stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]&lt;br /&gt;
&lt;br /&gt;
GameSalad is a popular tool for developing mobile and desktop games with little actual programming. In this presentation, Stan Bogdanov breaks down the development process he followed while building [https://github.com/stanrb/mobiLit mobiLit], a mobile app with the goal of being the first open-source gamified information literacy app to be used as part of a college-level information literacy curriculum. He will go through the basics of using GameSalad to create an app that can be easily customized by non-programmers and the instructional principles used to teach the material in a mobile medium. Stan will also go through two qualitative design studies he did on the app and discuss their results and the lessons learned from building mobiLit. The session will conclude with an overview of the next steps for the [https://github.com/stanrb/mobiLit mobiLit project].&lt;br /&gt;
&lt;br /&gt;
==The Impossible Search: Pulling data from multiple unknown sources==&lt;br /&gt;
 &lt;br /&gt;
* Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com &lt;br /&gt;
&lt;br /&gt;
It's easy to search data you know the structure of, but what if you need to pull in data from sources that don't have a standard structure. The ability to search community events along with your standard catalog search results is an example, but often the only way to pull these events is through XML, JSON, (Insert structured format here), or even just raw html. But how do you get that structure? That simple question is what makes this impossible. The process to define and process this structure takes a lot of manual labor, especially if the data you are pulling is just HTML, and then every time you add data to the index you have to run all the data through a script to pull in data in a format Solr or an other index can use. This talk will focus on Solr, but the principles explained will apply to many other indexes.&lt;br /&gt;
&lt;br /&gt;
==What! You're Not Using Docker?==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Boring part: Docker[1] is a container system that provides benefits similar to virtualization with only a fraction of the overhead. Scintillating part: Docker can host between four to six times the number of service instances than systems such as Xen or VMWare on a given piece of hardware. But thats not all! Docker also makes it simple(r) to create transportable instances, so you can spin up development servers on your laptop.&lt;br /&gt;
&lt;br /&gt;
*[1]https://www.docker.com/&lt;br /&gt;
&lt;br /&gt;
== Video Accessibility, WebVTT, and Timed Text Track Tricks ==&lt;br /&gt;
&lt;br /&gt;
* Jason Ronallo, jronallo@gmail.com, NCSU Libraries&lt;br /&gt;
&lt;br /&gt;
Video on the Web presents new challenges and opportunities. How do you make your video more accessible to those with various disabilities and needs? I'll show you how. This presentation will focus on how to write and deliver captions, subtitles, audio descriptions, and timed metadata tracks for Web video using the WebVTT W3C standard. Encoding timed text tracks in this way opens up opportunities for new functionality on your websites beyond accessibility. The presentation will show some examples of the potential for using timed text tracks in creative ways. I'll cover all the HTML and JavaScript you will need to know as well as some of the CSS and other bits you could probably do without but are too fun to pass up.&lt;br /&gt;
&lt;br /&gt;
== Categorizing Records with Random Forests ==&lt;br /&gt;
 &lt;br /&gt;
* Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library&lt;br /&gt;
Academic libraries are increasingly responsible for providing ingest, search, discovery, and analysis for data sets.  Emerging techniques from data science and machine learning can provide librarians and developers with an opportunity to generate new insights and services from these document collections.  This presentation will provide a brief overview of common machine learning classification techniques, then dive into a more detailed example using a random forest to assign keywords to research data sets.  The talk will emphasize the insight that can be gained from machine learning rather than the inner workings of the algorithms.  The overall goal of this presentation is to provide librarians and developers with the context to recognize an opportunity to apply machine learning categorization techniques at their home campuses and organizations.  &lt;br /&gt;
&lt;br /&gt;
== Data Science in Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Devon Smith, smithde@oclc.org, OCLC&lt;br /&gt;
&lt;br /&gt;
Data Science is increasing in buzz and hype. I'll go over what it is, what it isn't, and how it fits in libraries.&lt;br /&gt;
&lt;br /&gt;
== PDF metadata extraction for academic literature == &lt;br /&gt;
&lt;br /&gt;
* Kevin Savage, kevin.savage at mendeley.com, Mendeley&lt;br /&gt;
* Joyce Stack, joyce.stack at mendeley.com, Mendeley&lt;br /&gt;
&lt;br /&gt;
Mendeley recently added a, &amp;quot;document from file,&amp;quot; endpoint to its API which attempts to extract metadata such as title and authors directly from PDF files. This talk will describe at a high level the machine learning methods we used including how we measured and tuned our model. We will then delve more deeply into our stack, the tools we used, some of the things that didn't work and why PDFs are the worst thing ever to compute over.&lt;br /&gt;
&lt;br /&gt;
== Giving Users What They Want: Record Grouping in VuFind ==&lt;br /&gt;
 &lt;br /&gt;
* Mark Noble,  mark@marmot.org, [//www.marmot.org Marmot Library Network]&lt;br /&gt;
&lt;br /&gt;
In 2013, Marmot did extensive usability studies with patrons to determine what was difficult in the catalog.  Many patrons had problems sifting through all of the various formats and editions of a title.  In 2014 we developed a method for [//mercury.marmot.org/Union/Search?lookfor=divergent grouping records] so only a single work is shown in search results and all formats and editions are listed under that work.  We will discuss our definition of a 'work' based on FRBR principles; combining meta data from MARC records with metadata from other sources like OverDrive; the technical details of Record Grouping; the design decisions made during implementation; and the reaction from users and staff.&lt;br /&gt;
&lt;br /&gt;
== Topic Space: a mobile augmented reality recommendation app ==&lt;br /&gt;
&lt;br /&gt;
* Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign&lt;br /&gt;
&lt;br /&gt;
The Topic Space module (http://minrvaproject.org/modules_topicspace.php ) was developed with an IMLS Sparks! Grant to investigate augmented reality technologies for in-library recommendations. The funding allowed for sustained university community collaboration by the University Library, the Graduate School of Library and Information Science, as well as graduate student programmers sourced from the Department of Computer Science. Collaborators designed app functionality and identified relevant open source libraries that could power optical character recognition (OCR) functionality from within the mobile phone.&lt;br /&gt;
&lt;br /&gt;
Topic space allows a user to take a picture of an item's call number in the book stacks. The module will show the user other books that are relevant but that are not shelved nearby. It can also show users books that are normally shelved here but that are currently checked out. Recommendations are based on Library of Congress subject headings and ILS circulation data which indicate recommendation candidates based on total check-outs. &lt;br /&gt;
&lt;br /&gt;
Research questions included development of back end (server-side) pattern matching algorithms for recommendations, and a rapid formative evaluation of interface design that would provide optimal user experience for navigation of the book stacks as a context to recommendations.&lt;br /&gt;
&lt;br /&gt;
Along with the Topic Space native app, grant collaborators prototyped web based recommendations which could serve as a new way of providing readers advisory and “more like this” recommendations from discovery interfaces accessed through desktop browsers. Outcomes of the grant include the availability of the [https://play.google.com/store/apps/details?id=edu.illinois.ugl.minrva Topic Spaces module within Minrva app on the Android Play store] and an experimental [http://backbonejs.org/ Backbone.js] based [http://minrva-dev.library.illinois.edu Topic Space web app].&lt;br /&gt;
&lt;br /&gt;
== Leveling Up Your Git Workflow ==&lt;br /&gt;
&lt;br /&gt;
* Megan Kudzia, moneill@albion.edu, Albion College Library&lt;br /&gt;
* Kate Sears, eks11@albion.edu, Albion College Library&lt;br /&gt;
&lt;br /&gt;
Have you started experimenting with Git on your own, but now you need to include others in your projects? Learn from our mistakes! Transitioning from a one-person git workflow and repo structure, to a structure that includes multiple people (including student workers), is not for the faint of heart. We'll talk about why we decided to work this way, our path to developing a git culture amongst ourselves, conceptual and technical difficulties we've faced, what we learned, and where we are now. Also with pretty pictures (aka workflow drawings).&lt;br /&gt;
&lt;br /&gt;
== Drone Loaning Program: Because Laptops are so last century ==&lt;br /&gt;
&lt;br /&gt;
 * Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries&lt;br /&gt;
 * Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries&lt;br /&gt;
&lt;br /&gt;
At Univ. Maryland we are in the very early stages of looking into allowing our student body get their hands on a drone. Yes that's right we will let students take out a drone for n amount of hours to work on projects of their choosing. The talk will talk about the logistics of getting a program of this sort from concept to &amp;quot;Is the drone available?&amp;quot;. If people sign waivers we will also promise not to crash the drone into code4lib attendees.&lt;br /&gt;
&lt;br /&gt;
== Got Git? Getting More Out of Your GitHub Repositories ==&lt;br /&gt;
&lt;br /&gt;
 * Terry Brady, twb27@georgetown.edu, Georgetown University Library&lt;br /&gt;
&lt;br /&gt;
This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories. &lt;br /&gt;
&lt;br /&gt;
In additional to all of the great benefits of using Git for code management, the GitHub interface provides a powerful set of tools to showcase a project and to keep your users informed of developments to your project.  These tools can assist with marketing and outreach - turning your code repository into a focus of conversation!&lt;br /&gt;
&lt;br /&gt;
* [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]&lt;br /&gt;
* [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]&lt;br /&gt;
* [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]&lt;br /&gt;
* [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]&lt;br /&gt;
* Gists for code sharing&lt;br /&gt;
* Private Repositories and Organizational Groups&lt;br /&gt;
* Pull Request Conversation Tracking&lt;br /&gt;
* Customized Issue management&lt;br /&gt;
&lt;br /&gt;
== Quick Wins for Every Department in the Library - File Analyzer! ==&lt;br /&gt;
&lt;br /&gt;
 * Terry Brady, twb27@georgetown.edu, Georgetown University Library&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.&lt;br /&gt;
* Analyzing Marc Records for the Cataloging department&lt;br /&gt;
* Transferring ILS invoices for the University Account System for the Acquisitions department &lt;br /&gt;
* Delivering patron fines to the Bursar’s office for the Access Service department&lt;br /&gt;
* Summarizing student worker timesheet data for the Finance department&lt;br /&gt;
* Validating COUNTER compliant reports for the Electronic Resources department&lt;br /&gt;
* Generating ingest packages for the Digital Services department&lt;br /&gt;
* Validating checksums for the Preservation department&lt;br /&gt;
&lt;br /&gt;
Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!&lt;br /&gt;
&lt;br /&gt;
==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor&lt;br /&gt;
&lt;br /&gt;
The transition from paper maps to digital ones changed much more than the maps themselves; it changed the very foundation of how we work and how we find each other. Now maps are transforming again.  The Geospatial World is moving from GIS systems that are institutionally-focused, expensive, feature-burdened, and binds data into a complicated and demanding user-hostile interface. From this transition from digital to web-based digital geospatial tools has come growth and development in new forms of map-based investigative journalism, activism, scholarship, and business ventures. This talk will highlight the conditions and strategies that made these changes possible as a means to draw a path by which librarians through our own work may follow, dragons notwithstanding. &lt;br /&gt;
&lt;br /&gt;
== Building Your Own Federated Search ==&lt;br /&gt;
&lt;br /&gt;
* Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco&lt;br /&gt;
&lt;br /&gt;
Advances in modern browsers have created some interesting possibilities for federated search. This presentation will cover common techniques and pitfalls in building a federated search. We will discuss what principles guided our decisions when implementing our own federated search. We will show tools we've built and our findings from building and using experimental prototypes.&lt;br /&gt;
&lt;br /&gt;
Your higher education institution likely offers dozens of online resources for educators, students, researchers, and the public. And each of these online resources likely has its own search tool. But users can't be expected to search in dozens of different interfaces to find what they're looking for. A typical solution for this issue is federated search. &lt;br /&gt;
&lt;br /&gt;
==  Indexing Linked Data with LDPath ==&lt;br /&gt;
&lt;br /&gt;
* Chris Beer, cabeer@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
LDPath [1] is a simple query language for indexing linked open data, with support for caching, content negotiation, and integration with non-RDF endpoints. This talk will demonstrate the features and potential of the language and framework to index a resource with links into id.loc.gov, viaf.org, geonames.org, etc to build an application-ready document.&lt;br /&gt;
&lt;br /&gt;
[1] http://marmotta.apache.org/ldpath/language.html&lt;br /&gt;
&lt;br /&gt;
== Show Me the Money: Integrating an LMS with Payment Providers ==&lt;br /&gt;
 &lt;br /&gt;
* Josh Weisman,  Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group&lt;br /&gt;
&lt;br /&gt;
In order to provide an easy and convenient way for patrons to pay fines, we are exploring ways to integrate the library management system with online payment providers such as PayPal. With many LMS systems being designed and developed for the cloud, we should be able to provide the frictionless user experience our patrons have come to expect from online transactions. In this session we'll discuss strategies for integration and review a sample application which uses REST APIs from a library management system to integrate with PayPal.&lt;br /&gt;
&lt;br /&gt;
== Shibboleth Federated Authentication for Library Applications: ==&lt;br /&gt;
&lt;br /&gt;
* Scott Fisher, scott.fisher@ucop.edu, California Digital Library&lt;br /&gt;
* Ken Weiss, ken.weiss@ucop.edu, California Digital Library&lt;br /&gt;
&lt;br /&gt;
Shibboleth is the most widely-used method to provide single-sign-on authentication to academic applications where users come from many different institutions. Shibboleth, the InCommon education and research trust framework, and the SAML protocol comprise a very powerful - but very complicated - solution to this very complicated problem. Scott and Ken have implemented Shibboleth for multiple library applications. They will share their understanding of the good, the bad, and the underlying spaghetti that makes it all work. Ken will discuss some of the technical aspects of the solution, touching on optimal and non-optimal use cases, administrative challenges, and authorization concerns. Scott will describe the implementation pattern for multi-institution single-sign-on that the California Digital Library has evolved, using the recently released Dash application (http://dash.cdlib.org) as an example.&lt;br /&gt;
&lt;br /&gt;
==Scientific Data: A Needs Assessment Journey==&lt;br /&gt;
 &lt;br /&gt;
*[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History&lt;br /&gt;
&lt;br /&gt;
While surveying digital research and collections data in the research science divisions at the American Museum of Natural History in NYC (as a part of my [http://ndsr.nycdigital.org/ National Digital Stewardship Residency] project), I have come across the big data hogs (genome sequencing and CT scanning) and the little pieces of data (images, publications), all equally important to not only scientific discovery, but as nodes in the history of science. &lt;br /&gt;
&lt;br /&gt;
In this session, I will discuss the development of my needs assessment surveys for scientific datasets and the interview process with Museum curators and researchers as background, seguing into an explanation of the results. I will then combine my findings into preliminary selection criteria to choose tools for digital preservation and management unique to scientific datasets. This will brooke a discussion on emerging standards, tools, and technologies in big data, specific to research science. &lt;br /&gt;
&lt;br /&gt;
I will conclude with preliminary findings on emerging technology that can be used to answer concerns surrounding the management and digital preservation of these data. I am hoping the Q&amp;amp;A session can be used to both answer questions about my project, and function as a way for you (the larger tech-savy library community)  to discuss the tools I’ve touched on in this talk. &lt;br /&gt;
&lt;br /&gt;
== Feminist Human Computer Interaction (HCI) in Library Software ==&lt;br /&gt;
 &lt;br /&gt;
* Bess Sadler,  bess@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
Libraries are not neutral repositories of knowledge. Library classification systems and search technologies tend to reflect the inequalities, biases, ethnocentrism, and power imbalances of the societies in which they are built [1]. How might we better resist these tendencies in the library software we create? This talk will examine some qualities of feminist HCI (pluralism, self-disclosure, participation, ecology, advocacy, and embodiment) [2] through the lens of library software. &lt;br /&gt;
&lt;br /&gt;
[1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.&lt;br /&gt;
&lt;br /&gt;
[2] Bardzell, Shaowen. Feminist HCI: Taking Stock and Outlining an Agenda for Design. CHI 2010: HCI For All. http://dmrussell.net/CHI2010/docs/p1301.pdf&lt;br /&gt;
&lt;br /&gt;
== Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==&lt;br /&gt;
&lt;br /&gt;
* Audrey Altman, audrey at dp.la, Digital Public Library of America&lt;br /&gt;
* Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America&lt;br /&gt;
* Mark Breedlove, mb at dp.la, Digital Public Library of America&lt;br /&gt;
&lt;br /&gt;
The Digital Public Library of America aggregates metadata for over 8 million objects from more than 24 direct partners, or Hubs, using its Metadata Application Profile (MAP), an RDF metadata application profile based on the Europeana Data Model. After working with the initial system for harvesting, mapping and enhancing our Hub’s metadata for a year, we realized that it was inadequate for working with data at this scale. There were architectural issues; it was opaque to non-developer and partner staff; there were inadequate tools for quality assurance and analysis; and the system was unaware that it was working with RDF data. As the network of Hubs expanded and we ingested more metadata, it became harder and harder to know when or why a harvest, a mapping task, or an enrichment went wrong because the tools for quality assurance were largely inadequate. &lt;br /&gt;
&lt;br /&gt;
The DPLA Content and Technology teams decided to develop a new system from the ground up to address those problems. Development of Heidrun, the internal version of the new system, started in October 2014. Heidrun’s goals are to make it easier for us to harvest and map metadata from various sources and in variety of schemas to the DPLA MAP, to better enrich that metadata using external data sources, and to actively involve our partners in the ingestion process through access to better QA tools. Heidrun and its componentry are built on Ruby on Rails, Blacklight, and ActiveTriples. Our presentation will give some background on our design principles and processes used during development, the architecture of the system, and its functionality. We plan to release a version of Heidrun and its components as a generalized metadata aggregation system for use by DPLA Hubs and others working to aggregate cultural heritage metadata.&lt;br /&gt;
&lt;br /&gt;
== OS or GTFO: Program or Perish ==&lt;br /&gt;
*Tessa Fallon, tessa.fallon@gmail.com&lt;br /&gt;
&lt;br /&gt;
Description TBD&lt;br /&gt;
&lt;br /&gt;
== Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==&lt;br /&gt;
* Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries&lt;br /&gt;
Would your library like to have large digital signage that displays dynamic information such as library hours, weather, room availability, and more? Have you looked into purchasing large digital signage, only to be turned off by the high price tag and lack of customization available with commercial solutions? Our library has developed a cheap and effective alternative to these systems using HTML 5 authoring software, a large TV, and freely-available APIs from Google, Springshare, and others. At this session, you’ll learn about the system that we have in place for displaying dynamic and easily-updatable information on our library’s large digital display, and how you can easily create something similar for your library.&lt;br /&gt;
&lt;br /&gt;
== REPOX: Metadata Blender ==&lt;br /&gt;
 &lt;br /&gt;
* John Mignault, jmignault@metro.org, Empire State Digital Network&lt;br /&gt;
&lt;br /&gt;
With the growth in the number of hubs providing metadata to the Digital Public Library of America, many of them are using REPOX, a tool originally created for the Europeana project, to aggregate disparate metadata feeds and transform them into formats suitable for ingest into DPLA. The Empire State Digital Network, the forthcoming DPLA service hub for NY state, is using it to prepare for our first ingest into DPLA in early 2015.  We'll take a look at REPOX and its capabilities and how it can be useful for ingesting and transforming metadata, and also discuss some things we've learned in massaging widely varied metadata feeds.&lt;br /&gt;
&lt;br /&gt;
== Beyond Open Source ==&lt;br /&gt;
&lt;br /&gt;
* Jason Casden, jmcasden@ncsu.edu, NCSU Libraries&lt;br /&gt;
* Bret Davidson, bddavids@ncsu.edu, NCSU Libraries&lt;br /&gt;
&lt;br /&gt;
The Code4Lib community has produced an increasingly impressive collection of open source software over the last decade, but much of this creative work remains out of reach for large portions of the library community. Do the relatively privileged institutions represented by a majority of Code4Lib participants have a professional responsibility to support the adoption of their innovations?&lt;br /&gt;
&lt;br /&gt;
Drawing from old and new software packaging and distribution approaches (from freeware to Docker), we will propose extending the open source software values of collaboration and transparency to include the wide and affordable distribution of software. We believe this will not only simplify the process of sharing our applications within the Code4Lib community, but also make it possible for less well resourced institutions to actually use our software. We will identify areas of need, present our experiences with the users of our own open source projects, discuss our attempts to go beyond open source, and make an argument for the internal value of supporting and encouraging a vibrant library ecosystem.&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]] &lt;br /&gt;
[[Category:Talk Proposals]]&lt;br /&gt;
&lt;br /&gt;
== Making It Work: Problem Solving Using Open Source at a Small Academic Library ==&lt;br /&gt;
 &lt;br /&gt;
* Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology&lt;br /&gt;
* Max King, mking9@iit.edu, Illinois Institute of Technology&lt;br /&gt;
&lt;br /&gt;
The Illinois Institute of Technology campus was added to the National Register of Historic Places in 2005, and contains a building, Mies van der Rohe's S.R. Crown Hall, that was named a National Historic Landmark in 2001. Creating a digital resource that can adequately showcase the campus and its architecture is challenge enough in and of itself, but doing so as a two-person team of relative newcomers, at a university library without dedicated programmers on staff, ups the ante considerably.&lt;br /&gt;
The challenges of technical know-how, staff time, and funding are nothing new to anyone working on digital projects at a university library, and are amplified when doing so at a smaller institution. This talk covers the conception, development, and design of the campus map site that was built, concentrating on the problem-solving strategies developed to cope with limited technical and financial resources.&lt;br /&gt;
We'll talk about our approach to development with Open Source software, including Omeka, along with the Neatline and Simile Timeline plugins. We'll also discuss the juggling act of designing for mobile mapping functionality without sacrificing desktop design, weighing the costs of increased functionality versus our ability to time-effectively include that functionality, and the challenge of building a site that could be developed iteratively, with an eye towards future enhancement and sustainability. Finally, we’ll provide recommendations for other librarians at smaller institutions for their own efforts at digital development.&lt;br /&gt;
&lt;br /&gt;
== Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==&lt;br /&gt;
 &lt;br /&gt;
* Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art&lt;br /&gt;
&lt;br /&gt;
The Museum of Modern Art has amassed a large collection of audiovisual materials over its many decades of existence. In order to preserve these materials, much of the audiovisual collection has been digitized. This is a complex process involving numerous steps and devices, and the methods used for digitization can have an effect on the quality of the file that is preserved. Therefore, knowing exactly how something was digitized is critical for future stewards of these objects to be able to properly care for and preserve them. However, detailed technical information about the processes involved in the digitization of audiovisual materials is not defined explicitly in most metadata schemas used for audiovisual materials. In order to record process history using existing metadata standards, some level of creativity is required to allow existing standards to express this information.&lt;br /&gt;
&lt;br /&gt;
This talk will detail different metadata standards, including PBCore, PREMIS, and reVTMD, that can be implemented as methods of recording this information. Specifically, the talk will examine efforts to integrate this metadata into the Museum of Modern Art’s new digital repository, the DRMC. This talk will provide background on the DRMC as well as MoMA’s specific institutional needs for process history metadata, then discuss different metadata implementations we have considered to document process history.&lt;br /&gt;
&lt;br /&gt;
== Pig Kisses Elephant: Building Research Data Services for Web Archives ==&lt;br /&gt;
 &lt;br /&gt;
* Jefferson Bailey,  jefferson@archive.org, Internet Archive&lt;br /&gt;
* Vinay Goel, vinay@archive.org, Internet Archive&lt;br /&gt;
&lt;br /&gt;
More and more libraries and archives are creating web archiving programs.  For both new and established programs, these archives can consist of hundreds of thousands, if not millions, of born-digital resources within a single collection; as such, they are ideally suited for large-scale computational study and analysis. Yet current access methods for web archives consist largely of browsing the archived web in the same manner as browsing the live web and the size of these collections and complexity of the WARC format can make aggregate analysis difficult. This talk will describe a project to create new ways for users and researchers to access and study web archives by offering extracted and post-processed datasets derived from web collections. Working with the 325+ institutions and their 2600+ collections within the Archive-It service, the Internet Archive is building methods to deliver a variety of datasets culled from collections of web content, including extracted metadata packaged in JSON, longitudinal link graph data, named entities, and other types of data. The talk will cover the technical details of building dataset production pipelines with Apache Pig, Hadoop, and tools like Stanford NER, the programmatic aspects of building data services for archives and researchers, and ongoing work to create new ways to access and study web archives.&lt;br /&gt;
&lt;br /&gt;
== Awesome Pi, LOL! ==&lt;br /&gt;
&lt;br /&gt;
* Matt Connolly, mconnolly@cornell.edu, Cornell University Library&lt;br /&gt;
* Jennifer Colt, jrc88@cornell.edu, Cornell University Library&lt;br /&gt;
&lt;br /&gt;
Inspired by Harvard Library Lab’s “Awesome Box” project, Cornell’s Library Outside the Library (LOL) group is piloting a more automated approach to letting our users tell us which materials they find particularly stunning. Armed with a Raspberry Pi, a barcode scanner, and some bits of kit that flash and glow, we have ventured into the foreign world of hardware development. This talk will discuss what it’s like for software developers and designers to get their hands dirty, how patrons are reacting to the Awesomizer, and LOL’s not-afraid-to-fail philosophy of experimentation.&lt;br /&gt;
&lt;br /&gt;
== You Gotta Keep 'em Separated: The Case for &amp;quot;Bento Box&amp;quot; Discovery Interfaces ==&lt;br /&gt;
 &lt;br /&gt;
* Jason Thomale,  jason.thomale@unt.edu, University of North Texas Libraries&lt;br /&gt;
&lt;br /&gt;
I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.&lt;br /&gt;
&lt;br /&gt;
The thing is, practically all of us--in academic libraries at least--have a similar set up for discovery, with just a few variations, and so talking about it still seems useful. Stop me if this sounds familiar. You've got a single search box on the library homepage as a starting point for discovery. And it's probably a tabbed affair, with an option for searching the catalog for books, an option for searching a discovery service for articles, an option for searching databases, and maybe a few others. Maybe you have an option to search everything at once--probably the default, if you have it. And, if you're a crazy hepcat, maybe you ''only'' have your one search that searches everything, with no tabs.&lt;br /&gt;
&lt;br /&gt;
Now, the question is, for your &amp;quot;everything&amp;quot; search, are you doing a combined list of results, or are you doing it bento-box style, with a short results list from each category displayed in its own compartment?&lt;br /&gt;
&lt;br /&gt;
At UNT, we've been holding off on implementing an &amp;quot;everything&amp;quot; search, for various reasons. One reason is that the evidence for either style hasn't been very clear. There's this persistent paradox that we just can't reconcile: users tell us, through word and action, that they prefer searching Google, yet, libraries aren't Google, and there are valid design reasons why we shouldn't try to oversimplify our discovery interfaces to be like Google. And there's user data that supports both sides.&lt;br /&gt;
&lt;br /&gt;
Holding off on making this decision has granted us 2 years of data on how people use our tabbed search interface that does ''not'' include an &amp;quot;everything&amp;quot; search. Recently I conducted a thorough analysis of this data--specifically the usage and query data for our catalog and discovery system (Summon). And I think it helps make the case for a bento box style discovery interface. To be clear, it isn't exactly the smoking gun that I was hoping for, but the picture it paints I think is telling. At the very least, it points away from a combined-results approach.&lt;br /&gt;
&lt;br /&gt;
I'm proposing a talk discussing the data we've collected, the trends we've seen, and what I think it all means--plus other reasons that we're jumping on the &amp;quot;bento box&amp;quot; discovery bandwagon and why I think &amp;quot;bento box&amp;quot; is at this point the path that least sells our souls.&lt;br /&gt;
&lt;br /&gt;
== Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift ==&lt;br /&gt;
 &lt;br /&gt;
* Ashley Blewer!, ashley.blewer@gmail.com&lt;br /&gt;
&lt;br /&gt;
Checksum technology is used all over the place, from git commits to authenticating Linux packages. It is most commonly used in the digital preservation field to monitor materials in storage for changes that will occur over time or used in the transmission of files during duplication. But do you even checksum, bro? I want this talk to move checksums from a position of mysterious macho jargon to something everyone can understand and want to use. I think a lot of people have heard of checksum but don’t know where to begin when it comes to actually using it at their institution. And cryptography is hella intimidating! This talk will cover what checksums are, how they can be integrated into a library or archival workflow, protecting collections requiring additional levels of security, algorithms used to verify file fixity and how they are different, and other aspects of cryptographic technology. Oh, and please note that all points in this talk will be emphasized or lightly performed through Taylor Swift lyrics. Seriously, this talk will consist of at least 50% Taylor Swift. Can you, like, even?&lt;br /&gt;
&lt;br /&gt;
== Level Up Your Coding with Code Club (yes, you can talk about it) ==&lt;br /&gt;
&lt;br /&gt;
* Coral Sheldon-Hess, coral@sheldon-hess.org&lt;br /&gt;
&lt;br /&gt;
Reading code is a necessary part of becoming a better developer. It gives you more experience and more insight into How Things Are (or Aren't) Done; it builds your intuition about how to solve problems with code; and it increases your confidence that you, too, can tackle whatever technological problems you're facing.&lt;br /&gt;
&lt;br /&gt;
But you don't have to read code alone! (Which is good. It's really not fun to read code alone.) &lt;br /&gt;
&lt;br /&gt;
In late 2014, a group of librarians formed two Code Clubs, inspired by [http://bloggytoons.com/code-club/ this talk by Saron] (of Bloggytoons fame). I'd like to tell you about how we've structured our Code Clubs, what has gone well, what we've learned, and what you need to do to form your own Code Club. I'll share a list of the codebases we've looked at, too, to help you get your own Code Club off the ground! &lt;br /&gt;
&lt;br /&gt;
== The Growth of a Programmer ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:jgo | Joshua Gomez]], Getty Research Institute, jgomez@getty.edu&lt;br /&gt;
&lt;br /&gt;
Just like other creative endeavors, software developers can experience periods of great productivity or find themselves in a rut. After contemplating the alternating periods in my own career I've noticed several factors that have effected my own professional growth and happiness, including: mentorship, structure, community, teamwork, environment, formal education, etc. Not all of the factors need to be present at all times; but some mixture of them is critical for continued growth. In this talk, I will articulate these factors, discuss how they can effect a developer's career, and how they can be sought out when missing. This talk is aimed at both new developers looking to strike their own path as well as the veterans that lead or mentor them.&lt;br /&gt;
&lt;br /&gt;
== Developing a Fedora 4.0 Content Model for Disk Images ==&lt;br /&gt;
&lt;br /&gt;
* Matthew Farrell, matthew.j.farrell@duke.edu, Duke University Libraries&lt;br /&gt;
* Alexandra Chassanoff, achass@email.unc.edu, BitCurator Access Project Manager&lt;br /&gt;
&lt;br /&gt;
As the acquisition of born-digital materials grows, institutions are seeking methods to facilitate easy ingest into their repositories and provide access to disk images and files derived or extracted from disk images. In this session, we describe our development of a Fedora 4.0 Content model for disk images, including acceptable image file formats and the rationale behind those choices.  We will also discuss efforts to integrate the disk image content model into the BitCurator Access environment. Unlike generalized, format-agnostic content models which might treat the disk image as a generic bitstream, a content model designed for disk images enables expression of relationships among associated content in the collection such as files extracted from images and other born-digital and digitized material associated with the same creator.  It also enables capture of file-system attributes such as file paths, timestamps, whether files are allocated/deleted, etc.  Further, a disk image content model suggests further steps repositories can take in order to transform and re-use associated metadata generated during the creation and forensic analysis of the disk image.&lt;br /&gt;
&lt;br /&gt;
== Data acquisition and publishing tools in R ==&lt;br /&gt;
&lt;br /&gt;
* Scott Chamberlain,  scott@ropensci.org, rOpenSci/UC Berkeley - first-time presenter&lt;br /&gt;
&lt;br /&gt;
R is an open source programming environment that is widely used among researchers in many fields. R is powerful because it's free, increasingly robust, and facilitates reproducible research, an increasingly sought after goal in academia. Although tools for data manipulation/visualization/analysis are well developed in R, data acquisition and publishing tools are not. rOpenSci is a collaborative effort to create the tools necessary to complete the reproducible research workflow. This presentation discusses the need for these tools, including examples, including interacting with the repositories Mendeley, Dryad, DataONE, and Figshare. In addition, we are building tools for searching scholarly metadata and acuiring full text of open access articles in a standarized way across metadata providers (e.g., Crossref, DataCite, DPLA) and publishers (e.g., PLOS, PeerJ, BMC, Pubmed). Last, we are building out tools for data reading and writing in Ecologial Metadata Language (EML).&lt;br /&gt;
&lt;br /&gt;
== SPLUNK: Log File Analysis ==&lt;br /&gt;
&lt;br /&gt;
* Jim LeFager, jlefager@depaul.edu, DePaul University Library&lt;br /&gt;
DePaul University Library recently took over monitoring and maintaining of the library EZproxy servers this past year and using Splunk, a machine data analysis tool, we are able to gather information and statistics on our electronic resource usage in addition to monitoring the servers. Splunk is a tool that can collect, analyze, and visualize log files and other machine data in real time and this has allowed for gathering realtime usage statistics for our electronic resources allowing us to filter by multiple facets including IP Range, Group Membership (student, faculty), so that we can see who is accessing our resources and from where. Splunk allows our library to query our data and create rich custom dashboards as well as create alerts that can be triggered when certain conditions are met, such as error codes, which can send an email alert to a group of users. We will be leveraging Splunk to monitor all library web applications going forward. This talk will review setting up Splunk and best practices in using the available features and customizations available including creating queries, alerts, and custom dashboards.  &lt;br /&gt;
&lt;br /&gt;
== Your code does not exist in a vacuum ==&lt;br /&gt;
* Becky Yoose, yoosebec at grinnell dot edu, Grinnell College (Done a lightning talk, MC duties, but have not presented a prepared talk)&lt;br /&gt;
&lt;br /&gt;
“If you have something to say, then say it in code…” - Sebastian Hammer, code4lib 2009&lt;br /&gt;
&lt;br /&gt;
In its 10 year run, code4lib has covered the spectrum of libtech development, from search to repositories to interfaces. However, during this time there has been little discussion about this one little fact about development - code does not exist in a vacuum. &lt;br /&gt;
&lt;br /&gt;
Like the comment above, code has something to say. A person’s or organization’s culture and beliefs influences code in all steps of the development cycle. What development method you use, tools, programming languages, licenses - everything is interconnected with and influenced by the philosophies, economics, social structures, and cultural beliefs of the developer and their organization/community.&lt;br /&gt;
&lt;br /&gt;
This talk will discuss these interconnections and influences when one develops code for libraries, focusing on several development practices (such as “Fail Fast, Fail Often” and Agile)   and licensing choices (such as open source) that libtech has either tried to model or incorporate into mainstream libtech practices. It’ll only scratch the surface of the many influences present in libtech development, but it will give folks a starting point to further investigate these connections at their own organizations and as a community as a whole.&lt;br /&gt;
&lt;br /&gt;
tl;dr - this will be a messy theoretical talk about technology and libraries. No shiny code slides, no live demos. You might come out of this talk feeling uncomfortable. Your code does not exist in a vacuum. Then again, you don’t exist in a vacuum either.&lt;br /&gt;
&lt;br /&gt;
== The Metadata Hopper: Mapping and Merging Metadata Standards for Simple, User-Friendly Access ==&lt;br /&gt;
&lt;br /&gt;
* Tracy Seneca, tjseneca@uic.edu, University of Illinois at Chicago&lt;br /&gt;
* Esther Verreau: verreau1@uic.edu, University of Illinois at Chicago&lt;br /&gt;
&lt;br /&gt;
The Chicago Collections Consortium: 15 institutions and growing!  8 distinct EAD standards! At least 3 permutations of MARC, and we lost count of the varieties of custom CONTENTdm image collections.  Not to mention the 14,730 unique subject terms, nearly all of which lead our poor end-users to exactly one organization's content. &lt;br /&gt;
&lt;br /&gt;
All large content aggregation projects have faced this challenge, and there are a few emerging tools to help us wrangle disparate metadata into new contexts.  The Metadata Hopper is one such tool. The Metadata Hopper enables archivists to map their local metadata standards to standardized deposit records, and tags those materials using a shared vocabulary, integrating them into a user-friendly portal without disrupting local practices. In last year's Code4Lib lightning talk we described the challenges that the Chicago Collections Consortium faces in creating shared, in-depth access to archival and digital collections about Chicago history and culture across CCC member organizations. This year, thanks to the Andrew W. Mellon Foundation, we have a working Django application to demonstrate.  In this talk we'll discuss the design that enables multiple layers of flexibility, from the ability to accept a variety of metadata standards to designing for an open source audience.&lt;br /&gt;
&lt;br /&gt;
http://chicagocollectionsconsortium.org&lt;br /&gt;
&lt;br /&gt;
== Programmers are not projects: lessons learned from managing humans ==&lt;br /&gt;
&lt;br /&gt;
* Erin White, erwhite@vcu.edu, Virginia Commonwealth University - first-time presenter&lt;br /&gt;
&lt;br /&gt;
Managing projects is one thing, but managing people is another. Whether we’re hired as managers or grow “organically” into management roles, sometimes technical people end up leading technical teams (gasp!). I’ll talk about lessons I’ve learned about hiring, retaining, and working long-term and day-to-day with highly tech-competent humans. I’ll also talk about navigating the politics of libraryland, juggling different types of projects, and working with constrained budgets to make good things and keep talented people engaged.&lt;br /&gt;
&lt;br /&gt;
== Practical Strategies for Picking Low-Hanging Fruits to Improve Your Library's Web Usability and UX ==&lt;br /&gt;
&lt;br /&gt;
* Bohyun Kim, bkim@hshsl.umaryland.edu, University of Maryland, Baltimore&lt;br /&gt;
&lt;br /&gt;
Have you ever tried to fix an obvious (to you at least!) problem in Web usability or UX (user experience) only to face strong resistance from the library staff? Are you a strong advocate for making library resources, systems, services, and space as usable as possible, but do you often find yourself struggling to get the point across and/or obtain the crucial buy-in from colleagues and administrators? &lt;br /&gt;
&lt;br /&gt;
There is no shortage of Web usability and UX guidelines. But applying them to a library and implementing desired changes often involve a long and slow process. To tackle this issue, this talk will focus on how to utilize the 'expert review' process (aka 'heuristic evaluation') as a preliminary or even preparatory step before embarking on more time-and-labor-intensive usability testing and user research. Several examples from  simple fixes to more nuanced usability and UX issues in libraries will be discussed to your heart's content. The goal of this talk is to provide practical strategies for picking as many low-hanging fruits as possible to make a real (albeit small) difference to your library's Web usability and UX effectively and efficiently.&lt;br /&gt;
&lt;br /&gt;
== A Semantic Makeover for CMS Data ==&lt;br /&gt;
&lt;br /&gt;
* Bill Levay, wjlevay@gmail.com, Linked Jazz Project&lt;br /&gt;
&lt;br /&gt;
How can we take semi-structured but messy metadata from a repository like CONTENTdm and transform it into rich linked data? Working with metadata from Tulane’s Hogan Jazz Archive Photography Collection, the Linked Jazz Project used Open Refine and Python scripts to tease out proper names, match them with name authority URIs, and specify FOAF relationships between musicians who appear together in photographs. Additional RDF triples were created for any dates associated with the photos, and for those images with place information we employed GeoNames URIs. Historical images and data that were siloed can now interact with other datasets, like Linked Jazz’s rich set of names and personal relationships, and can be visualized [link to come] or otherwise presented on the web in any number of ways. I have not previously presented at a Code4Lib conference.&lt;br /&gt;
&lt;br /&gt;
== Taking User Experience (UX) to new heights ==&lt;br /&gt;
 &lt;br /&gt;
* Kayne Richens, kayne.richens@deakin.edu.au, Deakin University&lt;br /&gt;
&lt;br /&gt;
User Experience, or &amp;quot;UX&amp;quot;, is for more than just websites. At Deakin University Library we're exploring ways to improve the user experience inside our campus library spaces, by putting new technologies front and centre in the overall experience for our students. How are we doing this? We’re collaborating with the University's IT department and exploring the following Library-changing opportunities:&lt;br /&gt;
&lt;br /&gt;
- Augmented Reality for Way-finding: We’re tackling that infamous thing that all Libraries can't get right – way-finding. We're enhancing library tour information and way-finding experiences by introducing augmented reality solutions.&lt;br /&gt;
 &lt;br /&gt;
- Heat mapping the library with wi-fi: We’re using our existing wi-fi infrastructure to present &amp;quot;heat maps&amp;quot; of library space utilisation, allowing our users to easily locate the space that best suits their needs, whether it be busy spaces to collaborate, or quiet spaces to study. And by overlaying computer usage and group study room bookings, users can quickly locate the space they need.&lt;br /&gt;
 &lt;br /&gt;
- Video chat library service: We’re piloting video-conferencing facilities in our group study rooms and spaces, connecting users and librarians and other professionals.&lt;br /&gt;
         &lt;br /&gt;
This talk will look at how these different technologies will be brought together to provide improved user experiences, as well some of the evidence and reasons that helped us to identify our needs, so you can too.&lt;br /&gt;
&lt;br /&gt;
==How to Hack it as a Working Parent: or, Should Your Face be Bathed in the Blue Glow of a Phone at 2 AM?==&lt;br /&gt;
&lt;br /&gt;
*Margaret Heller, Loyola University Chicago, mheller1@luc.edu&lt;br /&gt;
*Christina Salazar, California State University Channel Islands, christina.salazar@csuci.edu&lt;br /&gt;
*May Yan, Ryerson University, may.yan@ryerson.ca&lt;br /&gt;
&lt;br /&gt;
Modern technology has made it easier than ever for parents employed in technical environments to keep up with work at all hours and in all locations. This makes it possible to work a flexible schedule, but also may lead to problems with work/life balance and furthering unreasonable expectations about working hours. Add to that shifting gender roles and limited paid parental leave in the United States and you have potential for burnout and a certainty for anxiety. It raises the additioal question of whether the “always connected” mindset puts up a barrier to some populations who otherwise might be better represented in open source and library technology communities. &lt;br /&gt;
&lt;br /&gt;
This presentation will address tools that are useful for working parents in technical library positions, and share some lessons learned about using these tools while maintaining a reasonable work/life balance. We will consider a question that Karen Coyle raised back in 1996: &lt;br /&gt;
“What if the thousands of hours of graveyard shift amateur hacking wasn't really the best way to get the job done? That would be unthinkable.” &lt;br /&gt;
&lt;br /&gt;
For those who are able to take an extended parental leave, we will present strategies for minimizing the impact to your career and your employer. For those (particularly in the United States) who are only able to take a short leave will require different strategies. Despite different levels of preparation, all are useful exercises in succession planning and making a stronger workplace and future ability to work a flexible schedule through reviewing workloads, cross-training personnel, hiring contract replacements, and creative divisions of labor. Such preparation makes work better for everyone, kids or no kids.&lt;br /&gt;
&lt;br /&gt;
==Making your digital objects embeddable around the web==&lt;br /&gt;
 &lt;br /&gt;
* Jessie Keck, jkeck@stanford.edu, Stanford University Libraries&lt;br /&gt;
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
With more and more content from our digital repositories making their way into our discovery environments we quickly realize that we’re repeatedly re-inventing the wheel when it comes to creating “Viewers” for these digital objects.  With various different types of viewers necessary (books, images, audio, video, geospatial data, etc) the burden of getting these viewers into various environments (topic guides, blogs, catalogs, etc) becomes exponential.&lt;br /&gt;
&lt;br /&gt;
In this talk we’ll discuss how Stanford University Libraries implemented an oEmbed service to create an extensible viewer framework for all of its digital content. Using this service we’ve been able to easily integrate viewers into various discovery applications as well as make it easy for end users who discover our objects to easily embed customized versions into their own websites and blogs.&lt;br /&gt;
&lt;br /&gt;
==So you want to make your geospatial data discoverable==&lt;br /&gt;
 &lt;br /&gt;
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
Finding data for research or coursework can be one of the most time intensive tasks for a scholar or student. We introduce GeoBlacklight, an open source, multi-institutional software project focused on solving these common challenges at institutions across the world. GeoBlacklight prioritizes user experience, integrates with many GIS tools, and streamlines the use and organization of geospatial data. This talk will provide an introduction to the software, demonstrate current functionality, and provide a road map for future work.&lt;br /&gt;
&lt;br /&gt;
== Clueless-Driven Development: How I learned to migrate to Fedora 4 ==&lt;br /&gt;
&lt;br /&gt;
* Adam Wead, awead@psu.edu, Penn State University&lt;br /&gt;
&lt;br /&gt;
Recently I was tasked with migrating the content from our Fedora3 repository to the new Fedora4 repository architecture.&lt;br /&gt;
Despite a wealth of community support, I had no idea how to approach, or even begin to solve this problem. I knew I&lt;br /&gt;
wanted to follow best practices and use test-driven  development to build my solution, but had no idea where to start.&lt;br /&gt;
Despite this initial setback, I was able to start writing tests with only a  vague understanding of the problem. As my&lt;br /&gt;
tests exposed where my understanding of the problem was flawed, my code evolved, and within a week I had arrived  at a&lt;br /&gt;
working solution that exhibited all the hallmarks of good testing and software design.&lt;br /&gt;
&lt;br /&gt;
This talk recounts the process I went through from starting with practically nothing, to arriving at a working solution.&lt;br /&gt;
You can follow the rules of  test-driven development, but you can write tests in an expressive way to describe the&lt;br /&gt;
problem instead of just describing what the code should do. It was also essential to begin testing from an integration&lt;br /&gt;
viewpoint as opposed to a unit one, because at the outset the units were unknown and were later realized through further&lt;br /&gt;
development. For the presentation, I will be demonstrating using RSpec and Ruby. All the code examples will be related&lt;br /&gt;
to the Hydra software stack; however, I hope to show  that the processes at work will be applicable in any context.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Designing and Leading a Kick A** Tech Team ==&lt;br /&gt;
 &lt;br /&gt;
* Sibyl Schaefer,  sschaefer@rockarch.org, Rockefeller Archive Center&lt;br /&gt;
&lt;br /&gt;
New managers are often promoted without receiving management training, yet management is not something you just figure out. The experience of being expected to know how to manage, yet not being trained to do so often results in new managers feeling isolated and unsure how to move from making to managing. In this talk I’ll focus on my own managerial experience of designing and leading an archival tech team in a small independent archives. Topics covered will include hiring, delegating, creating a team culture, and leading people whose specialized knowledge exceeds your own. The talk take-aways should be applicable to managers and employees at large and small institutions alike.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==American (Archives) Horror Story: LTO Failure and Data Loss ==&lt;br /&gt;
 &lt;br /&gt;
* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH&lt;br /&gt;
* Casey Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH&lt;br /&gt;
&lt;br /&gt;
Here’s a story to send shivers down archival spines: when transferring video files off LTO for the American Archive project, WGBH got an initial failure rate of 57%.   After repeat tries, the rates improved; still, an unnervingly large percentage of files were never able to be transferred successfully.   Even more unnerving, going public with our horror story got a big response from other archives using LTO -- it seems like many institutions are having similarly scary results.   What are the real risks with LTO tape?  Are there steps that archives should be taking to better circumvent those risks?  This presentation will share information about LTO storage failures across archives world and discuss the process of investigating the problem at WGBH by testing different methods of data retrieval from LTO (direct and networked downloads, individual file retrieval and bulk data dump, use of LTO 4 and LTO 6 decks) and using checksum comparisons and file analysis and characterization tools such as ffprobe, mediainfo and exiftool to analyze failed files.  We'll also present whatever results we’ve managed to turn up by the time of Code4Lib!&lt;br /&gt;
&lt;br /&gt;
== PBCore in Action: Three Words, Not Two! ==&lt;br /&gt;
 &lt;br /&gt;
* Casey E. Davis,  casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting, WGBH&lt;br /&gt;
* Andrew (Drew) Myers, andrew_myers@wgbh.org, Supervising Developer, WGBH&lt;br /&gt;
&lt;br /&gt;
In 2001, public media representatives developed the PBCore XML schema to establish a common language for managing metadata about their analog and digital audio and video. Since then, PBCore has been adopted by a number of organizations and archivists in the moving image archival community. The schema has also undergone a few revisions, but on more than one occasion it was left orphaned and with little to no support.&lt;br /&gt;
 &lt;br /&gt;
Times have changed. You may have heard the news that PBCore is back in action as part of the American Archive of Public Broadcasting initiative and via the Association of Moving Image Archivists (AMIA) PBCore Advisory Subcommittee. A group of archivists, public media stakeholders, and engaged users have come together to provide necessary support for the standard and to see to its further development.&lt;br /&gt;
 &lt;br /&gt;
At this session, I'll discuss the scope and uses of PBCore in digital preservation and access, report on the progress and goals of the PBCore Advisory Subcommittee, and share how the group (by the time of the conference) will have transformed the XML schema into an RDF ontology, bringing PBCore into the second decade of the 21st century. #PBHardcore&lt;/div&gt;</summary>
		<author><name>Afred</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&amp;diff=41967</id>
		<title>2015 Prepared Talk Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&amp;diff=41967"/>
				<updated>2014-11-07T17:22:04Z</updated>
		
		<summary type="html">&lt;p&gt;Afred: /* American (Archives) Horror Story: LTO Failure and Data Loss */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Code4lib 2015 is a loosely-structured conference that provides people working at the intersection of libraries/archives/museums/cultural heritage and technology with a chance to share ideas, be inspired, and forge collaborations. For more information about the Code4lib community, please visit http://code4lib.org/about/. &lt;br /&gt;
The conference will be held at the Portland Hilton &amp;amp; Executive Tower in Portland, Oregon, from February 9-12, 2015.&lt;br /&gt;
&lt;br /&gt;
'''Proposals for Prepared Talks:'''&lt;br /&gt;
&lt;br /&gt;
We encourage everyone to propose a talk.&lt;br /&gt;
 &lt;br /&gt;
Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:&lt;br /&gt;
* Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software&lt;br /&gt;
* Tools and technologies – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)&lt;br /&gt;
* Technical issues - Big issues in library technology that should be addressed or better understood&lt;br /&gt;
* Relevant non-technical issues – Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc.&lt;br /&gt;
&lt;br /&gt;
Proposals can be submitted through Friday, November 7, 2014 at 5pm PST (GMT−8). Voting will start on November 11, 2014 and continue through November 25, 2014. The URL to submit votes will be announced on the Code4Lib website and mailing list and will require an active code4lib.org account to participate. The final list of presentations will be announced in early- to mid-December.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Proposals for Prepared Talks:'''&lt;br /&gt;
&lt;br /&gt;
Log in to the Code4lib wiki and edit this wiki page using the prescribed format. If you are not already registered, follow the instructions to do so.&lt;br /&gt;
Provide a title and brief (500 words or fewer) description of your proposed talk.&lt;br /&gt;
If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist voters in opening the conference to new presenters.&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Talk Title: ==&lt;br /&gt;
 &lt;br /&gt;
* Speaker's name,  email address, and (optional) affiliation&lt;br /&gt;
* Second speaker's name, email address, and affiliation, if second speaker&lt;br /&gt;
&lt;br /&gt;
Abstract of no more than 500 words.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Talk Proposals'''&lt;br /&gt;
== Zines + Gamification = Awesomest Metadata Literacy Outreach Event Ever! ==&lt;br /&gt;
 &lt;br /&gt;
* Jennifer Hecker, jenniferraehecker@gmail.com, University of Texas Libraries &amp;amp; Austin Fanzine Project&lt;br /&gt;
* Lillian Karabaic, librarian@iprc.org, Independent Publishing Resource Center (Portland)&lt;br /&gt;
 &lt;br /&gt;
In academic libraries, and elsewhere, the popularity of zine (a magazine produced for love, not profit) collections is on the rise. At the same time, metadata literacy is becoming an increasingly important skill, helping people navigate and understand digital environments and interactions. We have found a way to teach metadata literacy to the general public that isn’t super-boring – in fact, we’ve made it downright fun!&lt;br /&gt;
&lt;br /&gt;
First, volunteer zine librarian Lillian Karabaic of Portland’s Independent Publishing Resource Center facilitated the creation of a gamified cataloging interface for the IPRC’s annual Raiders of the Lost Archives backlog-busting 24-hour volunteer cataloging event.&lt;br /&gt;
&lt;br /&gt;
Then, archivist Jennifer Hecker facilitated the adaptation of the IPRC’s game for use in a similar, but also very different context – promoting UT Libraries newly-acquired zine collections. The main goal of the academic-library-based event was increasing excitement around the collections, but with the side goal of building metadata literacy, and introducing an understanding of library cataloging issues.&lt;br /&gt;
&lt;br /&gt;
The Texas modification also conforms to the xZINECOREx metadata schema developed by the national Zine Librarians Interest Group, and triggered interesting conversations with the Libraries’s cataloging department about evolving metadata standards and how to incorporate the products of crowd-sourcing projects into existing workflows.&lt;br /&gt;
&lt;br /&gt;
Both games will be demoed.&lt;br /&gt;
&lt;br /&gt;
== Do the Semantic FRBRoo ==&lt;br /&gt;
* Rosie Le Faive, rlefaive@upei.ca, University of Prince Edward Island&lt;br /&gt;
&lt;br /&gt;
[http://www.islandora.ca Islandora] is great for creating repositories of any data type, but how can you model meaningful relationships between digital objects and use them to tell a story?&lt;br /&gt;
&lt;br /&gt;
At UPEI, I’m assembling an ethnography of Prince Edward Island’s traditional fiddle music that includes musical clips, video clips, oral histories, musical notation, images, and ethnographic commentaries. In order to present an exhibition-style site, I’m tying these digital objects together via the people, places, events, tunes and topics that they share or describe. &lt;br /&gt;
&lt;br /&gt;
To describe the relationships, I’m extending Islandora to use [http://www.cidoc-crm.org/frbr_inro.html FRBRoo], a vocabulary that combines the FRBR model with CIDOC-CRM, the the object-oriented museum documentation ontology. These modules being developed will allow other researchers to create a structured, navigable digital repository of diverse object types, that uses Islandora as an exhibition platform. &lt;br /&gt;
&lt;br /&gt;
== Our $50,000 Problem: Why Library School? ==&lt;br /&gt;
* Jennie Rose Halperin, jhalperin@mozilla.com, Mozilla Corporation&lt;br /&gt;
&lt;br /&gt;
57 library schools in the United States are churning out approximately 100 graduates per year, many with debt upwards of $50,000.  According to ONet, [http://www.inthelibrarywiththeleadpipe.org/2011/is-the-united-states-training-too-many-librarians-or-too-few-part-1/ 84% of library jobs in the US require an MLS.] The library profession is [http://dpeaflcio.org/programs-publications/issue-fact-sheets/library-workers-facts-figures/) 92% white and 82% female and entry-level librarians can expect to make $32,500 per year.]&lt;br /&gt;
&lt;br /&gt;
Contrasted with developers, who are almost [http://www.ncwit.org/blog/did-you-know-demographics-technical-women 90% male] and can expect to make [http://www.forbes.com/sites/jennagoudreau/2011/06/01/best-entry-level-jobs/ $70,000 in an entry-level position,] these numbers are dismal.&lt;br /&gt;
&lt;br /&gt;
According to a recent survey, the top skill that outgoing library students want to know is “programming” and yet many MLS programs still consider Microsoft Word an essential technology skill.&lt;br /&gt;
&lt;br /&gt;
What is going on here? Why do we accept this fate, where mostly female debt-burdened professionals continue to be thrown onto the work force without the education their expensive degrees promised?&lt;br /&gt;
&lt;br /&gt;
As a community we need to come together to stop this cycle. We need to provide better support and mentorship to diversify and keep the profession relevant and help librarianship move into the future it deserves.&lt;br /&gt;
&lt;br /&gt;
This talk will walk through the challenges of navigating a hostile employment environment as well as present models for better development and future state imagining.&lt;br /&gt;
&lt;br /&gt;
== No cataloging software? Need more than Dublin Core? No problem!: Experiences with CollectiveAccess ==&lt;br /&gt;
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University&lt;br /&gt;
* Rachel Wittmann, rwittma@clemson.edu, Clemson University&lt;br /&gt;
&lt;br /&gt;
Clemson University Libraries has implemented the open-source software CollectiveAccess for customized digital collection needs. CollectiveAccess is an open-source project with the goal of providing a flexible way to manage and publish museum and archival collections. There are several applications associated with the projects; most used are: Providence (for cataloging and entering metadata) and Pawtucket (for displaying objects in a collection for the public). It has many profiles readily available for installing with existing library standards, such as Dublin Core, and there is a robust syntax for creating your own profiles to fit custom tailored metadata schemas. Plus, the user interface allows you to modify the metadata profile quickly and easily.&lt;br /&gt;
&lt;br /&gt;
In this talk, we will discuss:&lt;br /&gt;
* Our experiences with installing Providence and creating an installation profile that satisfies the needs of many of the Clemson Libraries digital archiving processes. &lt;br /&gt;
* The stumbling blocks experienced in that process and how they were resolved.&lt;br /&gt;
* The available plugins sourcing widely used authorities, such as Library of Congress thesauri and GeoNames.org, and how they have been used by our projects. &lt;br /&gt;
* A brief overview of the export and import functions and also current workflow practices within Providence.&lt;br /&gt;
* Future plans &amp;amp; the role of CollectiveAccess at Clemson University Libraries&lt;br /&gt;
&lt;br /&gt;
== Getting ContentDM and Wordpress to Play Together ==&lt;br /&gt;
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University&lt;br /&gt;
&lt;br /&gt;
Clemson University Libraries has a very strong program for digitizing and archiving photographs, and the Digital Imaging team processes many hundreds of photographs every month. These images are managed using different methods, including ContentDM, a digital collection manager.&lt;br /&gt;
&lt;br /&gt;
ContentDM provides various methods for searching and displaying photographs, along with their metadata. However, recent initiatives have resulted in the need to leverage those collections into exhibits displayed on other library-related websites, such as our Special Collections unit. The Clemson Libraries has invested heavily in Wordpress as our content management system of choice, and it seemed most efficient not to have to export and import images into our Wordpress sites in order to provide exhibited images.&lt;br /&gt;
&lt;br /&gt;
Fortunately, ContentDM has provided an API to many of their functions, allowing the extraction of metadata and even rescaled images through URLs. This project has been developing a plugin for Wordpress that integrates with ContentDM through shortcodes that Wordpress editors can easily include in their content. These shortcodes allow editors to choose how many images, which images from which collections, thumbnail sizes, etc. to display in different gallery styles. Plans are for it to allow integration with different plugins such as Fancybox and Masonry.&lt;br /&gt;
&lt;br /&gt;
In this presentation, I will demonstrate the current state of the plugin and discuss future plans. &lt;br /&gt;
&lt;br /&gt;
==Refinery — An open source locally deployable web platform for the analysis of large document collections==&lt;br /&gt;
 &lt;br /&gt;
* [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com&lt;br /&gt;
&lt;br /&gt;
Refinery is an open source web platform for the analysis of large unstructured document collections. It extracts meaningful semantic themes within documents also known as &amp;quot;topics&amp;quot; which can be thought of as word clouds composed of terms that highly co-occur with one another. Once this semantic index is formed, one can extract relevant documents related to these topics and further refine their contents through a summarization process that allows users to search for phrases that are relevant to them within the corpus. The goal of Refinery is to make this whole process easier and to provide some of the latest scalable versions of these learning algorithms in an intuitive web-based interface. Refinery is also meant to be run locally, thus bypassing the need for securing document collections over the internet. The talk will go through some of the technologies involved and a demo of the app.&lt;br /&gt;
&lt;br /&gt;
For more info check out http://www.docrefinery.org.&lt;br /&gt;
&lt;br /&gt;
==Drupal 8 — Evolution &amp;amp; Revolution==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Drupal 8 is in beta and nearing release. Among its many features, it notably has become more developer friendly through its adoption of the Symfony PHP framework along with Symfony's outstanding set of libraries (like Guzzle) and tools (like Composer). And, in implementing the Twig theming system, it is can begin to escape PHPtemplate. These moves also make it easier to create headless systems that uses Angular.js and other systems for presentation, or even forgo presentation entirely.&lt;br /&gt;
&lt;br /&gt;
From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.&lt;br /&gt;
&lt;br /&gt;
==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==&lt;br /&gt;
 &lt;br /&gt;
* [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]],  stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]&lt;br /&gt;
&lt;br /&gt;
GameSalad is a popular tool for developing mobile and desktop games with little actual programming. In this presentation, Stan Bogdanov breaks down the development process he followed while building [https://github.com/stanrb/mobiLit mobiLit], a mobile app with the goal of being the first open-source gamified information literacy app to be used as part of a college-level information literacy curriculum. He will go through the basics of using GameSalad to create an app that can be easily customized by non-programmers and the instructional principles used to teach the material in a mobile medium. Stan will also go through two qualitative design studies he did on the app and discuss their results and the lessons learned from building mobiLit. The session will conclude with an overview of the next steps for the [https://github.com/stanrb/mobiLit mobiLit project].&lt;br /&gt;
&lt;br /&gt;
==The Impossible Search: Pulling data from multiple unknown sources==&lt;br /&gt;
 &lt;br /&gt;
* Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com &lt;br /&gt;
&lt;br /&gt;
It's easy to search data you know the structure of, but what if you need to pull in data from sources that don't have a standard structure. The ability to search community events along with your standard catalog search results is an example, but often the only way to pull these events is through XML, JSON, (Insert structured format here), or even just raw html. But how do you get that structure? That simple question is what makes this impossible. The process to define and process this structure takes a lot of manual labor, especially if the data you are pulling is just HTML, and then every time you add data to the index you have to run all the data through a script to pull in data in a format Solr or an other index can use. This talk will focus on Solr, but the principles explained will apply to many other indexes.&lt;br /&gt;
&lt;br /&gt;
==What! You're Not Using Docker?==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Boring part: Docker[1] is a container system that provides benefits similar to virtualization with only a fraction of the overhead. Scintillating part: Docker can host between four to six times the number of service instances than systems such as Xen or VMWare on a given piece of hardware. But thats not all! Docker also makes it simple(r) to create transportable instances, so you can spin up development servers on your laptop.&lt;br /&gt;
&lt;br /&gt;
*[1]https://www.docker.com/&lt;br /&gt;
&lt;br /&gt;
== Video Accessibility, WebVTT, and Timed Text Track Tricks ==&lt;br /&gt;
&lt;br /&gt;
* Jason Ronallo, jronallo@gmail.com, NCSU Libraries&lt;br /&gt;
&lt;br /&gt;
Video on the Web presents new challenges and opportunities. How do you make your video more accessible to those with various disabilities and needs? I'll show you how. This presentation will focus on how to write and deliver captions, subtitles, audio descriptions, and timed metadata tracks for Web video using the WebVTT W3C standard. Encoding timed text tracks in this way opens up opportunities for new functionality on your websites beyond accessibility. The presentation will show some examples of the potential for using timed text tracks in creative ways. I'll cover all the HTML and JavaScript you will need to know as well as some of the CSS and other bits you could probably do without but are too fun to pass up.&lt;br /&gt;
&lt;br /&gt;
== Categorizing Records with Random Forests ==&lt;br /&gt;
 &lt;br /&gt;
* Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library&lt;br /&gt;
Academic libraries are increasingly responsible for providing ingest, search, discovery, and analysis for data sets.  Emerging techniques from data science and machine learning can provide librarians and developers with an opportunity to generate new insights and services from these document collections.  This presentation will provide a brief overview of common machine learning classification techniques, then dive into a more detailed example using a random forest to assign keywords to research data sets.  The talk will emphasize the insight that can be gained from machine learning rather than the inner workings of the algorithms.  The overall goal of this presentation is to provide librarians and developers with the context to recognize an opportunity to apply machine learning categorization techniques at their home campuses and organizations.  &lt;br /&gt;
&lt;br /&gt;
== Data Science in Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Devon Smith, smithde@oclc.org, OCLC&lt;br /&gt;
&lt;br /&gt;
Data Science is increasing in buzz and hype. I'll go over what it is, what it isn't, and how it fits in libraries.&lt;br /&gt;
&lt;br /&gt;
== PDF metadata extraction for academic literature == &lt;br /&gt;
&lt;br /&gt;
* Kevin Savage, kevin.savage at mendeley.com, Mendeley&lt;br /&gt;
* Joyce Stack, joyce.stack at mendeley.com, Mendeley&lt;br /&gt;
&lt;br /&gt;
Mendeley recently added a, &amp;quot;document from file,&amp;quot; endpoint to its API which attempts to extract metadata such as title and authors directly from PDF files. This talk will describe at a high level the machine learning methods we used including how we measured and tuned our model. We will then delve more deeply into our stack, the tools we used, some of the things that didn't work and why PDFs are the worst thing ever to compute over.&lt;br /&gt;
&lt;br /&gt;
== Giving Users What They Want: Record Grouping in VuFind ==&lt;br /&gt;
 &lt;br /&gt;
* Mark Noble,  mark@marmot.org, [//www.marmot.org Marmot Library Network]&lt;br /&gt;
&lt;br /&gt;
In 2013, Marmot did extensive usability studies with patrons to determine what was difficult in the catalog.  Many patrons had problems sifting through all of the various formats and editions of a title.  In 2014 we developed a method for [//mercury.marmot.org/Union/Search?lookfor=divergent grouping records] so only a single work is shown in search results and all formats and editions are listed under that work.  We will discuss our definition of a 'work' based on FRBR principles; combining meta data from MARC records with metadata from other sources like OverDrive; the technical details of Record Grouping; the design decisions made during implementation; and the reaction from users and staff.&lt;br /&gt;
&lt;br /&gt;
== Topic Space: a mobile augmented reality recommendation app ==&lt;br /&gt;
&lt;br /&gt;
* Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign&lt;br /&gt;
&lt;br /&gt;
The Topic Space module (http://minrvaproject.org/modules_topicspace.php ) was developed with an IMLS Sparks! Grant to investigate augmented reality technologies for in-library recommendations. The funding allowed for sustained university community collaboration by the University Library, the Graduate School of Library and Information Science, as well as graduate student programmers sourced from the Department of Computer Science. Collaborators designed app functionality and identified relevant open source libraries that could power optical character recognition (OCR) functionality from within the mobile phone.&lt;br /&gt;
&lt;br /&gt;
Topic space allows a user to take a picture of an item's call number in the book stacks. The module will show the user other books that are relevant but that are not shelved nearby. It can also show users books that are normally shelved here but that are currently checked out. Recommendations are based on Library of Congress subject headings and ILS circulation data which indicate recommendation candidates based on total check-outs. &lt;br /&gt;
&lt;br /&gt;
Research questions included development of back end (server-side) pattern matching algorithms for recommendations, and a rapid formative evaluation of interface design that would provide optimal user experience for navigation of the book stacks as a context to recommendations.&lt;br /&gt;
&lt;br /&gt;
Along with the Topic Space native app, grant collaborators prototyped web based recommendations which could serve as a new way of providing readers advisory and “more like this” recommendations from discovery interfaces accessed through desktop browsers. Outcomes of the grant include the availability of the [https://play.google.com/store/apps/details?id=edu.illinois.ugl.minrva Topic Spaces module within Minrva app on the Android Play store] and an experimental [http://backbonejs.org/ Backbone.js] based [http://minrva-dev.library.illinois.edu Topic Space web app].&lt;br /&gt;
&lt;br /&gt;
== Leveling Up Your Git Workflow ==&lt;br /&gt;
&lt;br /&gt;
* Megan Kudzia, moneill@albion.edu, Albion College Library&lt;br /&gt;
* Kate Sears, eks11@albion.edu, Albion College Library&lt;br /&gt;
&lt;br /&gt;
Have you started experimenting with Git on your own, but now you need to include others in your projects? Learn from our mistakes! Transitioning from a one-person git workflow and repo structure, to a structure that includes multiple people (including student workers), is not for the faint of heart. We'll talk about why we decided to work this way, our path to developing a git culture amongst ourselves, conceptual and technical difficulties we've faced, what we learned, and where we are now. Also with pretty pictures (aka workflow drawings).&lt;br /&gt;
&lt;br /&gt;
== Drone Loaning Program: Because Laptops are so last century ==&lt;br /&gt;
&lt;br /&gt;
 * Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries&lt;br /&gt;
 * Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries&lt;br /&gt;
&lt;br /&gt;
At Univ. Maryland we are in the very early stages of looking into allowing our student body get their hands on a drone. Yes that's right we will let students take out a drone for n amount of hours to work on projects of their choosing. The talk will talk about the logistics of getting a program of this sort from concept to &amp;quot;Is the drone available?&amp;quot;. If people sign waivers we will also promise not to crash the drone into code4lib attendees.&lt;br /&gt;
&lt;br /&gt;
== Got Git? Getting More Out of Your GitHub Repositories ==&lt;br /&gt;
&lt;br /&gt;
 * Terry Brady, twb27@georgetown.edu, Georgetown University Library&lt;br /&gt;
&lt;br /&gt;
This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories. &lt;br /&gt;
&lt;br /&gt;
In additional to all of the great benefits of using Git for code management, the GitHub interface provides a powerful set of tools to showcase a project and to keep your users informed of developments to your project.  These tools can assist with marketing and outreach - turning your code repository into a focus of conversation!&lt;br /&gt;
&lt;br /&gt;
* [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]&lt;br /&gt;
* [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]&lt;br /&gt;
* [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]&lt;br /&gt;
* [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]&lt;br /&gt;
* Gists for code sharing&lt;br /&gt;
* Private Repositories and Organizational Groups&lt;br /&gt;
* Pull Request Conversation Tracking&lt;br /&gt;
* Customized Issue management&lt;br /&gt;
&lt;br /&gt;
== Quick Wins for Every Department in the Library - File Analyzer! ==&lt;br /&gt;
&lt;br /&gt;
 * Terry Brady, twb27@georgetown.edu, Georgetown University Library&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.&lt;br /&gt;
* Analyzing Marc Records for the Cataloging department&lt;br /&gt;
* Transferring ILS invoices for the University Account System for the Acquisitions department &lt;br /&gt;
* Delivering patron fines to the Bursar’s office for the Access Service department&lt;br /&gt;
* Summarizing student worker timesheet data for the Finance department&lt;br /&gt;
* Validating COUNTER compliant reports for the Electronic Resources department&lt;br /&gt;
* Generating ingest packages for the Digital Services department&lt;br /&gt;
* Validating checksums for the Preservation department&lt;br /&gt;
&lt;br /&gt;
Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!&lt;br /&gt;
&lt;br /&gt;
==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor&lt;br /&gt;
&lt;br /&gt;
The transition from paper maps to digital ones changed much more than the maps themselves; it changed the very foundation of how we work and how we find each other. Now maps are transforming again.  The Geospatial World is moving from GIS systems that are institutionally-focused, expensive, feature-burdened, and binds data into a complicated and demanding user-hostile interface. From this transition from digital to web-based digital geospatial tools has come growth and development in new forms of map-based investigative journalism, activism, scholarship, and business ventures. This talk will highlight the conditions and strategies that made these changes possible as a means to draw a path by which librarians through our own work may follow, dragons notwithstanding. &lt;br /&gt;
&lt;br /&gt;
== Building Your Own Federated Search ==&lt;br /&gt;
&lt;br /&gt;
* Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco&lt;br /&gt;
&lt;br /&gt;
Advances in modern browsers have created some interesting possibilities for federated search. This presentation will cover common techniques and pitfalls in building a federated search. We will discuss what principles guided our decisions when implementing our own federated search. We will show tools we've built and our findings from building and using experimental prototypes.&lt;br /&gt;
&lt;br /&gt;
Your higher education institution likely offers dozens of online resources for educators, students, researchers, and the public. And each of these online resources likely has its own search tool. But users can't be expected to search in dozens of different interfaces to find what they're looking for. A typical solution for this issue is federated search. &lt;br /&gt;
&lt;br /&gt;
==  Indexing Linked Data with LDPath ==&lt;br /&gt;
&lt;br /&gt;
* Chris Beer, cabeer@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
LDPath [1] is a simple query language for indexing linked open data, with support for caching, content negotiation, and integration with non-RDF endpoints. This talk will demonstrate the features and potential of the language and framework to index a resource with links into id.loc.gov, viaf.org, geonames.org, etc to build an application-ready document.&lt;br /&gt;
&lt;br /&gt;
[1] http://marmotta.apache.org/ldpath/language.html&lt;br /&gt;
&lt;br /&gt;
== Show Me the Money: Integrating an LMS with Payment Providers ==&lt;br /&gt;
 &lt;br /&gt;
* Josh Weisman,  Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group&lt;br /&gt;
&lt;br /&gt;
In order to provide an easy and convenient way for patrons to pay fines, we are exploring ways to integrate the library management system with online payment providers such as PayPal. With many LMS systems being designed and developed for the cloud, we should be able to provide the frictionless user experience our patrons have come to expect from online transactions. In this session we'll discuss strategies for integration and review a sample application which uses REST APIs from a library management system to integrate with PayPal.&lt;br /&gt;
&lt;br /&gt;
== Shibboleth Federated Authentication for Library Applications: ==&lt;br /&gt;
&lt;br /&gt;
* Scott Fisher, scott.fisher@ucop.edu, California Digital Library&lt;br /&gt;
* Ken Weiss, ken.weiss@ucop.edu, California Digital Library&lt;br /&gt;
&lt;br /&gt;
Shibboleth is the most widely-used method to provide single-sign-on authentication to academic applications where users come from many different institutions. Shibboleth, the InCommon education and research trust framework, and the SAML protocol comprise a very powerful - but very complicated - solution to this very complicated problem. Scott and Ken have implemented Shibboleth for multiple library applications. They will share their understanding of the good, the bad, and the underlying spaghetti that makes it all work. Ken will discuss some of the technical aspects of the solution, touching on optimal and non-optimal use cases, administrative challenges, and authorization concerns. Scott will describe the implementation pattern for multi-institution single-sign-on that the California Digital Library has evolved, using the recently released Dash application (http://dash.cdlib.org) as an example.&lt;br /&gt;
&lt;br /&gt;
==Scientific Data: A Needs Assessment Journey==&lt;br /&gt;
 &lt;br /&gt;
*[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History&lt;br /&gt;
&lt;br /&gt;
While surveying digital research and collections data in the research science divisions at the American Museum of Natural History in NYC (as a part of my [http://ndsr.nycdigital.org/ National Digital Stewardship Residency] project), I have come across the big data hogs (genome sequencing and CT scanning) and the little pieces of data (images, publications), all equally important to not only scientific discovery, but as nodes in the history of science. &lt;br /&gt;
&lt;br /&gt;
In this session, I will discuss the development of my needs assessment surveys for scientific datasets and the interview process with Museum curators and researchers as background, seguing into an explanation of the results. I will then combine my findings into preliminary selection criteria to choose tools for digital preservation and management unique to scientific datasets. This will brooke a discussion on emerging standards, tools, and technologies in big data, specific to research science. &lt;br /&gt;
&lt;br /&gt;
I will conclude with preliminary findings on emerging technology that can be used to answer concerns surrounding the management and digital preservation of these data. I am hoping the Q&amp;amp;A session can be used to both answer questions about my project, and function as a way for you (the larger tech-savy library community)  to discuss the tools I’ve touched on in this talk. &lt;br /&gt;
&lt;br /&gt;
== Feminist Human Computer Interaction (HCI) in Library Software ==&lt;br /&gt;
 &lt;br /&gt;
* Bess Sadler,  bess@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
Libraries are not neutral repositories of knowledge. Library classification systems and search technologies tend to reflect the inequalities, biases, ethnocentrism, and power imbalances of the societies in which they are built [1]. How might we better resist these tendencies in the library software we create? This talk will examine some qualities of feminist HCI (pluralism, self-disclosure, participation, ecology, advocacy, and embodiment) [2] through the lens of library software. &lt;br /&gt;
&lt;br /&gt;
[1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.&lt;br /&gt;
&lt;br /&gt;
[2] Bardzell, Shaowen. Feminist HCI: Taking Stock and Outlining an Agenda for Design. CHI 2010: HCI For All. http://dmrussell.net/CHI2010/docs/p1301.pdf&lt;br /&gt;
&lt;br /&gt;
== Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==&lt;br /&gt;
&lt;br /&gt;
* Audrey Altman, audrey at dp.la, Digital Public Library of America&lt;br /&gt;
* Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America&lt;br /&gt;
* Mark Breedlove, mb at dp.la, Digital Public Library of America&lt;br /&gt;
&lt;br /&gt;
The Digital Public Library of America aggregates metadata for over 8 million objects from more than 24 direct partners, or Hubs, using its Metadata Application Profile (MAP), an RDF metadata application profile based on the Europeana Data Model. After working with the initial system for harvesting, mapping and enhancing our Hub’s metadata for a year, we realized that it was inadequate for working with data at this scale. There were architectural issues; it was opaque to non-developer and partner staff; there were inadequate tools for quality assurance and analysis; and the system was unaware that it was working with RDF data. As the network of Hubs expanded and we ingested more metadata, it became harder and harder to know when or why a harvest, a mapping task, or an enrichment went wrong because the tools for quality assurance were largely inadequate. &lt;br /&gt;
&lt;br /&gt;
The DPLA Content and Technology teams decided to develop a new system from the ground up to address those problems. Development of Heidrun, the internal version of the new system, started in October 2014. Heidrun’s goals are to make it easier for us to harvest and map metadata from various sources and in variety of schemas to the DPLA MAP, to better enrich that metadata using external data sources, and to actively involve our partners in the ingestion process through access to better QA tools. Heidrun and its componentry are built on Ruby on Rails, Blacklight, and ActiveTriples. Our presentation will give some background on our design principles and processes used during development, the architecture of the system, and its functionality. We plan to release a version of Heidrun and its components as a generalized metadata aggregation system for use by DPLA Hubs and others working to aggregate cultural heritage metadata.&lt;br /&gt;
&lt;br /&gt;
== OS or GTFO: Program or Perish ==&lt;br /&gt;
*Tessa Fallon, tessa.fallon@gmail.com&lt;br /&gt;
&lt;br /&gt;
Description TBD&lt;br /&gt;
&lt;br /&gt;
== Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==&lt;br /&gt;
* Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries&lt;br /&gt;
Would your library like to have large digital signage that displays dynamic information such as library hours, weather, room availability, and more? Have you looked into purchasing large digital signage, only to be turned off by the high price tag and lack of customization available with commercial solutions? Our library has developed a cheap and effective alternative to these systems using HTML 5 authoring software, a large TV, and freely-available APIs from Google, Springshare, and others. At this session, you’ll learn about the system that we have in place for displaying dynamic and easily-updatable information on our library’s large digital display, and how you can easily create something similar for your library.&lt;br /&gt;
&lt;br /&gt;
== REPOX: Metadata Blender ==&lt;br /&gt;
 &lt;br /&gt;
* John Mignault, jmignault@metro.org, Empire State Digital Network&lt;br /&gt;
&lt;br /&gt;
With the growth in the number of hubs providing metadata to the Digital Public Library of America, many of them are using REPOX, a tool originally created for the Europeana project, to aggregate disparate metadata feeds and transform them into formats suitable for ingest into DPLA. The Empire State Digital Network, the forthcoming DPLA service hub for NY state, is using it to prepare for our first ingest into DPLA in early 2015.  We'll take a look at REPOX and its capabilities and how it can be useful for ingesting and transforming metadata, and also discuss some things we've learned in massaging widely varied metadata feeds.&lt;br /&gt;
&lt;br /&gt;
== Beyond Open Source ==&lt;br /&gt;
&lt;br /&gt;
* Jason Casden, jmcasden@ncsu.edu, NCSU Libraries&lt;br /&gt;
* Bret Davidson, bddavids@ncsu.edu, NCSU Libraries&lt;br /&gt;
&lt;br /&gt;
The Code4Lib community has produced an increasingly impressive collection of open source software over the last decade, but much of this creative work remains out of reach for large portions of the library community. Do the relatively privileged institutions represented by a majority of Code4Lib participants have a professional responsibility to support the adoption of their innovations?&lt;br /&gt;
&lt;br /&gt;
Drawing from old and new software packaging and distribution approaches (from freeware to Docker), we will propose extending the open source software values of collaboration and transparency to include the wide and affordable distribution of software. We believe this will not only simplify the process of sharing our applications within the Code4Lib community, but also make it possible for less well resourced institutions to actually use our software. We will identify areas of need, present our experiences with the users of our own open source projects, discuss our attempts to go beyond open source, and make an argument for the internal value of supporting and encouraging a vibrant library ecosystem.&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]] &lt;br /&gt;
[[Category:Talk Proposals]]&lt;br /&gt;
&lt;br /&gt;
== Making It Work: Problem Solving Using Open Source at a Small Academic Library ==&lt;br /&gt;
 &lt;br /&gt;
* Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology&lt;br /&gt;
* Max King, mking9@iit.edu, Illinois Institute of Technology&lt;br /&gt;
&lt;br /&gt;
The Illinois Institute of Technology campus was added to the National Register of Historic Places in 2005, and contains a building, Mies van der Rohe's S.R. Crown Hall, that was named a National Historic Landmark in 2001. Creating a digital resource that can adequately showcase the campus and its architecture is challenge enough in and of itself, but doing so as a two-person team of relative newcomers, at a university library without dedicated programmers on staff, ups the ante considerably.&lt;br /&gt;
The challenges of technical know-how, staff time, and funding are nothing new to anyone working on digital projects at a university library, and are amplified when doing so at a smaller institution. This talk covers the conception, development, and design of the campus map site that was built, concentrating on the problem-solving strategies developed to cope with limited technical and financial resources.&lt;br /&gt;
We'll talk about our approach to development with Open Source software, including Omeka, along with the Neatline and Simile Timeline plugins. We'll also discuss the juggling act of designing for mobile mapping functionality without sacrificing desktop design, weighing the costs of increased functionality versus our ability to time-effectively include that functionality, and the challenge of building a site that could be developed iteratively, with an eye towards future enhancement and sustainability. Finally, we’ll provide recommendations for other librarians at smaller institutions for their own efforts at digital development.&lt;br /&gt;
&lt;br /&gt;
== Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==&lt;br /&gt;
 &lt;br /&gt;
* Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art&lt;br /&gt;
&lt;br /&gt;
The Museum of Modern Art has amassed a large collection of audiovisual materials over its many decades of existence. In order to preserve these materials, much of the audiovisual collection has been digitized. This is a complex process involving numerous steps and devices, and the methods used for digitization can have an effect on the quality of the file that is preserved. Therefore, knowing exactly how something was digitized is critical for future stewards of these objects to be able to properly care for and preserve them. However, detailed technical information about the processes involved in the digitization of audiovisual materials is not defined explicitly in most metadata schemas used for audiovisual materials. In order to record process history using existing metadata standards, some level of creativity is required to allow existing standards to express this information.&lt;br /&gt;
&lt;br /&gt;
This talk will detail different metadata standards, including PBCore, PREMIS, and reVTMD, that can be implemented as methods of recording this information. Specifically, the talk will examine efforts to integrate this metadata into the Museum of Modern Art’s new digital repository, the DRMC. This talk will provide background on the DRMC as well as MoMA’s specific institutional needs for process history metadata, then discuss different metadata implementations we have considered to document process history.&lt;br /&gt;
&lt;br /&gt;
== Pig Kisses Elephant: Building Research Data Services for Web Archives ==&lt;br /&gt;
 &lt;br /&gt;
* Jefferson Bailey,  jefferson@archive.org, Internet Archive&lt;br /&gt;
* Vinay Goel, vinay@archive.org, Internet Archive&lt;br /&gt;
&lt;br /&gt;
More and more libraries and archives are creating web archiving programs.  For both new and established programs, these archives can consist of hundreds of thousands, if not millions, of born-digital resources within a single collection; as such, they are ideally suited for large-scale computational study and analysis. Yet current access methods for web archives consist largely of browsing the archived web in the same manner as browsing the live web and the size of these collections and complexity of the WARC format can make aggregate analysis difficult. This talk will describe a project to create new ways for users and researchers to access and study web archives by offering extracted and post-processed datasets derived from web collections. Working with the 325+ institutions and their 2600+ collections within the Archive-It service, the Internet Archive is building methods to deliver a variety of datasets culled from collections of web content, including extracted metadata packaged in JSON, longitudinal link graph data, named entities, and other types of data. The talk will cover the technical details of building dataset production pipelines with Apache Pig, Hadoop, and tools like Stanford NER, the programmatic aspects of building data services for archives and researchers, and ongoing work to create new ways to access and study web archives.&lt;br /&gt;
&lt;br /&gt;
== Awesome Pi, LOL! ==&lt;br /&gt;
&lt;br /&gt;
* Matt Connolly, mconnolly@cornell.edu, Cornell University Library&lt;br /&gt;
* Jennifer Colt, jrc88@cornell.edu, Cornell University Library&lt;br /&gt;
&lt;br /&gt;
Inspired by Harvard Library Lab’s “Awesome Box” project, Cornell’s Library Outside the Library (LOL) group is piloting a more automated approach to letting our users tell us which materials they find particularly stunning. Armed with a Raspberry Pi, a barcode scanner, and some bits of kit that flash and glow, we have ventured into the foreign world of hardware development. This talk will discuss what it’s like for software developers and designers to get their hands dirty, how patrons are reacting to the Awesomizer, and LOL’s not-afraid-to-fail philosophy of experimentation.&lt;br /&gt;
&lt;br /&gt;
== You Gotta Keep 'em Separated: The Case for &amp;quot;Bento Box&amp;quot; Discovery Interfaces ==&lt;br /&gt;
 &lt;br /&gt;
* Jason Thomale,  jason.thomale@unt.edu, University of North Texas Libraries&lt;br /&gt;
&lt;br /&gt;
I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.&lt;br /&gt;
&lt;br /&gt;
The thing is, practically all of us--in academic libraries at least--have a similar set up for discovery, with just a few variations, and so talking about it still seems useful. Stop me if this sounds familiar. You've got a single search box on the library homepage as a starting point for discovery. And it's probably a tabbed affair, with an option for searching the catalog for books, an option for searching a discovery service for articles, an option for searching databases, and maybe a few others. Maybe you have an option to search everything at once--probably the default, if you have it. And, if you're a crazy hepcat, maybe you ''only'' have your one search that searches everything, with no tabs.&lt;br /&gt;
&lt;br /&gt;
Now, the question is, for your &amp;quot;everything&amp;quot; search, are you doing a combined list of results, or are you doing it bento-box style, with a short results list from each category displayed in its own compartment?&lt;br /&gt;
&lt;br /&gt;
At UNT, we've been holding off on implementing an &amp;quot;everything&amp;quot; search, for various reasons. One reason is that the evidence for either style hasn't been very clear. There's this persistent paradox that we just can't reconcile: users tell us, through word and action, that they prefer searching Google, yet, libraries aren't Google, and there are valid design reasons why we shouldn't try to oversimplify our discovery interfaces to be like Google. And there's user data that supports both sides.&lt;br /&gt;
&lt;br /&gt;
Holding off on making this decision has granted us 2 years of data on how people use our tabbed search interface that does ''not'' include an &amp;quot;everything&amp;quot; search. Recently I conducted a thorough analysis of this data--specifically the usage and query data for our catalog and discovery system (Summon). And I think it helps make the case for a bento box style discovery interface. To be clear, it isn't exactly the smoking gun that I was hoping for, but the picture it paints I think is telling. At the very least, it points away from a combined-results approach.&lt;br /&gt;
&lt;br /&gt;
I'm proposing a talk discussing the data we've collected, the trends we've seen, and what I think it all means--plus other reasons that we're jumping on the &amp;quot;bento box&amp;quot; discovery bandwagon and why I think &amp;quot;bento box&amp;quot; is at this point the path that least sells our souls.&lt;br /&gt;
&lt;br /&gt;
== Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift ==&lt;br /&gt;
 &lt;br /&gt;
* Ashley Blewer!, ashley.blewer@gmail.com&lt;br /&gt;
&lt;br /&gt;
Checksum technology is used all over the place, from git commits to authenticating Linux packages. It is most commonly used in the digital preservation field to monitor materials in storage for changes that will occur over time or used in the transmission of files during duplication. But do you even checksum, bro? I want this talk to move checksums from a position of mysterious macho jargon to something everyone can understand and want to use. I think a lot of people have heard of checksum but don’t know where to begin when it comes to actually using it at their institution. And cryptography is hella intimidating! This talk will cover what checksums are, how they can be integrated into a library or archival workflow, protecting collections requiring additional levels of security, algorithms used to verify file fixity and how they are different, and other aspects of cryptographic technology. Oh, and please note that all points in this talk will be emphasized or lightly performed through Taylor Swift lyrics. Seriously, this talk will consist of at least 50% Taylor Swift. Can you, like, even?&lt;br /&gt;
&lt;br /&gt;
== Level Up Your Coding with Code Club (yes, you can talk about it) ==&lt;br /&gt;
&lt;br /&gt;
* Coral Sheldon-Hess, coral@sheldon-hess.org&lt;br /&gt;
&lt;br /&gt;
Reading code is a necessary part of becoming a better developer. It gives you more experience and more insight into How Things Are (or Aren't) Done; it builds your intuition about how to solve problems with code; and it increases your confidence that you, too, can tackle whatever technological problems you're facing.&lt;br /&gt;
&lt;br /&gt;
But you don't have to read code alone! (Which is good. It's really not fun to read code alone.) &lt;br /&gt;
&lt;br /&gt;
In late 2014, a group of librarians formed two Code Clubs, inspired by [http://bloggytoons.com/code-club/ this talk by Saron] (of Bloggytoons fame). I'd like to tell you about how we've structured our Code Clubs, what has gone well, what we've learned, and what you need to do to form your own Code Club. I'll share a list of the codebases we've looked at, too, to help you get your own Code Club off the ground! &lt;br /&gt;
&lt;br /&gt;
== The Growth of a Programmer ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:jgo | Joshua Gomez]], Getty Research Institute, jgomez@getty.edu&lt;br /&gt;
&lt;br /&gt;
Just like other creative endeavors, software developers can experience periods of great productivity or find themselves in a rut. After contemplating the alternating periods in my own career I've noticed several factors that have effected my own professional growth and happiness, including: mentorship, structure, community, teamwork, environment, formal education, etc. Not all of the factors need to be present at all times; but some mixture of them is critical for continued growth. In this talk, I will articulate these factors, discuss how they can effect a developer's career, and how they can be sought out when missing. This talk is aimed at both new developers looking to strike their own path as well as the veterans that lead or mentor them.&lt;br /&gt;
&lt;br /&gt;
== Developing a Fedora 4.0 Content Model for Disk Images ==&lt;br /&gt;
&lt;br /&gt;
* Matthew Farrell, matthew.j.farrell@duke.edu, Duke University Libraries&lt;br /&gt;
* Alexandra Chassanoff, achass@email.unc.edu, BitCurator Access Project Manager&lt;br /&gt;
&lt;br /&gt;
As the acquisition of born-digital materials grows, institutions are seeking methods to facilitate easy ingest into their repositories and provide access to disk images and files derived or extracted from disk images. In this session, we describe our development of a Fedora 4.0 Content model for disk images, including acceptable image file formats and the rationale behind those choices.  We will also discuss efforts to integrate the disk image content model into the BitCurator Access environment. Unlike generalized, format-agnostic content models which might treat the disk image as a generic bitstream, a content model designed for disk images enables expression of relationships among associated content in the collection such as files extracted from images and other born-digital and digitized material associated with the same creator.  It also enables capture of file-system attributes such as file paths, timestamps, whether files are allocated/deleted, etc.  Further, a disk image content model suggests further steps repositories can take in order to transform and re-use associated metadata generated during the creation and forensic analysis of the disk image.&lt;br /&gt;
&lt;br /&gt;
== Data acquisition and publishing tools in R ==&lt;br /&gt;
&lt;br /&gt;
* Scott Chamberlain,  scott@ropensci.org, rOpenSci/UC Berkeley - first-time presenter&lt;br /&gt;
&lt;br /&gt;
R is an open source programming environment that is widely used among researchers in many fields. R is powerful because it's free, increasingly robust, and facilitates reproducible research, an increasingly sought after goal in academia. Although tools for data manipulation/visualization/analysis are well developed in R, data acquisition and publishing tools are not. rOpenSci is a collaborative effort to create the tools necessary to complete the reproducible research workflow. This presentation discusses the need for these tools, including examples, including interacting with the repositories Mendeley, Dryad, DataONE, and Figshare. In addition, we are building tools for searching scholarly metadata and acuiring full text of open access articles in a standarized way across metadata providers (e.g., Crossref, DataCite, DPLA) and publishers (e.g., PLOS, PeerJ, BMC, Pubmed). Last, we are building out tools for data reading and writing in Ecologial Metadata Language (EML).&lt;br /&gt;
&lt;br /&gt;
== SPLUNK: Log File Analysis ==&lt;br /&gt;
&lt;br /&gt;
* Jim LeFager, jlefager@depaul.edu, DePaul University Library&lt;br /&gt;
DePaul University Library recently took over monitoring and maintaining of the library EZproxy servers this past year and using Splunk, a machine data analysis tool, we are able to gather information and statistics on our electronic resource usage in addition to monitoring the servers. Splunk is a tool that can collect, analyze, and visualize log files and other machine data in real time and this has allowed for gathering realtime usage statistics for our electronic resources allowing us to filter by multiple facets including IP Range, Group Membership (student, faculty), so that we can see who is accessing our resources and from where. Splunk allows our library to query our data and create rich custom dashboards as well as create alerts that can be triggered when certain conditions are met, such as error codes, which can send an email alert to a group of users. We will be leveraging Splunk to monitor all library web applications going forward. This talk will review setting up Splunk and best practices in using the available features and customizations available including creating queries, alerts, and custom dashboards.  &lt;br /&gt;
&lt;br /&gt;
== Your code does not exist in a vacuum ==&lt;br /&gt;
* Becky Yoose, yoosebec at grinnell dot edu, Grinnell College (Done a lightning talk, MC duties, but have not presented a prepared talk)&lt;br /&gt;
&lt;br /&gt;
“If you have something to say, then say it in code…” - Sebastian Hammer, code4lib 2009&lt;br /&gt;
&lt;br /&gt;
In its 10 year run, code4lib has covered the spectrum of libtech development, from search to repositories to interfaces. However, during this time there has been little discussion about this one little fact about development - code does not exist in a vacuum. &lt;br /&gt;
&lt;br /&gt;
Like the comment above, code has something to say. A person’s or organization’s culture and beliefs influences code in all steps of the development cycle. What development method you use, tools, programming languages, licenses - everything is interconnected with and influenced by the philosophies, economics, social structures, and cultural beliefs of the developer and their organization/community.&lt;br /&gt;
&lt;br /&gt;
This talk will discuss these interconnections and influences when one develops code for libraries, focusing on several development practices (such as “Fail Fast, Fail Often” and Agile)   and licensing choices (such as open source) that libtech has either tried to model or incorporate into mainstream libtech practices. It’ll only scratch the surface of the many influences present in libtech development, but it will give folks a starting point to further investigate these connections at their own organizations and as a community as a whole.&lt;br /&gt;
&lt;br /&gt;
tl;dr - this will be a messy theoretical talk about technology and libraries. No shiny code slides, no live demos. You might come out of this talk feeling uncomfortable. Your code does not exist in a vacuum. Then again, you don’t exist in a vacuum either.&lt;br /&gt;
&lt;br /&gt;
== The Metadata Hopper: Mapping and Merging Metadata Standards for Simple, User-Friendly Access ==&lt;br /&gt;
&lt;br /&gt;
* Tracy Seneca, tjseneca@uic.edu, University of Illinois at Chicago&lt;br /&gt;
* Esther Verreau: verreau1@uic.edu, University of Illinois at Chicago&lt;br /&gt;
&lt;br /&gt;
The Chicago Collections Consortium: 15 institutions and growing!  8 distinct EAD standards! At least 3 permutations of MARC, and we lost count of the varieties of custom CONTENTdm image collections.  Not to mention the 14,730 unique subject terms, nearly all of which lead our poor end-users to exactly one organization's content. &lt;br /&gt;
&lt;br /&gt;
All large content aggregation projects have faced this challenge, and there are a few emerging tools to help us wrangle disparate metadata into new contexts.  The Metadata Hopper is one such tool. The Metadata Hopper enables archivists to map their local metadata standards to standardized deposit records, and tags those materials using a shared vocabulary, integrating them into a user-friendly portal without disrupting local practices. In last year's Code4Lib lightning talk we described the challenges that the Chicago Collections Consortium faces in creating shared, in-depth access to archival and digital collections about Chicago history and culture across CCC member organizations. This year, thanks to the Andrew W. Mellon Foundation, we have a working Django application to demonstrate.  In this talk we'll discuss the design that enables multiple layers of flexibility, from the ability to accept a variety of metadata standards to designing for an open source audience.&lt;br /&gt;
&lt;br /&gt;
http://chicagocollectionsconsortium.org&lt;br /&gt;
&lt;br /&gt;
== Programmers are not projects: lessons learned from managing humans ==&lt;br /&gt;
&lt;br /&gt;
* Erin White, erwhite@vcu.edu, Virginia Commonwealth University - first-time presenter&lt;br /&gt;
&lt;br /&gt;
Managing projects is one thing, but managing people is another. Whether we’re hired as managers or grow “organically” into management roles, sometimes technical people end up leading technical teams (gasp!). I’ll talk about lessons I’ve learned about hiring, retaining, and working long-term and day-to-day with highly tech-competent humans. I’ll also talk about navigating the politics of libraryland, juggling different types of projects, and working with constrained budgets to make good things and keep talented people engaged.&lt;br /&gt;
&lt;br /&gt;
== Practical Strategies for Picking Low-Hanging Fruits to Improve Your Library's Web Usability and UX ==&lt;br /&gt;
&lt;br /&gt;
* Bohyun Kim, bkim@hshsl.umaryland.edu, University of Maryland, Baltimore&lt;br /&gt;
&lt;br /&gt;
Have you ever tried to fix an obvious (to you at least!) problem in Web usability or UX (user experience) only to face strong resistance from the library staff? Are you a strong advocate for making library resources, systems, services, and space as usable as possible, but do you often find yourself struggling to get the point across and/or obtain the crucial buy-in from colleagues and administrators? &lt;br /&gt;
&lt;br /&gt;
There is no shortage of Web usability and UX guidelines. But applying them to a library and implementing desired changes often involve a long and slow process. To tackle this issue, this talk will focus on how to utilize the 'expert review' process (aka 'heuristic evaluation') as a preliminary or even preparatory step before embarking on more time-and-labor-intensive usability testing and user research. Several examples from  simple fixes to more nuanced usability and UX issues in libraries will be discussed to your heart's content. The goal of this talk is to provide practical strategies for picking as many low-hanging fruits as possible to make a real (albeit small) difference to your library's Web usability and UX effectively and efficiently.&lt;br /&gt;
&lt;br /&gt;
== A Semantic Makeover for CMS Data ==&lt;br /&gt;
&lt;br /&gt;
* Bill Levay, wjlevay@gmail.com, Linked Jazz Project&lt;br /&gt;
&lt;br /&gt;
How can we take semi-structured but messy metadata from a repository like CONTENTdm and transform it into rich linked data? Working with metadata from Tulane’s Hogan Jazz Archive Photography Collection, the Linked Jazz Project used Open Refine and Python scripts to tease out proper names, match them with name authority URIs, and specify FOAF relationships between musicians who appear together in photographs. Additional RDF triples were created for any dates associated with the photos, and for those images with place information we employed GeoNames URIs. Historical images and data that were siloed can now interact with other datasets, like Linked Jazz’s rich set of names and personal relationships, and can be visualized [link to come] or otherwise presented on the web in any number of ways. I have not previously presented at a Code4Lib conference.&lt;br /&gt;
&lt;br /&gt;
== Taking User Experience (UX) to new heights ==&lt;br /&gt;
 &lt;br /&gt;
* Kayne Richens, kayne.richens@deakin.edu.au, Deakin University&lt;br /&gt;
&lt;br /&gt;
User Experience, or &amp;quot;UX&amp;quot;, is for more than just websites. At Deakin University Library we're exploring ways to improve the user experience inside our campus library spaces, by putting new technologies front and centre in the overall experience for our students. How are we doing this? We’re collaborating with the University's IT department and exploring the following Library-changing opportunities:&lt;br /&gt;
&lt;br /&gt;
- Augmented Reality for Way-finding: We’re tackling that infamous thing that all Libraries can't get right – way-finding. We're enhancing library tour information and way-finding experiences by introducing augmented reality solutions.&lt;br /&gt;
 &lt;br /&gt;
- Heat mapping the library with wi-fi: We’re using our existing wi-fi infrastructure to present &amp;quot;heat maps&amp;quot; of library space utilisation, allowing our users to easily locate the space that best suits their needs, whether it be busy spaces to collaborate, or quiet spaces to study. And by overlaying computer usage and group study room bookings, users can quickly locate the space they need.&lt;br /&gt;
 &lt;br /&gt;
- Video chat library service: We’re piloting video-conferencing facilities in our group study rooms and spaces, connecting users and librarians and other professionals.&lt;br /&gt;
         &lt;br /&gt;
This talk will look at how these different technologies will be brought together to provide improved user experiences, as well some of the evidence and reasons that helped us to identify our needs, so you can too.&lt;br /&gt;
&lt;br /&gt;
==How to Hack it as a Working Parent: or, Should Your Face be Bathed in the Blue Glow of a Phone at 2 AM?==&lt;br /&gt;
&lt;br /&gt;
*Margaret Heller, Loyola University Chicago, mheller1@luc.edu&lt;br /&gt;
*Christina Salazar, California State University Channel Islands, christina.salazar@csuci.edu&lt;br /&gt;
*May Yan, Ryerson University, may.yan@ryerson.ca&lt;br /&gt;
&lt;br /&gt;
Modern technology has made it easier than ever for parents employed in technical environments to keep up with work at all hours and in all locations. This makes it possible to work a flexible schedule, but also may lead to problems with work/life balance and furthering unreasonable expectations about working hours. Add to that shifting gender roles and limited paid parental leave in the United States and you have potential for burnout and a certainty for anxiety. It raises the additioal question of whether the “always connected” mindset puts up a barrier to some populations who otherwise might be better represented in open source and library technology communities. &lt;br /&gt;
&lt;br /&gt;
This presentation will address tools that are useful for working parents in technical library positions, and share some lessons learned about using these tools while maintaining a reasonable work/life balance. We will consider a question that Karen Coyle raised back in 1996: &lt;br /&gt;
“What if the thousands of hours of graveyard shift amateur hacking wasn't really the best way to get the job done? That would be unthinkable.” &lt;br /&gt;
&lt;br /&gt;
For those who are able to take an extended parental leave, we will present strategies for minimizing the impact to your career and your employer. For those (particularly in the United States) who are only able to take a short leave will require different strategies. Despite different levels of preparation, all are useful exercises in succession planning and making a stronger workplace and future ability to work a flexible schedule through reviewing workloads, cross-training personnel, hiring contract replacements, and creative divisions of labor. Such preparation makes work better for everyone, kids or no kids.&lt;br /&gt;
&lt;br /&gt;
==Making your digital objects embeddable around the web==&lt;br /&gt;
 &lt;br /&gt;
* Jessie Keck, jkeck@stanford.edu, Stanford University Libraries&lt;br /&gt;
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
With more and more content from our digital repositories making their way into our discovery environments we quickly realize that we’re repeatedly re-inventing the wheel when it comes to creating “Viewers” for these digital objects.  With various different types of viewers necessary (books, images, audio, video, geospatial data, etc) the burden of getting these viewers into various environments (topic guides, blogs, catalogs, etc) becomes exponential.&lt;br /&gt;
&lt;br /&gt;
In this talk we’ll discuss how Stanford University Libraries implemented an oEmbed service to create an extensible viewer framework for all of its digital content. Using this service we’ve been able to easily integrate viewers into various discovery applications as well as make it easy for end users who discover our objects to easily embed customized versions into their own websites and blogs.&lt;br /&gt;
&lt;br /&gt;
==So you want to make your geospatial data discoverable==&lt;br /&gt;
 &lt;br /&gt;
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
Finding data for research or coursework can be one of the most time intensive tasks for a scholar or student. We introduce GeoBlacklight, an open source, multi-institutional software project focused on solving these common challenges at institutions across the world. GeoBlacklight prioritizes user experience, integrates with many GIS tools, and streamlines the use and organization of geospatial data. This talk will provide an introduction to the software, demonstrate current functionality, and provide a road map for future work.&lt;br /&gt;
&lt;br /&gt;
== Clueless-Driven Development: How I learned to migrate to Fedora 4 ==&lt;br /&gt;
&lt;br /&gt;
* Adam Wead, awead@psu.edu, Penn State University&lt;br /&gt;
&lt;br /&gt;
Recently I was tasked with migrating the content from our Fedora3 repository to the new Fedora4 repository architecture.&lt;br /&gt;
Despite a wealth of community support, I had no idea how to approach, or even begin to solve this problem. I knew I&lt;br /&gt;
wanted to follow best practices and use test-driven  development to build my solution, but had no idea where to start.&lt;br /&gt;
Despite this initial setback, I was able to start writing tests with only a  vague understanding of the problem. As my&lt;br /&gt;
tests exposed where my understanding of the problem was flawed, my code evolved, and within a week I had arrived  at a&lt;br /&gt;
working solution that exhibited all the hallmarks of good testing and software design.&lt;br /&gt;
&lt;br /&gt;
This talk recounts the process I went through from starting with practically nothing, to arriving at a working solution.&lt;br /&gt;
You can follow the rules of  test-driven development, but you can write tests in an expressive way to describe the&lt;br /&gt;
problem instead of just describing what the code should do. It was also essential to begin testing from an integration&lt;br /&gt;
viewpoint as opposed to a unit one, because at the outset the units were unknown and were later realized through further&lt;br /&gt;
development. For the presentation, I will be demonstrating using RSpec and Ruby. All the code examples will be related&lt;br /&gt;
to the Hydra software stack; however, I hope to show  that the processes at work will be applicable in any context.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Designing and Leading a Kick A** Tech Team ==&lt;br /&gt;
 &lt;br /&gt;
* Sibyl Schaefer,  sschaefer@rockarch.org, Rockefeller Archive Center&lt;br /&gt;
&lt;br /&gt;
New managers are often promoted without receiving management training, yet management is not something you just figure out. The experience of being expected to know how to manage, yet not being trained to do so often results in new managers feeling isolated and unsure how to move from making to managing. In this talk I’ll focus on my own managerial experience of designing and leading an archival tech team in a small independent archives. Topics covered will include hiring, delegating, creating a team culture, and leading people whose specialized knowledge exceeds your own. The talk take-aways should be applicable to managers and employees at large and small institutions alike.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==American (Archives) Horror Story: LTO Failure and Data Loss ==&lt;br /&gt;
 &lt;br /&gt;
* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH&lt;br /&gt;
* Casey Davis, casey_davis@wgbh.org, Project Manager, American Archive of Public Broadcasting&lt;br /&gt;
&lt;br /&gt;
Here’s a story to send shivers down archival spines: when transferring video files off LTO for the American Archive project, WGBH got an initial failure rate of 57%.   After repeat tries, the rates improved; still, an unnervingly large percentage of files were never able to be transferred successfully.   Even more unnerving, going public with our horror story got a big response from other archives using LTO -- it seems like many institutions are having similarly scary results.   What are the real risks with LTO tape?  Are there steps that archives should be taking to better circumvent those risks?  This presentation will share information about LTO storage failures across archives world and discuss the process of investigating the problem at WGBH by testing different methods of data retrieval from LTO (direct and networked downloads, individual file retrieval and bulk data dump, use of LTO 4 and LTO 6 decks) and using checksum comparisons and file analysis and characterization tools such as ffprobe, mediainfo and exiftool to analyze failed files.  We'll also present whatever results we’ve managed to turn up by the time of Code4Lib!&lt;/div&gt;</summary>
		<author><name>Afred</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&amp;diff=41964</id>
		<title>2015 Prepared Talk Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Prepared_Talk_Proposals&amp;diff=41964"/>
				<updated>2014-11-07T17:19:37Z</updated>
		
		<summary type="html">&lt;p&gt;Afred: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Code4lib 2015 is a loosely-structured conference that provides people working at the intersection of libraries/archives/museums/cultural heritage and technology with a chance to share ideas, be inspired, and forge collaborations. For more information about the Code4lib community, please visit http://code4lib.org/about/. &lt;br /&gt;
The conference will be held at the Portland Hilton &amp;amp; Executive Tower in Portland, Oregon, from February 9-12, 2015.&lt;br /&gt;
&lt;br /&gt;
'''Proposals for Prepared Talks:'''&lt;br /&gt;
&lt;br /&gt;
We encourage everyone to propose a talk.&lt;br /&gt;
 &lt;br /&gt;
Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:&lt;br /&gt;
* Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software&lt;br /&gt;
* Tools and technologies – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)&lt;br /&gt;
* Technical issues - Big issues in library technology that should be addressed or better understood&lt;br /&gt;
* Relevant non-technical issues – Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc.&lt;br /&gt;
&lt;br /&gt;
Proposals can be submitted through Friday, November 7, 2014 at 5pm PST (GMT−8). Voting will start on November 11, 2014 and continue through November 25, 2014. The URL to submit votes will be announced on the Code4Lib website and mailing list and will require an active code4lib.org account to participate. The final list of presentations will be announced in early- to mid-December.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Proposals for Prepared Talks:'''&lt;br /&gt;
&lt;br /&gt;
Log in to the Code4lib wiki and edit this wiki page using the prescribed format. If you are not already registered, follow the instructions to do so.&lt;br /&gt;
Provide a title and brief (500 words or fewer) description of your proposed talk.&lt;br /&gt;
If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist voters in opening the conference to new presenters.&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Talk Title: ==&lt;br /&gt;
 &lt;br /&gt;
* Speaker's name,  email address, and (optional) affiliation&lt;br /&gt;
* Second speaker's name, email address, and affiliation, if second speaker&lt;br /&gt;
&lt;br /&gt;
Abstract of no more than 500 words.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Talk Proposals'''&lt;br /&gt;
== Zines + Gamification = Awesomest Metadata Literacy Outreach Event Ever! ==&lt;br /&gt;
 &lt;br /&gt;
* Jennifer Hecker, jenniferraehecker@gmail.com, University of Texas Libraries &amp;amp; Austin Fanzine Project&lt;br /&gt;
* Lillian Karabaic, librarian@iprc.org, Independent Publishing Resource Center (Portland)&lt;br /&gt;
 &lt;br /&gt;
In academic libraries, and elsewhere, the popularity of zine* collections is on the rise. At the same time, metadata literacy is becoming an increasingly important skill, helping people navigate and understand digital environments and interactions. We have found a way to teach metadata literacy to the general public that isn’t super-boring – in fact, we’ve made it downright fun! - First, volunteer zine librarian Lillian Karabaic of Portland’s Independent Publishing Resource Center facilitated the creation of a gamified cataloging interface for the IPRC’s annual Raiders of the Lost Archives backlog-busting 24-hour volunteer cataloging event. - Then, archivist Jennifer Hecker facilitated the adaptation of the IPRC’s game for use in a similar, but also very different context – promoting UT Libraries newly-acquired zine collections. The main goal of the academic-library-based event was increasing excitement around the collections, but with the side goal of building metadata literacy, and introducing an understanding of library cataloging issues. The Texas modification also conforms to the xZINECOREx metadata schema developed by the national Zine Librarians Interest Group, and triggered interesting conversations with the Libraries’s cataloging department about evolving metadata standards and how to incorporate the products of crowd-sourcing projects into existing workflows. Both games will be demoed.                                      * a magazine produced for love, not profit.&lt;br /&gt;
&lt;br /&gt;
== Do the Semantic FRBRoo ==&lt;br /&gt;
* Rosie Le Faive, rlefaive@upei.ca, University of Prince Edward Island&lt;br /&gt;
&lt;br /&gt;
[http://www.islandora.ca Islandora] is great for creating repositories of any data type, but how can you model meaningful relationships between digital objects and use them to tell a story?&lt;br /&gt;
&lt;br /&gt;
At UPEI, I’m assembling an ethnography of Prince Edward Island’s traditional fiddle music that includes musical clips, video clips, oral histories, musical notation, images, and ethnographic commentaries. In order to present an exhibition-style site, I’m tying these digital objects together via the people, places, events, tunes and topics that they share or describe. &lt;br /&gt;
&lt;br /&gt;
To describe the relationships, I’m extending Islandora to use [http://www.cidoc-crm.org/frbr_inro.html FRBRoo], a vocabulary that combines the FRBR model with CIDOC-CRM, the the object-oriented museum documentation ontology. These modules being developed will allow other researchers to create a structured, navigable digital repository of diverse object types, that uses Islandora as an exhibition platform. &lt;br /&gt;
&lt;br /&gt;
== Our $50,000 Problem: Why Library School? ==&lt;br /&gt;
* Jennie Rose Halperin, jhalperin@mozilla.com, Mozilla Corporation&lt;br /&gt;
&lt;br /&gt;
57 library schools in the United States are churning out approximately 100 graduates per year, many with debt upwards of $50,000.  According to ONet, [http://www.inthelibrarywiththeleadpipe.org/2011/is-the-united-states-training-too-many-librarians-or-too-few-part-1/ 84% of library jobs in the US require an MLS.] The library profession is [http://dpeaflcio.org/programs-publications/issue-fact-sheets/library-workers-facts-figures/) 92% white and 82% female and entry-level librarians can expect to make $32,500 per year.]&lt;br /&gt;
&lt;br /&gt;
Contrasted with developers, who are almost [http://www.ncwit.org/blog/did-you-know-demographics-technical-women 90% male] and can expect to make [http://www.forbes.com/sites/jennagoudreau/2011/06/01/best-entry-level-jobs/ $70,000 in an entry-level position,] these numbers are dismal.&lt;br /&gt;
&lt;br /&gt;
According to a recent survey, the top skill that outgoing library students want to know is “programming” and yet many MLS programs still consider Microsoft Word an essential technology skill.&lt;br /&gt;
&lt;br /&gt;
What is going on here? Why do we accept this fate, where mostly female debt-burdened professionals continue to be thrown onto the work force without the education their expensive degrees promised?&lt;br /&gt;
&lt;br /&gt;
As a community we need to come together to stop this cycle. We need to provide better support and mentorship to diversify and keep the profession relevant and help librarianship move into the future it deserves.&lt;br /&gt;
&lt;br /&gt;
This talk will walk through the challenges of navigating a hostile employment environment as well as present models for better development and future state imagining.&lt;br /&gt;
&lt;br /&gt;
== No cataloging software? Need more than Dublin Core? No problem!: Experiences with CollectiveAccess ==&lt;br /&gt;
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University&lt;br /&gt;
* Rachel Wittmann, rwittma@clemson.edu, Clemson University&lt;br /&gt;
&lt;br /&gt;
Clemson University Libraries has implemented the open-source software CollectiveAccess for customized digital collection needs. CollectiveAccess is an open-source project with the goal of providing a flexible way to manage and publish museum and archival collections. There are several applications associated with the projects; most used are: Providence (for cataloging and entering metadata) and Pawtucket (for displaying objects in a collection for the public). It has many profiles readily available for installing with existing library standards, such as Dublin Core, and there is a robust syntax for creating your own profiles to fit custom tailored metadata schemas. Plus, the user interface allows you to modify the metadata profile quickly and easily.&lt;br /&gt;
&lt;br /&gt;
In this talk, we will discuss:&lt;br /&gt;
* Our experiences with installing Providence and creating an installation profile that satisfies the needs of many of the Clemson Libraries digital archiving processes. &lt;br /&gt;
* The stumbling blocks experienced in that process and how they were resolved.&lt;br /&gt;
* The available plugins sourcing widely used authorities, such as Library of Congress thesauri and GeoNames.org, and how they have been used by our projects. &lt;br /&gt;
* A brief overview of the export and import functions and also current workflow practices within Providence.&lt;br /&gt;
* Future plans &amp;amp; the role of CollectiveAccess at Clemson University Libraries&lt;br /&gt;
&lt;br /&gt;
== Getting ContentDM and Wordpress to Play Together ==&lt;br /&gt;
* [[User:SeanHendricks|Sean Q. Hendricks]], sqhendr@clemson.edu, Clemson University&lt;br /&gt;
&lt;br /&gt;
Clemson University Libraries has a very strong program for digitizing and archiving photographs, and the Digital Imaging team processes many hundreds of photographs every month. These images are managed using different methods, including ContentDM, a digital collection manager.&lt;br /&gt;
&lt;br /&gt;
ContentDM provides various methods for searching and displaying photographs, along with their metadata. However, recent initiatives have resulted in the need to leverage those collections into exhibits displayed on other library-related websites, such as our Special Collections unit. The Clemson Libraries has invested heavily in Wordpress as our content management system of choice, and it seemed most efficient not to have to export and import images into our Wordpress sites in order to provide exhibited images.&lt;br /&gt;
&lt;br /&gt;
Fortunately, ContentDM has provided an API to many of their functions, allowing the extraction of metadata and even rescaled images through URLs. This project has been developing a plugin for Wordpress that integrates with ContentDM through shortcodes that Wordpress editors can easily include in their content. These shortcodes allow editors to choose how many images, which images from which collections, thumbnail sizes, etc. to display in different gallery styles. Plans are for it to allow integration with different plugins such as Fancybox and Masonry.&lt;br /&gt;
&lt;br /&gt;
In this presentation, I will demonstrate the current state of the plugin and discuss future plans. &lt;br /&gt;
&lt;br /&gt;
==Refinery — An open source locally deployable web platform for the analysis of large document collections==&lt;br /&gt;
 &lt;br /&gt;
* [[User:DaeilKim|Daeil Kim]], The New York Times, daeil.kim@nytimes.com&lt;br /&gt;
&lt;br /&gt;
Refinery is an open source web platform for the analysis of large unstructured document collections. It extracts meaningful semantic themes within documents also known as &amp;quot;topics&amp;quot; which can be thought of as word clouds composed of terms that highly co-occur with one another. Once this semantic index is formed, one can extract relevant documents related to these topics and further refine their contents through a summarization process that allows users to search for phrases that are relevant to them within the corpus. The goal of Refinery is to make this whole process easier and to provide some of the latest scalable versions of these learning algorithms in an intuitive web-based interface. Refinery is also meant to be run locally, thus bypassing the need for securing document collections over the internet. The talk will go through some of the technologies involved and a demo of the app.&lt;br /&gt;
&lt;br /&gt;
For more info check out http://www.docrefinery.org.&lt;br /&gt;
&lt;br /&gt;
==Drupal 8 — Evolution &amp;amp; Revolution==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Drupal 8 is in beta and nearing release. Among its many features, it notably has become more developer friendly through its adoption of the Symfony PHP framework along with Symfony's outstanding set of libraries (like Guzzle) and tools (like Composer). And, in implementing the Twig theming system, it is can begin to escape PHPtemplate. These moves also make it easier to create headless systems that uses Angular.js and other systems for presentation, or even forgo presentation entirely.&lt;br /&gt;
&lt;br /&gt;
From the site-builder's perspective, Drupal 8 provides a much smother experience and makes it easier to build and implement site recipes.&lt;br /&gt;
&lt;br /&gt;
==Using GameSalad to Build a Gamified Information Literacy Mobile App for Higher Education==&lt;br /&gt;
 &lt;br /&gt;
* [[User:StanBogdanov|Stanislav 'Stan' Bogdanov]],  stan@stanrb.com, Adelphi University and [http://bogliollc.com Boglio LLC]&lt;br /&gt;
&lt;br /&gt;
GameSalad is a popular tool for developing mobile and desktop games with little actual programming. In this presentation, Stan Bogdanov breaks down the development process he followed while building [https://github.com/stanrb/mobiLit mobiLit], a mobile app with the goal of being the first open-source gamified information literacy app to be used as part of a college-level information literacy curriculum. He will go through the basics of using GameSalad to create an app that can be easily customized by non-programmers and the instructional principles used to teach the material in a mobile medium. Stan will also go through two qualitative design studies he did on the app and discuss their results and the lessons learned from building mobiLit. The session will conclude with an overview of the next steps for the [https://github.com/stanrb/mobiLit mobiLit project].&lt;br /&gt;
&lt;br /&gt;
==The Impossible Search: Pulling data from multiple unknown sources==&lt;br /&gt;
 &lt;br /&gt;
* Riley Childs, no official affiliation (currently a Senior in High School at Charlotte United Christian Academy), rchilds (AT) cucawarriors.com &lt;br /&gt;
&lt;br /&gt;
It's easy to search data you know the structure of, but what if you need to pull in data from sources that don't have a standard structure. The ability to search community events along with your standard catalog search results is an example, but often the only way to pull these events is through XML, JSON, (Insert structured format here), or even just raw html. But how do you get that structure? That simple question is what makes this impossible. The process to define and process this structure takes a lot of manual labor, especially if the data you are pulling is just HTML, and then every time you add data to the index you have to run all the data through a script to pull in data in a format Solr or an other index can use. This talk will focus on Solr, but the principles explained will apply to many other indexes.&lt;br /&gt;
&lt;br /&gt;
==What! You're Not Using Docker?==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com&lt;br /&gt;
&lt;br /&gt;
Boring part: Docker[1] is a container system that provides benefits similar to virtualization with only a fraction of the overhead. Scintillating part: Docker can host between four to six times the number of service instances than systems such as Xen or VMWare on a given piece of hardware. But thats not all! Docker also makes it simple(r) to create transportable instances, so you can spin up development servers on your laptop.&lt;br /&gt;
&lt;br /&gt;
*[1]https://www.docker.com/&lt;br /&gt;
&lt;br /&gt;
== Video Accessibility, WebVTT, and Timed Text Track Tricks ==&lt;br /&gt;
&lt;br /&gt;
* Jason Ronallo, jronallo@gmail.com, NCSU Libraries&lt;br /&gt;
&lt;br /&gt;
Video on the Web presents new challenges and opportunities. How do you make your video more accessible to those with various disabilities and needs? I'll show you how. This presentation will focus on how to write and deliver captions, subtitles, audio descriptions, and timed metadata tracks for Web video using the WebVTT W3C standard. Encoding timed text tracks in this way opens up opportunities for new functionality on your websites beyond accessibility. The presentation will show some examples of the potential for using timed text tracks in creative ways. I'll cover all the HTML and JavaScript you will need to know as well as some of the CSS and other bits you could probably do without but are too fun to pass up.&lt;br /&gt;
&lt;br /&gt;
== Categorizing Records with Random Forests ==&lt;br /&gt;
 &lt;br /&gt;
* Geoffrey Boushey, geoffrey.boushey@ucsf.edu, UCSF Library&lt;br /&gt;
Academic libraries are increasingly responsible for providing ingest, search, discovery, and analysis for data sets.  Emerging techniques from data science and machine learning can provide librarians and developers with an opportunity to generate new insights and services from these document collections.  This presentation will provide a brief overview of common machine learning classification techniques, then dive into a more detailed example using a random forest to assign keywords to research data sets.  The talk will emphasize the insight that can be gained from machine learning rather than the inner workings of the algorithms.  The overall goal of this presentation is to provide librarians and developers with the context to recognize an opportunity to apply machine learning categorization techniques at their home campuses and organizations.  &lt;br /&gt;
&lt;br /&gt;
== Data Science in Libraries ==&lt;br /&gt;
 &lt;br /&gt;
* Devon Smith, smithde@oclc.org, OCLC&lt;br /&gt;
&lt;br /&gt;
Data Science is increasing in buzz and hype. I'll go over what it is, what it isn't, and how it fits in libraries.&lt;br /&gt;
&lt;br /&gt;
== PDF metadata extraction for academic literature == &lt;br /&gt;
&lt;br /&gt;
* Kevin Savage, kevin.savage at mendeley.com, Mendeley&lt;br /&gt;
* Joyce Stack, joyce.stack at mendeley.com, Mendeley&lt;br /&gt;
&lt;br /&gt;
Mendeley recently added a, &amp;quot;document from file,&amp;quot; endpoint to its API which attempts to extract metadata such as title and authors directly from PDF files. This talk will describe at a high level the machine learning methods we used including how we measured and tuned our model. We will then delve more deeply into our stack, the tools we used, some of the things that didn't work and why PDFs are the worst thing ever to compute over.&lt;br /&gt;
&lt;br /&gt;
== Giving Users What They Want: Record Grouping in VuFind ==&lt;br /&gt;
 &lt;br /&gt;
* Mark Noble,  mark@marmot.org, [//www.marmot.org Marmot Library Network]&lt;br /&gt;
&lt;br /&gt;
In 2013, Marmot did extensive usability studies with patrons to determine what was difficult in the catalog.  Many patrons had problems sifting through all of the various formats and editions of a title.  In 2014 we developed a method for [//mercury.marmot.org/Union/Search?lookfor=divergent grouping records] so only a single work is shown in search results and all formats and editions are listed under that work.  We will discuss our definition of a 'work' based on FRBR principles; combining meta data from MARC records with metadata from other sources like OverDrive; the technical details of Record Grouping; the design decisions made during implementation; and the reaction from users and staff.&lt;br /&gt;
&lt;br /&gt;
== Topic Space: a mobile augmented reality recommendation app ==&lt;br /&gt;
&lt;br /&gt;
* Jim Hahn, jimhahn@illinois.edu, University of Illinois at Urbana-Champaign&lt;br /&gt;
&lt;br /&gt;
The Topic Space module (http://minrvaproject.org/modules_topicspace.php ) was developed with an IMLS Sparks! Grant to investigate augmented reality technologies for in-library recommendations. The funding allowed for sustained university community collaboration by the University Library, the Graduate School of Library and Information Science, as well as graduate student programmers sourced from the Department of Computer Science. Collaborators designed app functionality and identified relevant open source libraries that could power optical character recognition (OCR) functionality from within the mobile phone.&lt;br /&gt;
&lt;br /&gt;
Topic space allows a user to take a picture of an item's call number in the book stacks. The module will show the user other books that are relevant but that are not shelved nearby. It can also show users books that are normally shelved here but that are currently checked out. Recommendations are based on Library of Congress subject headings and ILS circulation data which indicate recommendation candidates based on total check-outs. &lt;br /&gt;
&lt;br /&gt;
Research questions included development of back end (server-side) pattern matching algorithms for recommendations, and a rapid formative evaluation of interface design that would provide optimal user experience for navigation of the book stacks as a context to recommendations.&lt;br /&gt;
&lt;br /&gt;
Along with the Topic Space native app, grant collaborators prototyped web based recommendations which could serve as a new way of providing readers advisory and “more like this” recommendations from discovery interfaces accessed through desktop browsers. Outcomes of the grant include the availability of the [https://play.google.com/store/apps/details?id=edu.illinois.ugl.minrva Topic Spaces module within Minrva app on the Android Play store] and an experimental [http://backbonejs.org/ Backbone.js] based [http://minrva-dev.library.illinois.edu Topic Space web app].&lt;br /&gt;
&lt;br /&gt;
== Leveling Up Your Git Workflow ==&lt;br /&gt;
&lt;br /&gt;
* Megan Kudzia, moneill@albion.edu, Albion College Library&lt;br /&gt;
* Kate Sears, eks11@albion.edu, Albion College Library&lt;br /&gt;
&lt;br /&gt;
Have you started experimenting with Git on your own, but now you need to include others in your projects? Learn from our mistakes! Transitioning from a one-person git workflow and repo structure, to a structure that includes multiple people (including student workers), is not for the faint of heart. We'll talk about why we decided to work this way, our path to developing a git culture amongst ourselves, conceptual and technical difficulties we've faced, what we learned, and where we are now. Also with pretty pictures (aka workflow drawings).&lt;br /&gt;
&lt;br /&gt;
== Drone Loaning Program: Because Laptops are so last century ==&lt;br /&gt;
&lt;br /&gt;
 * Uche Enwesi, uenwesi@umd.edu, University of Maryland Libraries&lt;br /&gt;
 * Francis Kayiwa, fkayiwa@umd.edu, University of Maryland Libraries&lt;br /&gt;
&lt;br /&gt;
At Univ. Maryland we are in the very early stages of looking into allowing our student body get their hands on a drone. Yes that's right we will let students take out a drone for n amount of hours to work on projects of their choosing. The talk will talk about the logistics of getting a program of this sort from concept to &amp;quot;Is the drone available?&amp;quot;. If people sign waivers we will also promise not to crash the drone into code4lib attendees.&lt;br /&gt;
&lt;br /&gt;
== Got Git? Getting More Out of Your GitHub Repositories ==&lt;br /&gt;
&lt;br /&gt;
 * Terry Brady, twb27@georgetown.edu, Georgetown University Library&lt;br /&gt;
&lt;br /&gt;
This presentation will discuss how librarians, developers, and system administrators at Georgetown University are maximizing their use of the public and private GitHub repositories. &lt;br /&gt;
&lt;br /&gt;
In additional to all of the great benefits of using Git for code management, the GitHub interface provides a powerful set of tools to showcase a project and to keep your users informed of developments to your project.  These tools can assist with marketing and outreach - turning your code repository into a focus of conversation!&lt;br /&gt;
&lt;br /&gt;
* [http://georgetown-university-libraries.github.io/File-Analyzer/ Style-able Project Pages]&lt;br /&gt;
* [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki Project Wikis]&lt;br /&gt;
* [https://github.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/releases Project Release Notes/Portfolios]&lt;br /&gt;
* [https://rawgit.com/Georgetown-University-Libraries/Georgetown-University-Libraries-Code/master/samples/GoogleSpreadsheetFilter.html Web Resources That Can Be Directly Requested]&lt;br /&gt;
* Gists for code sharing&lt;br /&gt;
* Private Repositories and Organizational Groups&lt;br /&gt;
* Pull Request Conversation Tracking&lt;br /&gt;
* Customized Issue management&lt;br /&gt;
&lt;br /&gt;
== Quick Wins for Every Department in the Library - File Analyzer! ==&lt;br /&gt;
&lt;br /&gt;
 * Terry Brady, twb27@georgetown.edu, Georgetown University Library&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Library has customized workflows for nearly every department in our library with a single code base.&lt;br /&gt;
* Analyzing Marc Records for the Cataloging department&lt;br /&gt;
* Transferring ILS invoices for the University Account System for the Acquisitions department &lt;br /&gt;
* Delivering patron fines to the Bursar’s office for the Access Service department&lt;br /&gt;
* Summarizing student worker timesheet data for the Finance department&lt;br /&gt;
* Validating COUNTER compliant reports for the Electronic Resources department&lt;br /&gt;
* Generating ingest packages for the Digital Services department&lt;br /&gt;
* Validating checksums for the Preservation department&lt;br /&gt;
&lt;br /&gt;
Learn how you can customize the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] to become a hero in your library!&lt;br /&gt;
&lt;br /&gt;
==The Geospatial World is Moving from Maps *on* the Web to Maps *of* the web. Libraries can too==&lt;br /&gt;
 &lt;br /&gt;
* [[User:Copystar|Mita Williams]], mita@uwindsor.ca, User Experience Librarian, University of Windsor&lt;br /&gt;
&lt;br /&gt;
The transition from paper maps to digital ones changed much more than the maps themselves; it changed the very foundation of how we work and how we find each other. Now maps are transforming again.  The Geospatial World is moving from GIS systems that are institutionally-focused, expensive, feature-burdened, and binds data into a complicated and demanding user-hostile interface. From this transition from digital to web-based digital geospatial tools has come growth and development in new forms of map-based investigative journalism, activism, scholarship, and business ventures. This talk will highlight the conditions and strategies that made these changes possible as a means to draw a path by which librarians through our own work may follow, dragons notwithstanding. &lt;br /&gt;
&lt;br /&gt;
== Building Your Own Federated Search ==&lt;br /&gt;
&lt;br /&gt;
* Rich Trott, Richard.Trott@ucsf.edu, UC San Francisco&lt;br /&gt;
&lt;br /&gt;
Advances in modern browsers have created some interesting possibilities for federated search. This presentation will cover common techniques and pitfalls in building a federated search. We will discuss what principles guided our decisions when implementing our own federated search. We will show tools we've built and our findings from building and using experimental prototypes.&lt;br /&gt;
&lt;br /&gt;
Your higher education institution likely offers dozens of online resources for educators, students, researchers, and the public. And each of these online resources likely has its own search tool. But users can't be expected to search in dozens of different interfaces to find what they're looking for. A typical solution for this issue is federated search. &lt;br /&gt;
&lt;br /&gt;
==  Indexing Linked Data with LDPath ==&lt;br /&gt;
&lt;br /&gt;
* Chris Beer, cabeer@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
LDPath [1] is a simple query language for indexing linked open data, with support for caching, content negotiation, and integration with non-RDF endpoints. This talk will demonstrate the features and potential of the language and framework to index a resource with links into id.loc.gov, viaf.org, geonames.org, etc to build an application-ready document.&lt;br /&gt;
&lt;br /&gt;
[1] http://marmotta.apache.org/ldpath/language.html&lt;br /&gt;
&lt;br /&gt;
== Show Me the Money: Integrating an LMS with Payment Providers ==&lt;br /&gt;
 &lt;br /&gt;
* Josh Weisman,  Josh.Weisman@exlibrisgroup.com, Development Director-Resources Management, Ex Libris Group&lt;br /&gt;
&lt;br /&gt;
In order to provide an easy and convenient way for patrons to pay fines, we are exploring ways to integrate the library management system with online payment providers such as PayPal. With many LMS systems being designed and developed for the cloud, we should be able to provide the frictionless user experience our patrons have come to expect from online transactions. In this session we'll discuss strategies for integration and review a sample application which uses REST APIs from a library management system to integrate with PayPal.&lt;br /&gt;
&lt;br /&gt;
== Shibboleth Federated Authentication for Library Applications: ==&lt;br /&gt;
&lt;br /&gt;
* Scott Fisher, scott.fisher@ucop.edu, California Digital Library&lt;br /&gt;
* Ken Weiss, ken.weiss@ucop.edu, California Digital Library&lt;br /&gt;
&lt;br /&gt;
Shibboleth is the most widely-used method to provide single-sign-on authentication to academic applications where users come from many different institutions. Shibboleth, the InCommon education and research trust framework, and the SAML protocol comprise a very powerful - but very complicated - solution to this very complicated problem. Scott and Ken have implemented Shibboleth for multiple library applications. They will share their understanding of the good, the bad, and the underlying spaghetti that makes it all work. Ken will discuss some of the technical aspects of the solution, touching on optimal and non-optimal use cases, administrative challenges, and authorization concerns. Scott will describe the implementation pattern for multi-institution single-sign-on that the California Digital Library has evolved, using the recently released Dash application (http://dash.cdlib.org) as an example.&lt;br /&gt;
&lt;br /&gt;
==Scientific Data: A Needs Assessment Journey==&lt;br /&gt;
 &lt;br /&gt;
*[[User:VickySteeves| Vicky Steeves]], vsteeves@amnh.org, American Museum of Natural History&lt;br /&gt;
&lt;br /&gt;
While surveying digital research and collections data in the research science divisions at the American Museum of Natural History in NYC (as a part of my [http://ndsr.nycdigital.org/ National Digital Stewardship Residency] project), I have come across the big data hogs (genome sequencing and CT scanning) and the little pieces of data (images, publications), all equally important to not only scientific discovery, but as nodes in the history of science. &lt;br /&gt;
&lt;br /&gt;
In this session, I will discuss the development of my needs assessment surveys for scientific datasets and the interview process with Museum curators and researchers as background, seguing into an explanation of the results. I will then combine my findings into preliminary selection criteria to choose tools for digital preservation and management unique to scientific datasets. This will brooke a discussion on emerging standards, tools, and technologies in big data, specific to research science. &lt;br /&gt;
&lt;br /&gt;
I will conclude with preliminary findings on emerging technology that can be used to answer concerns surrounding the management and digital preservation of these data. I am hoping the Q&amp;amp;A session can be used to both answer questions about my project, and function as a way for you (the larger tech-savy library community)  to discuss the tools I’ve touched on in this talk. &lt;br /&gt;
&lt;br /&gt;
== Feminist Human Computer Interaction (HCI) in Library Software ==&lt;br /&gt;
 &lt;br /&gt;
* Bess Sadler,  bess@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
Libraries are not neutral repositories of knowledge. Library classification systems and search technologies tend to reflect the inequalities, biases, ethnocentrism, and power imbalances of the societies in which they are built [1]. How might we better resist these tendencies in the library software we create? This talk will examine some qualities of feminist HCI (pluralism, self-disclosure, participation, ecology, advocacy, and embodiment) [2] through the lens of library software. &lt;br /&gt;
&lt;br /&gt;
[1] Olson, Hope A. (2002). The Power to Name: Locating the Limits of Subject Representation in Libraries. Dordrecht, The Netherlands: Kluwer Academic Publishers.&lt;br /&gt;
&lt;br /&gt;
[2] Bardzell, Shaowen. Feminist HCI: Taking Stock and Outlining an Agenda for Design. CHI 2010: HCI For All. http://dmrussell.net/CHI2010/docs/p1301.pdf&lt;br /&gt;
&lt;br /&gt;
== Heiðrún: DPLA's Metadata Harvesting, Mapping and Enhancement System ==&lt;br /&gt;
&lt;br /&gt;
* Audrey Altman, audrey at dp.la, Digital Public Library of America&lt;br /&gt;
* Gretchen Gueguen, gretchen at dp.la, Digital Public Library of America&lt;br /&gt;
* Mark Breedlove, mb at dp.la, Digital Public Library of America&lt;br /&gt;
&lt;br /&gt;
The Digital Public Library of America aggregates metadata for over 8 million objects from more than 24 direct partners, or Hubs, using its Metadata Application Profile (MAP), an RDF metadata application profile based on the Europeana Data Model. After working with the initial system for harvesting, mapping and enhancing our Hub’s metadata for a year, we realized that it was inadequate for working with data at this scale. There were architectural issues; it was opaque to non-developer and partner staff; there were inadequate tools for quality assurance and analysis; and the system was unaware that it was working with RDF data. As the network of Hubs expanded and we ingested more metadata, it became harder and harder to know when or why a harvest, a mapping task, or an enrichment went wrong because the tools for quality assurance were largely inadequate. &lt;br /&gt;
&lt;br /&gt;
The DPLA Content and Technology teams decided to develop a new system from the ground up to address those problems. Development of Heidrun, the internal version of the new system, started in October 2014. Heidrun’s goals are to make it easier for us to harvest and map metadata from various sources and in variety of schemas to the DPLA MAP, to better enrich that metadata using external data sources, and to actively involve our partners in the ingestion process through access to better QA tools. Heidrun and its componentry are built on Ruby on Rails, Blacklight, and ActiveTriples. Our presentation will give some background on our design principles and processes used during development, the architecture of the system, and its functionality. We plan to release a version of Heidrun and its components as a generalized metadata aggregation system for use by DPLA Hubs and others working to aggregate cultural heritage metadata.&lt;br /&gt;
&lt;br /&gt;
== OS or GTFO: Program or Perish ==&lt;br /&gt;
*Tessa Fallon, tessa.fallon@gmail.com&lt;br /&gt;
&lt;br /&gt;
Description TBD&lt;br /&gt;
&lt;br /&gt;
== Creating Dynamic— and Cheap!— Digital Displays with HTML 5 Authoring Software ==&lt;br /&gt;
* Chris Woodall, cmwoodall@salisbury.edu, Salisbury University Libraries&lt;br /&gt;
Would your library like to have large digital signage that displays dynamic information such as library hours, weather, room availability, and more? Have you looked into purchasing large digital signage, only to be turned off by the high price tag and lack of customization available with commercial solutions? Our library has developed a cheap and effective alternative to these systems using HTML 5 authoring software, a large TV, and freely-available APIs from Google, Springshare, and others. At this session, you’ll learn about the system that we have in place for displaying dynamic and easily-updatable information on our library’s large digital display, and how you can easily create something similar for your library.&lt;br /&gt;
&lt;br /&gt;
== REPOX: Metadata Blender ==&lt;br /&gt;
 &lt;br /&gt;
* John Mignault, jmignault@metro.org, Empire State Digital Network&lt;br /&gt;
&lt;br /&gt;
With the growth in the number of hubs providing metadata to the Digital Public Library of America, many of them are using REPOX, a tool originally created for the Europeana project, to aggregate disparate metadata feeds and transform them into formats suitable for ingest into DPLA. The Empire State Digital Network, the forthcoming DPLA service hub for NY state, is using it to prepare for our first ingest into DPLA in early 2015.  We'll take a look at REPOX and its capabilities and how it can be useful for ingesting and transforming metadata, and also discuss some things we've learned in massaging widely varied metadata feeds.&lt;br /&gt;
&lt;br /&gt;
== Beyond Open Source ==&lt;br /&gt;
&lt;br /&gt;
* Jason Casden, jmcasden@ncsu.edu, NCSU Libraries&lt;br /&gt;
* Bret Davidson, bddavids@ncsu.edu, NCSU Libraries&lt;br /&gt;
&lt;br /&gt;
The Code4Lib community has produced an increasingly impressive collection of open source software over the last decade, but much of this creative work remains out of reach for large portions of the library community. Do the relatively privileged institutions represented by a majority of Code4Lib participants have a professional responsibility to support the adoption of their innovations?&lt;br /&gt;
&lt;br /&gt;
Drawing from old and new software packaging and distribution approaches (from freeware to Docker), we will propose extending the open source software values of collaboration and transparency to include the wide and affordable distribution of software. We believe this will not only simplify the process of sharing our applications within the Code4Lib community, but also make it possible for less well resourced institutions to actually use our software. We will identify areas of need, present our experiences with the users of our own open source projects, discuss our attempts to go beyond open source, and make an argument for the internal value of supporting and encouraging a vibrant library ecosystem.&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]] &lt;br /&gt;
[[Category:Talk Proposals]]&lt;br /&gt;
&lt;br /&gt;
== Making It Work: Problem Solving Using Open Source at a Small Academic Library ==&lt;br /&gt;
 &lt;br /&gt;
* Adam Strohm, astrohm@iit.edu, Illinois Institute of Technology&lt;br /&gt;
* Max King, mking9@iit.edu, Illinois Institute of Technology&lt;br /&gt;
&lt;br /&gt;
The Illinois Institute of Technology campus was added to the National Register of Historic Places in 2005, and contains a building, Mies van der Rohe's S.R. Crown Hall, that was named a National Historic Landmark in 2001. Creating a digital resource that can adequately showcase the campus and its architecture is challenge enough in and of itself, but doing so as a two-person team of relative newcomers, at a university library without dedicated programmers on staff, ups the ante considerably.&lt;br /&gt;
The challenges of technical know-how, staff time, and funding are nothing new to anyone working on digital projects at a university library, and are amplified when doing so at a smaller institution. This talk covers the conception, development, and design of the campus map site that was built, concentrating on the problem-solving strategies developed to cope with limited technical and financial resources.&lt;br /&gt;
We'll talk about our approach to development with Open Source software, including Omeka, along with the Neatline and Simile Timeline plugins. We'll also discuss the juggling act of designing for mobile mapping functionality without sacrificing desktop design, weighing the costs of increased functionality versus our ability to time-effectively include that functionality, and the challenge of building a site that could be developed iteratively, with an eye towards future enhancement and sustainability. Finally, we’ll provide recommendations for other librarians at smaller institutions for their own efforts at digital development.&lt;br /&gt;
&lt;br /&gt;
== Recording Digitization History: Metadata Options for the Process History of Audiovisual Materials ==&lt;br /&gt;
 &lt;br /&gt;
* Peggy Griesinger, peggy_griesinger@moma.org, Museum of Modern Art&lt;br /&gt;
&lt;br /&gt;
The Museum of Modern Art has amassed a large collection of audiovisual materials over its many decades of existence. In order to preserve these materials, much of the audiovisual collection has been digitized. This is a complex process involving numerous steps and devices, and the methods used for digitization can have an effect on the quality of the file that is preserved. Therefore, knowing exactly how something was digitized is critical for future stewards of these objects to be able to properly care for and preserve them. However, detailed technical information about the processes involved in the digitization of audiovisual materials is not defined explicitly in most metadata schemas used for audiovisual materials. In order to record process history using existing metadata standards, some level of creativity is required to allow existing standards to express this information.&lt;br /&gt;
&lt;br /&gt;
This talk will detail different metadata standards, including PBCore, PREMIS, and reVTMD, that can be implemented as methods of recording this information. Specifically, the talk will examine efforts to integrate this metadata into the Museum of Modern Art’s new digital repository, the DRMC. This talk will provide background on the DRMC as well as MoMA’s specific institutional needs for process history metadata, then discuss different metadata implementations we have considered to document process history.&lt;br /&gt;
&lt;br /&gt;
== Pig Kisses Elephant: Building Research Data Services for Web Archives ==&lt;br /&gt;
 &lt;br /&gt;
* Jefferson Bailey,  jefferson@archive.org, Internet Archive&lt;br /&gt;
* Vinay Goel, vinay@archive.org, Internet Archive&lt;br /&gt;
&lt;br /&gt;
More and more libraries and archives are creating web archiving programs.  For both new and established programs, these archives can consist of hundreds of thousands, if not millions, of born-digital resources within a single collection; as such, they are ideally suited for large-scale computational study and analysis. Yet current access methods for web archives consist largely of browsing the archived web in the same manner as browsing the live web and the size of these collections and complexity of the WARC format can make aggregate analysis difficult. This talk will describe a project to create new ways for users and researchers to access and study web archives by offering extracted and post-processed datasets derived from web collections. Working with the 325+ institutions and their 2600+ collections within the Archive-It service, the Internet Archive is building methods to deliver a variety of datasets culled from collections of web content, including extracted metadata packaged in JSON, longitudinal link graph data, named entities, and other types of data. The talk will cover the technical details of building dataset production pipelines with Apache Pig, Hadoop, and tools like Stanford NER, the programmatic aspects of building data services for archives and researchers, and ongoing work to create new ways to access and study web archives.&lt;br /&gt;
&lt;br /&gt;
== Awesome Pi, LOL! ==&lt;br /&gt;
&lt;br /&gt;
* Matt Connolly, mconnolly@cornell.edu, Cornell University Library&lt;br /&gt;
* Jennifer Colt, jrc88@cornell.edu, Cornell University Library&lt;br /&gt;
&lt;br /&gt;
Inspired by Harvard Library Lab’s “Awesome Box” project, Cornell’s Library Outside the Library (LOL) group is piloting a more automated approach to letting our users tell us which materials they find particularly stunning. Armed with a Raspberry Pi, a barcode scanner, and some bits of kit that flash and glow, we have ventured into the foreign world of hardware development. This talk will discuss what it’s like for software developers and designers to get their hands dirty, how patrons are reacting to the Awesomizer, and LOL’s not-afraid-to-fail philosophy of experimentation.&lt;br /&gt;
&lt;br /&gt;
== You Gotta Keep 'em Separated: The Case for &amp;quot;Bento Box&amp;quot; Discovery Interfaces ==&lt;br /&gt;
 &lt;br /&gt;
* Jason Thomale,  jason.thomale@unt.edu, University of North Texas Libraries&lt;br /&gt;
&lt;br /&gt;
I know, I know--proposing a talk about Resource Discovery is like, ''so'' 2010.&lt;br /&gt;
&lt;br /&gt;
The thing is, practically all of us--in academic libraries at least--have a similar set up for discovery, with just a few variations, and so talking about it still seems useful. Stop me if this sounds familiar. You've got a single search box on the library homepage as a starting point for discovery. And it's probably a tabbed affair, with an option for searching the catalog for books, an option for searching a discovery service for articles, an option for searching databases, and maybe a few others. Maybe you have an option to search everything at once--probably the default, if you have it. And, if you're a crazy hepcat, maybe you ''only'' have your one search that searches everything, with no tabs.&lt;br /&gt;
&lt;br /&gt;
Now, the question is, for your &amp;quot;everything&amp;quot; search, are you doing a combined list of results, or are you doing it bento-box style, with a short results list from each category displayed in its own compartment?&lt;br /&gt;
&lt;br /&gt;
At UNT, we've been holding off on implementing an &amp;quot;everything&amp;quot; search, for various reasons. One reason is that the evidence for either style hasn't been very clear. There's this persistent paradox that we just can't reconcile: users tell us, through word and action, that they prefer searching Google, yet, libraries aren't Google, and there are valid design reasons why we shouldn't try to oversimplify our discovery interfaces to be like Google. And there's user data that supports both sides.&lt;br /&gt;
&lt;br /&gt;
Holding off on making this decision has granted us 2 years of data on how people use our tabbed search interface that does ''not'' include an &amp;quot;everything&amp;quot; search. Recently I conducted a thorough analysis of this data--specifically the usage and query data for our catalog and discovery system (Summon). And I think it helps make the case for a bento box style discovery interface. To be clear, it isn't exactly the smoking gun that I was hoping for, but the picture it paints I think is telling. At the very least, it points away from a combined-results approach.&lt;br /&gt;
&lt;br /&gt;
I'm proposing a talk discussing the data we've collected, the trends we've seen, and what I think it all means--plus other reasons that we're jumping on the &amp;quot;bento box&amp;quot; discovery bandwagon and why I think &amp;quot;bento box&amp;quot; is at this point the path that least sells our souls.&lt;br /&gt;
&lt;br /&gt;
== Don’t know about you, but I’m feeling like SHA-2!: Checksumming with Taylor Swift ==&lt;br /&gt;
 &lt;br /&gt;
* Ashley Blewer!, ashley.blewer@gmail.com&lt;br /&gt;
&lt;br /&gt;
Checksum technology is used all over the place, from git commits to authenticating Linux packages. It is most commonly used in the digital preservation field to monitor materials in storage for changes that will occur over time or used in the transmission of files during duplication. But do you even checksum, bro? I want this talk to move checksums from a position of mysterious macho jargon to something everyone can understand and want to use. I think a lot of people have heard of checksum but don’t know where to begin when it comes to actually using it at their institution. And cryptography is hella intimidating! This talk will cover what checksums are, how they can be integrated into a library or archival workflow, protecting collections requiring additional levels of security, algorithms used to verify file fixity and how they are different, and other aspects of cryptographic technology. Oh, and please note that all points in this talk will be emphasized or lightly performed through Taylor Swift lyrics. Seriously, this talk will consist of at least 50% Taylor Swift. Can you, like, even?&lt;br /&gt;
&lt;br /&gt;
== Level Up Your Coding with Code Club (yes, you can talk about it) ==&lt;br /&gt;
&lt;br /&gt;
* Coral Sheldon-Hess, coral@sheldon-hess.org&lt;br /&gt;
&lt;br /&gt;
Reading code is a necessary part of becoming a better developer. It gives you more experience and more insight into How Things Are (or Aren't) Done; it builds your intuition about how to solve problems with code; and it increases your confidence that you, too, can tackle whatever technological problems you're facing.&lt;br /&gt;
&lt;br /&gt;
But you don't have to read code alone! (Which is good. It's really not fun to read code alone.) &lt;br /&gt;
&lt;br /&gt;
In late 2014, a group of librarians formed two Code Clubs, inspired by [http://bloggytoons.com/code-club/ this talk by Saron] (of Bloggytoons fame). I'd like to tell you about how we've structured our Code Clubs, what has gone well, what we've learned, and what you need to do to form your own Code Club. I'll share a list of the codebases we've looked at, too, to help you get your own Code Club off the ground! &lt;br /&gt;
&lt;br /&gt;
== The Growth of a Programmer ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:jgo | Joshua Gomez]], Getty Research Institute, jgomez@getty.edu&lt;br /&gt;
&lt;br /&gt;
Just like other creative endeavors, software developers can experience periods of great productivity or find themselves in a rut. After contemplating the alternating periods in my own career I've noticed several factors that have effected my own professional growth and happiness, including: mentorship, structure, community, teamwork, environment, formal education, etc. Not all of the factors need to be present at all times; but some mixture of them is critical for continued growth. In this talk, I will articulate these factors, discuss how they can effect a developer's career, and how they can be sought out when missing. This talk is aimed at both new developers looking to strike their own path as well as the veterans that lead or mentor them.&lt;br /&gt;
&lt;br /&gt;
== Developing a Fedora 4.0 Content Model for Disk Images ==&lt;br /&gt;
&lt;br /&gt;
* Matthew Farrell, matthew.j.farrell@duke.edu, Duke University Libraries&lt;br /&gt;
* Alexandra Chassanoff, achass@email.unc.edu, BitCurator Access Project Manager&lt;br /&gt;
&lt;br /&gt;
As the acquisition of born-digital materials grows, institutions are seeking methods to facilitate easy ingest into their repositories and provide access to disk images and files derived or extracted from disk images. In this session, we describe our development of a Fedora 4.0 Content model for disk images, including acceptable image file formats and the rationale behind those choices.  We will also discuss efforts to integrate the disk image content model into the BitCurator Access environment. Unlike generalized, format-agnostic content models which might treat the disk image as a generic bitstream, a content model designed for disk images enables expression of relationships among associated content in the collection such as files extracted from images and other born-digital and digitized material associated with the same creator.  It also enables capture of file-system attributes such as file paths, timestamps, whether files are allocated/deleted, etc.  Further, a disk image content model suggests further steps repositories can take in order to transform and re-use associated metadata generated during the creation and forensic analysis of the disk image.&lt;br /&gt;
&lt;br /&gt;
== Data acquisition and publishing tools in R ==&lt;br /&gt;
&lt;br /&gt;
* Scott Chamberlain,  scott@ropensci.org, rOpenSci/UC Berkeley - first-time presenter&lt;br /&gt;
&lt;br /&gt;
R is an open source programming environment that is widely used among researchers in many fields. R is powerful because it's free, increasingly robust, and facilitates reproducible research, an increasingly sought after goal in academia. Although tools for data manipulation/visualization/analysis are well developed in R, data acquisition and publishing tools are not. rOpenSci is a collaborative effort to create the tools necessary to complete the reproducible research workflow. This presentation discusses the need for these tools, including examples, including interacting with the repositories Mendeley, Dryad, DataONE, and Figshare. In addition, we are building tools for searching scholarly metadata and acuiring full text of open access articles in a standarized way across metadata providers (e.g., Crossref, DataCite, DPLA) and publishers (e.g., PLOS, PeerJ, BMC, Pubmed). Last, we are building out tools for data reading and writing in Ecologial Metadata Language (EML).&lt;br /&gt;
&lt;br /&gt;
== SPLUNK: Log File Analysis ==&lt;br /&gt;
&lt;br /&gt;
* Jim LeFager, jlefager@depaul.edu, DePaul University Library&lt;br /&gt;
DePaul University Library recently took over monitoring and maintaining of the library EZproxy servers this past year and using Splunk, a machine data analysis tool, we are able to gather information and statistics on our electronic resource usage in addition to monitoring the servers. Splunk is a tool that can collect, analyze, and visualize log files and other machine data in real time and this has allowed for gathering realtime usage statistics for our electronic resources allowing us to filter by multiple facets including IP Range, Group Membership (student, faculty), so that we can see who is accessing our resources and from where. Splunk allows our library to query our data and create rich custom dashboards as well as create alerts that can be triggered when certain conditions are met, such as error codes, which can send an email alert to a group of users. We will be leveraging Splunk to monitor all library web applications going forward. This talk will review setting up Splunk and best practices in using the available features and customizations available including creating queries, alerts, and custom dashboards.  &lt;br /&gt;
&lt;br /&gt;
== Your code does not exist in a vacuum ==&lt;br /&gt;
* Becky Yoose, yoosebec at grinnell dot edu, Grinnell College (Done a lightning talk, MC duties, but have not presented a prepared talk)&lt;br /&gt;
&lt;br /&gt;
“If you have something to say, then say it in code…” - Sebastian Hammer, code4lib 2009&lt;br /&gt;
&lt;br /&gt;
In its 10 year run, code4lib has covered the spectrum of libtech development, from search to repositories to interfaces. However, during this time there has been little discussion about this one little fact about development - code does not exist in a vacuum. &lt;br /&gt;
&lt;br /&gt;
Like the comment above, code has something to say. A person’s or organization’s culture and beliefs influences code in all steps of the development cycle. What development method you use, tools, programming languages, licenses - everything is interconnected with and influenced by the philosophies, economics, social structures, and cultural beliefs of the developer and their organization/community.&lt;br /&gt;
&lt;br /&gt;
This talk will discuss these interconnections and influences when one develops code for libraries, focusing on several development practices (such as “Fail Fast, Fail Often” and Agile)   and licensing choices (such as open source) that libtech has either tried to model or incorporate into mainstream libtech practices. It’ll only scratch the surface of the many influences present in libtech development, but it will give folks a starting point to further investigate these connections at their own organizations and as a community as a whole.&lt;br /&gt;
&lt;br /&gt;
tl;dr - this will be a messy theoretical talk about technology and libraries. No shiny code slides, no live demos. You might come out of this talk feeling uncomfortable. Your code does not exist in a vacuum. Then again, you don’t exist in a vacuum either.&lt;br /&gt;
&lt;br /&gt;
== The Metadata Hopper: Mapping and Merging Metadata Standards for Simple, User-Friendly Access ==&lt;br /&gt;
&lt;br /&gt;
* Tracy Seneca, tjseneca@uic.edu, University of Illinois at Chicago&lt;br /&gt;
* Esther Verreau: verreau1@uic.edu, University of Illinois at Chicago&lt;br /&gt;
&lt;br /&gt;
The Chicago Collections Consortium: 15 institutions and growing!  8 distinct EAD standards! At least 3 permutations of MARC, and we lost count of the varieties of custom CONTENTdm image collections.  Not to mention the 14,730 unique subject terms, nearly all of which lead our poor end-users to exactly one organization's content. &lt;br /&gt;
&lt;br /&gt;
All large content aggregation projects have faced this challenge, and there are a few emerging tools to help us wrangle disparate metadata into new contexts.  The Metadata Hopper is one such tool. The Metadata Hopper enables archivists to map their local metadata standards to standardized deposit records, and tags those materials using a shared vocabulary, integrating them into a user-friendly portal without disrupting local practices. In last year's Code4Lib lightning talk we described the challenges that the Chicago Collections Consortium faces in creating shared, in-depth access to archival and digital collections about Chicago history and culture across CCC member organizations. This year, thanks to the Andrew W. Mellon Foundation, we have a working Django application to demonstrate.  In this talk we'll discuss the design that enables multiple layers of flexibility, from the ability to accept a variety of metadata standards to designing for an open source audience.&lt;br /&gt;
&lt;br /&gt;
http://chicagocollectionsconsortium.org&lt;br /&gt;
&lt;br /&gt;
== Programmers are not projects: lessons learned from managing humans ==&lt;br /&gt;
&lt;br /&gt;
* Erin White, erwhite@vcu.edu, Virginia Commonwealth University - first-time presenter&lt;br /&gt;
&lt;br /&gt;
Managing projects is one thing, but managing people is another. Whether we’re hired as managers or grow “organically” into management roles, sometimes technical people end up leading technical teams (gasp!). I’ll talk about lessons I’ve learned about hiring, retaining, and working long-term and day-to-day with highly tech-competent humans. I’ll also talk about navigating the politics of libraryland, juggling different types of projects, and working with constrained budgets to make good things and keep talented people engaged.&lt;br /&gt;
&lt;br /&gt;
== Practical Strategies for Picking Low-Hanging Fruits to Improve Your Library's Web Usability and UX ==&lt;br /&gt;
&lt;br /&gt;
* Bohyun Kim, bkim@hshsl.umaryland.edu, University of Maryland, Baltimore&lt;br /&gt;
&lt;br /&gt;
Have you ever tried to fix an obvious (to you at least!) problem in Web usability or UX (user experience) only to face strong resistance from the library staff? Are you a strong advocate for making library resources, systems, services, and space as usable as possible, but do you often find yourself struggling to get the point across and/or obtain the crucial buy-in from colleagues and administrators? &lt;br /&gt;
&lt;br /&gt;
There is no shortage of Web usability and UX guidelines. But applying them to a library and implementing desired changes often involve a long and slow process. To tackle this issue, this talk will focus on how to utilize the 'expert review' process (aka 'heuristic evaluation') as a preliminary or even preparatory step before embarking on more time-and-labor-intensive usability testing and user research. Several examples from  simple fixes to more nuanced usability and UX issues in libraries will be discussed to your heart's content. The goal of this talk is to provide practical strategies for picking as many low-hanging fruits as possible to make a real (albeit small) difference to your library's Web usability and UX effectively and efficiently.&lt;br /&gt;
&lt;br /&gt;
== A Semantic Makeover for CMS Data ==&lt;br /&gt;
&lt;br /&gt;
* Bill Levay, wjlevay@gmail.com, Linked Jazz Project&lt;br /&gt;
&lt;br /&gt;
How can we take semi-structured but messy metadata from a repository like CONTENTdm and transform it into rich linked data? Working with metadata from Tulane’s Hogan Jazz Archive Photography Collection, the Linked Jazz Project used Open Refine and Python scripts to tease out proper names, match them with name authority URIs, and specify FOAF relationships between musicians who appear together in photographs. Additional RDF triples were created for any dates associated with the photos, and for those images with place information we employed GeoNames URIs. Historical images and data that were siloed can now interact with other datasets, like Linked Jazz’s rich set of names and personal relationships, and can be visualized [link to come] or otherwise presented on the web in any number of ways. I have not previously presented at a Code4Lib conference.&lt;br /&gt;
&lt;br /&gt;
== Taking User Experience (UX) to new heights ==&lt;br /&gt;
 &lt;br /&gt;
* Kayne Richens, kayne.richens@deakin.edu.au, Deakin University&lt;br /&gt;
&lt;br /&gt;
User Experience, or &amp;quot;UX&amp;quot;, is for more than just websites. At Deakin University Library we're exploring ways to improve the user experience inside our campus library spaces, by putting new technologies front and centre in the overall experience for our students. How are we doing this? We’re collaborating with the University's IT department and exploring the following Library-changing opportunities:&lt;br /&gt;
&lt;br /&gt;
- Augmented Reality for Way-finding: We’re tackling that infamous thing that all Libraries can't get right – way-finding. We're enhancing library tour information and way-finding experiences by introducing augmented reality solutions.&lt;br /&gt;
 &lt;br /&gt;
- Heat mapping the library with wi-fi: We’re using our existing wi-fi infrastructure to present &amp;quot;heat maps&amp;quot; of library space utilisation, allowing our users to easily locate the space that best suits their needs, whether it be busy spaces to collaborate, or quiet spaces to study. And by overlaying computer usage and group study room bookings, users can quickly locate the space they need.&lt;br /&gt;
 &lt;br /&gt;
- Video chat library service: We’re piloting video-conferencing facilities in our group study rooms and spaces, connecting users and librarians and other professionals.&lt;br /&gt;
         &lt;br /&gt;
This talk will look at how these different technologies will be brought together to provide improved user experiences, as well some of the evidence and reasons that helped us to identify our needs, so you can too.&lt;br /&gt;
&lt;br /&gt;
==How to Hack it as a Working Parent: or, Should Your Face be Bathed in the Blue Glow of a Phone at 2 AM?==&lt;br /&gt;
&lt;br /&gt;
*Margaret Heller, Loyola University Chicago, mheller1@luc.edu&lt;br /&gt;
*Christina Salazar, California State University Channel Islands, christina.salazar@csuci.edu&lt;br /&gt;
*May Yan, Ryerson University, may.yan@ryerson.ca&lt;br /&gt;
&lt;br /&gt;
Modern technology has made it easier than ever for parents employed in technical environments to keep up with work at all hours and in all locations. This makes it possible to work a flexible schedule, but also may lead to problems with work/life balance and furthering unreasonable expectations about working hours. Add to that shifting gender roles and limited paid parental leave in the United States and you have potential for burnout and a certainty for anxiety. It raises the additioal question of whether the “always connected” mindset puts up a barrier to some populations who otherwise might be better represented in open source and library technology communities. &lt;br /&gt;
&lt;br /&gt;
This presentation will address tools that are useful for working parents in technical library positions, and share some lessons learned about using these tools while maintaining a reasonable work/life balance. We will consider a question that Karen Coyle raised back in 1996: &lt;br /&gt;
“What if the thousands of hours of graveyard shift amateur hacking wasn't really the best way to get the job done? That would be unthinkable.” &lt;br /&gt;
&lt;br /&gt;
For those who are able to take an extended parental leave, we will present strategies for minimizing the impact to your career and your employer. For those (particularly in the United States) who are only able to take a short leave will require different strategies. Despite different levels of preparation, all are useful exercises in succession planning and making a stronger workplace and future ability to work a flexible schedule through reviewing workloads, cross-training personnel, hiring contract replacements, and creative divisions of labor. Such preparation makes work better for everyone, kids or no kids.&lt;br /&gt;
&lt;br /&gt;
==Making your digital objects embeddable around the web==&lt;br /&gt;
 &lt;br /&gt;
* Jessie Keck, jkeck@stanford.edu, Stanford University Libraries&lt;br /&gt;
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
With more and more content from our digital repositories making their way into our discovery environments we quickly realize that we’re repeatedly re-inventing the wheel when it comes to creating “Viewers” for these digital objects.  With various different types of viewers necessary (books, images, audio, video, geospatial data, etc) the burden of getting these viewers into various environments (topic guides, blogs, catalogs, etc) becomes exponential.&lt;br /&gt;
&lt;br /&gt;
In this talk we’ll discuss how Stanford University Libraries implemented an oEmbed service to create an extensible viewer framework for all of its digital content. Using this service we’ve been able to easily integrate viewers into various discovery applications as well as make it easy for end users who discover our objects to easily embed customized versions into their own websites and blogs.&lt;br /&gt;
&lt;br /&gt;
==So you want to make your geospatial data discoverable==&lt;br /&gt;
 &lt;br /&gt;
* Jack Reed, pjreed@stanford.edu, Stanford University Libraries&lt;br /&gt;
&lt;br /&gt;
Finding data for research or coursework can be one of the most time intensive tasks for a scholar or student. We introduce GeoBlacklight, an open source, multi-institutional software project focused on solving these common challenges at institutions across the world. GeoBlacklight prioritizes user experience, integrates with many GIS tools, and streamlines the use and organization of geospatial data. This talk will provide an introduction to the software, demonstrate current functionality, and provide a road map for future work.&lt;br /&gt;
&lt;br /&gt;
== Clueless-Driven Development: How I learned to migrate to Fedora 4 ==&lt;br /&gt;
&lt;br /&gt;
* Adam Wead, awead@psu.edu, Penn State University&lt;br /&gt;
&lt;br /&gt;
Recently I was tasked with migrating the content from our Fedora3 repository to the new Fedora4 repository architecture.&lt;br /&gt;
Despite a wealth of community support, I had no idea how to approach, or even begin to solve this problem. I knew I&lt;br /&gt;
wanted to follow best practices and use test-driven  development to build my solution, but had no idea where to start.&lt;br /&gt;
Despite this initial setback, I was able to start writing tests with only a  vague understanding of the problem. As my&lt;br /&gt;
tests exposed where my understanding of the problem was flawed, my code evolved, and within a week I had arrived  at a&lt;br /&gt;
working solution that exhibited all the hallmarks of good testing and software design.&lt;br /&gt;
&lt;br /&gt;
This talk recounts the process I went through from starting with practically nothing, to arriving at a working solution.&lt;br /&gt;
You can follow the rules of  test-driven development, but you can write tests in an expressive way to describe the&lt;br /&gt;
problem instead of just describing what the code should do. It was also essential to begin testing from an integration&lt;br /&gt;
viewpoint as opposed to a unit one, because at the outset the units were unknown and were later realized through further&lt;br /&gt;
development. For the presentation, I will be demonstrating using RSpec and Ruby. All the code examples will be related&lt;br /&gt;
to the Hydra software stack; however, I hope to show  that the processes at work will be applicable in any context.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Designing and Leading a Kick A** Tech Team ==&lt;br /&gt;
 &lt;br /&gt;
* Sibyl Schaefer,  sschaefer@rockarch.org, Rockefeller Archive Center&lt;br /&gt;
&lt;br /&gt;
New managers are often promoted without receiving management training, yet management is not something you just figure out. The experience of being expected to know how to manage, yet not being trained to do so often results in new managers feeling isolated and unsure how to move from making to managing. In this talk I’ll focus on my own managerial experience of designing and leading an archival tech team in a small independent archives. Topics covered will include hiring, delegating, creating a team culture, and leading people whose specialized knowledge exceeds your own. The talk take-aways should be applicable to managers and employees at large and small institutions alike.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==American (Archives) Horror Story: LTO Failure and Data Loss ==&lt;br /&gt;
 &lt;br /&gt;
* Rebecca Fraimow, rebecca_fraimow@wgbh.org, NDSR Resident, WGBH&lt;br /&gt;
&lt;br /&gt;
Here’s a story to send shivers down archival spines: when transferring video files off LTO for the American Archive project, WGBH got an initial failure rate of 57%.   After repeat tries, the rates improved; still, an unnervingly large percentage of files were never able to be transferred successfully.   Even more unnerving, going public with our horror story got a big response from other archives using LTO -- it seems like many institutions are having similarly scary results.   What are the real risks with LTO tape?  Are there steps that archives should be taking to better circumvent those risks?  This presentation will share information about LTO storage failures across archives world and discuss the process of investigating the problem at WGBH by testing different methods of data retrieval from LTO (direct and networked downloads, individual file retrieval and bulk data dump, use of LTO 4 and LTO 6 decks) and using checksum comparisons and file analysis and characterization tools such as ffprobe, mediainfo and exiftool to analyze failed files.  We'll also present whatever results we’ve managed to turn up by the time of Code4Lib!&lt;/div&gt;</summary>
		<author><name>Afred</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2013_social_activities&amp;diff=36476</id>
		<title>2013 social activities</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2013_social_activities&amp;diff=36476"/>
				<updated>2013-02-12T15:45:54Z</updated>
		
		<summary type="html">&lt;p&gt;Afred: /* Newcomer Dinner, Tuesday 2/12 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Ideas ==&lt;br /&gt;
&lt;br /&gt;
* Aviary: super-crazy cocktails. http://www.molecularrecipes.com/molecular-mixology/aviary-cocktails/ . List your name if you're interested, whether Sunday, Monday, and/or Tuesday (after newcomer dinners) work, and whether you're just interested in stopping by, or doing a 7 cocktail tasting flight.*&lt;br /&gt;
** statsfool: sunday/monday/tuesday, either drinks or flight.&lt;br /&gt;
** Amyhannah: monday/tuesday, drinks, probably not the flight.&lt;br /&gt;
** anarchivist: sunday/monday, prefer drinks over flight but could be convinced&lt;br /&gt;
** [[User:highermath|highermath]]: monday (could use 10 cocktails after Drupal subCon, I am sure). Uber now works in Chicago, so I would do the flight.&lt;br /&gt;
** [[User:pberry|pberry]]: any night but Wednesday (that's  Goose Island night) and I'd be up for drinks or flight, although leaning away from flight.&lt;br /&gt;
** [[User:thatandromeda|thatandromeda]] oh my gosh yes, any time, probably not the flight.&lt;br /&gt;
** [[User:Gdave|gdave]] beautiful site, I would be interested, Sun,Mon,Tues.  either drink or flight.&lt;br /&gt;
** [[User:shawnc12|shawnc12]]: sunday/monday, either drink or flight&lt;br /&gt;
** wdenton: any night, either drink or flight&lt;br /&gt;
** beatricep: sunday/monday drink, highly susceptible to flight by peer pressure..&lt;br /&gt;
** ryan hess: sunday/monday drink or flight&lt;br /&gt;
** infosoph: sunday/monday yes/yes!!&lt;br /&gt;
** [[User:Pfeeley|Pfeeley]]: sunday/monday/tuesday, either drink or flight&lt;br /&gt;
** [[User:Ksprague|Ksprague]]: tuesday, drink or flight&lt;br /&gt;
** [[User:schwartzray|schwartzray]]: anything on any day&lt;br /&gt;
* Brewery tour - some possible candidates would be Goose Island, Brew Bus http://www.chicagobrewbus.com/, Piece, Revolution, Half Acre.&lt;br /&gt;
* Library field trips - because we're library geeks. Possible places include Newberry and Read/Write.--Read/Write Library confirmed for February 11.--Newberry Library confirmed for February 14.&lt;br /&gt;
* Art Institute of Chicago - Only open until 5pm, but possible for people coming in early enough on Sunday. There seems to be enough interest here to actually have a group, when and where should we meet? I added my email so that we could discuss details off the wiki.&lt;br /&gt;
** escowles: I'm getting in around noon on Sunday, and interested in this.&lt;br /&gt;
** pgrayove at gmail dot com: I'm getting in around noon on Sunday too.  I'm interested.&lt;br /&gt;
** ranti: And I am. &lt;br /&gt;
** tshearerlib: Coming in at around the same time and hope to get to the museum by 1:00.  Lunch first?&lt;br /&gt;
* Local Option http://localoptionbier.com/ - So you've heard of Hopleaf, you've heard of Maproom. Come to Chicago's *ahem* best kept secret for good food and an evening session on Monday. We will need a tally to make requisite arrangements. Target for arrival at bar: 7ish. Probably a group gathering to head north around 6:30 in hotel lobby (if you want to take the #8 Halsted bus that is).&lt;br /&gt;
** kayiwa&lt;br /&gt;
** Linda Ballinger&lt;br /&gt;
** Courtney Greene&lt;br /&gt;
** John Pillans&lt;br /&gt;
** +6 from NCSU incl one Bret Davidson&lt;br /&gt;
** Megan Kudzia&lt;br /&gt;
** Andrew Darby&lt;br /&gt;
** erinrwhite&lt;br /&gt;
** Will Clarke&lt;br /&gt;
** Cody Hanson&lt;br /&gt;
** Jesse Brown&lt;br /&gt;
** Matt Cordial +1 (my friend and I were already planning a Monday trip here)&lt;br /&gt;
** Ray Schwartz&lt;br /&gt;
** Eric Larson&lt;br /&gt;
** David Cliff&lt;br /&gt;
** Ken Irwin&lt;br /&gt;
** Dileshni Jayasinghe&lt;br /&gt;
&lt;br /&gt;
== Planned Events ==&lt;br /&gt;
&lt;br /&gt;
===Read/Write Library Field Trip, Monday 2/11===&lt;br /&gt;
Field trip to the [http://readwritelibrary.org/ Read/Write Library] 6:30PM-9PM &lt;br /&gt;
&lt;br /&gt;
Drop in whenever during this time.&lt;br /&gt;
&lt;br /&gt;
Come help catalog the Read/Write Library catalog and hack on the library catalog. We will get food or go to a nearby restaurant depending on interest. We will also invite friends from Code for America to hang out and talk civic data. Bring your laptop along if you have one.&lt;br /&gt;
&lt;br /&gt;
Let us know if you are coming so we can figure out food:&lt;br /&gt;
* Margaret Heller&lt;br /&gt;
* Ranti Junus&lt;br /&gt;
* Wayne Schneider&lt;br /&gt;
* jrochkind will try to make it&lt;br /&gt;
* emily shaw (may be a little late)&lt;br /&gt;
* &amp;lt;strike&amp;gt;kenirwin - bailed on acct of pre-conf brain death&amp;lt;/strike&amp;gt;&lt;br /&gt;
* Andromeda - yes, unless someone gets Aviary reservations&lt;br /&gt;
* Chris Clement - may attend&lt;br /&gt;
(hey, there are great bars in that neighborhood!)&lt;br /&gt;
* wdenton&lt;br /&gt;
&lt;br /&gt;
'''Directions to the library from UIC:'''&lt;br /&gt;
&lt;br /&gt;
''Bus''&lt;br /&gt;
&lt;br /&gt;
Take the #8 Halsted Bus north to Chicago (Bus will say &amp;quot;#8 Halsted/79th North to Broadway/Waveland&amp;quot;)&lt;br /&gt;
Take the #66 Chicago Bus west to California (Bus will say either &amp;quot;#66 Chicago west to Austin&amp;quot; or &amp;quot;#66 Chicago West to Pulaski.&amp;quot; You can take either one because both Austin and Pulaski are further west than we are so both stop at California)&lt;br /&gt;
The Chicago bus stops on the west side of California, which is the side of the street we're on. On California, walk a block north to Walton.&lt;br /&gt;
&lt;br /&gt;
''Train + Bus (slightly faster/more reliable, but only by about 5-10 minutes)''&lt;br /&gt;
&lt;br /&gt;
Walk to the UIC/Halsted Blue Line &lt;br /&gt;
Take the O'Hare train (toward the Loop) and go all the way through the Loop and back west. Get off at Chicago and use the exit that says &amp;quot;North side of Chicago Ave&amp;quot; (or something similar — I don't remember exactly).&lt;br /&gt;
Take the #66 Chicago Bus west to California (Bus will say either &amp;quot;#66 Chicago west to Austin&amp;quot; or &amp;quot;#66 Chicago West to Pulaski.&amp;quot; You can take either one because both Austin and Pulaski are further west than we are so both stop at California)&lt;br /&gt;
The Chicago bus stops on the west side of California, which is the side of the street we're on. On California, walk a block north to Walton.&lt;br /&gt;
&lt;br /&gt;
=== Newcomer Dinner, Tuesday 2/12 ===&lt;br /&gt;
&lt;br /&gt;
First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating &amp;lt;strike&amp;gt;discussions about&amp;lt;/strike&amp;gt; demonstrations of the many uses of &amp;lt;strike&amp;gt;bacon&amp;lt;/strike&amp;gt; &amp;lt;strike&amp;gt;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/12)&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 tech type folks&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;
&lt;br /&gt;
'''Restaurants within .25 miles of the hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://www.athenarestaurantchicago.com/index.php Athena] (Greek)&lt;br /&gt;
&lt;br /&gt;
* Al Cornish - v (leader)&lt;br /&gt;
* Carolyn Cole - n&lt;br /&gt;
* Dileshni Jayasinghe - v&lt;br /&gt;
* Will Clark - n&lt;br /&gt;
* Adam Constabaris - v&lt;br /&gt;
* Patrick Hogan - n&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.dinerestaurant.com/ Dine] (Contemporary)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;del&amp;gt;[http://www.girlandthegoat.com/ Girl and the Goat] (American) Top Chef fans take note! This is Stephanie Izard's award-winning resto.&amp;lt;/del&amp;gt; Totally booked.&lt;br /&gt;
&lt;br /&gt;
[http://littlegoatchicago.com/ Little Goat] - Izard just opened a diner across the street from G&amp;amp;G that is walk-in only. (very good, probably a wait but they also have a bar in the back --wickr)&lt;br /&gt;
&lt;br /&gt;
[http://www.haymarketbrewing.com/ Haymarket Pub &amp;amp; Brewery] (Pub food) - Reservations at 6:30pm. Meet in conference hotel lobby at 6:10pm&lt;br /&gt;
&lt;br /&gt;
* Ryan Wick (leader) - v&lt;br /&gt;
* Sean Purcell - v&lt;br /&gt;
* Dan Fehrenbach - n&lt;br /&gt;
* Pierre Nault - n&lt;br /&gt;
* Minh-Quang Nguyen - n&lt;br /&gt;
* Matt Bernhardt - n&lt;br /&gt;
* Jim LeFager - n&lt;br /&gt;
* '''Capped at 7'''&lt;br /&gt;
&lt;br /&gt;
[http://www.karynsongreen.com/ Karyn’s on Green] (Vegan)&lt;br /&gt;
Completely vegan and close to the conference hotel. We'll meet in the conference hotel at around 6:45 (reservation at 7:00 for 6). Google maps says it is a 5 minute walk.&lt;br /&gt;
&lt;br /&gt;
*Jason Ronallo (leader)- v&lt;br /&gt;
*Alicia Cozine - n&lt;br /&gt;
*Mark Mounts - v&lt;br /&gt;
*Barbara Hui - n&lt;br /&gt;
*Amy Deschenes - n&lt;br /&gt;
*Adam Strohm - n&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://niarestaurant.com/nia-restaurant-mediterranean-cuisine/ Nia] (Mediterranean tapas)&lt;br /&gt;
&lt;br /&gt;
[http://www.pegasuschicago.com/index.php Pegasus] (Greek)&lt;br /&gt;
&lt;br /&gt;
[http://www.roditys.com/index.html Roditys] (Greek) -- Reservations made for 6:30pm.  Let's meet in the hotel lobby at 6pm and walk over from there.  Its ok if you're a bit late to the lobby, we'll wait.  If you have any questions email Rosalyn (Rosy) rosalynmetz at gmail dot com&lt;br /&gt;
&lt;br /&gt;
* Rosalyn Metz (leader) - v&lt;br /&gt;
* [[User:highermath|Cary Gordon]] - v&lt;br /&gt;
* [[User:Jacobandresen|Jacob Andresen]] - n&lt;br /&gt;
* Karen Miller - n&lt;br /&gt;
* Dre - v&lt;br /&gt;
* Mahria Lebow - n&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
'''Restaurants between .25 miles and .5 miles of the hotel'''&lt;br /&gt;
&lt;br /&gt;
Code4lib Chicago Celery Salt Society - [http://www.alsbeef.com/ Al's Beef]&lt;br /&gt;
&lt;br /&gt;
* Jason Casden (leader) - v - No reservations. We can walk from the hotel at 7.&lt;br /&gt;
* Charlie Morris - n&lt;br /&gt;
* Cory Lown - v&lt;br /&gt;
* Carolina Garcia - n&lt;br /&gt;
* Cody Hanson - n&lt;br /&gt;
* Ken Varnum - v&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://avecrestaurant.com/# Avec] (Small plate)&lt;br /&gt;
Family-style small plate and tapas.  Great Yelp reviews.  We'll meet in the conference hotel at 6:00 &amp;lt;strike&amp;gt;6:45&amp;lt;/strike&amp;gt; (they don't take reservations, but have stuff to sip on if there's a wait).  Less than 10 minute walk from hotel.&lt;br /&gt;
&lt;br /&gt;
* Shaun Ellis (leader) - v&lt;br /&gt;
* Jon Stroop - v&lt;br /&gt;
* Paula Gray-Overtoom - n&lt;br /&gt;
* Emily Zervas - n&lt;br /&gt;
* Cynthia Ng - neither&lt;br /&gt;
* Sarah Dooley - n&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.babavillage.com/ Baba’s Village] (Indian/Pakistani)&lt;br /&gt;
&lt;br /&gt;
[http://blackbirdrestaurant.com/ Blackbird] (Contemporary)&lt;br /&gt;
&lt;br /&gt;
(Since the reservation is late, does anyone want to meet for drink in the hotel bar beforehand? There's really no place to wait at the restaurant, and there's no nice bar nearby that I can recall. cm)&lt;br /&gt;
* Justin Coyne (reserver) - v - Reservation for Blackbird for 6 at 8:30pm&lt;br /&gt;
* Matt Cordial - v&lt;br /&gt;
* [http://wiki.code4lib.org/index.php/User:Camcclure Christine McClure - n]&lt;br /&gt;
* Devin Higgins - n (devinhiggins at gmail)&lt;br /&gt;
* Ken Irwin&lt;br /&gt;
* Tad Merchant - n (tadoneus @ gmail)&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.carnivalechicago.com/menu Carnivale] (Nuevo Latino)&lt;br /&gt;
* Nettie Lagace (oh hell, I'll host - I'll call over this afternoon(Tues)) - n/v&lt;br /&gt;
&lt;br /&gt;
[http://decero.hellotacos.com/ De Cero] (Mexican)&lt;br /&gt;
&lt;br /&gt;
[http://www.dragonflymandarin.com/  Dragonfly] (Chinese, sushi)&lt;br /&gt;
&lt;br /&gt;
[http://giordanos.com/ Giordano's] (Chicago Style Pizza) This place should be able to handle multiple groups...&lt;br /&gt;
&lt;br /&gt;
* Andrew Nagy (leader) - v&lt;br /&gt;
* Virginia Schilling - n&lt;br /&gt;
* Jane Sandberg - n&lt;br /&gt;
* Richard Aroksaar - n&lt;br /&gt;
* Jesse Brown - n (jfbrown78 at gmail dot com)&lt;br /&gt;
* John Macgillivray&lt;br /&gt;
* Alicia Morris&lt;br /&gt;
* Ayla Stein - n&lt;br /&gt;
* Sharona Ginsberg - n&lt;br /&gt;
* Andrew Myers - n&lt;br /&gt;
[http://www.grangehallburgerbar.com/ Grange Hall Burger Bar] (Local food)&lt;br /&gt;
&lt;br /&gt;
[http://www.idreamoffalafel.com/  I Dream of Falafel] (Mediterranean) -- No reservations -- this is a casual place. Supposed to be an 8 minute walk from the hotel. Let's meet at 6:20pm in the Crowne Plaza lobby. I have chin-length brown hair and probably will be holding a paper scribbled with 'falafel.'&lt;br /&gt;
&lt;br /&gt;
* Emily Lynema (leader) - v&lt;br /&gt;
* Christie Peterson - n&lt;br /&gt;
* James Stuart - v&lt;br /&gt;
* Emily Shaw - n (emilyfshaw at gmail dot com)&lt;br /&gt;
* Ian Chan - n (ichan@csusm.edu)&lt;br /&gt;
* Zeno Tajoli - n&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.jaipurchicago.com/ Jaipur] (Indian; Reservation made for 6 at 6:30)&lt;br /&gt;
-- Let's meet in the crowne plaza lobby @ 6:15; it's supposed to be a 6 minute walk&lt;br /&gt;
&lt;br /&gt;
* Andrew Darby (leader) - v&lt;br /&gt;
* Josh Wilson (joshwilsonnc at gmail) - n&lt;br /&gt;
* Tim Thompson - n&lt;br /&gt;
* Mariela Hristova - n&lt;br /&gt;
* ryan hess - n&lt;br /&gt;
* Patrick Feeley - n&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://lasardine.com/ La Sardine] (French)&lt;br /&gt;
&lt;br /&gt;
[http://www.mythaitakumi.com/index.html MyThai Takumi] (Japanese Thai) Reservation at 6:15. Meet in the hotel lobby at 6 pm. Look for the women in a trench coat and hat.&lt;br /&gt;
&lt;br /&gt;
*Becky Yoose (leader) b dot yoose at gmail - v&lt;br /&gt;
*May Chan - n&lt;br /&gt;
*David Anderson - newby&lt;br /&gt;
*Terry Brady - new&lt;br /&gt;
* Dave Menninger - n&lt;br /&gt;
*Shawn Carraway -n&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.nellcoterestaurant.com/ Nellcôte] (French)&lt;br /&gt;
&lt;br /&gt;
[http://chicago.provincerestaurant.com/ Province] (American with Central/South American/Spanish influence)&lt;br /&gt;
&lt;br /&gt;
[http://thepublicanrestaurant.com/ The Publican] (Seafood)&lt;br /&gt;
&lt;br /&gt;
* Jay Luker (eater) - v - Rezzie is for 8pm&lt;br /&gt;
* Mark Matienzo (tweeter) - v&lt;br /&gt;
* Devon Smith (pickle eater) - repeat offender&lt;br /&gt;
* Chris Sharp (dead horse beater) - v&lt;br /&gt;
* Michael B. Klein (greeter) - v&lt;br /&gt;
* Bill McMillin (meeter) - n&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://saigonsisters.tumblr.com/ Saigon Sisters] (Vietnamese) Reservation for 6:15, meet in hotel lobby&lt;br /&gt;
* Margaret Heller - v and leader&lt;br /&gt;
* Sharon Clapp - n&lt;br /&gt;
* Sean Crowe - n&lt;br /&gt;
* Meghan Finch - n&lt;br /&gt;
* Maccabee Levine - v&lt;br /&gt;
* James Griffin - n&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.thaiurbankitchen.com/ Thai Urban Kitchen] (Thai, sushi)&lt;br /&gt;
&lt;br /&gt;
[http://www.trattoriaisabellachicago.com/rest.html Trattoria Isabella] (Italian)&lt;br /&gt;
&lt;br /&gt;
[http://www.vivo-chicago.com/homepage-2 Vivo] (Italian) &lt;br /&gt;
&lt;br /&gt;
[http://www.wishbonechicago.com/dining/westloop/ Wishbone] (Southern Reconstruction)&lt;br /&gt;
&lt;br /&gt;
* Rachel Shaevel (herder, self-proclaimed dictator, and reservation maker) - n  (we're on for 6:15!)&lt;br /&gt;
* Myrna E Morales (follower) - n&lt;br /&gt;
* Sarah Thorngate - n&lt;br /&gt;
* Steven Marsden - n&lt;br /&gt;
* David Lacy - v&lt;br /&gt;
* Luke Gaudreau - n&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
'''Restaurants between .5 miles and .75 miles of the hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://currentsontheriver.com/ Currents on the River] (Eclectic)&lt;br /&gt;
&lt;br /&gt;
[http://n9ne.com/ N9NE Steakhouse] (Steak)&lt;br /&gt;
&lt;br /&gt;
[http://www.verachicago.com/menu Vera Chicago] (Spanish)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Restaurants between .75 miles and 1 mile of the hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://www.theberghoff.com/default.aspx The Berghoff] (German)&lt;br /&gt;
* Declan Fleming - v (leader)  I checked reservations, and for 6 people, the first time open after the conf is 7:30, so I grabbed that.&lt;br /&gt;
** Let's meet in the lobby at 7p and cab over (or would people rather walk?)&lt;br /&gt;
* Dave Green - n &lt;br /&gt;
* Steven Villereal - n&lt;br /&gt;
* Peter Murray - v&lt;br /&gt;
* Trey Terrell - n&lt;br /&gt;
* Mike Giarlo - v&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.yelp.com/biz/frontera-grill-chicago Frontera] (a Rick Bayliss Mex-American restaurant) Reservations are for 7:30, so perhaps the group could get a drink in the lobby beforehand.  Either way, we'll depart at 7pm.&lt;br /&gt;
: (''note: the drinks at the bar at frontera are very tasty.'')&lt;br /&gt;
*Dan Suchy (leader and over-eater) - v&lt;br /&gt;
*Matt Critchlow - v&lt;br /&gt;
*Carmen Mitchell - v&lt;br /&gt;
*Maureen Callahan - n&lt;br /&gt;
*David Cliff - n&lt;br /&gt;
* Patrick Berry - 3rd year red-shirt freshman&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.nativefoods.com/ Native Foods] (Vegan) lots of vegan, vegetarian, gluten free options. No reservations needed. We could meet near the convention center or Daley library around 6 and take the train together. Lots of places to get drinks afterwards. &lt;br /&gt;
&lt;br /&gt;
I will wait at 5:30 at outside the UIC forum for anyone who wants to meet here. We'll pick up everyone else at Daley library at 6, then walk to the train station together. &lt;br /&gt;
&lt;br /&gt;
*Annie Pho(potential leader) - n &lt;br /&gt;
*Lauren Magnuson - n&lt;br /&gt;
*Bennett Magnino - n (meeting outside the Daley library sounds good)&lt;br /&gt;
*Kelly Thompson - n&lt;br /&gt;
*Audrey Altman - n&lt;br /&gt;
*Mackenzie Brooks - n&lt;br /&gt;
*Steven Bassett - n (Can't wait! Native Foods is awesome!).&lt;br /&gt;
'''Restaurants more than 1 mile from the hotel'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://www.greenzebrachicago.com/index.html Green Zebra] (Vegan)&lt;br /&gt;
&lt;br /&gt;
[http://honkytonkbbqchicago.com/ Honky Tonk Barbeque] (BBQ)&lt;br /&gt;
*Allan Berry (leader) - n&lt;br /&gt;
*Jason Raitz - n&lt;br /&gt;
*Brian Wu - n&lt;br /&gt;
*Gary Maixner - n&lt;br /&gt;
*Keith Nickum -v&lt;br /&gt;
*&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
[http://www.karynraw.com/cooked Karyn’s Cooked] (Vegan)&lt;br /&gt;
&lt;br /&gt;
[http://www.latabernatapas.com/ La Taberna Tapas] (Mediterranean)&lt;br /&gt;
&lt;br /&gt;
[http://www.morganschicago.com/ Morgan's on Maxwell] (Pub food)&lt;br /&gt;
&lt;br /&gt;
[http://www.chezjoelbistro.com/ Chez Joël] (French/Tangiers food) I am leaning towards an early dinner of 6:15 as I have to take-off to make sure the Game Night takes off without a hitch. So leave the conference hotel by 5:45 if it is walk weather or 6PM if it is taxi weather.&lt;br /&gt;
&lt;br /&gt;
* Francis Kayiwa (knackered leader) - v&lt;br /&gt;
* Megan O'Neill Kudzia - n&lt;br /&gt;
* Esther Verreau - n&lt;br /&gt;
* Michael Neidhardt - n&lt;br /&gt;
* Rikke Willer - n&lt;br /&gt;
* Esme Cowles - v&lt;br /&gt;
* '''Capped at 6'''&lt;br /&gt;
&lt;br /&gt;
=== Veg*n Dinner ===&lt;br /&gt;
&lt;br /&gt;
Let's have dinner at a veg*n-friendly place one night of the conference. Folks of all eating styles welcome.&lt;br /&gt;
&lt;br /&gt;
Max *6* people per party this year.&lt;br /&gt;
&lt;br /&gt;
'''Party #1: Chicago Diner''', Wednesday Night http://www.veggiediner.com/ &amp;quot;meat free since '83&amp;quot; &lt;br /&gt;
Will they easily be able to accommodate 6 folks walking in?&lt;br /&gt;
We'll plan on meeting in the conference hotel at 6pm and taking the 8 bus up there (3411 N. Halsted St  Chicago, IL 60657). &lt;br /&gt;
# Jason Ronallo (jronallo@gmail.com)&lt;br /&gt;
# Linda Ballinger (linda dot ballinger at gmail)&lt;br /&gt;
# May Chan (msuicat at gmail dot com)&lt;br /&gt;
# Demian Katz (demian DOT katz AT villanova DOT edu)&lt;br /&gt;
# David Uspal (david dot uspal at villanova dot edu) In for the Country Fried StAEk and/or the Soul Bowl.  Ex-Vegetarian (which may make it a crime for me to go), so if the list is full and you still want in, feel free to email me and I'll gladly turn over my spot to an actual Veg*n.&lt;br /&gt;
# Cynthia Ng (cynthia dot s dot ng at gmail)&lt;br /&gt;
Capped at 6&lt;br /&gt;
&lt;br /&gt;
=== Code4lib/Goose Island Brewing Pull Request ===&lt;br /&gt;
'''When:''' Wednesday, 2/13, 8:00 PM to 11:00 PM&lt;br /&gt;
&lt;br /&gt;
More information and sign up at [https://code4lib2013-estw.eventbrite.com/|https://code4lib2013-estw.eventbrite.com/]&lt;br /&gt;
&lt;br /&gt;
=== Bourbon and barbecue ===&lt;br /&gt;
'''When:''' Wednesday, 2/13, 7:00 PM&lt;br /&gt;
&lt;br /&gt;
Friend of mine tells me his cousin manages a Chicago restaurant, Chicago q, and I should go there and tell him my friend sent me.  [http://www.chicagoqrestaurant.com/menus/dinner.php Menu] keeps talking about artisanal barbecue and extensive bourbon options.  DONE.&lt;br /&gt;
&lt;br /&gt;
Reservation is at 7 for a party of 8.  Add yourselves.  &lt;br /&gt;
&lt;br /&gt;
We can take the number 20 bus to the Red Line. We should plan to meet in the lobby at 6:10; that way we can work with the bus tracker and make a leisurely trip over. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Andromeda Yelton&lt;br /&gt;
* Chris Day [cday2 at saic.edu]&lt;br /&gt;
* Abigail Goben &lt;br /&gt;
* Rosalyn Metz [rosalynmetz at gmail dot com]&lt;br /&gt;
* Dileshni Jayasinghe [d dot jayasinghe at utoronto dot ca]&lt;br /&gt;
* Ray Mathew&lt;br /&gt;
* Dre (Barbecue, yes. Bourbon... well, we'll see.) akorphan at ncsu.edu&lt;br /&gt;
* Sean Chen schen at law.duke.edu&lt;br /&gt;
&lt;br /&gt;
=== Non-beery get together ===&lt;br /&gt;
'''When:''' Wednesday, 2/13, Meet at hotel lobby at around 6:30 (and take public transport over to the park) OR meet us at the rink at 6:45, skating rink closes at 8 PM&lt;br /&gt;
&lt;br /&gt;
'''Where:''' [https://www.cityofchicago.org/city/en/depts/dca/supp_info/ice_skating_at_themccormicktribuneicerink.html McCormick Tribune Ice Rink]&lt;br /&gt;
&lt;br /&gt;
'''Contact:''' @dchud, @ranti, @yo_bj (b dot yoose at gmail), @wendyrlibrarian&lt;br /&gt;
&lt;br /&gt;
'''Cost:''' $10 skate rental, people watching free&lt;br /&gt;
&lt;br /&gt;
Come and (attempt to) skate with us! This is also a good people watching opportunity, so if you don't want to skate, there will be places to hang out around the rink and the park. There is a [http://www.parkgrillchicago.com/cafe/food-menu cafe] near the rink as well, with hot drinks and food.&lt;br /&gt;
&lt;br /&gt;
FYI - For those of you who want something else to munch on while hanging out, there's a [http://www.garrettpopcorn.com/chicago-locations/4-east-madison-street/ Garrett Popcorn Shop] a couple blocks away.&lt;br /&gt;
&lt;br /&gt;
# Chris Sharp (indicating interest)&lt;br /&gt;
# Becky Yoose (ready to fall on her butt repeatedly for the entertainment of others)&lt;br /&gt;
# Peter Murray&lt;br /&gt;
# Shawn Carraway&lt;br /&gt;
# Karen Coombs&lt;br /&gt;
# Michael Levy&lt;br /&gt;
# Christie Peterson&lt;br /&gt;
# Andrew Pasterfield&lt;br /&gt;
# Virginia Schilling&lt;br /&gt;
# Al Cornish&lt;br /&gt;
# Sibyl Schaefer&lt;br /&gt;
# Kalee Sprague&lt;br /&gt;
# Luis Baquera (ready to distract everyone with his own fantastic wipeouts while Becky composes herself)&lt;br /&gt;
# Maccabee Levine&lt;br /&gt;
# Sarah Shealy (I'm pretty sure I'll fall spectacularly as well :) )&lt;br /&gt;
# Emily Lynema (interested!)&lt;br /&gt;
&lt;br /&gt;
=== Flying Trapeze ===&lt;br /&gt;
'''When:''' Monday, 2/11, TBD&lt;br /&gt;
&lt;br /&gt;
'''Contact:''' rosalynmetz at gmail dot com&lt;br /&gt;
&lt;br /&gt;
'''Class is full.'''&lt;br /&gt;
&lt;br /&gt;
No this is not a joke. If you haven't heard Rosy is an aspiring trapeze artists and wants to bring the fun to her friends in Code4Lib.  There is a trapeze rig in Chicago and she plans on visiting it and hopes that some of you can come along as well.  If its your first time taking a trapeze class, they'll start you off learning [http://www.youtube.com/watch?v=_oqPi_zuX7A a knee hang] and depending on how that goes you might be able to catch it at the end of class.  If you have any questions about whether or not this is for you, [http://chicago.trapezeschool.com/classes/trapeze.php TSNY Chicago's website] should have the answer, if not feel free to contact Rosy.&lt;br /&gt;
&lt;br /&gt;
Trapeze classes are $57, last 2 hours, and are limited to 10 people.  Currently TSNY Chicago hasn't release their class schedule for February -- they should be doing that around Jan. 1.  If we can get enough people interested before then, we can buy out a whole class.  If not it'll be first come, first serve (along with the general public).&lt;br /&gt;
&lt;br /&gt;
If you're interested in signing up, feel free to add your name and contact info to the list below.&lt;br /&gt;
&lt;br /&gt;
'''''Sign Up List'''''&lt;br /&gt;
# Jay Luker (first!)&lt;br /&gt;
# Bill McMillin&lt;br /&gt;
# Bess Sadler&lt;br /&gt;
# Karen Coyle&lt;br /&gt;
# Sibyl Schaefer&lt;br /&gt;
# Rosalyn Metz (because I'm organizing)&lt;br /&gt;
# Alicia Cozine&lt;br /&gt;
# Gabriel Farrell&lt;br /&gt;
&lt;br /&gt;
=== Game Night! ===&lt;br /&gt;
&lt;br /&gt;
See the http://wiki.code4lib.org/index.php/2013_game_night page for the latest details and to sign up for individual games or add games you're willing to lead/teach!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Moved this from idea to an actual event.  Still getting some details, but here's what we know:&lt;br /&gt;
&lt;br /&gt;
Game Night!  Type of games might vary due to interest and what people bring. Looks like interest right now is mostly on light to mediumish games with a dash of abstracts ;). &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Rough Schedule:&lt;br /&gt;
* 7:30  setup&lt;br /&gt;
* 7:45  start playing games!&lt;br /&gt;
* 10:00 start winding down (don't start new games)&lt;br /&gt;
* 10:30 all done, turn off the lights&lt;br /&gt;
&lt;br /&gt;
* I highly recommend that people walk in groups to get back to their respective lodgings. I'll ask folks still around at the end to help me clean up so we can walk back to the conference hotel*&lt;br /&gt;
&lt;br /&gt;
Please bring your badge with.  (You don't need to wear it on the way, but that'll help us make sure everyone in the room is supposed to be there.)&lt;br /&gt;
&lt;br /&gt;
We have a conference room at the UIC library (Richard J. Daley Library MC 234, 801 S. Morgan, Chicago) reserved for 7:30 on Tuesday the 11th. I'll try to show up at the lobby and hang out there for at about 7:15.  I'll be the guy with a code4lib nametag and a box of games ;). Not sure how late we'll play, it looks like the library is open till 1:00am, but I suspect I will for now put a rough ending time of 11pm.  &lt;br /&gt;
&lt;br /&gt;
(Note, there's also some discussion on Cards Against Humanity.  I will try to make sure there's an alternative game, but I don't know if I want to prohibit any games. I would say though to remember to be respectful and courteous to those around you. I will probably be pondering this issue for a while)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The original list of people who signed up is below.&lt;br /&gt;
&lt;br /&gt;
I (Jon Gorman) will bring some board games and pick up some cards. Add your name to the list below if you're interested in attending. Also not if you can bring games. Bringing games is NOT REQUIRED. If you can bring a game you can teach, that's great and will make sure we're not just stuck playing the games I bring.&lt;br /&gt;
&lt;br /&gt;
(I've added some comments to the game lists below)&lt;br /&gt;
* jtgorman, aka Jon Gorman: I'll bring Time's Up: Total Recall, Tsuro, Hey, That's My Fish, Hive, and some more I haven't decided on yet.  (My profile over at http://www.boardgamegeek.com/ is jtgorman as well if you want to browse my games and make requests)&lt;br /&gt;
* yo_bj: I have some games I can bring as well (Kill Doctor Lucky, Fluxx, Godzilla: Stomp, Munchkin Zombies, etc.). Monday doesn't have anything major planned... &lt;br /&gt;
*danwho:  I 'll bring the Cards Against Humanity set.&lt;br /&gt;
*escowles (Mon/Tue preferred): I've got lots of games I could bring like Settlers of Catan, Carcassonne, Ticket to Ride, Age of Renaissance, Elfenland, Agricola, Le Havre, Smallworld, RoboRally, etc. etc. &lt;br /&gt;
** Take your pick! All good games.  I'll try to finalize my list of games before Friday - JonG &lt;br /&gt;
*jen_young: I'm local and I have quite a few games. Just about every version of Fluxx, Bananagrams, Gloom, Munchkin Cthulu,Cards Against Humanity, Apples to Apples, Risk, Last Night on Earth, etc.) &lt;br /&gt;
**All good games! If you don't mind bringing a box that would be awesome.  I particularly like Apples to Apples, Last Night on Earth and Gloom  - JonG&lt;br /&gt;
* decasm: Interested in Go (aka igo, weiqi, baduk) anytime, not just game night. I can do Catan as well. (And as much as I love it, Cards Against Humanity is probably a violation of the new Code of Conduct.) &lt;br /&gt;
** I look forward to losing my first game of Go to you ;) - JonG&lt;br /&gt;
** I'd love to learn Go. &amp;lt;del&amp;gt;Perhaps after the newcomer dinner?&amp;lt;/del&amp;gt; Oof... won't make for Tues. But would still be interested to learn.  --ranti.&lt;br /&gt;
* csharp: I'm interested in playing games - whatever people bring.  I almost always travel with a pack or two of playing cards ;-).  Monday or Tuesday nights are fine.&lt;br /&gt;
* moneill: I would love to join in! I have a version of Catchphrase floating around somewhere, and I think I have Battleship...I need to go weed around in that drawer and see what else presents itself. Tuesday would be my preferred night, but I will make it work! &lt;br /&gt;
** Don't worry too much about bringing a game if transportation is a problem. One thing I've done w/ stuff like catchphrase is not take the box but to put pieces and cards in a bag - JOn G&lt;br /&gt;
* demiankatz: I'm always up for a game.  I'm hoping to travel light so probably shouldn't bring anything, but if there's a local game shop, I might be persuaded to pick up something new as a souvenir. &lt;br /&gt;
** Don't worry, I think there will be plenty of games - JonG&lt;br /&gt;
* sekjal: I've got [http://boardgamegeek.com/boardgame/36218/dominion Dominion], [http://boardgamegeek.com/boardgame/68448/7-wonders 7 Wonders], [http://boardgamegeek.com/boardgame/30933/bang-the-bullet Bang!], [http://boardgamegeek.com/boardgame/18333/ecofluxx EcoFluxx] and [http://boardgamegeek.com/boardgame/116/guillotine Guillotine] that I can bring.  ++ on Cards against Humanity!  Prefer non-conflict with beer night. &lt;br /&gt;
** Also all good games. I have 7 Wonders, but can bring some other games if you bring that. - Jon G&lt;br /&gt;
* arty: so totally interested. Unfortunately, I have no games to contribute.&lt;br /&gt;
** No prob.&lt;br /&gt;
* sanderson: I would be interested. I can bring [http://boardgamegeek.com/boardgame/478/citadels Citadels] (2-7 players)&lt;br /&gt;
** Citadels would be awesome and means I don't have to bring it ;) - JonG&lt;br /&gt;
* dvdndrsn: Definitely in! Can bring Innovation, Tichu, Dominion, but Cards Against Humanity sounds good. &lt;br /&gt;
** I'll put in a vote for Tichu, heard good things about it - Jon G &lt;br /&gt;
* smkiewel: I'm likely to join. Can bring Arkham Horror and Munchkin.&lt;br /&gt;
** Arkham Horror seems rather bulky to travel with, but if you want to play bring it ;) - Jon G&lt;br /&gt;
** mbutler: If someone actually brings Arkham Horror I'd throw down. Otherwise, whateve. &lt;br /&gt;
* jkwilson: I'd like to attend Monday or Tuesday. I have a bunch of games but I'd prefer not to travel with them, and anyway it sounds like they're covered above. I'll bring the 5-6 player Catan extension.&lt;br /&gt;
* ejlynema: Interested, but will probably attend Newcomer dinner on Tuesday. Like Dominion and 7 Wonders, but probably don't have room to bring in suitcase. Anyone bringing Tsuro? &lt;br /&gt;
** I can bring Tsuro  - Jon G&lt;br /&gt;
* Christie Peterson (save4use): Also interested, but also probably attending newcomer dinner on Tuesday. Can bring [http://boardgamegeek.com/boardgame/11/bohnanza Bohnanza] and one deck of [http://en.wikipedia.org/wiki/Set_%28game%29 Set].  &lt;br /&gt;
**Bohnanza and Set would be awesome - JonG&lt;br /&gt;
**Done! I will bring them both -- C&lt;br /&gt;
* dgcliff: I'd be interested. Can bring Ticket to Ride.&lt;br /&gt;
* mbklein: definitely interested. Will check on my (currently unpacked) games. I am dying to play Cards Against Humanity. If we can't find a way to reconcile it with the Code of Conduct, we need a different Code of Conduct.&lt;br /&gt;
** Considering that this is a public event, and that no one knows everyone's sensitivity levels in the room, it might not be a good idea to break out a crass, adult version of apples to apples in the middle of the gaming room. :cP (yo_bj)&lt;br /&gt;
* duspal:  In.  My board game collection is small but mighty (Arkham Horror, Catan, Vampire: Prince of the City, Deadlands: Battle for Slaughter Gulch, Arabian Nights, Diplomacy, Shogun, and Cosmic Encounter off the top of my head, amongst a few others).  Let me know ahead of time if anyone is interested, since they're all relatively big... &lt;br /&gt;
** If you really want to play Cosmic Encounter, I can bring my copy (Fantasy Flight edition, 3 expansions), just let me know - JonG&lt;br /&gt;
*librarywebchic: I'm willing to bring a set and teach folks how to play Majhong. Need at least three to play though.&lt;br /&gt;
**beatricep:  Uno gets no respect. ;-)  @librarywebchic: I have always wanted to learn to play Majhong.  If you're still bringing it, I'm in!&lt;br /&gt;
** Agreed, I don't know Majhong and I love learning new games. - JonG&lt;br /&gt;
** I actually know a few different rule sets. It's too bad I don't have a travel set or I'd bring a 2nd one -Arty&lt;br /&gt;
** I'm local and can bring a mahjong set. I've had no one to play with for years, so have probably forgotten how. -Linda B&lt;br /&gt;
* jcraitz: I'm in after the newcomer dinner.  I'll bring Citadels and Bang! &lt;br /&gt;
**I think someone higher in the list offered to bring citadels, but won't hurt to have two copies just in case one of you don't show ;) - JonG&lt;br /&gt;
**Aww no. left my games at the office.  Looks like I'll have to jump in someone else's game.&lt;br /&gt;
* julia: I'll be the freeloader who showed up and didn't bring any games.&lt;br /&gt;
* kenirwin: interested in attending&lt;br /&gt;
* sdellis: attending&lt;br /&gt;
* ianc: interested in attending, a little rusty but definitely up for a couple rounds of Mahjong, also want to try something new too!&lt;br /&gt;
* haschart: Interested in attending, if I can make it work with the newcomer dinner.  Big fan of Dominion lately, but probably cannot bring it `cause the &amp;quot;Big Box&amp;quot; with the base game and two expansion sets is bigger than my suitcase.  I could bring &amp;quot;Race for the Galaxy&amp;quot; if there's any interest.&lt;br /&gt;
* jessebrown: Interested in attending. I can bring Set and Zombie Fluxx.&lt;br /&gt;
* terrywbrady: I would like to attend&lt;br /&gt;
* dan fehrenbach (dnfehren): I would like to attend, can bring Pandemic if anyone is interested.&lt;br /&gt;
* dileshni: interested in attending. &lt;br /&gt;
* Corey Harper: definitely interested in attending if space allows.&lt;br /&gt;
* saverkamp: interested in attending.&lt;br /&gt;
* Emily Shaw: I like games. &lt;br /&gt;
* Alan Dyck: I play Carcassonne and Munchkin among others. I see those listed so I'm bringing a game some friends and I have been creating: Wandering Monster.&lt;br /&gt;
* Heidi Frank (hf36@nyu.edu) - I love card games like gin/rummy, but am open to anything.&lt;br /&gt;
* Sibyl Schaefer - attending, and will bring anything that fits in my carry-on&lt;br /&gt;
* Gary Maixner - Joining. Have a copy of Savage Worlds for roleplaying if anyone's interested.&lt;br /&gt;
&lt;br /&gt;
-- *Please, please, please, if you're signing up on this list, also sign up for a paritcular game slot to start out the evening or put your game in: http://wiki.code4lib.org/index.php/2013_game_night&lt;br /&gt;
we're having so many people sign up after Jan. 14th we're in risk of overflowing the room.  (I should have put in a cap limit, but given how late I realized this, I haven't *&lt;br /&gt;
&lt;br /&gt;
I have to confess, I started trying to organize what games certain people were bringing, but it got confusing fast and I don't want anyone to feel compelled to bring anything or feel bad if they can't make it.  So if there is something you're dying to play, let me know and I'll try to bring it if I have it.&lt;br /&gt;
&lt;br /&gt;
== Social Map - Places of Interest==&lt;br /&gt;
&lt;br /&gt;
https://maps.google.com/maps/ms?msid=213549257652679418473.0004ce6c25e6cdeb0319d&amp;amp;msa=0&lt;br /&gt;
&lt;br /&gt;
== Layar: augmented reality Code4Lib view of Chicago ==&lt;br /&gt;
&lt;br /&gt;
There's a &amp;quot;Code4Lib 2013&amp;quot; layer in [http://www.layar.com/ Layar], an augmented reality app that runs on both Android and iOS. You can use it to scan around the city to see two kinds of things: 1) tweets using the #c4l13 or #code4lib hashtag (if the tweets are geolocated so they can be&lt;br /&gt;
nailed to a point) and 2) points of interest from the [https://maps.google.com/maps/ms?msid=213549257652679418473.0004ce6c25e6cdeb0319d&amp;amp;msa=0 shared Google Map]. &lt;br /&gt;
&lt;br /&gt;
To use it:&lt;br /&gt;
&lt;br /&gt;
* install Layar on your phone&lt;br /&gt;
* run it and click to go into Geo Layers mode&lt;br /&gt;
* search for &amp;quot;code4lib 2013&amp;quot;&lt;br /&gt;
* launch the layer and look around&lt;br /&gt;
&lt;br /&gt;
See Code4Lib people and events overlaid on top of Chicago, in real time! See an alternate view of the city that's all about libraries and coders!&lt;br /&gt;
&lt;br /&gt;
To make your own tweets appear, use the #c4l13 hashtag and make sure the tweet is geolocated.  In Twitter's client you need to do this by enabling geolocation in settings and then enabling it for each tweet.&lt;br /&gt;
&lt;br /&gt;
Source code running this: [https://github.com/wdenton/laertes Laertes]. Bill Denton set it up and is very curious to find out if it's useful, so let him know if you try it out.&lt;br /&gt;
&lt;br /&gt;
== Local Events ==&lt;br /&gt;
Events Listings&lt;br /&gt;
* Chicago Reader http://www.chicagoreader.com/&lt;br /&gt;
* The City of Chicago’s Events Guide: http://www.choosechicago.com/ &lt;br /&gt;
* Metromix Chicago: http://chicago.metromix.com/events &lt;br /&gt;
* Timeout Chicago: http://timeoutchicago.com/&lt;br /&gt;
* Chicago Studio Club's [http://www.google.com/calendar/embed?title=LIVE%20MUSIC%20in%20Chicagoland%20via%20Chicago%20Studio%20Club!%20&amp;amp;height=1000&amp;amp;wkst=1&amp;amp;hl=en&amp;amp;bgcolor=%2399ff99&amp;amp;src=info%40chicagostudioclub.net&amp;amp;color=%237A367A&amp;amp;ctz=America%2FChicago Live Music Google Calendar]&lt;br /&gt;
&lt;br /&gt;
== Local Food ==&lt;br /&gt;
== Local Drinks ==&lt;br /&gt;
==Chicago Events Feb 10-14==&lt;br /&gt;
&lt;br /&gt;
=== Sunday February 10===&lt;br /&gt;
Theater - [http://www.neofuturists.org/ Too Much Light Makes the Baby Go Blind] &amp;quot;...with its ever-changing &amp;quot;menu,&amp;quot; is an attempt to perform 30 plays in 60 minutes. &amp;quot; 7pm.&lt;br /&gt;
&lt;br /&gt;
Theater  - [http://www.chicagoreader.com/chicago/chunks/Event?oid=8557720 Chunks] :  Funny, Heartbreaking, Gross. 7pm &amp;amp; BYOB!&lt;br /&gt;
&lt;br /&gt;
===Monday February 11===&lt;br /&gt;
&lt;br /&gt;
Music - [http://www.hideoutchicago.com/event/208497-robbie-fulks-michael-miles-chicago/ Robbie Fulks at the Hideout]&lt;br /&gt;
&lt;br /&gt;
[http://fedora4lib.org/ fedora4lib] - 7 pm to whenever&lt;br /&gt;
&lt;br /&gt;
===Tuesday, February 12===&lt;br /&gt;
&lt;br /&gt;
Concert - [http://www.thefatbabies.com/ The Fat Babies] playing at an awesome venue, [http://greenmilljazz.com/ The Green Mill].&lt;br /&gt;
&lt;br /&gt;
[http://fedora4lib.org/ fedora4lib] - 7 pm to whenever&lt;br /&gt;
&lt;br /&gt;
===Wednesday, February 13===&lt;br /&gt;
===Thursday, February 14===&lt;br /&gt;
Tour of the [http://www.newberry.org/ Newberry Library] -- 3:30 p.m.&lt;br /&gt;
This will be a special tour for Code4Lib attendees, so please sign up below if you are interested, as I'll need to give the tour guide an estimate of how many people will come. Details on how to get to the Newberry will follow. Questions? Contact ballingerl at newberry dot org&lt;br /&gt;
&lt;br /&gt;
'''''Directions: '''''&lt;br /&gt;
The Newberry is at 60 W Walton St. It could take half an hour to get there from the conference hotel via CTA, so those of you who wish to take public transit as a group can meet me in the hotel lobby by 3:00. We will then go to the UIC-Halsted El stop (5 blocks from hotel), change trains in the Loop, then walk 3-4 blocks to the Newberry. Otherwise, plan on making your preferred way there and meet in the Newberry lobby by 3:30.&lt;br /&gt;
&lt;br /&gt;
'''''Sign Up List'''''&lt;br /&gt;
# Michael Doran - doran@uta.edu&lt;br /&gt;
# William Denton - wtd@pobox.com&lt;br /&gt;
# Wayne Schneider - wschneider@hclib.org&lt;br /&gt;
# Matt Cordial - rev3lator [at] gmail.com&lt;br /&gt;
# ryan hess - mhess8 [at] depaul.edu&lt;br /&gt;
# [[User:ianc|Ian Chan]] ichan@csusm.edu&lt;br /&gt;
# Richard Aroksaar - richard_aroksaar@nps.gov&lt;br /&gt;
# [name] - [email address]&lt;br /&gt;
# Laurie Lee Moses - lmoses [at] colum.edu&lt;br /&gt;
# Ray Schwartz - schwartzr2@wpunj.edu&lt;br /&gt;
&lt;br /&gt;
== Music ==&lt;br /&gt;
&lt;br /&gt;
There's a [http://www.rdio.com/people/wdenton/playlists/2229053/Code4Lib_2013_in_Chicago/ Code4Lib 2013 in Chicago] collaborative playlist on Rdio. If you're a subscriber, have a look, and add something you think everyone would like to hear or use as their personal soundtrack while they're hacking and exploring Chicago.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2013]]&lt;/div&gt;</summary>
		<author><name>Afred</name></author>	</entry>

	</feed>